Already a subscriber? 
MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
Security check
Please login to your personal account to use this feature.
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
BS EN 9320:2014 Aerospace series. Programme Management. General guidelines for acquisition and supply of open systems, 2014
- Contents Page
- Foreword
- 1 Scope
- 2 Normative references
- 3 Terms and definitions and abbreviated terms [Go to Page]
- 3.1 Terms and definitions
- 3.2 List of abbreviations
- 4 Acquisition process [Go to Page]
- 4.1 An acquisition strategy is established [Go to Page]
- 4.1.1 Define an openness strategy
- 4.1.2 Define an acquisition strategy
- 4.2 A supplier is selected and the selection justified [Go to Page]
- 4.2.1 Define selection criteria
- 4.2.2 Justify the choice of supplier
- 4.3 Communication with the supplier is maintained
- 4.4 A contract is drawn up [Go to Page]
- 4.4.1 State the acceptance criteria for openness
- 4.4.2 Stipulate the legal conditions
- 4.4.3 Define the means for checking openness characteristics
- 4.5 A product or service conforming to the contract terms is accepted
- 4.6 The contract is closed
- 5 Supply process [Go to Page]
- 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
- 5.4 Ownership is transferred to the client
- 5.5 The contract is closed
- 6 Life cycle model management process [Go to Page]
- 6.1 The strategy and the processes required for managing the life cycle model are defined
- 7 Infrastructure management process
- 8 Budget management process [Go to Page]
- 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 [Go to Page]
- 9.1 The core skills required by the projects are identified
- 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
- 10 Quality management process
- 11 Project planning process [Go to Page]
- 11.1 The project plan is available
- 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
- 13 Decision-making process
- 14 Risk management process [Go to Page]
- 14.1 The scope of risk management is determined
- 14.2 Appropriate risk and opportunity management strategies are defined and implemented
- 14.3 Risks and opportunities are identified as soon as they emerge, managed until a conclusion is reached and funded
- 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 [Go to Page]
- 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
- 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 [Go to Page]
- 16.1 The information to be managed is identified
- 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
- 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 [Go to Page]
- 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.
- 17.3 Assessment activities are identified and planned
- 17.4 The required data is compiled, stored, analysed and the results interpreted
- 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”)
- 18 Requirement establishment and analysis process [Go to Page]
- 18.1 Establishment of stakeholder requirements [Go to Page]
- 18.1.1 Define the requirement
- 18.1.2 Identify the stakeholders
- 18.1.3 Identify the requirements and constraints of the openness
- 18.2 Definition of stakeholder requirements [Go to Page]
- 18.2.1 Establish usage scenarios
- 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
- 18.2.7 Identify the openness characteristics associated with the MMI
- 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
- 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 [Go to Page]
- 18.3.1 Analyse all requirements obtained
- 18.3.2 Select the critical requirements with regard to openness
- 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 [Go to Page]
- 18.4.1 Continue monitoring requirements during the whole life cycle of the system
- 19 Architecture design process [Go to Page]
- 19.1 Describe and model prospective architectures
- 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 [Go to Page]
- 21.1 Establish an integration strategy
- 21.2 Define the design constraints resulting from the integration
- 22 Verification process [Go to Page]
- 22.1 Establish a verification strategy
- 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
- 23 Validation process [Go to Page]
- 23.1 Establish a validation strategy
- 23.2 Define the constraints resulting from validation
- 23.3 Validate the openness characteristics
- 23.4 Identify and correct nonconformities
- 24 Qualification process
- 25 Operating process [Go to Page]
- 25.1 Prepare a strategy for operation
- 25.2 Monitor the level of openness of the system throughout its operating cycle
- 26 Maintenance process
- 27 Withdrawal from service process
- Bibliography [Go to Page]
