空军中央司令部 (AFCENT) 案例研究
公司规模
1,000+
地区
- America
- Asia
国家
- United States
产品
- Forcepoint™’s Trusted Thin Client®
- Citrix®
- NetApp®
- Avocent®
- Hewlett Packard™ (HP) thin client device
技术栈
- Network Infrastructure
- Thin Client Technology
- Multilevel Security
实施规模
- Enterprise-wide Deployment
影响指标
- Cost Savings
- Digital Expertise
- Productivity Improvements
技术
- 基础设施即服务 (IaaS) - 云计算
- 基础设施即服务 (IaaS) - 云存储服务
适用行业
- 航天
- 国家安全与国防
适用功能
- 离散制造
- 物流运输
用例
- 网络安全
- 远程资产管理
- 远程协作
服务
- 云规划/设计/实施服务
- 网络安全服务
关于客户
空军中央司令部 (AFCENT) 负责支持在西南亚进行的所有空中行动，并为作战人员提供增强的能力。2009 年，第 350 电子系统组 (ESG) 参与了一个建立新的联合空中和太空作战中心 (CAOC) 的项目。在新设施投入使用之前，美国和联军使用了六年的“临时”仓库式设施。
挑战
空军中央司令部 (AFCENT) 的任务是建立一个新的联合空中和太空作战中心 (CAOC)，以取代已使用六年的临时设施。新的 CAOC 需要提供更强大的系统来满足用户需求并提高互操作性。它还必须充分利用物理空间并降低功耗。从旧设施到新设施的过渡必须无缝衔接，以免中断任务行动。在过渡期间，CAOC 控制着两个现场战区的空中行动。该项目从规划到实施，不到两年就完成了。这个桌面整合项目给各方带来了其他挑战，因为 AFCENT 的任务要求全天候运营，可用性达到 99.99%。
解决方案
为了完成这项大规模工作，AFCENT 选择了 Forcepoint™ 的 Trusted Thin Client® 作为多级安全组件，并采用了 Citrix®、NetApp® 和 Avocent® 的技术来完善解决方案。为了恢复所需的工作空间、降低功耗并实现计算环境和网络基础设施的现代化，AFCENT 的目标是用瘦客户端取代 95% 的台式计算机。通过实施 Trusted Thin Client 软件，每个用户工作站的多个台式系统都被单个 Hewlett Packard™ (HP) 瘦客户端设备取代。用户现在可以从单个监视器查看多个网络，即使是不同分类级别的网络。如今，已部署了 1,648 个 Trusted Thin Client 席位。后端有多个分发控制台来支持用户、负载平衡和故障转移。Trusted Thin Client 部署最初为四个分类网络提供网络分离，现在提供对六个不同网络的安全访问。此实施支持超过 120 个命令和控制 (C2) 应用程序。
运营影响
数量效益
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.
