PIPELINE PROJECT APPROACH
PSE considers the generation of the Basis of Design Document (BOD) and its ongoing maintenance, critical to the execution of a successful pipeline project.
Upon receipt of a pipeline project Request for Proposal (RFP), PSE begins to assemble a BOD that becomes the repository for all tabular information, both those that are found in the RFP and those that are gleaned from subsequent meetings. By default, the BOD also records client decisions such as equipment preferences, control scheme and leak detection approaches, etc. The BOD is considered an “evergreen” document, in that it is continually updated with new information throughout the course of the project.
A few examples of items covered in the BOD would include;
- Collaboration meeting schedule for early extraction of stakeholder and specialist input
- Chemical and physical nature of the fluid to be transported
- Delivery requirements – head, flow, and schedule
- Available suction head
- API gravities
- Product temperatures
- Pipeline jurisdiction – DOT, etc.
- Cleaning and inspection schedules and requirements (traps, etc.)
- Leak detection sensing and reporting requirements
- Cathodic protection approach
- ROW and alignment requirements
- Under-road borings and over-road support requirements
- Metering requirements
- Slug-catching requirements
- Pipeline system reporting requirements
- Safety and site access requirements for project personnel
- UNEV Project
- Natural Gas Pipeline