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.
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 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.
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 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 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.
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 outlines the mission of the Launch Services Program at NASA's Kennedy Space Center, which provides support for spacecraft throughout their lifecycle including mission planning, engineering, manufacturing, launch site operations, and post-launch operations. The LSP interfaces with other NASA centers and provides support for over 50 successful launches including recent missions like THEMIS, MMS, JUNO, and upcoming ones such as MSL, LRO, and JWST.
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 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 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.
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 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 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.
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 outlines the mission of the Launch Services Program at NASA's Kennedy Space Center, which provides support for spacecraft throughout their lifecycle including mission planning, engineering, manufacturing, launch site operations, and post-launch operations. The LSP interfaces with other NASA centers and provides support for over 50 successful launches including recent missions like THEMIS, MMS, JUNO, and upcoming ones such as MSL, LRO, and JWST.
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 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 provides an overview of critical path method (CPM) scheduling presented at the First Annual NASA Project Management Conference. It includes a scheduling awareness quiz, types of schedules and networks, precedence diagramming methods, task durations, forward and backward passes to calculate early and late start/finish dates, and total float. The purpose is to introduce essential CPM scheduling concepts and techniques.
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.
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.
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 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.
The document discusses the use of probabilistic risk assessment (PRA) in decision making for the Space Shuttle program. It provides background on the development of the Shuttle PRA since 1987. Key information for management includes clearly presenting the PRA analysis and assumptions, limitations, and estimates of uncertainty to support risk-informed decisions.
The 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 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 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.
The document provides an overview of the requirements and processes needed to successfully pass Preliminary Design Review (PDR) and Key Decision Point C (KDP C) under NASA Procedural Requirements 7120.5D. It first discusses categorizing a project based on cost and complexity to determine the appropriate decision authority and governing documents. It then outlines the phases of formulation and implementation in the project lifecycle and the major reviews and decision gates including PDR, which provides approval to proceed to implementation phases. Examples from the Juno project are given to demonstrate how to address the requirements to have a successful PDR while still accomplishing the primary work.
Project termination can occur for various reasons such as technical or financial failure, changes in needs or priorities, or budget constraints. When a project is terminated, it impacts individuals and the organization. A terminated project requires closure while minimizing trauma through open communication. Methods of project termination include removing resources, integrating the project, or squeezing the budget. Examples of terminated NASA projects include Apollo missions 18-20 and programs such as X-33 due to cost and technical issues.
The document discusses lessons learned from turbulence experienced during a NASA aeronautics research project. Key points include: a new project manager was selected who was unfamiliar with the role and processes, which led to leadership issues; the program was undergoing changes that created an unclear vision and shifting requirements, adding turbulence; clear communication between project leadership and open discussion of challenges is important for navigating periods of turbulence; selecting candidates well-suited for open roles and providing needed training and mentoring can help address issues that arise.
This presentation discusses applying principles of guidance, navigation, and control (GN&C) theory to project management. It provides an overview of GN&C theory and how it has been used to model physical systems. The presentation argues that GN&C principles can also be applied to model human project teams as physical systems. It then discusses how GN&C concepts were applied to manage the NASA Constellation Space Suit project, allowing it to meet tight schedules and budgets. The results demonstrated that utilizing modern GN&C approaches can improve a project's performance and outcomes.
The document outlines the organizational structure and timeline of the Constellation Program. The program manager is J. Hanley and the deputy manager is M. Geyer. The program includes several offices and projects focused on areas like engineering, safety, and advanced projects. Key milestones on the timeline include Ares I and II launches between 2009-2016 culminating in the first human launch in 2015. The integrated testing and verification plan involves a series of flight and ground tests leading up to the first uncrewed and crewed Orion missions.
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 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.
The document discusses NASA's Innovative Partnerships Program (IPP), which facilitates partnerships between NASA and external parties. The IPP aims to identify ways to add value to NASA's priorities through a win-win-win approach benefiting NASA, partners, and taxpayers. The IPP encompasses various elements including technology infusion, innovation incubation, and partnership development. It also discusses the value of software reuse across NASA programs and projects and provides examples of where software is used and how much is developed at NASA based on FY09 agency reports.
This document introduces the return on investment (ROI) methodology for measuring the value of project management. It discusses why measuring value is important, as most projects are over budget and behind schedule. The ROI methodology provides a 10-step process for conducting an evaluation, including planning objectives, collecting data during and after implementation, analyzing data, calculating costs and benefits, and reporting results. Implementing ROI can help justify budgets, improve processes, and show how project management contributes to business goals.
This document outlines three NASA development programs: the Program and Project Management Development Program (PPMD), the Project Leadership Program (PLP), and the Small Satellite Engineering Development Program (SSEDP). The PPMD prepares future program and project managers for leadership roles, the PLP and SSEDP develop project management and systems engineering competencies, and all three programs provide training, mentoring, and work assignments. Examples are given of participants from different NASA centers using their program to develop skills for roles in safety assurance, program integration, and engineering.
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.
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 provides an overview of critical path method (CPM) scheduling presented at the First Annual NASA Project Management Conference. It includes a scheduling awareness quiz, types of schedules and networks, precedence diagramming methods, task durations, forward and backward passes to calculate early and late start/finish dates, and total float. The purpose is to introduce essential CPM scheduling concepts and techniques.
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.
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.
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 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.
The document discusses the use of probabilistic risk assessment (PRA) in decision making for the Space Shuttle program. It provides background on the development of the Shuttle PRA since 1987. Key information for management includes clearly presenting the PRA analysis and assumptions, limitations, and estimates of uncertainty to support risk-informed decisions.
The 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 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 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.
The document provides an overview of the requirements and processes needed to successfully pass Preliminary Design Review (PDR) and Key Decision Point C (KDP C) under NASA Procedural Requirements 7120.5D. It first discusses categorizing a project based on cost and complexity to determine the appropriate decision authority and governing documents. It then outlines the phases of formulation and implementation in the project lifecycle and the major reviews and decision gates including PDR, which provides approval to proceed to implementation phases. Examples from the Juno project are given to demonstrate how to address the requirements to have a successful PDR while still accomplishing the primary work.
Project termination can occur for various reasons such as technical or financial failure, changes in needs or priorities, or budget constraints. When a project is terminated, it impacts individuals and the organization. A terminated project requires closure while minimizing trauma through open communication. Methods of project termination include removing resources, integrating the project, or squeezing the budget. Examples of terminated NASA projects include Apollo missions 18-20 and programs such as X-33 due to cost and technical issues.
The document discusses lessons learned from turbulence experienced during a NASA aeronautics research project. Key points include: a new project manager was selected who was unfamiliar with the role and processes, which led to leadership issues; the program was undergoing changes that created an unclear vision and shifting requirements, adding turbulence; clear communication between project leadership and open discussion of challenges is important for navigating periods of turbulence; selecting candidates well-suited for open roles and providing needed training and mentoring can help address issues that arise.
This presentation discusses applying principles of guidance, navigation, and control (GN&C) theory to project management. It provides an overview of GN&C theory and how it has been used to model physical systems. The presentation argues that GN&C principles can also be applied to model human project teams as physical systems. It then discusses how GN&C concepts were applied to manage the NASA Constellation Space Suit project, allowing it to meet tight schedules and budgets. The results demonstrated that utilizing modern GN&C approaches can improve a project's performance and outcomes.
The document outlines the organizational structure and timeline of the Constellation Program. The program manager is J. Hanley and the deputy manager is M. Geyer. The program includes several offices and projects focused on areas like engineering, safety, and advanced projects. Key milestones on the timeline include Ares I and II launches between 2009-2016 culminating in the first human launch in 2015. The integrated testing and verification plan involves a series of flight and ground tests leading up to the first uncrewed and crewed Orion missions.
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 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.
The document discusses NASA's Innovative Partnerships Program (IPP), which facilitates partnerships between NASA and external parties. The IPP aims to identify ways to add value to NASA's priorities through a win-win-win approach benefiting NASA, partners, and taxpayers. The IPP encompasses various elements including technology infusion, innovation incubation, and partnership development. It also discusses the value of software reuse across NASA programs and projects and provides examples of where software is used and how much is developed at NASA based on FY09 agency reports.
This document introduces the return on investment (ROI) methodology for measuring the value of project management. It discusses why measuring value is important, as most projects are over budget and behind schedule. The ROI methodology provides a 10-step process for conducting an evaluation, including planning objectives, collecting data during and after implementation, analyzing data, calculating costs and benefits, and reporting results. Implementing ROI can help justify budgets, improve processes, and show how project management contributes to business goals.
This document outlines three NASA development programs: the Program and Project Management Development Program (PPMD), the Project Leadership Program (PLP), and the Small Satellite Engineering Development Program (SSEDP). The PPMD prepares future program and project managers for leadership roles, the PLP and SSEDP develop project management and systems engineering competencies, and all three programs provide training, mentoring, and work assignments. Examples are given of participants from different NASA centers using their program to develop skills for roles in safety assurance, program integration, and engineering.
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.
The Moon Mineralogy Mapper instrument was selected to fly on India's first lunar mission, Chandrayaan-1. Working with the Indian Space Research Organization presented challenges ranging from ITAR issues to cultural differences. These included negotiating interfaces while ITAR agreements were pending and overcoming communication difficulties due to language and process differences. However, both teams achieved a successful outcome through a flexible approach and by addressing challenges through in-person meetings and repeated teleconferences.
This document provides an overview of Microsoft's Project 2007 Server with Project Web Access. It discusses the key components of the Enterprise Project Management system including Project Server 2007, Project Professional 2007, and Project Web Access. It also summarizes Jacobs' customization of the system with templates and views tailored for NASA projects. Project Web Access is highlighted as providing specialized views and reports to facilitate collaboration among project stakeholders.
The document discusses the growing demand for project managers and the Project Management Professional (PMP) certification. It provides statistics on PMP certification holders and salaries. It outlines the requirements to sit for the PMP exam, including education, experience, and training hours required. It describes the exam format, content areas, and costs. It also discusses ongoing continuing education and recertification requirements to maintain the PMP certification.
The document discusses how NASA has used virtual and augmented reality technologies over the past few decades for astronaut training and facility design. It describes some of NASA's early experiments with virtual reality in the 1980s and 1990s for astronaut training. It then outlines various projects NASA's Jet Propulsion Laboratory conducted using virtual worlds like Second Life from 2007-2010 for facility design reviews, meetings, and public engagement. It provides an example of how an virtual design review of a new Earth Science Center helped identify issues and lead to major design changes before construction.
A matrix organization structure combines functional and project-based organization to balance specialized expertise and project accountability. However, it can also lead to role confusion, conflicting goals, and duplication of work between line managers and project managers. The line manager is responsible for organizational goals, resources, external relationships, and staff development, while maintaining awareness of customer needs. Effective collaboration between line managers and project managers is needed to overcome challenges in the matrix structure.
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.
The document discusses balancing NASA's portfolio within tight budgets between successful programs and maintaining institutional capabilities. It addresses whether programs and institutions are competing priorities or if a competitive environment is healthy. It also questions if NASA can succeed with only one or the other. The document also notes challenges around effectively managing NASA's aging infrastructure portfolio, given it controls over 5,400 buildings and structures. Finally, it outlines NASA's budget formulation process and timeline, which allows only a small window for integrating program and institutional budgets.
1. SAIC and ePM used simulation techniques to model and optimize the manufacturing process for the Upper Stage Simulator for the Ares I-X rocket.
2. The simulation results showed that the manufacturing process is highly sensitive to the number of fabricators and welders, and recommended a baseline of 8 fabricators and 6 welders per shift.
3. The investigation of non-destructive inspection factors found that the manufacturing process duration is most impacted by the defect rate during inspections. Higher defect rates significantly increase the overall duration.
The document discusses a case study on risk management challenges for a program transitioning from the Titan IV rocket to new launch vehicles. It describes how failures of the Titan IV led to concerns about losing critical workforce skills. Participants were asked to identify risks and mitigation strategies. The actual Titan IV program implemented strategies like accrual accounts for successful missions, launch awards, identifying critical skills, work sharing programs, and aggressive communication to maintain workforce focus and stability during the transition. The key success factors were starting retention programs early, continuous communication, creating near-term financial incentives for work, and providing long-term transition support and opportunities.
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 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.
The document discusses risk assessment processes at NASA's Marshall Space Flight Center. It provides background on MSFC and its Office of Strategic Analysis and Communication. It then discusses the relationship between cost and schedule, and how quantitative cost and schedule risk assessment is used to determine the probability of finishing a project on time and within budget. The document outlines the basic risk assessment process and various data collection methods that can be used, ranging from most accurate (data interview) to least accurate (heuristic methods).
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.
This document discusses the relationship between spirituality and project management. It defines spirituality as having meaning, values, transcendence, connection, and personal development. Spirituality is described as being in tune with life and helping to align one's work with dimensions that are harmonious. The document then discusses how spirituality relates to the aims of projects in terms of righteousness, wealth, desire, and liberation. It argues that actions on projects should help move toward ultimate goals and building strong connections through trust, nurturing, and shared vision.
The Naval Aviation Enterprise Carrier Readiness Team required a holistic understanding of risks to aircraft carrier availability over the next 10-15 years. They applied a quantitative schedule risk analysis methodology to address questions about how risk impacts availability, cost, schedule, and how mitigation funds should be prioritized. The analysis provided a framework to incorporate uncertainty and risk, using historical data, stakeholder input, and risk modeling to assess impacts on availability metrics and inform strategic recommendations.
This document discusses strategies for developing IT systems that people can and will use. It notes high failure rates of government IT projects and common pitfalls like unclear requirements, poor usability, and lack of focus on business processes. Success strategies include using a project methodology, managing risks, clearly defining outcomes, understanding the environment, involving customers, and communicating frequently. The key is focusing on the customer perspective and engaging people in the process.
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 discusses operability challenges for NASA's Constellation program. It defines operability as the system characteristics that ensure safe flight while minimizing costs during production, operations, and sustainment. The Constellation program has made progress on operability during early design but more work is needed. Key factors like producibility, reliability, interoperability, sustainability, and maintainability must be considered throughout the design process to balance performance and operability.
The document discusses modeling mission operations to reduce risk for NASA's Constellation Program. It begins with defining the goals of incorporating new technologies into operations while controlling risk and cost. It then discusses challenges like the need for increased automation and streamlined systems. The solution involved a collaboration between JSC and ARC to develop a simulation of shuttle operations using BRAHMS modeling tools. This prototype showed benefits like reducing time spent on mirroring tasks from over 5% to under 0.5% of a shift. The conclusions were that BRAHMS feasibility for automating complex MCC tasks was verified and could provide insights into processes while assessing risk.
1) The document discusses the development of requirements for a vehicle through model-based systems engineering.
2) It describes capturing requirements from sources like the customer, operational analysis, technical best practices, and standards.
3) Requirements are developed by tracing vehicle functionality to a concept of operations model and ensuring requirements are necessary, attainable, traceable, and verifiable.
The Constellation Program is transitioning from defining requirements to preliminary design and development of hardware and software for its systems. It leverages a nationwide team from NASA and industry. This team is focused on designing and incrementally integrating and verifying a set of increasingly capable systems over the next decade to meet exploration goals of completing the ISS, retiring the Shuttle, developing Orion and Ares launch vehicles, and returning to the Moon by 2020.
The document describes a project management toolkit developed by NASA Glenn Research Center to help with space flight projects. The toolkit provides a collection of standardized project planning and management tools accessible through a web portal. It aims to facilitate rigorous and compliant project proposal, planning, execution, and control according to NASA requirements and best practices. The development of the operational toolkit was driven by a strategic goal of delivering project management excellence for successful customer missions.
1. The project update discusses the installation timeline for the Integrated Operations Control System (IOCS) software, which is scheduled to be completed by February 2009.
2. Issues addressed include consolidating team members, integrating with other airline applications, and establishing necessary network connections.
3. The summary recommends closely monitoring the software installation, focusing team efforts on implementation, and holding regular team and steering committee meetings to support the project. It also suggests starting an aircraft maintenance planning project.
Overview of CMMI and Software Process ImprovementNelson Piedra
This document summarizes a presentation on software process improvement using CMMI and the IDEAL model. It discusses the key aspects of CMMI including maturity levels and process areas. It also outlines considerations for transitioning to CMMI level 2, including changes required from managers and practitioners. Finally, it shares experiences from initiating corporate-wide process improvements using the IDEAL framework.
Skibsmotorer reducerer brændselsforbruget (IBM Rational)IBM Danmark
Outsourcing skal skabe gode forretningsresultater og ikke blot være en kontraktuel øvelse. Derfor er det vigtigt at tænke test med i processen, således at man kan skabe løsninger af høj kvalitet.
Lær mere om, hvordan du bedst muligt kan stimulere infrastrukturen ved outsourcet softwareudvikling og service gennem cloud computing og SaaS.
Læs mere her: bit.ly/softwaredagrational3
The document discusses the roles and implementation plan of the Constellation Space Transportation Planning Office (CSTP). It outlines that NASA engineers will lead design, development, testing and evaluation of Ares and Orion hardware as well as ground systems. The CSTP will establish key personnel, engage with Constellation projects, define processes, and work on production contracts. The implementation plan shows activities from FY2009 to FY2012 such as establishing project offices, assigning managers, and defining production structure.
The document discusses challenges faced in re-engineering the Mission Operations Directorate's (MOD) Flight Production Process (FPP). Key challenges include: 1) Building support for adopting Model Based Systems Engineering (MBSE) and Enterprise Architecture (EA) methodologies, 2) Resource limitations, 3) Maintaining management support, and 4) Establishing tools for MBSE and EA development. The FPP must be redesigned as an integrated system to address issues like duplication, data errors, and lack of interoperability between its separate processes for Space Shuttle and ISS programs.
The Lunar Surface Systems Project Office was established in 2007 to develop a sustained human presence on the Moon. It focuses on supporting lunar architecture definition and defining technology needs. The office has helped assess transportation system performance and risks. Next steps include further defining concepts for an initial and full lunar outpost capability with potential international and commercial partners.
The document summarizes the development of the Ares I-X Roll Control System (RoCS) for the Ares I-X launch vehicle. The RoCS provided rotational control using a bi-propellant system developed under an Integrated Product Team model. Key aspects included delivering the system on schedule, within budget, and with high quality to support the October 2009 launch. Off-the-shelf and surplus government components were used, including components from decommissioned Peacekeeper missiles, saving over $10 million.
The document summarizes the development of the Ares I-X Roll Control System (RoCS) for the Ares I-X test launch in October 2009. The RoCS team successfully delivered the flight hardware for the Ares I-X launch on time, within budget, and with high quality by utilizing an Integrated Product Team model and harvesting components from decommissioned Peacekeeper rockets. Key factors in the project's success included establishing a small accountable team, early identification of waivers, front-loading the schedule, and maintaining focus on the final integration and launch milestones.
The document discusses the NASA Johnson Space Center's use of model-based systems engineering (MBSE) to develop and manage requirements for space suits. It outlines their MBSE approach, which includes developing operational concepts, architectural models, and requirements models to define the technical baseline for space suits. The models help ensure traceability, support analysis, and allow impacts from changes to be efficiently identified.
The document provides an overview of NASA's Software Engineering Initiative from 2002 to 2008. The initiative aimed to advance software engineering practices across NASA to improve schedule, cost, quality and delivered functionality. It established groups and policies to improve processes, provide training, infuse new technologies, and increase collaboration. Key impacts included improved planning, use of best practices by contractors, and a foundation for disciplined software development through shared process assets.
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.
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 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.
The document discusses project management at NASA. It provides definitions of projects and project management, and traces the evolution of project management from ancient times to the present. It also discusses frameworks for classifying projects based on their complexity, novelty, and pace. Specifically, it introduces the NCTP model for distinguishing project types and analyzing which project management approach is optimal. It analyzes examples like the Denver airport and space shuttle projects using this framework. Finally, it considers some limitations of current project management approaches.
The document discusses powerful phrases for project managers to use in personal communication. It presents 7 phrases and their benefits: thank you, I don't know, you're right, how are you doing, my personal apology, what do you suggest, and what do you need from me. Using these phrases in personal communication with team members can enable additional ideas, insights, confidence, and a strong cohesive team, which are vital for project success.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
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.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
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.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
CAKE: Sharing Slices of Confidential Data on BlockchainClaudio Di Ciccio
Presented at the CAiSE 2024 Forum, Intelligent Information Systems, June 6th, Limassol, Cyprus.
Synopsis: Cooperative information systems typically involve various entities in a collaborative process within a distributed environment. Blockchain technology offers a mechanism for automating such processes, even when only partial trust exists among participants. The data stored on the blockchain is replicated across all nodes in the network, ensuring accessibility to all participants. While this aspect facilitates traceability, integrity, and persistence, it poses challenges for adopting public blockchains in enterprise settings due to confidentiality issues. In this paper, we present a software tool named Control Access via Key Encryption (CAKE), designed to ensure data confidentiality in scenarios involving public blockchains. After outlining its core components and functionalities, we showcase the application of CAKE in the context of a real-world cyber-security project within the logistics domain.
Paper: https://doi.org/10.1007/978-3-031-61000-4_16
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.
Things to Consider When Choosing a Website Developer for your Website | FODUUFODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
National Security Agency - NSA mobile device best practices
Ed.mango
1. Constellation Space Transportation Planning Office
Standing Up at the CSTP Office at KSC
Program Management Challenge
February 2010
Ed Mango
Josephine Burnett
Philip Engelauf
Cheryl McPhilips
David Martin
Maria Collura
NASA KSC
Used with Permission
2. Agenda
Constellation Space Transportation Planning Office
CSTP Overview
Organizational Structure
Accomplishments
Program Update
Operations and Integration
Organizational Structure
Project Update
Launch Vehicle, Space Craft & Ground Operations Projects
Organizational Structure
Project Update
CSTP Forward Work
2
3. Constellation Space Transportation Program
Constellation Space Transportation Planning Office
CSTP will manage the CSTP
Component Refurbishment /
Work Cycle Final Disposition
production, sustaining,
launch preparations,
Element Final Element
mission operations, and Return to OEM Disassembly Element Acceptance
& Production
recovery of the Orion/Ares Evaluation
I vehicle configuration that
Initial Planning, Processing &
will transport crew safely Disassembly Analysis, Integration
Sustaining
to/from the International (H/W & S/W)
Element & Training Launch
Space Station (ISS). Return to KSC Countdown
Launch Start
Recovery
Operations
Mission
Operations
Splashdown Liftoff
Outer Cycle: Hardware phases for each mission cycle
Inner Cycle: Activities supporting multiple mission
cycles
3
4. Constellation Space Transportation Program
Constellation Space Transportation Planning Office
CSTP
Component Refurbishment /
Work Cycle Final Disposition
Element Final Element
Return to OEM Disassembly Element Acceptance
& Production
Evaluation
Initial Planning, Processing &
Disassembly Analysis, Integration
Sustaining
(H/W & S/W)
Element & Training Launch
Return to KSC Countdown
Launch Start
Recovery
Operations
Mission
Operations
Splashdown Liftoff
4
5. Constellation Space Transportation Program
Constellation Space Transportation Planning Office
SOMD
Constellation Space
Constellation Space Transportation Program Constellation Space
Transportation Program Manager Transportation
Deputy PM
Chief Engineer Risk Manager Chief S&MA
Systems
Program Program Planning Operations &
Engineering &
Integration & Control Integration
Prog. Integration (JSC)
Support Services SE&I
Support Services
Spacecraft Launch Vehicle Ground Processing Flight Crew
Mission Operations Extra Vehicular
Production Production & Integration Operations
Directorate Activity
Project Project Project (JSC) (JSC) Directorate (JSC)
Orion Production ARES IIProduction
ARES Production EGLS IMOC FDOC
Project Project Chief
Project
Chief Engineer Project Chief
Safety Officer
Project
Chief Engineer Project Chief
Safety Officer
Project
Chief Engineer Sub-System Engineering Project Chief
Safety Officer
Sub-System
Sub-System
Chief Engineer Managers/
Sub-System Flight Safety Officer
Managers/
Managers/ Software
Managers /Leads
IPT
IPT Leads Analysis
IPT Leads Integration
IPT Leads
5 Engineering
Legend: Level II Level III Matrix Support Prime Contract Support Contract
Matrix Support
6. FY09 Programmatic Accomplishments
Constellation Space Transportation Planning Office
Engage CSTP Project Planning Team and FPSEs with Cx Projects
Strategic Alliance Agreement
Produced Operability White Paper
Initiated Business Plan for low cost LEO alternatives
Virtual Mission 1 participant
Support of Ares I-X through Launch Director, CoFTR planning and
support, launch support
Support many CxP boards, panels
Data Architecture Team , Configuration Management, LCC, TVR’s
CxCB, CSECB, CSIP,SACB, VICB, PCB’s, etc.
Supported CxP O&TI development of Program Operations
Management Plan
Initiated definition of MER Functional Requirements/
Responsibilities
Collection of SEI “Lessons Learn” from SSP and ISS contractors .
6
9. Operations & Integration
Constellation Space Transportation Planning Office
Constellation Space Transportation Planning Office
CSTP
Operations and Integration
Manager
Deputy
– Program Fight Manifest
Technical Assistant – Operational Requirements
Secretary – Operations Schedules
S&MA
Management Integration Program Planning & Control
SE&I
Other JSC Organizations
Mission & Flight Integration Flight Crew Equipment Systems Engineering &
Integration Program Interface
Cargo Engineering &
Integration
9 Legend: Level II Level III Matrix Support
10. Operations and Integration Update
Constellation Space Transportation Planning Office
Conduit for Flight Operations and
Integration community
EVA, Crew, MOD, Space &Life
Sciences, Flight Crew Equipment,
Engineering
Collaboration in CxP OTI
Mission Product Template
Development
Fixed Base Simulator
MOD ops evaluation
MOD 101
Virtual Mission Lead Interface CxP
Motion Base Simulator
Neutral Buoyancy Laboratory
10
12. Spacecraft Production Project
Constellation Space Transportation Planning Office
CSTP Spacecraft Production
Constellation Space Transportation Planning Office
Chief Engineer
Project
Manager Project S&MA Lead
Deputy Procurement
COTR Project Planning & Control
Risk Manager
MSA Admin. Officer
Crew/Service Module Element Vehicle Integration Launch Abort System Logistics
Manager Manager Manager Manager
Deputy Deputy Deputy
Element Element Electrical Power
Integration External Integration Product Mgrs
Field Reps (MAF) Integration Field Reps (ATK)
Human Systems Propulsion Structures / Propulsion
Product Mgrs Product Mgrs Internal Mechanisms / TPS Product Mgrs
Integration Product Mgrs
Electrical Power Flight Dynamics
Product Mgrs Product Mgrs CAIL / T&V
Structures/ Integrated
Mechanisms/TPS Avionics and
Product Mgrs Software
Product Mgrs
12 Legend: Level II Level III Matrix Support
13. Spacecraft Production Project Update
Constellation Space Transportation Planning Office
Significant Collaboration w/ all
launch vehicle elements for
Operability, operational planning
and sustaining engineering concepts.
Participant in Orion PDR
Simulator Orion Crew
Established CSTP Spacecraft Module in KSC O&C
Orion Manufacturing at MAF
COTR focusing on sustaining
contract costs and Production
contract evaluations and
management
Supporting Contract management
including TMR for Production,
CSIP lead, and misc. contract
support.
Supporting ground and mission
operations design support
Post-landing Orion Recovery Test
Operability Assessments such as (PORT)
Kaizen events
13
15. Launch Vehicle Production Project
Constellation Space Transportation Planning Office
Launch Vehicle Production
Project
Launch Vehicle Manager
Deputy
MSA
Administrator
Chief Engineer 1st Stage Element 2/3/4
Upper Stage Element Chief Engineer
2/3/4
Project S&MA Lead Element Manager Element Manager Project S&MA Lead
Deputy LV Integration Deputy
Procurement Procurement
COTR Element Mgr COTR
Project Planning & Control MSA Deputy MSA Project Planning & Control
Production Site Field Reps Production Site Field Reps
TPS/Mat’l Structures Pyro, Prop, Avionics TVC S&T Avionics TVC/RoCS J2X/MPS USM/Pyro
& Recovery Elec/Instr ReCS
Product Product Product Product Product Product Product
MGRS MGRS Product MGRS MGRS MGRS Product Product MGRS MGRS
MGRS MGRS MGRS
15 Legend: Level III Matrix Support
16. Launch Vehicle Production Project Update
Constellation Space Transportation Planning Office
Significant Collaboration w/ all launch vehicle
elements for Operability, operational planning
and sustaining engineering concepts.
Participant at all levels on element boards ,
planning meetings, quarterly and monthly
reviews.
CSTP personnel and FPSE’s at design
Michoud Assembly Facility center nearly 100%
Develop Launch Vehicle Project
Organization Concept and Planning for
Sustaining
Ares 101 training at KSC.
Vehicle Integration – Operational Integration of
Ares I at KSC.
Support the Operability Assessment Team
Upper Stage & Upper Stage Engine. –
Super sonic film cooling
Sustaining Engineering Plan
effectiveness testing
First Stage
participation in the Life Cycle Cost
J2-X Engine Reduction Study
Assist EGLS contract definition for First
Stage.
16
18. Ground Processing and Integration Project
Constellation Space Transportation Planning Office
CSTP Ground Processing and
Constellation Space Transportation Planning Office
Chief Engineer
Integration Project
Project S&MA Lead
Manager
Deputy Contract Mgmt Procurement
COTR Project Planning & Control
MSA Admin. Officer
Flight Systems Ground Systems Integration Logistics
Manager Manager Manager Manager
Deputy Deputy Deputy
First Stage Orion Mobile Flow
MPPF CoFR
Lead Lead Launcher Management
Upper Stage RSPF/ARF/P
Integration VAB Test Ops Business
Lead RF/Hangar
Lead Systems
AF, N
Configuration Manifest
Launch Pad CCC Management Planning
18 Legend: Level II Level III Matrix Support
19. Ground Processing and Integration Project Update
Constellation Space Transportation Planning Office
Conduit for Ground Operations and Mobile Launcher Construction
Integration community at KSC
Center Operations,
Engineering
Collaboration w/ CxP Ground
Operations Project
GPI - support GPD ODT.
EGLS contract management
planning.
Participant in the GOP PDR Lightning Mast Installation
at Launch Pad 39B
19
20. CSTP Forward Work
Constellation Space Transportation Planning Office
FY10 FY11 FY12
Expand Interaction with CxP
Projects
Initiate definition of Program Prepare FAD/PCA for approval Establish Project Offices /
Processes Establish Program Office, Assign Managers
Obtain Agency approval of plan Program Manager Assign System Project Managers
to procure and sustain LEO Partner Chief Engineer/ETA Partner Sub-System Managers
capability Assignment assignments
Continue Program Planning Partner Chief Safety Officer/STA Facility and System O&M
Develop System Integration Plan Assignment Support T&E Flight Tests
Define Inter-Center Task Prepare Program Plan Initiate Flight/Mission Planning
Agreements Establish Program Office key Execute CxP to CSTP transition
Work Contract Structure positions plan
Define Production Structure Contract Management Office
Establish Sharing for DDTE Draft CxP to CSTP handover plan
Production Engineering with (collaborative agreements)
MSFC and JSC Establish EGLS contract management
Support CxP PDR office
Establish EGLS contract Further collaboration into production,
management role supply chain management
Ares 2X flight test planning
20