Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Factory Sensor Monitoring and Incident Management

Factory Sensor Monitoring and Incident Management is a 9-node automation blueprint connecting AMQP, PagerDuty, CrateDB. Inspect its trigger, execution graph, branches, and implementation requirements.

AMQPPagerDutyCrateDB

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

9

Nodes

8

Links

1

Run groups

Connected tools

3 integrations

  • AMQP
  • PagerDuty
  • CrateDB

Canvas controls

Fit wide systems, then zoom into any run group.

Factory Sensor Monitoring and Incident Management execution lanes1 run groups containing 9 workflow nodes and 8 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Data from factory sensors. trigger node, amqpTrigger. 0 incoming and 2 outgoing connections.STARTData from factory sensorsTRIGGERAMQPTRIGGER0 IN / 2 OUTValues higher than 50°C. decision node, if. 1 incoming and 2 outgoing connections.STEP 02Values higher than 50°CDECISIONIF1 IN / 2 OUTData enrichment (°C to °F). transform node, function. 1 incoming and 1 outgoing connections.STEP 02Data enrichment (°C to °F)TRANSFORMFUNCTION1 IN / 1 OUTCreate an incident. integration node, pagerDuty. 1 incoming and 1 outgoing connections.STEP 03Create an incidentINTEGRATIONPAGERDUTY1 IN / 1 OUTDo nothing. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 03Do nothingINTEGRATIONNOOP1 IN / 0 OUTSet sensor data. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Set sensor dataTRANSFORMSET1 IN / 1 OUTSet incident info. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Set incident infoTRANSFORMSET1 IN / 1 OUTIngest machine data. integration node, crateDb. 1 incoming and 0 outgoing connections.STEP 04Ingest machine dataINTEGRATIONCRATEDB1 IN / 0 OUTIngest incident data. integration node, crateDb. 1 incoming and 0 outgoing connections.OUTCOMEIngest incident dataINTEGRATIONCRATEDB1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.9 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Data from factory sensors

8 Execution Links

  1. Start

    Data from factory sensors

    Trigger

  2. Step 2

    Values higher than 50°C

    Decision

    Data enrichment (°C to °F)

    Transform

  3. Step 3

    Create an incident

    Integration

    Do nothing

    Integration

    Set sensor data

    Transform

  4. Step 4

    Set incident info

    Transform

    Ingest machine data

    Integration

  5. Outcome

    Ingest incident data

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas