Data boundaries
The platform is described as using database-level workspace separation with facility-level access. Review the isolation model, administrative access and export permissions for your proposed deployment.
Enterprise evaluation center
Bring the questions your IT team will ask.
A clear evaluation starts with documented boundaries: where data lives, who can act, how systems connect and which evidence establishes operational readiness.
This page is an evaluation guide based on the platform’s described capabilities. It is not an independent security attestation or a published performance benchmark.
Review the controls
Make the operating boundary explicit.
Identity & operational roles
Microsoft 365 sign-in and role-scoped access are part of the platform positioning. Agree identity lifecycle, privileged access and segregation of review and release responsibilities during evaluation.
Versioned accounting
Inspect how run versions, period close and subsequent adjustments preserve the original record. Request examples that show a correction and its downstream consequences.
AI governance
Treat inferred mappings and recommendations as drafts. Establish reviewer authority, approval evidence and the boundary between a study and the production ledger.
Integration register
A workflow is not the same as a certified connector.
The following distinguishes the integration approach from the evidence needed to confirm readiness in your environment.
| System | Approach | Validate before deployment |
|---|---|---|
| Spreadsheets & historical exports | File-based ingestion | Confirm schema, units, period coverage and validation rules with sample exports. |
| Historian & SCADA | Tag-mapping workflow | Confirm the source system, protocol, connector availability and read/write boundary. |
| Microsoft 365 | Identity integration described | Confirm tenant configuration, role provisioning and authentication requirements. |
| SAP / Oracle ERP | Structured outbound integration | Agree payloads, ownership, retry handling and reconciliation. A certified connector is not asserted here. |
| PostgreSQL / SQL Server / Oracle | Database deployment options | Confirm supported versions, licensing, backup ownership and the hosting responsibility matrix. |
Hosting responsibility
Choose the placement. Agree the ownership.
Shared service, dedicated instance and on-premises placement have different infrastructure responsibilities. Record these in the proposed operating model rather than assuming they are identical.
01
Backup & recovery
Request backup frequency, restore-test evidence, retention and agreed recovery objectives for the selected environment.
02
Security assurance
Request security testing, vulnerability management, encryption and incident handling evidence. No SOC 2 or ISO certification is claimed on this website.
03
AI data handling
Confirm model providers, data destinations, retention, training-use terms and permitted information before production data is submitted to an AI service.
04
Scale & support
Agree asset counts, historical data volumes, peak ingest rates, support hours, escalation routes and service expectations. Establish performance with a representative test.
Evidence before expansion
A pilot should answer the hard questions.
Use your own representative period and acceptance criteria to establish data quality, reconciliation, access behavior and operational readiness.
Request a demonstration
See your operations connected across the value chain.
We will scope the demonstration to the facilities you operate and the way you close today.