Information Manager (ISO 19650)

Finish all 8 lessons to download a certificate of completion.

1. Chapter 1. The job and the people

   0/2 done
   • 1.1 Information management is a job, not a job titleISO 19650 does not ask for an “information manager”. It asks every party to make sure a set of activities gets done, by named people, before the work starts.
   • 1.2 Parties, teams and appointmentsAppointing party, lead appointed party, appointed party; project team, delivery team, task team. Who is who depends on who appointed whom, and it can change mid-project.
   • Chapter recap

2. Chapter 2. Setting requirements

   0/3 done
   • 2.1 From organisational needs to exchange requirementsOIR, AIR, PIR, EIR. Four sets of requirements, each built on the one before, ending in sentences a supplier can price and deliver.
   • 2.2 The information standard, methods and shared resourcesBefore anyone is appointed, the client sets the project-wide rules every team will work to, and the files every team will start from.
   • 2.3 The information protocolRequirements, standards and plans only bind anyone when an appointment says so. The information protocol is the part of each appointment that does.
   • Chapter recap

3. Chapter 3. Tender and appointment

   0/3 done
   • 3.1 Capability and capacityBefore you promise a delivery plan, check that your team knows how to deliver it, has the hours to do it, and has the IT to do it with.
   • 3.2 The pre-appointment BEP and the tender responseA tender response proves the team understood the requirements and can deliver them. The BEP is one of four parts, and the one most often written from a template.
   • 3.3 The detailed responsibility matrixTwo kinds of matrix, two levels of detail. At appointment, “the architect does architecture” becomes “who produces which information, by which milestone, for which requirement”.
   • Chapter recap

4. Chapter 4. Planning and production

   Coming soon
   • 4.1 Federation strategy and breakdown structure Coming soonSplitting the project into models and containers that teams can own.
   • 4.2 Container metadata: status, revision and classification Coming soonThe attributes that say what a file is, how far it can be trusted and where it belongs.
   • 4.3 Review, authorisation and acceptance Coming soonThe three decisions between a team’s check and the client’s acceptance.
   • 4.4 Mobilisation Coming soonTesting people, IT and methods before the first deliverable is due.

5. Chapter 5. Beyond delivery

   Coming soon
   • 5.1 Security-minded information management Coming soonWhen a project needs ISO 19650-5, and what changes if it does.
   • 5.2 The operational phase Coming soonAsset information requirements and the asset information model under ISO 19650-3.
   • 5.3 Health and safety information through the project Coming soonKeeping safety information findable from design to demolition.
   • 5.4 Soft landings Coming soonPlanning handover and the first years of operation with the people who will run the asset.