Stage 0
Engagement
Engagement Header
OwnerArcestra Commercial
0.1
Engagement Identification
The governing charter this onboarding maps to.
Gates which permissions and actuation rights exist across the platform. Enforced by the Guardrail Engine.
Stage 1
Business & Financial
The Economic Reality
OwnerArcestra Commercial ↔ Channel Partner
StandardsISO 50006ISO 17741GHG ProtocolIPMVPGreen Button
1.1
Client & Corporate Structure
Add a row per facility to map the multi-site portfolio.
1.2
Utility Providers & Contracts
Add one per resource (electricity, water, gas, district energy, fuel, steam).
1.3
Financial Baseline · Utility Bills (Critical)
CriticalMinimum 12 months per resource required before baseline lock.
Metered telemetry must be cross-checked against billed consumption before baseline lock. A discrepancy greater than plus or minus 2 percent triggers a data-quality investigation.
1.4
Economic Model & Business KPIs
e.g., trailing 12 months, or a normalized reference year.
1.5
Business Objectives & Outcomes
Link each agreed business outcome to the KPI that evaluates it.
Rank objectives and define success per objective.
Handoff gateStage 1 is ready when the Pilot Charter, the Economic Model, and the 12-month utility bill set are signed off.
Stage 2
Facility & Digital Twin
The Physical Reality
OwnerImplementer / Field Integrator (with Arcestra L3 guidance)
StandardsProject HaystackBrickIFC / BIMASHRAE TC 9.9The Green GridISO/IEC 30134EN 50600
2.1
Facility Identification & Geolocation
Critical for cooling-efficiency interpretation.
2.2
Physical & Logical Topology (Digital Twin Hierarchy)
Org → Portfolio → Site → Building → Data Center / Zone → System → Equipment → Sensor / Point. This is the digital twin skeleton.
2.3
Electrical Topology (Single-Line Relationships)
Precisely where IT energy is measured (PDU output, rack input). This is the PUE denominator and must be explicitly agreed.
2.4
Mechanical / Cooling Topology
Hot/cold aisle, containment type.
Flow, temperature, quality sensors.
2.5
Asset Condition & Lifecycle
Add one per critical asset or system. Condition is contextual, not a performance conclusion without telemetry.
2.6
WAGES Utility Sub-Metering Inventory
Water, Air, Gas, Electricity, Steam. Add one per meter.
e.g., Total facility kWh, cooling kWh, IT kWh, water m³
CT ratio, meter class
2.7
BMS / DCIM Integration & Protocol Discovery
e.g., Niagara, Metasys, EcoStruxure, PI, Nlyte.
2.8
External & Environmental Context
Handoff gateStage 2 is ready when the digital twin hierarchy is populated, the IT-load boundary is signed off, and the WAGES meter inventory is complete.
Stage 3
Governance & Interaction
The Operational Reality
OwnerArcestra + Channel Partner + Implementer (joint, with client)
StandardsITIL 4IEC 62443ISO 27001PMBOKRACIIPMVP
3.1
RACI Matrix (Agnostic Roles)
Reference RACI matrix
| Activity | Arcestra (Vendor) | Channel Partner | Implementer | Client |
|---|---|---|---|---|
| Economic model & KPIs | A/R | C | I | C |
| Client business data collection | C | A/R | I | C |
| Facility / digital-twin capture | C | C | A/R | C |
| BMS integration & connectors | A | C | R | C |
| Data flow agreement & security sign-off | R | C | C | A |
| Baseline definition & Day-30 lock | A/R | I | I | C |
| L1 / L2 support | I | A/R | R | · |
| L3 / backline support | A/R | I | I | · |
R = Responsible, A = Accountable, C = Consulted, I = Informed
3.2
Interaction & Handoff Rules
3.3
Data Flow Agreement & Data Sovereignty
Actuation boundaries and data flow governed by the Guardrail Engine and client-approved policies.
3.4
Baseline Governance (IPMVP-Aligned)
3.5
Support & Escalation Model (ITIL-Aligned)
3.6
Operational Context & Constraints
Handoff gateStage 3 is ready when the RACI is signed, the Data Flow Agreement is approved, and the security sign-off is complete.
Stage 4
Identity, Access & Security
The Access Reality
OwnerClient Tenant Admin + Partner + Arcestra Administration (distributed)
StandardsOIDC + MFAIEC 62443ISO 27001RBAC
4.1
Reference: Roles, Scope & Permissions
4.1 Six principal role families
| # | Role Family | Who They Are | Primary Need |
|---|---|---|---|
| 1 | End User (Client Business) | Client executives, ESG leads, finance, leadership | Outcomes, KPIs, savings, ESG |
| 2 | Operator (Client Operations) | Facilities, data center, site operations teams | Operational detail, alerts, recommendations, execution status |
| 3 | Partner (Master Channel) | Master commercial partner reselling the platform | Client-book visibility, sub-partner management, commercial metrics |
| 4 | Sub-Partner (Reseller / Integrator) | Downstream partner under the master partner | Visibility only over assigned sites |
| 5 | Account Manager (Arcestra) | Arcestra's named account owner | Client health, usage, support, relationship |
| 6 | Arcestra Administration | Arcestra internal platform operators | Full platform administration, billing, compliance, security |
4.2 Scope hierarchy (one level granted, inherits below, nothing above)
| Scope | Definition | Typical Holder |
|---|---|---|
| L0 · Platform | All tenants, all facilities, internal only | Arcestra Administration |
| L1 · Account Group | A set of assigned client accounts | Account Manager |
| L2 · Partner Pool | All clients & sites under one master partner | Partner |
| L3 · Sub-Partner | Only sites assigned by the master partner | Sub-Partner |
| L4 · Tenant / Company | One entire client organization | Client Tenant Admin |
| L5 · Portfolio | A subset of the client's sites | End User (leadership), Operator lead |
| L6 · Site / Facility | One building or data center | Site Operator, Site End User |
| L7 · System | One subsystem (cooling loop, power chain) | Specialist Operator |
| L8 · Point / Equipment | Individual sensor or asset | Diagnostics / maintenance |
Isolation rule: a request above or outside granted scope returns a hard 403 at the API/data layer, never a hidden UI element.
4.3 Permission model
| Permission | Meaning | Autonomy-governed? |
|---|---|---|
| VIEW | Read dashboards, telemetry, reports, KPIs | Yes |
| ANALYZE | Drill-down, custom queries, export data / reports | Yes |
| ACKNOWLEDGE | Acknowledge alerts, add notes, route to a human | Yes |
| APPROVE | Approve / reject an AI recommendation before execution | Required for Guided; pre-approved in Autonomous; N/A in Advisory |
| CONFIGURE | Modify thresholds, guardrails, policies, setpoints | Per agreed Autonomy level |
| ADMINISTER | Manage users, roles, billing, tenants, connectors | No at client level; yes within Arcestra |
4.6.3
Tenant-Level Capture (per client organization)
Minimum one. Owns user provisioning for the client's End Users and Operators.
Affects what admin roles can access remotely.
Gates which permissions and execution rights are available.
4.5
Licensing & Seat Reconciliation
Included seats per site: 5 total · 3 Viewer + 1 Analyst + 1 Admin. Additional seats are billable per tier. Any roster exceeding included seats triggers a commercial confirmation before accounts are activated.
4.6
User Roster · Onboarding Data Collection Template
Capture identity (4.6.1) and role-specific detail (4.6.2) for every user. MFA is mandatory; the platform refuses to start without it.
End User: reporting focus, dashboards, export, visibility scope. Operator: assigned systems, shift model, alert channels, approval authority, escalation. Tenant Admin: provisioning authority, billing visibility, cost-center ownership. Sub-Partner: assigning master partner, assigned sites, support tier. Partner: client book, sub-partner roster, margin visibility, L1/L2 ownership. Account Manager: assigned accounts, escalation rights, CRM linkage. Arcestra Admin: internal role level, break-glass rights, audit duty.
4.9
Access Layer Readiness Gate
Handoff gateStage 4 is ready when the Tenant Admin is enrolled (SSO+MFA), the roster is provisioned (role / scope / seat), RBAC is enforced, and the provisioning audit trail is active. Stage 4 is a HARD GATE: telemetry ingestion cannot begin until it is green.
Gate
Cross-Stage Readiness & Export
The Unified Readiness Gate
R
Readiness Gate
Stages 1 to 3 may run in parallel. Stage 4 is a hard gate: telemetry ingestion cannot begin until the roster is provisioned and RBAC is enforced, because every reading, approval, and configuration action from Day 1 must be attributable to a scoped, authenticated identity in the tamper-evident audit ledger.
Overall onboarding status
NOT READY
S
Submit to Arcestra
Send your completed intake to the Arcestra team. They are notified the moment you submit and will follow up to confirm next steps. You can still download or print a copy below for your records.
E
Export the Onboarding Record
Progress autosaves to this browser. Export the full record to hand off, or print a clean summary for the onboarding pack.