This document discusses challenges in managing NASA's Small Business Innovation Research (SBIR) program. It provides an overview of NASA's SBIR implementation including its focus areas of technology, innovation, and partnerships. It also outlines Congress' goals for the SBIR program to stimulate technological innovation, meet federal research needs through small businesses, and increase commercialization. The document summarizes the multi-phase SBIR process and challenges with technology infusion into NASA programs and commercial markets. It promotes engagement between NASA programs and small businesses to facilitate technology development and adoption.
This document summarizes a presentation about lessons learned from the Big Dig project in Boston. It provides background on the project, discusses existing literature on cost overruns in mega projects, and analyzes cost and schedule data over the life of the Big Dig. The presentation examines project structure, organization, and factors that contributed to cost increases from the initial $2.5 billion estimate to the final $14.8 billion. It aims to identify techniques for improving cost estimation and management of large infrastructure projects.
The document discusses the growth of project management as a field and the need to develop the international project management community. It notes that 20% of global GDP, or $12 trillion annually, is spent on capital projects worldwide. However, an increasing skills gap exists as the number of project-oriented jobs is expected to grow significantly in projectized industries by 2016. The document explores questions around where priority for developing project managers should lie, how industry and governments can address the supply-demand gap, and where project management organizations should focus resources to mitigate the gap.
This document discusses the challenges NASA faces in managing institutional risks to its space exploration missions. It outlines NASA's strategic goals and notes that the agency's missions present intense technical, financial, and management challenges within an extremely constrained operating environment. It emphasizes that increased performance from all systems, especially the institutional base of centers and support functions, is critical for mission success. The document identifies several categories of institutional risks to missions, such as environmental regulations and resource scarcity, and calls for risk mitigation strategies like investing in renewable energy and sustainability technologies.
The document discusses NASA's plans to replace aging facilities through its Renovation by Replacement (RbR) program. It analyzes two RbR projects: the NASA Ames Sustainability Base and the Langley New Town AOB1 facility. For the NASA Ames project, the key factors for project initiation success were establishing a compelling business case, incorporating NASA technologies, and meeting tight budget and schedule goals of $26 million by July 2009.
National Aeronautics and Space Administration (NASA) Goddard Space Flight Center's Innovative Partnerships Program (IPP) seeks to form partnerships to enhance future mission capabilities. The IPP acts as a facilitator and catalyst by bringing parties together, implementing new approaches, and identifying ways for partnerships to benefit NASA, partners, and taxpayers. The presentation provides an example partnership between NASA and Carnegie Mellon University's Robotics Institute to demonstrate how innovative partnerships can leverage resources and accelerate technology maturation.
This document outlines a presentation by NASA on adapting project management practices to research-based projects. It discusses the challenges of managing science research using traditional project management techniques due to differences in culture and goals between scientists and project managers. It provides perspectives from both scientists and project managers and examples of how NASA has worked to bridge this gap on human research projects through matrix organizational structures, collaboration between project managers and scientists, and involvement of scientists in requirements development.
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.
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 a presentation about lessons learned from the Big Dig project in Boston. It provides background on the project, discusses existing literature on cost overruns in mega projects, and analyzes cost and schedule data over the life of the Big Dig. The presentation examines project structure, organization, and factors that contributed to cost increases from the initial $2.5 billion estimate to the final $14.8 billion. It aims to identify techniques for improving cost estimation and management of large infrastructure projects.
The document discusses the growth of project management as a field and the need to develop the international project management community. It notes that 20% of global GDP, or $12 trillion annually, is spent on capital projects worldwide. However, an increasing skills gap exists as the number of project-oriented jobs is expected to grow significantly in projectized industries by 2016. The document explores questions around where priority for developing project managers should lie, how industry and governments can address the supply-demand gap, and where project management organizations should focus resources to mitigate the gap.
This document discusses the challenges NASA faces in managing institutional risks to its space exploration missions. It outlines NASA's strategic goals and notes that the agency's missions present intense technical, financial, and management challenges within an extremely constrained operating environment. It emphasizes that increased performance from all systems, especially the institutional base of centers and support functions, is critical for mission success. The document identifies several categories of institutional risks to missions, such as environmental regulations and resource scarcity, and calls for risk mitigation strategies like investing in renewable energy and sustainability technologies.
The document discusses NASA's plans to replace aging facilities through its Renovation by Replacement (RbR) program. It analyzes two RbR projects: the NASA Ames Sustainability Base and the Langley New Town AOB1 facility. For the NASA Ames project, the key factors for project initiation success were establishing a compelling business case, incorporating NASA technologies, and meeting tight budget and schedule goals of $26 million by July 2009.
National Aeronautics and Space Administration (NASA) Goddard Space Flight Center's Innovative Partnerships Program (IPP) seeks to form partnerships to enhance future mission capabilities. The IPP acts as a facilitator and catalyst by bringing parties together, implementing new approaches, and identifying ways for partnerships to benefit NASA, partners, and taxpayers. The presentation provides an example partnership between NASA and Carnegie Mellon University's Robotics Institute to demonstrate how innovative partnerships can leverage resources and accelerate technology maturation.
This document outlines a presentation by NASA on adapting project management practices to research-based projects. It discusses the challenges of managing science research using traditional project management techniques due to differences in culture and goals between scientists and project managers. It provides perspectives from both scientists and project managers and examples of how NASA has worked to bridge this gap on human research projects through matrix organizational structures, collaboration between project managers and scientists, and involvement of scientists in requirements development.
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.
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 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 provides an overview of NASA's policy for independent program reviews:
1. NASA policy mandates independent reviews at key decision points to validate programs' readiness and identify risks. This includes NPD 1000.0 requiring checks and balances like independent reviews.
2. The Standing Review Board process in NPR 7120.5 standardizes independent reviews across NASA. Reviews assess technical and programmatic status at life cycle milestones.
3. The SRB Handbook provides guidance for Standing Review Boards to apply review criteria consistently across programs in accordance with NASA's technical and program management requirements. It outlines the roles, processes, and expected work products for the reviews.
The document 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.
The document discusses challenges facing the Systems and Software Engineering Directorate within the Department of Defense. It outlines the Directorate's vision, mission, and responsibilities, which include providing technical advice on programs, establishing acquisition policies, and managing the systems engineering career field. The document also discusses key challenges programs face related to requirements, risk management, and reliability. It proposes ways the Directorate can better support programs early in the acquisition process through workshops, guidance updates, and collaboration tools.
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 analyses conducted by NASA's Strategic Investments Division to support agency management and decision making. It provides examples of performance analyses of projects, analyses for key decision points, budget decision analyses, and strategic investment analyses. The presentation emphasizes that objective, complete analyses from multiple sources and perspectives are critical to informing complex management decisions at NASA.
The document discusses how configuration management (CM) helps projects innovate and communicate. It compares project management and CM processes, and describes traditional CM versus CM II approaches. It also outlines two project management models - Kepner-Tregoe and Deming's Plan-Do-Check-Act cycle. CM expands on these models by managing both requirements definition and physical project tasks in synchronized cycles. The document argues that CM helps address common problems that cause project failures, such as poor communication, requirements, documentation, and change control. CM is positioned to support the entire project management process.
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 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.
The document outlines a proposed problem management process to help NASA program and project managers address risks that become problems. It describes a framework with two parts: technical data management procedures for identifying, investigating, resolving and preventing recurring problems; and support processes like data mining and trend analysis to inform decision making. The status provided is that NASA center comments on an initial draft guidebook are currently under review.
The document summarizes an NSC Audits and Assessments Workshop from September 2009-2010. It discusses the background and purpose of different types of NASA safety audits conducted by the NSC Audits and Assessments Office. The document analyzes audit findings from 2007-2010 and identifies potential systemic safety issues across multiple NASA centers, particularly in electrical safety, inspection records, and probabilistic risk assessment. Action plans were developed to address these issues and improve safety audit processes.
This document discusses increasing the robustness of flight project concepts. It proposes several improvements and innovations, including establishing new concept maturity levels (CML) to better communicate a concept's readiness. A new P4 document is suggested to provide requirements and guidelines for incorporating and evaluating a concept's robustness. Additional proposed enhancements involve new tools and templates, increased project team support, organizational changes, and training for the pre-phase A community. The overall goal is to address current challenges around assessing risks, communicating maturity, and guidelines for robustness evaluations in NASA's competitive funding environment.
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.
The document discusses the role of in-house consulting at NASA. It proposes that staff offices at NASA centers can take on the perspective of internal consultants by understanding project manager needs, interpreting policies, developing expertise, and providing ongoing support. This would help staff offices maintain relevance and justify their roles, rather than focusing only on processes. Examples are provided of how NASA Goddard's Policy and Standards Office takes a consulting approach to activities like Integrated Baseline Reviews. Potential benefits include improved consistency, training, and cultural alignment across NASA. Risks of undesirable roles like being an "enforcer" or "going native" are also discussed.
This document discusses the process for developing Joint Confidence Level (JCL) assessments of cost and schedule estimates for programs and projects. It outlines the roles of programs/projects and the independent review board (SRB) in developing probabilistic cost estimates, risk analyses, and JCL assessments to present at key decision points. Both the program/project and SRB will develop their own analyses, then reconcile differences through iterative reviews and updates until agreeing on a final JCL assessment to report out. The goal is for estimates to have a 70% confidence level that costs and schedules will be equal to or less than predicted.
The document summarizes changes made in the latest revisions of two NASA policy documents: NPR 7120.5 Rev E regarding space flight programs and projects, and NPR 7120.7 regarding IT and infrastructure. For NPR 7120.5 Rev E, key changes included streamlining requirements, establishing clear objectives for project reviews, and empowering project managers. Major topics of change in the latest revision included applicability, tailoring, compliance matrices, and project formulation agreements. The document provides an overview of the objectives and history of revisions to both policy documents.
The Composite Crew Module project brought together engineers from multiple NASA centers to design and build a composite crew capsule. A broad team was assembled with representation from various NASA centers and aerospace industry partners. They worked collaboratively over 18 months to design, build, and test a full-scale composite crew module, gaining hands-on experience. The goal was to advance composite materials technology in anticipation of future exploration systems utilizing composites.
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 an update to NASA's software engineering requirements in NPR 7150.2. It provides an overview of the topics to be covered, including the NPD/NPR architecture, lessons learned from the previous NPR, updates to NPR 7150.2, and future work. It then summarizes lessons learned from developing the original NPR 7150.2, such as forming a strong core team, selecting the target audience wisely, understanding where the NPR fits in directives, setting inclusion/exclusion criteria early, and getting professional help. The document outlines changes between the 2004 and 2009 versions, including some added and deleted requirements. It concludes by noting innovations incorporated in the updated NPR 7150.2
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 outlines the strategic initiatives process used by an organization. It involves four main stages: initiation, planning, execution, and exit. In the initiation stage, a business case is developed. In the planning stage, a project charter and plan are created defining objectives, resources, and milestones. Projects are then executed according to the plan, with regular status reports. Finally, upon completion, a financial audit is performed and lessons learned are documented.
Stanford 2012: Building the Entrepreneurial UniversityJack Brittain
Stanford panel focused on how universities are leveraging scholarship to make a difference in the world and the communities in which they are located. This presentation describes the "Utah model" and the changes the University of Utah made to become one of the top public university commercialization programs in the nation.
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 provides an overview of NASA's policy for independent program reviews:
1. NASA policy mandates independent reviews at key decision points to validate programs' readiness and identify risks. This includes NPD 1000.0 requiring checks and balances like independent reviews.
2. The Standing Review Board process in NPR 7120.5 standardizes independent reviews across NASA. Reviews assess technical and programmatic status at life cycle milestones.
3. The SRB Handbook provides guidance for Standing Review Boards to apply review criteria consistently across programs in accordance with NASA's technical and program management requirements. It outlines the roles, processes, and expected work products for the reviews.
The document 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.
The document discusses challenges facing the Systems and Software Engineering Directorate within the Department of Defense. It outlines the Directorate's vision, mission, and responsibilities, which include providing technical advice on programs, establishing acquisition policies, and managing the systems engineering career field. The document also discusses key challenges programs face related to requirements, risk management, and reliability. It proposes ways the Directorate can better support programs early in the acquisition process through workshops, guidance updates, and collaboration tools.
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 analyses conducted by NASA's Strategic Investments Division to support agency management and decision making. It provides examples of performance analyses of projects, analyses for key decision points, budget decision analyses, and strategic investment analyses. The presentation emphasizes that objective, complete analyses from multiple sources and perspectives are critical to informing complex management decisions at NASA.
The document discusses how configuration management (CM) helps projects innovate and communicate. It compares project management and CM processes, and describes traditional CM versus CM II approaches. It also outlines two project management models - Kepner-Tregoe and Deming's Plan-Do-Check-Act cycle. CM expands on these models by managing both requirements definition and physical project tasks in synchronized cycles. The document argues that CM helps address common problems that cause project failures, such as poor communication, requirements, documentation, and change control. CM is positioned to support the entire project management process.
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 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.
The document outlines a proposed problem management process to help NASA program and project managers address risks that become problems. It describes a framework with two parts: technical data management procedures for identifying, investigating, resolving and preventing recurring problems; and support processes like data mining and trend analysis to inform decision making. The status provided is that NASA center comments on an initial draft guidebook are currently under review.
The document summarizes an NSC Audits and Assessments Workshop from September 2009-2010. It discusses the background and purpose of different types of NASA safety audits conducted by the NSC Audits and Assessments Office. The document analyzes audit findings from 2007-2010 and identifies potential systemic safety issues across multiple NASA centers, particularly in electrical safety, inspection records, and probabilistic risk assessment. Action plans were developed to address these issues and improve safety audit processes.
This document discusses increasing the robustness of flight project concepts. It proposes several improvements and innovations, including establishing new concept maturity levels (CML) to better communicate a concept's readiness. A new P4 document is suggested to provide requirements and guidelines for incorporating and evaluating a concept's robustness. Additional proposed enhancements involve new tools and templates, increased project team support, organizational changes, and training for the pre-phase A community. The overall goal is to address current challenges around assessing risks, communicating maturity, and guidelines for robustness evaluations in NASA's competitive funding environment.
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.
The document discusses the role of in-house consulting at NASA. It proposes that staff offices at NASA centers can take on the perspective of internal consultants by understanding project manager needs, interpreting policies, developing expertise, and providing ongoing support. This would help staff offices maintain relevance and justify their roles, rather than focusing only on processes. Examples are provided of how NASA Goddard's Policy and Standards Office takes a consulting approach to activities like Integrated Baseline Reviews. Potential benefits include improved consistency, training, and cultural alignment across NASA. Risks of undesirable roles like being an "enforcer" or "going native" are also discussed.
This document discusses the process for developing Joint Confidence Level (JCL) assessments of cost and schedule estimates for programs and projects. It outlines the roles of programs/projects and the independent review board (SRB) in developing probabilistic cost estimates, risk analyses, and JCL assessments to present at key decision points. Both the program/project and SRB will develop their own analyses, then reconcile differences through iterative reviews and updates until agreeing on a final JCL assessment to report out. The goal is for estimates to have a 70% confidence level that costs and schedules will be equal to or less than predicted.
The document summarizes changes made in the latest revisions of two NASA policy documents: NPR 7120.5 Rev E regarding space flight programs and projects, and NPR 7120.7 regarding IT and infrastructure. For NPR 7120.5 Rev E, key changes included streamlining requirements, establishing clear objectives for project reviews, and empowering project managers. Major topics of change in the latest revision included applicability, tailoring, compliance matrices, and project formulation agreements. The document provides an overview of the objectives and history of revisions to both policy documents.
The Composite Crew Module project brought together engineers from multiple NASA centers to design and build a composite crew capsule. A broad team was assembled with representation from various NASA centers and aerospace industry partners. They worked collaboratively over 18 months to design, build, and test a full-scale composite crew module, gaining hands-on experience. The goal was to advance composite materials technology in anticipation of future exploration systems utilizing composites.
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 an update to NASA's software engineering requirements in NPR 7150.2. It provides an overview of the topics to be covered, including the NPD/NPR architecture, lessons learned from the previous NPR, updates to NPR 7150.2, and future work. It then summarizes lessons learned from developing the original NPR 7150.2, such as forming a strong core team, selecting the target audience wisely, understanding where the NPR fits in directives, setting inclusion/exclusion criteria early, and getting professional help. The document outlines changes between the 2004 and 2009 versions, including some added and deleted requirements. It concludes by noting innovations incorporated in the updated NPR 7150.2
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 outlines the strategic initiatives process used by an organization. It involves four main stages: initiation, planning, execution, and exit. In the initiation stage, a business case is developed. In the planning stage, a project charter and plan are created defining objectives, resources, and milestones. Projects are then executed according to the plan, with regular status reports. Finally, upon completion, a financial audit is performed and lessons learned are documented.
Stanford 2012: Building the Entrepreneurial UniversityJack Brittain
Stanford panel focused on how universities are leveraging scholarship to make a difference in the world and the communities in which they are located. This presentation describes the "Utah model" and the changes the University of Utah made to become one of the top public university commercialization programs in the nation.
The document summarizes the economic significance of university research and commercialization efforts. It discusses how university research leads to technological advancements that enter the marketplace through startups, licenses, and collaborations. It then provides details on the University of Utah's commercialization programs and outcomes, including generating over 150 startup companies, $1.3 billion in total annual payroll, and $129.6 million in total annual tax contributions. It argues the university's model of leveraging grants and donors, funding critical development paths, and focusing on outcomes has led to reinvented and successful university commercialization.
Portal GSTI
-----------------------------------------------------
Participe dos treinamentos de preparação para a certificação ITIL e COBIT via EAD. Solicite agora mesmo o material gratuito de amostra dos cursos e inicie seus estudos. fernando.palma@gmail.com
-----------------------------------------------------
http://www.portalgsti.com.br/Publicidade Portal GSTI
-----------------------------------------------------
Participe dos treinamentos de preparação para a certificação ITIL e COBIT via EAD. Solicite agora mesmo o material gratuito de amostra dos cursos e inicie seus estudos. fernando.palma@gmail.com
-----------------------------------------------------
http://www.portalgsti.com.br/Publicidade Portal GSTI
-----------------------------------------------------
Participe dos treinamentos de preparação para a certificação ITIL e COBIT via EAD. Solicite agora mesmo o material gratuito de amostra dos cursos e inicie seus estudos. fernando.palma@gmail.com
-----------------------------------------------------
http://www.portalgsti.com.br/
This document discusses Cablevision's investigation into using offshore outsourcing for IT projects. It outlines the roadmap Cablevision followed, which included fact finding, socializing the idea internally, developing a strategy, preparing staff, and engaging a vendor. It notes challenges like cultural differences but also potential benefits like cost savings. The key is finding the right projects, doing thorough due diligence on vendors, and managing the relationship actively long-term.
DQO is an initiative that provides guidance for organizations to develop digital strategies. It involves four phases: Discover, Define, Develop, and Deploy. The Discover phase involves assessing an organization's readiness for social media use and determining desired outcomes. The Define phase defines goals and key performance indicators. The Develop phase establishes policies, processes, and appropriate platforms. Finally, the Deploy phase involves piloting social media strategies before full implementation. DQO provides tools and best practices to help organizations strategically develop and deploy social media initiatives.
Hardik Doshi has over 10 years of experience in finance and research. He holds an MBA in finance and investment banking and is a CFA Level 3 candidate. Currently he works as an equity research analyst covering the banking sector in India and Eastern Europe. Previously he has interned at financial firms in Dubai and worked as a systems executive, project engineer, and PeopleSoft consultant.
The document provides an overview of the Alberta Natural Gas and Conventional Oil Investment Competitiveness Study 2009. The study aims to determine if Alberta is competitive for investment in the natural gas and conventional oil sectors. Key steps in the study include collecting data from industry, analyzing factors of competitiveness, engaging stakeholders, and developing conclusions and recommendations. The project will analyze economic and financial aspects of investment competitiveness through interviews, workshops, and focus groups with government, industry, and financial sectors.
This document provides an overview of project chartering for continuous process improvement (CPI) projects. It discusses selecting CPI projects, developing a project charter, and who is responsible for chartering a project. The project charter defines the team's mission and includes the opportunity/problem statement, business case, goal statement, project scope, timeline, and team selection. It is a living document that may change over time. Developing an effective charter involves scoping the project based on the identified problem and determining proportional benefits, measurements, and boundaries.
This document outlines the define phase of an 8-step continuous process improvement (CPI) roadmap. The define phase includes activities like identifying problems, validating the problem statement, establishing strategic alignment, gathering customer input, and creating a goal statement. It also lists required deliverables for the define tollgate, such as a problem statement, goal statement, project scope, timeline, and high-level process map. The document provides an overview of the key elements and documentation needed to properly define a CPI project.
The document outlines the SIPs (Strategic Innovation Processes) process which includes four main phases: 1) Define & Discovery, 2) Design & Architecture, 3) Development & Execution, and 4) Roll Out. It also lists the roles involved in a project including founders, partners, team members, and users/stakeholders.
This document discusses IT strategy and transformation. It outlines benefits such as better governance, aligning business and IT strategies, cost management, and unleashing value from technology investments. The approach involves 10 steps to develop a multi-stage transformation roadmap. These steps include understanding the strategic context, building constituent maps, assessing capabilities, and defining a portfolio of prioritized opportunities. The methodology is based on constituent business modeling to support strategic decision making independently of processes or organizational boundaries.
Joint UNDP-UNESCAP Initiative: CapacityDevelopment of Local Governments in ...Oswar Mungkasa
Public-Private Partnerships for Service Delivery (PPPSD) Facility of the UNDP
UNESCAP Workshop on Knowledge Transfer & Capacity
Building for Water & Sanitation Services in Asia & the Pacific
17 – 19 February 2009, Bangkok, Thailand
The document discusses process improvement metrics and methods at the Jet Propulsion Laboratory (JPL). It notes that while JPL aims to perform like a CMMI Level 4 organization, it is actually assessed at CMMI Level 3. It outlines some of JPL's data collection methods and key questions around understanding their software environment. Some of the processes in place include tailoring software development processes and measuring performance against processes. Risks, strengths and recommendations are identified from process reviews.
Project management in pharmaceutical generic industry basics and standardsJayesh Khatri
Project management involves coordinating activities to meet objectives within constraints like time, cost and quality. It involves planning, tracking progress, and controlling a project. Key aspects include defining requirements, creating a schedule and assigning resources. Tools like Gantt charts help plan and monitor the project. Benefits-centered project management focuses on achieving business benefits in addition to project execution. Prioritization techniques like MoSCoW help determine requirement importance. Effective strategies include empowered decision making, clear roles, and collaboration across functions.
1. The document outlines a 5-step process for change management and sustainability consulting projects that includes defining the scope, collecting and assessing data, setting strategy and plans, implementing and adjusting initiatives, and monitoring and reporting on progress.
2. A wide range of tools are presented for each project phase, including sustainability tools like life-cycle analysis and energy analysis, as well as change management tools like communications planning, open space technology, and lean six sigma.
3. Employees are identified as a major leverage point for driving organizational changes related to sustainability through their ability to reduce impacts, alter production, and increase efficiency.
The document summarizes the goals and focus areas of AIESEC Kolkata for 2013. It discusses growing programs like the temporary internship program and developing integrated experiences. Key goals are outlined for different programs along with a focus on financial sustainability, national alignment, brand and IM implementation. Growth drivers identified include showcasing impact, financial sustainability and national/regional projects. The agenda proposes a critical SWOT analysis and innovative strategies. Plans for Q2 include showcasing trainee impact through feedback, evolved projects, and processed matching through skype interviews. Synergy outputs across different departments are also mapped out.
ECATA - Sourcing Strategies of IT ServicesPatrick Nolot
The 11th International Aerospace Seminar organized by the ECATA Alumni (European Consortium for Advanced Training in Aerospace, www.ecata.org) took place in Munich, Germany, and hosted industry leaders who made presentations on the conference's theme "Balancing Core Competences and Out-Sourcing".
Patrick Nolot, VP Technology Strategy & Architecture, BNP Paribas Personal Finance, together with Björn Schichler, Senior Manager, LogicaCMG Management Consulting and Michel Cadars, LogicaCMG Global Account Director EADS, made a presentation on "Sourcing Strategies of IT Services".
Presentation abstract:
• Main evolutions of the IT sourcing services market, from off shoring of IT programming skills to Business Process Outsourcing (BPO)
• What IT outsourcing (ITO) is and is not? (scope)
• Why deciding for “optimal IT sourcing” initiatives? (business objectives)
• Where to source IT services? (location analysis)
• How to source IT services? (sourcing models)
• Best practices and return on experience from LogicaCMG, one of the leading 10 players in the Western European IT and BPO services market
• Emerging trends in the IT sourcing services market
In this presentation, we provide the details of an ecosystem to foster scholarly work at an educational institution. Various research and funding processes are outlined to set up and execute a successful operational model.
The document compares the operational complexity and costs of the Space Shuttle versus the Sea Launch Zenit rocket. [1] The Space Shuttle was designed for performance but not operational efficiency, resulting in costly ground, mission planning, and flight operations. [2] In contrast, the Zenit rocket was designed from the start to have automated and robust processes to keep operations simple and costs low. [3] The key lesson is that designing a launch system with operational requirements in mind from the beginning leads to much more efficient operations long-term.
The document provides an overview of project management and procurement at NASA. It discusses the key skills required for project managers, including acquisition management. It notes that 80-85% of NASA's budget is spent on contracts, and procurement processes are complex and constantly changing. The document outlines some common contract types and how they allocate risk between the government and contractor. It also discusses the relationship between contracting officers and project managers, and how successful procurement requires effective communication rather than direct control or authority.
The document introduces the NASA Engineering Network (NEN), which was created by the Office of the Chief Engineer to be a knowledge management system connecting NASA's engineering community. The NEN integrates various tools like a content management system, search engine, and collaboration tools. It provides access to key knowledge resources like NASA's Lessons Learned database and engineering databases. The NEN is working to expand by adding more communities, engineering disciplines, and knowledge repositories.
Laptops were first used in space in 1983 on the Space Shuttle, when Commander John Young brought the GRiD Compass portable computer on STS-9. Laptops are now widely used on the Space Shuttle and International Space Station for tasks like monitoring spacecraft systems, tracking satellites, inventory management, procedures viewing, and videoconferencing. Managing laptops in space presents challenges around cooling, power, and software/hardware compatibility in the harsh space environment.
Laptops were first used in space in 1983 on the Space Shuttle, when Commander John Young brought the GRiD Compass portable computer on STS-9. Laptops are now widely used on the Space Shuttle and International Space Station for tasks like monitoring spacecraft systems, planning rendezvous and proximity operations, inventory management, procedure reviews, and communication between space and ground via software like WorldMap and DOUG. Managing laptops in space presents challenges around hardware durability, cooling, and software/data management in the space environment.
This document discusses the use of market-based systems to allocate scarce resources for NASA missions and projects. It provides examples of how market-based approaches were used for instrument development for the Cassini mission, manifesting secondary payloads on the space shuttle, and mission planning for the LightSAR Earth imaging satellite project. The document finds that these applications of market-based allocation benefited or could have benefited from a decentralized, incentive-based approach compared to traditional centralized planning methods. However, it notes that resistance to new approaches and loss of managerial control are barriers to adoption of market-based systems.
The Stardust mission collected samples from comet Wild 2 and interstellar dust particles. It launched in February 1999 and encountered Wild 2 in January 2004, collecting dust samples in aerogel. It returned the samples to Earth safely in January 2006. The spacecraft used an innovative Whipple shield to protect itself from comet dust impacts during the encounter. Analysis of the Stardust samples has provided insights about comet composition and the early solar system.
This document discusses solutions for integrating schedules on NASA programs. It introduces Stuart Trahan's company, which provides Earned Value Management (EVM) solutions using Microsoft Office Project that comply with OMB and ANSI requirements. It also introduces a partner company, Pinnacle Management Systems, that specializes in enterprise project management solutions including EVM, project portfolio management, and enterprise project resource management, with experience in the aerospace, defense, and other industries. The document defines schedule integration and describes some methods including importing to a centralized Primavera database for review or using Primavera ProjectLink for updates, and challenges including inconsistent data formats and levels of detail across sub-schedules.
The document discusses NASA's implementation of earned value management (EVM) across its Constellation Program to coordinate work across multiple teams. It outlines the organizational structure, current target groups, and an EVM training suite. It also summarizes lessons learned and the need for project/center collaboration to integrate schedules horizontally and vertically.
This document summarizes a presentation about systems engineering processes for principle investigator (PI) mode missions. It discusses how PI missions face special challenges due to cost caps and lower technology readiness levels. It then outlines various systems engineering techniques used for PI missions, including safety compliance, organizational communication, design tools, requirements management, and lessons learned from past missions. Specific case studies from NASA's Explorers Program Office are provided as examples.
This document discusses changes to NASA's business practices for managing projects, including adopting a new acquisition strategy approach and implementing planning, programming, and budget execution (PPBE). The new acquisition strategy involves additional approval meetings at the strategic planning and project levels to better integrate acquisition with strategic and budgetary planning. PPBE focuses on analyzing programs and infrastructure to align with strategic goals and answer whether proposed programs will help achieve NASA's mission. The document also notes improvements in funds distribution and inter-center transfers, reducing the time for these processes from several weeks to only a few days.
Spaceflight Project Security: Terrestrial and On-Orbit/Mission
The document discusses security challenges for spaceflight projects, including protecting space assets from disruption, exploitation, or attack. It highlights national space policy principles of protecting space capabilities. It also discusses trends in cyber threats, including the increasing capabilities of adversaries and how even unskilled attackers can compromise terrestrial support systems linked to space assets if defenses are not strong. Protecting space projects requires awareness of threats, vulnerabilities, and strategies to defend, restore, and increase situational awareness of space assets and supporting systems.
Humor can positively impact many aspects of project management. It can improve communication, aid in team building, help detect team morale issues, and influence leadership, conflict management, negotiation, motivation, and problem solving. While humor has benefits, it also has risks and not all uses of humor are positive. Future research is needed on humor in multicultural teams, its relationship to team performance, how humor is learned, and determining optimal "doses" of humor. In conclusion, humor is a tool that can influence people and projects, but must be used carefully and spontaneously for best effect.
The recovery of Space Shuttle Columbia after its loss in 2003 involved a massive multi-agency effort to search a wide debris field, recover crew remains and evidence, and compensate local communities. Over 25,000 people searched over 680,000 acres, recovering 38% of Columbia's weight. Extensive engineering investigations were conducted to identify the causes of failure and implement changes to allow the safe return to flight of Discovery in 2005.
This document summarizes research on enhancing safety culture at NASA. It describes a survey developed to assess NASA's safety culture based on principles of high reliability organizations. The survey was tailored specifically for NASA and has been implemented to provide feedback and identify areas for improvement. It allows NASA to benchmark its safety culture within and across other industries pursuing high reliability.
This document summarizes a presentation about project management challenges at NASA Goddard Space Flight Center. The presentation outlines a vision for anomaly management, including establishing consistent problem reporting and analysis processes across all missions. It describes the current problem management approach, which lacks centralized information sharing. The presentation aims to close this gap by implementing online problem reporting and trend analysis tools to extract lessons learned across missions over time. This will help improve spacecraft design and operations based on ongoing anomaly experiences.
This document discusses leveraging scheduling productivity with practical scheduling techniques. It addresses scheduling issues such as unwieldy schedule databases and faulty logic. It then discusses taming the schedule beast through using a scheduler's toolkit, schedule templates, codes to manipulate MS Project data, common views/filters/tables, limiting constraints, and other best practices. The document provides examples of using codes and custom views/filters to effectively organize and display schedule information.
This document describes Ball Aerospace's implementation of a Life Cycle and Gated Milestone (LCGM) process to improve program planning, execution, and control across its diverse portfolio. The LCGM provides a standardized yet flexible framework that maps out program activities and products across phases. It was developed through cross-functional collaboration and introduced gradually across programs while allowing flexibility. Initial results showed the LCGM supported improved planning and management while aligning with Ball Aerospace's entrepreneurial culture.
This document discusses the importance of situation awareness (SA) for project team members. It defines SA as having three levels: perception of elements in the current situation, comprehension of the current situation, and projection of the future status. Good team SA is achieved by turning individual SAs into shared SA through communication. Teams with strong SA prepare more, focus on comprehending and projecting, and maintain awareness through techniques like questioning assumptions and seeking additional information.
This document discusses theories of leadership and how a project manager's leadership style may impact project success depending on the type of project. It outlines early hypotheses that a PM's competence, including leadership style, is a success factor on projects. It presents a research model linking PM leadership competencies to project success, moderated by factors like project type. Initial interviews found that leadership style is more important on complex projects, and different competencies are needed depending on if a project is technical or involves change. Certain competencies like communication skills and cultural sensitivity were seen as important for different project types and contexts.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
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.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
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.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
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.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Ray hines stegeman
1. Challenges in Managing the
SBIR Program
Strategic View
Mission Directorate Perspective
Infusion Challenge
Carl G. Ray,
Jim Stegeman,
Kimberly Hines
Used with permission
2. Implementation of SBIR/STTR at NASA
Innovative Partnerships Program (IPP)
Technology Innovation Partnership
Infusion Incubator Development
– SBIR – Centennial – Intellectual
Challenges Property
– STTR
– New Business management
– IPP Seed Fund
Models – Technology
– Innovation Transfer
Transfusion – New Innovative
Partnerships
3. WHY SBIR????
Congress designated 4 major goals
• Stimulate technological innovation
• Use small business to meet federal R&D needs
• Foster and encourage participation by
minorities and disadvantaged persons in
technological innovation
• Increase private-sector commercialization
innovations derived from federal R&D
4. SBIR/STTR Participating Agencies
• DOD SBIR/STTR
• HHS SBIR/STTR
• NASA SBIR/STTR
• DOE SBIR/STTR
• NSF SBIR/STTR
• HLS SBIR
• USDA SBIR
• DOC SBIR
• EPA SBIR
TOTAL ~ $2.3 B FY 2009
• DOT SBIR
• ED SBIR
6. IPP Technology for Mission Directorates
MD Technology Needs Communication
IPP “Landscape” Development
Innovative Mission Directorates
Partnerships Program • Programs
• SBIR/STTR • Projects
• Centennial Challenges Technology Infusion
• Seed Fund • Bridging the “Valley
• Partnerships of Death”
• Narrow the gap and
reduce risk
Executed at the Field Executed at the Field
• Begin building
Centers Centers
bridges early
7. SBIR/STTR: 3-Phase Program
• PHASE I
• Feasibility study
• $100K award
• 6 months duration (SBIR)
• 12 months duration (STTR)
• PHASE II
• Technology Development
• 2-Year Award
• Up to $750K (SBIR/STTR)
SBIR is 2.5% of extramural R&D, STTR is 0.3% of extramural R&D.
• PHASE III
• Technology Infusion/Commercialization Stage.
• Use of non-SBIR Funds.
• Ability to award sole-source contracts without JOFOC based on specific
SBIR authority – NASA and NASA primes.
8. SBIR/STTR Pre-Solicitation Development & Solicitation
Release Process Management 2009/2010 Milestones
* Starts with strategic assessment of 2009/10
SBIR/STTR Budget estimate, IPP Landscape
Development and Topic/Subtopic portfolio
Subtopics Development (Support sub-process)
Subtopic Write-ups from Centers
Solicitations Development Workshop
Revise Topics and Subtopics
Preliminary release for comment
Centers’ Coordination
Mission Directorates’ Approvals
Solicitation Preparation
PMO Review and HQ Concurrence
Preparation of Website
Final Publication Solicitation Review
Official Solicitation Released
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep
9. Mission Driven
SBIR/STTR = Small Business Innovation for NASA and the Nation
Partnership with Mission Directorates Drives SBIR/STTR Investment
Exploration Systems Aeronautics Research
Science Space Operations
10. SBIR/STTR Program Annual
TECHNOLOGY DEVELOPMENT
& INFUSION PROCESS FLOW
Awardees
SBIR/STTR Program
MD Technology Needs AGENCY MISSIONS
& Strategic Planning IPP “LANDSCAPE” Mission Directorates
Development Independent Survey
& Internal Assessment
SBIR/STTR
TOPICS /SUBTOPICS
Independent
Development
Survey
& SOLICITATION
Internal Assessment
PHASE I
EVALUATIONS AND SELECTIONS
Program Small Business FEASABILITY CONTRACTS
Performance & Research Institutions PHASE II
Coordination EVALUATIONS AND SELECTIONS
CONTRACT AWARD
TECHNOLOGY
Infusion DEVELOPMENT &
Mission Maturation & Integration Contract Performance COMMERCIAL
Programs SBC Execution APPROACH
COTR Oversight
Commercial
Phase III
COMMERCIALIZATION
Industry
OVERSIGHT ACTIVITIES
Interfaces
Process Path
12. Phase 3: Follow-on development, investment and use
Commercial Products, Services, Systems
System Test,
Launch & Mission TRL 9
Operations Mission
Operations
System/ TRL 8
Subsystem
Development
Technology
TRL 7 System
Transition
Technology
Development
Demonstration
TRL 6
Technology
Technology
TRL 5 Development Requirements / GFE
Development &
Demonstration
TRL 4
Technology
Research to
Research
Prove &
Feasibility
TRL 3 Developmen
t
Basic/Applied
TRL 2
Basic
Research Research
TRL 1
Federal, SBIR/STTR, Mission Programs, Mission Programs, Mission Programs,
Funding Sources: Industry, Federal Industry Industry Industry,VCs,
Industry
13. Phase III CHALLENGE
►Phase II results infused into NASA programs or
commercial market
►Phase III work may be for products, production,
services, or additional R&D
►Funded from a source other than the SBIR
Program Office
►Private-sector investment, in various forms, is also
a vehicle for the Phase III process.
►Granted based on the merits of the Phase I or II
results without further need for competition
►Viewed as “success stories”
►Contract can be Fixed Price or Cost-Type
13
14. SBIR/STTR Taxonomy
• Avionics and Astrionics
• Biotechnology
• Communications
• Cryogenics
• Education
• Electronics
• Extravehicular Activity
• Information
• Manufacturing
• Materials
• Microgravity
• Power and Energy
• Propulsion
• Robotics
• Sensors and Sources
• Structures
• Thermal
• Verification and Validation
18. SOMD Technology Areas
2009 Phase I
Topic O1 – Space Communications Topic O2 – Space Transportation Topic O4 – Navigation
O2.01 Automated Collection and Transfer of
O1.01 Coding, Modulation, and Compression Launch Range Data (Surveillance, Intrusion, O4.01 Metric Tracking of Launch Vehicles
Weather)
O1.02 Antenna Technology O4.02 On-orbit PNT (Positioning,
O2.02 Ground Test Facility Technologies Navigation, and Timing) Sensors and
Components
O1.03 Reconfigurable/Reprogrammable
Communications Systems O4.03 Lunar Surface Navigation
O1.04 Miniaturized Digital EVA Radio O4.04 Flight Dynamics Technologies and
Software
O1.05 Transformational Communications O4.05 Space Based Range Technologies
Technology Topic O3 – Processing &
Operations
O1.06 Long Range Optical
Telecommunications O3.01 Human Interface Systems and
Technologies Topic O5 – Low-Cost and
O1.07 Long Range Space RF Reliable Access to Space
Telecommunications (LCRATS)
O3.02 Vehicle Integration and Ground
Processing
O1.08 Lunar Surface Communication
Networks and Orbit Access Links
O3.03 Enabling Research for ISS
O1.9 Software for Space Communications
Infrastructure Operations
18
19. SOMD Solicitation
Development Approach
Responsibilities
• Topic / subtopic managers develop technology area descriptions based
on MD, program, and center needs
• TIMs engage center programs, line organizations, and topic / subtopic
managers
• Centers establish commitment to these technology areas (e.g., ensure
appropriate subtopic manager(s), reviewers, and COTRs are available)
SOMD MD
Offices
Center Chief SOMD Program
Technologist Offices
SOMD MDR
SOMD Topic & Internal (Center) Gap Analysis
SBIR TIMs Center-Level Prioritization of
Subtopic Managers
Technology Areas
Draft Technology Center Management SOMD MDR
Areas Concurrence Concurrence
19
20. Solicitation Strategy
Analysis of Topic contents
Review technology portfolio, which provides a snapshot of the products
being developed or that have been developed.
Ask and answer the following questions:
• Is the topic generating the interest we envision?
• Is the topic generating products we can use?
• How do these products fit into Agency plans? What is the pull? Or
are we pushing technology?
• Are more products needed to provide trade space input?
• Yes - Keep the same product call? (i.e., keep the same content)
• No - why? Satisfied with current products? Industry has
something we can buy?
20
23. SBIR – TMP Technology Integration
• Objective
• Leverage SBIR awards and process as much as
possible within the SCaN Technology Development
Program (TDP)
• Approach
• Merge the SBIR process with the SCaN TDP
process
• Recommend 2 full SBIR cycles for trial period (~4
yrs)
24. SOMD/SCaN Technology Development Process
ADD ADD ADD
SBIR SBIR SCaN Technology
Phase I Phase II
Process Process Development
Process
• Selection
• Development
Technology Technology
Management Management
Team (TMT) Team (TMT)
Existing SCaN Existing SCaN
Technology Technology
Developments Developments
1 2- 3 3-4 Year
28. Lessons Learned, Issues, or
Comments
• Collaboration opportunities are plentiful
• Coordination with AFRL, Missile Defense Agency, Navy SPAWAR reported earlier
• SPAWAR invited NASA input towards their new SBIR solicitation
• US Army now included in SOMD SBIR content alignment discussions
• Content alignment collaboration with DoD underway
• Reformulation of SOMD SBIR content underway for 2010:
• All SOMD areas: Space Communications, Space Transportation, Processing and Operations,
and Navigation
• Significant effort planned with a systems engineering approach towards technology needs;
current recommendations included extensive discussions during topic reviews
• Working with SCaN and other SOMD areas
• Clustering of awards around central technology theme being evaluated
• Expect to “jumpstart” capability in an area
• Building upon previous NASA and DARPA investments in XNAV technologies
29. Infusion Challenge
• What technology “infusion” is…
• Used in a trade space
• Phase III contracts
• Used in NASA projects or missions
• What is in it for you, a program or project
manager!
• Access to current technology developments
• Streamlined procurement process
30. Technology Infusion Managers’
Infusion Approach
• Collaborate with COTR’s to maintain
technology awareness
• Facilitate the Phase I-II process without losing
sight of the end goal
• Communicate with Programs and Projects to
status technology capabilities and maturity
30
31. Infusion Cycle
• Solicitation Development
• Engage Mission Directorates on behalf of
researchers enabling subtopic formulation
and participation
• Facilitate review and ranking process at
centers
• Advise Mission Directorate concerning highly
regarded proposals
• Maintain local technology portfolio
31
32. SBIR Technology Infusion Examples
Icy Soil
Acquisition
Device
supplied by
Honeybee
Robotics,
Mars Phoenix Lander
Inc.
Lithium ion SpaceDev (formerly
batteries Starsys) contributed to the
supplied by design of the Microscopy
Yardney Electrochemistry and
Technical Conductivity Analyzer
Products, Inc. (MECA)
34. Sources for Phase III Contracts
• Technologies developed under a Phase I or
Phase II SBIR or STTR contract from NASA
• Technologies developed under a Phase I or
Phase II SBIR or STTR contract from another
government agency
34
35. Resources for Programs and Projects
• Technology Infusion Managers
• Advocacy and assist with Phase III contracts
• Contract kick-off, midterm and final technical
reviews
• SBIR Technology Search
• NASA’s SBIR Electronic Handbook
• SBA Tech-Net
• NTTC
• http://www.sbipp.com/technologyportfolios/
36. What Program and
Project Managers Can Do
• Provide subject matter experts for SBIR
proposal reviews.
• Provide subject matter experts for technical
reviews throughout technology development.
• Consider SBIR Technologies in:
• Project formulation
• Trade spaces (i.e. key decision points)
• Acquisition planning