The capabilities and limitations of a particular system design are well known by the people who operate it. Operational workarounds, operational notes and lessons learned are traditional methods for dealing with and documenting design shortcomings. The beginning of each new program brings the hope that hard-learned lessons will be incorporated into the next new system. But often operations personnel find their well-intentioned efforts frustrated by an inability to have their inputs considered by design personnel who have strictly-scoped requirements that are coupled with ambitious cost and schedule targets. There is a way for operational inputs to make it into the design, but the solution involves a combination of organizational culture and technical data. Any organization that utilizes this approach can realize significant benefits over the life cycle of their project.


    Access

    Access via TIB

    Check availability in my library


    Export, share and cite



    Title :

    Turning Operational Lessons Learned into Design Reality


    Contributors:

    Conference:

    AIAA SpaceOps 2010 Conference ; 2010 ; Hunstville, AL, United States
    NASA Project Management Challenge 2010 ; 2010 ; Washington, D.C., United States


    Publication date :

    2009-01-01


    Type of media :

    Conference paper


    Type of material :

    No indication


    Language :

    English






    CloudSat Anomaly Recovery and Operational Lessons Learned

    Nayak, M. / Witkowski, M. / Vane, D. et al. | British Library Conference Proceedings | 2012


    CloudSat Anomaly Recovery and Operational Lessons Learned

    M. Nayak / M. Witkowski / D. Vane et al. | NTIS | 2012


    CloudSat Anomaly Recovery and Operational Lessons Learned

    Witkowski, Mona / Vane, Deborah / Livermore, Thomas et al. | NTRS | 2012