Fast, streamlined, compliant development of next-generation flight management systems
Customer Company Size
Large Corporate
Region
- America
Country
- United States
Product
- IBM Rational Rhapsody
- IBM Rational Rhapsody kit for DO-178B/C
- IBM Rational Rhapsody Test Conductor
- IBM Rational Publishing Engine
- IBM Rational DOORS
Tech Stack
- IBM Software Services for Rational
- Unified Modeling Language (UML)
- Simplified C++ execution framework
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Productivity Improvements
- Cost Savings
Technology Category
- Application Infrastructure & Middleware - API Integration & Management
Applicable Industries
- Aerospace
Applicable Functions
- Product Research & Development
Use Cases
- Manufacturing System Automation
- Predictive Maintenance
Services
- Software Design & Engineering Services
- System Integration
About The Customer
CMC Electronics is a company owned by Esterline Corporation, a specialized manufacturing company that principally serves the aerospace and defense markets. CMC Electronics designs and produces leading technology electronics products for the aviation and global positioning markets. The company is well known in the aviation industry for its flight management systems (FMS) – the sophisticated navigation systems that help modern aircraft manage flight plans without the need for a human navigator or flight engineer. Over the years, CMC has developed a comprehensive range of FMS products, designed to meet the specific needs of different sectors of the aviation market.
The Challenge
CMC Electronics, a company known for its flight management systems (FMS) in the aviation industry, was facing a challenge in developing its next-generation FMS. The company had a range of FMS products, each designed to meet the specific needs of different sectors of the aviation market. However, this approach was time-consuming and required more effort to develop and maintain separate software for each target market. For its next generation of FMS products, the company decided to build a core system that would be used by all of its FMS products, and supplement it with customizable, reusable components that could meet the specific requirements of different markets. To support this new development process, CMC needed a new set of tools that would provide a collaborative environment for software and systems design, development, and testing.
The Solution
After reviewing options from various vendors and the open source community, CMC chose IBM® Rational® Rhapsody®. Working with IBM, the CMC team tailored the IBM Rational Rhapsody solution to its requirements. IBM helped to identify best practices for model-based, object-oriented development in compliance with DO-178C and other aviation standards such as ARP4754A. IBM Rational Rhapsody was used during the system design phase for system requirements analysis, system design, and high-level design requirements development. During software design, IBM Rational Rhapsody was also used for software design and automatic code generation using the simplified C++ execution framework, which is ideally suited for safety-critical development. To ensure that the software design was properly verified, CMC used IBM Rational Rhapsody Test Conductor with the Unified Modeling Language (UML) Testing Profile to automate aspects of the unit testing process.
Operational Impact
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
Airbus Soars with Wearable Technology
Building an Airbus aircraft involves complex manufacturing processes consisting of thousands of moving parts. Speed and accuracy are critical to business and competitive advantage. Improvements in both would have high impact on Airbus’ bottom line. Airbus wanted to help operators reduce the complexity of assembling cabin seats and decrease the time required to complete this task.
Case Study
Aircraft Predictive Maintenance and Workflow Optimization
First, aircraft manufacturer have trouble monitoring the health of aircraft systems with health prognostics and deliver predictive maintenance insights. Second, aircraft manufacturer wants a solution that can provide an in-context advisory and align job assignments to match technician experience and expertise.
Case Study
Aerospace & Defense Case Study Airbus
For the development of its new wide-body aircraft, Airbus needed to ensure quality and consistency across all internal and external stakeholders. Airbus had many challenges including a very aggressive development schedule and the need to ramp up production quickly to satisfy their delivery commitments. The lack of communication extended design time and introduced errors that drove up costs.
Case Study
Developing Smart Tools for the Airbus Factory
Manufacturing and assembly of aircraft, which involves tens of thousands of steps that must be followed by the operators, and a single mistake in the process could cost hundreds of thousands of dollars to fix, makes the room for error very small.
Case Study
Accelerate Production for Spirit AeroSystems
The manufacture and assembly of massive fuselage assemblies and other large structures generates a river of data. In fact, the bill of materials for a single fuselage alone can be millions of rows of data. In-house production processes and testing, as well as other manufacturers and customers created data flows that overwhelmed previous processes and information systems. Spirit’s customer base had grown substantially since their 2005 divestiture from Boeing, resulting in a $41 billion backlog of orders to fill. To address this backlog, meet increased customer demands and minimize additional capital investment, the company needed a way to improve throughput in the existing operational footprint. Spirit had a requirement from customers to increase fuselage production by 30%. To accomplish this goal, Spirit needed real-time information on its value chain and workflow. However, the two terabytes of data being pulled from their SAP ECC was unmanageable and overloaded their business warehouse. It had become time-consuming and difficult to pull aggregate data, disaggregate it for the needed information and then reassemble to create a report. During the 6-8 hours it took to build a report, another work shift (they run three per day) would have already taken place, thus the report content was out-of-date before it was ever delivered. As a result, supervisors often had to rely on manual efforts to provide charts, reports and analysis.
