No abstract

No abstract

Given the ever increasing number, scope and complexity of systems today, it is vital to have a cadre of highly trained and skilled systems engineers to ensure that those systems are developed and operated successfully. But from where will those systems engineers come? The Jet Propulsion Laboratory (JPL) has come to the conclusion that if you want them, sometimes you have to grow your own.The JPL Systems Engineering Advancement (SEA) project was launched in FY2004 to advance the practice of systems engineering at JPL, and to address the three key aspects of change: people, process and technology. A significant major portion of the People component of the SEA Project is devoted to a systems engineering on-the-job training (OJT) program. The SEA OJT program will train 50 systems engineers over a five year period according to a threepronged systems engineering competency model. This competency model includes technical domain knowledge, understanding of systems engineering standards, processes and practices, and highly valued behavioral attributes. The behavioral attributes fall into four broad categories: leadership, communication, problem solving and systems thinking, and attitudes and attributes.The SEA Project wrestled with determining the best way to train potential systems engineers along each axis of the competency model, especially how best to inculcate the behavioral attributes. Ultimately, they determined a range of activities that would accomplish their objectives. This mix includes classroom training, hands-on project experience, mentoring and coaching, shadowing, 360 degree feedback, and attending conferences and workshops. This paper 1, 2 provides an overview of the JPL SEA OJT Program including the candidate selection criteria, selection process, training approach and activities, and lessons learned.

No abstract

Systems engineers across NASA needed a single place to go to find various assets to support them in their work, and to help ensure that their missions are successful. These assets ranged from templates and resources to various requirements and processes, as well as points of contact, etc. Hence, there was a need for a central NASA Systems Engineering Body of Knowledge (SEBoK) to store and provide access to systems engineering resources of all types.