1. Access and responsibilities
Defines who can start and review tasks, which resources are in scope and who administers the configuration.
See how the design organizes access, execution and records.
Use this reference to define what your deployment needs to demonstrate. The five responsibilities below show how the platform organizes execution. The demonstration shows what is available today; the pilot confirms the configuration and the limits that apply to your environment.
Five responsibilities in the design
2. Execution configuration
Brings together the environment, files, systems, tools, credentials and review requirements for the task.
3. Temporary environment
Provides for running the agent in an environment per task. Disposal and separation are part of the deployment assessment.
4. Events and decisions
Provides for assessing execution events and requesting review of actions defined by the organization. Approval during execution still needs a specific demonstration.
5. Records for review
Provides for preserving inputs, output files, events and decisions. The scope defines records, periods and audit requirements to assess.
What your team needs to be able to answer
Before
What data and systems are involved? Who authorizes access and defines the expected output?
During
What events need to be available? Which situations require review or interruption?
After
What files and decisions can be inspected? For how long? Who can access them?
See a run and its records
In the 30-minute meeting, we present a live or previously prepared run in ContactLab’s environment. You see the inputs, output and available records from that same run. Then we discuss your workflow and what the pilot needs to assess.