The 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.
The need for a competency modeland the challengesPeople carry out processes, use the tools and perform the activities required. Therefore the definition of the relevant competencies for these people is essential. The UK Engineering Council defines professional competency as integrating knowledge, understanding, skills and engineering (UK Eng Council, 2011). This definition goes further to state that "professional competence goes beyond the ability to perform specific tasks", and so demonstration of competency includes demonstration of the application of skill, not simply the completion of tasks. This is critical, and therefore it is important to have a means of defining the competencies engineers in an organization need, and develop ways of effectively developing them.