The document discusses managing requirements and architecture volatility for NASA's CPAS (CEV Parachute Assembly System) project. It summarizes how [1] requirements and architectures can change over time as multiple organizations work together, [2] early CPAS requirements exceeded Apollo-era requirements, and [3] collaboration between CPAS and Lockheed Martin helped establish interim requirements to allow design work to proceed.
The document summarizes the development of the Ares I-X Roll Control System (RoCS) for the Ares I-X launch vehicle. The RoCS provided rotational control using a bi-propellant system developed under an Integrated Product Team model. Key aspects included delivering the system on schedule, within budget, and with high quality to support the October 2009 launch. Off-the-shelf and surplus government components were used, including components from decommissioned Peacekeeper missiles, saving over $10 million.
This document provides information about MilSOFT, including:
- It was established in 1998 and operates facilities in Ankara and Istanbul, Turkey.
- It has expertise in areas like C4I, data links, image exploitation, electronic warfare, training and simulation, and embedded systems.
- It has experience providing systems integration and software development for military programs to Turkish and international clients.
- It maintains various quality certifications including CMMI Level-5, ISO 9001:2008, and NATO AQAP-160.
1. SAIC and ePM used simulation techniques to model and optimize the manufacturing process for the Upper Stage Simulator for the Ares I-X rocket.
2. The simulation results showed that the manufacturing process is highly sensitive to the number of fabricators and welders, and recommended a baseline of 8 fabricators and 6 welders per shift.
3. The investigation of non-destructive inspection factors found that the manufacturing process duration is most impacted by the defect rate during inspections. Higher defect rates significantly increase the overall duration.
NASA-NOAA Cooperative Supports for Aqua and Aura Missionsledlow
How NOAA and NASA established an effective working relationship at the Fairbanks Command and Data Acquisition Station. Presented at the 2005 Ground Systems Architecture Workshop.
The Space and Naval Warfare Systems Center Atlantic provides information technology solutions for naval, joint, national, and coalition forces. It has over 3,900 employees and works with 9,200 industry partners. SSC Atlantic conducts research, testing, and integration work at its facilities in Charleston. It has a large economic impact in South Carolina and helps develop the state's technology workforce.
The document provides an overview of the requirements and processes needed to successfully pass Preliminary Design Review (PDR) and Key Decision Point C (KDP C) under NASA Procedural Requirements 7120.5D. It first discusses categorizing a project based on cost and complexity to determine the appropriate decision authority and governing documents. It then outlines the phases of formulation and implementation in the project lifecycle and the major reviews and decision gates including PDR, which provides approval to proceed to implementation phases. Examples from the Juno project are given to demonstrate how to address the requirements to have a successful PDR while still accomplishing the primary work.
Présentation de Mme Julie-Soleil Meeson, directrice de GRIP Montréal et Élixir lors de la première journée des organismes communautaires en prévention des dépendances
The document summarizes the development of the Ares I-X Roll Control System (RoCS) for the Ares I-X launch vehicle. The RoCS provided rotational control using a bi-propellant system developed under an Integrated Product Team model. Key aspects included delivering the system on schedule, within budget, and with high quality to support the October 2009 launch. Off-the-shelf and surplus government components were used, including components from decommissioned Peacekeeper missiles, saving over $10 million.
This document provides information about MilSOFT, including:
- It was established in 1998 and operates facilities in Ankara and Istanbul, Turkey.
- It has expertise in areas like C4I, data links, image exploitation, electronic warfare, training and simulation, and embedded systems.
- It has experience providing systems integration and software development for military programs to Turkish and international clients.
- It maintains various quality certifications including CMMI Level-5, ISO 9001:2008, and NATO AQAP-160.
1. SAIC and ePM used simulation techniques to model and optimize the manufacturing process for the Upper Stage Simulator for the Ares I-X rocket.
2. The simulation results showed that the manufacturing process is highly sensitive to the number of fabricators and welders, and recommended a baseline of 8 fabricators and 6 welders per shift.
3. The investigation of non-destructive inspection factors found that the manufacturing process duration is most impacted by the defect rate during inspections. Higher defect rates significantly increase the overall duration.
NASA-NOAA Cooperative Supports for Aqua and Aura Missionsledlow
How NOAA and NASA established an effective working relationship at the Fairbanks Command and Data Acquisition Station. Presented at the 2005 Ground Systems Architecture Workshop.
The Space and Naval Warfare Systems Center Atlantic provides information technology solutions for naval, joint, national, and coalition forces. It has over 3,900 employees and works with 9,200 industry partners. SSC Atlantic conducts research, testing, and integration work at its facilities in Charleston. It has a large economic impact in South Carolina and helps develop the state's technology workforce.
The document provides an overview of the requirements and processes needed to successfully pass Preliminary Design Review (PDR) and Key Decision Point C (KDP C) under NASA Procedural Requirements 7120.5D. It first discusses categorizing a project based on cost and complexity to determine the appropriate decision authority and governing documents. It then outlines the phases of formulation and implementation in the project lifecycle and the major reviews and decision gates including PDR, which provides approval to proceed to implementation phases. Examples from the Juno project are given to demonstrate how to address the requirements to have a successful PDR while still accomplishing the primary work.
Présentation de Mme Julie-Soleil Meeson, directrice de GRIP Montréal et Élixir lors de la première journée des organismes communautaires en prévention des dépendances
The document describes the evolution of command and control systems at Kennedy Space Center from the 1950s to present day. Early systems involved manually controlling launches from vehicles. As systems grew more complex, automation was required. The Space Shuttle introduced digital controls. For future vehicles like Constellation, a new standards-based system was designed using commercial off-the-shelf components. The Launch Control System is now operational and supports multiple customers and vehicles.
This document describes the design of a vertical take-off and landing (VTOL) unmanned aerial vehicle (UAV) for intelligence, surveillance, and reconnaissance missions. The goals are to develop a fixed-wing UAV with VTOL capability, high speed, stealth, and autonomous payload delivery. An additive manufactured airframe and commercial off-the-shelf components are selected to allow for low cost and reconfiguration. Electronics including batteries, motors, flight controller, and Android device are designed to fit within the airframe. A transition rig is built and tested to demonstrate VTOL capability using simpler autopilot software prior to integrating the design onto the full-scale aircraft.
The document discusses COTS FACE solutions from RTI and Wind River that can help address challenges in developing airborne systems. It describes how the FACE initiative uses standardized interfaces and layered architectures to enable software reuse and reduce costs. RTI provides a Transport Services Segment that uses DDS for loose coupling between applications. Wind River offers FACE-aligned operating systems like VxWorks 653 that achieve safety certifications. Together these COTS solutions form a partner stack that delivers FACE-compliant capabilities to warfighters faster and at lower cost.
BAE Systems implemented a PROFIBUS network on submarines to address issues with legacy control systems, including obsolescence and difficulty maintaining bespoke systems. The PROFIBUS network provides a dual redundant architecture to interface thousands of inputs and outputs across vessel systems to the Integrated Platform Management System. Safety was a key requirement and was ensured through assessments, redundancy in the network design, and a reliance on operators in degraded conditions. Initial benefits of the PROFIBUS network included improved diagnostics, reduced cabling, and flexibility to modify the system, with expected cost savings over the life of the submarines.
The document discusses determining requirements compliance during the design phase for a system of systems. It outlines the methodology used, which involves identifying and resolving non-compliant design aspects early through objective evidence and assessments. Requirements traceability and stakeholder involvement are important. The process connects requirements to verification and provides periodic assessments of design health. Making it work for complex systems requires collaboration, clear communication, and a simple approach.
The Max Launch Abort System (MLAS) project developed an alternative design for NASA's Orion Launch Abort System to demonstrate during a pad abort test. A broad-based team designed a flight test vehicle using existing hardware when possible. The MLAS concept utilized four center-clustered solid rocket motors on a separable boost skirt and planar fins on a coast skirt. Upcoming milestones included completing integration and testing of the crew module avionics and conducting the pad abort flight test in March 2009.
Frame Relay is a widely used WAN technology that provides greater bandwidth than leased lines at a lower cost. It encapsulates data packets into frame relay frames that are transmitted over virtual circuits identified by a DLCI. Frame Relay uses inverse ARP to map DLCIs to IP addresses. Configuring Frame Relay requires enabling encapsulation and configuring static or dynamic mapping, considering split horizon problems when multiple VCs are on one interface. Flow control mechanisms like DE, FECN, and BECN can also be implemented.
The document discusses Frame Relay, a widely used WAN technology. It describes how Frame Relay uses virtual circuits to carry packets between devices and explains the encapsulation process. The document also covers configuring basic and advanced Frame Relay PVCs, including subinterfaces, bandwidth control, flow control, and troubleshooting. Key commands for verifying and debugging Frame Relay are provided.
The document discusses project management practices for defense acquisition programs in the United States. It describes how the U.S. Department of Defense extends the Project Management Body of Knowledge (PMBOK) guide for defense systems. It also discusses how work breakdown structures (WBS), earned value management (EVM), and integrated master plans/schedules are used to define work, allocate costs, and integrate technical and schedule performance for defense acquisition projects. Requirements documents, contracts, and proposals must reflect these project management elements.
This document provides an overview of the Aircraft Classification Rating - Pavement Classification Rating (ACR-PCR) system that is being developed in cooperation with the International Civil Aviation Organization (ICAO) to replace the existing Aircraft Classification Number - Pavement Classification Number (ACN-PCN) method. The key points are:
1) The ACR-PCR system uses a fully layered elastic analysis approach without factors like alpha or equivalency factors.
2) It has completed state review and will enter a 4-year transition period in 2020 before full implementation in 2024.
3) The FAA has developed the ICAO-ACR program to compute ACR values using a visual basic library, and
Rapid Development of a Rotorcraft UAV System - AHS Tech Specialists Meeting 2005Mark Hardesty
This document summarizes the development of a rotorcraft unmanned aerial vehicle (UAV) system by Boeing Phantom Works over less than one year. They selected the MD 530F helicopter due to its performance capabilities and military counterpart. The design integrated commercial off-the-shelf hardware and proprietary Boeing flight control software. Bench and flight testing were prioritized to rapidly expand the flight envelope from initial engagement of the electrical flight controls to autonomous takeoffs, landings and navigation. The manual override capability allowed high-risk prototype systems to be safely tested.
Mushini Lakshmi Venkata Sairam has over 2 years of experience as a System Engineer working on industrial automation projects. She has extensive experience designing and implementing DCS systems for various clients, including migration projects, third party interfaces, and handling ongoing AMC visits. Sairam holds a B.Tech in Electronics and Communication Engineering and has received several certifications in areas such as DCS configuration, Triconex, Archestra, and industrial safety.
AIAA White Paper on Fluid Dynamics Challenges in Flight mechanicsstephen_mcparlin
This document proposes a taxonomy to systematically address flight mechanics issues for aircraft using computational fluid dynamics (CFD). It recommends a series of workshops focusing on specific fluid dynamics phenomena relevant to flight stability problems. The workshops would combine experimental data analysis and CFD evaluation to determine the appropriate level of modeling needed to predict each phenomenon. This "building block" approach aims to advance CFD capabilities and identify areas needing further research, in order to improve prediction of nonlinear flight stability characteristics.
This document analyzes bungee cord launching devices (LDs) for unmanned aerial vehicles (UAVs). It provides four analyses: 1) an analysis of LD systems against critical design requirements and customer needs, 2) an analysis of the motion of the UAV-cradle subsystem on the launch rail, 3) an analysis of cord selection and the cord's energetic capabilities based on design requirements, and 4) an analysis of how aerodynamic lift and drag forces influence mathematical and physical models, with results compared. The analyses recommend bungee cord LDs for early design phases. Mathematical models of the UAV-cradle motion on the launch rail are developed based on various assumptions about forces like gravity
Frame Relay is a WAN protocol that operates at the data link layer. It was developed as a simpler version of X.25 to use over ISDN interfaces. Frame Relay is widely used for voice and data connectivity between LANs over a WAN due to its lower cost compared to dedicated lines. It uses virtual circuits to connect devices and provides bandwidth, reliability, and scalability benefits over private lines.
When it comes to offshore wind energy technology, most innovations are dedicated to foundations or construction techniques to lower LCOE by lowering CapEx and OpEx, but we are reaching an inflection point and AEP needs to be prioritized. Wind park controls and operations methods for revenue and power maximization being developed for onshore wind will be fundamentally necessary to leverage in order to drive maximum offshore LCOE benefit as the CapEx impact on reducing LCOE slows down in the coming years.
Enhancement of ARINC 653 for Multi-core Hardware.pptxAbrar Hafiz
The document discusses the enhancement of ARINC 653 for multi-core hardware. It provides an overview of industry trends driving more functionality and connectivity in aerospace and defense systems. This is creating challenges around safety, security, and certification. The presentation then describes ARINC 653 and its role in integrated modular avionics, and some of the issues that arise in multi-core systems. It outlines the capabilities of the VxWorks 653 single-core and multi-core editions for addressing these issues and supporting certification. Use cases are presented for migrating existing systems to multi-core and expanding functionality.
This document discusses Frame Relay networking concepts and configuration. It covers fundamental Frame Relay concepts such as encapsulation and virtual circuits. It also covers configuring basic and advanced Frame Relay PVCs, including subinterfaces, bandwidth control, and flow control. Troubleshooting techniques are provided. The overall purpose is to teach system administrators how to implement and manage Frame Relay networks.
Technology Primer: Software-Defined Networking and Its Impact on Infrastructu...CA Technologies
Software Defined Networking (SDN) and Network Function Virtualization (NFV) represent a major shift in the way networks will be designed, deployed and managed—requiring changes in infrastructure management tools and practices. This presentation illustrates our vision with use cases under consideration for CA Performance Management, which is designed for managing complex, highly-scaled networks and could be applied in the future to managing Software Defined Networks and integrating with SDN controllers and NFV elements.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
This document provides a manual for the design and detailing of reinforced concrete structures according to the Code of Practice for Structural Use of Concrete 2004. It outlines key aspects of the code including basis of design, design loads, materials, ductility requirements, and provides guidance on detailing various reinforced concrete elements like beams, slabs, columns, foundations and more. Design examples, derivations and appendices are included to aid understanding and application of the code.
The document compares the operational complexity and costs of the Space Shuttle versus the Sea Launch Zenit rocket. [1] The Space Shuttle was designed for performance but not operational efficiency, resulting in costly ground, mission planning, and flight operations. [2] In contrast, the Zenit rocket was designed from the start to have automated and robust processes to keep operations simple and costs low. [3] The key lesson is that designing a launch system with operational requirements in mind from the beginning leads to much more efficient operations long-term.
The document provides an overview of project management and procurement at NASA. It discusses the key skills required for project managers, including acquisition management. It notes that 80-85% of NASA's budget is spent on contracts, and procurement processes are complex and constantly changing. The document outlines some common contract types and how they allocate risk between the government and contractor. It also discusses the relationship between contracting officers and project managers, and how successful procurement requires effective communication rather than direct control or authority.
The document describes the evolution of command and control systems at Kennedy Space Center from the 1950s to present day. Early systems involved manually controlling launches from vehicles. As systems grew more complex, automation was required. The Space Shuttle introduced digital controls. For future vehicles like Constellation, a new standards-based system was designed using commercial off-the-shelf components. The Launch Control System is now operational and supports multiple customers and vehicles.
This document describes the design of a vertical take-off and landing (VTOL) unmanned aerial vehicle (UAV) for intelligence, surveillance, and reconnaissance missions. The goals are to develop a fixed-wing UAV with VTOL capability, high speed, stealth, and autonomous payload delivery. An additive manufactured airframe and commercial off-the-shelf components are selected to allow for low cost and reconfiguration. Electronics including batteries, motors, flight controller, and Android device are designed to fit within the airframe. A transition rig is built and tested to demonstrate VTOL capability using simpler autopilot software prior to integrating the design onto the full-scale aircraft.
The document discusses COTS FACE solutions from RTI and Wind River that can help address challenges in developing airborne systems. It describes how the FACE initiative uses standardized interfaces and layered architectures to enable software reuse and reduce costs. RTI provides a Transport Services Segment that uses DDS for loose coupling between applications. Wind River offers FACE-aligned operating systems like VxWorks 653 that achieve safety certifications. Together these COTS solutions form a partner stack that delivers FACE-compliant capabilities to warfighters faster and at lower cost.
BAE Systems implemented a PROFIBUS network on submarines to address issues with legacy control systems, including obsolescence and difficulty maintaining bespoke systems. The PROFIBUS network provides a dual redundant architecture to interface thousands of inputs and outputs across vessel systems to the Integrated Platform Management System. Safety was a key requirement and was ensured through assessments, redundancy in the network design, and a reliance on operators in degraded conditions. Initial benefits of the PROFIBUS network included improved diagnostics, reduced cabling, and flexibility to modify the system, with expected cost savings over the life of the submarines.
The document discusses determining requirements compliance during the design phase for a system of systems. It outlines the methodology used, which involves identifying and resolving non-compliant design aspects early through objective evidence and assessments. Requirements traceability and stakeholder involvement are important. The process connects requirements to verification and provides periodic assessments of design health. Making it work for complex systems requires collaboration, clear communication, and a simple approach.
The Max Launch Abort System (MLAS) project developed an alternative design for NASA's Orion Launch Abort System to demonstrate during a pad abort test. A broad-based team designed a flight test vehicle using existing hardware when possible. The MLAS concept utilized four center-clustered solid rocket motors on a separable boost skirt and planar fins on a coast skirt. Upcoming milestones included completing integration and testing of the crew module avionics and conducting the pad abort flight test in March 2009.
Frame Relay is a widely used WAN technology that provides greater bandwidth than leased lines at a lower cost. It encapsulates data packets into frame relay frames that are transmitted over virtual circuits identified by a DLCI. Frame Relay uses inverse ARP to map DLCIs to IP addresses. Configuring Frame Relay requires enabling encapsulation and configuring static or dynamic mapping, considering split horizon problems when multiple VCs are on one interface. Flow control mechanisms like DE, FECN, and BECN can also be implemented.
The document discusses Frame Relay, a widely used WAN technology. It describes how Frame Relay uses virtual circuits to carry packets between devices and explains the encapsulation process. The document also covers configuring basic and advanced Frame Relay PVCs, including subinterfaces, bandwidth control, flow control, and troubleshooting. Key commands for verifying and debugging Frame Relay are provided.
The document discusses project management practices for defense acquisition programs in the United States. It describes how the U.S. Department of Defense extends the Project Management Body of Knowledge (PMBOK) guide for defense systems. It also discusses how work breakdown structures (WBS), earned value management (EVM), and integrated master plans/schedules are used to define work, allocate costs, and integrate technical and schedule performance for defense acquisition projects. Requirements documents, contracts, and proposals must reflect these project management elements.
This document provides an overview of the Aircraft Classification Rating - Pavement Classification Rating (ACR-PCR) system that is being developed in cooperation with the International Civil Aviation Organization (ICAO) to replace the existing Aircraft Classification Number - Pavement Classification Number (ACN-PCN) method. The key points are:
1) The ACR-PCR system uses a fully layered elastic analysis approach without factors like alpha or equivalency factors.
2) It has completed state review and will enter a 4-year transition period in 2020 before full implementation in 2024.
3) The FAA has developed the ICAO-ACR program to compute ACR values using a visual basic library, and
Rapid Development of a Rotorcraft UAV System - AHS Tech Specialists Meeting 2005Mark Hardesty
This document summarizes the development of a rotorcraft unmanned aerial vehicle (UAV) system by Boeing Phantom Works over less than one year. They selected the MD 530F helicopter due to its performance capabilities and military counterpart. The design integrated commercial off-the-shelf hardware and proprietary Boeing flight control software. Bench and flight testing were prioritized to rapidly expand the flight envelope from initial engagement of the electrical flight controls to autonomous takeoffs, landings and navigation. The manual override capability allowed high-risk prototype systems to be safely tested.
Mushini Lakshmi Venkata Sairam has over 2 years of experience as a System Engineer working on industrial automation projects. She has extensive experience designing and implementing DCS systems for various clients, including migration projects, third party interfaces, and handling ongoing AMC visits. Sairam holds a B.Tech in Electronics and Communication Engineering and has received several certifications in areas such as DCS configuration, Triconex, Archestra, and industrial safety.
AIAA White Paper on Fluid Dynamics Challenges in Flight mechanicsstephen_mcparlin
This document proposes a taxonomy to systematically address flight mechanics issues for aircraft using computational fluid dynamics (CFD). It recommends a series of workshops focusing on specific fluid dynamics phenomena relevant to flight stability problems. The workshops would combine experimental data analysis and CFD evaluation to determine the appropriate level of modeling needed to predict each phenomenon. This "building block" approach aims to advance CFD capabilities and identify areas needing further research, in order to improve prediction of nonlinear flight stability characteristics.
This document analyzes bungee cord launching devices (LDs) for unmanned aerial vehicles (UAVs). It provides four analyses: 1) an analysis of LD systems against critical design requirements and customer needs, 2) an analysis of the motion of the UAV-cradle subsystem on the launch rail, 3) an analysis of cord selection and the cord's energetic capabilities based on design requirements, and 4) an analysis of how aerodynamic lift and drag forces influence mathematical and physical models, with results compared. The analyses recommend bungee cord LDs for early design phases. Mathematical models of the UAV-cradle motion on the launch rail are developed based on various assumptions about forces like gravity
Frame Relay is a WAN protocol that operates at the data link layer. It was developed as a simpler version of X.25 to use over ISDN interfaces. Frame Relay is widely used for voice and data connectivity between LANs over a WAN due to its lower cost compared to dedicated lines. It uses virtual circuits to connect devices and provides bandwidth, reliability, and scalability benefits over private lines.
When it comes to offshore wind energy technology, most innovations are dedicated to foundations or construction techniques to lower LCOE by lowering CapEx and OpEx, but we are reaching an inflection point and AEP needs to be prioritized. Wind park controls and operations methods for revenue and power maximization being developed for onshore wind will be fundamentally necessary to leverage in order to drive maximum offshore LCOE benefit as the CapEx impact on reducing LCOE slows down in the coming years.
Enhancement of ARINC 653 for Multi-core Hardware.pptxAbrar Hafiz
The document discusses the enhancement of ARINC 653 for multi-core hardware. It provides an overview of industry trends driving more functionality and connectivity in aerospace and defense systems. This is creating challenges around safety, security, and certification. The presentation then describes ARINC 653 and its role in integrated modular avionics, and some of the issues that arise in multi-core systems. It outlines the capabilities of the VxWorks 653 single-core and multi-core editions for addressing these issues and supporting certification. Use cases are presented for migrating existing systems to multi-core and expanding functionality.
This document discusses Frame Relay networking concepts and configuration. It covers fundamental Frame Relay concepts such as encapsulation and virtual circuits. It also covers configuring basic and advanced Frame Relay PVCs, including subinterfaces, bandwidth control, and flow control. Troubleshooting techniques are provided. The overall purpose is to teach system administrators how to implement and manage Frame Relay networks.
Technology Primer: Software-Defined Networking and Its Impact on Infrastructu...CA Technologies
Software Defined Networking (SDN) and Network Function Virtualization (NFV) represent a major shift in the way networks will be designed, deployed and managed—requiring changes in infrastructure management tools and practices. This presentation illustrates our vision with use cases under consideration for CA Performance Management, which is designed for managing complex, highly-scaled networks and could be applied in the future to managing Software Defined Networks and integrating with SDN controllers and NFV elements.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
This document provides a manual for the design and detailing of reinforced concrete structures according to the Code of Practice for Structural Use of Concrete 2004. It outlines key aspects of the code including basis of design, design loads, materials, ductility requirements, and provides guidance on detailing various reinforced concrete elements like beams, slabs, columns, foundations and more. Design examples, derivations and appendices are included to aid understanding and application of the code.
The document compares the operational complexity and costs of the Space Shuttle versus the Sea Launch Zenit rocket. [1] The Space Shuttle was designed for performance but not operational efficiency, resulting in costly ground, mission planning, and flight operations. [2] In contrast, the Zenit rocket was designed from the start to have automated and robust processes to keep operations simple and costs low. [3] The key lesson is that designing a launch system with operational requirements in mind from the beginning leads to much more efficient operations long-term.
The document provides an overview of project management and procurement at NASA. It discusses the key skills required for project managers, including acquisition management. It notes that 80-85% of NASA's budget is spent on contracts, and procurement processes are complex and constantly changing. The document outlines some common contract types and how they allocate risk between the government and contractor. It also discusses the relationship between contracting officers and project managers, and how successful procurement requires effective communication rather than direct control or authority.
The document introduces the NASA Engineering Network (NEN), which was created by the Office of the Chief Engineer to be a knowledge management system connecting NASA's engineering community. The NEN integrates various tools like a content management system, search engine, and collaboration tools. It provides access to key knowledge resources like NASA's Lessons Learned database and engineering databases. The NEN is working to expand by adding more communities, engineering disciplines, and knowledge repositories.
Laptops were first used in space in 1983 on the Space Shuttle, when Commander John Young brought the GRiD Compass portable computer on STS-9. Laptops are now widely used on the Space Shuttle and International Space Station for tasks like monitoring spacecraft systems, tracking satellites, inventory management, procedures viewing, and videoconferencing. Managing laptops in space presents challenges around cooling, power, and software/hardware compatibility in the harsh space environment.
Laptops were first used in space in 1983 on the Space Shuttle, when Commander John Young brought the GRiD Compass portable computer on STS-9. Laptops are now widely used on the Space Shuttle and International Space Station for tasks like monitoring spacecraft systems, planning rendezvous and proximity operations, inventory management, procedure reviews, and communication between space and ground via software like WorldMap and DOUG. Managing laptops in space presents challenges around hardware durability, cooling, and software/data management in the space environment.
This document discusses the use of market-based systems to allocate scarce resources for NASA missions and projects. It provides examples of how market-based approaches were used for instrument development for the Cassini mission, manifesting secondary payloads on the space shuttle, and mission planning for the LightSAR Earth imaging satellite project. The document finds that these applications of market-based allocation benefited or could have benefited from a decentralized, incentive-based approach compared to traditional centralized planning methods. However, it notes that resistance to new approaches and loss of managerial control are barriers to adoption of market-based systems.
The Stardust mission collected samples from comet Wild 2 and interstellar dust particles. It launched in February 1999 and encountered Wild 2 in January 2004, collecting dust samples in aerogel. It returned the samples to Earth safely in January 2006. The spacecraft used an innovative Whipple shield to protect itself from comet dust impacts during the encounter. Analysis of the Stardust samples has provided insights about comet composition and the early solar system.
This document discusses solutions for integrating schedules on NASA programs. It introduces Stuart Trahan's company, which provides Earned Value Management (EVM) solutions using Microsoft Office Project that comply with OMB and ANSI requirements. It also introduces a partner company, Pinnacle Management Systems, that specializes in enterprise project management solutions including EVM, project portfolio management, and enterprise project resource management, with experience in the aerospace, defense, and other industries. The document defines schedule integration and describes some methods including importing to a centralized Primavera database for review or using Primavera ProjectLink for updates, and challenges including inconsistent data formats and levels of detail across sub-schedules.
The document discusses NASA's implementation of earned value management (EVM) across its Constellation Program to coordinate work across multiple teams. It outlines the organizational structure, current target groups, and an EVM training suite. It also summarizes lessons learned and the need for project/center collaboration to integrate schedules horizontally and vertically.
This document summarizes a presentation about systems engineering processes for principle investigator (PI) mode missions. It discusses how PI missions face special challenges due to cost caps and lower technology readiness levels. It then outlines various systems engineering techniques used for PI missions, including safety compliance, organizational communication, design tools, requirements management, and lessons learned from past missions. Specific case studies from NASA's Explorers Program Office are provided as examples.
This document discusses changes to NASA's business practices for managing projects, including adopting a new acquisition strategy approach and implementing planning, programming, and budget execution (PPBE). The new acquisition strategy involves additional approval meetings at the strategic planning and project levels to better integrate acquisition with strategic and budgetary planning. PPBE focuses on analyzing programs and infrastructure to align with strategic goals and answer whether proposed programs will help achieve NASA's mission. The document also notes improvements in funds distribution and inter-center transfers, reducing the time for these processes from several weeks to only a few days.
Spaceflight Project Security: Terrestrial and On-Orbit/Mission
The document discusses security challenges for spaceflight projects, including protecting space assets from disruption, exploitation, or attack. It highlights national space policy principles of protecting space capabilities. It also discusses trends in cyber threats, including the increasing capabilities of adversaries and how even unskilled attackers can compromise terrestrial support systems linked to space assets if defenses are not strong. Protecting space projects requires awareness of threats, vulnerabilities, and strategies to defend, restore, and increase situational awareness of space assets and supporting systems.
Humor can positively impact many aspects of project management. It can improve communication, aid in team building, help detect team morale issues, and influence leadership, conflict management, negotiation, motivation, and problem solving. While humor has benefits, it also has risks and not all uses of humor are positive. Future research is needed on humor in multicultural teams, its relationship to team performance, how humor is learned, and determining optimal "doses" of humor. In conclusion, humor is a tool that can influence people and projects, but must be used carefully and spontaneously for best effect.
The recovery of Space Shuttle Columbia after its loss in 2003 involved a massive multi-agency effort to search a wide debris field, recover crew remains and evidence, and compensate local communities. Over 25,000 people searched over 680,000 acres, recovering 38% of Columbia's weight. Extensive engineering investigations were conducted to identify the causes of failure and implement changes to allow the safe return to flight of Discovery in 2005.
This document summarizes research on enhancing safety culture at NASA. It describes a survey developed to assess NASA's safety culture based on principles of high reliability organizations. The survey was tailored specifically for NASA and has been implemented to provide feedback and identify areas for improvement. It allows NASA to benchmark its safety culture within and across other industries pursuing high reliability.
This document summarizes a presentation about project management challenges at NASA Goddard Space Flight Center. The presentation outlines a vision for anomaly management, including establishing consistent problem reporting and analysis processes across all missions. It describes the current problem management approach, which lacks centralized information sharing. The presentation aims to close this gap by implementing online problem reporting and trend analysis tools to extract lessons learned across missions over time. This will help improve spacecraft design and operations based on ongoing anomaly experiences.
This document discusses leveraging scheduling productivity with practical scheduling techniques. It addresses scheduling issues such as unwieldy schedule databases and faulty logic. It then discusses taming the schedule beast through using a scheduler's toolkit, schedule templates, codes to manipulate MS Project data, common views/filters/tables, limiting constraints, and other best practices. The document provides examples of using codes and custom views/filters to effectively organize and display schedule information.
This document describes Ball Aerospace's implementation of a Life Cycle and Gated Milestone (LCGM) process to improve program planning, execution, and control across its diverse portfolio. The LCGM provides a standardized yet flexible framework that maps out program activities and products across phases. It was developed through cross-functional collaboration and introduced gradually across programs while allowing flexibility. Initial results showed the LCGM supported improved planning and management while aligning with Ball Aerospace's entrepreneurial culture.
This document discusses the importance of situation awareness (SA) for project team members. It defines SA as having three levels: perception of elements in the current situation, comprehension of the current situation, and projection of the future status. Good team SA is achieved by turning individual SAs into shared SA through communication. Teams with strong SA prepare more, focus on comprehending and projecting, and maintain awareness through techniques like questioning assumptions and seeking additional information.
This document discusses theories of leadership and how a project manager's leadership style may impact project success depending on the type of project. It outlines early hypotheses that a PM's competence, including leadership style, is a success factor on projects. It presents a research model linking PM leadership competencies to project success, moderated by factors like project type. Initial interviews found that leadership style is more important on complex projects, and different competencies are needed depending on if a project is technical or involves change. Certain competencies like communication skills and cultural sensitivity were seen as important for different project types and contexts.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Choosing The Best AWS Service For Your Website + API.pptx
Michael.hazen
1. Managing CPAS Architecture
and Requirements Volatility
NASA Project Management Challenge 2010
Michael Hazen
Jacobs Technology
Used with permission
2. Introduction
Complex systems frequently see
requirements and architecture volatility.
These kinds of volatility can be
aggravated when multiple contractors and
government agencies are working to
interdependent but loosely coupled
schedules.
Recent experience on CPAS is used to
illustrate some high value / low cost
systems engineering approaches to help
identify areas of volatility and to address
these kinds of issues in a direct manner.
2
3. Background
The Crew Exploration Vehicle (CEV) will
land using parachutes much like Apollo did
in the 1960s era.
NASA decided to provide the parachute
portion of the landing system, referred to
as CPAS (CEV Parachute Assembly
System) as GFE (Government Furnished
Equipment) based on NASA Johnson
Space Center (JSC) experience with the
X-38 and other parachute programs.
3
4. Background (continued)
JSC chose Jacobs Technology from ESCG
(Engineering and Science Contract Group)
to manage the overall program
development.
After a detailed selection program, Jacobs
chose Irvin Aerospace (now Airborne
Systems) to provide the parachutes and
mortars for CPAS.
4
6. Can we just re-use the Apollo design?
Some believe that the CPAS design should just be
an Apollo carbon copy. Some things have
changed since the 1960s technology used by
Apollo:
Use of modern materials (Kevlar, Vectran and
Spectra) that did not exist in the Apollo era
Drogue parachutes updated to Variable Porosity
Conical ribbon.
Main parachute design updated from ringsail
technology of the 1960s to the Irvin Quarter –
Spherical technology.
Numerous CPAS requirements were significantly
more demanding than those levied on Apollo.
6
7. Generation 1 CPAS Requirements and
Architecture
Requirements that significantly
exceeded those levied on Apollo:
Deployment envelope (max altitude of
72,000 feet vs. 40,000 ft.)
Unprecedented vibration levels
Reliability requirement twice that of
Apollo
The requirements management
paradigm has also changed since
the days of Apollo
7
9. System Dependencies (Ref. 2)
$
System
$ $
dependencies
within a
single
organization
$
Systems with interdependencies
Across multiple organizations
9
11. CPAS Mandate
Operational parachutes are required to
support early program Pad Abort tests.
Pad Abort 1 is scheduled for early 2010.
More parachutes required to support
Ascent Abort tests and early Orbital tests.
This mandate for CPAS was challenging
with the still draft and evolving parent
requirements for Orion.
11
12. Early Requirements Volatility
As the prime contractor prepared for a
System Requirements Review, CPAS
closely monitored the proposed content of
the SRD (System Requirements
Document)
As the Orion requirements were
proposed, lower level requirements were
articulated. The following slide illustrates
the state of CPAS parent requirements at
the CPAS SRR .
12
14. Meeting the Mandate !
Team Collaboration between CPAS and
Lockheed Martin was a big enabler to stop
the requirements “tail chasing” by coming
up with an explicit set of key requirements
that would allow CPAS to proceed with Gen
1 design
This set of requirements (without TBDs)
was labeled as an “Interim Requirements
Memo”, also dubbed “The Prouty Memo”,
named after its primary author from
Lockheed Martin, Chris Prouty. The memo
also included key interface requirements
14
15. Stakeholder Expectations Clear?
A separate assumptions document was
developed to:
Identify areas of disagreement with
interim parent requirements
Add needed details where existing
requirements were incomplete
Articulate perceived interface requirements
on the vehicle side of the interface
Serve as a stakeholder expectations
baseline, formally approved by the
program.
15
16. Beyond Stakeholder Expectations
Definition
Requirements and architecture volatility
can happen within a project too.
A clearly defined Architecture and
Requirements baseline to capture derived
requirements and architecture decisions is
essential
A Design Guidance & Direction Document
was developed to communicate key
technical decisions and ground rules
within the project and to ensure
stakeholders were kept fully informed.
16
17. EXAMPLE Design Guidance & Direction Document Entry
Main Chute Deployment Altitude
Design Item: 09-009a
Owner: CPAS SE&I IPT
Date: 05/07/2009
Issue: Main Chute Deployment Altitude
Guidance: CPAS will use 8,000 ft MSL to determine if it meets the
performance and functional requirements.
Discussion: The Aerodynamic Decelerator System specification, the
PTRS, and the assumptions document do not specify the deployment
altitude of the main parachutes. Without an assumed deployment
height on nominal and high altitude aborts, it is impossible to determine
if CPAS meets its functional and performance requirements. LM GN&C
indicated during the CPAS summit that 8,000 ft would likely be the main
chute deployment altitude.
Disposition: Use through PDR.
Modified: 06/15/09
Approval: Tim Fisher CPAS SE&I IPT Chair
17
18. Getting Program Buy-In
Getting CEV program concurrence at each
step of the requirements and architecture
volatility management process is a key
enabler.
The GFE Equipment and Materials Control
Panel (GEMCP) was empowered to
provide directives to CPAS to formalize
CPAS Generation 1 requirements.
This concurrence allowed parachute
development to proceed without undue
risk and with direct involvement of key
stakeholders.
18
19. Architecture Changes due to
Stability Concerns
Significant oscillations of the crew
module under drogues could result in
a “flipped” crew module which would
amount to a backwards (or apex
forward) parachute deployment.
Confirmed by early drop tests
Confirmed by extensive simulations
using evolving Orion aerodynamics
data base.
19
20. Step Back to Look at the “Big Picture”
A proposal was
brought forward for a
significantly different
parachute architecture
to address these
stability concerns.
20
22. Assess candidate architecture using
an “architecture first” approach (Ref. 3)
Elicit Architectural Requirements
Document the architecture
Analyze the architecture
Stakeholders / scenarios
Independent reviewers
Prove Architecture will meet stated
requirements
Realize the architecture
Maintain the architecture
22
23. Drogue Mortar & Mains Installation
Inside the Forward Bay Cover
24. Exercise architecture first approach
process
CPAS now owns FBC separation and
recontact avoidance.
Mains just too heavy for effective
deployment using forward bay cover – so
move to forward bay cover deployed pilot
chutes which in turn will deploy mains.
Benefits of moving to alternate
architecture starting to degrade.
IDAT team commissioned to sort out the
real “big picture” including not only CPAS,
but the entire vehicle.
24
26. Alternate Architecture Challenges
Integrated system challenges
were identified in baseline
design (606G) of Orion Entry,
Descent, and Landing (EDL)
architecture
First openly discussed at May 2009
“CPAS Summit”
Issues were symptomatic of a
highly coupled architecture
26
27. Alternate Architecture Issues
606G Baseline Issues
Main chute volume
FBC near-field re-contact
Drogue load mass threats (chute
inflation, mortar kick-loads)
Drogue harness extraction thru TPS
Aux chute packaging and deployment
Reliability – probability of loss of
crew
27
28. IDAT Recommendations
Forward Bay Volume
Backshell Outer Mold Line change from
32.5 to 30 degrees
Steel risers for both mains and
drogues to enable “any attitude”
parachute deployment
Forward Bay Cover – 6 Segments
Launch Abort System (LAS) Abort
Conops - Straight to Mains
28
29. Straight to Mains Sequence
Blunt End Forward
LAS Jettison
• A blunt-end- Segmented FBC
Jettison
forward LAS
jettison approach
was chosen for
the Generation 2
Straight to Main Deploy
(using chosen
Parachute
CPAS architecture Architecture)
• Used for Pad Main Line Stretch
aborts and low
altitude aborts
Touchdown,
Main Chute Cutaway, 29
CMUS Airbag Inflation
29
30. Parachute Architecture Selection
Parachute Architectures Considered
Modified Apollo (three point drogue harness)
3 Drogues 3 mains concept where each drogue
would extract one of the main chutes at the right
time
Ultimately selected “classic Apollo”
30
31. Classic Apollo
Drogues
2 each attached to
flower pot gusset
Each cut away with
single dual-initiated
cutter
Main parachutes
3 each attached to
flower pot gusset
Each deployed by use
of individual mortar
deployed pilot
parachutes
31
31
32. Classic Apollo?
Isn’t that where we were when we started
this journey for CPAS?
Yes and No – we did not start with an
integrated design solution and architecture.
Smooth sailing now?
No – we still have some unprecedented
requirements that will likely result in additional
requirements and architecture volatility
Using test planning to explicitly address key
risks (not only identify the risks but take
concrete action to abate)
32
33. Role of Testing in Managing
Requirements and Architecture Volatility
33
34. Test and Verification influences on
requirements & architecture volatility
Engineering development unit tests are
key in validating requirements and
candidate architectures
Extensive Monte Carlo simulations are
anchored by test data.
Assessment of which tests are architecture
specific helps to zero in on testability aspects
of candidate architectures
Early validation of performance
requirements revealed several problems
and risks
34
35. Risk Assessment
Extensive brainstorming sessions
were conducted with grey beards
from the Apollo era and parachute
experts from both industry and the
government
This enabled identification of
requirements and architecture
attributes which posed the greatest
risk.
35
36. Example architecture and
requirements risk areas identified
Architecture
High Risk: Drogue Harness Deploy,
Pilot off-angle deployment
Medium Risk: Drogue confluence, Pilot
deployment and inflation
Low Risk: Two drogue chute / two aux
chute performance
36
37. Example architecture and
requirements risk areas identified
Requirements
High Risk: Drogue High Altitude, two
mains
Medium Risk: high body rate
deployment, riser abrasion, skipped
reefing stages
Low Risk: Main riser twist, one drogue
and two mains
37
38. Requirements related enablers
Master Verification Plan –ask
specifically “how can that
requirement be verified?”
NESC proposed statistical “design of
experiments” test approach
associated requirements impact
NESC proposed component level
verification assessment – are end
item specs needed?
38
39. Looking Ahead
A stakeholder-wide Entry Descent
and Landing Focus Integration
Team (EDL FIT) has been
established to ensure future design
decisions reflect truly integrated
solutions
39
40. Closing Comments
Requirements & architecture volatility is
part of the job
The techniques described in this
presentation helped CPAS to ensure the
right system (right requirements and
architecture) is built BEFORE anyone’s life
depends on the successful operation of
CPAS
Part of Systems Engineering’s role is acting
as the project’s “technical conscience” as
requirements and architecture volatility
issues are addressed
40
41. References
1. NPR 7123.1A, NASA Systems Engineering
Processes and Requirements. March 2007
2. Department of Defense System of
Systems Challenges, JSC Systems
Engineering Seminar Presentation.
Dr. Judith Dahlman. August 2007
3. Architecture First Approach, DACS
(Department of Defense Data & Analysis
Center for Software)
https://www.goldpractices.com/practices/
afa/index.php
41