Presentation is loading. Please wait.

Presentation is loading. Please wait.

FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Standard Systems Engineering in the Business Environment Stuart Arnold QinetiQ Fort.

Similar presentations


Presentation on theme: "FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Standard Systems Engineering in the Business Environment Stuart Arnold QinetiQ Fort."— Presentation transcript:

1 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Standard Systems Engineering in the Business Environment Stuart Arnold QinetiQ Fort Halstead Sevenoaks Kent TN14 7BP

2 A Thought…

3 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold z Definition 1……….. z Definition 2……….. z ……….. Standard

4 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold z ……….. zA device or emblem used as a rallying point in times of conflict or battle Standard

5 A Changing View of Systems Engineering

6 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold In the early 90s new views of systems engineering were emerging - driven largely by the business environment and international trade A reassessment of Systems Engineering was occurring exactly what it is, why we do it, how we do it who does it when do we do it ….. ……and can we all agree on it ?

7 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering - Everyone has their own model Systems Engineering Product Service System

8 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Increasing business challenge in systems zAdditional complexity in systems –multiple technologies –multiple contributing enterprises Coordinated cooperation zMore capability + less budget –Need for international customers –Need for international supplier collaborations International trade

9 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold The changing systems engineering paradigm zDe-emphasis of systems engineers in development making all the system decisions - we all do systems engineering. zLife cycle thinking - dont throw problems and costs over the wall. zSimplistic sequence gives way to more realistic life cycle representations - linearity maps into hierarchy zEnterprises, projects and technologies influence a systems architecture. zLife cycle management - synonymous with risk management. zCooperation between contributors - softening the traditional boundaries of multiple trading enterprises.

10 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering – A Key Component of the Organizations Business Management System zISO (trade and commerce) and IEC (technical integrity and safety) recognised that a shift in the definition of business processes was occuring – setting systems engineering in terms of both technical and management actions. z Organisations needed a common, internationally-endorsed approach to their management of system complexity. zISO and IEC jointly decided to act as the forum for the international definition and codification of systems engineering. zIn the foreseeable future, the approaches defined in this International Standard are expected to be an aspect of standard business practice.

11 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering – A Key Component of the Organizations Business Management System ISO/IEC International Standard to: zCodify a widely accepted model for international cooperative action zDesignate common concepts for clarity of international communication zEstablish common understanding to underpin agreement and consent zPermit actions and responsibilities to be cited in formal or informal acquirer/supplier transactions zSupport the determination of organisational capability zContribute to a framework for developing individual competence

12 Process Descriptions of Systems Engineering

13 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering - Everyone has their own model Systems Engineering Product Service System

14 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold People (in organizations) act on systems by performing processes throughout the life cycle. Process is the most effective basis for a common model Product Service System Process

15 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Mil-std Mil-Std- 499A 1974 Mil-Std- 499B 1994 EIA IS IEEE P DoD solutions halted, US favour civil standards Early codification of systems engineering zEmphasis of systems engineers in development making all the system decisions. zSimplistic sequence describes system lifetime zLimited life cycle thinking threw problems and costs over the wall zDefence/aerospace view zBig acquirer/big supplier perspective zUS culture view

16 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering A Brief History of Systems Engineering Process Standards Mil-std- 499 Software Engineering 1969 Mil-Std- 499A 1974 Mil-Std- 499B 1994 EIA /IS ISO IEEE P DoD solutions halted, US favour civil standards Standard for Application and Management of the Systems Engineering Process Process for Engineering a System Systems Engineering System Life Cycle Processes ISO Life Cycle Management Software Life Cycle Processes DERA Systems Engineering Reference Model 1997 ESA PS-05 Software Engineering Standard 1993

17 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering A Brief History of Systems Engineering Process Standards Mil-std- 499 Software Engineering 1969 Mil-Std- 499A 1974 Mil-Std- 499B 1994 EIA /IS EIA ISO IEEE P IEEE ISO Amd DoD solutions halted, US favour civil standards Standard for Application and Management of the Systems Engineering Process Process for Engineering a System Systems Engineering System Life Cycle Processes ISO Life Cycle Management Software Life Cycle Processes Life Cycle Management Software Life Cycle Processes DERA Systems Engineering Reference Model 1997 ESA PS-05 Software Engineering Standard

18 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering A Brief History of Systems Engineering Process Standards Mil-std- 499 Software Engineering 1969 Mil-Std- 499A 1974 Mil-Std- 499B 1994 EIA /IS EIA ISO/IEC IEEE P IEEE ISO/IEC Amd DoD solutions halted, US favour civil standards Standard for Application and Management of the Systems Engineering Process Process for Engineering a System Systems Engineering System Life Cycle Processes ISO/IEC Life Cycle Management Software Life Cycle Processes Life Cycle Management Software Life Cycle Processes DERA Systems Engineering Reference Model 1996 ESA PS-05 Software Engineering Standard X EIA 632 IEEE 1220 ISO/IEC X

19 A Challenging Journey

20 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Active ISO/IEC participants zAustralia zBrazil zCanada zChina zCzech Republic zDenmark zFrance zGermany zIsrael zItaly zJapan zKorea zNorway zRussia zSweden zSpain zUK zUSA Up to 40 around the table Final cost $9.5M zINCOSE

21 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold ISO/IEC Milestones zJun 94: ISO Study Group on software-system relationship zMar 95: USA New Work Item proposal zApr 96: ISO/IEC JTC1 approval of the project zMay 96: Work started zJuly 99: CD 1(766 comments) zFeb 00: CD 2 (1450 comments) zNov 00: CD 2 rev (300 comments) zMay 01: CD 3 (680 comments) zNov 01: FCD (274 Comments) zJan 02: FDIS zJune 02: Unanimous ratification of International Standard zNov 02: Publication

22 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Keep in mind zISO/IEC only a model, like any model it has problems of representing the complexity of reality and has limits to its range of validity. zIt is a top-level model that will need to be supported by detail in other standards. zReviewers and users all want to see themselves in the model ISO/IEC zMost people come to preconditioned by models in other systems engineering standards. zIt is not intended to be a idealized model; it has to be used in practice. zISO/IEC is therefore a workable compromise.

23 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Also keep in mind zISO/IEC is principally implemented using language –linear sequence of words - trying to capture an iterative, recursive, dynamic reality –most of the good words have been used in other models with different meaning - misconceptions –unambiguous translation into French, Russian and also Spanish, Japanese, Swedish, Portuguese etc. introduces constraints - zGraphical/schematic representations may be rich but they imply notations and conventions which have to be interpreted. zIn varying detail, the users of ISO/IEC are all functions in the organisation – one story, many actors, many discipline-specific terms.

24 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold And a few more challenges? zIt was a requirement that it can be cited in contract. zMany concepts were muddled in preceding standards (Verification and Validation, Process and Life Cycle Stage, Products and Services, Systems and Components, Iteration and Recursion) zThe decision to write a Guide (ISO Technical Report) was made half way through. zIt was a requirement that it could be used for maturity assessment. zSize matters!

25 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Were we successful? zPublished Nov 2002 zLinks to implementation technology standards zLinks to assessment standards From a business perspective it…..

26 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Business Outcomes of Complying with ISO/IEC z Provides a tailorable, multi-domain, system-driven profile of business processes. z Can be applied bi-laterally, contributes to consistency across a trading boundary; applied multi-laterally, contributes to supply chains. z Lets customer satisfaction drive technology opportunities and the supplier chain. z Influences inter-and intra-organisational accountability and structure. z Defines system-oriented managerial outcomes that are directed toward customer satisfaction. z Builds the essential relationship between product creation and the provision and management of services. z Assists development of a service (capability)-driven culture

27 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold

28 Application in the Defence Industry Acquisition Management System ISO/IEC is the basis of UK MODs Acquisition Policy and Process Framework

29 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Application in the Rail Industry z From the EPT Final Report During the development phase [of ERTMS] a robust System Engineering Process and Quality Management System will be required. The scope of this work would include the production and approval of necessary processes, procedures and standards based on ISO/IEC and CENELEC EN 50126, and the achievement of ISO 9000 certification. z From the EPT Year 1 Progress Report 2003 …the EPT has established a Quality Management System. It is based on IEC but has been focused on the specific needs of the programme. It concentrates on staff competencies, configuration management, change control, document review and requirement management, and is underpinned by a programme of internal audits….

30 Establishing the Business Context

31 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Project Managers Business Managers Specialist Engineers Enterprise Processes Project Processes Implementation Technology Processes Mind The Gap

32 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Project Managers Business Managers Specialist Engineers Enterprise Processes Project Processes Implementation Technology Processes Same Gap – Multiple Views Project View of Systems Implementation Discipline View of Systems Described in Project Management Practices /Body of Knowledge Described in Discipline Standards/Practices e.g. Software Practices, Human Centred Practices

33 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineers Project Managers Business Managers Specialist Engineers Enterprise Processes Project Processes System Technical Processes Implementation Technology Processes A Common, Profiled View Set in a Management Context

34 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Context for Systems Engineering SOCIAL ENVIRONMENT ENTERPRISE ENVIRONMENT PROJECT ENVIRONMENT SYSTEMS ENGINEERING DOMAIN IMPLEMENTATION TECHNOLOGY ENVIRONMENT

35 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Organization ENTERPRISE PROCESSES PROJECT PROCESSES TECHNICAL PROCESSES enterprise management project management technical management Organisational Structure enterprise that part of an organization with responsibility to acquire and to supply products and/or services according to agreements NOTEAn organization may be involved in several enterprises and an enterprise may involve one or more organizations.

36 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold AGREEMENT PROCESSES Organization A Organization C ENTERPRISE PROCESSES PROJECT PROCESSES TECHNICAL PROCESSES enterprise management project management technical management ENTERPRISE PROCESSES PROJECT PROCESSES TECHNICAL PROCESSES enterprise management project management technical management Organisational trading agreement the mutual acknowledgement of terms and conditions under which a working relationship is conducted acquirer the stakeholder that acquires or procures a product or service from a supplier NOTE Other terms commonly used for an acquirer are buyer, customer, purchaser. The acquirer may at the same time be the owner, user or operating organization. supplier an organization or an individual that enters into an agreement with the acquirer for the supply of a product or service

37 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold AGREEMENT PROCESSES Organization A Organization B Organization C AGREEMENT PROCESSES ENTERPRISE PROCESSES PROJECT PROCESSES TECHNICAL PROCESSES enterprise management project management technical management ENTERPRISE PROCESSES PROJECT PROCESSES TECHNICAL PROCESSES enterprise management project management technical management ENTERPRISE PROCESSES PROJECT PROCESSES TECHNICAL PROCESSES enterprise management project management technical management Organisational trading Acquirer/supplier chains

38 Structure, Architecture, Hierarchy and Recursion

39 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Aircraft System Defining a System system a combination of interacting elements organized to achieve one or more stated purposes NOTE 1A system may be considered as a product or as the services it provides. NOTE 2In practice, the interpretation of its meaning is frequently clarified by the use of an associative noun, e.g. aircraft system. Alternatively the word system may be substituted simply by a context dependent synonym, e.g. aircraft, though this may then obscure a system principles perspective.

40 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System element System element System element is completely composed of A system a set of interacting system elements System Composition system a combination of interacting elements organized to achieve one or more stated purposes NOTE 1A system may be considered as a product or as the services it provides. NOTE 2In practice, the interpretation of its meaning is frequently clarified by the use of an associative noun, e.g. aircraft system. Alternatively the word system may be substituted simply by a context dependent synonym, e.g. aircraft, though this may then obscure a system principles perspective.

41 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Aircraft System Airframe system Propulsion system Air Crew Life support system Flight control system Navigation system Global positioning receiver system Display system Navigation System Recursion gives us Hierarchy

42 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Air traffic control system Air Transport System Fuel distribution system Airport system Ticketing system Ground Transportation System Maritime Transport System Aircraft System Airframe system Propulsion system Air Crew Life support system Flight control system Navigation system Global positioning receiver system Display system Navigation System Recursion gives us Hierarchy

43 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Establishing Ones Bearings in Recursion PRODUCT SUBASSEMBLY PART ASSEMBLY 1:N 1:N X Real world - absolute SYSTEM -OF-INTEREST SYSTEM SYSTEM ELEMENT SYSTEM 1:N X 1:N Abstract - absolute SYSTEM 1:N Abstract - relative

44 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System element System- of-interest System element System element System element Architecture Assists the Management of Complexity system-of-interest the system whose life cycle is under consideration in the context of this International Standard

45 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System element System- of-interest System element System element System element System element System element System element System element System element System element Architecture Assists the Management of Complexity system element a member of a set of elements that constitutes a system NOTEA system element is a discrete part of a system that can be implemented to fulfil specified requirements

46 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System element System- of-interest System element System element System element System element System element System element System element System element System element System element System element System element System element System element System element System element Architecture Assists the Management of Complexity

47 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System element System- of-interest System element System element System element System element System element System element System element System element System element System element System element System element System element System element System element System element System element System element System element System element System element Architecture Assists the Management of Complexity

48 Project Focus

49 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System-of -interest System System element Project (Subordinate) Project 1:many Is responsible for Is responsible for System 1:many Acquisition Supply ISO/IEC 15288s Project Centred View project an endeavour with defined start and finish dates undertaken to create a product or service in accordance with specified resources and requirements NOTE 1Adapted from ISO 9000: 2000 and the PMBOK Guide(2000). NOTE 2A project may be viewed as a unique process comprising co-ordinated and controlled activities and may be composed of activities from the Project Processes and Technical Processes defined in this International Standard..

50 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering is Conducted in Projects Project Planning Process Project Assessment Process Project Control Process Decision-making Process Risk Management Process Configuration Management Process Agreement Processes Information Management Process Enterprise ProcessesTechnical Processes Project Processes

51 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold And Project Are Created by Enterprise Management in Organisations Project Planning Process Project Assessment Process Project Control Process Decision-making Process Risk Management Process Configuration Management Process Agreement Processes Acquisition Process Supply Process Information Management Process Enterprise Environment Management Process Investment Management Process System Life Cycle Management Process Resource Management Process Quality Management Process Enterprise Processes Technical Processes Project Processes

52 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold And Project Execute Technical Processes to Create Products and Deliver Services

53 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System Creation Local requirements & constraints Requirements analysis Requirements analysis Requirements analysis Architectural design Architectural design Architectural design Integrated system Integrated subsystem Integration & verification Integrated subsystem Reporting, metrics & management control Reporting, metrics & management control Supplied subsystems Local requirements & constraints Proposed characteristics Verification Derived requirements Proposed characteristics Derived requirements Supplied subsystems VerificationIntegration

54 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System Creation Local requirements & constraints Stakeholder requirements definition Requirements analysis Requirements analysis Requirements analysis Architectural design Architectural design Architectural design Integrated system Integrated subsystem Integration & verification Validation Operational capability Integrated subsystem Reporting, metrics & management control Reporting, metrics & management control Supplied subsystems Reporting, metrics & management control Local requirements & constraints Proposed characteristics Verification Derived requirements Proposed characteristics Derived requirements Proposed characteristics Supplied subsystems Supplied system Transition VerificationIntegration

55 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System element verificatio n System Creation Local requirements & constraints Stakeholder requirements definition Requirements analysis Requirements analysis Requirements analysis Architectural design Architectural design Architectural design Integrated system Integrated subsystem System element requirements System element design System element fabrication System Element Integration & verification Validation Operational capability Integrated subsystem Reporting, metrics & management control Reporting, metrics & management control Reporting, metrics & Management control Supplied subsystems Supplied components Reporting, metrics & management control Local requirements & constraints Proposed characteristics Verification a1 Derived requirements Proposed characteristics Derived requirements Proposed characteristics Proposed characteristics Derived requirements Supplied subsystems Supplied system Transition VerificationIntegration Process Concurrency

56 Implementation Technologies

57 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Mechanical Engineering Human Factors Electronic Engineering …. Software Engineering Engineering across the Organisation Implementation Technologies

58 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Mechanical Engineering Human Factors Electronic Engineering …. Software Engineering Implementation Technologies Systems Engineering Engineering across the Organisation

59 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold x8 SOI User requirements definition SOI Installation Operational System Proposed characteristics Software element implementation System Elements Delivered components Integrated system Allocated requirements Proposed characteristics Derived requirements Proposed characteristics Supplied subsystems Proposed characteristics Integrated Elements Supplied subsystems Engineering at an implementation -independent level of abstraction Engineering at an implementation technology level Derived requirements System Requirement s Definition System Architectural Design System Integration System Verificatio n SOI Validation Software Requirement s Definition Software Detailed Design Software Integration Software Verificatio n

60 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Business Process Profile of ISO/IEC Enterprise Processes Project Processes System Technical Processes Implementation Technology Processes Systems Engineers Project Managers Business Managers Specialist Engineers

61 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Characteristically Different System Element Implementation Media

62 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Humans and Systems Operators System-of-interest operator an individual who, or an organization that, contributes to the functionality of a system and draws on knowledge, skills and procedures to contribute the function NOTE 1The role of operator and the role of user may be vested, simultaneously or sequentially, in the same individual or organization. NOTE 2 An individual operator combined with knowledge, skills and procedures may be considered as an element of the system.

63 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Operators Operators are not stakeholders Stakeholders stakeholder a party having a right, share or claim in a system or in its possession of characteristics that meet that partys needs and expectations

64 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Role rather than person

65 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Humans and Systems Systems in operational environment System-of-interest Users (& stakeholders) Operators user individual who or group that benefits from a system during its utilization NOTEThe role of user and the role of operator may be vested, simultaneously or sequentially, in the same individual or organization.

66 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Humans and Systems Systems in operational environment System-of-interest Users (& stakeholders) Stakeholders Society Operators

67 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System-of-interest Interactions throughout the Life Cycle Systems in operational environment Enabling systems Production systemMaintenance system System-of-interest

68 Stages through the Life Cycle

69 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System Life Cycle Stages Functional Views System Life Cycle Processes People (in organizations) act on systems by performing common processes throughout the life cycle life cycle model a framework of processes and activities concerned with the life cycle, which also acts as a common reference for communication and understanding

70 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold A Hierarchy of Processes Process Stage Life cycle Activity 1:n Generic Patterns Unique t 2 -t 1 large instantaneous

71 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Needs, Concepts, Feasibility Engineering, Solutions, Practicability Fabrication, Assembly, Verification Operation, Usage, Validation Reuse, Archiving, Destruction Installation, Maintenance, Logistics LIFE CYCLE STAGES ORGANIZATIONAL FUNCTIONS Contribute to Personnel CONCEIVERS DEVELOPERS PRODUCERS USERS SUPPORTERS RETIRERS Whole life thinking from each contributing function DEVELOPMENT PRODUCTION UTILIZATION SUPPORT RETIREMENT CONCEPTION

72 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Needs, Concepts, Feasibility Engineering, Solutions, Practicability Fabrication, Assembly, Verification Operation, Usage, Validation Reuse, Archiving, Destruction Installation, Maintenance, Logistics ORGANIZATIONAL FUNCTIONS Contribute to Personnel DEVELOPMENT PRODUCTIONUTILIZATIONSUPPORTRETIREMENT CONCEIVERS DEVELOPERS PRODUCERS USERS SUPPORTERS RETIRERS CONCEPTION Integrated Project Teams DEVELOPMENT LIFE CYCLE STAGE

73 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Compatibility, Feasibility Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Consistency, Viability Needs, Concepts, Feasibility Engineering, Solutions, Practicability Fabrication, Assembly, Verification Operation, Usage, Validation Reuse, Archiving, Destruction Installation, Maintenance, Logistics LIFE CYCLE STAGES ORGANIZATIONAL FUNCTIONS Contribute to Personnel DEVELOPMENT PRODUCTIONUTILIZATIONSUPPORTRETIREMENT CONCEIVERS DEVELOPERS PRODUCERS USERS SUPPORTERS RETIRERS CONCEPTION A Matrix of Responsibilities

74 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System Life Cycle Stages LIFE CYCLE STAGES PURPOSE DECISION GATES CONCEPT Identify stakeholders needs Explore concepts Propose viable solutions DEVELOPMENT Refine system requirements Create solution description Build system Verify and validate system PRODUCTION Mass produce system Inspect and test UTILIZATION Operate system to satisfy users needs SUPPORT Provide sustained system capability RETIREMENT Store, archive or dispose the system Execute next stage Continue this stage Go to previous stage Hold project activity Terminate project Decision Options: CONCEPT UK MOD Smart Acquisition Stages ASSESSMENT DEMONSTRATION MANUFACTURE IN-SERVICE DISPOSAL DoD Phases CONCEPT REFINEMENT TECHNOLOGY DEVELOPMENT SYSTEM DEVELOPMENT & DEMONSTRATION PRODUCTION & DEPLOYMENT OPERATIONS & SUPPORT stage a period within the life cycle of a system that relates to the state of the system description or the system itself NOTE 1Stages relate to major progress and achievement milestones of the system through its life cycle. NOTE 2 Stages may be overlapping.

75 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System Life Cycle Stages LIFE CYCLE STAGES PURPOSE DECISION GATES CONCEPT Identify stakeholders needs Explore concepts Propose viable solutions DEVELOPMENT Refine system requirements Create solution description Build system Verify and validate system PRODUCTION Mass produce system Inspect and test UTILIZATION Operate system to satisfy users needs SUPPORT Provide sustained system capability RETIREMENT Store, archive or dispose the system Execute next stage Continue this stage Go to previous stage Hold project activity Terminate project Decision Options: CONCEPT UK MOD Smart Acquisition Stages ASSESSMENT DEMONSTRATION MANUFACTURE IN-SERVICE DISPOSAL DoD Phases CONCEPT REFINEMENT TECHNOLOGY DEVELOPMENT SYSTEM DEVELOPMENT & DEMONSTRATION PRODUCTION & DEPLOYMENT OPERATIONS & SUPPORT

76 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold System of Interest Enabling System C System A in Operational Environment System B in Operational Environment System C in Operational Environment Enabling System B Enabling System A Interaction with systems comprising the operational environment Interaction with enabling systems enabling system a system that complements a system-of-interest during its life cycle stages but does not necessarily contribute directly to its function during operation NOTE 1For example, when a system-of-interest enters the production stage, an enabling production system is required. NOTE 2Each enabling system has a life cycle of its own. This International Standard is applicable to each enabling system when, in its own right, it is treated as a system-of-interest.

77 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Production Utilization Support RetirementDevelopment System-of-Interest NEED FOR SERVICES FROM A SYSTEM-OF-INTEREST NEED FOR SERVICES FROM A SYSTEM-OF-INTEREST SERVICES TO ITS OPERATIONAL ENVIRONMENT SYSTEM-OF-INTEREST SERVICES TO ITS OPERATIONAL ENVIRONMENT Concept Enabling Systems through the Life Cycle

78 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Production Utilization Support RetirementDevelopment System-of-Interest Production Utilization Support RetirementDevelopmentConcept Concept System The Enabling System services delivered to the System-of-Interest The System-of-Interest requirements for enabling services NEED FOR SERVICES FROM A SYSTEM-OF-INTEREST NEED FOR SERVICES FROM A SYSTEM-OF-INTEREST SERVICES TO ITS OPERATIONAL ENVIRONMENT SYSTEM-OF-INTEREST SERVICES TO ITS OPERATIONAL ENVIRONMENT Concept Enabling Systems through the Life Cycle

79 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Production Utilization Support RetirementDevelopment System-of-Interest Production Utilization Support RetirementDevelopmentConcept Concept System Production Utilization Support RetirementDevelopment Concept Development System The Enabling System services delivered to the System-of-Interest The System-of-Interest requirements for enabling services NEED FOR SERVICES FROM A SYSTEM-OF-INTEREST NEED FOR SERVICES FROM A SYSTEM-OF-INTEREST SERVICES TO ITS OPERATIONAL ENVIRONMENT SYSTEM-OF-INTEREST SERVICES TO ITS OPERATIONAL ENVIRONMENT Concept Enabling Systems through the Life Cycle

80 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Production Utilization Support RetirementDevelopment Concept Support System Production Utilization Support RetirementDevelopment System-of-Interest Production Utilization Support RetirementDevelopmentConcept Concept System Production Utilization Support RetirementDevelopment Concept Development System Production Utilization Support RetirementDevelopment Concept Production System Production Utilization Support RetirementDevelopment Concept Retirement System The Enabling System services delivered to the System-of-Interest The System-of-Interest requirements for enabling services NEED FOR SERVICES FROM A SYSTEM-OF-INTEREST NEED FOR SERVICES FROM A SYSTEM-OF-INTEREST SERVICES TO ITS OPERATIONAL ENVIRONMENT SYSTEM-OF-INTEREST SERVICES TO ITS OPERATIONAL ENVIRONMENT Concept Enabling Systems through the Life Cycle

81 The Next Steps

82 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Processes are essential; alone, they are not sufficient z Processes are essential but not a Recipe Competence and Capability z Processes need to be practiced –by competent professionals –in a compatible environment of methods and tools –operating within appropriate organisational resource and responsibility structures Business Processes Organizational Capability Professional Competence Business Excellence

83 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Standardising Systems Engineering Capability zAn influence on organizations systems engineering policies, practices and procedures zA driver for process implementation - method, tools, resources zBasis for measurement and continuous improvement zYardstick for performance evaluation of an organization, zEstablishes a common approach for determining supplier acceptability

84 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering A Simplified History of Capability Assessment Software Engineering EIA/IS 731 ISO TR15504 EIA ISO Systems Engineering Capability Process for Engineering a System System Life Cycle Processes SW CMM CMMI EIA /IS ISO

85 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold ISO/IEC15504 Process Assessment A structured approach to software process assessment for use by, or on behalf of an organization, with the objective of: –understanding the state of its own processes for process improvement; –determining the suitability of its own processes for a particular requirement or class of requirements; –determining the suitability of another organization's processes for a particular contract or class of contracts.

86 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Process Maturity Processes Capability Levels 1 - Performed Informally 4 - Quantitatively Controlled 2 - Planned and Tracked 3 - Well Defined 5 - Continuously Improving

87 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold ISO 18152

88 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Standardising Systems Engineering Competence zEncourage Proficiency and Professionalism zEstablish performance criteria, permitting demonstration of competence zImply codes of professional conduct and approach zPrescribe social responsibilities, e.g. safety, environment zProfile training and education schemes zLead toward norms of attainment and qualification zCareer development decisions

89 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering ability of an individual (or group) draws on four principal constituents zAptitude - inherent qualities of the individual zKnowledge - information gathered from others by the individual zExperience - direct personal participation by the individual zSkills - learned practical execution by the individual HUMANS Systems Engineering Competence System Life Cycle PROCESSES ABILITY To Perform Develop

90 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Systems Engineering Competence System Life Cycle PROCESSES ABILITYHUMANSSYSTEMS METHODS TOOLS SKILLS KNOWLEDGE APTITUDE EXPERIENCE To Perform To Act on Develop Learn Possess Interpreted to provide Automate Build up Train to Acquire Facilitate Evolves Enables Make practical Structure Leverage

91 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Attainment Enterprise Processes Project Processes System Technical Processes Implementation Technology Processes Knowledge AptitudeExperience Skill System Life Cycle Processes Basic Understanding Competent Advice Professional Guidance Recognized Authority Working Knowledge Basic Elements of a Systems Engineering Competence Framework

92 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Enterprise Processes Project Processes System Technical Processes Implementation Technology Processes PMBOK/ Association of Project Managers Body of Knowledge BCS Professional Development Scheme Levels of attainment A Better Structure for Future Competence IEE/INCOSE Industry Basic Understanding Competent Advice Professional Guidance Recognized Authority Working Knowledge

93 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Individuals development of competence profile focus, attainment levels and career progression Attainment Infrastructure Development Project Monitoring Stakeholders Requirements Definition Human Factors Integration Enterprise Processes Project Processes System Technical Processes Implementation Technology Processes System Life Cycle Processes Basic Understanding Competent Advice Professional Guidance Recognized Authority Working Knowledge System Installation Profile focus Attainment level Career direction

94 FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Thank You & Questions Stuart Arnold QinetiQ Fort Halstead Sevenoaks Kent TN14 7BP


Download ppt "FINSE, Finish Chapter of INCOSE, 26 th May 2005, Helsinki, S.Arnold Standard Systems Engineering in the Business Environment Stuart Arnold QinetiQ Fort."

Similar presentations


Ads by Google