Engineering topics
Taylor, Randall L.
Publications and source records attributed to Taylor, Randall L..
Managing GRAIL: Launching on Cost, on Schedule, and on Spec
No abstract available
Reengineering the Acquisition/Procurement Process: Requirements Collection Methodology
No abstract available
Reducing NPR 7120.5D to Practice: Preparing for a Life-Cycle Review
In March 2007, NASA issued revised rules for space flight project management, NPR 7120.5D, 'NASA Space Flight Program and Project Management Requirements.' Central to the new rules was the construct of Key Decision Points, maturity gates that the project team must pass in order to continue development. In order that the KDP decision be fully informed, the NPR required, as entrance criteria for the gate, the generation and delivery of specified planning, technical, and cost/schedule documents (gate products) and a life-cycle review, the Preliminary Design Review. Building on JPL experience on the Prometheus and Juno projects, the team successfully organized for and conducted these reviews on an aggressive schedule. Key actions were taken to proactively interact with the SRB, produce high-quality gate products with stakeholder review, generate review presentation materials, and handle a myriad of supporting logistical functions. A review preparation team was established, including a Review Captain and leads for documentation, information systems, and logistics, and their roles, responsibilities and task assignments were identified. Aids were produced, including a detailed review preparation schedule and a comprehensive gate products production table. Institutional support was leveraged early and often. Implementation strategy reflected the needs of a nationally-distributed team, as well as applicable export control and IT security requirements. This paper gives a brief overview of the GRAIL mission and its project management challenges, provides a detailed description of project PMSR and PDR preparation and execution activities, including positive and negative lessons learned, and identifies recommendations for future NASA (and non-NASA) project teams.
Acquisition strategy and source selection for co-designing a new-development spacecraft
Explore the source record for details and available documents.
Experiences in managing the Prometheus Project
Congress authorized NASA?s Prometheus Project in February 2003, with the first Prometheus mission slated to explore the icy moons of Jupiter. The Project had two major objectives: (1) to develop a nuclear reactor that would provide unprecedented levels of power and show that it could be processed safely and operated reliably in space for long-duration, deep-space exploration and (2) to explore the three icy moons of Jupiter - Callisto, Ganymede, and Europa - and return science data that would meet the scientific goals as set forth in the Decadal Survey Report of the National Academy of Sciences. Early in Project planning, it was determined that the development of the Prometheus nuclear powered Spaceship would be complex and require the intellectual knowledge residing at numerous organizations across the country. In addition, because of the complex nature of the Project and the multiple partners, approaches beyond those successfully used to manage a typical JPL project would be needed. This paper1 will describe the key experiences in managing Prometheus that should prove useful for future projects of similar scope and magnitude
Source selection for a co-designed spacecraft
Explore the source record for details and available documents.