Systems Working Group Meeting Kevin MooreChristopher Hall Program ManagerProgram Coordinator

1
Systems Working Group MeetingKevin
Moore Christopher HallProgram Manager Program
Coordinator
2
Preliminaries

• Emergency Procedures
• Group Photograph
• Lunch

3
Agenda - Morning

• Introductions Group
• The ASSC in 2005 Kevin Moore ERA
• Document Review Group

4
Agenda - Afternoon

• MoDs AfAv Strategy Kevin Moore ERA
• ASAAC Avionic API Brian Stevens QinetiQ
• Feedback AOB

5
Introductions

• Name
• Organisation
• Area of Expertise

6
Christopher Hall

• ASSC Coordinator
• Engineer ERA Safety Engineering Group
• Specialising in Military Aircraft
• Previously RA HISE University of York
• MSc Computer Science Dept UoY

7
Welcome to ERA

8
Safety Engineering

• System Safety Engineering and Consultancy
• 18 permanent staff
• Orders 1.9m
• Specialist Services
• independent safety advice and audits
• through-life safety management consultancy
• safety case preparation
• hazard and risk identification
• software assurance
• training

9
Built on a Solid Technical Heritage

• ERA Technology
• A Chelton Group Company(Part of Cobham plc)
• 20m turnover
• 250 staff
• Specialist Engineering Consultancy
• System Safety and Software Assurance
• EMC Modelling, Test and Consultancy
• Mechanical and Electrical Consultancy
• Antenna and Electronic Systems
• World-class Engineers
• 71 with university degrees
• 43 with post-graduate qualifications

10
Cobham Organisation Structure
11
Cobham plc Fiscal 2004

• A global aerospace, avionics and flight
  operations company
• FTSE 125 organisation
• 1.6bn market capitalisation
• 983m turnover
• 146.9m profit
• 1.3bn order book
• gt 9800 employees worldwide
• operating in 5 continents

12
Cobham Revenue Analysis
13
ASSC Overview
14
Setting the Scene

• MoD Declared Aim
• Reduce risk and encourage innovation
• Increase defence industry competitiveness
• Delivering projects within performance, time and
  cost parameters
• MoD Acknowledge
• Standards provide the fundamental building blocks
  in the design, procurement and maintenance of
  defence equipment
• Important element of MoD procurement strategies

15
Setting the Scene

• Avoid 'gold-plated' military equipment
• Greater emphasis on, and willingness to use
  industry and commercial standards
• In preference to military standards
• However must comply legislation and standards
  associated with safety, security and equipment
  clearance
• MoD Acknowledge
• Standardisation programs
• Selection and application of standards
• Require careful consideration at the earliest
  stages of the project life

16
Setting the Scene

• Misuse of standardisation strategies lead to
  procurement issues
• Unacceptable impact on safety, security and the
  environmental
• Limiting interoperability between services
• Reduced quality, reliability and availability
• Continued dependence on specific vendors,
  especially for software support
• Bespoke (difficult to maintain) COTS equipment
• Procurement against undesirable specifications
  (long term)
• Difficulties assessing multiple bids against
  various supplier defined standards

17
ASSC Program

• ASSC Unique UK MoD and Industry Forum
• 3 year extended contract
• Includes Core Management and agreed Tasks
• Core Management
• Steering Group meetings
• Working Group meetings
• Workshops, seminars and tutorials
• Gathering and disseminating information
  pertaining to standards and standardisation
  issues
• ASSC Website

18
ASSC Program

• Agreed Tasks
• Identify issue, requirement, owner and
  deliverable
• Undertake technical investigations,surveys and
  studies
• Developing, maintaining and vetting
• Standards
• Guidance Documents
• Informative reports

19
ASSC Support Structure
20
ASSC Support Structure
Funded for 3 years
Not fully Resourced
21
ASSC and Possible Role
Software
Distributed
Distributed
Systems
Systems
Interfaces
Interfaces
Core
Distributed
Distributed
Distributed
Distributed
Systems
Systems
Systems
Systems
Avionics Systems
Electro
Electro
Magnetic
Magnetic
Effects
Effects
Integrated Weapon
Integrated Weapon
Systems
Systems
22
ASSC and Possible Role
Software Working Group
23
ASSC and Possible Role
Software Working Group
24
ASSC and Possible Role
Software Working Group
25
Task Case Study C Survey and Recommendations
26
C Survey and Recommendations

• Issue
• The use of C for safety and mission critical
  defence applications becoming more prevalent
• Certification (SW Clearance) being carried out on
  a case-by-case basis.
• Requirement
• In order to reduce costs the MoD need to define a
  universal process for suppliers and assessors of
  these systems
• Guidance document to be produced for the
  practitioners of C

27
Agreed C Task

• Phase I
• Identify the C and C keys issues/players/program
  mes
• Especially with regard to safety critical/related
  systems
• Facilitate a forum for key players
• Scope task to produce Best Practice guidance
• In a manner analogous to MISRA's role in the
  development of safety related C
• Phase II
• Produce a Strategy Paper for general review and
  buy-in

28
C Survey

• OO methodologies including programming languages
  on safety and mission critical system development
  and certification
• 5 Working Groups/committees identified
• Sub Committee 22 ISO/IEC JTCI
• proposal for the preparation of generic guidance
  has recently released
• Guidance for Avoiding Vulnerabilities in
  Programming Languages
• Various programming languages including safety
  and security issues
• SC-205/WG-71
• Working groups from RTCA (SC205 Committee
  Software Considerations) and EUROCAE (WG71
  Aeronautical Software)
• Collaboration to produce RTCA DO 178C Software
  Considerations in Airborne Systems and Equipment
  Certification (Ref 9)
• One of the issues being addressed is OO techniques

29
C Survey

• FAA CAST
• CAST provides guidance for the use of OOT in
  avionics systems
• Aim for guidance to contribute to DO 178C.
• MISRA C
• Automotive (based) working group produced the
  MISRA C Guidelines
• International recognized and used standard
• Members (users) expressed interested in producing
  a similar guideline for C
• Initial MISRA/ASSC meeting successful
• Strategy to produce guideline tailored for MoD
  and industry use
• Real-Time for Java Expert Group and the
  J-Consortium
• Involved with the development of a subset of Java
  for real-time high integrity applications.

30
Observations and Feedback
MISRA C Guideline
Java
Sw Maintenance Certification Legacy
Modular Certification
Is C the starting Point?
Supporting Ada
Sub-committee-22
Sw Certification New Build
RTCA DO 178B Amendment
31
C Recommendations

• Provide MoD and Industry Forum
• Provide input into guidance document
  requirements, scope and development via a series
  of workshops
• Early involvement will provide the benefit of
  maximizing MoD and industry buy-in to developed
  guidance
• Monitor and report on progress of guidance
  material development
• Maintain MoD/Industry awareness through regular
  meetings with MoD stakeholders.
• ASSC Support Structure
• Provide a basis for contribution to its
  development
• Disseminate information throughout MoD Integrated
  Project Teams (IPT) and industry via workshops
  and a software web portal
• Provide training in the use of guidance material
• Ensure usability of developed guidance material

32
C Recommendations

• MISRA Partnership
• Determine scope of tasks and timescales in
  relation to C guidance material development
• Determine a strategy for addressing the gaps
  between MISRAs agenda and the MoDs requirements
  to maximize cross-industry participation and
  reduce costs in guidance material development
• Sub Committee-22
• Liaison to determine progress and outputs of
  developed guidance material
• set up a working relationship to enable
  cross-flow of ideas
• RTCA DO-178B Amendment
• Determine if there is scope for providing UK
  input to the development of this update
• Liaise with SC-205/WG-71 to achieve this aim
• Monitor the progress with regards to the
  inclusion of Object Oriented Technology (OOT)

33
Questions or Feedback
34
Task Case Study AfAv Survey and Recommendations
35
Setting the Scene

• John Jones DEC(TA) DTS - AFFORDABLE AVIONICS
  THE MOD STRATEGY
• The following identified as significant risks
• Interface standards are not widely supported.
• Qualification and certification procedures are
  unable to certify or re-certify such
  architectures, or wholesale re-qualification and
  re-certification of the system is required
  following upgrade.
• Lack of overall MOD co-ordination and acceptance
  of common standards.
• The failure to use COTS hardware and software.
• Potential difficulties with the adoption of COTS
  software
• Certification and, importantly, re-certification
  are far from guaranteed
• Evidence to produce a robust safety case, in
  particular for safety or flight critical
  software, may not be available for some
  commercially available software
• Traditional route to certification following
  modification may become unaffordable, even for
  relatively trivial hardware modifications.

36
Agreed AfAv Task

• Issue
• Military avionics are expensive to support and
  upgrade
• Cannot readily employ new technology
• Shrinking research budget and the increasing
  scale of the commercial electronics market
• MOD cannot dominate the electronics market and no
  longer drives technical development
• Military avionics systems are becoming
  prohibitively expensive to procure, adapt and
  support through-life

37
Agreed AfAv Task

• Requirement
• Military customer must change its thinking and
  approach to avionics system procurement and their
  whole life support
• Establish management framework and guidelines to
  promote and assist with the adoption of advanced
  avionics architectures
• Ensure avionics are affordable and receptive to
  technology insertion
• Ensure strategy allows standard hardware and
  software employment in both legacy and future
  weapon systems.

38
Agreed AfAv Task

• Phase 1
• Investigate technical progress and on-going
  actions on the MoD Affordable Avionics program
• Discussion with stakeholders and UK-funded
  project participants
• Access findings against MoD's initial roadmap and
  implementation plan.
• Identify areas where other technical work needs
  to be carried out to achieve more affordable
  avionics
• Consider use of and develop outline for GSN based
  Risk assessment model and management tool.
• Phase II
• Produce a Strategy Paper for general review and
  buy-in

39

• Five main areas for consideration
• AfAv Strategy
• AfAv Requirements
• ASSC Role or alternative?
• AfAv Research
• AfAv Application

AfAv Requires MoD Focus
40
High Level commitment

• Review
• Buy-in
• Endorsement
• Policy?

AfAv Strategy
AfAv Requires MoD Focus
41
High Level commitment

• Review
• Buy-in
• Endorsement
• Policy?

AfAv Strategy
AfAv Reqments
AfAv Requires MoD Focus
Requirement Statement

• Ident
• Define
• Measure

42
High Level commitment
ASSC Role or not?

• Review
• Buy-in
• Endorsement
• Policy?

AfAv Strategy

• Decide
• Define
• Implement

Avionics Champions MoD - Industry
AfAv Reqments
AfAv Requires MoD Focus

• Ident
• Define
• Measure

Reqmt Statement
43
High Level commitment
ASSC Role or not?

• Review
• Buy-in
• Endorsement
• Policy?

AfAv Strategy

• Decide
• Define
• Implement

Avionics Champions MoD - Industry
AfAv Reqments
AfAv Requires MoD Focus

• Ident
• Define
• Measure

Reqmt Statement
Facilitate Connectivity AfAv Grey book

• Status
• Gap Analysis
• Direct?

AfAv Research
44
High Level commitment
ASSC Role or not?

• Review
• Buy-in
• Endorsement
• Policy?

AfAv Strategy

• Decide
• Define
• Implement

Avionics Champions MoD - Industry
AfAv Reqments
AfAv Requires MoD Focus

• Ident
• Define
• Measure

Reqmt Statement
Facilitate Connectivity AfAv Grey book
Communication Web site, library Workshops

• Status
• Gap Analysis
• Direct?

• Identify
• Understand
• Communicate

AfAv Research
AfAv Application
45
High Level commitment
ASSC Role or not?

• Review
• Buy-in
• Endorsement
• Policy?

AfAv Strategy

• Decide
• Define
• Implement

Avionics Champions MoD - Industry
AfAv Reqments
AfAv Requires MoD Focus

• Ident
• Define
• Measure

Reqmt Statement
Facilitate Connectivity AfAv Grey book
Communication Web site, library Workshops

• Status
• Gap Analysis
• Direct?

• Identify
• Understand
• Communicate

AfAv Research
AfAv Application
Develop and maintain 1 Standards 2 Guidelines,
3 Informative Reports
46
High Level commitment
ASSC Role or not?

• Review
• Buy-in
• Endorsement
• Policy?

AfAv Strategy

• Decide
• Define
• Implement

Avionics Champions MoD - Industry
AfAv Reqments

• Ident
• Define
• Measure

Reqmt Statement
Facilitate Connectivity AfAv Grey book
Communication Web site, library Workshops

• Status
• Gap Analysis
• Direct?

Technology Pull-through Demonstrations
AfAv Research

• Identify
• Understand
• Communicate

AfAv Application
Develop and maintain 1 Standards 2 Guidelines,
3 Informative Reports
47
High Level commitment
ASSC Role or not?

• Review
• Buy-in
• Endorsement
• Policy?

AfAv Strategy

• Decide
• Define
• Implement

Avionics Champions MoD - Industry
AfAv Reqments
Stakeholder Analysis
AfAv MoD Focus

• Ident
• Define
• Measure

Reqmt Statement
Facilitate Connectivity AfAv Grey book
Communication Web site, library Workshops

• Status
• Gap Analysis
• Direct?

Technology Pull-through Demonstrations

• Identify
• Understand
• Communicate

AfAv Research
AfAv Application
Develop and maintain 1 Standards 2 Guidelines,
3 Informative Reports
48
MoD AfAv Sponsors

• Equipment Capability Customer
• Squadron Leader Mil MillerDEC (TA)
• Defence Logistics Organisation (DLO)
• Squadron Leader Steve ClappADAS(AIR) Future
  Support Environment
• DSTL
• Steve ColmanDirectorate of Concepts and
  Technology

49
Questions or Feedback