ABSTRACT DEADLINE: March 15, 2018
· Abstracts should be no more than 2,000 characters.
· In submitting an abstract you are indicating your availability and willingness to attend and present at the 5th annual Pipeline Week.
· Your abstract should be in English, completely original, and address issues as outlined in the conference focus areas.
· Abstracts should summarize a noncommercial, technical presentation about solutions, approaches, areas of technology, technology application, theory, case studies on application, evaluation, results, management processes and application, impact on value, and/or other management and technical benefits and costs.
· The primary contact will be notified by email as to whether the abstract has been selected for inclusion in the conference program by the end of April 2018.
· If your abstract is selected, you must comply with all the deadlines.
· A PowerPoint presentation will be required to be given at the conference if your abstract is selected.
· Thirty minutes will be allocated to make a presentation (includes question/answer discussion).
· Full instructions on the preparation of presentations will be sent to the authors of selected abstracts.
· Speakers are responsible for their own travel and related expenses, but receive a significantly reduced conference registration rate. Co-authors register at the prevailing rate at the time of registration.
· Please ensure that the speaker details provided when submitting an abstract are correct, as these will be used for pre-event marketing purposes.
TECHNICAL FOCUS AREAS
Asset Management, Mobility, Analytical and Business Intelligence, Regulatory Compliance, Operational Awareness, Integration/Interoperability, Project Planning and Records Management, Construction Standards/Data Standards, Existing and Emerging Standards, Pipeline Integrity/Integrity Management, Emerging Technologies/Trends, Site and Facility Management, Social License to Operate, PODS
When submitting an abstract, you will be asked to select a topic for which you wish to submit.
Your abstract should address at least one of the following areas:
1. Asset Management: Describe your organization’s solutions relating to maintaining a verifiable, traceable, and complete record of your assets. Lessons learned from MAOP validation are of particular interest.
2. Mobility: How is your organization collecting and distributing data to your field operations? Has the technology caught up with your needs?
3. Analytics and Business Intelligence: With the information your company has available, what new analytical processes or report have you implemented to improve operations, pipeline safety or the bottom line? What types of data do you still need and cannot get at that could reap benefits to your company? Tell attendees how these process and reporting implementations have impacted decision making within your organization.
4. Operational Awareness: Describe how you are disseminating information to everyone within your organization. Provide examples of solutions that feature intuitive, easy to use interfaces for those not familiar with traditional GIS and can be made available on multiple device platforms (web, iOS, Android, etc.).
5. Integration/Interoperability: Presentations should focus on multiple systems and process integrations. Examine and explain the benefits of these strategies in supporting operational awareness, compliance, and timeliness of decision making across organizations.
6. Project Planning and Records Management: What are people doing in the planning and execution phases of pipeline construction to ensure better data records are captured and input from the beginning? How are operators and service providers handing data archival and historical reporting? How are they getting contractors and vendors to participate?
7. Construction Standards/Data Standards: What “should be/needs to be” digitally captured when we put assets in the ground, including offshore?
8. Convergence of information technology and operational technology systems: Presentations should focus on the transformational opportunities that convergence affords pipelines that take advantage of it.
9. Existing and Emerging Standards: Database standards, such as PODS, UPDM etc. operational standards, regulatory standards, environmental standards, all as they apply to using geospatial in the pipeline domain. Additionally, consider approaches to data governance, migrating data when assets are merged or acquired, use of PODS data model and upgrading to PODS versions and PODS Next Gen.
10. Pipeline Integrity/Integrity Management (from a GIS perspective): Presentations should demonstrate how advances in GIS and those impacting integrity management activities (such as in-line inspection tools) are impacting one another and how the impacts are shaping the management and interoperability of those data. Similarly, what synergies are emerging between GIS, SCADA, and IM programs within individual operator approaches and how can these be better leveraged as industry best practices?
11. Pipeline Integrity/Integrity Management (non-GIS): Topics ranging from pigging and in-line inspection to cathodic protection and direct assessment are welcome. Other topics can include pipeline design compliance, pipeline safety management, implementation of integrity management processes for distribution and transmission pipeline systems (DIMP/TIMP), and emergency planning and preparedness.
12. Emerging Technologies/Trends: Presentations in this session would cover advances in hardware, software, and techniques and the trends both driving these advances and stemming from them. Topics should be set in an operational setting, (not simply approached as a PowerPoint version of your new device’s one-sheet) and could include real-time analytics capabilities, UAV/drone usage, or unique process changes as well as demonstrations of how existing technologies have been implemented in a new manner to improve operational excellence.
13. Site and Facility Management: A large part of any robust integrity plan is effective day-to-day management of infrastructural assets. Whether you’ve reinvented the wheel or simply added another spoke to it, you colleagues will be interested to hear you share your experiences.
14: Social License to Operate: It’s no longer enough to have your pipeline properly engineered, routed, permitted, and financed. The pipeline industry and its projects are increasingly challenged by outside groups. Anticipating the concerns of these groups and attempting to address them well in advance is now an important part of planning a new pipeline, operating an existing one, and retiring old systems.
15. PODS: Outline and discuss PODS or other Pipeline database implementations, versions can be 4-6, PODS Spatial, PODS lite, NO PODS as all, UPDM, or any combination. Discuss why you did or did not decide to use PODS. We are interested in hearing the benefits to the organization as well as the limitations of various Pipeline database models.
For questions please contact the Conference Manager: