Systems Architecture
Systems Architecture A system is an interacting combination of elements to accomplish a defined objective Presenter: John de Wardt CEng, FIMechE DE WARDT AND COMPANY
Issues with Systems Architecture in Drilling / Completion Operations • Drilling is a complex multi-disciplinary expertise • System Engineering is a well defined métier used in other industries like aerospace, defense and automotive for decades • System thinking role is to capture gains through designing optimal-systems focused on most important customer needs • System Engineering is not Project Management • An optimal Drilling System can´t simply be obtained by combining best-in class tools and products • We need it both in engineering and field operations IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Challenge Team Members • • • •
John de Wardt – DE WARDT AND CO Slim Hbaieb - Schlumberger David Haas – Aerojet Rocketdyne Andy Fawkes – Thinke Co Ltd
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Functional Description • Well construction (drilling and completing oil and gas wells) is a fragmented business • No logical construct
• Well construction is a complex, highly interdependent activity which has not been modeled • It is a significant challenge to develop an architecture
• Systems architecture is the foundation of the development of drilling systems automation • Aerospace, DOD, automobiles, … IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Performance Targets • 3,000 ft (920 m/day) per day overall spud to TD repeatable wells with smooth wellbore (low tortuosity / rugosity), full integrity • Long reach horizontal wells • Consistent and repeatable
• 1,500 ft per day (460 m/day) exploration wells with full data acquisition
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Current Situation There is no systems architecture in well construction
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
What is Systems Architecture • A system is defined as a set of different elements so connected or related as to perform a unique function not performable by the elements alone. • The term 'architecture' is widely understood and used for what it is--a top-down description of the structure of the system International Council on Systems Engineering – INCOSE Systems Engineering Body of Knowledge - SEBoK IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Systems Architecture Model Top down Systems sub-systems Components Components cross sub-systems
Source: INCOSE IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Systems of Systems Architecture Example
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Multiple use of “Architecture” • The software architecture of a program or computing system is the structure or structures of the system which comprise: • Software components, • The externally visible properties of these components • And the relationships among them.
• Technical architecture (IT) is the formal description of an information technology system organized in a way that supports reasoning about the structural properties of the system IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Vee Model of Systems Engineering Stakeholder Requirements Concept Validation
Concept of Operations
Field Delivery Commissioning
System Validation
Architecture Description
Production, FAT Gate
Requirement Validation
Qualification & Certification Complete
System Level Requirements Gate
Requirement Validation
Sub-System HW/SW Requirements
Integrated Functional Verification Gate
Requirement Validation
Component HW/SW Specifications
Sub-System Functional Verification
Development Risk Reduction
Design Validation
Hardware Verification
Software Verification
Gate
Version courtesy of Aerojet Rocketdyne
Proto-Qual Unit Beta Software Production
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Stakeholder Requirements Concept Validation
Concept of Operations
Production, FAT Gate
Drilling System
System Level Requirements
Gate Requirement Validation
System Validation
Systems Architecture
Architecture Description
Requirement Validation
Field Delivery Commissioning
Sub-System HW/SW Requirements
Qualification & Certification Complete
Excavation System
Integrated Functional Verification
Gate Requirement Validation
Component HW/SW Specifications
Drill Bit
Development Risk Reduction
Design Validation
Sub-System Functional Verification
Hardware Verification
Software Verification
Gate Proto-Qual Unit Beta Software Production
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Problem Statement
barriers, needs, critical success factors
• Barriers • As an industry we struggle to think in systems • It could become a revolution
• Needs • System definition is fundamental to automation
• Critical success factors • Very few of us are familiar with this approach
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Hoisting System
Power Gen System
Drill String System
Hydraulics System
BHA System
DP System
Well Uplift Assembly System
Well Inflow Assembly System
Well Integrity System
How can systems architecture present itself?
Rotating System
Fluids System
Data Acquisition System
Drive this value
Steering System
Excavation System
Deliver Customer Value
Interaction of these interdependent systems are critical to success
Definitions we know are important • Drilling State • Knowing where “we” are is fundamental • Knowing what “we” are doing is fundamental
• Use cases • What “we” intend to do is fundamental • A list of steps to achieve a goal • Consequently who is controlling it
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Drilling State examples • Drilling State • Knowing where “we” are is fundamental • Knowing what “we” are doing is fundamental
• Use cases • What “we” intend to do is fundamental • A list of steps to achieve a goal • Consequently who is controlling it
Source: Bertrand du Castel, The Drillers Brain Source: Patent 2005 Noble Drilling / ProNova IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Way Ahead • Systems thinking will create an architecture that delivers stakeholder requirements • Issue is how will the industry perceive it and accept it
• Drilling State and Use Cases are critical • Do we inherently understand them? • Should we define standards to enable interoperability?
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Issues with Systems Architecture in Drilling / Completion Operations • Drilling is a complex multi-disciplinary expertise • System Engineering is a well defined métier used in other industries like aerospace, defense and automotive for decades • System thinking role is to capture gains through designing optimal-systems focused on most important customer needs • System Engineering is not Project Management • An optimal Drilling System can´t simply be obtained by combining best-in class tools and products • We need it both in engineering and field operations IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Challenge Team Members • • • •
John de Wardt – DE WARDT AND CO Slim Hbaieb - Schlumberger David Haas – Aerojet Rocketdyne Andy Fawkes – Thinke Co Ltd
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Functional Description • Well construction (drilling and completing oil and gas wells) is a fragmented business • No logical construct
• Well construction is a complex, highly interdependent activity which has not been modeled • It is a significant challenge to develop an architecture
• Systems architecture is the foundation of the development of drilling systems automation • Aerospace, DOD, automobiles, … IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Performance Targets • 3,000 ft (920 m/day) per day overall spud to TD repeatable wells with smooth wellbore (low tortuosity / rugosity), full integrity • Long reach horizontal wells • Consistent and repeatable
• 1,500 ft per day (460 m/day) exploration wells with full data acquisition
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Current Situation There is no systems architecture in well construction
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
What is Systems Architecture • A system is defined as a set of different elements so connected or related as to perform a unique function not performable by the elements alone. • The term 'architecture' is widely understood and used for what it is--a top-down description of the structure of the system International Council on Systems Engineering – INCOSE Systems Engineering Body of Knowledge - SEBoK IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Systems Architecture Model Top down Systems sub-systems Components Components cross sub-systems
Source: INCOSE IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Systems of Systems Architecture Example
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Multiple use of “Architecture” • The software architecture of a program or computing system is the structure or structures of the system which comprise: • Software components, • The externally visible properties of these components • And the relationships among them.
• Technical architecture (IT) is the formal description of an information technology system organized in a way that supports reasoning about the structural properties of the system IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Vee Model of Systems Engineering Stakeholder Requirements Concept Validation
Concept of Operations
Field Delivery Commissioning
System Validation
Architecture Description
Production, FAT Gate
Requirement Validation
Qualification & Certification Complete
System Level Requirements Gate
Requirement Validation
Sub-System HW/SW Requirements
Integrated Functional Verification Gate
Requirement Validation
Component HW/SW Specifications
Sub-System Functional Verification
Development Risk Reduction
Design Validation
Hardware Verification
Software Verification
Gate
Version courtesy of Aerojet Rocketdyne
Proto-Qual Unit Beta Software Production
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Stakeholder Requirements Concept Validation
Concept of Operations
Production, FAT Gate
Drilling System
System Level Requirements
Gate Requirement Validation
System Validation
Systems Architecture
Architecture Description
Requirement Validation
Field Delivery Commissioning
Sub-System HW/SW Requirements
Qualification & Certification Complete
Excavation System
Integrated Functional Verification
Gate Requirement Validation
Component HW/SW Specifications
Drill Bit
Development Risk Reduction
Design Validation
Sub-System Functional Verification
Hardware Verification
Software Verification
Gate Proto-Qual Unit Beta Software Production
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Problem Statement
barriers, needs, critical success factors
• Barriers • As an industry we struggle to think in systems • It could become a revolution
• Needs • System definition is fundamental to automation
• Critical success factors • Very few of us are familiar with this approach
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Hoisting System
Power Gen System
Drill String System
Hydraulics System
BHA System
DP System
Well Uplift Assembly System
Well Inflow Assembly System
Well Integrity System
How can systems architecture present itself?
Rotating System
Fluids System
Data Acquisition System
Drive this value
Steering System
Excavation System
Deliver Customer Value
Interaction of these interdependent systems are critical to success
Definitions we know are important • Drilling State • Knowing where “we” are is fundamental • Knowing what “we” are doing is fundamental
• Use cases • What “we” intend to do is fundamental • A list of steps to achieve a goal • Consequently who is controlling it
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Drilling State examples • Drilling State • Knowing where “we” are is fundamental • Knowing what “we” are doing is fundamental
• Use cases • What “we” intend to do is fundamental • A list of steps to achieve a goal • Consequently who is controlling it
Source: Bertrand du Castel, The Drillers Brain Source: Patent 2005 Noble Drilling / ProNova IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
Way Ahead • Systems thinking will create an architecture that delivers stakeholder requirements • Issue is how will the industry perceive it and accept it
• Drilling State and Use Cases are critical • Do we inherently understand them? • Should we define standards to enable interoperability?
IADC ART Workshop Vienna June 2014 Systems Architecture Presenter: John de Wardt
