Chapter 2 recap

Setting requirements

The key takeaways from this chapter’s 3 lessons.

From organisational needs to exchange requirements

Organisational information requirements (OIR) say what the organisation needs to know to run its business and its assets.
Asset (AIR) and project (PIR) information requirements turn those needs into what each asset and each project must provide.
Exchange information requirements (EIR) are the detailed, per-appointment version: what to deliver, in what form and when.
A requirement is ready when the supplier could price and produce it from the text alone.

The information standard says how information is structured: naming, classification, codes, units, coordinates, level of information need.
The production methods and procedures say how it is made and moved: capture, checks, reviews, approvals, CDE workflow.
Reference information and shared resources are what every team starts from: surveys, templates, libraries, existing asset data.
All three are set once per project by the appointing party, issued with every tender, and kept consistent with the organisation’s own standards.

The information protocol sets out each party’s rights and obligations for managing and producing information in that appointment.
The appointing party writes it for the project and includes it in every tender and every appointment; each appointing party down the chain passes it on.
Its front page lists the documents that apply to this appointment (EIR, BEP, MIDP, standard…) and marks the others not applicable.
Without it, an EIR or a BEP may have no contractual force at all. It is not legal advice: involve the people who draft the contracts.