Stay audit-ready with confidence.

The platform implements the controls 21 CFR Part 11 requires of an electronic record system: enforced multi-factor authentication, role-based access control that scopes what each user can see and change, tamper-evident audit logging on every user action and alarm event, and time-stamped electronic signatures on acknowledgements recording who accepted an alarm and when. Validation is supported through customer-led IQ/OQ/PQ packages, which is the model regulated sites usually need, because the system being qualified is your configured deployment rather than the vendor's. Two practical notes for an evaluation: the security page lists each control alongside the plan tier that carries it, since audit logs are a Professional and Enterprise plan feature, and Part 11 applies to the record system as operated, so the IQ/OQ/PQ documentation exists to support the assessment an auditor will actually perform.

A configuration lists the generators it covers, and for each one the minimum load percentage the machine must hold during a test, 30 percent by default, so a 750 kW generator has to hold 225 kW. A report trigger marks the start of a run: the generator breaker closing, or a transfer switch calling for the engine. From there the platform does the watching. It re-checks each active configuration hourly, scans the previous day for generator runs, and writes one report per run it finds, so a test performed on Tuesday shows up without anyone opening the page. A run passes when the generator holds the configured load for 30 continuous minutes; otherwise the report is marked Incomplete with the reason stated, such as the load threshold never being reached or a transfer switch exceeding its required transfer time. Save to PDF produces the inspector copy, and Regenerate rebuilds a report if the underlying data changed.

Yes. Generator runtime reports list every run with its start time, end time, and duration, and split the totals into emergency and non-emergency hours, which is the shape EPA reporting asks for. Runs are detected from the generator's engine hours reading, so any generator that reports hours to the platform builds its own log with no operator input. When a run recorded as routine was in fact an outage, Mark As Emergency opens an override that records the emergency duration and a comment; the original record is kept and the row is shown as overridden, so the correction itself becomes part of the audit trail rather than a silent edit. The report opens on the current year to date with each run charted as a bar in hours, and the period can be changed to match whatever window the filing covers.

Every user action and alarm event lands in a tamper-evident audit trail, and alarm acknowledgements carry a time-stamped electronic signature recording who accepted the alarm and when. Acknowledgement is only possible while an event is still active, so the record distinguishes a response made during the condition from one added after the fact. Role-based access scopes who could have acted at all: Administrator, Editor, and View roles bound what each account can change, and enforced multi-factor authentication ties an identity in the log to a person rather than a shared password. When the question comes up in an audit, the answer is a query rather than an investigation: alarm history filters by date, asset, location, and assignment, each event shows its notifications and acknowledgement, and the export carries the full filtered record. Audit logs are included on the Professional and Enterprise plans.

No. The ControlCom Edge Server connects to existing controllers, BMS, and SCADA systems over Modbus TCP/RTU, OPC-UA, EtherNet/IP, BACnet, and MQTT, and reads the values those systems already expose, so the control layer keeps running as it does today. For a compliance evaluation, the architecture detail that matters is the direction of traffic: the Edge Server makes outbound connections only and opens no inbound ports into the OT network, which keeps the monitoring layer from becoming a network-security finding of its own. It also buffers readings locally through a WAN outage, so the compliance record has no gap for the week the internet dropped. The platform then adds what the control systems were never built to provide, the audit trail, the signatures, and the reports, on top of equipment that does not change.

Three ways, matched to how auditors actually ask. For a hand-over document, any generated report saves to PDF: a generator compliance report for the inspector, or an asset data report covering the period in question. For recurring filings, scheduled reports run hourly, daily, weekly, or monthly and email the PDF to the recipients you list, inside or outside the organization, and each job keeps a run history showing every delivery and its result, which is itself evidence that the reporting process operated. When the auditor wants underlying data rather than a document, Export to CSV downloads the raw readings, flat with one row per reading or pivoted with one row per timestamp and a column per variable, and alarm history's Export All fetches the complete filtered event record from the server rather than just the rows on screen.