Support / Documentation / GridIntegrate

GridIntegrate

GridIntegrate is the integration, synchronization, normalization, and lifecycle record layer for the GridSite ecosystem. It connects our platform to external systems, ingests and maps data from multiple sources, preserves provenance and historical context, and establishes a durable single source of truth across projects, facilities, assets, vendors, incidents, maintenance records, and operational systems.

What It Is

GridIntegrate is the top-level integration application for the ecosystem. It is where connector management, external system mapping, data ingestion, transformation, reconciliation, synchronization, and archival live as first-class capabilities. Rather than burying connectors inside individual modules, GridIntegrate provides a central integration plane for the entire platform.

This application exists because many customers will continue using third-party systems for some parts of their business, especially during the early years of adoption. They may use one system for construction project management, another for ticketing, another for access control, another for cameras, another for BMS or DCIM, and still another for procurement, utility, or asset records. GridIntegrate allows our platform to ingest, correlate, normalize, preserve, and operationalize that information across the full lifecycle of a facility and organization.

GridIntegrate should become the canonical place where we answer questions like: What systems are connected? Where did this record come from? What source system is authoritative for this field? When was this object last synchronized? What data has been archived historically? What external events are available to drive workflows, alerts, dispatching, digital twin overlays, and compliance evidence?

Why It Matters

Without a robust integration layer, every application becomes a silo. GridIntegrate prevents that by creating a shared object model and shared integration backbone for all ecosystem apps. It makes the platform more adoptable because customers do not need to replace every existing system on day one. It makes the platform more valuable because once data is normalized and tied together, it can be reused everywhere else: in GridTwin, GridPolicy, GridCommand, GridPass, ComputeComplete, reporting, auditing, and future analytics.

It also creates strategic defensibility. Even when a customer continues to use external products, the GridSite ecosystem becomes the place where those products are unified, cross-referenced, archived, and transformed into actionable operational intelligence.

Features

Each feature has its own documentation page. Click through for details.

Example Workflows

  • Import project milestones from a third-party platform and tie them to facilities, assets, vendors, and commissioning records.
  • Pull access control events, correlate them with patrol actions and incidents, and trigger policy rules on abnormal conditions.
  • Aggregate maintenance records from an external CMMS and attach them to long-term lifecycle histories visible in GridTwin.
  • Ingest utility and metering data for dashboards, alerts, reporting, and asset performance analysis.
  • Import vendor, procurement, and delivery records tied to project plans and operations readiness workflows.

Intended Users

  • Platform administrators
  • Integration engineers
  • Operations leaders
  • Site administrators
  • Project and commissioning teams
  • Compliance and audit stakeholders

Ecosystem Integration

GridIntegrate is foundational. GridTwin consumes clean, normalized data for accurate digital twin views. GridPolicy uses integrated events to drive rules and automations. GridCommand uses integrated context to correlate incidents. GridPass benefits from synchronized identities and access events. ComputeComplete benefits from project data imports and lifecycle continuity. GridStation and GridComms benefit from location context and device associations.