Answers for technical evaluations.

An on-premise edge computing platform and high-performance distributed time-series historian that connects to machines, archives data and provides monitoring and visualization.

Sensors, SCADA systems, databases and other operational or GxP systems, using native and aggregated data streams.

Connect more devices to add tags, streams, storage and compute. Plug-and-play nodes start talking to each other immediately.

Role-based access control and audit trails are built in. It is 21 CFR Part 11 compliant for life sciences and certified “Safe-To-Host”.

Subscription includes technical assistance, modelling support, maintenance and user training. Support covers the two most recent versions.

A tag-based subscription covers unlimited users and client connections, and includes Grafana dashboards and the plugin. The Stimulsoft reporting engine is licensed separately per site. Hardware is a one-time cost and is not part of the subscription.

Yes. The REST API exports history, metadata, timestamps and event context for migration to another historian or data lake, and tags can be deactivated without losing history.

The OPC-UA client reconnects automatically and resumes with the source’s own timestamps. Only the outage itself cannot be captured, since the source made no values available. Each site cluster also acquires and stores locally, so a site-to-central network outage loses no site data.

Only good-quality values are retained. Bad values go to a separate dead-letter queue for later investigation. Storage is lossless and ordered by source timestamp.

No. It runs inside your existing IT, OT, LAN or WAN, including DMZs and data diodes, with read-only, port-level access.

Factorian keeps the timestamp assigned by the source system and synchronizes its own clock from an authoritative time source, so every record shares one time base.

No. Raw source data and audit entries cannot be modified or deleted, even by administrators. Only metadata such as tag names, scaling or hierarchy can change, and every change is logged.

Not in the traditional sense, because historian data comes straight from machines with no manual approval of individual values. Where a quality process needs a signature on a report, it is typically handled in the reporting or document-management layer.

Process data stays online for five years or more, and metadata and audit-trail records are kept for the lifetime of the product. Old data is read through the same interfaces, with no archive restore.

Supplier quality documentation (development lifecycle, change control, release and defect management) and a sample requirements-traceability matrix can be assembled to support your validation or computer software assurance approach.

Dashboards run on Grafana through a zero-code plugin. Reports use an integrated Stimulsoft engine with revision tracking. Time-range reports can be scheduled, batch reports run on demand, and data exports to PDF, CSV or Excel with timestamps and quality codes.

Yes. Context follows an asset hierarchy aligned to ISA-88 and ISA-95, so batch, phase, alarm and process-parameter data line up on one timeline and one dashboard.

Authentication is delegated to Active Directory/LDAP, so your password and lockout policies apply. MFA works through your Microsoft 365/Azure AD sign-in. Hardware-token factors depend on what your identity provider supports.

You are emailed when security patches are available, and blue-green updates are supported where applicable. OPC-UA uses a locally generated certificate valid for ten years, and a CA-issued one can be substituted. Vendor remote support goes through your own zero-trust access controls.

Four predefined roles (Super-Admin, Admin, User, External) plus custom groups for viewing, configuration, export and audit review, supporting least privilege and segregation of duties.

Web traffic uses HTTPS, OPC-UA sessions use sign-and-encrypt, and only port 443 is open externally by default. A full port matrix and hardening guide are available.

Yes. It runs alongside standard endpoint protection and has been tested with CrowdStrike.

Adding or updating a tag needs no restart. There is no built-in pre-change approval workflow, so approvals are handled in your change-request process and verified afterwards using the audit trail.

In a multi-node cluster every node replicates data in near real time. If a node fails, the others continue acquisition, storage and visualization without manual failover.

Backups cover configuration, the tag database, metadata, audit trail and security settings. With daily backups, expect about a day of data at risk and roughly three to four hours to restore.

Rack hardware is rated 0 to 50°C and 0 to 95% non-condensing humidity. Smaller clusters (under 10,000 tags) use rugged fanless DIN-mount units for the plant floor.

Through two read-only interfaces: an MQTT broker for live feeds and a secure REST API over HTTPS. Nothing outside can write back to the historian.

The two most recent versions are supported. Upgrades carry tag configuration, history, audit trails and security settings forward automatically.