| Electronic permit-to-work workflows | Documented by vendor | ePAS is described as a web-based integrated safe-system-of-work product with configurable workflows, approvals, permit templates, hazard/control visibility and EAM integration. Customer rules, roles and acceptance testing determine the implemented control. Electronic permitting and safety |
|---|
| Hazard identification and risk assessment | Documented by vendor | ePAS documents location-specific hazards, HIRA configuration and lessons associated with equipment or assets. A configured risk screen does not replace competent assessment, site verification or required professional judgment. Electronic permitting and safety |
|---|
| Hot-work and confined-space permit configuration | Depends on scope | The ePAS page documents specialized HIRA, atmospheric-test requirements and rescue-plan attachments for these permit types. The software records and enforces configured requirements; it does not perform gas testing or certify the work area. Electronic permitting and safety |
|---|
| Isolation and lockout/tagout management | Documented by vendor | ePAS documents isolation templates, cross-referencing, isolation-point validation and tag printing. Demonstrate site-specific point identity, independent verification, group isolation, concurrent work and release controls. Electronic permitting and safety |
|---|
| Permit audits and reporting | Documented by vendor | ePAS documents safety-document audits, configurable questions and scoring plus auditable permit records across departments and sites. Validate immutability, amendments, signatures, retention and export requirements. Electronic permitting and safety |
|---|
| Barrier-health and mitigation visibility | Depends on scope | RiskPoynt documents telemetry-driven barrier status, degradation alerts and mitigation streams across assets and sites. Value and safety relevance depend on mapped sources, data quality, latency and outage handling. RiskPoynt process safety |
|---|
| Permit and barrier integration | Depends on scope | RiskPoynt describes integration with ePAS to show cumulative risk, degraded barriers and mitigation validation. Require proof of the configured gating behavior, data timestamp, override authority and audit trail; visibility alone is not an automatic interlock. RiskPoynt process safety |
|---|
| Offline Mobile EAM work execution | Depends on scope | Mobile EAM documents offline generation, execution and completion of work orders with synchronization to supported SAP, Oracle or IBM Maximo systems when connectivity returns. Confirm the exact ERP version, objects, on-device security and conflict rules. SAP Mobile EAMOracle Mobile EAM connectivity boundary |
|---|
| Mobile rounds, inspections, parts and media | Depends on scope | The mobility page documents offline readings, inspections, operator rounds, parts tracking and annotated media. Validate device/OS support, storage limits, attachment retry, barcode handling and supervisor review. SAP Mobile EAM |
|---|
| Disconnected permit approval and release | Not verified | The reviewed mobility material does not establish offline ePAS issue, approval, suspension, isolation release or live RiskPoynt checking. Do not transfer Mobile EAM offline claims to safety-critical control-of-work decisions. |
|---|
| Mechanical-integrity inspection records | Documented by vendor | Mechanical Integrity documents asset-linked readings, inspection protocols, non-conformances, documents, version history, field packs and traceability. Engineering codes, intervals and acceptance criteria still require controlled configuration. Mechanical integrity |
|---|
| Mechanical-integrity to CMMS handoff | Depends on scope | The product page describes connections to SAP, Maximo, Oracle or Infor and flow of non-conformances, evidence and inspection context. Demonstrate work-order creation/update, duplicate prevention, failed-message recovery and authoritative status. Mechanical integritySAP, Oracle and IBM Maximo integration scope |
|---|