PLC Multilin Remote Bridge Sensors RTDS Panel/PC Controller - - PowerPoint PPT Presentation

plc multilin
SMART_READER_LITE
LIVE PREVIEW

PLC Multilin Remote Bridge Sensors RTDS Panel/PC Controller - - PowerPoint PPT Presentation

PLC Multilin Remote Bridge Sensors RTDS Panel/PC Controller Controller Panel/PC Cables and Terminations L-3 L-3 Siem Siemens GE GE Stewart & Stevenson Stewart & Stev enson Initial High Rig Risk Risk Launch Kongsberg


slide-1
SLIDE 1
slide-2
SLIDE 2

Sensors

RTDS

Multilin

Controller

PLC

Controller Remote

Panel/PC Bridge

Panel/PC Stewart & Stev Stewart & Stevenson enson GE GE

Siem Siemens

L-3 L-3

Cables and Terminations

slide-3
SLIDE 3
slide-4
SLIDE 4
slide-5
SLIDE 5

Kongsberg DP/VMS/PMS NOV VICIS Drilling Package ABB Power Control Engine Control Systems Rig Launch Initial Risk High Risk Low Risk Caution Risk High Risk

The above is an example of a rig with vendor software that has dependencies on other vendor versions and products to operate. When a vendor de-supports a product, risk can be beyond the specific vendor product or it can have integrations that depend on a specific technology such as DDE dependant on the operating systems. In the above scenario, we would make recommendations to the client regarding upgrades and half life planning as appropriate.

slide-6
SLIDE 6

 Example of a systems lifecycle, the

  • pportunity here is to align all systems that

integrate to highlight risk considerations.

slide-7
SLIDE 7

Requirements Review Validation of Setups and Configurations Integration Testing User Acceptance Testing Validation of Architecture SCM Baseline INFOSEC SCM Audit FMECA/FMEA MRO System Assessments Vendor Acceptance/Testin g

slide-8
SLIDE 8
slide-9
SLIDE 9

The objective of this phase is to define the scope of the project, the needs and constraints it should fulfill, and to establish the preliminary design of the system. It should identify the main ISDS (Integrated Software Dependent System) Elements which will be assembled in the system. This is also a setup phase, where project organization should be defined, as well as the planning

  • f the development. At the beginning of this phase the

Confidence Level shall be defined

Less unplanned issues at startup and delays

  • Insight into long term stability and supportability based on software

engineering standards

  • Confirmation of systems compliance mandates and philosophy, for

instance alarms, interlocks etc.

  • Failure modes identified in systems design
  • Confirms systems lifecycle
slide-10
SLIDE 10

During In this phase, the detailed design of the system is established, and suppliers are involved to setup the development of each subcontracted ISDS Element of the system. Contracts are established with suppliers and detailed design of each ISDS Element is performed.

  • Time to establish a chain of information relative to

system versions, software controls, documentation of systems, testing results, integration etc.

  • Meeting with system developers, and observing their

internal quality process, we can establish expectation for future reliability issues, make recommendations to mitigate risk and make constructive recommendations to help establish a better delivered product.

slide-11
SLIDE 11

 During the construction and installation

phase, the systems team will be able to confirm:

  • Wire and cable installation to standards – using

cable verification and test tools all or select links can be tested.

  • Capture initial setups and software versions
  • Note any inconsistencies between design and as

delivered configurations

  • Note any risk to system operating as designed
slide-12
SLIDE 12

 Technical teams typically provide the following

“value add” during the acceptance phase:

  • Testing validation and witness
  • Confirmation of final alarm mapping to cause
  • Software configuration and documentation of final

versions

  • Review of NVM backup of critical PLC code
  • FMECA and focused testing review of safety related

systems

  • Review of version changes that could impact testing
  • bjectives
slide-13
SLIDE 13

 Continued refinement of process as well as

risk management are the core objectives

  • SCM – Software configuration management, audit of

prior SCM engagements for governance of practice

  • INFOSEC audit and assessment
  • FMEA/incident investigation – on going
  • Systems lifecycle planning- Evaluating risk relative

to systems lifecycles and assessing optimum time for upgrade activities

  • ISM compliance of safety systems
slide-14
SLIDE 14

Problem Problem TA TAC Resolut C Resolution

  • n

During rig acceptance from the shipyard, initial configurations

  • f systems were expedited to meet aggressive date
  • commitments. The systems were configured to base line

settings and values without coordination with other integrated systems vendors. During sea trials, it was observed that thruster power was limited and operation was unstable. It was resolved that the power control systems were never properly configured and restricted performance of thrusters Acceptance test planning, vendor management of

  • configurations. SCM.

During rig acceptance, a number of transient anomalies in the drilling systems was impeding success. Rig and Vendor specialists were involved for several days troubleshooting issues. A recommendation of cable verification and certification uncovered several bad fiber terminations, crimped strands and incorrect wire-maps on copper RJ45 terminations. A operator with several sister rigs engaged a vendor to make minor changes on one of the rigs drilling systems, the vendor assumed that the rig baseline configuration was the same as a sister ship and proceeded to attempt consolidating changes to this rig as well. When the vendor completed his activity, the rig floor began experiencing anomalies of unknown source. The vendor realized he had over written the configurations of prior vendor changes and lost the baseline reference version. A recovery was finally done by re-programming all the changes again manually and retesting. The rig was out of operation for several hours and risked several more days of down time if the baseline could not be recovered. A recommendation to establish formality of SCM – software change management was done. Procedures and processes for software change were developed for the rig operation and vendors were included in the initiative to insure compliance

slide-15
SLIDE 15

Maintenance Data Sources

Engineering Design and Reliability OpenO&M Services Operational, Control, IADC, EHS, Quality, & CBM OpenO&M Services Maintenance Strategy, Plans and Actuals OpenO&M Services

CM/PM/CBM Completed Hard Failure Histories PM/CBM Backlog Software Updates

I BM I LOG/ I I F System s-Based Rig Prognostic Health Managem ent Portal

Remove / Replace Ops I OM-OG Maintenance Str ategy Editor & What-I f System Maint. Pre-plans

Best - of- Breed Equipm ent Condit ion Monit oring & Diagnost ic Syst em s

Monitored Data Sources

Rig Captain Toolpusher Com pany Man Driller

Drilling Op. Control Log

Engineering Data Sources (Rig-Specific Subset)

Top Drive Motor Data IADC Logs / KPIs

Best-of-Breed Maintenance Managem ent System s

Best-of-Br eed Contr ol, EHS, & Quality System s BOP Op. Control Log FMECA / RBI / HAZOP Studies OEM Product Datasheets Platform & Rig Design Drawings Actionable Events and Data, PM/CBM Backlog and Current O&M Schedules Best-of-Br eed Document Managem ent System , Engineer ing/ PDM Design, & Reliability System s All Accessible Data & Events System Condition Data & Prognostic Health Events

Comprehensive Systems-Based Rig Data Monitoring Architecture

IOM-OG ISO15926-MIMOSA Transform Engine

I OM-OG OpenO&M Data I ntegration Registry System OpenO&M Services

Shore

IOM On-shore Data Center(s) Bulk Data Transferred As Bandwidth Permits Actionable Event Data Transferred Immediately

I BM I LOG/ I I F System s-Based Rig Prognostic & Health Monitoring Portal OpenO&M Services I OM-OG OpenO&M Data I ntegration Registry System

Chief Risk Officer Rig Manager ( on-shore) I OM-OG EHS Com pliance Engineer I OM-OG PHM / Risk Analyst

IOM Op. Data Black Boxes

IOM Maint. Event Log Black Box IOM PHM Events Black Box Mud & BOP HPU Pump Data BOP & Drilling Control UPS Data

Top Drive BOP Mud Pump

Bulk O&M from IOM Black Boxes

Best - of- Breed I nt elligent Analyt ics & O&M Scheduling Syst em

OpenO&M Services

Supply Chain Extra-Net

slide-16
SLIDE 16

Maintenance Data Sources

Engineering Design and Reliability OpenO&M Services Operational, Control, IADC, EHS, Quality, & CBM OpenO&M Services Maintenance Strategy, Plans and Actuals OpenO&M Services

CM/PM/CBM Completed Hard Failure Histories PM/CBM Backlog Software Updates

I BM I LOG/ I I F System s-Based Rig Prognostic Health Managem ent Portal

Remove / Replace Ops I OM-OG Maintenance Str ategy Editor & What-I f System Maint. Pre-plans

Best - of- Breed Equipm ent Condit ion Monit oring & Diagnost ic Syst em s

Monitored Data Sources

Rig Captain Toolpusher Com pany Man Driller

Drilling Op. Control Log

Engineering Data Sources (Rig-Specific Subset)

Top Drive Motor Data IADC Logs / KPIs

Best-of-Breed Maintenance Managem ent System s

Best-of-Br eed Contr ol, EHS, & Quality System s BOP Op. Control Log FMECA / RBI / HAZOP Studies OEM Product Datasheets Platform & Rig Design Drawings Actionable Events and Data, PM/CBM Backlog and Current O&M Schedules Best-of-Br eed Document Managem ent System , Engineer ing/ PDM Design, & Reliability System s All Accessible Data & Events System Condition Data & Prognostic Health Events

Comprehensive Systems-Based Rig Data Monitoring Architecture

IOM-OG ISO15926-MIMOSA Transform Engine

I OM-OG OpenO&M Data I ntegration Registry System OpenO&M Services

Shore

IOM On-shore Data Center(s) Bulk Data Transferred As Bandwidth Permits Actionable Event Data Transferred Immediately

I BM I LOG/ I I F System s-Based Rig Prognostic & Health Monitoring Portal OpenO&M Services I OM-OG OpenO&M Data I ntegration Registry System

Chief Risk Officer Rig Manager ( on-shore) I OM-OG EHS Com pliance Engineer I OM-OG PHM / Risk Analyst

IOM Op. Data Black Boxes

IOM Maint. Event Log Black Box IOM PHM Events Black Box Mud & BOP HPU Pump Data BOP & Drilling Control UPS Data

Top Drive BOP Mud Pump

Bulk O&M from IOM Black Boxes

Best - of- Breed I nt elligent Analyt ics & O&M Scheduling Syst em

OpenO&M Services

Supply Chain Extra-Net FMECA PDFs, Hazop Studies PDFs, OEM Product Model Datasheet PDFs, O&M Maintenance Manual PDFs (Document Mgmt. System) Mapping Keys Between Various Systems, MIMOSA Taxonomies, Rig Segment Topology, OEM Model Design Spec. Data, & Synchronized Serialized Assets with Subset of Spec. Data WBS linked to Document Mgmt. System and Maintenance , Maintenance PM Schedules, Overdue PM Task Events, Actual Work Done with Cost & Time, Remove/Replace Operations, Serialized Assets, Maint. KPI’s (Focused on BOP, Top Drive, & Mud Pump) Drilling Control System Op. Logs (RigSense), IADC Logs / KPIs (RIMDrill / Daily Reporting), BOP Control, BOP UPS, Drilling Control System UPS Portal Displays of Key Information & Provides mud pump and liner wear as-designed/as-is analysis, BOP hydraulic power unit (HPU) pump fluid flow as- designed/as-is analysis, Top drive VFD motor as- designed/as-is analysis On-rig black box data captures with a safe & secure data transport and storage system using an information service bus to

  • n-shore data center(s).

The bus immediately transfers actionable

  • events. High-volume data

transferred as bandwidth permits. Intelligent analytics with

  • ptimized

O&M scheduling

slide-17
SLIDE 17
slide-18
SLIDE 18
slide-19
SLIDE 19
slide-20
SLIDE 20

Software Update Request Change Management Process Software Update Approval Software Update Create Image or Backup Updated Software Image or Backup Files on Portable Media Update Backup Server

Backup Repository

  • n Server

Image or Backup Files Image or Backup Files from Repository Update Auxiliary Backup

DVDs or Other Media

Closed Item

Firmware Modules

Notice of Completion

Broadband Transmission Onshore

End End

Image or Backup Files