Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization...
-
Upload
emilee-ganter -
Category
Documents
-
view
234 -
download
0
Transcript of Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization...
![Page 1: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/1.jpg)
Presented to:
By:
Date:
Federal AviationAdministrationFLS & UMS
Software Standardization Conference
Dennis Wallace, Software Technical Specialist
July 2005
![Page 2: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/2.jpg)
Federal AviationAdministration
2FLS & UMSJuly 2005
Order 8110.49
• Approval of Field-Loadable Software (FLS)
• Approval of FLS by Finding Identically through the Parts Manufacturer Approval (PMA) Process
• Approval of Airborne Systems and Equipment Containing User-Modifiable Software (UMS)
![Page 3: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/3.jpg)
Federal AviationAdministration
3FLS & UMSJuly 2005
DO-178B References to FLS
• Field-Loadable Software (FLS) and Loading References:- System Design: Sections 2.0 and 2.5- SW Process: 6.4.3a., 7.2.1d., e.; 7.2.8, 8.3g.- SW Data: 11.1g., 11.2c.(3), 11.4b.(8), (9); 11.10g., 11.11, 11.15, 11.16, 11.20g.
![Page 4: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/4.jpg)
Federal AviationAdministration
4FLS & UMSJuly 2005
Definitions
Field- Software that can be loaded without Loadable removal of the equipment from the Softwareaircraft installation.
User- Software intended for modification Modifiable by the airplane operator without review Softwareby the certification authority, air framer,
or equipment manufacturer.
Option- Software that contains approved and Selectable validated components that may be Softwareactivated by the user.
![Page 5: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/5.jpg)
Federal AviationAdministration
5FLS & UMSJuly 2005
Examples
• Field-Loadable Software– Engine Control Software– Flight Control Software– Boeing 777 Has Many Systems With
FLS
• User-Modifiable Software– Non-Required, Airline-Specific
Electronic Checklists
• Option-Selectable Software– Selection Of Sensors For An FMS
![Page 6: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/6.jpg)
Federal AviationAdministration
6FLS & UMSJuly 2005
Approval of FLS
3
Considerations
Changing
Loading
Developing
![Page 7: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/7.jpg)
Federal AviationAdministration
7FLS & UMSJuly 2005
Approval of FLS Developing
Considers 178B Paragraph 2.5
Verify SW on Target HW
Meets 178B Objectives
Configuration Management
Considering Redundant Parts
![Page 8: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/8.jpg)
Federal AviationAdministration
8FLS & UMSJuly 2005
Approval of FLS Loading
Data Integrity
Check?
Consider loading systemduring SW verif.
Approve onboardloading system.
Verify SW part number onboard the aircraft.
Y
![Page 9: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/9.jpg)
Federal AviationAdministration
9FLS & UMSJuly 2005
Approval of FLSChanging
Is FLS also UMS?
Change Impact Analysis
Use guidelines for UMS
Y
![Page 10: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/10.jpg)
Federal AviationAdministration
10FLS & UMSJuly 2005
Installation of FLS
Documentation to Include the Following Items:a) Aircraft and HW Applicabilityb) Verification Proceduresc) Post Load Verification and/or Proceduresd) Actions for Unsuccessful Loade) Reference to Approved Loading Proceduresf) Maintenance Record Entry Proceduresg) Reference to AFM, AFMS, or Ops Manual
![Page 11: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/11.jpg)
Federal AviationAdministration
11FLS & UMSJuly 2005
Maintenance & Part Marking of FLS
• Maintenance Procedure in Aircraft Maintenance Manual
• Procedure to Include Reading of SW Version
• Procedure to Include Part Number in Maintenance Records
• Changes Reflected in Appropriate Manual or Logbook
![Page 12: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/12.jpg)
Federal AviationAdministration
12FLS & UMSJuly 2005
Maintenance & Part Marking of FLS
HW P/N:
SW P/N:
LRU P/N:
Procedure to Verify SW Load
Procedure to Verify Nameplate & SW Load
![Page 13: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/13.jpg)
Federal AviationAdministration
13FLS & UMSJuly 2005
Parts Manufacturer Approval of Field-loadable Software
![Page 14: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/14.jpg)
Federal AviationAdministration
14FLS & UMSJuly 2005
Purpose
• Provides Guidelines for Approving FLS Through PMA
• Limited to Identicality With or Without a Licensing Agreement
• Does Not Cover Test and Computation
![Page 15: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/15.jpg)
Federal AviationAdministration
15FLS & UMSJuly 2005
Technical Information
• FLS Is Beneficial to Airlines and Applicants
• Order 8110.42, “PMA Procedures,” Does Not Specifically Address Software
• CFRs 21.301, 303, and 305 Do Not Specifically Address Software
• Data Being Loaded Is Approved, Not Media
![Page 16: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/16.jpg)
Federal AviationAdministration
16FLS & UMSJuly 2005
Procedures
• Follow Part 21 and O8110.42 in Conjunction With the Software-Specific Procedures in O8110.49
Part 2
1
O81
10.4
2
O81
10.4
9
![Page 17: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/17.jpg)
Federal AviationAdministration
17FLS & UMSJuly 2005
Procedures
Design Approval w/ Licensing Agreement
Design Change w/ Licensing Agreement
Design Approval w/o
Licensing Agreement
Design Changew/o Licensing
Agreement
1 2
3
4
![Page 18: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/18.jpg)
Federal AviationAdministration
18FLS & UMSJuly 2005
Design ApprovalIdenticality With Licensing Agreement
• Reference O8110.42, 8(a)(3)(a)• FLS Should Be Approved Through TC, STC,
ATC • FLS Should Be Installed Via Service Bulletin
Or Similar Means• Configuration Management Process Should
Be In Place To Assure Software Part Number, Hardware Part Number, Aircraft Series, etc. Are Accurate
![Page 19: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/19.jpg)
Federal AviationAdministration
19FLS & UMSJuly 2005
Design Change Identicality With Licensing Agreement
• Reference O8110.42, 8(h)(5)• Applicant Should Coordinate Change
With TC, STC, ATC Holder • Change Impact Analysis• Determine Minor/Major Classification
– Major change O8110.42 8(h)(5)(a)– Minor change O8110.42 8(h)(5)
![Page 20: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/20.jpg)
Federal AviationAdministration
20FLS & UMSJuly 2005
Design Approval Identicality W/o Licensing Agreement
• Order 8110.42, 8(a)(3)(b) - Parts Must Be Identical In “All Respects”
• FLS Should Be Identical To The Software On The TC, STC, ATC Approval– Bit-by-bit Comparison– Evidence of Identical Type Design Data - DO-
178B Section 9.4
![Page 21: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/21.jpg)
Federal AviationAdministration
21FLS & UMSJuly 2005
Design Change Identicality w/o Licensing Agreement
• Change Considered Major
• Reference Order 8110.42, 8(h)(5)(a)
![Page 22: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/22.jpg)
Federal AviationAdministration
22FLS & UMSJuly 2005
Summary• Chapter 5 - Approval of FLS
• Chapter 6 – Approval of FLS by Finding Identicality through PMA
• Reference DO-178B, Part 21, and Order 8110.42
![Page 23: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/23.jpg)
Federal AviationAdministration
23FLS & UMSJuly 2005
Approval of Airborne Systems and Equipment Containing User-modifiable Software
![Page 24: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/24.jpg)
Federal AviationAdministration
24FLS & UMSJuly 2005
Purpose
• To Provide Guidelines To ACO Engineers and DERs For Approval of Systems With User-Modifiable Software (UMS)
• To Encourage Working With Flight Standards Personnel:– Maintenance Inspectors, Avionics
Inspectors, and Operations Inspectors
![Page 25: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/25.jpg)
Federal AviationAdministration
25FLS & UMSJuly 2005
DO-178B References to UMS
• User-Modifiable Software (UMS) References:- System Design: Sections 2.0 and 2.4a.- d.
- SW Process: 5.2.3, 7.2.2b.
- SW Data: 11.1g., 11.10g., 11.20g.
![Page 26: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/26.jpg)
Federal AviationAdministration
26FLS & UMSJuly 2005
Corruption of Non-modifiable, Safety-related Software
Change Control Problems in the Field
Compelling but Invalid Information in the Cockpit
Technical Information
Biggest Concerns:
![Page 27: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/27.jpg)
Federal AviationAdministration
27FLS & UMSJuly 2005
Definitions User- Software intended for modification Modifiable by the airplane operator without review Software by the certification authority, airframer,
or equipment manufacturer.
Option- Software that contains approved and Selectable validated components that may be Software activated by the user.
Field- Software that can be loaded without Loadable removal of the equipment from the Software aircraft installation.
![Page 28: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/28.jpg)
Federal AviationAdministration
28FLS & UMSJuly 2005
Definitions
FLS
UMS OSS
![Page 29: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/29.jpg)
Federal AviationAdministration
29FLS & UMSJuly 2005
• What About Navigation or Terrain Databases?
• What About Programmable Waypoints or Other Programmable Database-Like Items?
Databases, etc?
![Page 30: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/30.jpg)
Federal AviationAdministration
30FLS & UMSJuly 2005
![Page 31: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/31.jpg)
Federal AviationAdministration
31FLS & UMSJuly 2005
Earlier Versions of DO-178 Contain No Guidance for User-Modifiable Software
Use DO-178B Guidance for The User-Modifiable Portions
Earlier Version of DO-178 (Section 6)
![Page 32: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/32.jpg)
Federal AviationAdministration
32FLS & UMSJuly 2005
• Once Certified as UMS There is No Certification Authority Oversight
Safety Considerations
![Page 33: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/33.jpg)
Federal AviationAdministration
33FLS & UMSJuly 2005
Modifications Should Have No Effect On
Safety Considerations
SafetyMargins
OperationalCapability
CrewWorkload
Non-Modifiable
Components
ProtectiveMechanisms
SoftwareBoundaries
![Page 34: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/34.jpg)
Federal AviationAdministration
34FLS & UMSJuly 2005
Effects Must Be Bounded
Safety Considerations
![Page 35: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/35.jpg)
Federal AviationAdministration
35FLS & UMSJuly 2005
• Obvious or Explicit Indication That the Data is Not Cert Authority Approved
Identification of Displayed Data
![Page 36: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/36.jpg)
Federal AviationAdministration
36FLS & UMSJuly 2005
Performance Parameters
• Modifications to Provide or Revise Performance Parameters Requires Certification Authority Review and Approval
• Examples of Parameters– Safety margins– Operational capabilities– Crew workload
![Page 37: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/37.jpg)
Federal AviationAdministration
37FLS & UMSJuly 2005
Performance Parameters
• Modifications to Provide or Revise Performance Parameters Requires Certification Authority Review and Approval
• Examples of Parameters– Safety margins– Operational capabilities– Crew workload
![Page 38: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/38.jpg)
Federal AviationAdministration
38FLS & UMSJuly 2005
Protection
• UMS Components Shouldn’t Affect Non-UMS Components
• Assure Protection Is Developed to at Least Same Level of Robustness Required of the Most Robust Non-UMS Component
![Page 39: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/39.jpg)
Federal AviationAdministration
39FLS & UMSJuly 2005
Two Considerations Operating In:
• Protection in the design and operation
Changing Out:• Protection during
modification
Protection
![Page 40: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/40.jpg)
Federal AviationAdministration
40FLS & UMSJuly 2005
• Examples– Partitioning– Hardware Modes– Encoding– Tools
•Modifications•Loading Protection
Protection
![Page 41: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/41.jpg)
Federal AviationAdministration
41FLS & UMSJuly 2005
• Accidental Breach– Low Likelihood Under Reasonably
Probable Circumstances– (Subjective statement of probability
- not a xx.1309 definition)
• Intentional Breach– Low Likelihood Without Undue Effort
Protection
Protect AgainstBreaches
![Page 42: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/42.jpg)
Federal AviationAdministration
42FLS & UMSJuly 2005
Tools
• Used to Enforce Protection – Not DO-178B Qualified
Tools?
• Demonstrated As the Only Means To Modify UMS Component
![Page 43: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/43.jpg)
Federal AviationAdministration
43FLS & UMSJuly 2005
Tools Requires Review and Approval Of:
Use
Tool Design
Control
Modifications
Maintenance
![Page 44: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/44.jpg)
Federal AviationAdministration
44FLS & UMSJuly 2005
Design Approval of Tools
Tools
By ACO Engineer
![Page 45: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/45.jpg)
Federal AviationAdministration
45FLS & UMSJuly 2005
Maintenance Approval of Tools
Tools
Jointly By: ACO EngineerOperational AuthorityMaintenance Authority
![Page 46: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/46.jpg)
Federal AviationAdministration
46FLS & UMSJuly 2005
Data Requirements
PSAC
Design Data
Software ConfigurationIndex
Software AccomplishmentSummary
![Page 47: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/47.jpg)
Federal AviationAdministration
47FLS & UMSJuly 2005
Other Considerations
• User Follows the Approved Procedures for
Modifications to UMS
• User Responsible for Configuration Management, Quality Assurance, and Verification of the Software
• Changing Anything Besides UMS Can
Result in Certificate Being Rescinded
![Page 48: Presented to: By: Date: Federal Aviation Administration FLS & UMS Software Standardization Conference Dennis Wallace, Software Technical Specialist July.](https://reader036.fdocuments.in/reader036/viewer/2022081507/551a92785503466b3a8b4fd5/html5/thumbnails/48.jpg)
Federal AviationAdministration
48FLS & UMSJuly 2005
Summary
• Order 8110.49 Provides Guidelines For Approval of Systems & Equipment Containing UMS
• Provides Guidelines On:– Safety Considerations &
Safety Parameters– Protection– Tools– Data Requirements– Working With FSDO Personnel