The Prepossession Meeting is held to:
• Brief and induct Protection Officers and Supervisors on the specifics of each configuration/closedown possession
• Disseminate information on safe working arrangements, including live track interfaces, possession boundaries, and electrical isolation requirements, combined worksite and congested worksites, if applicable
• Brief attendees on lessons learnt from previous possessions and to inform attendees of new possession processes and procedures
The Project Owner must ensure that all final worksite staff information has been included in PACT at least 7 days prior to the Prepossession Meeting date.
The Prepossession Meeting is held not less than 3 days prior to the possession. A set of Prepossession Briefing Notes (AMD-ASD-TEM-001) are issued electronically prior to the meeting.
These Notes include necessary information such as PPO Office contact details, Track Diagrams showing possession configuration protection arrangements, Safe Notices, STNs, Lessons Learnt, Possession Notices and the approved Possession Works Program (Scope of Work) for the nominated Configuration / Closedown Possession.
Failure to have adequate representation at this meeting may lead to the cancellation of the Job and notification of the impact on the possession to their DED.
Jobs not adequately represented at the meeting will be cancelled unless there is an agreement with the NAM prior to the meeting.
Worksites will not be authorised to start work unless it is included in the Possession Works Program presented at the Prepossession Meeting.
No changes to the Possession Works Program or the possession configuration will be made at the Prepossession Meeting unless identified as “Urgent” work.
Urgent works are works required for the purpose of addressing any infrastructure issues considered by the Engineering and Maintenance Directorate to have the potential to deteriorate below base operating standards within the normally agreed target timeframes.
Urgent work will only be accepted into the possession after the conclusion of the Prepossession Meeting subject to all approvals described in Late Scope Request Procedure.
Refer: AS&DC SharePoint – ASDC Pre-Possession Meeting Guide (AMD-ASD-GUI-010)
Network Access Manual Volume 2
2 General Requirements
2.1 Master Schedule
2.2 Baseline Master Schedule
2.3 High-Level Scope and Resource Plan
2.4 Monthly Resource Confirmation meeting
2.5 Possession Planning Sequence
2.6 Program Coordination Unit (PCU)
2.7 Primavera (P6)
2.8 Possessions setup in PACT
2.9 Possession Constraints Register
2.10 Track Diagram
2.11 Possession bids in TRAK 2
2.12 Scope of work entered in PACT
2.13 Possession Start times
2.14 Late Scope Approval
2.15 Late/Change of Scope Submissions
2.16 Who Must Attend the Meetings
3 Works Coordination Meeting
3.1 Critical Projects for possession on time handback
3.2 Electrical Controls
3.3 Chronological Train List
3.4 Coordinated Worksites
3.5 Congested Worksites
3.6 Interface Issues
4 Finalisation Meeting
4.1 Final Chronological Train List
4.2 Coordinated Worksite Coordination Plans
4.3 Congested Worksites and Access Restrictions Plans
4.4 Records of Meetings
4.5 Possession Scope changes
5 Neighbour Notifications
5.1 Interface Issues
5.2 Late/Change of Scope Approval
6 Prepossession Meeting
6.1 Details Presented at Prepossession Meeting
6.2 Prepossession Meeting Notes Include Specific Forms
6.3 Worksite Incident Reporting
6.4 Work Train and Track Machine movements
6.5 Records of Meetings
7 Delivering the Possession
7.1 PPO Induction
7.2 Track Vehicle movements
7.3 Taking the Local Possession Authority
7.4 Possession Protection
7.5 Cascading the Prepossession Meeting Requirements
7.6 Work Commences
7.7 Possession Manager – Monitoring Critical Work
7.8 Possession Handback
7.9 Possession Reporting
Our Partners
- FR2 Infrastructure – Constructability advise and project and planning controls
- Staging Diagrams – Staging diagrams for possession planning
Possession Planning – Current Possession Calendars
✨ Support Our Mission ✨
Help us continue building tools that simplify complexity!
Every contribution fuels new features and improvements
Thank you for being part of our journey! 🚀
