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.

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.

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.

Security & Deployment Walkthrough

SaaS or On-Premises: Fully Secure & Auditable

Watch how HCF360 enforces database-level tenant separation, air-gapped on-premises installations, and Microsoft 365 identity integration.

LIVE DEMO · SaaS or On-Premises Enterprise Security & Audit
Azure AD & Audit Trail3:48
SaaS or On-Premises Enterprise Security & Audit
Watch live demonstration (3:48)

Enterprise & Security

What is demonstrated in this recording

Database-level workspace tenant separation, Microsoft 365 / Azure AD integration, role-based review/release gates, and air-gapped on-premises options.

  • Dedicated database tenant separation or air-gapped on-premises deployment
  • Microsoft 365 SSO with segregation of accounting and operational duties
  • Immutable change-logging with complete field, method, and approval history
  • 3–7 day accelerated deployment target via AI-assisted legacy schema ingestion
Video ID: -mcPY7Mai2oWatch on YouTube

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.

Integration approaches and required evaluation evidence
SystemApproachValidate before deployment
Spreadsheets & historical exportsFile-based ingestionConfirm schema, units, period coverage and validation rules with sample exports.
Historian & SCADATag-mapping workflowConfirm the source system, protocol, connector availability and read/write boundary.
Microsoft 365Identity integration describedConfirm tenant configuration, role provisioning and authentication requirements.
SAP / Oracle ERPStructured outbound integrationAgree payloads, ownership, retry handling and reconciliation. A certified connector is not asserted here.
PostgreSQL / SQL Server / OracleDatabase deployment optionsConfirm 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.

Scope the evaluation

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.

Request a demonstration