公司规模
Large Corporate
地区
- America
国家
- United States
产品
- IBM Rational Rhapsody
- IBM Rational Rhapsody kit for DO-178B/C
- IBM Rational Rhapsody Test Conductor
- IBM Rational Publishing Engine
- IBM Rational DOORS
技术栈
- IBM Software Services for Rational
- Unified Modeling Language (UML)
- Simplified C++ execution framework
实施规模
- Enterprise-wide Deployment
影响指标
- Productivity Improvements
- Cost Savings
技术
- 应用基础设施与中间件 - API 集成与管理
适用行业
- 航天
适用功能
- 产品研发
用例
- 自动化制造系统
- 预测性维护
服务
- 软件设计与工程服务
- 系统集成
关于客户
CMC Electronics 是 Esterline Corporation 旗下的一家公司,后者是一家主要服务于航空航天和国防市场的专业制造公司。CMC Electronics 为航空和全球定位市场设计和生产技术领先的电子产品。该公司以其飞行管理系统 (FMS) 而闻名于航空业 - 这是一种先进的导航系统,可帮助现代飞机管理飞行计划,而无需人工导航员或飞行工程师。多年来,CMC 开发了全面的 FMS 产品系列,旨在满足航空市场不同部门的特定需求。
挑战
CMC Electronics 是一家以航空业飞行管理系统 (FMS) 而闻名的公司,它在开发下一代 FMS 时面临着挑战。该公司拥有一系列 FMS 产品,每款产品都旨在满足航空市场不同部门的特定需求。但是,这种方法非常耗时,而且需要付出更多努力来为每个目标市场开发和维护单独的软件。对于其下一代 FMS 产品,该公司决定构建一个可供其所有 FMS 产品使用的核心系统,并用可定制、可重复使用的组件对其进行补充,以满足不同市场的特定要求。为了支持这一新的开发流程,CMC 需要一套新的工具,为软件和系统的设计、开发和测试提供协作环境。
解决方案
在审查了来自不同供应商和开源社区的选项后,CMC 选择了 IBM® Rational® Rhapsody®。通过与 IBM 合作,CMC 团队根据其需求定制了 IBM Rational Rhapsody 解决方案。IBM 帮助确定了符合 DO-178C 和其他航空标准(如 ARP4754A)的基于模型、面向对象的开发的最佳实践。在系统设计阶段,IBM Rational Rhapsody 用于系统需求分析、系统设计和高级设计需求开发。在软件设计期间,IBM Rational Rhapsody 还用于软件设计和自动代码生成,使用简化的 C++ 执行框架,该框架非常适合安全关键型开发。为了确保软件设计得到正确验证,CMC 使用 IBM Rational Rhapsody Test Conductor 和统一建模语言 (UML) 测试配置文件来自动化单元测试过程的各个方面。
运营影响
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
相关案例.
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.