The document summarizes a presentation about NASA's Johnson Space Center's (JSC) approach to integrating facilities planning information across the center. It describes how JSC developed a Facilities Review Database (JFReD) to capture and assess facility usage and cost data over multiple years. JFReD integrates with JSC's Geographic Information System to allow visualization of facility locations and utilization profiles. It also incorporates capabilities assessment information to support strategic planning for facilities and technical capabilities.
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.
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.
This document discusses efforts to extract operational performance data from historical spaceflight records to inform cost and operations modeling.
It describes challenges in obtaining usable data due to inconsistent recording practices and lack of recording non-milestone data. However, it notes that "gold dust" can still be found by mining records created for other purposes.
Case studies of data mining Space Shuttle and other launch vehicle records are presented, along with examples of metrics extracted to support modeling tools for cost estimation, reliability analysis, and design root cause analysis. Lessons learned around synthesizing data from multiple sources and accounting for changes in recording practices over time are also shared.
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.
Monitoring and Evaluation Plan for Africa RISINGafrica-rising
The document provides a monitoring and evaluation plan for the Africa RISING program. It outlines the program's objectives to sustainably intensify agricultural systems in Africa. Key activities include on-farm trials, scaling of technologies, and value chain improvements. The M&E plan aims to support project management, learning, and reporting. It details indicators, methods, roles, and commitments such as providing open-access data. The plan outlines approaches for monitoring multiple scales, evaluating impacts, and ensuring compliance with Feed the Future standards.
Arasin T.M. Staubly is a retired Master Sergeant in the U.S. Air Force with over 20 years of experience in project management, technical evaluation, training, data management, and organizational development. He has a Top Secret SCI clearance and experience managing communication/IT systems, conducting compliance inspections, overseeing budgets, and leading inventory projects. Staubly has extensive experience using tools like Excel, Word, PowerPoint, SharePoint, and data management systems. He has managed multi-million dollar projects and led teams across several international locations.
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.
Kevin Allen has over 10 years of experience using GIS software such as ESRI ArcGIS and Google Earth. He has worked on a variety of environmental planning, military, and engineering projects. Allen is skilled at analyzing geospatial data, creating maps and other deliverables, and communicating technical information clearly. He has a history of successfully leading GIS teams and initiatives to help organizations meet their goals.
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.
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.
This document discusses efforts to extract operational performance data from historical spaceflight records to inform cost and operations modeling.
It describes challenges in obtaining usable data due to inconsistent recording practices and lack of recording non-milestone data. However, it notes that "gold dust" can still be found by mining records created for other purposes.
Case studies of data mining Space Shuttle and other launch vehicle records are presented, along with examples of metrics extracted to support modeling tools for cost estimation, reliability analysis, and design root cause analysis. Lessons learned around synthesizing data from multiple sources and accounting for changes in recording practices over time are also shared.
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.
Monitoring and Evaluation Plan for Africa RISINGafrica-rising
The document provides a monitoring and evaluation plan for the Africa RISING program. It outlines the program's objectives to sustainably intensify agricultural systems in Africa. Key activities include on-farm trials, scaling of technologies, and value chain improvements. The M&E plan aims to support project management, learning, and reporting. It details indicators, methods, roles, and commitments such as providing open-access data. The plan outlines approaches for monitoring multiple scales, evaluating impacts, and ensuring compliance with Feed the Future standards.
Arasin T.M. Staubly is a retired Master Sergeant in the U.S. Air Force with over 20 years of experience in project management, technical evaluation, training, data management, and organizational development. He has a Top Secret SCI clearance and experience managing communication/IT systems, conducting compliance inspections, overseeing budgets, and leading inventory projects. Staubly has extensive experience using tools like Excel, Word, PowerPoint, SharePoint, and data management systems. He has managed multi-million dollar projects and led teams across several international locations.
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.
Kevin Allen has over 10 years of experience using GIS software such as ESRI ArcGIS and Google Earth. He has worked on a variety of environmental planning, military, and engineering projects. Allen is skilled at analyzing geospatial data, creating maps and other deliverables, and communicating technical information clearly. He has a history of successfully leading GIS teams and initiatives to help organizations meet their goals.
The document discusses managing requirements and architecture volatility for NASA's CPAS (CEV Parachute Assembly System) project. It summarizes how [1] requirements and architectures can change over time as multiple organizations work together, [2] early CPAS requirements exceeded Apollo-era requirements, and [3] collaboration between CPAS and Lockheed Martin helped establish interim requirements to allow design work to proceed.
The document discusses developing high performance teams. It provides an overview of team building components including purpose, structure, motivation, dynamics, communication and respect among members. Effective team leadership is highlighted as understanding organizational context, goals, stakeholders and communicating clearly. High performing teams are balanced and implement processes to maximize efficiency through cooperation and buy-in from team members. Ten reasons for using teams are presented, including reducing stress, creating consensus, leveraging diversity, continuous improvement, and producing better solutions that get implemented because everyone is invested in the team's success.
This document discusses Lockheed Martin's approach to achieving mission success. It outlines that mission success means delivering quality products and services that meet or exceed customer requirements. It emphasizes that mission success requires contributions from organizations, processes, people and facilities. Several past mission failures are reviewed and attributed to factors such as engineering errors, inadequate testing, and failures to follow procedures. The document proposes seven key elements to ensure mission success, including having a mission success advocate and independent reviews. It stresses that mission success must be a continuous focus throughout the entire program life cycle.
The document describes the evolution of command and control systems at Kennedy Space Center from the 1950s to present day. Early systems involved manually controlling launches from vehicles. As systems grew more complex, automation was required. The Space Shuttle introduced digital controls. For future vehicles like Constellation, a new standards-based system was designed using commercial off-the-shelf components. The Launch Control System is now operational and supports multiple customers and vehicles.
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.
NASA has implemented CMMI models to improve software engineering processes. Key impacts include reduced risk, more accurate cost estimates, and finding defects earlier. NASA requires a minimum CMMI level for contractors depending on software class. Lessons learned are that preparation is critical, tools help achieve compliance, and cultural changes have significantly improved practices. CMMI provides a proven approach to manage performance if defined processes are used, results measured, and continuous improvements made.
Architecture is a foundational element of complex system design. Upfront analysis and architecting helps understand essential requirements and reduce incidental complexity through a well-designed structure. This recommendation promotes investing in system-level thinking to establish a solid foundation addressing the problem, rather than its symptoms.
This document discusses Langley Research Center's new approach to project teams in support of NASA's Constellation Program. Langley has established 6 project teams over the last 9 months to support Orion, Ares, and other aspects of Constellation. Langley's approach is based on projectizing its support and integrating its project teams with partner teams at other NASA centers. Langley is developing a project management system and practices handbook adapted from other centers to manage its new exploration projects.
The role of a Program Executive (PE) at NASA involves serving as both an advocate and enforcer for projects. As an advocate, PEs defend projects, promote their science and success, and help projects navigate NASA requirements and processes. However, PEs must also enforce NASA rules to ensure projects follow cost, schedule, technical, and policy requirements. This dual role requires PEs to balance supporting projects while also preventing problems. PEs aim to help projects succeed by facilitating resources, coordinating reviews, and ensuring projects have support across the agency.
This document discusses applying navigation techniques used for deep space missions to cost and schedule monitoring and control of projects. It notes that cost estimates and project progress are uncertain and subject to biases. It recommends treating estimates as distributions rather than single values, understanding biases in estimators, resources, financial reporting, and performance tracking over time. Applying these biases can provide more accurate estimates of expected total costs and allow for faster response to funding changes or issues, increasing the probability of completing projects on budget.
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 unspoken fears that brave project managers face, including unrealistic expectations, lack of support, and stress, and provides techniques for managing fears such as making lists, focusing on facts, discussing concerns with others, and establishing work-life balance. It also outlines causes of stress for project managers like unrealistic deadlines and organizational politics.
The document outlines the LAUNCH initiative, which aims to accelerate sustainable development solutions through convening a council of global leaders to provide guidance and support to innovators working on sustainability challenges. The inaugural LAUNCH forum will focus on water sustainability and bring together a council representing different sectors to engage with 10 innovators and help accelerate the adoption of their solutions. NASA is a founding partner and will provide strategic guidance and leverage its expertise to help realize a more sustainable future.
The Constellation Program Planning and Control office oversees planning, control, and integration activities for NASA's Constellation Program. It ensures proper implementation of NASA policies and procedures, including NASA Procedural Requirements 7120.5D which outlines life cycle project management requirements. Lessons learned from establishing the Constellation Program include thoroughly understanding 7120.5D requirements, having validated program baselines ready for review, and proactively engaging convening authorities and other stakeholders.
This document outlines the investigation process of the NASA Organization Design Team. It describes three tracks of the investigation: 1) inviting lectures from program managers to identify best practices and lessons learned, 2) identifying tools to design and assess organizations, and 3) pilot studies applying those tools. The goal is to capture these lessons into a "toolkit" to disseminate organizational best practices across NASA. Track 1 involved 12 lectures on programs like Apollo, the F-117 stealth fighter, and submarines. The lectures explored organizational strategies for complex technical projects.
This document discusses what makes a good project schedule. It explains that a good schedule is predictive by showing relationships between activities, reflective by accurately tracking progress against the plan, and dynamic by adjusting when changes occur. Characteristics of a predictive schedule include predecessors/successors for tasks and minimal constrained dates. Reflective schedules include expected work streams and milestones to check progress. Dynamic schedules have an up-to-date baseline and status dates, without past start/finish dates and incomplete work. The key reasons for having a good schedule are to map out the work, forecast completion, measure progress against plans, and assess impacts of changes.
The document summarizes the activities and research projects of the Integrated Media Systems Center (IMSC) at the University of Southern California. IMSC is an NSF Engineering Research Center that conducts research in multimedia and immersive technologies through partnerships with industry, government agencies, and other universities. Its research focuses on areas like immersive audio, computer vision, graphics & animation, and virtual reality simulations. IMSC also supports education programs and has graduated over 200 students. Its application projects include ImmersiNet for entertainment, InterAct for communication, and 2020Classroom for education.
This document discusses a historic NASA project failure. It provides charts showing the project's approved budget over time compared to estimates and actual costs. It shows that after an initial milestone was passed, costs grew substantially until a stop work order was issued. The project highlights the importance of accurate cost estimating and controlling costs once development begins.
The document discusses the phases of developing an in-house cost estimate (IHCE) for the Space Network Ground Segment Sustainment (SGSS) project. It describes four phases: 1) developing a conceptual estimate using parametric models, 2) refining the estimate using a bottoms-up approach, 3) aligning the cost structure based on matured requirements, and 4) performing a risk analysis to assess confidence levels. Key lessons learned include starting early, using a team approach, adapting to changes, and ensuring confidence through multiple iterations.
The document discusses contingency plans for project management, including that preliminary contingency plans should be completed during Phase B of a project and updated throughout the project lifecycle. It outlines what should be included in a contingency plan such as checklists, response teams, evidence handling procedures, hazardous materials handling, and expiration dates. It also defines mishaps and close calls, describes appointing officials and high visibility events, the need for contract clauses covering investigations, and the corrective action process if an investigation occurs.
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 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 managing requirements and architecture volatility for NASA's CPAS (CEV Parachute Assembly System) project. It summarizes how [1] requirements and architectures can change over time as multiple organizations work together, [2] early CPAS requirements exceeded Apollo-era requirements, and [3] collaboration between CPAS and Lockheed Martin helped establish interim requirements to allow design work to proceed.
The document discusses developing high performance teams. It provides an overview of team building components including purpose, structure, motivation, dynamics, communication and respect among members. Effective team leadership is highlighted as understanding organizational context, goals, stakeholders and communicating clearly. High performing teams are balanced and implement processes to maximize efficiency through cooperation and buy-in from team members. Ten reasons for using teams are presented, including reducing stress, creating consensus, leveraging diversity, continuous improvement, and producing better solutions that get implemented because everyone is invested in the team's success.
This document discusses Lockheed Martin's approach to achieving mission success. It outlines that mission success means delivering quality products and services that meet or exceed customer requirements. It emphasizes that mission success requires contributions from organizations, processes, people and facilities. Several past mission failures are reviewed and attributed to factors such as engineering errors, inadequate testing, and failures to follow procedures. The document proposes seven key elements to ensure mission success, including having a mission success advocate and independent reviews. It stresses that mission success must be a continuous focus throughout the entire program life cycle.
The document describes the evolution of command and control systems at Kennedy Space Center from the 1950s to present day. Early systems involved manually controlling launches from vehicles. As systems grew more complex, automation was required. The Space Shuttle introduced digital controls. For future vehicles like Constellation, a new standards-based system was designed using commercial off-the-shelf components. The Launch Control System is now operational and supports multiple customers and vehicles.
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.
NASA has implemented CMMI models to improve software engineering processes. Key impacts include reduced risk, more accurate cost estimates, and finding defects earlier. NASA requires a minimum CMMI level for contractors depending on software class. Lessons learned are that preparation is critical, tools help achieve compliance, and cultural changes have significantly improved practices. CMMI provides a proven approach to manage performance if defined processes are used, results measured, and continuous improvements made.
Architecture is a foundational element of complex system design. Upfront analysis and architecting helps understand essential requirements and reduce incidental complexity through a well-designed structure. This recommendation promotes investing in system-level thinking to establish a solid foundation addressing the problem, rather than its symptoms.
This document discusses Langley Research Center's new approach to project teams in support of NASA's Constellation Program. Langley has established 6 project teams over the last 9 months to support Orion, Ares, and other aspects of Constellation. Langley's approach is based on projectizing its support and integrating its project teams with partner teams at other NASA centers. Langley is developing a project management system and practices handbook adapted from other centers to manage its new exploration projects.
The role of a Program Executive (PE) at NASA involves serving as both an advocate and enforcer for projects. As an advocate, PEs defend projects, promote their science and success, and help projects navigate NASA requirements and processes. However, PEs must also enforce NASA rules to ensure projects follow cost, schedule, technical, and policy requirements. This dual role requires PEs to balance supporting projects while also preventing problems. PEs aim to help projects succeed by facilitating resources, coordinating reviews, and ensuring projects have support across the agency.
This document discusses applying navigation techniques used for deep space missions to cost and schedule monitoring and control of projects. It notes that cost estimates and project progress are uncertain and subject to biases. It recommends treating estimates as distributions rather than single values, understanding biases in estimators, resources, financial reporting, and performance tracking over time. Applying these biases can provide more accurate estimates of expected total costs and allow for faster response to funding changes or issues, increasing the probability of completing projects on budget.
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 unspoken fears that brave project managers face, including unrealistic expectations, lack of support, and stress, and provides techniques for managing fears such as making lists, focusing on facts, discussing concerns with others, and establishing work-life balance. It also outlines causes of stress for project managers like unrealistic deadlines and organizational politics.
The document outlines the LAUNCH initiative, which aims to accelerate sustainable development solutions through convening a council of global leaders to provide guidance and support to innovators working on sustainability challenges. The inaugural LAUNCH forum will focus on water sustainability and bring together a council representing different sectors to engage with 10 innovators and help accelerate the adoption of their solutions. NASA is a founding partner and will provide strategic guidance and leverage its expertise to help realize a more sustainable future.
The Constellation Program Planning and Control office oversees planning, control, and integration activities for NASA's Constellation Program. It ensures proper implementation of NASA policies and procedures, including NASA Procedural Requirements 7120.5D which outlines life cycle project management requirements. Lessons learned from establishing the Constellation Program include thoroughly understanding 7120.5D requirements, having validated program baselines ready for review, and proactively engaging convening authorities and other stakeholders.
This document outlines the investigation process of the NASA Organization Design Team. It describes three tracks of the investigation: 1) inviting lectures from program managers to identify best practices and lessons learned, 2) identifying tools to design and assess organizations, and 3) pilot studies applying those tools. The goal is to capture these lessons into a "toolkit" to disseminate organizational best practices across NASA. Track 1 involved 12 lectures on programs like Apollo, the F-117 stealth fighter, and submarines. The lectures explored organizational strategies for complex technical projects.
This document discusses what makes a good project schedule. It explains that a good schedule is predictive by showing relationships between activities, reflective by accurately tracking progress against the plan, and dynamic by adjusting when changes occur. Characteristics of a predictive schedule include predecessors/successors for tasks and minimal constrained dates. Reflective schedules include expected work streams and milestones to check progress. Dynamic schedules have an up-to-date baseline and status dates, without past start/finish dates and incomplete work. The key reasons for having a good schedule are to map out the work, forecast completion, measure progress against plans, and assess impacts of changes.
The document summarizes the activities and research projects of the Integrated Media Systems Center (IMSC) at the University of Southern California. IMSC is an NSF Engineering Research Center that conducts research in multimedia and immersive technologies through partnerships with industry, government agencies, and other universities. Its research focuses on areas like immersive audio, computer vision, graphics & animation, and virtual reality simulations. IMSC also supports education programs and has graduated over 200 students. Its application projects include ImmersiNet for entertainment, InterAct for communication, and 2020Classroom for education.
This document discusses a historic NASA project failure. It provides charts showing the project's approved budget over time compared to estimates and actual costs. It shows that after an initial milestone was passed, costs grew substantially until a stop work order was issued. The project highlights the importance of accurate cost estimating and controlling costs once development begins.
The document discusses the phases of developing an in-house cost estimate (IHCE) for the Space Network Ground Segment Sustainment (SGSS) project. It describes four phases: 1) developing a conceptual estimate using parametric models, 2) refining the estimate using a bottoms-up approach, 3) aligning the cost structure based on matured requirements, and 4) performing a risk analysis to assess confidence levels. Key lessons learned include starting early, using a team approach, adapting to changes, and ensuring confidence through multiple iterations.
The document discusses contingency plans for project management, including that preliminary contingency plans should be completed during Phase B of a project and updated throughout the project lifecycle. It outlines what should be included in a contingency plan such as checklists, response teams, evidence handling procedures, hazardous materials handling, and expiration dates. It also defines mishaps and close calls, describes appointing officials and high visibility events, the need for contract clauses covering investigations, and the corrective action process if an investigation occurs.
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 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.
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 Navy’s GeoReadiness Repository builds on a Web services, using ArcObjects 9 and open
standards, and provides the Navy with the following:
• Authoritative source of geospatial data for Navy Real Property in support of Critical
Infrastructure and Force Protection, Shore Installation Management, and
Environmental Protection
• Baseline architecture for a network of Regional Repositories
• Portal that integrates functional applications and databases
• Security controls limiting access to specific data layers
• Quality control by automating the SDSFIE Standards and IVT Quality Assurance
Plan compliance check function, and
• Access between authoritative geospatial databases
The document provides details of the individual's professional experience including roles as Chief of GIS/Spatial Data Systems and various project management roles at the District Department of Transportation from 2007-2010. Some key responsibilities and projects mentioned include establishing GIS committees and programs, managing the development of an Enterprise Asset Management System, upgrading the Street Inventory System, and developing asset inventories.
The document discusses applying Model-Based Systems Engineering (MBSE) to analyze trade studies for NASA's Space Communications and Navigation (SCaN) integrated network architecture. It provides an overview of MBSE and compares it to traditional document-based approaches. The document then details how MBSE was used to model existing network elements, potential architecture options, and operational scenarios to enable comparison and analysis. Products of the MBSE analysis included models of network element workflows and proposed integrated network control concepts. MBSE allowed more efficient evaluation of the complex SCaN system architecture alternatives than traditional documentation-based methods.
This document provides a summary of William J. White's professional experience, including his roles as a Senior Radar Engineer, System Engineer, and Program Manager. Over his long career spanning back to 1969, he has gained extensive experience in radar, tactical data communication design, and program/project management for both government and private sector organizations. His areas of expertise include spectrum management, requirements development, risk management, and systems engineering.
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.
ISR-Smarter Strategic Program - K2H_Rev2-PD-30minPedro De Jesus
This document discusses the importance of strategic programming for ISR (intelligence, surveillance, and reconnaissance) facilities. It notes that traditional facility programming methods are insufficient for ISR operations centers, which require human-centered design to support constantly evolving missions and technology. The document outlines an approach to strategic programming that involves assembling an interdisciplinary team, assessing facility needs, determining requirements, developing options to address gaps, and justifying funding to support the mission over the long term in a flexible, adaptable manner. The goal is to program facilities that enhance the human-centered ISR mission rather than constrain it.
The document provides an update on projects within the Earth Science Data and Information System (ESDIS). Recent progress includes the delivery of version 8.1 of the ECS software, which consolidated databases and improved data access capabilities. The ECHO search tool was replaced with Reverb, improving query times. The Worldview visualization tool now supports over 50 global satellite imagery products. The Coherent Web project consolidated various NASA websites and added new features like labs and metrics viewers. Phase 1 of the Universal Registration System will transition user authentication for some EOSDIS tools. Overall metrics show continued growth in archive size, data distribution, and user activity on EOSDIS systems.
This document contains a summary of Raj Ganesh Subramanian's work experience and qualifications. He has over 5 years of experience in data warehousing, ETL development, and database management. He has extensive experience with Informatica PowerCenter and has worked on projects for clients such as GE Transportation, GE Aviation, and IGATE Technologies. He has expertise in Oracle, SQL Server, Informatica, Unix scripting, and reporting tools such as Spotfire, Tableau, and Cognos.
POLARIS is a web-based tool developed by NASA to help project managers access information and requirements related to project management. It provides a searchable database of NASA's project management requirements and templates. Future enhancements may include additional requirements, review content, and linking the tool to NASA's metadata database to integrate more project information. The tool aims to be continually improved based on user feedback to better support NASA's project management community.
During the June 2010 quarterly meeting of the Tennessee Board of Regents, board members approved an implementation plan recommended by the National Center for Higher Education Management Systems (NCHEMS) that called for the creation of a data warehouse to be used to enhance decision-making at both the system and campus levels. The strategy now referred to as the “Common Data Repository” (CDR) is to create a single authoritative data warehouse where data from institutions will automatically be fed into the CDR from their Banner administrative systems be they hosted or located at the campus. The presentation provided an overview of the project as to its strategic purpose, how the technology will work, and the role that the functional users will play (including governance).
Dax Garner is an experienced C/C++ programmer and aerospace engineer with over 6 years of experience developing Linux-based applications for space systems. He currently works as a Guidance, Navigation and Controls Engineer at Firefly Space Systems, where he leads the navigation algorithm design and simulation development for an orbital rocket. Prior to this, he held engineering roles at Odyssey Space Research and Lockheed Martin, where he developed flight software, simulations, and verification tools for programs including Orion, Dragon, and NASA's Core Flight Software. He has a Master's degree in Aerospace Engineering from the University of Texas at Austin.
MCE GeoProcessing Services for ADM(IE): Self Validation of Spatial Data Input...Safe Software
The Department of National Defence (DND) is developing a central repository for land, building, and infrastructure data. This a joint project between the Assistant Deputy Minister Infrastructure and Environment (ADMIE) and the Mapping and Charting Establishment (MCE). This project involves managing DND real property and other spatial data provided by DND bases and wings across Canada through a unique, integrated and standardized Real Property Spatial Data Warehouse (RPSDW), hosted at MCE, containing a SQL Server database. Data provided by DND bases and wings must meet standards defined and documented by ADMIE, in terms of data formats accepted (GeoMedia MDB, ArcGIS FGDB, MapInfo MIF or AutoCAD SDF), geometry, schema and attribute data types, domains and accepted values for each feature class. An FME workspace and an equivalent tool contained within an ArcGIS Data Interoperability Toolbox were created to provide the geotechs from DND Bases using ArcGIS Data Interoperability or FME Desktop with a toolset, delivered together with a user’s guide, that allows them to perform a self-validation of the DND real property and other spatial data before these data is sent to MCE to be loaded into the RPSDW SQL Server database.
Neeti Pratap has over 6 years of experience in business intelligence, data warehousing, and software consulting. She has extensive experience designing, developing, and implementing business intelligence and data warehousing projects using tools like SAP Business Objects. She is skilled in gathering requirements, data modeling, ETL processes, report development, and testing. Her past projects include developing the data warehouse and reports for several banks to support equity compensation, risk management, and trading systems.
Neeti Pratap has over 6 years of experience in business intelligence, data warehousing, and software consulting. She has extensive experience designing, developing, and implementing business intelligence and data warehousing projects using tools like SAP Business Objects. She is skilled in gathering requirements, data modeling, ETL processes, report development, and testing. Her past projects include developing the data warehouse and reports for Citi Bank's equity compensation and Mexico business units.
Aden Bahdon has over 15 years of experience as an Oracle developer and database administrator, specializing in designing and implementing data warehouse solutions. He has extensive experience working on projects for clients such as IBM Canada, Bell Canada, and the Department of National Defence, where he developed databases, ETL processes, and reports. His skills include Oracle, SQL, PL/SQL, Java, DataStage, MicroStrategy, and he has experience in all phases of the software development lifecycle.
Shelby Rotenberry has over 10 years of experience in project management, logistics, and program analysis roles supporting various defense programs. She currently works as a Facility Staff Support Associate for Tactical Edge, where she performs tasks such as maintaining tracking products, running reports, facilitating meetings, and reviewing documents. Previously, she held positions as a Project Scheduler, Program Analyst, Logistics Database Manager, and Staff Analyst, supporting programs focused on communications, GPS systems, and more. She has a Master's degree from Mississippi State University and security clearance.
The document discusses NASA's center-wide facilities planning process at Johnson Space Center over 3 years from 2007-2009. It outlines the objectives of conducting annual facilities reviews and assessments to capture facility data, usage requirements, and cost estimates. This information is stored in a database called JFReD to help analyze closeout candidates, gaps, and utilization trends to support strategic decision making. The approach evolved over the years to improve data validation, tracking of updates, and reporting/analysis capabilities. Continued integration with other facility data tools is needed to align strategic and tactical facility planning goals.
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 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.
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.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
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.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
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.
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.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
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
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.
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.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
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.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
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.
1. Center-wide Facilities Planning:
An Information Integration
Approach
NASA Project Management Challenge 2011
February 9-10, 2011
Track: Facilities
Presenters:
Perri E. Fox, Transition Manager
NASA-Johnson Space Center
Lovely Krishen, Ph.D., Lead Risk Analyst-Transition Team Lead
Futron Corporation
2. Outline
• Introduction
• NASA-JSC Center-wide Facilities
Assessment: An Overview
• JSC Facilities Review Database (JFReD)
– Information Integration with Geographic
Information System (GIS)
– JFReD-GIS features
• Building Information Architecture for JSC
Capabilities
– JSC Technical Capabilities Tiger Team (TCTT)
– JFReD: JSC Capabilities Assessment Module
(JCAM) features
• Summary
• Backup Slides
February 9, 2011 2
3. Introduction
•As part of Transition management, JSC has been
integrating facilities planning information and
performing high-level gap analysis to feed decision
makers at the Center level
– Capturing comprehensive facility listing, description and
baseline cost estimates
– Assessing budget associated with closeout, gaps and
utilization of the facilities (Workforce and Dollars) tied to
Core Capabilities
– Linking utilization of buildings/facilities for overall Center
Master Planning efforts
•Pre-decisional data capture initiated and updated
over 4 years – now initiating data collection for a 5th
year
•Currently, focused on supporting Center and
Agency-wide scalability and strategic planning for
facilities and capabilities utilization
February 9, 2011 3
4. JSC Facilities Assessment: An Overview
• A facility is primarily defined by a real property component that
represents a significant (or core) capability or asset and becomes a factor
in the overall center “supply” to meet the “demand” of
mission, program, or project requirements
– For JSC, includes labs, aircraft, test stands, specialized equipment, storage
areas, mission operations/planning areas or entire buildings
– Does not include office space or other personnel support areas (break
rooms, general conference rooms, restrooms, equipment closets, etc.)
•Information capture, assessment, and reporting processes -
established, tested, and refined over time by JSC Transition management
team
•The only baselined JSC Facilities Listing and the standard for Center Ops
Facilities Utilization activities
•Assessment and JSC Facilities listing originally captured in FY2007 in
spreadsheets – but this was quickly outgrown
JSC Transition Team Designed and Developed JSC Facilities
Review Database - JFReD
February 9, 2011 4
5. JFReD Description and Capability
•The JSC Facilities Review Database (JFReD) is…
– A user-interface, secure web-based application with advanced
data archiving and reporting capabilities that synthesizes
integrated analysis and decision/metrics reports for Center
Management
•Provides a baseline listing of all facilities at JSC, Ellington, El
Paso, Sonny Carter Neutral Buoyancy Lab, and White Sands
Test Facility (WSTF) sites
•Tracks/assesses Facilities Usage requirements and associated
Resource profiles over a multi-year timeframe with pre-
decisional inputs from
– Managing DLO Facility owners (“Supply” data)
– Funding Programs/Customers (“Demand” data)
– Center Operations – infrastructure and master planning
•Established User Group with JSC and Headquarters members
•Provider of Best Practices and Lessons Learned in information
management of infrastructure planning and disposition
February 9, 2011 5
6. JFReD Integration with JSC-GIS
•With changes in Agency direction, found growing demand for
right-sizing the Centers and scaling capabilities and associated
facilities
•JSC Transition team proposed direct information exchange
between JFReD and JSC space utilization and real property
databases
•Geographic Information System (GIS) provides a framework
for organizing institutional real property spatial information
– Integrates data from several sources, including JSC’s Space
Utilization Tool (SUT) and Real Property Inventory (RPI)
•JFReD integration with GIS is designed to:
– Promote convergence of facility information gathering processes
at JSC
– Provide graphical visualization of facility location and utilization
profiles over planning timelines
– Maintain quality control and standardization of JSC space
utilization and facility location information
February 9, 2011 6
8. JSC-GIS Data Exchange Process
*Outlined in the JFReD-GIS Interface Control Requirements Document
February 9, 2011 8
9. JFReD-GIS Integration Benefits
• Center Operations (COD) is responsible for
maintaining the configuration of the buildings/rooms at
JSC
– JFReD users will be able to see the data, but not change it
• COD has already been approving facility changes to
JFReD.
– Facility change requests can still be made to JFReD
administrators who will work with COD and obtain approval
•Less data entry into JFReD
– No need to enter facility
name, center/site, rooms, buildings, square footage, facility
class/subclass
•Ability to be able to look at Utilization Data spatially
– Can look at any building or any floor of any building that is
utilized by a JSC facility
– Facility owners are color-coded at the DLO level
February 9, 2011 9
19. Decision-making Approach: JSC
Capabilities Assessment
• Facilities grouped together to define JSC-unique Capabilities
• These Associated Facilities groupings formed the basis for capturing
and assessing Technical Capabilities (TCs)
– JSC Technical Capabilities Tiger Team (TCTT) chartered in August 2010
to initiate capture of a structured Center-wide Technical Capabilities
Listing
– Assess Ready-to-produce costs/resources and prioritization criteria
based on mapping to potential mission scenarios
– Provide insights into recommended scalability-based cost-savings
measures
– Prepare for NASA Technical Capabilities Assessment cycle
• JFReD platform is incorporating data or mapping from other Real
Property and Capabilities assessments
– At JSC: GIS; TCTT Skill-Based TCs, Facilities-Based TCs, and Core
Technical Capabilities
– Agency: NASA Capabilities Forum (NCF) Gap Assessments; Major
Facilities Inventory; Real Property Inventory; NASA Technical Capabilities
(NTC)
February 9, 2011 19
21. Technical Capabilities Assessment at JSC
•Definition of Technical Capability (TC): “All of the
facilities/infrastructure, property/equipment, workforce
(FTE/WYE, with competency/skills), and support
(suppliers/supplies, contracts, control systems)
required to accomplish a given program’s mission
execution requirements"
•JSC TCTT adopted the following approach:
–Capability owners enter Capability Listing data, which
includes a basic capability description, NASA Agency (OCE)
capability categories, Uniqueness, and Associated Facilities
(if applicable)
Capabilities may be skill-based
Tie back directly to JFReD Baselined data
Defines the “supply” aspect of the assessment - individual
records managed at the Direct Line Organizational (DLO)
level
For JSC Core Technical Capabilities (CTCs), DLO-
managed sub-capabilities are grouped into JSC-managed
Core Capabilities
February 9, 2011 21
22. Technical Capabilities Assessment at JSC, cont.
– Capability owners enter Capability Usage and Cost data
Includes current and future mapping to missions, and
Ready-to-produce costs among other factors
Defines the “demand” aspect of the assessment
• JFReD Platform has continued to integrate and
transform to meet Capabilities Information capture
needs
– JSC Capabilities Assessment Module (JCAM) developed
with similar architecture and logic as JFReD
– Reporting and other features are in requirements
building/testing phase
– If Capability data becomes the “currency” for managing
the Center products and services:
Possible integration of cost data, risk data, and
infrastructure (workforce/facilities) through a well-tested
JSC application platform
http://jfreddev.jsc.nasa.gov/jcam/default.aspx
February 9, 2011 22
25. JCAM – Capability Listing Page
List is displayed automatically when populated, provides navigation to capabilities
in the database
February 9, 2011 25 18
26. JCAM – Capability Page for Edit Capability
(Skill-Based)
February 9, 2011 26
27. JCAM – Usage Page for Edit Capability
(Skills-Based)
February 9, 2011 27
28. JCAM – Cost Page for Edit Capability
(Skills-Based)
February 9, 2011 28
29. JCAM – Capability Page for Edit Capability
(Facility-Based)
February 9, 2011 29
31. JCAM – Associated Facility Data Page
(for Facility-Based Capability)
February 9, 2011 31
32. JCAM – Associated Facility Usage Page
( for Facility-Based Capability)
February 9, 2011 32
33. JCAM – Associated Facility Cost Page
( for Facility-Based Capability)
February 9, 2011 33
34. Summary Best Practices
• Integrate Facility data capture tools at the Center level
to keep strategic planning and tactical implementation
goals aligned
• Maintain accurate and traceable facilities listing and
strict configuration control procedures
• Leverage PPBE yearly cost exercises in validating
and updating data content
• Collaborate closely with Agency Facilities Planning
entities and experts to standardize terminology,
requirements, and IT integration practices
• Center-wide Facilities Planning requires flexible
approach to facility usage and cost capture
– Changing Program requirements will drive usage levels and
institutional facilities decisions – keep it fluid
• Continue mapping facilities to Center-wide major
Strategic capabilities and associated funding profiles
February 9, 2011 34
35. Some Interesting Take-aways
• JSC Facilities Assessment and JFReD Best Practices tell us:
– Institute robust process and reliable sources/providers of data
– Tool serves to strengthen the process and should be focused
on user needs and convenience
–Focus on baselining the Listing and keeping information
accurate with strict configuration control – even in a changing
environment
–Schedule, performance metrics, and strategic planning
scenarios may be incorporated into a tried and tested platform
like JFReD
• Tools, Processes, and Assessments must be versatile to
assist with successful Change Management
Transition Management combined with
Capabilities and Assets Management is
needed to promote successful Center-wide
TRANSFORMATION MANAGEMENT
February 9, 2011 35