Download PDF
---nasdaq--amzn_14.jpg "Amazon Web Services Logo")
NASA/JPL's Mars Curiosity Mission
Technology Category
- Infrastructure as a Service (IaaS) - Cloud Computing
Applicable Industries
- Aerospace
The Challenge
NASA's Jet Propulsion Laboratory wanted to share the launching of Curiosity with fans by providing up-to-the-minute details of the mission. Supporting hundreds of thousands of concurrent visitors to the website would have been very difficult since NASA did not have significant web and live video streaming infrastructure.
The Customer
NASA
About The Customer
NASA is the agency of the United States Federal Government responsible for the civilian space program, as well as aeronautics and aerospace research, with more than 17,000 employees.
The Solution
NASA’s Jet Propulsion Laboratory used AWS to stream the images and video associated with Curiosity’s landing. Cloud computing enabled NASA to provision capacity rapidly and leverage the AWS cloud to deliver successfully engaging experiences of Mars to the public. Novel use of Amazon Route 53 and Elastic Load Balancers enabled NASA to balance the load across AWS regions and ensure the availability of its content under all circumstances imaginable.
Data Collected
Connectivity Status, Images Captured, Video
Operational Impact
Quantitative Benefit
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.
