Integrations
Validated maintenance actions in the systems your team already uses
SAM4 turns detected faults into structured findings: asset ID, fault type, severity, evidence, recommended action, and status. Those findings can route into your CMMS, SCADA environment, historian, API workflow, email, or team notifications. No duplicate data entry. No extra dashboard dependency. Your teams keep working in the systems they already trust.
From validated fault to maintenance action
SAM4 does not just send anomaly pings. Customer-facing fault alerts include the affected asset, likely fault, severity, evidence, and recommended next step. They can route into your CMMS, SCADA environment, API workflow, email, or team notifications.
SAM4 detects and validates
SAM4 identifies fault patterns in the electrical signal and compares them with the asset's baseline. Ambiguous, urgent, and edge-case findings are reviewed by Samotics reliability engineers before notification.
Result: a validated finding, not a raw anomaly.
The finding routes to your systems
Validated findings can flow into your CMMS as work orders, into SCADA or historians as health signals, or into enterprise workflows through API, webhook, email, SMS, or Slack.
Result: structured data where your team already works.
Maintenance acts
Your team receives the likely fault, asset ID, severity, evidence, and recommended action. Feedback from inspection and repair can feed back into the monitoring loop.
Result: action without duplicate data entry.
One finding, routed for each team
A SAM4 finding can become different outputs for different teams: a work order for maintenance, diagnostic evidence for reliability, a critical notification for operations, and structured data for enterprise systems. Same finding. Different format.
work order
dashboard
Slack
webhook
Maintenance planner
Reliability engineer
Operator / site lead
Enterprise systems team
What every validated fault contains
SAM4 does not send raw anomaly pings. A validated fault is a customer-facing finding that has passed SAM4's automated checks and, where needed, reliability engineer review. Each report contains the asset, fault type, severity, evidence, recommended action, and delivery status your team needs to act. The same structure can appear as a CMMS work order, SAM4 dashboard report, email notification, API payload, or webhook event.
Which asset is affected, where it sits, which component is involved, and what fault mechanism is suspected.
How severe the fault is, how quickly it is progressing, how confident the finding is, and when your team should act.
Where the finding was sent, which system reference was created, and what feedback is needed after inspection or repair.
Keep the workflow. Add validated fault intelligence.
SAM4 can route validated findings into your CMMS, SCADA environment, historian, API workflow, or SAM4 dashboard. Each finding includes asset ID, fault type, severity, diagnostic evidence, recommended action, and status. Integration is configured during onboarding so planners, operators, and reliability teams receive SAM4 output in the systems they already use.
SAP Plant Maintenance
SAM4 can create SAP PM notifications or maintenance orders with mapped functional location, fault classification, priority, description, and recommended action.
IBM Maximo
SAM4 can create Maximo work orders with asset reference, fault classification, severity, diagnostic context, and recommended action.
Other CMMS platforms
Any CMMS that accepts structured API input can receive SAM4 findings. Samotics maps incident fields to your work-order schema during deployment.
SCADA and historian overlay
SAM4 health, status, and selected metrics can appear alongside existing process data in SCADA, historians, or operational dashboards. Best for control-room visibility, operational context, and site-level review.
Typical setup: custom CMMS integrations are configured in 1 to 2 weeks, depending on system access, field mapping, and customer approval. SAM4 improves the workflow you already use. It does not replace it.
Programmatic access to SAM4 incidents, metrics, and asset data
SAM4 exposes structured data through REST APIs, webhooks, exports, and notification channels. Use it to feed CMMS workflows, SCADA overlays, historians, BI tools, enterprise data platforms, and digital twins. Data is delivered as JSON over HTTPS. API documentation, authentication details, field mapping, and webhook configuration are provided during onboarding.
Pull SAM4 data into your systems
Query assets, incidents, recommendations, severity status, diagnostic context, and time-series metrics. Use the API to populate dashboards, historians, data platforms, or custom maintenance workflows.
Push events when something changes
SAM4 can send incidents and selected metric updates to configured endpoints when they happen. Use webhooks to trigger work orders, SCADA events, notifications, or custom automations without polling.
Asset-level time-series data
Access current, voltage, power, power factor, energy, runtime, load, speed, and supported pump-performance estimates at configured intervals.
For teams without system integration
Validated findings can be delivered by email, SMS, or team notifications. Each alert includes fault type, asset, severity, evidence, and recommended action.
What SAM4 sends. What SAM4 expects.
Every integration starts with a data contract. Here is what flows in each direction.
What SAM4 sends (per incident)
| Field | Type | Description |
|---|---|---|
| ci-number | string | Incident ID in SAM4 (e.g., CI-1234). Use for customer-facing workflows. |
| motor-id | string | Unique asset identifier in SAM4. Maps to your CMMS equipment number. |
| status | enum | Severity level: MONITORING, DEGRADING, or FAILING. |
| type | enum | Fault category: MECHANICAL, ELECTRICAL, or PUMP_PERFORMANCE. |
| advice | string | Recommended action written by a Samotics reliability engineer. Populates the CMMS work order description. |
| failure-modes | array | Specific failure mode classification (e.g., bearing damage, cavitation, blockages). |
| start-timestamp | integer | Unix timestamp (ms, UTC) when the incident started. |
What SAM4 expects (per asset)
| Field | Type | Description |
|---|---|---|
| application_type | enum | Asset classification: Pump, Fan, Compressor, Conveyor, Mixer, Blower, or Other. |
| rated_voltage | integer | Motor nameplate voltage (V). |
| rated_rpm | integer | Motor nameplate speed (RPM). |
| power | number | Rated motor output power (kW). |
| amps | number | Rated current (A). |
| cmms_equipment_number | string | Your internal asset ID. Maps SAM4 assets to CMMS functional locations. |
Secure integration without opening your OT network
SAM4 does not require inbound access to your network. The NOVAQ device initiates outbound-only communication to the Samotics platform. It measures current and voltage for monitoring only; it does not write to PLCs, issue control commands, or change process setpoints. Full security architecture →
Outbound-only architecture
The NOVAQ device initiates communication to the Samotics platform. No inbound ports, VPN tunnel, or remote access into the customer network is required.
Read-only measurement
SAM4 captures electrical signals from the motor supply. It does not interact with control logic, send commands to equipment, or modify plant operation.
Cellular, Ethernet, or Wi-Fi
Cellular can keep the monitoring path separate from the customer network. Ethernet or Wi-Fi can be used where approved by IT and security.
Certified and tested
ISO 27001 and ISO 9001 certified. Annual independent penetration testing. Security documentation is available for customer review.
Clear boundaries for enterprise integration
SAM4 is designed to fit into existing maintenance, operations, and data systems. It does not replace CMMS, SCADA, or process-control systems. These are the boundaries to expect.
Validated findings only
SAM4 does not push raw anomaly pings or unreviewed detections into work-order queues. Customer-facing findings are validated before delivery.
CMMS creation, not automatic closure
SAM4 can create CMMS notifications or work orders. It does not automatically close tickets or change work-order status unless specifically scoped.
1-minute API metrics
Standard metric data is available at 1-minute intervals. Sub-second waveform data is not exposed through standard external APIs.
OPC-UA requires scoping
Standard deployment uses REST API, webhooks, and exports. OPC-UA connectivity requires site-specific configuration and validation.
SAM4 does not control the process
It can surface asset health and selected metrics alongside SCADA data, but does not send control commands, change setpoints, or write to PLCs.
SCADA integration is for visibility
SAM4 can support overlays, events, or health signals. It is not a process-control system.
Customers retain control of their data
Samotics uses customer data only as permitted for service delivery, support, security, and platform improvement. Export and deletion requests are handled according to contract and retention policy.
SAM4 sends validated monitoring data into your workflow. It does not take control of your workflow or your process.
Connect SAM4 to your maintenance workflow
See how SAM4 fits your CMMS, SCADA, and operational processes.