Configuration & Scalability

Readiness behaviour is expressed as configuration, not project-specific code paths. Every rule below is evaluated by the readiness core; the interface only renders the outcome.

Configuration scopes

Configuration dimensions available to a project without code change.

Project

Readiness gate set, snapshot validity policy, shift calendar

Site

Local legal requirement pack, emergency scenarios, muster points

Discipline

Default applicability rules, required activity roles

Work type

Preventive package template, checklist set

Risk category

Mandatory critical control taxonomy, verification frequency

Document type

Authority source, freshness class, pinning rule

Permit type

Approval route, validity window, delegation eligibility

Readiness gate

Owner role, non-compensable flag, evaluation inputs

Role

Attribute-based authority matrix, field visibility

Approval route

Primary authority, delegation scope, escalation owner

Critical control taxonomy

Fatal risk mapping, verification evidence type

Scalability envelope

Projects

Multi-project with isolated configuration sets

Areas

Unlimited area / facility / system hierarchy

Contractors

Multi-contractor with federated competency sources

Permit configurations

Per-site permit types and approval routes

Document taxonomies

Project-specific classes and freshness policies

Legal requirements

Local regulatory packs loaded per site

Enterprise combinations

Adapters enabled per project; absent sources degrade explicitly

This product is not

Stated explicitly so the capability boundary is not misread.

ERPDocument management replacementP6 replacementQ4 replacementForwood replacementWorkforce masterHealth-record systemAutonomous work authorization systemLegal interpretation engine

Sample readiness rule configuration

Illustrative rule set for Area 200, showing the shape of configuration.

Gate	Scope	Evaluation input	Owner role	Non-compensable
Engineering Readiness	Project · Discipline	Engineering release status from document authority	Engineering Manager	COMPENSABLE IN GROUP
Client Release Readiness	Contract	Client release object / zone access grant	Client Interface Manager	NON-COMPENSABLE
G1 Legal & Regulatory	Site	Local regulatory pack + permit validity	ES&H Manager	NON-COMPENSABLE
G2 Risk & Critical Control	Risk category	Critical control availability, verification, effectiveness	ES&H Supervisor	NON-COMPENSABLE
G3 Operational & Competency	Discipline · Work type	Activity role competency validity	General Foreman	NON-COMPENSABLE
G4 Emergency Response	Site · Scenario	Capability availability, not plan existence	Emergency Response Coordinator	NON-COMPENSABLE
G5 Documentary & Evidence	Document type	Pinned snapshot freshness + evidence integrity	Document Control	NON-COMPENSABLE

Data governance attributes

Only the minimum necessary field is exposed to each persona.

BusinessOwner

Accountable business function

DataOwner

Owns the data definition

DataSteward

Maintains quality and reconciliation

SourceSystem

Authoritative platform

Classification

Internal / Confidential / Restricted

Retention

Retention class and duration

Sensitivity

Personal / operational / commercial

AuthoritativeState

Authoritative or operational snapshot

ReplicationRule

What may be cached and where

ReconciliationRule

How divergence is resolved and by whom

No medical, diagnostic or personal information beyond the minimum operational necessity is held or displayed. Personnel appear as references and activity roles, never as clinical records.