PI Specifications and Data Standards

Specify project information that is ready for structured forecasting, reporting and look-ahead planning.

PI Specifications help owners, contractors, EPCMs and project controls teams define the project information needed for a PI-compatible workflow. The goal is to make registers, progress data, resource expenditure records, cost-code structure and reporting assumptions easier to align before the project depends on them.

The current PI_SPEC pack is request-only / controlled-access while legal, commercial and publication review continues. A future public information pack can be published once release wording and disclaimers are locked.

Request PI Specifications information pack Discuss implementation support

Definition

What PI-compatible information means

PI-compatible information is project information that can be consistently interpreted by a structured Excel-based forecasting and reporting workflow. It is not just a file format. It is a practical data standard for how project registers, progress updates, cost codes, resource expenditure and look-ahead inputs are prepared and maintained.

The specification should make clear who owns the information, when it is updated, how it is validated and what minimum fields or assumptions are required before the information is used for forecasting or reporting.

Audience

Who this is for

PI Specifications are relevant for project teams that need project information to be usable across planning, project controls, engineering, construction, completions, commercial, cost and reporting functions.

Owners and asset operators
Contractors and subcontractors
EPCM teams
Project controls, planning, commercial, cost, engineering, construction, completions and QA teams

What the PI_SPEC pack supports

The current pack is structured around the information needed to make an Excel-based project-controls workflow repeatable and reviewable.

Core Data Requirements

Minimum information expectations for registers, type definitions, cost-code mapping, progress gates and workbook workflow inputs.

Enhanced Forecast Governance

Additional governance for Resource Expenditure, forecast reliance, validation, reporting controls and controlled project use where selected.

Workbook Standard

Register template and workbook-standard requirements, including approved-equivalent options for project-specific workbook structures.

RACI and Service Levels

Division of responsibilities, service-level assumptions and Pi Labs responsibility only where a written service scope exists.

Tenderer Compliance Matrix

A two-track compliance model that can distinguish core requirements from enhanced or service-specific requirements.

Contract-Type Disclosure

Controls for how data reliance and commercial disclosure requirements change between lump sum, schedule of rates, cost reimbursable, alliance, hybrid or project-specific models.

Core track

Core requirements

Core requirements establish the minimum data structure needed for a PI-compatible workflow. They focus on register identity, type/cost-code mapping, quantity and unit fields where applicable, progress gate structure, ownership and validation expectations.

Unique item, activity, tag, deliverable, work package or quantity identifier
Description, discipline, area, system, location or work-breakdown grouping
Cost-code or reporting-code mapping
Quantity and unit of measure where applicable
Progress-gate structure, owner and update basis

Enhanced track

Enhanced governance requirements

Enhanced requirements can apply where the project wants stronger forecast governance, Resource Expenditure use, commercial disclosure, validation controls, formal reporting cycles or a managed PI engagement.

Resource Expenditure and cost-code forecast records
BudgetHrsPerUnit or equivalent productivity assumptions where relevant
Forecast basis, validation status and exception handling
Contract-type disclosure and data-reliance controls
RACI and service-level alignment for scoped support

Contract model adaptation

Not all commercial models need the same disclosures

PI Specifications can be adapted for different procurement and contract models, including lump sum, schedule of rates, cost reimbursable / cost-plus, alliance, hybrid or project-specific arrangements.

Public website wording should not assume that one model fits every project. The contract model affects what information is required, who owns it, what can be disclosed, and how forecast reliance is controlled.

Controlled access now

Request-only pack, public information path later

Pi Labs can provide the current PI Specifications pack for review on request. It is intended to support structured Excel-based project-controls workflows and must be adapted for the relevant project, procurement model, contract terms, data availability and owner/legal/commercial review requirements before use.

The planned future path is a separate public information-only pack with a cover sheet, document map, approved disclaimers, version history and selected documents.

Registers that feed the workflow

A PI-compatible workflow depends on the quality of the registers that feed it. Register originators may include design, engineering, procurement, planning, construction, completions, QA, equipment schedule owners, cable schedule owners, deliverable schedule owners and owners of bulk or untagged quantity registers.

Tagged equipment, cable, instrument, deliverable, procurement, construction work-package, completions, QA, inspection, bulk quantity and untagged work registers

Progress and expenditure owners

Progress data has owners too

Progress and resource expenditure data usually comes from a different group of people than the original registers. The specification should identify who supplies progress, who validates progress gates, who owns cost-code mapping and who confirms resource expenditure.

Project controls
Site engineers and supervisors
Planners
Commercial and cost teams
Discipline leads and delivery managers

Tender and contract review

Tender and contractual wording requires review

PI specification material can help structure project information requirements, but tender, contract, procurement, liability, warranty, forecast-reliance, insurance, privacy, security and compliance wording must be reviewed and approved by the project owner and relevant advisers before use.

Pi Labs can provide candidate technical wording and project-controls workflow guidance, but the project owner remains responsible for deciding whether and how those requirements are used in tenders, contracts or procurement documents.

Contact

Request PI Specifications information pack

Email Ryan McCall at Pi Labs with a short description of the project, the registers involved, who owns progress data, how resource expenditure is recorded and whether the requirement is for an internal standard, a managed pilot or a tender/specification discussion.

ryan.mccall@pilabs.app