Advisor Project Handover, Management Requirements and Asset Information

You will work in a department responsible for provincial infrastructure, including roads, waterways, bridges, and locks. This department realizes infrastructure projects, often within UAV-gc contracts, where a large amount of technical, administrative, and management information is built up. The transfer of these objects and information to the management organization is currently not always uniform, leading to differences in expectations and acceptance.

The goal is to develop a clear working method for collaboration between the project and management organizations throughout the entire project lifecycle.

What you will do.

• Bring together existing building blocks (documents, working methods, experiences, and initiatives) in the field of asset information, client requirements, and project handover.
• Develop a uniform, practically applicable, and organization-wide system for requirements management, project handover, and asset information.
• Elaborate management requirements for application within both system-oriented contracts and RAW specifications, ensuring that management interests, asset information, and handover requirements are secured throughout the project lifecycle.
• Ensure connection with the management systems used within the organization and relevant information standards.
• Clearly establish the information needs, responsibilities, review moments, stop and attendance points, and acceptance criteria of the management organization, and embed them in the project processes.

Activities.

• Analysis of the existing situation, including inventory of available documents such as client requirement specifications, standards, and manuals, working methods, and initiatives, and a description of the main differences, overlaps, and improvement opportunities.
• Development of a uniform framework for management requirements and asset information, specifying which requirements the management organization sets for assets, asset information, documentation, and data to be supplied, how these requirements are processed in both system-oriented contracts and RAW specifications, what information is needed for recording and management in the relevant management systems, and the relationship with relevant standards and information models including IMBOR, NEN 2767, and the object structures and decompositions used within the organization.
• Elaboration for application within projects, including a proposal for principles regarding the structure of demand specifications, management requirements, and supporting annexes for projects.
• A process framework with process requirements for collaboration between project and management, defining per project phase, type of change, and decision moment when management is involved, when review moments and stop and attendance points are required, and when management involvement is not necessary.
• An acceptance framework for handover to management, including review moments, quality criteria, acceptance conditions, requirements for asset information, requirements for processing in management systems, and how deviations are handled.
• A standard handover file with a corresponding checklist, clearly describing which documents, data, and approvals are minimally required for handover to management.
• An implementation and embedding advice, aimed at the introduction and sustainable application of the developed working method within the department.