Corrective Actions
Overview
The Corrective Actions module enables automated workflows to ensure prompt response and traceability when temperature thresholds are breached by sensor devices. This system integrates deeply with the platform-as-a-service structure to allow dynamic, customized forms and operations triggered by sensor data.

Step 1: Creating the Corrective Action Form
1.1 Purpose
This form is used to capture actions taken in response to sensor alerts. It combines telemetry data with predefined workflows to guide the user.
1.2 Using the Form Builder
Start with the Form Builder.
Use prebuilt templates where possible (e.g., Sensor Corrective Actions V2 PROD), or create a new form from scratch.

1.3 Include Sensor Data via API Tags
Add fields for:
Device name, tag, label, and source
Current temperature (
iot.value,iot.valueprobe,iot.valueambient)Timestamps (
iot.now)Recent historical readings (
iot.prevhistories)Alert message (
iot.message)
Use the iot.* tags in Field Tags under the API tab. Fields should be disabled for editing.

1.4 Corrective Action Inputs
Include components for:
Predefined checklists (e.g., transfer food, close door, inform engineer)
Alarm snooze selection (3h, 6h, 12h, 24h)
Maintenance mode toggle
Comments or remarks
Optional image upload for evidence
Optional digital signature

1.5 Navigation Link
Add a "Go to Device" button using iot.dashboardlink to let users access live sensor dashboards.
Step 2: Configuring the Operation
2.1 Add to Work Area
Navigate to the appropriate Work Area.
Create a new operation (e.g., Sensors - Alerts & Actions).
Assign the Corrective Action Form to this operation.
2.2 Required Settings
Operation Mode: Must be set to
Multipleinstance.Manual Trigger: Disable (the system auto-triggers based on alerts).
Expire: Define expiry (e.g., 24 hours). After this period, instances auto-close.
Report View: Recommend
Active Instancesas default.Submission Table: Enable for review.

2.3 Public Access
To simplify submission:
Enable Allow Public Submission.
Disable login requirement via Public Settings tab.
Share the provided public URL via email or WhatsApp.

2.4 UI Enhancements
Configure Card Builder to display Device Name, Timestamp, Alert Message for a clear user dashboard.

Step 3: Linking to Sensor Dashboard
3.1 Assigning the Operation
As an Admin, go to the Sensor Dashboard.
Open the Corrective Actions tab.
Select the operation previously configured.
Click Save to complete the assignment.


Step 4: Runtime Behavior
4.1 Triggering Events
Triggered automatically when threshold and delay are exceeded.
Instance created with live data from the sensor.
4.2 User Interaction
Users complete the form directly via notification link.
On submission, the corrective action is closed.
4.3 Data Management
All corrective actions are logged in the operation table.
Exportable as Web Report, PDF, or CSV for audit and compliance.
Summary
Corrective Actions is a powerful automation tool for managing sensor anomalies. With modular configuration, API data tagging, and real-time integration, it supports fast response, traceability, and compliance.
Always test form behavior and user permissions in a staging environment before full deployment to ensure a smooth and compliant rollout.
Last updated
Was this helpful?
