|
|
Due to the complexity of implementing a Pipeline Integrity Management system, we have to understand how wide the net falls on the groups of specialists that an installation affects.
ATP can provide any of the following documentation to specific experts to help fully understand the bigger picture of implementing PiMS.
Whether it is a Director of Risk Management, Project Manager, IT Managers or Operations Managers, we can provide you with the appropriate supporting documentation to
help understand how a PiMSlider implementation will affect these roles.
|
PiMSlider Concepts |
PiMSlider Concepts document describes the content of the software package, providing detail of the main components, in terms of the information storage and retrieval system, the analytical sub-system and decision-making sub-system. Each of the modules of PiMSlider fits into one or more of these categories.
There is also a high-level explanation of the main concepts of the combined modules, such as utilising a single-uniform database, how to create complex queries and how all data of a pipeline is completely integrated for an organisations network.
|
|
|
An extremely comprehensive 36-page document covering a wide area of common questions about implementing PiMSlider®.
The first section, Common Functional Requirements, is divided into sub-sections, such as Risk Assessment, In-Line Inspection, Pipeline Surveys, Field Services & Repair,
Project Management and so on, and directly maps exactly what a customer may ask for onto the actual PiMSlider module that meets these requirements.
So, for example, if a customers requirement was to deliver a report of likely causes of pipeline corrosion and recommended mitigation measures, then PiMSlider®
Rehabilitation Expert and CM Expert are the modules that will deliver this report.
The second section provides answers to questions about system architecture, IT implementations, interfacing with external databases, particular features required in PiMSlider modules, and also covers subjects such as data alignment, integrity management and dynamic segmentation.
|
Frequently Asked Questions (FAQs) |
|
Functional Specifications |
The Functional Specification document provides the reader with a high-level summary of the main functionality of PiMSlider.
Each section describes a major area of functionality, and the main features and kind of data available as part of that function.
For example, data management, topology (basic GIS functionality), monitoring/analysis/modelling of a CP system, analysing pigrun data, defect assessment,
risk calculations and levels and direct assessment.
|
|
|
It is important not to underestimate the work required to integrate into an organisations infrastructure.
ATP has considerable experience developing specialist interfaces to local Document Management Systems (DMS),
Geographical Systems (GIS), Enterprise Resource Planning (ERP) systems and other external systems.
An ideal solution would be to provide an automated interface between an organisations data systems and PiMSlider.
Whilst this sounds a relatively simple concept, it still requires some effort to get the automation developed, tested and integrated fully.
All these IT requirements are normally under the jurisdiction of the IT Manager, and our software must conform to security standards each site,
most of which differ from one customer to another.
The final section describes how PiMSlider is constructed, and how data would need to be formatted in order to be valid for PiMSlider.
|
Information Technology Requirements |
|
Pipeline Questionnaire |
One of the first documents completed early on in the relationship, this is a high-level document that asks open questions about a potential customers pipeline network.
This questionnaire is provided to all prospective clients of ATP Limited, in order that ATP can further understand initial requirements, and guide the client to the first set of negotiations for implementing a PiMS solution.
The more information that the client can provide, the quicker ATP can provide appropriate quotations and estimated timescales for implementing such a solution.
|
|
|
This document comprehensively describes the major data requirements of the PiMSlider application software, covering all components of PiMSlider.
For each component part of PiMSlider, sub-sections describe the various items of data that that component requires to function.
The fundamental objectives of this document are to give ATP an indication of:
how much data is readily available at a customers location (what is available and what is missing)
where this data resides (electronically or on paper) and
what format this data is available in
In addition to these objectives, it also gives ATP a clearer understanding of what needs to be done to develop electronic interfaces between a customers systems (such as GIS, DMS or ERP systems) and PiMSlider.
ATP can then use this information as a basis for further discussions related to the data requirements for PiMSlider.
|
Data Requirements |
|
If you wish to receive copies of any of the above, please click here.
|