Chapter 12.8
Airborne Software and Data Management
|
Table of contents Paragraph |
|
1.4 4Associated publications3.. 1
2 Policy on airborne software and data management
3 Management of software prior to introduction to service
4 In-service software support functions
5.2 Integrated Logistic Support Manager (ILSM) responsibilities
Historically, aircraft system functionality has been enabled by hardware. However, modern aircraft and/or equipment have become more software-intensive as software provides the functionality formerly performed by hardware. The impact of this is that airborne systems include larger and more complex software products and this trend will continue in the future. Hence, software support is an essential aspect of the support for any system that contains software and controls are needed to manage aircraft software systems development and modification in order to preserve airworthiness and minimize production and through-life costs.
1 Software – The set of computer programs, procedures and associated documentation and data (BS ISO/IEC 12207).
2 Software Support – The activities concerned with supporting the operation of software, and sustaining the ability of software to satisfy the required system performance and functionality during its operational life.
3 Data – Representation of information in a manner suitable for communication, interpretation or processing by computers. Data may take the form of static information (for example, configuration of a set point or a representation of geographical information) or it may take the form of instructions to specify a series of pre-existing functions.
4 User – An individual or organization that uses the operational system to perform a specific function (BS ISO/IEC 12207).
This chapter is applicable to all software and data used on aircraft and/or equipment that may affect an aircraft’s Release To Service (RTS).
1 Def Stan 00-56 - Safety Management Requirements for Defence Systems.
2 Def Stan 05-57 - Configuration Management of Defence Materiel.
3 ISO 9001-2000 - Quality Management System - Requirements.
4 JSP 440 - The Defence Manual of Security.
5 JSP 553 - Military Airworthiness Regulations.
6 JSP 886 Vol 7 Pt 2 - Integrated Logistic Support Manual.
7 MAE BP 1201 - Equipment Safety Management.
8 TickIT Guide - Software Quality Systems Construction and Certification.
2 Policy on airborne software and data management
The Release To Service Authority (RTSA), in conjunction with the Integrated Project Team Leader (IPTL), is to ensure that changes to software are implemented following the same principles as for hardware changes; in particular that all changes are implemented as a 4Design3 Modification (DM) or Service Modification (SM) and Service Deviation (SD) if appropriate.
The user, IPT staff, contractors or 4Design Organisation3 may initiate changes to the aircraft and/or system software.
Software changes are to be progressed through the aircraft Software Configuration Management Board (SCMB) for inclusion in a subsequent issue of the relevant software program and referred to the RTSA for Generic Aircraft Release Process/Military Aircraft Release/RTS amendment.
3 Management of software prior to introduction to service
The MOD must act as an intelligent customer throughout the Concept, Assessment, Demonstration, Manufacture, In-service and Disposal (CADMID) or the Concept, Assessment, Demonstration, 4Migration3, In-service and Termination (CADMIT) lifecycle. To do this, the MOD must maintain a level of expertise sufficient to evaluate user and management-driven software issues and assess their operational benefits, risks and costs.
User (operational) and other requirements are to be stated in the User Requirements Document and System Requirements Document respectively; these may be determined using Logistic Support Analysis (LSA), as detailed in 4JSP 886 Vol 7 Pt 3,3 during the Concept and Assessment lifecycle phases.
Based on the results of LSA and/or other relevant analysis, a 4Support Policy Statement (SPS)3 is to be produced by the Integrated Logistic Support Manager (ILSM) in accordance with the MOD ILS Manual, Section 00.01.10 4and the Chapter 5.14 series. This SPS is to include any required software support, detailed either within the SPS or in a separate Software Support Policy Statement (SSPS) where such support is complex.3
4 In-service software support functions
Following the introduction to service of the aircraft and/or equipment, the aircraft or equipment IPT is to maintain the 4SPS/SSPS3 to ensure that it reflects the status of the aircraft and/or system software support. Typical software support functions 4are detailed within JSP 886 Vol 7 Pt 4.3
The IPT is responsible for ensuring that the software and data is managed throughout the CADMID/CADMIT lifecycle.
5.2 Integrated Logistic Support Manager (ILSM) responsibilities
The ILSM is responsible for ensuring that:
1 LSA is carried out on the aircraft and/or equipment.
2 Based on the results of LSA, an 4SPS3 is produced in accordance with the MOD ILS Manual, Section 00.01.10 4and Chapter 5.143.
This chapter refers to the following publications and websites:
1 MOD Integrated Logistic Support.
2 4BS ISO/IEC 12207 - Information Technology, Software Life Cycle Processes.3