INTELLISYS / WORKFLOW

How it works

From administrator setup to an employee's daily workspace.

01 / ADMINISTRATOR

Turn a server into
assigned places to work.

Select the deployment, choose models and dependencies, then create employee environments with the right Harness.

ENVIRONMENT LIFECYCLE

Prepare once. Operate with a clear lifecycle.

Full size ↗
Prepare once. Operate with a clear lifecycle.. An environment keeps its Harness for its lifetime. Changing it currently requires deletion and a new environment with empty private directories.
An environment keeps its Harness for its lifetime. Changing it currently requires deletion and a new environment with empty private directories.

02 / EMPLOYEE

Bring material in.
Use the right combination.
Review the result.

CroLink connects the employee to their environment. The runtime, model, tools and business setup determine how the task is carried out.

FROM INFRASTRUCTURE TO WORK

A runtime, a model, and the right tools

Full size ↗
A runtime, a model, and the right tools. Actual capabilities depend on the selected Harness, model, dependencies, skills and business configuration.
Actual capabilities depend on the selected Harness, model, dependencies, skills and business configuration.

Document workflows

Prepare source materials, work through documents and review the resulting files.

Data analysis

Combine data, repeatable scripts and the selected model to explore a question.

Software development

Use terminal tools, code and project files in an assigned environment.

Application scenarios, illustrated conceptually. Actual results depend on the runtime, model, tools and business setup.

03 / CONTINUITY

Reconnect to work
that stayed on the server.

Gateway-held terminal sessions can continue while the client is offline. Persistent files and running processes have different lifetimes.

TERMINAL LIFECYCLE

Your connection and your task have different lifetimes

Full size ↗
Your connection and your task have different lifetimes. Client disconnects can leave the program running. Gateway restart or terminal link failure ends the session; detached background processes may continue in the container.
Client disconnects can leave the program running. Gateway restart or terminal link failure ends the session; detached background processes may continue in the container.