This document discusses the development of uncertainty factors from historical NASA projects. It presents analysis of cost and schedule data from 60 completed NASA science missions from 1990 to 2015. The analysis found most projects experienced cost growth, with over half having growth rates of 20% or more. Based on this data, the authors developed new uncertainty factors specifically for NASA science missions to more accurately capture project risks for planning and estimation purposes.
This report summarizes a study on tools for psychological support during long-duration space exploration missions. It identifies challenges crews may face, such as isolation and confinement. It develops a Psychological Issues Matrix to categorize interacting factors. It also defines a new Embedded Psychological Support Integrated for Long-duration missions (EPSILON) model. This model incorporates prevention, monitoring and resolution approaches. Finally, it recommends priority tools for development based on workshops with experts. These tools aim to help crews effectively address psychological issues.
The document discusses modeling mission operations to reduce risk for NASA's Constellation Program. It begins with defining the goals of incorporating new technologies into operations while controlling risk and cost. It then discusses challenges like the need for increased automation and streamlined systems. The solution involved a collaboration between JSC and ARC to develop a simulation of shuttle operations using BRAHMS modeling tools. This prototype showed benefits like reducing time spent on mirroring tasks from over 5% to under 0.5% of a shift. The conclusions were that BRAHMS feasibility for automating complex MCC tasks was verified and could provide insights into processes while assessing risk.
The document discusses improving life-cycle cost management of NASA's Discovery and New Frontiers spacecraft missions. It summarizes a study that identified several factors that contribute to cost overruns in these programs, including inadequate consideration of review findings, ineffective management structures, lack of integrated project schedules, insufficient project oversight, inexperienced project teams, inadequate mission replanning, unrealistic heritage and technology assumptions, and insufficient planning for operations and autonomy systems. The study provides recommendations to address these issues and better manage costs over the full mission life cycle.
Gary Tigerman's science fiction novel The Orion Protocol follows former Apollo astronauts Commander Jake Deaver and Colonel Augie Blake who have kept secret their findings from the Moon for nearly 30 years. Journalist Angela Browning receives a mysterious computer disk showing images from Mars, contradicting NASA's report that the Mars Observer spacecraft was lost. The astronauts and journalist investigate Project Orion, a supposed space defense system, and whether the US government has concealed extraterrestrial life or findings from the public. The dialogue-driven story examines the relationship between the government and press regarding transparency.
This document discusses the impact of mood and emotions on team performance. It defines mood as a relatively lasting emotional state compared to emotions, which are short-lived reactions to stimuli. Mood and emotions influence soft skills like leadership, team climate, motivation, and communication as well as hard skills like decision making. Managers can influence mood and emotions through their own displays, feedback, celebrations, monitoring team climate, and using humor. Environmental factors like lighting, air quality, temperature, and ergonomics also impact mood. The document concludes that mood and emotions significantly impact work and managers have tools to shape them.
Blythe ortiz7120 5e handbooks 2 15-2012 finalNASAPMC
This document discusses updates to NASA guidance documents for program and project management. The NPR 7120.5 has been streamlined and implementation guidance is now contained in a new Program and Project Management Handbook and an updated Standing Review Board Handbook. These handbooks provide best practices and guidelines to implement the requirements of NPR 7120.5. The speakers discuss the status and future plans for completing these handbooks, including aligning them with the revised NPR 7120.5E set to be released in summer 2012. The handbooks are intended to provide practical support for program/project managers in satisfying NASA's management requirements.
The document provides a summary of the Orion program from FY05 to FY11, highlighting key milestones such as design phases, spacecraft development, naming of the Multi-Purpose Crew Vehicle, parachute and launch abort system tests. It also outlines the Exploration Flight Test-1, describing the 2 revolutions and insertion trajectory. Furthermore, it presents Lockheed Martin's acoustic and vibration testing facilities and visualization of the vibration tests. Lastly, it introduces potential future exploration missions using Orion as part of NASA's stepping stones approach to explore Mars.
NASA Orion Multi Purpose Crew Vechicle - Full ExplanationGokul Lakshmanan
The document summarizes key components and technologies used in NASA's Orion Multi-Purpose Crew Vehicle, including the crew and service modules, thermal protection system, radiation shielding, and launch abort system. Orion will carry crews of up to four astronauts beyond low Earth orbit using advanced technologies like a glass cockpit, auto-docking capabilities, and improved waste management facilities. Its service module will provide power, oxygen, water recycling and other life support functions to sustain crews for up to 8 months.
This report summarizes a study on tools for psychological support during long-duration space exploration missions. It identifies challenges crews may face, such as isolation and confinement. It develops a Psychological Issues Matrix to categorize interacting factors. It also defines a new Embedded Psychological Support Integrated for Long-duration missions (EPSILON) model. This model incorporates prevention, monitoring and resolution approaches. Finally, it recommends priority tools for development based on workshops with experts. These tools aim to help crews effectively address psychological issues.
The document discusses modeling mission operations to reduce risk for NASA's Constellation Program. It begins with defining the goals of incorporating new technologies into operations while controlling risk and cost. It then discusses challenges like the need for increased automation and streamlined systems. The solution involved a collaboration between JSC and ARC to develop a simulation of shuttle operations using BRAHMS modeling tools. This prototype showed benefits like reducing time spent on mirroring tasks from over 5% to under 0.5% of a shift. The conclusions were that BRAHMS feasibility for automating complex MCC tasks was verified and could provide insights into processes while assessing risk.
The document discusses improving life-cycle cost management of NASA's Discovery and New Frontiers spacecraft missions. It summarizes a study that identified several factors that contribute to cost overruns in these programs, including inadequate consideration of review findings, ineffective management structures, lack of integrated project schedules, insufficient project oversight, inexperienced project teams, inadequate mission replanning, unrealistic heritage and technology assumptions, and insufficient planning for operations and autonomy systems. The study provides recommendations to address these issues and better manage costs over the full mission life cycle.
Gary Tigerman's science fiction novel The Orion Protocol follows former Apollo astronauts Commander Jake Deaver and Colonel Augie Blake who have kept secret their findings from the Moon for nearly 30 years. Journalist Angela Browning receives a mysterious computer disk showing images from Mars, contradicting NASA's report that the Mars Observer spacecraft was lost. The astronauts and journalist investigate Project Orion, a supposed space defense system, and whether the US government has concealed extraterrestrial life or findings from the public. The dialogue-driven story examines the relationship between the government and press regarding transparency.
This document discusses the impact of mood and emotions on team performance. It defines mood as a relatively lasting emotional state compared to emotions, which are short-lived reactions to stimuli. Mood and emotions influence soft skills like leadership, team climate, motivation, and communication as well as hard skills like decision making. Managers can influence mood and emotions through their own displays, feedback, celebrations, monitoring team climate, and using humor. Environmental factors like lighting, air quality, temperature, and ergonomics also impact mood. The document concludes that mood and emotions significantly impact work and managers have tools to shape them.
Blythe ortiz7120 5e handbooks 2 15-2012 finalNASAPMC
This document discusses updates to NASA guidance documents for program and project management. The NPR 7120.5 has been streamlined and implementation guidance is now contained in a new Program and Project Management Handbook and an updated Standing Review Board Handbook. These handbooks provide best practices and guidelines to implement the requirements of NPR 7120.5. The speakers discuss the status and future plans for completing these handbooks, including aligning them with the revised NPR 7120.5E set to be released in summer 2012. The handbooks are intended to provide practical support for program/project managers in satisfying NASA's management requirements.
The document provides a summary of the Orion program from FY05 to FY11, highlighting key milestones such as design phases, spacecraft development, naming of the Multi-Purpose Crew Vehicle, parachute and launch abort system tests. It also outlines the Exploration Flight Test-1, describing the 2 revolutions and insertion trajectory. Furthermore, it presents Lockheed Martin's acoustic and vibration testing facilities and visualization of the vibration tests. Lastly, it introduces potential future exploration missions using Orion as part of NASA's stepping stones approach to explore Mars.
NASA Orion Multi Purpose Crew Vechicle - Full ExplanationGokul Lakshmanan
The document summarizes key components and technologies used in NASA's Orion Multi-Purpose Crew Vehicle, including the crew and service modules, thermal protection system, radiation shielding, and launch abort system. Orion will carry crews of up to four astronauts beyond low Earth orbit using advanced technologies like a glass cockpit, auto-docking capabilities, and improved waste management facilities. Its service module will provide power, oxygen, water recycling and other life support functions to sustain crews for up to 8 months.
The Budget Control Act of 2011 will force significant budget reductions at NASA through automatic spending cuts (sequestration) beginning in 2013. If the cuts are around 9% as expected, NASA could lose $1.6 billion in funding for fiscal year 2013. Congress and the appropriations committees have expressed concerns about NASA's cost overruns and poor project management. For NASA to protect its funding in the future, it will need to improve its management and accountability to demonstrate that it is a good steward of taxpayer money.
This document discusses EVMS certification and provides an overview of earned value management. It contains the following key points:
1) The objectives are to provide perspective on the EVMS certification challenge and identify areas of focus to position an organization for successful certification.
2) EVMS certification evaluates an organization's compliance with 32 ANSI guidelines across stakeholders, processes, baseline development, status and forecasting, metrics and reports, management, and corrective action.
3) Successful certification depends on having a documented EVMS that meets all guidelines, projects executing the documented system, and an adequate surveillance plan to ensure sustainability.
The document summarizes NASA's Orion spacecraft and its Exploration Mission-1 (EM-1) test flight. Some key points:
- Orion will take astronauts farther into space than ever before, including to asteroids and Mars. It is designed to transport crew to and from the International Space Station and facilitate deep space exploration for decades.
- EM-1 will launch Orion on NASA's new Space Launch System rocket and send it around the moon without crew to test the spacecraft. The mission will deploy several small satellites and help check Orion's performance.
- Orion consists of crew, service, and launch abort modules and can carry more astronauts than Apollo. Its first uncrewed test flight was successful in 2014. Future missions will
Harper Lee's novel To Kill a Mockingbird is set in Maycomb, Alabama during the 1930s. It is narrated by six-year-old Scout Finch and focuses on her father Atticus, a lawyer who defends a black man named Tom Robinson against a rape charge. The novel explores themes of racial injustice and the loss of childhood innocence. It describes the segregated society of the novel and establishes Atticus as a morally upright lawyer defending a black man against racial prejudice.
Edgar Rice Burroughs' John Carter The Mars Trilogy Book Reportjamarch
1) Confederate officer John Carter is transported to the planet Barsoom (Mars) where he finds himself in the middle of an epic conflict.
2) On Mars, Carter allies with the Green Martian Tars Tarkas and falls in love with the Martian princess Dejah Thoris.
3) Over the course of three books, Carter helps lead revolutions to overthrow evil forces and save the Martian people, utilizing his enhanced strength from the lower Mars gravity.
This document provides a study guide for William Shakespeare's play Romeo and Juliet. It includes lists of major and minor characters, a brief overview of the plot and setting, and descriptions of key themes like love, death, and violence. It also discusses symbols in the play such as darkness and light, flowers, and the family feud between the Montagues and Capulets. The guide is intended to help students summarize and understand the most important elements of the famous tragedy.
The document presents a strategy proposed by NASA's AR&D Community of Practice to address NASA's history of developing autonomous and automated rendezvous and docking (AR&D) capabilities for individual programs rather than taking an integrated agency approach. The strategy calls for developing an "AR&D Warehouse" - a library of reusable AR&D hardware and software components with standardized interfaces. This would provide 80% of the AR&D capability needed for future missions at much lower costs compared to current single-program approaches. The strategy argues that an integrated, evolutionary development approach coordinated across NASA centers is needed to realize the benefits of the Warehouse concept.
The document discusses the need for an integrated NASA strategy for autonomy and automation (AR&D) capabilities. It notes that NASA programs currently spend up to 10 times more than necessary and take twice as long to develop AR&D capabilities by "reinventing the wheel" for each program. The NASA AR&D Community of Practice recommends developing an "AR&D Warehouse" of reusable hardware and software components to reduce costs and development time across programs. An integrated agency strategy requiring some initial investment could save over $500 million and 16 years of development over the next decade.
The document discusses NASA's status on the GAO's high-risk list for acquisition management and the initiatives NASA is taking to address this issue. It outlines NASA's definition of success, including maintaining cost and schedule performance for projects. It also discusses the impact on project management, such as defining supporting measures, implementing reporting processes, and increasing management oversight to monitor performance against the goals.
The document discusses managing external relations for NASA project managers. It outlines NASA's various customers and stakeholders that managers must communicate with, including other NASA centers, Congress, the media and the public. It then details the speaker's experience managing various NASA projects, like the Space Shuttle Main Engine and the Constellation program. A key lesson is that effective external communication is imperative for managing projects and maintaining relationships with stakeholders.
The document discusses the use of probabilistic risk assessment (PRA) in decision making for the Space Shuttle program. It provides background on the development of the Shuttle PRA since 1987. Key information for management includes clearly presenting the PRA analysis and assumptions, limitations, and estimates of uncertainty to support risk-informed decisions.
The summary data from assessments could help suppliers identify common issues and areas for improvement. Sharing this information supports continuous improvement across the supply chain.
This document provides an overview of NASA's Exploration Systems Development program, which is developing the Space Launch System (SLS), Orion Multi-Purpose Crew Vehicle (MPCV), and associated ground systems. It discusses the analysis of alternatives that was conducted to select these systems and an incremental approach to deliver beyond low Earth orbit exploration capabilities. Key decisions included validating Orion as the crew vehicle and selecting a heavy-lift launch vehicle concept using hydrogen and rocket propellant technologies.
Organizations around the world are facing a "data tsunami" as next-generation sensors produce enormous volumes of Earth observation data. Come learn how NASA is leveraging AWS to efficiently work with data and computing resources at massive scales. NASA is transforming its Earth Sciences EOSDIS (Earth Observing System Data Information System) program by moving data processing and archiving to the cloud. NASA anticipates that their Data Archives will grow from 16PB today to over 400PB by 2023 and 1 Exabyte by 2030, and they are moving to the cloud in order to scale their operations for this new paradigm. Learn More: https://aws.amazon.com/government-education/
Unifarm presentation @ space solutions 20121204.pptxTamme van der Wal
This document discusses the set-up of a GNSS user forum for agricultural users. It provides background on the estimated economic impact of GNSS technologies, such as satellite navigation, and outlines key application areas for GNSS in agriculture including production efficiency, farm management, logistics, and license to operate. The document invites participants to join the user forum and engage in discussions around advancing the use of GNSS technologies like EGNOS to improve precision agriculture and compliance monitoring in the agricultural sector.
Operations control centers are evolving from dedicated missions to support multiple missions and customers more efficiently. Control center management struggles to accurately model resource requirements and costs for providing mission services. A proposed solution is a mission resource/capability analyzer tool that uses a visual interface in Excel to estimate costs across different operational scenarios, identify resource shortfalls, and support budget planning through what-if analyses of resource usage and funding. The tool would build off a previous budget analysis tool by allowing automated selection of predefined common service characteristics and expansion to detailed monthly resource needs.
Presentation by Chris Lennard.
CCAFS workshop titled "Using Climate Scenarios and Analogues for Designing Adaptation Strategies in Agriculture," 19-23 September in Kathmandu, Nepal.
The Constellation Program is transitioning from defining requirements to preliminary design and development of hardware and software for its systems. It leverages a nationwide team from NASA and industry. This team is focused on designing and incrementally integrating and verifying a set of increasingly capable systems over the next decade to meet exploration goals of completing the ISS, retiring the Shuttle, developing Orion and Ares launch vehicles, and returning to the Moon by 2020.
The document provides a market feasibility study for developing Palm Island. It analyzes several quantitative tools:
1. Forecasting tourism growth to Palm Island, predicting over 26,000 tourists in 2011.
2. Calculating market penetration rates and potential customer segments by age group, showing highest potential among 30-40 year olds.
3. Using control charts to determine if projected tourism numbers fall within feasible ranges, finding 3,200 tourists is feasible.
4. Applying predictive gravity modeling to estimate total potential sales across territories, but noting feasibility may differ by location.
5. Proposing an assignment model to determine the most feasible territory for a new shopping mall.
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 Budget Control Act of 2011 will force significant budget reductions at NASA through automatic spending cuts (sequestration) beginning in 2013. If the cuts are around 9% as expected, NASA could lose $1.6 billion in funding for fiscal year 2013. Congress and the appropriations committees have expressed concerns about NASA's cost overruns and poor project management. For NASA to protect its funding in the future, it will need to improve its management and accountability to demonstrate that it is a good steward of taxpayer money.
This document discusses EVMS certification and provides an overview of earned value management. It contains the following key points:
1) The objectives are to provide perspective on the EVMS certification challenge and identify areas of focus to position an organization for successful certification.
2) EVMS certification evaluates an organization's compliance with 32 ANSI guidelines across stakeholders, processes, baseline development, status and forecasting, metrics and reports, management, and corrective action.
3) Successful certification depends on having a documented EVMS that meets all guidelines, projects executing the documented system, and an adequate surveillance plan to ensure sustainability.
The document summarizes NASA's Orion spacecraft and its Exploration Mission-1 (EM-1) test flight. Some key points:
- Orion will take astronauts farther into space than ever before, including to asteroids and Mars. It is designed to transport crew to and from the International Space Station and facilitate deep space exploration for decades.
- EM-1 will launch Orion on NASA's new Space Launch System rocket and send it around the moon without crew to test the spacecraft. The mission will deploy several small satellites and help check Orion's performance.
- Orion consists of crew, service, and launch abort modules and can carry more astronauts than Apollo. Its first uncrewed test flight was successful in 2014. Future missions will
Harper Lee's novel To Kill a Mockingbird is set in Maycomb, Alabama during the 1930s. It is narrated by six-year-old Scout Finch and focuses on her father Atticus, a lawyer who defends a black man named Tom Robinson against a rape charge. The novel explores themes of racial injustice and the loss of childhood innocence. It describes the segregated society of the novel and establishes Atticus as a morally upright lawyer defending a black man against racial prejudice.
Edgar Rice Burroughs' John Carter The Mars Trilogy Book Reportjamarch
1) Confederate officer John Carter is transported to the planet Barsoom (Mars) where he finds himself in the middle of an epic conflict.
2) On Mars, Carter allies with the Green Martian Tars Tarkas and falls in love with the Martian princess Dejah Thoris.
3) Over the course of three books, Carter helps lead revolutions to overthrow evil forces and save the Martian people, utilizing his enhanced strength from the lower Mars gravity.
This document provides a study guide for William Shakespeare's play Romeo and Juliet. It includes lists of major and minor characters, a brief overview of the plot and setting, and descriptions of key themes like love, death, and violence. It also discusses symbols in the play such as darkness and light, flowers, and the family feud between the Montagues and Capulets. The guide is intended to help students summarize and understand the most important elements of the famous tragedy.
The document presents a strategy proposed by NASA's AR&D Community of Practice to address NASA's history of developing autonomous and automated rendezvous and docking (AR&D) capabilities for individual programs rather than taking an integrated agency approach. The strategy calls for developing an "AR&D Warehouse" - a library of reusable AR&D hardware and software components with standardized interfaces. This would provide 80% of the AR&D capability needed for future missions at much lower costs compared to current single-program approaches. The strategy argues that an integrated, evolutionary development approach coordinated across NASA centers is needed to realize the benefits of the Warehouse concept.
The document discusses the need for an integrated NASA strategy for autonomy and automation (AR&D) capabilities. It notes that NASA programs currently spend up to 10 times more than necessary and take twice as long to develop AR&D capabilities by "reinventing the wheel" for each program. The NASA AR&D Community of Practice recommends developing an "AR&D Warehouse" of reusable hardware and software components to reduce costs and development time across programs. An integrated agency strategy requiring some initial investment could save over $500 million and 16 years of development over the next decade.
The document discusses NASA's status on the GAO's high-risk list for acquisition management and the initiatives NASA is taking to address this issue. It outlines NASA's definition of success, including maintaining cost and schedule performance for projects. It also discusses the impact on project management, such as defining supporting measures, implementing reporting processes, and increasing management oversight to monitor performance against the goals.
The document discusses managing external relations for NASA project managers. It outlines NASA's various customers and stakeholders that managers must communicate with, including other NASA centers, Congress, the media and the public. It then details the speaker's experience managing various NASA projects, like the Space Shuttle Main Engine and the Constellation program. A key lesson is that effective external communication is imperative for managing projects and maintaining relationships with stakeholders.
The document discusses the use of probabilistic risk assessment (PRA) in decision making for the Space Shuttle program. It provides background on the development of the Shuttle PRA since 1987. Key information for management includes clearly presenting the PRA analysis and assumptions, limitations, and estimates of uncertainty to support risk-informed decisions.
The summary data from assessments could help suppliers identify common issues and areas for improvement. Sharing this information supports continuous improvement across the supply chain.
This document provides an overview of NASA's Exploration Systems Development program, which is developing the Space Launch System (SLS), Orion Multi-Purpose Crew Vehicle (MPCV), and associated ground systems. It discusses the analysis of alternatives that was conducted to select these systems and an incremental approach to deliver beyond low Earth orbit exploration capabilities. Key decisions included validating Orion as the crew vehicle and selecting a heavy-lift launch vehicle concept using hydrogen and rocket propellant technologies.
Organizations around the world are facing a "data tsunami" as next-generation sensors produce enormous volumes of Earth observation data. Come learn how NASA is leveraging AWS to efficiently work with data and computing resources at massive scales. NASA is transforming its Earth Sciences EOSDIS (Earth Observing System Data Information System) program by moving data processing and archiving to the cloud. NASA anticipates that their Data Archives will grow from 16PB today to over 400PB by 2023 and 1 Exabyte by 2030, and they are moving to the cloud in order to scale their operations for this new paradigm. Learn More: https://aws.amazon.com/government-education/
Unifarm presentation @ space solutions 20121204.pptxTamme van der Wal
This document discusses the set-up of a GNSS user forum for agricultural users. It provides background on the estimated economic impact of GNSS technologies, such as satellite navigation, and outlines key application areas for GNSS in agriculture including production efficiency, farm management, logistics, and license to operate. The document invites participants to join the user forum and engage in discussions around advancing the use of GNSS technologies like EGNOS to improve precision agriculture and compliance monitoring in the agricultural sector.
Operations control centers are evolving from dedicated missions to support multiple missions and customers more efficiently. Control center management struggles to accurately model resource requirements and costs for providing mission services. A proposed solution is a mission resource/capability analyzer tool that uses a visual interface in Excel to estimate costs across different operational scenarios, identify resource shortfalls, and support budget planning through what-if analyses of resource usage and funding. The tool would build off a previous budget analysis tool by allowing automated selection of predefined common service characteristics and expansion to detailed monthly resource needs.
Presentation by Chris Lennard.
CCAFS workshop titled "Using Climate Scenarios and Analogues for Designing Adaptation Strategies in Agriculture," 19-23 September in Kathmandu, Nepal.
The Constellation Program is transitioning from defining requirements to preliminary design and development of hardware and software for its systems. It leverages a nationwide team from NASA and industry. This team is focused on designing and incrementally integrating and verifying a set of increasingly capable systems over the next decade to meet exploration goals of completing the ISS, retiring the Shuttle, developing Orion and Ares launch vehicles, and returning to the Moon by 2020.
The document provides a market feasibility study for developing Palm Island. It analyzes several quantitative tools:
1. Forecasting tourism growth to Palm Island, predicting over 26,000 tourists in 2011.
2. Calculating market penetration rates and potential customer segments by age group, showing highest potential among 30-40 year olds.
3. Using control charts to determine if projected tourism numbers fall within feasible ranges, finding 3,200 tourists is feasible.
4. Applying predictive gravity modeling to estimate total potential sales across territories, but noting feasibility may differ by location.
5. Proposing an assignment model to determine the most feasible territory for a new shopping mall.
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.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
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.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Amer v2
1. DEVELOPMENT OF UNCERTAINTY FACTORS FROM
HISTORICAL NASA PROJECTS
Dr. Tahani Amer, OE/IPAO NASA-HQ
Dr. Will Jarvis, OE/IPAO NASA-HQ
Dr. Ariel Pinto, Old Dominion University
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage.
2. Project Background
• Uncertainty analysis should be performed to capture the
program risks.
• NASA has been using available uncertainty factors from
Aerospace, Air Force, and Booz Allen Hamilton.
• NASA has no insight into the development of these factors,
which can lead to unrealistic risks in most NASA projects.
• SRB analysis requires cost growth factors that are
transparent and based on recent NASA experience.
• Better estimation and prediction of missions cost is
needed early on.
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 2
3. Data Collection Methodology
• NASA Fiscal Year Budget Estimates
• Cost Analysis Data Requirement (CADRe)
• Government Accountability Office Reports
• NASA Personal- IPAO/CAD/SMD
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 3
4. Data Collection Model
Budget Report
CADRe Report
Analysis- Recheck
Data Set
Assess Assess Assess
Analysis- Recheck
GAO Report
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 4
5. Source of Data
FY 2009 Budget
February 4, 2008
Amer DENG 5
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 5
6. Data Sampling Criteria
• Difficulty in collecting accurate data – limited dataset
• Criteria
– Science Mission Projects
– Developmental Phase
– Only cost data
– Use CARDe data as final for completed Missions
– For active missions: used in search of credible earliest available
and latest available estimates. Errors probably exist because
some projects are still in development and continue to evolve
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 6
7. Summary of NASA Missions Investigated
Active
Completed Missions Missions
NEAR MER HESSI EOS-Aqua AIM JUNO
LUNAR MRO GALEX EOS-Aura DAWN AQUARIUS
PROSPECTOR FAST SWIFT LANDSAT-7 PHOENIX LDCM
GENESIS SWAS GRACE TRMM GLAST NPP
MESSENGER TRACE CLOUDSAT TIMED KEPLER GPM
MARS WIRE CALIPSO GRAVITY SDO MMS
PATHFINDER DS-1 PROBE B WISE JWST
ACE
STARDUST EO-1 THEMIS NEW MSL
FUSE
CONTOUR SIRTF HETE-II HORIZONS GLORY
IMAGE STEREO GRAIL
DEEP IMPACT SORCE LRO
MAP
MGS ICESAT OCO
MCO/MPL
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 7
8. Initial & Final Cost for 50 Completed
Projects and Cost Growth Percentage
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 8
9. 60 NASA Missions - Historical Data
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 9
10. Mission Cost Growth Histogram
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 10
11. NASA & DOD Distribution
14
12
10
Number of Project
8
6
4
2
0
-21-0% 0 -10% 10-20% 20-30% 30-40% 40-50% 50-60% 60-70% >70%
Permission from McCrillis, DOD
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 11
12. 60 NASA Missions
14
12
10
Number of Project
8
6
4
2
0
- 21-0% 0 -10% 10-20% 20-30% 30-40% 40-50% 50-60% 60-70% >70%
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 12
13. Reasons for Cost Growth
• The major categories for cost growth:
– Overly optimistic and unrealistic initial cost estimates
– Project instability and funding issues
– Problems with development of instruments and other spacecraft
technology
– Launch service issues
– “Stuff” Happens
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 13
14. Uncertainly Factors from non-NASA Missions
Aerospace Air Force
Level Optimistic Most Likely Pessimistic
Low 0.95 1 1.1
Low Plus 0.96 1 1.23
Moderate 0.97 1 1.36
Moderate Plus 0.98 1 1.49
High 0.98 1 1.61
High Plus 0.99 1 1.74
Very High 1 1 1.87
Very High Plus 1 1 2
Booz Allen Hamilton
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 14
15. NASA Data & Air Force UF
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 15
16. NASA Data & Aerospace UF
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 16
17. NASA Data & BAH UF
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 17
18. Development of Distribution-54
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 18
19. Development of Distribution-44
0.12
0.11
0.1
0.09
0.08
0.07
PDF
0.06
0.05
0.04
0.03
0.02
0.01
0
0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150
Cost Growth (%)
Lognormal
µ= 3.03
F(X) = σ= 1.08
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 19
20. More Test Runs
• All data including Project A & B (A- Data), 54 missions.
• All data excluding Project A & B (B- Data), 52 missions.
• All completed missions (C-Data), 44 missions.
• All data less than 100% cost growth (D- Data).
0.12 Type of Data µ =Mean σ= Std
0.11 Dev.
0.1
0.09
A - Data 3.01 1.18
0.08
20.3 %
0.07
B - Data 2.92= 1.11
PDF
0.06
18.5 %
0.05
C - Data 3.03 1.08
0.04
0.03
Mean=37.08
0.02
Median= 20.7
0.01 Std. Dev.= 55.14
0
0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150
D-Data 2.85 1.07
Cost Growth (%)
17.3%
October 7, 2011 Lognormal
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 20
21. Selected Distribution
• The lognormal distribution is the most suitable distribution that
the cost estimator can use to perform an uncertainty analysis for
the NASA data.
• The quality of the fit of two tests:
– The Kolmogorov-test 0.032
– The Anderson-Darling test 0.028
0.024
0.02
PDF
0.016
0.012
0.008
0.004
0
0 50 100
Cost Growth (%)
Lognormal (1.08; 3.03)
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 21
22. Recommended UFs
Uncertainty
Level of Risk Factors
No- Risk
Adjusted Conservative Aggressive
Moderate (10-30%) 1 1.1 1.3
High (30-75%) 1 1.3 1.75
Very High (>75%) 1 1.75 2.5
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 22
23. UFs w/Conservative High Risk Level
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 23
24. UFs w/Aggressive Moderate Risk Level
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 24
25. Guideline to UFs
• Cost Analyst Judgment
• Mission Complexity: Number of Instruments,
Technical Development
• Heritage Level
• Partners Performance
• Mission Visibility: International & Commercial
• Similarity of Missions
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 25
26. Comparison of UFs
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 26
27. UFs ------Test Case
– Project A---
• Development Cost as of 2006 ~ $969 M
• Development Cost as of 2011 ~ $1.8 B
• Apply NUFs:
– Make the following assumptions:
» High Risk Mission (10 instruments, new Technology, Planetary)
» Aggressive Risk
» Select a range from NUFs, Table 20, 1.75-2.5
• Expected development estimate range: 1.69- $2.42 B
• Other factors estimates:
– AF (1.61- 1.74) $1.56B- $1.69 B, which is lower than the current
actual development cost.
– Aerospace (2.05-2.5) $1.99- $2.52 B, which is much higher then
expected estimate from the low range. Note: LCC is @$2.5B.
– BAH (1.9-2.10) $1.84- $2.03 B, which is might be closer to the
expected development cost . Note: see section 3.3 for these
factors interpolation from BAH table.
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 27
28. UFs Test Case
970 1.2 1.4 1.8 2.2 2.6 2.8
Current EST.
$1.69- $2.42B
. UF
$1.56B- $1.69B AF
$1.99- $2.52B AS
$1.84- $2.03B BAH
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 28
29. Conclusions
• This research provides an important contribution to the
discipline of cost estimating.
• It has developed a solid database of actual cost growth
history and adds some statistical rigor to the derivation
of cost growth factors based on the data.
• Thoughtful execution and effective monitoring of the
NUFs will improve the cost estimating.
• Additionally, it is expected that this work will be
referenced often for independent cost estimates,
correction of advocacy-bias in project-generated
estimates, and other programmatic work.
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 29
30. Point Taken
• The greatest benefit of this research is providing a
proactive approach to make a quick cost estimating as
in back of envelope by:
– Program Managers
– Decision Makers
– Congressional Staffer
– Cost analysts
– Awareness and reference to Standard Review Board
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 30
31. Future Work
• Increase the number of historical missions captured in
the database.
• Validate UFs with more available actual cost data.
• Test the UFs for missions in various life-cycle phases.
• Develop a more adaptable tool for NUFs.
• Accept the UFs by the cost analysis’ community for
implementation.
• Develop Agency standard.
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 31
32. Backup
NASA Program Management Challenge 2012 This briefing is for status only and does not represent complete release of usage. 32