03.1
Information transfer against stated requirements
Was what was delivered tested against what was asked for, by someone who will have to use it?
What goes wrong without it
Document acceptance and information transfer are different events, and only the first has a procedure attached. A pack can be complete against its register, accepted by the party who commissioned it, and still not answer the questions operations will ask in its first year. The cost of the difference lands after everyone responsible has left, which is why it is not felt as a cost by anybody with authority to prevent it.
What to examine
- Compare the delivered information against the asset information requirements, not against the document register.
- Have a competent person who was not involved attempt to answer three operating questions using only what was supplied. This test is cheap and almost nobody runs it.
- Check whether the accepting signature belongs to the receiving organisation or to the delivering one.
- Sample as-built records against physical reality in a small number of locations. Late substitutions and field modifications are the usual gap.
Required by
- ISO 19650-3, information management during the operational phase of assets.
- FIDIC Conditions of Contract, 2017 edition, Sub-Clause 10.1, which makes supply of as-built records and operation and maintenance manuals an express requirement of taking over.
- ISO 55001:2024, Clause 7.6, data and information.
Read the sources
- ISO 55001:2024, asset management system requirements2024 edition; read 2026-09-26.ISO’s product page: the publication details and ISO’s own summary of the standard, not the requirement text. The contents, foreword and introduction cited in this publication are taken from the standard’s preview pages hosted on the ANSI webstore, not from this page.
In the asset lifecycle method
The steps of the two methods that this domain examines.