Submitted by Sarah Robertson on September 10, 2013 - 8:00am
Last week we discussed Trend 2, Preparing for the Cloud, and that while the Cloud is changing many data-sharing and IT-related processes and systems, most pipeline planning and ROW teams are yet to feel the impact.
This week we’re walking through the 3rd and Final Trend – Design a Data Architecture to Ease Future Operations. Using the Cloud or any other system, teams should create a ROW data architecture that reflects an understanding of how documents will be used throughout a pipeline’s lifetime. And the very best time to think about how operational teams will later use ROW data is at the point of the initial ROW data collection.
A large part of the ROW data management process, of course, is centered on identifying and securing rights of way during the initial pipeline construction phase. As a result, many organizations focus their handling of survey, easement, and contract documents in a one-off project-management-like manner.
At a macro-level, teams identify routes and work through all of the documentation to secure the rights of way. At a micro-level, securing each individual ROW is also a project, often with stacks of documents accumulating in traveling packs to include surveys, ownership documents, offers, and contracts. In both cases, there’s often a “line-them-up-and-knock-them-down” project management approach which is important to keeping projects on track.
A challenge that many operational teams encounter after commissioning, however, is poorly organized ROW data that can be difficult to access and manage during later operations. Changes in rights of ways happen during construction, as routes are modified, and after construction, as ownership of land changes hands. ROW data is used to track owners, ownership changes, payments, and other material events. Teams also use ROW data as part of normal operations outside of payments, for example, in communicating with land owners around routine pipeline maintenance, vegetation abatement and management, and incident response. Well-organized data is critical to facilitate inspection documentation and the ability, for example, to quickly respond to inquiries from regulators and land owners, and to document compliance.
The best time to think about how operational teams will later use ROW data is at the point of the initial ROW data collection. Teams should create a ROW data architecture that reflects an understanding of how documents will be used throughout a pipeline’s lifetime. The right data taxonomy should be created and document tagging implemented to reflect payments, ownership changes, incidents, and compliance requirements. Teams should consider the following:
-
How should survey data be tracked and associated projects, owners, GIS data, and payment records?
-
As owners change is it easy to update and track records?
-
As changes arise during construction and rights of way adjusted, how are engineering documents updated and tracked? How are land surveys updated and tracked?
-
Do the CAD, GIS, and survey records stored by the organization actually reflect the ROW and pipeline as-it-was built?
-
Will future maintenance teams, regulators, or new owners be surprised when they arrive later?
Thinking about these issues early provides downstream operational teams with the chance to receive a logical, structured, and accessible set of ROW documents, instead of a disorganized collection of scanned files turned over to them after commissioning.
Final Thoughts on the series:
Many pipeline planning teams have already encountered some of these ROW data management trends, others will encounter these trends as they upgrade existing systems, work on new projects with partners that manage ROW data differently, or gradually as more devices begin appearing in the field.
Either way, it's important for teams to understand these trends and to begin thinking about how Changes in Devices, the Cloud, and the use of ROW data can create opportunities to streamline and improve operations rather than disrupt them.
I hope that you’ve found this series useful. While every ROW planning team and workflow is different, these best practices and considerations will help you find the right solution for you and your team. This series was based on an eBook, download it for free here: The Top 3 Pipeline Right-of-Way Data Management Trends eBook
Please also reach out if you have any comments, questions, or would like to get some feedback on your data management processes and workflows. Adapx has a team of workflow specialists that are all about finding the right fit. We’ve fielded thousands of deployment questions and requests, some are perfect fits for the digital pen and tablet workflows that we support, others we have directed toward different vendor solutions based on their workflow needs. Email [email protected] or visit www.adapx.com