公司规模
Mid-size Company
地区
- Europe
- America
国家
- Italy
- Germany
- United States
产品
- IBM Cloud
- IBM’s Disaster-Recovery-as-a-Service
技术栈
- Cloud Computing
- Disaster Recovery
- ERP Systems
实施规模
- Enterprise-wide Deployment
影响指标
- Productivity Improvements
- Cost Savings
技术
- 基础设施即服务 (IaaS) - 云计算
适用行业
- 航天
适用功能
- 离散制造
- 采购
用例
- 供应链可见性(SCV)
服务
- 云规划/设计/实施服务
- 系统集成
关于客户
UmbraGroup 是一家私营公司,总部位于意大利福利尼奥。该公司是波音、空客、英国航空、汉莎航空、荷兰皇家航空、洛克希德马丁、通快和森精机等航空航天公司的战略供应商。这些公司依靠 UmbraGroup 的高精度机械部件来保证飞机在空中飞行和机器运转。该集团的工业和能源客户也依赖 UmbraGroup 的螺丝、轴承和机电零件的稳定供应。UmbraGroup 在德国和美国都有业务。2012 年,该公司完成了为期两年的集团企业资源规划系统整合,将四家公司整合到一个 IT 集团旗下。
挑战
意大利制造商 UmbraGroup 是全球航空航天公司的战略供应商。该公司的客户依靠 UmbraGroup 的高精度机械部件来保证飞机在空中飞行和机器运转。在当今即时供应链管理的运营环境中,这些公司对供应商的要求很高。UmbraGroup 需要确保其作为关键供应商的弹性。随着 UmbraGroup 开始收购新业务,包括德国的两家制造商和美国的一家制造商,弹性对 UmbraGroup 的重要性变得更加紧迫。该公司必须确保其系统在多个时区在全球范围内可用,远远超出其总部和福利尼奥的主要数据中心。除了常见的弹性挑战之外,地震也是意大利中部的一个现实问题。UmbraGroup 需要确保即使发生地震也不会停止生产和向客户发货。
解决方案
UmbraGroup 向国际公认的 IT 合作伙伴 IBM 寻求帮助,以确保其作为关键供应商的弹性。IBM 能够满足 UmbraGroup 的要求,并在性能、服务水平和成本之间找到适当的平衡。IBM 的云产品采用模块化方式构建,并采用按使用量付费的定价方式。云产品依靠预配置的硬件和动态配置将所有内容复制到远程数据中心,因此实施时间极短。IBM 和 UmbraGroup 正在设计一个连续性计划,该计划定义了运营和技术中的所有程序和依赖关系。他们正在研究每个流程,以确保没有任何步骤依赖于单个人。目标是制定一个在紧急情况下涵盖所有操作的故障转移计划——该计划可以减少依赖关系或在必要时找到解决依赖关系的方法。
运营影响
数量效益
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.