Rectangle Bar

Avionics

SDA has extensive experience in the design of Flight Management Systems, Communication Management Systems, Test Equipment, and PC Based Tools for the avionics industry.



FMS Experience
[back to top]

We have provided development services (system and software) as well as test services on both new and legacy FMS programs. Some of the programs we have contributed to in the past include:

  • Pegasus FMS products
  • EPIC FMS products
  • NZ FMS products
  • HT9100 FMS products
  • Cessna Radio Control Heads
  • 777 FMS
  • 787 Core CMU
  • FIDO and other Flight Test Data extraction software
  • SDP 175/185 PC-Based Simulator
  • KSN7xx FMS
  • GNSXLS FMS
  • Radar-IO Simulation
  • Iridium based SATCOM SDU

Specific experience related to FMS products is listed below.

  1. Database Management and Database Design:
    1. SDA was contracted to design (system and software level requirements) and code the DBAM SQL based database access software for use on certain FMS products.
    2. SDA was responsible for a large portion of the database format design associated with the NAV DB format on certain FMS products (those that use DBAM).
    3. The original FIDO (Flight Information and Data Output) access software and database design was developed by SDA and used on many FMS products.
    4. SDA has extensive experience with the TOLD (Take Off and Landing) on many FMS products.

  2. Navigation Function:
    1. SDA has participated or has been solely responsible for the navigation function on several FMS programs. One SDA engineer actually has a patent through Honeywell for polar navigation. Over the years SDA has been responsible for:
    2. Developing algorithms for VHF Radio tuning
    3. IRS, Hybrid, Radio, and GPS Navigation.
    4. Navigation filters.
    5. Phase of flight and RNP operation.
    6. B787, 777, Pegasus, NZ, EPIC, and etc. FMS products.

  3. Guidance Function (Lateral and Vertical):
    1. SDA has extensive experience in guidance, both lateral and vertical.
    2. SDA was contracted for the PRNAV update solution for the GNSXLS FMS. Prior to this update, it was a point to point navigator. SDA implemented all ARINC 424 leg types and included lateral guidance and advisory VNAV operation with these new leg types.
    3. SDA has made extensive lateral and vertical deviation modifications to support lateral/vertical approaches on the KSN7xx program. In addition, we have provided manual leg sequencing capability, lateral suspension functionality, sequencing alerts, and etc. These were modifications to the EPIC/APEX baseline.
    4. SDA has made many lateral guidance design changes for air transport FMS products, including Boeing and Airbus in the Pegasus baseline.

  4. Human-Machine Interface (both MCDU and Graphical):
    1. SDA has extensive experience working with and designing FMS user interfaces. This experience includes both graphical as well as classical MCDU interfaces.
    2. SDA developed the MCDU pages for a number of FMS products, including all the CPDLC pages for the NZ and EPIC data link operation using an MCDU design.
    3. SDA has built the entire proxy system for the KSN7xx program (based off of EPIC) which provides the graphical interface for the UI on the KSN7xx. This also involves map display and providing other flight planning information to the UI.
    4. SDA has developed CDU/MCDU protocol for the Pegasus FMS.
    5. SDA has worked with customers to specify requirements for use of ARINC 661 in a graphical interface.

  5. IO:
    1. SDA has been a key provider of IO expertise for a number of FMS programs. Work includes ARINC 429 (countless types of interfaces), Ethernet, USB, ARINC 629, RS232, RS422, NVM access, custom analog output/input, discrete output, ASCB, and etc.
    2. ARINC 629 on 777 for output of FIDO and navigation information.
    3. ARINC 429 experience with many programs for MCDU protocol, GAMA output, Radio output, driving SDUs, etc.
    4. Ethernet and USB experience on a number of programs (i.e. KSN7xx, Radar IO simulation, etc.).
    5. RS232 experience on GNSXLS, KSN7xx (equivalent quick setup pages moved to RS232).
    6. RS422 experience on NZ.
    7. Custom analog IO on the Cessna Radio Control head, in addition to building a PC based decoder.
    8. ASCB output/input process for EPIC and NZ.

  6. Data Link:
    1. SDA has been extensively involved in data link from both the CMU and the FMS side. FMS data link tasks include:
    2. SDA implemented all of the FANS data link functionality on the NZ (CPDLC, ADS, and AFN).
    3. SDA implemented FANS CPDLC on the EPIC FMS, as well as being responsible for fixing many problems with EPIC ADS.
    4. SDA implemented ADS for the common CMU program (both 787 and 747-400). Although this was not an FMS task, it involved defining a large number of FMS interfaces for data link.

  7. Flight Planning:
    1. SDA has extensive experience with FMS flight planning, both graphical and standard MCDU based flight planning.
    2. System, software, and code for Pegasus FMS.
    3. SDA was responsible for fixing flight planning problems on the NZ FMS and Pegasus FMS.
    4. SDA designed, documented, and tested the entire proxy system for graphical flight planning interfaces on the KSN7xx.
    5. SDA updated all the new flight planning functionality for the PRNAV upgrade to the GNSXLS FMS.

  8. Dual and Triplex Operation:
    1. SDA has provided FMS synchronization functionality for a number of flight management systems in both dual and triplex configurations.
    2. Triplex did not exist on the NZ prior SDA implementing the data link function for Bombardier. The triplex functionality was added (fitting into existing tight constraints for ASCB throughput).
    3. SDA has been responsible for Dual synchronization fixes on both NZ and EPIC.
    4. SDA has defined/implemented dual data for the common CMU/FMS interfaces for the Boeing 787 and Boeing 747-400.
    5. Responsible for system definition of dual transfer for some functions on the Pegasus programs.
    6. All updates to dual synchronization for the GNSXLS were performed by SDA.

  9. EFIS and Other Map Display Software
    1. SDA has extensive experience in EFIS display both in the GA, Business, and air transport environment.
    2. SDA was responsible for all the EFIS upgrades when the GNSXLS was upgraded for PRNAV.
    3. SDA has been responsible for EFIS fixes on the Pegasus FMS.
    4. SDA was responsible for Gama and RS232 map display on the KSN7xx.

  10. Performance Function and TOLD
    1. SDA has made TOLD fix packages and functionality updates on the NZ FMS for two different airframes. We are familiar with the tools, databases, and etc. used for TOLD NZ development.

  11. Verification and Validation
    1. SDA has performed the verification and validation task on several different FMS programs for at least some functions and in other cases for the FMS as a whole.
    2. SDA performed much of the V&V for Bombardier modifications. All data link plus additional navigation and guidance functionality was performed by SDA.
    3. The entire GNSXLS FMS upgrade for PRNAV was V&Ved by SDA.
    4. Although still in work, the V&V of all FMS baseline changes as well as all Proxy interface code is to be V&Ved by SDA.
    5. In the past, we have assisted with various V&V tasks in the EPIC/NZ baseline (Pilatus PC 12 for example).

  12. System Level Design
    1. SDA has been responsible for system level design changes to a number of different FMS products over the years. Functions include:
    2. Navigation
    3. Lateral Guidance
    4. Data link
    5. IO
    6. Database Access

  13. System Level Testing
    1. SDA has been responsible for system level testing of changes to a number of different FMS products over the years.
    2. Navigation
    3. Lateral Guidance
    4. Data link
    5. IO
    6. Database Access


CMU Experience
[back to top]

SDA has extensive experience in CMU development. We have designed, built, and tested most of the CMU functionality for one of our customers. In addition, we have provided simulations and tools related to data link. Our experience in this area include:

  1. ACARS
    1. We have designed (system level and software requirements), built (code), and tested (system level tests and verification and validation) the entire ACARS protocol/stack for a CMU. This involves both VDL Mode 2, VDL Mode A, and SATCOM operation. All verification testing was automated.
  2. ATN, CMU
    1. We have designed (system level and software requirements), built (code), and tested (system level tests and verification and validation) the entire ATN stack to support ATN CPDLC in the European theatre. This included the ATN router, network layer, transport layer, session layer, etc. In addition, the design included an option to enable the entire ATN message set per ICAO 9705/RTCA 280B (i.e. it was not the limited to the message set per Link 2000 program). All verification testing was automated.
  3. AVLC and 8208
    1. We have designed (system level and software requirements), built (code), and tested (system level tests and verification and validation) these lower level layers of protocol associated with ACARS and ATN over VDL Mode 2.
  4. User Interface
    1. We have built the entire user interface for a CMU. This includes ATN, ACARS, configuration module, IO configuration, etc.
  5. Simulations and Tools
    1. We have built entire data link network simulations and analyzer tools associated with data link via ACARS and ATN. In addition, we have built simulations and automated test systems for both FMS products and CMUs.
  6. Core CMU
    1. Provided the ADS functionality in the 787 Core CMU.


Related Experience
[back to top]

SDA has performed a number of avionics related tasks outside of the FMS/CMU realm such as:

  1. We have designed, built, and offer for sale an entire ARINC/SITA Network simulation to support datalink testing.

  2. We have produced IO simulations used for use in testing weather radar.

  3. We have analyzed and fixed software errors in old Cessna tuning head. This included the generation of a PC based tool to read analog output encoded by the tuning heads and provided simulated input back.

  4. We created the database driven user interface (supports MIDU and MCDU) and ARINC 739 protocol for an Iridium SDU product.

  5. Over the years we have developed from scratch or modified a number of PC-based tools, including: FIDO, OneNav, and Structural Coverage tools.

  6. We have created simulators for older processors such as the SDP 185 PC based simulator.

"When performance is lacking, go with the alternative: Software Development Alternatives"
David W. Dodson, President and CEO, SDA Inc.