Shopping Cart

No products in the cart.

BS EN 9320:2014

$189.07

Aerospace series. Programme Management. General guidelines for acquisition and supply of open systems

Published By Publication Date Number of Pages
BSI 2014 48
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

These general guidelines cover the open system acquisition and supply processes.

There is an increasing requirement for systems designed and produced by industry, particularly in the aeronautic, space and defence fields, to be used with other systems designed, produced, acquired and operated independently.

The concept of open systems is touched upon in many systems engineering documents. This document deals specifically with this subject. To this end, through the various processes applied, it provides information to stakeholders (buyers, suppliers, designers, subcontractors, supervisors, etc.) on the best practice to be adopted.

The specific nature of openness for a system is defined by all the following properties:

  • Interchangeability,

  • Interoperability,

  • Upgradability,

  • Reusability,

  • Reversibility,

  • Flexibility,

  • Affordability.

These properties are defined in the glossary for these general guidelines.

These general guidelines are largely based on the structure and system life cycle processes described in standard ISO/IEC 15288:2008.

The characteristics of openness also relate to:

  • The products or services offered by the company (target systems resulting from use of company processes).

  • The company’s processes (project systems). Several stakeholders, with their own assignments, cultures, jobs and geographical locations, different working methods, modelling frameworks, standards, tools and aids, etc. are involved in the activities, which are sometimes multidisciplinary, of the internal and external processes of a company. These diverse elements are not necessarily all suited to working together without causing certain risks, a loss of autonomy, effectiveness and/or efficiency, etc. A company must, for example, develop its ability and capacity in terms of interoperability both internally (between the systems of which it is made) and externally (with other partners), including, by way of an example:

  • Ability of each stakeholder and each department involved to maintain efficient and trusting relationships with other stakeholders, taking into account deadline, cost and quality objectives,

  • Ability to exchange, communicate and use the necessary flows (data, information, knowledge, materials, energy) autonomously, without error and dynamically throughout the life cycle of the target system,

  • Ability to coordinate, synchronise and manage common tasks and share and use resources (human, machine or application) and services efficiently and appropriately.

PDF Catalog

PDF Pages PDF Title
4 Contents Page
5 Foreword
6 1 Scope
7 2 Normative references
3 Terms and definitions and abbreviated terms
3.1 Terms and definitions
10 3.2 List of abbreviations
4 Acquisition process
4.1 An acquisition strategy is established
4.1.1 Define an openness strategy
11 4.1.2 Define an acquisition strategy
4.2 A supplier is selected and the selection justified
4.2.1 Define selection criteria
4.2.2 Justify the choice of supplier
12 4.3 Communication with the supplier is maintained
4.4 A contract is drawn up
4.4.1 State the acceptance criteria for openness
4.4.2 Stipulate the legal conditions
13 4.4.3 Define the means for checking openness characteristics
4.5 A product or service conforming to the contract terms is accepted
14 4.6 The contract is closed
5 Supply process
5.1 A buyer or a market for a product/service is identified and a proposal made
5.2 A contract is drawn up and communication maintained
5.3 A product or service conforming to the contract terms is provided
15 5.4 Ownership is transferred to the client
5.5 The contract is closed
6 Life cycle model management process
6.1 The strategy and the processes required for managing the life cycle model are defined
7 Infrastructure management process
16 8 Budget management process
8.1 The opportunities, investments or requirements of the investment plan are defined, prioritised and selected
8.2 Resources and budgets are identified and allocated for each project
9 Resource management process
9.1 The core skills required by the projects are identified
17 9.2 The necessary human resources are provided for the projects
9.3 Staff core skills are developed, maintained or enhanced
9.4 Conflicts in multi-project resource demands are resolved
9.5 Individual knowledge, information and core skills are pooled, shared, reused and improved throughout the organisation
18 10 Quality management process
11 Project planning process
11.1 The project plan is available
19 11.2 Stakeholders, responsibilities and authorities are identified
11.3 The resources and services required for project completion are formally requested
12 Project control and assessment process
20 13 Decision-making process
14 Risk management process
14.1 The scope of risk management is determined
21 14.2 Appropriate risk and opportunity management strategies are defined and implemented
22 14.3 Risks and opportunities are identified as soon as they emerge, managed until a conclusion is reached and funded
23 14.4 Risks and opportunities are analysed and their priority (for allocation of resources) is determined
14.5 Risk management/opportunity exploitation measures are defined, implemented and evaluated to determine changes in the risk/opportunity status and the progress of activities to deal with them
14.6 The appropriate action is taken to integrate the opportunity into the project
15 Configuration management process
24 15.1 A configuration management strategy is defined
15.2 Define a configuration management strategy
15.3 The items requiring configuration management are defined
15.4 Configuration references are established
25 15.5 The configuration of configuration items is managed
15.6 The status of configuration items is available throughout the life cycle
16 Information management process
16.1 The information to be managed is identified
26 16.2 Information formalism is defined
16.3 Information is modified to suit requirements
16.4 Information is kept available
16.5 Information is up-to-date, complete and valid
27 16.6 Information is made available to the designated parties
16.7 Information is made available to the designated parties whenever changes are made
17 Measuring process
17.1 Information requirements for the technical and management processes are identified
17.2 An appropriate set of assessment measurements, based on information requirements, is identified and/or developed.
28 17.3 Assessment activities are identified and planned
17.4 The required data is compiled, stored, analysed and the results interpreted
29 17.5 Information products are used to uphold decisions and provide an objective basis for communication
17.6 The measuring process and the measurements are evaluated
17.7 Improvements are communicated to measuring process managers
17.8 Appendix: ATAM (“Method for Architecture Evaluation”)
30 18 Requirement establishment and analysis process
18.1 Establishment of stakeholder requirements
18.1.1 Define the requirement
31 18.1.2 Identify the stakeholders
18.1.3 Identify the requirements and constraints of the openness
18.2 Definition of stakeholder requirements
18.2.1 Establish usage scenarios
32 18.2.2 Characterise the operational flows and list the interfaces of the target system
18.2.3 Characterise the interfaces and define the openness requirements for the interfaces
18.2.4 Highlight the services that the system must provide
18.2.5 Define the functions that the system must carry out
18.2.6 Define the requirements that may restrict architectural choices
34 18.2.7 Identify the openness characteristics associated with the MMI
35 18.2.8 Define the requirements which have inevitable consequences for contracts and technical or project decisions
18.2.9 Formulate the Manufacturing, Integration and Transition requirements specific to the openness
18.2.10 Formulate Verification and Validation requirements
36 18.2.11 Prepare the information to be provided with regard to the operational openness requirement in the various documents at the beginning of the design phase
18.3 Analysis of stakeholder requirements
18.3.1 Analyse all requirements obtained
18.3.2 Select the critical requirements with regard to openness
37 18.3.3 Validate the specification of requirements with the stakeholders
18.3.4 Trace the requirements in a way appropriate to management of requirements
18.4 Requirement monitoring throughout the system life cycle
18.4.1 Continue monitoring requirements during the whole life cycle of the system
19 Architecture design process
38 19.1 Describe and model prospective architectures
39 19.2 Define, document and manage the architectures, mainly the interfaces, of the system
19.3 Compare the prospective architectures and select the one that best meets the requirement and the openness criteria
19.4 Check and validate the openness characteristics of the architecture and certify the interfaces
20 Execution process
21 Integration process
40 21.1 Establish an integration strategy
21.2 Define the design constraints resulting from the integration
22 Verification process
22.1 Establish a verification strategy
41 22.2 Define the design constraints so the system can be verified
22.3 Check the openness characteristics
22.4 Identify and correct non-conformities
42 23 Validation process
23.1 Establish a validation strategy
23.2 Define the constraints resulting from validation
23.3 Validate the openness characteristics
43 23.4 Identify and correct nonconformities
24 Qualification process
25 Operating process
25.1 Prepare a strategy for operation
44 25.2 Monitor the level of openness of the system throughout its operating cycle
45 26 Maintenance process
27 Withdrawal from service process
46 Bibliography
BS EN 9320:2014
$189.07