6. PROACTIVE MISSING INFORMATION PROTOCOL
The previous part of the project paid attention to the parameters needed to Analysts and took the Analysis phase as starting point. In this chapter, the protocol achieved in order to monitor and reduce the number of missing parameters previously identified, will be explained. To reach that conclusion, a step backwards must be taken, analysing the former phases of the ILI process and their parameters, and different options have been considered.
6.1 The ARR’s fields ownership
At this stage, all the needed parameters for analysts are together within the ARR. This is the presupposition to further interventions able to improve the process and decrease the number of missing parameters.
The first action undertaken by the candidate in this context has been addressed to have exact knowledge about who is the owner of each field in order to solve as fast as possible a situation of missing parameter.
The correct ownership of each field, is also needed in order to create a system that, once counted all the missing parameters, is able to communicate with the responsible and alert him about the lack. It can be useful, as well, to know which function the parameter supplies and if it needs it as a critical one or not.
To inform the Analyst about who is responsible of each field in the ARR, a document (shown in Figure 40) has been created by the candidate to be included in the necessary training about the modifications.
Figure 1 The ARR with indication about the responsible
The different ownership is highlighted by giving different colours to the fields, so that the responsible is easy to recognize.
The information about the ownership had already been included within the CPL but the graphical format has been seen like a good alternative to help the operator.
6.2 The Overall Critical Parameters List
Until now, the analysis has been bounded by the Analysis phase of the ILI process. At this stage, the candidate has thought that, in order to built a strategy to proactively secure all the parameters needed prior to each analysis task, the view must be extended, comprehending all the phases included inside the ILI process. This enlargement is limited at the parameters included in the CPL, this means that their behaviour outside the analysis phase will be studied. The CLP has been extended in order to cover all the other functions not considered until now. Since the ILI process is quite complex and full of feedbacks, the functions of the process have been replaced by the milestones BID, HOM and KOM. Therefore the ILI process has been schematized as follows.
Figure 2
Each parameter within the CPL has been investigated by the candidate identifying when it is used and how much important it is.
B ID R is k H O M R is k K O M R is k DC + A N R is k
PIPELINE SECTION DETAILS: Pipeline length (In
what units) Y H Y L Y H Y H
PIPELINE SECTION DETAILS: Dual diameter line? Y H Y H Y H Y H PIPELINE SECTION DETAILS: Year of construction Y L Y L Y L PIPELINE SECTION DETAILS: Subsections by wall
thickness Y H Y H Y H Y H
PIPELINE SECTION DETAILS: Nominal diameter Y H Y H Y H Y H PIPELINE SECTION DETAILS: Wall thickness Y H Y H PIPELINE SECTION DETAILS: Length (of each
individual section) Y H Y H
PIPELINE SECTION DETAILS: Pipeline Type Y H Y H Y H Y H PIPELINE SECTION DETAILS: Pipeline grade Y H Y H Y H Y H PIPELINE SECTION DETAILS: Coatings Y L Y H PIPELINE SECTION DETAILS: MAOP (Maximum
Allowable Operating Pressure) Y L Y H Y H
PIPELINE SECTION DETAILS: Design P Units Y L Y H Y H PIPELINE SECTION DETAILS: Minimum bore - Units Y L Y H Y H N PIPELINE SECTION DETAILS: Comments Y L Y L Y L Y L
PRODUCT DET:Product Y H Y H Y H Y H
Table 1 Part of the OCPL
The canons followed by the candidate building the list, are the same as the ones held for the CPL. So each parameter considered in the CPL has been taken into account. For each of them, an attribute Y or N and a weight has been assigned, in each sub-phases of the ILI process highlighted in Figure 41. Moreover, it has been established the exact stage when they are used within the analysis phase. Table 6 shows a section of the OCPL, and shows that one parameter can be critical for a phase and useless for the following, or of Low importance for a phase and H for the following one.
The principle that has driven the building of the OCPL is that it may be possible to restrict the study to the parameters that become H at the Analysis phase only and never before. This because, of all the critical parameters for this specific phase (the last one of the ILI process), some may be critical in the previous phases as well, and so we are confident that they won't be missing, since a backward phase needed them to carry on the job; meanwhile the H parameters for the Analysis phase only, could be missing.
For instance, the parameter “PIPELINE SECTION DETAILS: Pipeline length” is H for the phases before the Analysis phase. This means that, once the Analysis phase has been reached, the parameter is surely not missing, otherwise the process could not have reached that stage. Consequently there is no need for any procedure to handle those parameters.
Instead, the parameter “PIPELINE SECTION DETAILS: Coatings” is just Low in the previous phases, and it could be missing. For this reason it needs a formula to avoid that it is missing. The candidate has built 3 OCPL for Magnetic Technologies (Figure 42), UltraScan Technology (Figure 43) and Combined Technologies (Figure 44), grouping inside of these, several different technologies closed each others. The graphs illustrate the needed parameters, considering only
the CPL’s parameters, for each sub-phase and, in the yellow boxes, are highlighted the parameters which need a proactive protocol because they are not H in any previous phase.
The yellow boxes contained 46 parameters for MFL, 55 for Ultrasonic Technologies and 40 for Combined Technologies. They have been split in parameters properly for the Analysis phase and for the Data Control phase, that until now had been considered together.
Contract Logbook - Insp Run Report Section Logbook - Insp Run Report Run No Logbook - Insp Run Report Launch Logbook - Insp Run Report Receive Logbook - Insp Run Report Launch Date / Time Logbook - Insp Run Report Receive Date / Time Logbook - Insp Run Report Blocks Recorded on each Tape Logbook - Insp Run Report Total Distance Recorded Logbook - Insp Run Report Magloggers / TBM Used (y/n) Logbook - Insp Run Report Maglogger Trigger Data (y/n) Disk / eMail Maglogger Deployment Info Disk / eMail / Paper Log Field Outcome (S/F/D) Logbook - Insp Run Report Marker Magnets at Launch (y/n) Logbook - Insp Run Report Position (dist + oclock + dist to ref) Logbook - Insp Run Report Marker Magnets at Receive (y/n) Logbook - Insp Run Report Position (dist + oclock + dist to ref) Logbook - Insp Run Report T1 Gain Logbook - Insp Run Report T1 Threshold Logbook - Insp Run Report T1 Gain Run Header on Tape T1 Threshold Run Header on Tape T2 Gain Run Header on Tape T2 Threshold Run Header on Tape T1 / T2 Displacement (mm) Logbook - API T1 / T2 Displacement (mm) Run Header on Tape
T3 Attenuation Fitted (y/n) Logbook - API Project number (PII number) PQ ComOps DC PR T3 Mostly New (Green) / Mostly Old (W hite) / Mixed Logbook - T3 Data Client name PQ ComOps DC PR Mux Box Colour (Black/Green) Logbook - Insp Run Report Mobilization (s) PQ ComOps DC Magnet Type (New/Old) Logbook - Mechanical Checks Pipeline (s) PQ ComOps DC PR Options Kits Fitted Logbook - Mechanical Checks LOCATION: Launch PQ-Location ComOps DC PR Vehicle Train (LV/TV ..) Logbook - Insp Run Report LOCATION: Receive PQ-Location ComOps DC PR Sub Systems (pack/rec/bat) Logbook - Insp Run Report SERVICES REQUIRED: PQ-Services ComOps DC PR IMU Offset (mm) Logbook - Insp Run Report PIPELINE SECTION DETAILS: Pipeline length PQ-Sub-Section ComOps DC PR IMU Direction (Fwd / Rev) Logbook - Insp Run Report
PIPELINE SECTION DETAILS: Pipeline length (In
what units) PQ-Sub-Section ComOps DC PR T1 Sensor Ring Displacement* Logbook - Insp Run Report PIPELINE SEC DETAILS: Dual diameter line? PQ-Sub-Section ComOps DC PR Sensor Mapping Information* XLS from Field Tech
PIPELINE SECTION DETAILS: Subsections by wall
thickness PQ-Sub-Section ComOps DC PR Confirmation of LVDT Sensor output* Field Tech PIPELINE SECTION DETAILS: Nominal diameter PQ-Sub-Section ComOps DC PR Raw file (.mrd) Field Tech PIPELINE SECTION DETAILS: W all thickness PQ-Sub-Section ComOps DC PR Sample length Field Tech
PIPELINE SECTION DETAILS: Length (of each
individual section) PQ-Sub-Section ComOps DC PR
Tool gain Field Tech PIPELINE SECTION DETAILS: Pipeline Type PQ-Sub-Section ComOps DC PR Launch and receive photos or drawings Field Tech PIPELINE SECTION DETAILS: Pipeline grade PQ-Sub-Section ComOps DC PR Launch and receive locations (or LSD) Field Tech
PIPELINE SECTION DETAILS: MAOP (Maximum
Allowable Operating Pressure) PQ-Sub-Section ComOps DC PR AGM files Field Tech PIPELINE SECTION DETAILS: Design P Units PQ-Sub-Section ComOps PR
AGM locations Field Tech PRODUCT DET:Product PQ-Product ComOps PR
OP DETAILS:MAOP (Maximum Allowable Operating
Pressure) PQ-Product ComOps DC PR
OP DETAILS:Design Pressure PQ-Product ComOps PR
Project number (PII number) PQ ComOps DC PR REPORT TYPE:New Inspection PQ-Services ComOps DP PR
Client name PQ ComOps DC PR REPORT TYPE:Re-Inspection/Comparison PQ-Services ComOps DP PR
Mobilization (s) PQ ComOps DC REP CONTENTS: No Preliminary Report RequiredAR-MFL/TFL/HR report contents ComOps PR
Pipeline (s) PQ ComOps DC PR REP CONTENTS: >XX% Anomalies AR-MFL/TFL/HR report contents ComOps AN
LOCATION: Launch PQ-Location ComOps DC PR REP CONTENTS: Integrate/Merge with data ofAR-MFL/TFL/HR report contents ComOps AN LOCATION: Receive PQ-Location ComOps DC PR REP CONTENTS: Customer Specific RequirementsAR-MFL/TFL/HR report contents PM AN
SERVICES REQUIRED: PQ-Services ComOps DC PR CLUSTER: LminxWmin AR-MFL/TFL/HR Cluster/Feature RulesComOps AN
PIPELINE SECTION DETAILS: Dual diameter line? PQ-Sub-Section ComOps DC PR CLUSTER: Fixed Distance AR-MFL/TFL/HR Cluster/Feature RulesComOps AN
PIPELINE SECTION DETAILS: Subsections by wall
thickness PQ-Sub-Section ComOps DC PR CLUSTER: Fixed Axial AR-MFL/TFL/HR Cluster/Feature RulesComOps AN
PIPELINE SECTION DETAILS: Nominal diameter PQ-Sub-Section ComOps DC PR CLUSTER: Fixed Circumferential AR-MFL/TFL/HR Cluster/Feature RulesComOps AN
PIPELINE SECTION DETAILS: Pipeline Type PQ-Sub-Section ComOps DC PR CLUSTER: WT Multiple AR-MFL/TFL/HR Cluster/Feature RulesComOps AN
PIPELINE SECTION DETAILS: Pipeline grade PQ-Sub-Section ComOps DC PR CLUSTER: Multiple Axial AR-MFL/TFL/HR Cluster/Feature RulesComOps AN
PRODUCT DET:Product PQ-Product ComOps PR CLUSTER: Multiple Circumferential AR-MFL/TFL/HR Cluster/Feature RulesComOps AN
REPORT TYPE:New Inspection PQ-Services ComOps DP PR CODE REQ: Pressure Specification AR-MFL/TFL/HR Pipeline Code RequireComOps AN
REPORT TYPE:Re-Inspection/Comparison PQ-Services ComOps DP PR CODE REQ: MAOP Product ComOps DC PR
PREVIOUS PIGGING:Previous PII Ref. PQ-History ComOps DP PR CODE REQ: Units Product ComOps DC PR
REP CONTENTS: No Preliminary Report RequiredAR-MFL/TFL/HR report contents ComOps PR
REP CONTENTS: >XX% Anomalies AR-MFL/TFL/HR report contents ComOps AN
REP CONTENTS: Integrate/Merge with data ofAR-MFL/TFL/HR report contents ComOps AN
REP CONTENTS: Preliminary Report DaysAR-MFL/TFL/HR report contents PM AN
REP CONTENTS: Due from Milestone AR-MFL/TFL/HR report contents PM AN
REP CONTENTS: Customer Specific RequirementsAR-MFL/TFL/HR report contents PM PR
CODE REQ: Pressure Specification AR-MFL/TFL/HR Pipeline Code RequireComOps AN
Data Prep TA
P
E
Processing Prelim-Rep Analysis
REPORT TYPE:Other report Details Services ComOps REPORT TYPE:Specification Services ComOps
Project number (PII number) PQ ComOps DC PR PREVIOUS PIGGING:Last Company History ComOps
Client name PQ ComOps DC PR PREVIOUS PIGGING:Previous PII No. History ComOps
Pipeline (s) PQ ComOps DC PR CONTACT DELIV: Report Ship to Address Contract DeliverablesComOps
LOCATION: Launch PQ-Location ComOps DC PR CONTACT DELIV: Language Contract DeliverablesComOps LOCATION: Receive PQ-Location ComOps DC PR CONTACT DELIV: Number Contract DeliverablesComOps
SERVICES REQUIRED: PQ-Services ComOps DC PR CONTACT DELIV: Unit Contract DeliverablesComOps
PIPELINE SECTION DETAILS: Pipeline length PQ-Sub-Section ComOps DC PR CONTACT DELIV: Size Contract DeliverablesComOps PIPELINE SECTION DETAILS: Pipeline length (In what
units) PQ-Sub-Section ComOps DC PR CONTACT DELIV: # of CD's Contract DeliverablesComOps
PIPELINE SECTION DETAILS: Dual diameter line? PQ-Sub-Section ComOps DC PR CONTACT DELIV: Specify Deliverables Comments Contract DeliverablesComOps
PIPELINE SECTION DETAILS: Subsections by wall
thickness PQ-Sub-Section ComOps DC PR CONTACT DELIV: Contract penalities Contract DeliverablesComOps
PIPELINE SECTION DETAILS: Nominal diameter PQ-Sub-Section ComOps DC PR
REP CONTENTS: Dig sheets 15 std or specify
number MFL/TFL/HR report contents ComOps PIPELINE SECTION DETAILS: Pipeline Type PQ-Sub-Section ComOps DC PR REP CONTENTS: Pipe Image Client (Std) MFL/TFL/HR report contents ComOps
PIPELINE SECTION DETAILS: Pipeline grade PQ-Sub-Section ComOps PR REP CONTENTS: Special Excel/ Database Format MFL/TFL/HR report contents ComOps
PRODUCT DET:Product PQ-Product ComOps PR REP CONTENTS: GPS/IMU/ Mapping MFL/TFL/HR report contents ComOps
REP CONTENTS: Customer Specific RequirementsAR-MFL/TFL/HR report contents PM REP CONTENTS: Automatic General List MFL/TFL/HR report contents ComOps
CODE REQ: Pressure Specification AR-MFL/TFL/HR Pipeline Code RequireComOps AN REP CONTENTS: Re-Inspection Report MFL/TFL/HR report contents ComOps
REP CONTENTS: HardSpot MFL/TFL/HR report contents ComOps REP CONTENTS: Run Comparison MFL/TFL/HR report contents ComOps REP CONTENTS: Correlation W ith Previous Runs MFL/TFL/HR report contents ComOps REP CONTENTS: Corrsion Growth Study MFL/TFL/HR report contents ComOps REP CONTENTS: Fitness-For-Purpose MFL/TFL/HR report contents ComOps Scan rate (Scan Pitch) Not in eDelivery PM REP CONTENTS: LAPA MFL/TFL/HR report contents ComOps Data format System Settings-Critical InputsPM REP CONTENTS: Baseline Survey MFL/TFL/HR report contents ComOps Sizing Model (Run Time Model) System Settings-Critical InputsPM REP CONTENTS: POF MFL/TFL/HR report contents ComOps Mux Box colour System Settings-Critical InputsPM REP CONTENTS: Pipebook MFL/TFL/HR report contents ComOps T1 Gain System Settings-Critical InputsPM REP CONTENTS: Seam Weld MFL/TFL/HR report contents ComOps Attenuators fitted ? PM REP CONTENTS: Pipevision MFL/TFL/HR report contents ComOps Vehicle identification Resources-Specify Vehicle-Build ListPM REP CONTENTS: Full Body MFL/TFL/HR report contents ComOps Leading module id Project Plan-Run-Task DetailsPM
REP CONTENTS: Correlation with Client pipebook
Stationing MFL/TFL/HR report contents ComOps REP CONTENTS: Pitting Inspection MFL/TFL/HR report contents ComOps REP CONTENTS: Final Report Days MFL/TFL/HR report contents PM REP CONTENTS: Due from Milestone MFL/TFL/HR report contents PM REP CONTENTS: AGM-Client Referencing Required MFL/TFL/HR report contents ComOps CLUSTER: Feature Selection Rule PQ/Services ComOps CLUSTER: Real specification MFL/TFL/HR Cluster/Feature RulesComOps CODE REQ: Section # Sub-Section ComOps Data Control Additional Info (H)
Final-Rep
Field to Analysis Parameters
HOM H Priority Parameters
BID H Priority Parameters
KOM H Priority Parameters
Analysis Requirements Additional Info (H)
BID HOM KOM Check
Point
Project number (PII number) PQ ComOps
Client name PQ ComOps
Mobilization (s) PQ ComOps
Pipeline (s) PQ ComOps
LOCATION: Launch PQ-Location ComOps LOCATION: Receive PQ-Location ComOps
SERVICES REQUIRED: PQ-ServicesComOps log PIPELINE SECTION DETAILS: Pipeline length PQ-Sub-Section ComOps log
PIPELINE SECTION DETAILS: Pipeline length (In what units) PQ-Sub-Section ComOps log PIPELINE SECTION DETAILS: Dual diameter line?PQ-Sub-Section ComOps
PIPELINE SECTION DETAILS: Subsections by wall thickness PQ-Sub-Section ComOps log PIPELINE SECTION DETAILS: Nominal diameter PQ-Sub-Section ComOps
PIPELINE SECTION DETAILS: Wall thickness PQ-Sub-Section ComOps log individual section) PQ-Sub-Section ComOps Field Report WM-CD PIPELINE SECTION DETAILS: Pipeline grade PQ-Sub-Section ComOps Field Report WM-CD
PIPELINE SECTION DETAILS: MAOP (Maximum Allowable Operating Pressure) PQ-Sub-Section ComOps Field Report WM-CD PIPELINE SECTION DETAILS: Design P Units PQ-Sub-Section ComOps Field Report WM-CD PRODUCT DET:Product PQ-Product ComOps Field Report WM-CD
OP DETAILS:MAOP (Maximum Allowable Operating
Pressure) PQ-Product ComOps
Field Report WM-CD OP DETAILS:Design Pressure PQ-Product ComOps Field Report WM-CD REPORT TYPE:New Inspection PQ-ServicesComOps WM-CD REPORT TYPE:Other report Details PQ-Services ComOps Field Report WM-CD REPORT TYPE:Re-Inspection/Comparison PQ-ServicesComOps WM-CD REPORT TYPE:Specification PQ-Services ComOps Field Report WM-CD REPORT TYPE:Other report Details PQ-ServicesComOps WM-CD PREVIOUS PIGGING:Previous PII No. PQ-History ComOps PM or eDelivery WM-CD REPORT TYPE:Specification PQ-ServicesComOps WM-CD CONTACT DELIV: Report Ship to Address AR/Contract Deliverab ComOps PM or eDelivery WM-CD PREVIOUS PIGGING:Previous PII Ref. PQ-History ComOps WM-CD DELIVERABLES: Language AR/Contract Deliverab ComOps Field Report W M W M-CD US Report1: No Preliminary Report Required AR/US ReportComOps WM-CD DELIVERABLES: Number AR/Contract Deliverab ComOps Odo Pluses / Rotation Field Report W M W M USWM Report1: >XX% Anomalies AR/USWM Report ComOps WM-CD DELIVERABLES: Unit AR/Contract Deliverab ComOps Marker Corr. Distance Field Report W M CD USCD Rep Contents:No Preliminary Report Required AR/USCD Report ComOps WM-CD DELIVERABLES: Size AR/Contract Deliverab ComOps Trigger Delay Field Report W M CD USCD Rep Contents:Pipebook AR/USCD Report ComOps WM-CD DELIVERABLES: # of CD's AR/Contract Deliverab ComOps E Type / BTD / RoHatSu / AEP Field Report W M CD USCD Rep Contents:Marker List AR/USCD Report ComOps WM-CD DELIVERABLES: Specify Deliverables CommentsAR/Contract Deliverab ComOps W T - Resolution Field Report W M CD USCD Rep Contents:Feature List AR/USCD Report ComOps WM-CD US Report1: Dig sheets 15 std or specify number AR/US ReportComOps TBMS / Time Field Report W M CD USCD Rep Contents:Other AR/USCD Report ComOps WM-CD US Report1: Pipe Image Client (Std) AR/US ReportComOps No. of Sensors Installed Field Report W M W M-CD US Report1: Integrate/Merge with data of AR/US ReportComOps WM-CD US Report1: Special Excel/ Database Format AR/US ReportComOps No of Sensor Spots in Carrier Field Report W M W M-CD US Report2: Customer Specific Requirements AR/US ReportComOps WM-CD US Report1: GPS/IMU/ Mapping AR/US ReportComOps Longitudinal Sensor Distance Field Report W M W M USWM Specs1: Minimum size Stand off AR/USWM Specs ComOps WM-CD US Report1: Re-Inspection AR/US ReportComOps Assignment of Sensor Numbers Field Report W M W M USWM Specs1: Longitudinal ERW AR/USWM Specs ComOps WM-CD US Report1: Run Comparission AR/US ReportComOps Pend. Value for Ref. Sensor no Field Report W M W M USWM Specs1: Longitudinal DSAW AR/USWM Specs ComOps WM-CD US Report1: Correleation With Previous Runs AR/US ReportComOps Ref. Sensor No. at 6h position Field Report W M W M USWM Specs1: Spiral AR/USWM Specs ComOps WM-CD US Report1: Corrsion Growth Study AR/US ReportComOps Tolerance Band SO Field Report W M W M USWM Specs1: Seamless AR/USWM Specs ComOps WM-CD US Report1: Fitness-For-Purpose AR/US ReportComOps Tolerance Band W T Field Report W M W M-CD US Specs2: Previous Reports Available AR/US SpecsComOps WM-CD US Report1: Baseline Survey AR/US ReportComOps No. of Sensor Groups Field Report W M W M-CD SUB-SEC DETAILS: Coatings AR/US SpecsComOps WM-CD US Report1: POF AR/US ReportComOps Counting Dir of Pendulum Field Report W M CD USCD Specs: Type of USCD Inspection AR/USCD Specs ComOps WM-CD US Report1: Pipebook AR/US ReportComOps Counting Dir of Sensor Field Report W M CD USCD Specs: Length AR/USCD Specs ComOps WM-CD US Report1: Seam Weld AR/US ReportComOps Mass Storage Type Field Report W M CD USCD Specs: Depth AR/USCD Specs ComOps
WM USWM Report1: Pipevision AR/USWM Report ComOps Temperature in Pig Field Report W M CD USCD Specs: Length AR/USCD Specs ComOps
WM USWM Report1: Pitting Inspection AR/USWM Report ComOps Humidity in Pig Field Report W M CD USCD Specs: Depth AR/USCD Specs ComOps WM-CD US Report1: Full Body AR/US ReportComOps Temperat. In Meduim Field Report W M CD USCD Specs: Crack Like AR/USCD Specs ComOps WM-CD US Report1: Correlation with Client pipebook Stationing AR/US ReportComOps Pressure in Medium Field Report W M CD USCD Specs: Crack AR/USCD Specs ComOps WM-CD US Report1: Preliminary Report Days AR/US Report PM Real Pipeline Diameter Field Report W M CD USCD Specs: Notch AR/USCD Specs ComOps WM-CD US Report1: Due from Milestone AR/US Report PM Odo Wheel Diameter Field Report W M CD USCD Specs: Installations AR/USCD Specs ComOps WM-CD US Report2: AGM-Client Referencing Required AR/US ReportComOps Photos of fittings or engineering drawings of launchField Report CD CD USCD Specs: Longitudinal ERW AR/USCD Specs ComOps WM USWM Specs1: Depth AR/USWM Specs ComOps Photos of fittings or engineering drawings of receiveField Report CD CD USCD Specs: FW (Flash W elded) AR/USCD Specs ComOps WM USWM Specs1: OR if Other AR/USWM Specs ComOps B1 Sheet Comments (T-piece postions)Field Report CD CD USCD Specs: Longitudinal DSAW AR/USCD Specs ComOps WM USWM Specs1: OR remaining Wall Thickness AR/USWM Specs ComOps Run distance [km]: after receiving Field Report CD CD USCD Specs: Spiral AR/USCD Specs ComOps WM USWM Specs1: Min Length AR/USWM Specs ComOps Cycle count: after receiving Field Report CD CD USCD Specs: Seamless AR/USCD Specs ComOps WM USWM Specs1: Min Width AR/USWM Specs ComOps Cycles missing: after receiving Field Report CD W M-CD Add Customer Info: Pressure Specification Sub-Section ComOps WM USWM Specs1: With specification of Depth (Y/N)AR/USWM Specs ComOps Filecounts Bus 1 before launching Field Report CD W M-CD PIPELINE SECTION DETAILS: Design P Sub-Section ComOps WM USWM Specs1: Longitudinal Lap-W elded AR/USWM Specs ComOps Filecounts Bus 2 before launching Field Report CD W M-CD PIPELINE SECTION DETAILS: Design P Units Sub-Section ComOps WM USWM Specs1: Other AR/USWM Specs ComOps Filecounts Bus 1 after receiving Field Report CD W M-CD PIPELINE SECTION DETAILS: Pipeline grade Sub-Section ComOps WM USWM Specs2: Report of Pipe type changes AR/USWM Specs ComOps Filecounts Bus 2 after receiving Field Report CD W M-CD SUB-SEC DETAILS: Subsections by wall thickness Product ComOps WM USWM Specs2: Manufactored related WT variationsAR/USWM Specs ComOps Check of POSU error messages Field Report CD W M-CD SUB-SEC DETAILS: Nominal diameter Product ComOps WM USWM Specs2: If yes, min AR/USWM Specs ComOps Check of POSU resets during Run Field Report CD W M-CD SUB-SEC DETAILS: W all thickness Product ComOps WM USWM Specs2: Reporting of Deposits AR/USWM Specs ComOps Pig Run success evaluation S/D/F Field Report CD W M-CD
SUB-SEC DETAILS: Length (of each individual
section) Product ComOps WM USWM Specs2: If yes, min size AR/USWM Specs ComOps Describe any faults or condition changes during runField Report CD W M-CD PROD DETAILS: Product Product ComOps WM-CD
US Specs2: Previous Reports of other technology
Available AR/US SpecsComOps W M-CD
OP DETAILS: Flow Rate (Min, Normal, Max)
Product ComOps WM-CD US Specs2: If yes, which AR/US SpecsComOps W M-CD OP DETAILS: Pressure (Min, Normal, Max) Product ComOps WM-CD US Specs2: Pipebook available: Hardcopy AR/US SpecsComOps W M-CD OP DETAILS: MAOP Nominal Product ComOps WM-CD US Specs2: Pipebook available: Electronic AR/US SpecsComOps W M-CD OP DETAILS: Design Pressure Nominal Product ComOps WM-CD US Specs2: If yes, which AR/US SpecsComOps W M-CD TRAP DETAILS: Location Location ComOps CD USCD Specs: Longitudinal Lap-Welded AR/USCD Specs ComOps W M-CD TRAP DETAILS: Site Name Location ComOps CD USCD Specs: Other AR/USCD Specs ComOps W M-CD TRAP DETAILS: State/Province Location ComOps WM Add Customer Info: All Sub-Section ComOps W M-CD TRAP DETAILS: Country Location ComOps WM Add Customer Info: If no, Which Sub-Section ComOps
Data Prep TA
P
E
Processing Prelim-Rep Analysis
Project number (PII number) PQ ComOps DC PR Data Contro Additional Info (H)
Client name PQ ComOps DC PR PQ ComOps WM-CD PQ-Services ComOps
Pipeline (s) PQ ComOps DC PR PQ ComOps WM-CD PQ-History ComOps
LOCATION: Launch PQ-Location ComOps DC PR PQ ComOps WM-CD PQ-History ComOps LOCATION: Receive PQ-Location ComOps DC PR PQ-Location ComOps
SERVICES REQUIRED: PQ-Services ComOps DC PR PQ-Location ComOps PIPELINE SECTION DETAILS: Pipeline length PQ-Sub-Section ComOps DC PR PQ-Services ComOps PIPELINE SECTION DETAILS: Pipeline length (In what
units) PQ-Sub-Section ComOps DC PR PQ-Sub-Section ComOps
PIPELINE SECTION DETAILS: Dual diameter line?PQ-Sub-Section ComOps DC PR PQ-Sub-Section ComOps PIPELINE SECTION DETAILS: Subsections by wall
thickness PQ-Sub-Section ComOps DC PR PQ-Sub-Section ComOps
PIPELINE SECTION DETAILS: Nominal diameter PQ-Sub-Section ComOps DC PR PQ-Sub-Section ComOps
PIPELINE SECTION DETAILS: Pipeline grade PQ-Sub-Section ComOps DC PR PQ-Sub-Section ComOps
PRODUCT DET:Product PQ-Product ComOps PR PQ-Sub-Section ComOps
US Report: Customer Specific Requirements US Report PM PR PQ-Product ComOps
Add Customer Info: Pressure Specification Sub-Section ComOps AN US Report2: Customer Specific RequirementsAR/US Report ComOps
Add Customer Info: Pressure Specification Sub-Section ComOps
PREVIOUS PIGGING:Previous PII No.
BID H Priority Parameters Project number (PII number) HOM H Priority Parameters
REPORT TYPE:Other report Details PREVIOUS PIGGING:Last Company
Client name Pipeline (s)
Final-Rep Analysis Req Additional Info (H)
Run No Launch Receive Line Length Out of Trap Date Pipeline Diameter Medium Sound Velocity Meduim for Coupling Sensor Carrier Type
KOM H Priority Parameters
Contract Section Inspection Name
Field to Analysis Parameters
LOCATION: Launch LOCATION: Receive
SERVICES REQUIRED:
PIPELINE SECTION DETAILS: Pipeline length
PIPELINE SECTION DETAILS: Pipeline grade PRODUCT DET:Product
PIPELINE SECTION DETAILS: Pipeline length (In what units)
PIPELINE SECTION DETAILS: Dual diameter line?
PIPELINE SECTION DETAILS: Subsections by wall thickness
PIPELINE SECTION DETAILS: Nominal diameter
BID HOM KOM Check Point
Figure 4 OCPL for UltraScan
However, this strategy does not offer sufficient guaranty, because it is impossible to assure that a parameters is not missing, even if it is H, without the presence of a rigours point of control. For this reason it has been rejected for another more efficient.
Project number (PII number) PQ ComOps
Client name PQ ComOps
Mobilization (s) PQ ComOps
Pipeline (s) PQ ComOps
LOCATION: Launch PQ-Location ComOps LOCATION: Receive PQ-Location ComOps
SERVICES REQUIRED: PQ-Services ComOps
PIPELINE SECTION DETAILS: Pipeline length PQ-Sub-Section ComOps Project number (PII number) PQ ComOps
PIPELINE SECTION DETAILS: Pipeline length (In what
units) PQ-Sub-Section ComOps Client name PQ ComOps PIPELINE SECTION DETAILS: Dual diameter line? PQ-Sub-Section ComOps Mobilization (s) PQ ComOps
PIPELINE SECTION DETAILS: Subsections by wall
thickness PQ-Sub-Section ComOps Pipeline (s) PQ ComOps PIPELINE SECTION DETAILS: Nominal diameter PQ-Sub-Section ComOps LOCATION: Launch PQ-Location ComOps PIPELINE SECTION DETAILS: W all thickness PQ-Sub-Section ComOps LOCATION: Receive PQ-Location ComOps
PIPELINE SECTION DETAILS: Length (of each individual
section) PQ-Sub-Section ComOps
SERVICES REQUIRED: PQ-Services ComOps PIPELINE SECTION DETAILS: Minimum bore - Units PQ-Sub-Section ComOps
PIPELINE SECTION DETAILS: Dual diameter
line? PQ-Sub-Section ComOps PRODUCT DET:Product PQ-Product ComOps
PIPELINE SECTION DETAILS: Subsections by
wall thickness PQ-Sub-Section ComOps
OP DETAILS:MAOP (Maximum Allowable Operating
Pressure) PQ-Product ComOps PIPELINE SECTION DETAILS: Nominal diameter PQ-Sub-Section ComOps OP DETAILS:Design Pressure PQ-Product ComOps PIPELINE SECTION DETAILS: Minimum bore -
Units PQ-Sub-Section ComOps REPORT TYPE:New Inspection PQ-Services ComOps
PRODUCT DET:Product PQ-Product ComOps REPORT TYPE:Re-Inspection/Comparison PQ-Services ComOps OP DETAILS:Design Pressure PQ-Product ComOps PREVIOUS PIGGING:Previous PII Ref. PQ-History ComOps REPORT TYPE:New Inspection PQ-Services ComOps MODIFICATIONS:Launch PQ-Modifications ComOps REPORT TYPE:Re-Inspection/Comparison PQ-Services ComOps MODIFICATIONS:Receive PQ-Modifications ComOps PREVIOUS PIGGING:Previous PII Ref. PQ-History ComOps In-Field report req? Y/N AR-CLP/CLS ComOps In-Field report req? Y/N AR-CLP/CLS ComOps SUB-SEC DETAILS: Minimum Known Bore PQ-Sub-Section ComOps Field Report Days AR-CLP/CLS ComOps SUB-SEC DETAILS: Subsections by wall thickness PQ-Sub-Section ComOps Due from Milestone AR-CLP/CLS ComOps SUB-SEC DETAILS: Nominal diameter PQ-Sub-Section ComOps SUB-SEC DETAILS: Minimum Known Bore PQ-Sub-Section ComOps SUB-SEC DETAILS: W all thickness PQ-Sub-Section ComOps SUB-SEC DETAILS: Subsections by wall thickness PQ-Sub-Section ComOps
SUB-SEC DETAILS: Length (of each individual section)
PQ-Sub-Section ComOps SUB-SEC DETAILS: Nominal diameter PQ-Sub-Section ComOps PROD DETAILS: Product PQ-Product ComOps PROD DETAILS: Product PQ-Product ComOps OP DETAILS: Temperature (Min, normal, Max) PQ-Product ComOps OP DETAILS: Temperature (Min, normal, Max) PQ-Product ComOps OP DETAILS: Flow Rate (Min, Normal, Max) PQ-Product ComOps OP DETAILS: Flow Rate (Min, Normal, Max) PQ-Product ComOps OP DETAILS: Pressure (Min, Normal, Max) PQ-Product ComOps OP DETAILS: Pressure (Min, Normal, Max) PQ-Product ComOps TRAP DETAILS: Location PQ-Location ComOps TRAP DETAILS: Location PQ-Location ComOps TRAP DETAILS: Site Name PQ-Location ComOps TRAP DETAILS: Site Name PQ-Location ComOps TRAP DETAILS: State/Province PQ-Location ComOps TRAP DETAILS: State/Province PQ-Location ComOps TRAP DETAILS: Country PQ-Location ComOps TRAP DETAILS: Country PQ-Location ComOps
Data Prep TA
P
E
Processing Prelim-Rep Analysis
Project number (PII number) PQ ComOps
Client name PQ ComOps REPORT TYPE:Other report Details PQ-Services ComOps
Pipeline (s) PQ ComOps REPORT TYPE:Specification PQ-Services ComOps
LOCATION: Launch PQ-Location ComOps PREVIOUS PIGGING:Previous PII No. PQ-History ComOps LOCATION: Receive PQ-Location ComOps CONTACT DELIV: Report Ship to Address
AR-Contract Deliverables ComOps
SERVICES REQUIRED: PQ-Services ComOps CONTACT DELIV: Language
AR-Contract Deliverables ComOps PIPELINE SECTION DETAILS: Pipeline length PQ-Sub-Section ComOps CONTACT DELIV: Number
AR-Contract Deliverables ComOps PIPELINE SECTION DETAILS: Pipeline length (In
what units) PQ-Sub-Section ComOps CONTACT DELIV: Unit
AR-Contract Deliverables ComOps PIPELINE SECTION DETAILS: Dual diameter
line? PQ-Sub-Section ComOps CONTACT DELIV: Size
AR-Contract Deliverables ComOps PIPELINE SECTION DETAILS: Subsections by
wall thickness PQ-Sub-Section ComOps CONTACT DELIV: # of CD's
AR-Contract Deliverables ComOps PIPELINE SECTION DETAILS: Nominal diameter PQ-Sub-Section ComOps Threeshold: Dent % AR-CLP/CLS ComOps PRODUCT DET:Product PQ-Product ComOps Threeshold: Ovalities % AR-CLP/CLS ComOps SUB-SEC DETAILS: Subsections by wall thickness PQ-Sub-Section ComOps Passage Clearance Test Y/N AR-CLP/CLS ComOps SUB-SEC DETAILS: Nominal diameter PQ-Sub-Section ComOps Min ID in Straight Pipe mm AR-CLP/CLS ComOps TRAP DETAILS: Location PQ-Location ComOps Min ID in Bend mm AR-CLP/CLS ComOps TRAP DETAILS: Site Name PQ-Location ComOps Final report req? Y/N AR-CLP/CLS ComOps TRAP DETAILS: State/Province PQ-Location ComOps Threeshold: Dent % AR-CLP/CLS ComOps TRAP DETAILS: Country PQ-Location ComOps Threeshold: Ovalities % AR-CLP/CLS ComOps Bend Angle >= ° AR-CLP/CLS ComOps Other ID Reductions % AR-CLP/CLS ComOps Final Report Days AR-CLP/CLS ComOps Due from Milestone AR-CLP/CLS ComOps Can extend to wait for HOT? AR-CLP/CLS ComOps Max days to wait AR-CLP/CLS ComOps Rep Type: PII Standard Y AR-CLP/CLS ComOps Rep Type: POF Stand. AR-CLP/CLS ComOps Rep Type: API 1163 Stand AR-CLP/CLS ComOps Rep Type: Other – comment field AR-CLP/CLS ComOps Rep Style: Merge Only (no report) AR-CLP/CLS ComOps Rep Style: Stand-Alone (no correlation/no merge) AR-CLP/CLS ComOps Rep Style: Full Correlated Report AR-CLP/CLS ComOps Rep Style: Full Correlated Report (as appendix to HOT Report) AR-CLP/CLS ComOps Add-Ins: Data Set (Calview) AR-CLP/CLS ComOps Add-Ins: Pipebook (XLS) AR-CLP/CLS ComOps Add-Ins: Pipeline Listing (XLS) AR-CLP/CLS ComOps Add-Ins: Electronic Report (PDF) AR-CLP/CLS ComOps Add-Ins: Include Field Report as appendix AR-CLP/CLS ComOps Add-Ins: Provide Detailed Channel Information for IS AR-CLP/CLS ComOps Add-Ins: GPS Co-ordinates for GWs AR-CLP/CLS ComOps Add-Ins: GPS Co-ordinates for All Features AR-CLP/CLS ComOps
PROD DETAILS: Other (Specify) PQ-Product ComOps
Analysis Req Additiona Info (H)
Final-Rep
BID H Priority Parameters HOM H Priority Parameters
KOM H Priority Parameters
BID HOM KOM Check Point
These figures show the overall situation about the parameters within the CPL, that is the situation of the parameters critical for the Analysis phase. For each of them, a note about the location and the owner of the information has been added, together with the indication of the sub process of the
Analysis phase in which they are required. Therefore, the information shown in the list are:
• Owner (who is responsible for and who enters that parameter) • Position (where you can find it in eDelivery)
• Where the parameter became critical for the Analysis phase.
The OCPL makes available information about the stage of the Analysis Phases, where each parameter is required, as well as the moment when it becomes critical.
This information can be used to build a strategy to assure that needed parameters aren’t missing just a few days before the date in which they are expected to become critical. This option drives from the graph in Figure 45 about the MFL case. It shows that a big amount of parameters from the CPL is needed just in the end of the analysis process. This means that the time available to gather them is more than it would be if they were needed in the first phase, since the Analysis phase lasts almost a month and it is known that more than half parameters become critical in the last stages of the analysis process only; this would guarantee more time to gather them.
Owing this information it will be possible to establish, for each parameter, in which date it should be available and to monitoring the remaining time before that date.
Following all the considerations communicate above, the candidate has proposed two possible directions to pursue:
10
10
10
10
3333
28
28
28
28
Figure 6 Distribution of the parameters within the Analysis Phase
• To fix a different deadline for each parameter considering the stage of the Analysis phase where it become critical;
• To fix an unique deadline for all the parameters, ensuring that they are available before the start of the analysis phase.
Figure 7 Schema of the new approach adopted
The first direction gives more time to gather each parameters but, on the other hand, the procedure to monitoring them could become very complex, because each parameter has a different “critical date”.
The second direction is easier to implement but implies that some parameters are available lots before their critical date.
Together with the Data Control Team, the candidate has decided to follow the direction two, establishing an only deadline for all the parameters, and this date has been fixed 1 week before the tape arrival.
An interesting result of this analysis is about the parameters contained in the PQ, as shown in Table 7. The table is related to the parameters in CPL coming from the PQ only. It is clear that at the end of the HOM phase, when the PQ should be completed, just the 40% of the parameters are really needed. Since one of the problems about the PQ is the massive amount of parameters involved in it, a possible solution could be to split the request of those parameters in two different moments of the contact with the client.
Phase N° of required parameters to supply in the begin of the phase H 23 Bid 38 L 15 38 H 64 HOM 99 L 30 82 H 131 KOM 136 L 5 90 H 28 DC 29 L 1 5 H 31 Analysis 47 L 16 11 Table 7
This result may be useful for a forthcoming project about a review of the PQ, to which this project has given a first contribution.
The proposal about it is related with a subdivision of the parameters requested in two stages (as explained above) and a redevelopment of the graphic form of the form. Until now, PQ is just an excel form with hundreds of queries. This is why a new interactive version of it could be considerably helpful, inducing the client to reply to them and reducing the missing information and the work of ComOps of gathering them.
6.3 PM to Analyst Metric
At the moment, all the parameters needed for the analysis’ phases are known, as well as the exact stage of the process when they become critical and the owner: all those information are inside the CPL. This list, completed with the other information must be used as refer point to measure the trend of missing parameters and to avoid them.
First stage of contact with the Client - 39% of parameters inside PQ
Second stage of contact with the Client – remaining
To do that, together with the Data Control Team, the candidate has decided to implement a metric.
BID HOM KOM
Analysis Phase
TAPE ARRIVAL
CHECK POINT
This metric, called PM to Analyst Metric is based on a check-point, a point where the system checks which parameters are missing and starts the corrective actions.
The corrective actions are two:
• The system identifies the owner of the missing field and sends to him an alert about it. • The system builds a metric following several criteria.
Building a metric showing the number of missing parameters for any Project Manager could be seen as a corrective action because the knowledge that the performance are clearly recorded may increase the quality of the job done by PM.
The refer point for the metric will be the run date. It is the date when the inspection will take place, and it is about 1 week before the arrival of the tape at the site. The check point has been fixed up 2 weeks before the run date but the amount of time is variable.
The candidate has defined all the aspects of the metric and has interacted with the IT manager, in order to help him with the technical
operations needed to implement it.
6.3.1 Where
The metric will be available from two different points of eDelivery.
The first access is from the eDelivery Launch pad, where it will be possible to have access to the metrics directly through the dedicated section PM to ANALYSIS METRICS, inside Data Analysis (see figure 48). This section can be used by anyone who is interested to know more about the current or past situation within a
specific region, or about technologies or about the performance of a specific PM.
The second access expected is directly through a special Metric Tab inside the Data Analysis Area in the eProject section (see Figure 47 eDelivery Launch Pad). The Data Analysis Area already exists and in this area PM can already find information about the contract. Adding the metric, he will be able to check the missing parameters and the time available to provide/find them. Figure 45 shows an example about how the new tab will look like.
Figure 9 The new Tab: Metric
6.3.2 The search criteria
The metric is based on two sources of data: • Current data
• Alerts stored
The current data are the data that are at the moment inside eDelivery. The metric that uses the current data can specify the number of missing parameters at the moment when it has been produced and it depends on specific requirements. Therefore it can offer just a snapshot of that moment.
The alerts contained the information about the missing parameters at the trigger moment (2 weeks before the run date), that is the moment when the system automatically produces the alert to the charged PM. It is possible to produce consideration about the trend storing the information.
This second kind of metric is very powerful because, choosing an appropriate frequency of the alert, it is possible to measure and control the process of filling the parameters.
This information can be very useful in order to improve the process of gathering the parameters. The important difference, with the other kind of source of data, is that this one needs a
system knows what alert to consider and what else not to consider. The result will be the average value on the interval of time considered. This case will be explained in detail below. The search criteria, listed below, are the same for both the source utilized and they can be used separately or together following the logic schema below:
(criteria 1) AND (criteria 2) AND ….
• PM = using this criteria it is possible to see all the contract managed by a particular PM (at the moment or in a particular window of time).
• Region = this criteria includes all the contracts in a particular region. It is very general so it will be considered together with other criteria.
• Technology = this criteria includes a particular type of technology. The same considerations of Region are valid.
• Contract = it includes all the sections inspected for the particular contract number. • Section = it refers the metric to a particular section inside a contract number.
The combination of different criteria can generate several kinds of metric. The candidate has selected some of them to become active, following the requirements of the Data Control Team Global Leader.
In particular it has been decided to realize two metrics based on current data and two metrics based on historic data.
The elements considered in the calculation of the metric are the following:
Button to produce the list of missing
parameters M et ric s b as ed o n cu rr en t d at a M et ric s b as ed o n h is to ric d at a Buttons to produce the graphs
PII N° (noted with the pedicle i) is the PII code m ade up of the contract number and the section inspected. PII n° can not identify univocally an in spection and so a %MP because the same section, so that the same PII n°, may have been ins pected with two technologies. For this reason, the %MP is univocal for a combination of PII N° and Technology, indicated by the notation: %MPi,j
Where j is the technology so
j ∈ { M, U, C} with M = Magnetic, U = Ultrascan, C = Combined.
The pedicle r specifies the region. It is not strictly necessary because two regions can not have the same PII number. However, it is specified as a pedicle because is some cases the sum has been extended to the whole region.
6.3.3 Metric based on current situation
% of Missing Parameters for Section
% of Missing Parameters for Section
Input Output
PII number Charged PM
Section %of missing parameters (%MPs) Technology List of missing parameters
As explained above, this metric is based on the current situation, so that the information that will be produced are referred to the current date. This kind of metric is the kind that the system runs automatically at the trigger date, and this means that the alerts stored contained the information listed above. The %MP i i,j,r j
(n. missing parameters) 100
% MP
(Total amount of parameters)
⋅
=
is calculated like the percentage on the total number of parameters. This number is the total number of parameters contained in the CPL for the technology specified in the input’s window. The list of missing parameters (see figure 46) is contained in an excel worksheet and it can be seen by pressing the dedicated button on the PM to Analyst screen.
Figure 11 Result of the % of Missing Parameters for Section Metric
The cons of this metric is that, in order to decrease the number of missing parameters, PM could think to put 0 or any other value instead of the right value.
To avoid this, it is planned to insert, for each field, a check to control that the value falls into a valid segment, so that the value has to fit inside it to be accepted.
Establish a valid interval for each parameter is possible without any huge difficulty but the Data Control team has decided to concentrate the effort implementing this first version with the aim of following improvement in the future.
The metric will be located in the section dedicated to the PM to Analyst metric.
%Missing Parameters at the current situation
% of Missing Parameters at the current situation
Input Output (by section)
Window of time Charged PM
Region %of missing parameters (%MPs) Technology List of missing parameters
Run Date
This metric provides information about PM responsible, the %MPs, a list of them and the run date, for each section, that has run date included in the selected window of time, technology and region.
In this case, the information are shown in an excel graph only, because the graphic form can help to better comprehend the situation rather than the analytic form.
The run date is when the number in the bar is 0 (zero) and the positive and negative number shows respectively the days after and before the run date. The different colours mark the criticality of the situation. Two weeks before the run date, the yellow reveals that there are some missing parameters, but there is still some time available to gather them. The orange colour means that there is less than 1 week left to collect the missing parameters. The red colour shows that it is the of out-of-date case: a report has been produce and the performance of the PM will be decreased.
Current Date 01-feb Show Just Contract with Missing Information
R e g io n P M C o n tr a c t S e c ti o n T e c h R u n D a te R u n D a te % MPs ## ## ## ## ## -9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
NA Joe Bloggs C12344 12A MFL 01-feb 5% NA Joe Bloggs C12345 12A MFL 05-feb 1% NA Joe Bloggs C12346 12A MFL 25-gen 10% NA Joe Bloggs C12348 12A MFL 28-gen 10% NA Joe Bloggs C12350 12A MFL dd/mm 15%
Figure 12 Example of the graph result of the metric
It is also possible to see the list of missing parameters by clicking on the contract number on the graph. This link allows seeing the list of parameters missing. This percentage is shown by the metric: %Missing Parameters for Section seen above.
It is necessary to draw the attention to the fact that this graph is not dynamical, but it shows the situation at the date shown in the field Current date.
Of this category belong the metric contained in the Data Analysis Section as well. It will looks like the figure below
6.3.4 Metric based on Historic data
These metrics are based on all the alerts automatically produced by the system, 2 weeks before the RunDate. These reports must be stored in a special location, in order to be looked up. These kinds of metric are needed to the Management to analyze and draw conclusions about the situation.
These metric are selectable from the PM to Analyst Metric section, but the results are illustrated by a graph only. The criteria are selectable from a common area on the left of the screen, and the graph are visible by pressing the related buttons.
The two metric suggested by the candidate are:
%Missing Parameters for Region
%Missing Parameters for Region
Input Output
Window of time %MPs for each technology
Region total %MPs for each Region
The metric gives the opportunity to look at the general trend of each technology. In this way it is possible to have a general idea about the performance of each region, grouped by technology.
As explained in the formula, the %MPj,r is the medium percentage of missing parameters in a
region for a certain technology and it is the result of the rate between the sum of %MP related to a particular region and technology over the number of PII n° that use that technology in that region.
All these information are referred to PII N° with r un date included in the windows of time selected. The results will be shown in an excel worksheet, and an example is reported in figure 48. i,j,r i j,r j,r % MP % MP
(The number of PII n°)
Figure 14
Trend for %MPs for Technology
% of Missing Parameters at the current situation
Input Output (by reference period) Window of time %MPs for each technology for
each period Region
Reference Period
This metric provides, for the selected region, the %MPs per technology, dividing them for a period of time chosen by the user. In the example below, the comparison is made considering the results for each month.
The process of counting the parameters is not as easy as it seems.
The CPL is different for each technology, but it is different inside the same technology as well. For example, the number of critical parameters for MFL is different from the number for UltraScan CD, but, within MFL technology, the number of parameters is different even if the client wants or not the preliminary report. In the first case, both the Preliminary Report field and the field DATE must be filled in, so these are critical parameters, and they appeared inside the CPL. If the Preliminary Report is not required, the field Date is not required and so it must not be counted.
This is just one example of the tens of fields combined one another. In order to identify all the relations, the candidate has built a list with all the linked fields.
In some cases, this has implied to study technical parameters to better understand all the relations between them.
The figure shows part of the final worksheet.
The ticked box on the cross between rows and columns shows that the field must be counted. Each row assigns a refer number to the correspondent field. The row that are linked in the first column have to be counted in any situation. If the first column is not ticked, the field has a particular combination and the fields to count are the ones ticked in the column correspondent with the refer number of the row. This refer number is reported on the top of the graph to highlight the link with the field below it. A small complication about the construction of the graph is that often the fields are not just tickable or untickable but they imply the choice of on set of value. In that case, the refer number of the top pf the graph shows the name of the field and, below it, there is the
possible choice. If the field is just tickable or not, the fields below the refer number on the column shows “ticked” to mean that the combination is valid if the field is ticked.
The list is built on the current list of parameters, and so, with grey rows, are indicated the fields that will be eliminated when the SMR’s submitted will take place.
For example, the field 15 has to be counted in any situation because, as explained above, the box in its row on the first column is ticked. The box on the first column of the field 17, instead, is not ticked, so it has to be counted just in a particular situation. To understand when it has to be counted, it is necessary to go up in the column and see the refer number in the column when it is ticked. In this case, it is the number 22, this means that if the field correspondent with the row 22 has got the value “ASME G13B”, the field 17 must be counted. The System Support has created an algorithm able to respect these links so that the number of parameters counted is right and so is the metric based on it.
7. CONCLUSIONS AND RECOMANDATIONS
In this chapter a brief summary of the task has been presented. The inaccuracies found by the candidate have been listed and illustrated with their causes and consequences.
Ultimately, the recommendations suggested by the candidate and the actions undertaken by the company are described in their main points.
At present PII GE Oil&Gas is facing many delays due to this missing critical information, this is causing slippage to the Analysis delivery dates and additional non-production effort being spent by staff all along the ILI process.
The project scope, that the candidate had to cope with, was to create a strategy to proactively secure all the parameters needed prior to analysis task, where they become critical. By having this in place, PII will mitigate the risk of delays or lost of production time, and address any parameter issues or conflicts long before they become critical in the Analysis cycle. The issues that PII is dealing with can be illustrated in the graph in figure 49.
Figure 15 Actors involved in the process
From the research carried out by the candidate some points, on which PII should focus its efforts, have emerged. The opinion of the candidate is that, these inaccuracies all together build a scenario that causes directly and indirectly the delay on gathering the needed information.
The first problem met was that the entire process, of collecting the critical information, is not
Process
External Customer:
Client
Delivery on time and complete
Supplier:
Functions
involved in the ILI
Process
That supply internal PII parameters
Client
with the external parameters. Review of the procedure of supplying the parameters in order to secure all parameters needed prior to each analysis task
Internal Customer:
Analysis Phase
It needs all parameters needed prior to the analysis task to avoid slippage to the Analysis delivery dates and additional non-production effort being spent by Analysis staff
information has to follow going from the client to the Analyst, then going back to the client as final report. The implications of the lack of an exact and established procedure are many and they affect the availability of the parameters on time.
Building the process of collecting the information and going all along it, the candidate has met the following inaccuracies.
• The first contact with the client is formalized by the PQ. This form contained such a big amount of parameters that the client always avoided to fill them all.
• The ComOps, in charge of finding out the missing parameters, makes a big effort to fill them in and usually does not do it entirely.
• The PM spends time waiting for several authorizations from different functions and the lack of coordination between them pills up delays on the work.
• The client is not informed which data PII needs and does not know that his contribute filing in the form is important, first of all, to provide him the better possible service.
• There is not a control procedure along the process that guarantees or alerts about missing parameters but they are find out just at the Analyst stage.
• The data control spends a lot of time to check inconsistent information caused by the non-normalized database.
• If a parameter is missing, or inconsistent with the others source of the same information, the Analyst does not know exactly who to ask it to, or where to look out it for, increasing the delay.
Moreover, during the several interviews with the workers from the Cramlington and others sites, discontent about eDelivery have emerged:
• Duplication of information – malfunction in the data input: some data have to be filled more than once
• Missing Information
• Lack of training – people must be trained on every change to the system
• eDelivery is Not user friendly
The candidate has outlined some recommendations to work out the inaccuracies found. Furthermore, in order to maximize the profits and focus the effort, the Data Control Team Manager has decided to centre the analysis on the Analysis Phase.
Focusing the analysis on the Analysis phase, the candidate has created, for each technology offered by PII a list that illustrates critical parameters, source and owner of them. In particular, it has been very useful, in order to improve the process, to collect all the needed parameters in an
only location, saving the time spent by analyst, looking for the parameters, and facilitating further operations of control about missing parameters.
The Analysis Requirements Report has been completely redesigned by the candidate in order to match the previous aim and to create a document:
• Complete = with all the critical information
• Clear = with a clear meaning for each field
• Trustworthy = with the right value for each field
This document has been adopted as starting point for further improvement of the process.
Another important point to undertake in order to improve the process is adding a control phase that now is totally absent. A control point is really useful not just to understand the entity of the inaccuracy but also, and more important, to make aware workers that a clear ownership, about each field, has been established, and there are consequences for any missing information.
Naturally, before putting in action the control point, a training for each function has been prepared with the following topics:
• Give full visibility about the process, informing workers about what happened in the other function and the path that their work follows before becoming the final product.
• Give a full understanding about the ownership of each information, ensuring that all data entry owners are aware of their role for entering Analysis Parameter data.
• Inform people about the new ARR and how to use it
• Inform workers about the new metrics and how their performances and the PII’s performance will be measured.
In conclusion, the actions undertaken to improve the process have been:
Training – For all the staff to understand the Analysis Requirements, the global process, and about the meanings of the data fields.
Responsibility – a clear responsibility has been assigned to each critical parameter ensuring that all data entry owners are aware of their role for entering Analysis Parameter data.
Action addresses to: functions involved in the Analysis phase
eDelivery Functionality and Modifications – the part of eDelivery involved in the Analysis process has been reviewed, ensuring the right functionality and that all links and automatic updates are working correctly. Moreover, it has been streamlined deleting the unnecessary fields and adding the missing fields to become tightly connected with the
analysts requirements.
Action addresses to: Business Systems, Analysis
Add a Control Phase – A metrics’ system has been Implemented in order to measure the trend of missing parameters and to verify that the modification proposed for Analysis Requirements helps to reduce the number of missing parameters
The next step will be addressed in two main directions:
• Operating on the other functions of the ILI process to solve the problems highlighted in the first phase of this project, carrying out the same analysis but focusing on others point of the process.
• Analyzing in depth the behaviour of each parameter in order to understand the cause of its frequent absence and move in that direction, possibly with the collaboration of the client.