Skip to content
Scope4mation · Service Automation Suite
SASService Automation Suite
SAS Wiki
DocumentationPublicDoc version 1.0Source reviewed 2026-08-22

How SAS works

How process control and integration meet in the SAS platform.

On this page

SAS links two realities:

  • the business and service process that an organization must control;
  • the systems, APIs, data, people, and tasks that make that process work.

The operating model

  1. Connect & Integrate — connect APIs, endpoints, services, data stores, and existing applications.
  2. Structure — make data, inputs, actions, decisions, and responsibilities explicit.
  3. Orchestrate — run steps in the required order and coordinate systems and people.
  4. Control — monitor status, SLA, exceptions, permissions, policies, and evidence.
  5. Improve — use results, rework, trends, and operational insight to change the process deliberately.

Current components

Outcome Component
SAS calls an external REST API API Composer
An external caller accesses approved SAS data Endpoint Composer
Data is combined or transformed Dataflow Composer

Target platform model

The Process Orchestrator becomes the place where the complete flow is designed, executed, monitored, and improved. The Composers and other SAS components remain the building blocks used by that flow.

The SAS Cloud Management Platform sits above runtime instances and manages organizations, environments, access, lifecycle, usage, and partner service delivery.

Take the next step

Use the reference material for details or discuss your question with the team.

Ask your question