Swift Mission Project Management (Joe Dezio)
The primary responsibility of the Explorer Program Office is to ensure Explorer missions are successful in achieving their science
objectives. We do this by working with the PI and the project team to manage the cost, schedule, and technical elements of the project and by guiding them through the various processes that make up the life cycle of these missions. This presentation will provide an overview of the Explorer Program Office organization, functions, and approach to working with the PI, the project team, and SMD to ensure the success of Explorer missions. The intent is to provide guidance on working relationships and processes as well as lessons learned by the program office from the management of Explorer missions. Expectations of the PI on a PI-led mission will also be addressed.
Joseph A. Dezio came to the Explorers Program as the deputy program manager in November 2001 to support the
numerous Explorer missions’ activities and principal investigators. Since arriving at the Explorers Program Office, he has
supported the successful launches of the Swift, Time History of Events and Macroscale Interactions during Substorms,
Aeronomy of Ice in the Mesosphere, and Interstellar Boundary Explorer missions.
To learn more, please visit:
http://appel.nasa.gov/knowledge-sharing/pi-team-masters-forums/
Related Resources
-
Houston, we had a problem…and we learned from it!Space is hard. Inevitably, problems may occur. We can all learn valuable lessons from past events to ensure the safety and success of current and future programs. Enjoy reading and learning from a selection of such events. This booklet produced by the Johnson Space Center Knowledge Management Office contains numerous lesson learned from NASA missions and projects.
-
Apollo 1-Challenger-ColumbiaEvery year as we get back in the saddle, our Remembrance Day signals us to think back to the tragic events of Apollo 1, Challenger and Columbia as well as the context surrounding them. We’re accountable for learning from not just what went wrong, but how we recovered. As an example, read these rules recorded by Wayne Hale, former NASA Flight Director and Space Shuttle Program Manager. By actually applying such lessons from the past to your current work, our actions can honor our lost crews beyond silent reflection.
-
Shuttle Software AnomalyCase Study–A few minutes after the Shuttle Endeavour reached orbit for STS-126 on Nov. 14, 2008, mission control noticed that the shuttle did not automatically transfer two communications processes from launch to orbit configuration. Primary communications continued to use S-band frequencies after they should have transferred to the more powerful Ku-band. The link between the shuttle and its payload — the Payload Signal Processor (PSP)–remained configured for a radio link rather than switching.
