Abstract

AbstractThe definition of competency for Systems Engineering is an important aspect of the implementation and application of Systems Engineering into an organization. This paper outlines why the understanding of competency is important, and focuses on why it is absolutely necessary to tailor the competency model to a particular situation. Tailoring will handle variation both in the nature of the Systems Engineering that the organization does, and the nature of the existing organization in which Systems Engineering is performed. A specific and detailed example of how the Systems Engineering competency model was tailored in Rolls‐Royce (by the author) is presented. The conclusion from this case study is that the understanding of the organizations purpose for the competency model is vital in understanding how to develop it. Rather than attempting (and arguing endlessly) to create the single, definitive competency model INCOSE (through its Competency Working Group) should build a guide on how to create a bespoke model, drawing on a range of case studies that explore the range of purposes for which a competency model is needed.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.