The goal of implementing Earned Value Management (EVM) in the EVA Systems Project Office (ESPO) was to utilize existing products and processes where possible to make them compatible with EVM. The presentation covered the Work Breakdown Structure, Organizational Breakdown Structure, Responsibility Assignment Matrix, Control Accounts, Work Packages, Planning Packages, Integrated Master Plan, and schedule integration using Primavera and Deltek Cobra tools. It also discussed interfaces with other processes and EVM integration with the prime contractor.
The document discusses a center-wide facilities planning review conducted by NASA's Johnson Space Center from 2007-2009. The review aimed to capture a comprehensive facilities listing, assess budgets tied to facilities utilization, and support risk-based decisions regarding facility closeouts, consolidations and funding. In FY2007, the initial assessment was conducted through interviews and spreadsheets. This identified a need for more input from facility planners and management. In subsequent years, a database called JFReD was created to better capture and report facilities information to support strategic planning across the agency. The review process continued to be refined with the goals of comprehensive data collection and linking facilities utilization to overall center master planning.
The document discusses integrated testing plans for the Constellation program at KSC. It describes plans to conduct Multi-Element Integrated Tests (MEITs) to test interactions between Constellation flight elements launched on different vehicles before they are integrated in space. MEITs found significant problems in previous programs that could have impacted safety and mission objectives. The tests are intended to reduce risks by identifying issues early.
The Constellation Space Transportation Planning Office (CSTP) manages the production, launch preparations, mission operations, and recovery of the Orion/Ares vehicle configuration that will transport crew to and from the International Space Station. The CSTP oversees the entire work cycle from element production to final disposition. It uses an organizational structure with divisions for program integration, planning and control, systems engineering, and operations. The presentation provides an overview of CSTP and updates on its projects and forward work.
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.
The document describes NASA's Baseline Performance Review (BPR) process. The BPR provides NASA senior leadership with objective information on the performance of NASA programs, projects, and operations relative to their baseline plans. It aims to identify performance trends, issues, and risks. The BPR involves monthly reporting from Mission Directorates and support offices. Independent assessors evaluate performance metrics. The BPR process helps improve communication, identify cross-cutting issues, and inform decision-making.
The document introduces the Project Management Toolkit (PPME Toolkit) developed by NASA's Glenn Research Center (GRC) to provide a standardized set of project planning and execution tools. The PPME Toolkit aims to facilitate life cycle project management from proposal development through project control and reporting. It was developed using a rapid prototyping approach and has been piloted with five GRC space flight projects. Version 1 of the Toolkit will be deployed across GRC's space flight portfolio in 2011, and Version 2 will include additional capabilities and an enterprise server solution to enable true portfolio management.
The document discusses upcoming changes to NASA's independent review policies and processes. Some of the key changes include standardizing terms of reference, implementing a 1-step or 2-step review timeline, updating required lifecycle products, revising review criteria and maturity tables, and changes to review team composition and decision memos. The changes aim to improve the effectiveness and efficiency of NASA's review processes.
This document provides an overview of project scheduling from NASA's perspective. It discusses NASA's large, complex projects and the requirements for project scheduling. The presentation covers key project scheduling processes including activity definition, sequencing, duration estimating, schedule development, status accounting, and performance reporting. It provides examples and definitions for these processes. The goal is to give attendees a basic understanding of project scheduling as it relates to NASA projects.
The document discusses a center-wide facilities planning review conducted by NASA's Johnson Space Center from 2007-2009. The review aimed to capture a comprehensive facilities listing, assess budgets tied to facilities utilization, and support risk-based decisions regarding facility closeouts, consolidations and funding. In FY2007, the initial assessment was conducted through interviews and spreadsheets. This identified a need for more input from facility planners and management. In subsequent years, a database called JFReD was created to better capture and report facilities information to support strategic planning across the agency. The review process continued to be refined with the goals of comprehensive data collection and linking facilities utilization to overall center master planning.
The document discusses integrated testing plans for the Constellation program at KSC. It describes plans to conduct Multi-Element Integrated Tests (MEITs) to test interactions between Constellation flight elements launched on different vehicles before they are integrated in space. MEITs found significant problems in previous programs that could have impacted safety and mission objectives. The tests are intended to reduce risks by identifying issues early.
The Constellation Space Transportation Planning Office (CSTP) manages the production, launch preparations, mission operations, and recovery of the Orion/Ares vehicle configuration that will transport crew to and from the International Space Station. The CSTP oversees the entire work cycle from element production to final disposition. It uses an organizational structure with divisions for program integration, planning and control, systems engineering, and operations. The presentation provides an overview of CSTP and updates on its projects and forward work.
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.
The document describes NASA's Baseline Performance Review (BPR) process. The BPR provides NASA senior leadership with objective information on the performance of NASA programs, projects, and operations relative to their baseline plans. It aims to identify performance trends, issues, and risks. The BPR involves monthly reporting from Mission Directorates and support offices. Independent assessors evaluate performance metrics. The BPR process helps improve communication, identify cross-cutting issues, and inform decision-making.
The document introduces the Project Management Toolkit (PPME Toolkit) developed by NASA's Glenn Research Center (GRC) to provide a standardized set of project planning and execution tools. The PPME Toolkit aims to facilitate life cycle project management from proposal development through project control and reporting. It was developed using a rapid prototyping approach and has been piloted with five GRC space flight projects. Version 1 of the Toolkit will be deployed across GRC's space flight portfolio in 2011, and Version 2 will include additional capabilities and an enterprise server solution to enable true portfolio management.
The document discusses upcoming changes to NASA's independent review policies and processes. Some of the key changes include standardizing terms of reference, implementing a 1-step or 2-step review timeline, updating required lifecycle products, revising review criteria and maturity tables, and changes to review team composition and decision memos. The changes aim to improve the effectiveness and efficiency of NASA's review processes.
This document provides an overview of project scheduling from NASA's perspective. It discusses NASA's large, complex projects and the requirements for project scheduling. The presentation covers key project scheduling processes including activity definition, sequencing, duration estimating, schedule development, status accounting, and performance reporting. It provides examples and definitions for these processes. The goal is to give attendees a basic understanding of project scheduling as it relates to NASA projects.
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 Business Operating Success Strategies (BOSS), a new initiative at Kennedy Space Center Launch Services Program to standardize and improve consistency in mission management. It provides an overview of BOSS, including its purpose to align activities with requirements and increase accountability. It outlines how compliance will be achieved through checklists and schedules. Responsibility for implementation and updates is assigned, and next steps are to obtain feedback and measure BOSS' effectiveness.
The document describes the Orion project's plans to streamline the Critical Design Review (CDR) process compared to the previous Preliminary Design Review (PDR). Key aspects of the streamlined CDR include dividing design documentation reviews into focused subgroups, improving the quality and efficiency of identifying and resolving issues through the review process, and reducing the overall number of participants. The goal is to make the CDR process more effective while reducing costs to about one-third of the PDR costs.
The document provides an overview of the Global Precipitation Measurement (GPM) Project from a project management perspective. It discusses the GPM mission objectives of improving understanding of the global water cycle and precipitation forecasts. It describes the GPM observatory and spacecraft, including instruments and ground assets. It also summarizes the project management approach, including the use of an integrated master schedule, earned value management, and joint confidence level analysis to manage schedule and costs.
This document recommends an insight/oversight model for NASA's Commercial Crew Program. It suggests using technical expert engagement similar to other programs, with a focus on high-risk subsystems. The model includes discrete oversight at key decision points rather than continuous oversight. Insight teams would provide expertise and recommendations, while the Program Office makes oversight decisions.
National Aeronautics and Space Administration (NASA) Goddard Space Flight Center's Innovative Partnerships Program (IPP) seeks to form partnerships to enhance future mission capabilities. The IPP acts as a facilitator and catalyst by bringing parties together, implementing new approaches, and identifying ways for partnerships to benefit NASA, partners, and taxpayers. The presentation provides an example partnership between NASA and Carnegie Mellon University's Robotics Institute to demonstrate how innovative partnerships can leverage resources and accelerate technology maturation.
The document summarizes an NSC Audits and Assessments Workshop from September 2009-2010. It discusses the background and purpose of different types of NASA safety audits conducted by the NSC Audits and Assessments Office. The document analyzes audit findings from 2007-2010 and identifies potential systemic safety issues across multiple NASA centers, particularly in electrical safety, inspection records, and probabilistic risk assessment. Action plans were developed to address these issues and improve safety audit processes.
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.
This document summarizes the findings of a NASA survey of various centers regarding compliance with Office of the Chief Engineer (OCE) policy. It describes the survey objectives, methodology, elements reviewed, and schedule. Some key findings included inconsistent implementation of configuration management, risk management, and technical authority across centers. Strengths identified included lessons learned processes and software engineering at JPL. Opportunities for improvement included updating directives, validating Earned Value Management Systems, and clarifying the roles of technical authority and systems engineering.
The Coast-to-Coast Ground and Mission Operations Systems Integration Group was formed in 2006 to provide horizontal and vertical integration across the Constellation Program. Since then, the group has undergone leadership changes and organizational transfers but has relied on virtual collaboration tools to effectively communicate and work together from different locations. This document discusses how the group uses tools like email, teleconferences, an online wiki site and virtual meetings to collaborate and achieve their goals in an integrated manner despite being geographically dispersed.
This document summarizes the role and responsibilities of the Systems and Software Engineering Directorate within the Office of the Deputy Under Secretary of Defense for Acquisition and Technology. The Directorate provides independent technical advice and oversight to programs, establishes acquisition policy and guidance, and works to advance systems engineering practices. It sees opportunities to improve how programs apply systems engineering early in the acquisition lifecycle to better define requirements and manage risks.
The DART mission was intended to demonstrate autonomous rendezvous technology. However, it faced significant cost overruns, schedule delays, and technical risks. At the critical design review, 300 problems were identified. NASA management then reclassified it as a lower-risk, higher-priority mission for commercial resupply. In light of the identified issues, NASA called for a risk review on proceeding. Key risks included limited engineering resources, late changes to key systems, and tight budgets. Groups discussed whether to proceed to the next design review or cancel the mission, weighing risks and potential mitigation strategies. The case study aimed to help managers make risk-informed decisions.
The document discusses changes made to NASA's Safety and Mission Assurance (S&MA) paradigm following several accidents and reports. It outlines how S&MA was reorganized at Marshall Space Flight Center to improve expertise, resources, and inclusion in technical decisions. S&MA now takes an integrated, in-line approach to projects through activities like hazard analysis, risk assessment, and participating in working groups. This early involvement has impacted vehicle designs and produced risk-based products to meet new safety and reliability requirements for programs like Constellation's Ares I.
The document discusses integrating technical performance measures with earned value management. It argues that EVM data is only reliable if technical performance is objectively assessed using the right measures of progress. Standards like CMMI and IEEE 1220 provide guidance on using requirements, product metrics, and success criteria to evaluate technical progress. The document provides examples of how to calculate earned value by linking it to completion of drawings and meeting technical performance targets for weight and diameter. It recommends acquisition best practices like requiring technical performance measurement in proposals and verifying integration at contract award and reviews.
The Constellation Space Transportation Planning Office (CSTP) was established in 2008 to prepare NASA's Constellation Program for the operations and sustaining phase of the Ares I and Orion spacecraft's lifecycle. The CSTP works closely with the Constellation Program to address operability considerations in design and establish the future Constellation Space Transportation Program to manage production, launch, and recovery operations for Ares I/Orion missions to the International Space Station.
The document provides an overview of NASA's policy for independent program reviews:
1. NASA policy mandates independent reviews at key decision points to validate programs' readiness and identify risks. This includes NPD 1000.0 requiring checks and balances like independent reviews.
2. The Standing Review Board process in NPR 7120.5 standardizes independent reviews across NASA. Reviews assess technical and programmatic status at life cycle milestones.
3. The SRB Handbook provides guidance for Standing Review Boards to apply review criteria consistently across programs in accordance with NASA's technical and program management requirements. It outlines the roles, processes, and expected work products for the reviews.
The document outlines an architecture for a cost analytics process that includes capturing cost data in a database from various project phases and cost types, iterating the data through multiple estimation events, and using the stored data and associated schedule information to perform cost analytics and reporting across the project lifecycle. It details the types of fundamental cost and schedule data to be collected, how the data will be iterated through estimation events, and tools that can be used to analyze and report on the stored cost data.
The Commercial Crew Program had to change its acquisition strategy from a fixed-price contract to a public-private partnership due to a 52% budget reduction. The program manager quickly developed a new strategy using a Space Act Agreement and released a revised request for proposals within 11 weeks. While requirements did not change, the approach to verification development had to be adapted. Effective communication, keeping teams focused, and dividing the work into smaller pieces helped the program manager lead the organization through the change in direction.
NASA is working to improve its cost estimating practices by emphasizing cost-risk identification, quantification and management. This includes developing range estimates rather than single point estimates to account for uncertainty. Cost-risk assessments involve analyzing risk from cost models, input parameters, and key project characteristics. Risks are quantified and combined to create a probabilistic 'S-curve' estimate. Earned Value Management data on high-risk project elements is proposed to help connect cost estimating and risk management throughout the project lifecycle. Regularly updating estimates and tracking high-risks will improve cost projections and risk-adjusted budgets.
The document discusses the Ares I-X test flight conducted by NASA in October 2009. It provides background on the objectives and significance of the flight test. It highlights that healthy tension between the flight test's Mission Management Office and Technical Authorities was important to the flight test's success. It then discusses NASA's governance model and how technical authority is implemented. Specifically, it notes the Chief Engineer and Chief of Safety and Mission Assurance represented their communities and helped achieve an appropriate balance between constraints and risk. Information flow between groups was a key factor for the multi-center team's cooperation and success.
This document summarizes key points from a paper on how complex systems fail. It discusses that complex systems are inherently hazardous due to multiple potential failure points, but have many defensive layers that generally prevent failures. It notes that catastrophes occur when small, disconnected failures combine in unexpected ways. Complex systems also constantly operate with some degraded functionality and latent failures, requiring operators to adapt over time to changing conditions in order to maintain safety.
This document discusses using the National Advisory Committee for Aeronautics (NACA) approach to stimulate commercial spaceflight capabilities and achieve low-cost access to space. The NACA successfully built a world-leading aeronautics industry in the US in the early 20th century by partnering with government agencies and industry, conducting broad research, and openly publishing results without picking specific winners. The document argues NASA could adopt this approach of building an entire commercial space industry through partnerships and by addressing priority technical needs, rather than centrally-planning programs to pick winners. This may help achieve the Obama Administration's goal of stimulating commercial spaceflight where previous large, centrally-planned programs have failed.
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 Business Operating Success Strategies (BOSS), a new initiative at Kennedy Space Center Launch Services Program to standardize and improve consistency in mission management. It provides an overview of BOSS, including its purpose to align activities with requirements and increase accountability. It outlines how compliance will be achieved through checklists and schedules. Responsibility for implementation and updates is assigned, and next steps are to obtain feedback and measure BOSS' effectiveness.
The document describes the Orion project's plans to streamline the Critical Design Review (CDR) process compared to the previous Preliminary Design Review (PDR). Key aspects of the streamlined CDR include dividing design documentation reviews into focused subgroups, improving the quality and efficiency of identifying and resolving issues through the review process, and reducing the overall number of participants. The goal is to make the CDR process more effective while reducing costs to about one-third of the PDR costs.
The document provides an overview of the Global Precipitation Measurement (GPM) Project from a project management perspective. It discusses the GPM mission objectives of improving understanding of the global water cycle and precipitation forecasts. It describes the GPM observatory and spacecraft, including instruments and ground assets. It also summarizes the project management approach, including the use of an integrated master schedule, earned value management, and joint confidence level analysis to manage schedule and costs.
This document recommends an insight/oversight model for NASA's Commercial Crew Program. It suggests using technical expert engagement similar to other programs, with a focus on high-risk subsystems. The model includes discrete oversight at key decision points rather than continuous oversight. Insight teams would provide expertise and recommendations, while the Program Office makes oversight decisions.
National Aeronautics and Space Administration (NASA) Goddard Space Flight Center's Innovative Partnerships Program (IPP) seeks to form partnerships to enhance future mission capabilities. The IPP acts as a facilitator and catalyst by bringing parties together, implementing new approaches, and identifying ways for partnerships to benefit NASA, partners, and taxpayers. The presentation provides an example partnership between NASA and Carnegie Mellon University's Robotics Institute to demonstrate how innovative partnerships can leverage resources and accelerate technology maturation.
The document summarizes an NSC Audits and Assessments Workshop from September 2009-2010. It discusses the background and purpose of different types of NASA safety audits conducted by the NSC Audits and Assessments Office. The document analyzes audit findings from 2007-2010 and identifies potential systemic safety issues across multiple NASA centers, particularly in electrical safety, inspection records, and probabilistic risk assessment. Action plans were developed to address these issues and improve safety audit processes.
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.
This document summarizes the findings of a NASA survey of various centers regarding compliance with Office of the Chief Engineer (OCE) policy. It describes the survey objectives, methodology, elements reviewed, and schedule. Some key findings included inconsistent implementation of configuration management, risk management, and technical authority across centers. Strengths identified included lessons learned processes and software engineering at JPL. Opportunities for improvement included updating directives, validating Earned Value Management Systems, and clarifying the roles of technical authority and systems engineering.
The Coast-to-Coast Ground and Mission Operations Systems Integration Group was formed in 2006 to provide horizontal and vertical integration across the Constellation Program. Since then, the group has undergone leadership changes and organizational transfers but has relied on virtual collaboration tools to effectively communicate and work together from different locations. This document discusses how the group uses tools like email, teleconferences, an online wiki site and virtual meetings to collaborate and achieve their goals in an integrated manner despite being geographically dispersed.
This document summarizes the role and responsibilities of the Systems and Software Engineering Directorate within the Office of the Deputy Under Secretary of Defense for Acquisition and Technology. The Directorate provides independent technical advice and oversight to programs, establishes acquisition policy and guidance, and works to advance systems engineering practices. It sees opportunities to improve how programs apply systems engineering early in the acquisition lifecycle to better define requirements and manage risks.
The DART mission was intended to demonstrate autonomous rendezvous technology. However, it faced significant cost overruns, schedule delays, and technical risks. At the critical design review, 300 problems were identified. NASA management then reclassified it as a lower-risk, higher-priority mission for commercial resupply. In light of the identified issues, NASA called for a risk review on proceeding. Key risks included limited engineering resources, late changes to key systems, and tight budgets. Groups discussed whether to proceed to the next design review or cancel the mission, weighing risks and potential mitigation strategies. The case study aimed to help managers make risk-informed decisions.
The document discusses changes made to NASA's Safety and Mission Assurance (S&MA) paradigm following several accidents and reports. It outlines how S&MA was reorganized at Marshall Space Flight Center to improve expertise, resources, and inclusion in technical decisions. S&MA now takes an integrated, in-line approach to projects through activities like hazard analysis, risk assessment, and participating in working groups. This early involvement has impacted vehicle designs and produced risk-based products to meet new safety and reliability requirements for programs like Constellation's Ares I.
The document discusses integrating technical performance measures with earned value management. It argues that EVM data is only reliable if technical performance is objectively assessed using the right measures of progress. Standards like CMMI and IEEE 1220 provide guidance on using requirements, product metrics, and success criteria to evaluate technical progress. The document provides examples of how to calculate earned value by linking it to completion of drawings and meeting technical performance targets for weight and diameter. It recommends acquisition best practices like requiring technical performance measurement in proposals and verifying integration at contract award and reviews.
The Constellation Space Transportation Planning Office (CSTP) was established in 2008 to prepare NASA's Constellation Program for the operations and sustaining phase of the Ares I and Orion spacecraft's lifecycle. The CSTP works closely with the Constellation Program to address operability considerations in design and establish the future Constellation Space Transportation Program to manage production, launch, and recovery operations for Ares I/Orion missions to the International Space Station.
The document provides an overview of NASA's policy for independent program reviews:
1. NASA policy mandates independent reviews at key decision points to validate programs' readiness and identify risks. This includes NPD 1000.0 requiring checks and balances like independent reviews.
2. The Standing Review Board process in NPR 7120.5 standardizes independent reviews across NASA. Reviews assess technical and programmatic status at life cycle milestones.
3. The SRB Handbook provides guidance for Standing Review Boards to apply review criteria consistently across programs in accordance with NASA's technical and program management requirements. It outlines the roles, processes, and expected work products for the reviews.
The document outlines an architecture for a cost analytics process that includes capturing cost data in a database from various project phases and cost types, iterating the data through multiple estimation events, and using the stored data and associated schedule information to perform cost analytics and reporting across the project lifecycle. It details the types of fundamental cost and schedule data to be collected, how the data will be iterated through estimation events, and tools that can be used to analyze and report on the stored cost data.
The Commercial Crew Program had to change its acquisition strategy from a fixed-price contract to a public-private partnership due to a 52% budget reduction. The program manager quickly developed a new strategy using a Space Act Agreement and released a revised request for proposals within 11 weeks. While requirements did not change, the approach to verification development had to be adapted. Effective communication, keeping teams focused, and dividing the work into smaller pieces helped the program manager lead the organization through the change in direction.
NASA is working to improve its cost estimating practices by emphasizing cost-risk identification, quantification and management. This includes developing range estimates rather than single point estimates to account for uncertainty. Cost-risk assessments involve analyzing risk from cost models, input parameters, and key project characteristics. Risks are quantified and combined to create a probabilistic 'S-curve' estimate. Earned Value Management data on high-risk project elements is proposed to help connect cost estimating and risk management throughout the project lifecycle. Regularly updating estimates and tracking high-risks will improve cost projections and risk-adjusted budgets.
The document discusses the Ares I-X test flight conducted by NASA in October 2009. It provides background on the objectives and significance of the flight test. It highlights that healthy tension between the flight test's Mission Management Office and Technical Authorities was important to the flight test's success. It then discusses NASA's governance model and how technical authority is implemented. Specifically, it notes the Chief Engineer and Chief of Safety and Mission Assurance represented their communities and helped achieve an appropriate balance between constraints and risk. Information flow between groups was a key factor for the multi-center team's cooperation and success.
This document summarizes key points from a paper on how complex systems fail. It discusses that complex systems are inherently hazardous due to multiple potential failure points, but have many defensive layers that generally prevent failures. It notes that catastrophes occur when small, disconnected failures combine in unexpected ways. Complex systems also constantly operate with some degraded functionality and latent failures, requiring operators to adapt over time to changing conditions in order to maintain safety.
This document discusses using the National Advisory Committee for Aeronautics (NACA) approach to stimulate commercial spaceflight capabilities and achieve low-cost access to space. The NACA successfully built a world-leading aeronautics industry in the US in the early 20th century by partnering with government agencies and industry, conducting broad research, and openly publishing results without picking specific winners. The document argues NASA could adopt this approach of building an entire commercial space industry through partnerships and by addressing priority technical needs, rather than centrally-planning programs to pick winners. This may help achieve the Obama Administration's goal of stimulating commercial spaceflight where previous large, centrally-planned programs have failed.
This document discusses the importance of strengthening the connection between technical and financial managers on projects. Traditionally, these managers operate independently with the technical manager focused on requirements and the financial manager on funding. However, this can lead to problems like cost overruns, missed deadlines, and inconsistent information. To overcome these issues, the document recommends that the managers improve communication, develop a trusting relationship, work together on reviews, and share basic knowledge so technical changes are assessed for their budget impacts and funding issues are addressed jointly. Regular communication and cooperation between these critical roles is needed for a project's success.
The document discusses NASA's technology protection program, which aims to identify and protect mission critical information (MCI) from foreign threats. It outlines the technology protection process, which involves assessing technologies to identify MCI, evaluating vulnerabilities, selecting initial and final controls, and developing implementation plans. The process is facilitated by the Technology Protection Working Group and aims to balance security with continued information sharing and the NASA mission.
This document discusses integrated predictive performance management as a method for effective project management. It involves developing an integrated baseline for technical scope, schedule, and budget that serves as a shared plan. Performance is measured by comparing work completed to the baseline. This allows for predicting future performance and taking early actions to positively impact outcomes. Benefits include integrated performance measurement, a disciplined planning methodology, and improved visibility, accountability, and risk management. The key is for projects to own their baselines which are then status reported and maintained through a change control process.
The document discusses influencing culture change within an organization. It outlines a process that includes initial planning, establishing a framework, rollout, and making the change stick. The process is then illustrated through an example of restructuring a NASA safety and mission assurance division during the transition away from the space shuttle program. The case study describes dreaming up a new vision, analyzing roles and structure, communicating the changes, and taking actions to continually reinforce the new culture.
The document summarizes lessons learned from international partnerships between agencies like NASA and ESA. It discusses that successful partnerships require:
1) Early and clear definition of project baselines and interfaces to avoid surprises
2) Regular communication and recognition of differences in processes between agencies
3) Involving various capacities beyond just project management like external relations and legal
International cooperation for projects like the International Space Station require managing political changes that can impact programs and diplomatic skills to manage relationships between equal partners. Flexibility and understanding are essential for international exploration partnerships.
The document summarizes the goals and approach of the Software Architecture Review Board (SARB). The SARB aims to help NASA missions achieve higher reliability and cost savings by managing flight software complexity through better software architecture. It will do this by engaging with flight projects in the early stages of software architecture development to provide constructive feedback. The board will also help spread best practices across NASA and contribute to lessons learned. The summary discusses the typical architecture review process used, including preparation, meetings, and follow-up reports. It also outlines common issues identified in reviews and perceived impediments to software architecture at NASA.
The NASA Schedule Management Handbook provides guidance on developing and maintaining an integrated master schedule for NASA projects. It outlines roles and responsibilities, considerations for schedule management tools, and processes for pre-schedule development, developing the integrated master schedule, and ongoing status updates and maintenance. The handbook aims to help project managers and teams adhere to NASA requirements for sound schedule management practices.
The document discusses the development of requirements for a vehicle through model-based systems engineering. It provides examples of models that can be used to capture a vehicle's operational concept, including a design reference mission diagram, a phase model, and an activity model. The models aim to depict how the vehicle and crew interact during different mission activities and phases to achieve objectives. They are used to identify vehicle capabilities and functions needed to implement the operational concept.
This document discusses trends in project management (PM) and systems engineering (SE) costs for NASA space missions. It finds that PM and SE costs have been increasing over time as a percentage of total mission costs, driven by factors like increasing technical complexity, scale of projects, and specialization. Data is presented showing trends in PM and SE costs for NASA-funded APL space missions and other NASA robotic missions from 1996-2018. While instrument management costs have declined for some missions since 2002, overall the data indicates PM and SE costs are growing and additional resources are needed to ensure project success in the current environment.
This document summarizes a presentation about lessons learned from NASA's Stardust comet sample return mission. The Stardust mission returned the first solid samples from a comet in 2006. Key lessons included the value of detailed pre-flight measurements and instrumentation that were not included due to budget and schedule constraints. Future missions could benefit from more proactive "planning for learning" approaches rather than just reactive "lessons learned." Careful recovery operations are also important for preserving samples and data about the heatshield's condition upon reentry.
The document provides an integrated master schedule (IMS) for the Ares I-X flight test. It lists the IMS manager and project integration manager. The IMS details activities for various elements from 2008 to 2009, including delivery dates for components to the assembly facility and timelines for assembly, integration testing, and launch. The overall schedule aims to provide 60 days of margin and reduce rework through integrated planning.
The document discusses integrated architecture assessments for future crewed missions to the moon. It summarizes:
1) Experience has shown integrated architecture assessments are crucial to establish stable configurations that meet performance, cost and risk goals.
2) The analyses allow for mission-level trades to ensure efficient vehicle designs, allocation of design margins, and elimination of overlooked elements.
3) Preliminary analyses indicate the Ares V 51.0.47 and 51.0.48 concepts with the Altair lunar lander can achieve global access to the lunar surface through trades of delta-V, low lunar orbit loiter time, and temporal availability over the lunar nodal cycle.
This document discusses keys to making virtual communication work. It begins with an overview of communication challenges in general and for virtual teams specifically. It then provides tips for virtual teams such as establishing clear standards and norms, developing team charters, communicating vision and goals effectively, understanding different communication styles, and using structures like TREOA for presentations. The document concludes with references for further resources on virtual team management.
The document discusses systems engineering challenges and opportunities, including:
1) Growing mission complexity is exceeding our ability to manage risk, and system designs emerge from pieces rather than sound architectures, resulting in brittle systems.
2) Technical and programmatic sides of projects are poorly coupled, hampering decision making and increasing risk.
3) Too much focus on process comes at the expense of design quality, driving up costs and risk.
The document proposes addressing these with model-based systems engineering, architecture frameworks, and integrating technical and programmatic considerations through architecture.
NASA is transforming its aging facility portfolio into next generation centers through a strategic renewal process using the Kotter change model. The agency established a sense of urgency around renewing assets as 40% will be over 40 years old. A powerful guiding coalition was formed including agency leadership, center leadership, and project teams. A vision of renewing and modernizing facilities to sustain capabilities in efficient facilities was created. Communication of the vision and empowering others to act through center master plans and project teams is occurring. Short term wins are planned through visible renewal projects that expand stakeholder buy-in and consolidate improvements to further transform the agency's facilities portfolio.
This document discusses how to apply systems engineering principles to small, fast-paced projects with limited resources. It recommends tailoring systems engineering processes by deciding in advance how key elements will be addressed rather than questioning if they will be addressed. Checklists from NASA standards can help ensure critical items are considered. Organizational support, collaboration, and focused peer reviews are also important enablers.
This document discusses important considerations for forming effective project teams. It emphasizes selecting the right team members, establishing a shared vision and goals, clarifying roles and expectations, and ensuring the team understands its purpose. Specifically, it recommends selecting candidates based on their knowledge, skills, and abilities; developing a mission statement to guide the team's work; setting SMART goals to facilitate success; defining each member's responsibilities; and discussing the team's objectives during formation to set the stage for high performance. Forming the team carefully at the outset is critical to setting the foundation for successful collaboration.
This document outlines the development management framework for Nakheel Shopping Malls projects. It details the key phases and steps involved, from initial project identification through to completion and handover of the mall to operations. The major phases include initiation, pre-development, development, and completion/management. Key activities within each phase are defined such as concept development, design documentation, procurement, construction monitoring, and tenant coordination. The framework is intended to advise, facilitate and deliver mall development projects from start to finish.
This presentation provides an introduction to project structures in SAP Project Systems. It discusses how projects can be structured using work breakdown structures (WBS) and networks/activities. It then provides details on creating a WBS, including defining WBS elements and using templates. It also covers the use of system and user statuses to control the stages of a project.
The document discusses how the Constellation Program Office implemented Earned Value Management (EVM) across all of its projects. It describes how the Marshall Space Flight Center's Office of Strategic Analysis and Communications collaborated with various program elements to establish processes for collecting, formatting, and integrating EVM data. This included providing tools, training, and guidance on work breakdown structures and organization breakdown structures. Once the initial elements established these processes, other elements began adopting them as well. Eventually, EVM data was integrated and rolled up at the overall Constellation program level.
Enable Large Scale, High Volume Deployment For Enterprise ApplicationsClever Moe
Using Components, Spaces, and NoSQL technology and methodology to build and operate large scale Web enabled applications. Includes demonstration of TIBCO ActiveMatrix and Service Grid.
Nek e am_overview_2010_1f.ppt [compatibility mOracle Hrvatska
This document provides an overview of the implementation of Oracle EBS and EAM systems at Nuklearna Elektrarna Krško (NEK), a nuclear power plant in Slovenia. Some key details include:
- The project aims to implement a new long-term IT solution to support plant safety, reliability, and cost effectiveness.
- Implementation began in July 2009 and is planned to go-live in March 2011 using the Application Implementation Method.
- The system will include modules like asset management, maintenance management, project management, and financials to support overall business operations.
- NEK hopes to establish industry best practices and requirements through partnerships like the Oracle EAM Customer Advisory Board.
- Proper
Mr. Rangadham Ayyadevara is a Project Functional consultant with over 25 years of experience in project costing, billing, project management, and resource management. He has extensive experience implementing and supporting Oracle ERP modules such as financials, projects, supply chain management, and HCM for various industries. Mr. Ayyadevara specializes in Oracle ERP 12c implementations and upgrades for clients in industries such as oil and gas, manufacturing, and technology.
Byron Pang is an Industrial Engineering professional with over 15 years of experience in various roles. He is currently an IE Manager at Infineon Technologies where he leads a team and is responsible for maintaining manufacturing KPIs and driving productivity improvements. Some of his past accomplishments include receiving various achievement awards and improving OEE, setup times, and cycle times through projects applying IE tools and methodologies.
Semantics to energize the full Services Spectrum: Ontological approach to be...Amit Sheth
Amit Sheth's Talk at the inauguration invitational event for Research School on Services-Oriented Systems Engineering, Hasso-Plattner-Institute, Potsdam, Germany, June 22, 2006.
Global Automation Equipment Leader gains Scalability through Upgrades
Hexaware provided end-to-end development and maintenance services to help the client attain scalability, reduce costs, and enhance service value through deploying an experienced resource base and providing an extension of existing delivery systems. The solution involved Hexaware providing upgrades, development and maintenance services through an offshore delivery model and three phases: pre-upgrade assessment, upgrade of databases and applications, and post go-live support. This enabled the client to improve management of product tasks, reduce upgrade costs, and enhance service levels and scalability.
Riverbed's presentation at SFSE Meetup 2/22Sauce Labs
This document discusses Riverbed Technology, a company that produces network appliances and software. It outlines their goals of developing reusable, scalable, and easy to maintain automation for testing their web interfaces across browsers and platforms. It describes their approach using Selenium grids, abstract page objects, and data-driven tests. Challenges included testing complex AJAX functionality on a diverse install base with multiple independent releases.
EVM is a project management process that integrates scope, schedule, and cost to assess project performance and forecast outcomes. It allows objective assessment of current performance by comparing planned, earned, and actual costs. EVM enhances project success by defining the work, scheduling activities, allocating budgets, and measuring progress to identify variances and inform management decisions. Key aspects of EVM include establishing a performance measurement baseline, determining earned value, and analyzing variances and estimates at completion.
EVM is a project management process that integrates scope, schedule, and cost to assess project performance and forecast outcomes. It allows objective measurement of progress against a performance measurement baseline (PMB) which includes a work breakdown structure, schedule, and time-phased budget. EVM helps identify variances so management can take corrective actions to mitigate risks and keep the project on track. NASA requires EVM for projects over $20 million to enhance the likelihood of success through active measurement and management.
The document provides lessons learned from implementing Earned Value Management (EVM) on the Constellation (CxP) EVA Systems Project Office (ESPO) pilot project. Key lessons include: distinguishing between budget and funding to avoid replanning the performance measurement baseline for funding changes; tying risk assessments to developing management reserve and estimate at completion updates; ensuring all work scope is covered by authorization documents; and using consistent work breakdown structure and integrated master schedule structures across project tools and partners. The pilot project terminated early but documented lessons to improve NASA's agency-wide EVM processes.
The document discusses project management solutions for engineering and construction projects using SAP Project Systems (PS) enhanced by Noveco ePM. It highlights key requirements such as accurate cost estimating and forecasting, project progress measurement and reporting, procurement planning, and integration of subcontractors. It then summarizes why Noveco ePM is needed to enhance SAP PS, addressing gaps in areas like estimation, cost forecasting, variation management, and reporting. The rest of the document outlines the project management lifecycle supported in SAP PS and Noveco ePM, including planning, execution, monitoring, forecasting, and reporting.
IRJET- Analysis of Pre-Engineered Building and Conventional Building usin...IRJET Journal
This document analyzes and compares the construction of pre-engineered buildings and conventional steel buildings using Primavera scheduling software. It finds that pre-engineered buildings have a 15% lower cost and take 16 fewer days to complete construction compared to conventional buildings. The planning and scheduling of two warehouse projects in Kerala, India are modeled in Primavera. It is concluded that pre-engineered buildings provide advantages in both construction time and cost.
I recently did some consulting at a local agency and was asked to put together a presentation to help educate the account teams about what is going on in digital marketing. It has a few work flow tips, mobile stats, emerging platforms and some growing trends.
Want to start using EVM principles for your project based business? This is a great primer to get you started. Brought to you by the team at Unanet.com.
Learn more at: https://www.unanet.com/news/demand-webinars
SuccessFactors 2H 2021 Sneak Peek by Deloitte GermanyChristoph Pohl
The second release this year is available on all preview instances since a couple of hours. Therefore, we created a fresh Sneak Peek with a focus on Employee Central and Platform.
The document discusses managing federal agencies during turbulent times using an enterprise architecture approach. It states that federal agencies now need to focus on performance, customers, and high-value services to meet new standards. An enterprise architecture implements an operations concept and strategy tied to the agency's mission through defined releases. Each release provides new capabilities while integrating components to keep the enterprise functioning, with information systems development keeping pace with business changes.
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.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
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.
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3Data Hops
Free A4 downloadable and printable Cyber Security, Social Engineering Safety and security Training Posters . Promote security awareness in the home or workplace. Lock them Out From training providers datahops.com
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
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.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
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.
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
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.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Dandelion Hashtable: beyond billion requests per second on a commodity server
Les.sorge
1. Implementing Earned Value Management in
the CxP ESPO
Project Management Challenge 2010
Galveston, TX
February 9-10, 2010
Les Sorge/SGT, Inc.
ESPO Project Planning & Control
Used with Permission
2. Implementation Goal & Presentation Agenda
♦ The goal of the EVA Systems Project Office (ESPO) Earned Value
Management (EVM) implementation is to utilize existing products and
processes where possible or influence them to make them compatible
with EVM
♦ Agenda
• Work Breakdown Structure
• Organizational Breakdown Structure
• Responsibility Assignment Matrix and Control Accounts
• Work Packages / Charge Codes and Planning Packages
• Integrated Master Plan
• Integrated Master Schedule – Primavera PM Tool Implementation
• Deltek Cobra Tool Implementation
• Integration / Interfaces to Other Processes / Tools
• EVM Integration with Prime Contractor
• Future Opportunities for Improvements
• Acronyms and Reference Documents
• Questions & Answers
2
3. Work Breakdown Structure (WBS)
♦ Summary of WBS requirements defined in NPR 7120.5D, Appendix G
• The standard space flight project WBS applies to the entire life cycle of the project
• Space flight projects will use the standard Level 1/2 WBS elements with level 1 as the
Project name
• Level 3 and lower WBS elements will be determined by the project
• If there is no work to fit into a Level 1/2 WBS element, then an inactive placeholder
element will be established
• A single WBS will be used for both technical / business management and reporting
♦ ESPO Implementation
• The technical WBS matches the financial WBS excluding the 6 digit project code
• The figure below represents the CxP reporting level and the pre-defined Control Account
level
Agency Defined
Project Defined
3
4. Organizational Breakdown Structure (OBS)
♦ Defining the responsible organization versus the performing organization
• Ask the question, “How does the Project Manager distribute the budget for control?”
♦ The Responsible Organization
• Used to develop the Responsibility Assignment Matrix (RAM) and Cost Performance
Report (CPR) Format 2
• Aligns closely with the Work Breakdown Structure
♦ The Performing Organization
• Based on NASA Center, Directorate, and Divisions
− A budget forecasting requirement does exist for the performing organization for planning purposes
NASA Performing Organization ESPO Responsible Organization
4
5. Responsibility Assignment Matrix (RAM)
& Control Accounts (CA)
♦ Prime added as an organization in the OBS per ANSI-748 guidance
• This structure allows budgets to be segregated between prime and non-prime work while still
reinforcing the “integrated project – NASA and Prime” philosophy of ESPO
♦ CA nomenclature used: .29 for historical, .31 for NASA/non-prime, .32 for Prime
• .31 used for all NASA/non-prime organizations for easy recognition in SAP financial system
− Nomenclature works since multiple organizations don’t support a WBS element
ESPO RAM Rev #: 001 Budget in ($K) Constellation EVA Systems Project Office
Date: 11/3/2009 $0.0
PAD #: CxP-EV-731384-P1-00 OBS $0.0 $0.0 $0.0 $0.0 $0.0 $0.0 $0.0 $0.0 $0.0 $0.0 $0.0 $0.0
PAD Issue Date: 7/10/2009
Development
Project Mgmt
Historical CA
Operations &
Suit Element
CSSS Prime
Technology
Testing and
Planning &
Equipment
Sustaining
Tools and
Facilities
Interface
Element
Element
SR&QA
Control
Vehicle
Project
SE&I
WBS Description
731384.01.01 Project Management 731384.01.01.29 731384.01.01.31 731284.01.01.32
731384.01 $0.0 $0.0 $0.0 $0.0
731384.01.02 Project Planning & Control 731384.01.02.29 731384.01.02.31 731384.01.02.32
$0.0 $0.0 $0.0 $0.0 $0.0
731384.02 Systems Engineering & 731384.02.29 731384.02.31 731384.02.32
$0.0 Integration $0.0 $0.0 $0.0
731384.03 Safety, Reliability and 731384.03.29 731384.03.31 731384.03.32
$0.0 Quality Assurance $0.0 $0.0 $0.0
731384.04 Technology Development 731384.04.29 731384.04.31 731384.04.32
$0.0 $0.0 $0.0 $0.0
731384.05 Payload(s) 731384.05.29
$0.0 $0.0
EVA Systems H/W
731384.06.01 Management
731384.06.02 reserved
731384.06.03 EVA Systems Sustaining 731384.06.03.29 731384.06.03.31 731384.06.03.32
$0.0 Engineering $0.0 $0.0 $0.0
731384.06.04.01 Suit Element 731384.06.04.01.29 731384.06.04.01.31 731384.06.04.01.32
$0.0 $0.0 $0.0 $0.0
731384 731384.06.04 731384.06.04.02 Tools and Equipment 731384.06.04.02.31 731384.06.04.02.32
$0.0 Element $0.0 $0.0
731384.06.04.03 Vehicle Interface Element 731384.06.04.03.29 731384.06.04.03.31 731384.06.04.03.32
731384.06
$0.0 $0.0 $0.0 $0.0 $0.0
Logistics, Processing and 731384.06.05.31
Inventory Mgmt $0.0
Logistics Planning
Control Accounts identified in the 731384.06.05.32.01
$0.0
731384.06.05 Flight & Training Hardware 731384.06.05.32.02
Processing RAM create a natural extension to $0.0
Hardware Inventory 731384.06.05.32.03
Management the project WBS $0.0
Procedures Development 731384.06.05.32.04
$0.0 $0.0 and Control $0.0
731384.07 reserved
731384.08 reserved
731384.09 reserved
731384.10 Integrated Testing and 731384.10.29 731384.10.31 731384.10.32
$0.0 Facilities $0.0 $0.0 $0.0
731384.11 Education and Public 731384.11.29 731384.11.31 731384.11.32
$0.0 $0.0 Outreach $0.0 $0.0 $0.0
5
6. WBS and CA Levels
♦ Although the WBS expanded to a lower level, the summary level was requested as
the control point
• Control points/CAMs identified as the ESPO WBS Leads
• The EVM implementation added “subsystem” summary lines between the Control Accounts and
the Work Packages to match the expanded WBS
− Each subsystem has it’s own unique codes
− Allows easier summation of performance / costs at the subsystem level
♦ The implementation strategy works, but in hindsight, it may have been better to use
the lowest level of the WBS as the Control Account level
• CAMs would have multiple Control Accounts
• Budget changes between subsystems would be more closely tracked 731384.06.04.01
Suit Element
Pre-defined
Excerpt of ESPO WBS CA Level
.31 Govt CA .32 Prime CA
WBS WBS Title
6.4.1 Suit Element .06.04.01.31.01 Suit Mgmt
6.4.1.1 Suit Element Management & Administration WP / PP
6.4.1.2 Suit Element SE&I .06.04.01.31.01.01 – Suit Mgmt – IOC
6.4.1.3 Suit Element Safety .06.04.01.31.01.a – Suit Mgmt – CxLEOOps
Etc.
6.4.1.4 Pressure Garment Subsystem
6.4.1.5 Portable Life Support Subsystem .06.04.01.31.02 Suit SE&I
Power, Communication, Avionics, and WP / PP
6.4.1.6 Informatics (CAI) Subsystem .06.04.01.31.03 Suit Safety
6.4.1.7 Suit Ground Support Equipment (GSE)
WP / PP
Etc.
6
7. Work Packages (WP) / Charge Codes
& Planning Packages (PP)
Excerpt of ESPO WP / PP
♦ The financial WBS / charge codes are
maintained in SAP financial tool WBS Elem ent Long Title Project/WBS
Extravehicular Activity 731384
• Over 400 charge codes previously existed in SAP Project Management 731384.01
prior to EVM implementation due to multiple re-builds Project Management 731384.01.01
(most codes never used) Project Management and Administration 731384.01.01.01
• A “fresh” start was required for EVM GRC-Proj Mgt & Admin 731384.01.01.01.03
− Several ideas were explored LaRC-EVA Project Management 731384.01.01.01.04
731384.01.01.01.10
− Preferred option was an easily recognizable unique JSC-EVA-Project Mgmt.
Project Management Plan 731384.01.01.02
numbering for the CA
GRC-Proj Mgmt & Admin 731384.01.01.03
− All “old” codes collected in the historical CA
Internal/External Project Review Support 731384.01.01.04
LaRC-Internal/External Proj Review Spt 731384.01.01.04.04
♦ For CxP ESPO a WP equals a 731384.01.01.29 Performance Management and Review s 731384.01.01.05
JSC-Proj Mgmt & Amin 731384.01.01.10
charge code equals the lowest WBS NASA Project Management 731384.01.01.31
level JSC-EVA Project Mgmt - IOC 731384.01.01.31.01
♦ Adhere to SAP rule that charge Work Packages / JSC-External Review Supt thru KDP C 731384.01.01.31.02
Charge Codes GRC-EVA Project Mgmt -IOC 731384.01.01.31.03
codes cannot cross NASA centers LaRC-External Review Supt thru KDP C 731384.01.01.31.04
♦ PP identified as a letter in the code PP - JSC-EVA Project Mgmt - CxLEOOps 731384.01.01.31.a
731384.01.01.31.aa
and are not in the SAP financial tool Planning PP - JSC-EVA Project Mgmt - CxLEOOps -2
Packages PP - JSC-EVA Project Mgmt - HLR 731384.01.01.31.5a
• During rolling wave planning, a request PP - GRC-EVA Project Mgmt - HLR 731384.01.01.31.5b
for a new charge code will be submitted JSC-CSSS Project Managment 731384.01.01.32
for the next sequential number to be
opened in SAP
7
8. Integrated Master Plan (IMP)
♦ NASA Project life cycle defined in NPR
7120.5D, starting point used to define Constellation Program
the ESPO IMP EVA Systems Project Office
Lunar Capability Integrated Master Plan
IMP Significant Accomplishment
♦ CxP ESPO defined as two separate L
Code
Lunar Capability
Event Accomplishment Criteria
Projects, Initial Capability and Lunar L.A
L.B
Requirements Development & System Definition
Preliminary Design
L.C Final Design
Capability, that are linked L.D
L.E
System Assembly, Integration, and Test Constellation Program
Operations & Sustainment EVA Systems Project Office
♦ IMP needs to capture all work content L.S
L.T
Manufacturing
IMP Systems Tools
EVA
Code Event
Initial Capability Integrated Master Plan
Significant
Accomplishment Accomplishment Criteria
L.U GSE
of the entire Project L.V
L.W
I Facilities and TSE
Initial Capability
Requirements Development & System Definition
I.A Management and Integration
•
I.B Preliminary Design
L.X Constellation Program Integration
IMP events added for work content that is L.F
I.B.02
Decommissioning and Close-out
I.B.04
VIE PDR
Suit Element PDR
not readily defined by the life cycle phases I.B.05 EVA Systems PDR
EVA Systems PDR Planning
•
I.B.05.a Complete
IMP jointly developed with the Prime I.B.05.b
EVA Systems PDR Requirements
Analysis Cycle Complete
EVA Systems PDR Design
I.B.05.c Analysis Cycle Complete
EVA Systems PDR Hardware
I.B.05.d Complete
EVA Systems PDR Testing
I.B.05.e Complete
EVA Systems PDR Products
I.B.05.f Complete
EVA Systems PDR Execution
I.B.05.g Complete
Phase B Independent
I.B.06 Reviews
EVA Systems PDR SRB Activities
I.B.06.a Complete
Non-advocate Review (NAR) / KDP
I.B.06.b C Gate Review Complete
I.C Final Design
I.D System Test and Operational Readiness
I.E Operations & Sustainment
I.S Manufacturing
I.T EVA Systems Tools
I.U GSE
I.V Facilities and TSE
I.W Management and Integration
I.X Constellation Program Integration
I.Y Award and Transition
I.F Decommissioning and Close-out
8
9. Integrated Master Schedule (IMS)
Primavera PM Tool Implementation
♦ The Primavera IMS developed with Resource Loaded (RL) activities linked to
the budget WP / PP in Deltek Cobra
• Activities were originally resource loaded in the Primavera IMS
− Discovered resource loading easier to customize in Deltek Cobra as compared to Primavera
− Resources removed from IMS and only the activity dates and % completes are now linked
• Additional schedule detail added to the IMS by the rolling wave method
♦ All activities are also tagged with an IMP code for an event-driven view
9
10. Deltek Cobra Tool Implementation
WBS / OBS / CA Structure
Control Accounts (CA)
match RAM
Multiple WP make up
each CA
.00 WBS created to
track budget funding
marks
10
12. EVM Integration with Prime Contractor
Cx PAD
♦ Driving requirement is NOT EVA Systems Project
TAB
to replicate Prime EVM AUW OVERRUN
.31 CA budget
data within Project data NCC PBB OTB
.32 CA budget
♦ Utilize Deltek wInsight tool
Mgmt Reserve PMB
to integrate Prime EVM
data with ESPO EVM data Undistributed
Budget
Distributed
Budget
Summary Level
Planning Packages
♦ Items that must be
Work Planning Planning Planning Contract Price (Prime)
addressed to integrate Packages Packages Packages** Packages Total Allocated Budget Work
(IDIQ) (Prime not Package
data: Closed on contract)
Planning
Package
PMB
(award fee)
• Management Reserve (MR) Packages (Prime MR)
• Undistributed Budget (UB) **IDIQ budget has
• Summary Level Planning been distributed to Contract Price
the CAMs to manage
Packages
TAB Award
• Prime Award Fee AUW OVERRUN Fee
• IDIQ content NCC CBB OTB
• Differences between Cx PAD and Prime
Mgmt Reserve PMB Prime
contract periods of performance
• Differences between Prime contract value and Undistributed Distributed Summary Level
Budget Budget Planning Packages
Government probable cost
Closed Work Planning
Packages Packages Packages
12
13. Future Opportunities for Improvement
♦ NASA financial systems (SAP) not fully compatible with EVM
• SAP set up as a cost collection system, not necessarily a performance measurement system
− Requires obligation of funds at the lowest level of detail, i.e. the charge code for ESPO
− System cumbersome on Procurement personnel to de-obligate & re-obligate funds from old to new charge
codes
− System sometimes creates situations of lagging actuals due to obligations at the lowest level, i.e. cost over
obligations
− System cumbersome with regards to timely creation and inability to close charge codes and does not limit
access to charge codes
− These issues have forced the creation of long duration work / planning packages (multiple years)
♦ Continued training for understanding of Earned Value concepts, in particular,
separation of budget versus funding
• Existing NASA processes (PPBE, JSC ITA, etc.) are funding processes that are being used
synonymously with EVM budget processes
− They should be linked to EVM funding processes (ETC / EAC)
♦ Not all organization support contracts structured to collect and report data to
support Cx Project EVM requirements
• Contract structure forces organizations to "guess" on the monthly costs collected against charge
codes by applying estimates since data reported at a summary level
• Manual entry process of support contract data into SAP precludes detailed data due to the time
requirements to enter the data
13
14. Acronyms and Reference Documents
♦ Acronyms ♦ Reference Documents
• CA – Control Account • NPR 7120.5D – NASA Program and Project
• CAM – Control Account Manager Management Processes and Requirements
• CIRR - CxP Integrated Resources Report • CxP 72179 – CxP ESPO Project Plan
• CPR – Cost Performance Report • CxP 72179 Anx01 – CxP ESPO EVM
• CxP – Constellation Program Implementation Plan
• ESPO – EVA Systems Project Office • CxP 72179 Anx03 – CxP ESPO IMP/IMS
Implementation Plan
• EVA – Extravehicular Activity
• ANSI/EIA-748 – Earned Value Management
• EVM – Earned Value Management Systems
• EVMS – Earned Value Management System
• IBOT - Integrated Budget Office Toolkit
• IDIQ – Indefinite Delivery, Indefinite Quantity
• IMP – Integrated Master Plan
• IMS – Integrated Master Schedule
• IRMA – Integrated Risk Management Application
• ITA - Internal Task Agreement
• JCL - Joint Confidence Level
• JSC – Johnson Space Center
• NPR - NASA Procedural Requirements
• OBS – Organizational Breakdown Structure
• PAD – Project Authorization Document
• PP – Planning Package
• PPBE - Planning, Programming, Budgeting, and Execution
• RAM – Responsibility Assignment Matrix
• RL – Resource Loaded
• SAP – Systems Application and Products
• WBS – Work Breakdown Structure
• WP – Work Package
14