4. Systems Engineers from
FIVE continents
4
How to ensure effective Systems
Engineering deployment in Projects and
Organizations ?
WHY is key the above question
( see next slide )
Competency is a common
and shared concern of
Systems Engineers worldwide
5. Technical complexity continue
to grow over time
5
Programs that have missed their
commitments reveal many root causes,
including the use of immature
technologies, lack of appropriate
levels of systems engineering
discipline, and a plethora of complex
engineering changes.
6. Contents
6
• Introduction
• Systems Engineering Competencies within
INCOSE
• New Systems Engineering Framework
• Terminology, definitions, and expectations
• Examples of Systems Engineering Models
• INCOSE Systems Engineering Competency
Framework ( ISECF )
• Conclusions
• Final Proposal
7. Contents
7
• Introduction
• Systems Engineering Competencies within
INCOSE
• New Systems Engineering Framework
• Terminology, definitions, and expectations
• Examples of Systems Engineering Models
• INCOSE Systems Engineering Competency
Framework ( ISECF )
• Conclusions
• Final Proposal
8. The practice of Systems
Engineering is…..
8
…..a balance between Systemic and Systematic
aspects:
Systemic - thinking about the whole system, its
context and stakeholders
Systematic - following a structured approach to
the realization of the system
( INCOSE UK website )
10. Relevant Characteristics of
Systems Engineers
10
Systems Engineers are the glue that enables a
complex project to succeed
• Most good Systems Engineers are “T-shaped people“
• Broad understanding across domains/disciplines
• Deep specialist competence in systems approaches
• May also have secondary disciplines
• MOST systems engineers are interesting, and inquisitive people
open to new ideas
( INCOSE UK website )
12. T Model for SE Career Development
12
HW …
DEEP Large Project Lead
BREATH
Educational Disciplines
SW
…
Experience
Mentoring
&
Life-Long
Learning
Program Lead
Small project Lead
Systems Program Lead
BS
MS
PhD
Education
Technical Contributor
( 1 - 4 years )
Team Participant
( 5 - 8 years )
Senior Systems
Engineer
( 13 - 20 years)
Systems Engineering
Leader
( >20 years)
Systems
Engineer
( 9 - 12 years)
Kossiakoff et al ( 2011)
13. Contents
13
• Introduction
• Systems Engineering Competencies within
INCOSE
• New Systems Engineering Framework
• Terminology, definitions, and expectations
• Examples of Systems Engineering Models
• INCOSE Systems Engineering Competency
Framework ( ISECF )
• Conclusions
• Final Proposal
14. Most Relevant Activities on SE
Competencies
• Understanding what makes an
Effective Systems Engineer
o INCOSE Competency Working Group
o INCOSE Competency Framework
• Qualifications
o INCOSE SE Certification
14
15. CWG Scope
15
• Focused on the development and continual improvement of the SE Role
Based Competency Framework and Assessment Guide through collaboration
with users, academia, industry and Working Groups as it relates to changes in
SE processes and methods employed throughout a product or system
lifecycle.
• Maintain a broad membership to enhance knowledge base.
• Evaluate competency alignment with other organizations/functions such as
Program Management.
• Ensure consistency of product with INCOSE SE Handbook and Certification.
• Produce papers for publication.
• Provide training related to framework content and assessment capabilities.
• Collaborate with the INCOSE Professional Development Initiative with training
needs assessments.
16. CWG : Award for Product of the
Year
16
At IW 2019 Competency
Working Group was selected
to receive an award for
Product of the Year in 2018.
This award intended to
recognize the Competency
Working Group for publishing
the
INCOSE Systems Engineering
Competency Framework
17. INCOSE Competency Framework
(ISECF)
17
• This is a generic
framework. It can be
applied in the context of
any application, project,
organization or enterprise
for both individual and/or
organizational assessment
and/or development.
https://www.incose.org/products-and-publications/competency-framework
18. INCOSE SEP Architecture
18
Multi-Level Base Credentials
The base ASEP, CSEP, and ESEP
credentials cover the breadth of
systems engineering at increasing
levels of leadership,
accomplishments, and
experience.
Copyright by INCOSE. All rights reserved.
19. Contents
19
• Introduction
• Systems Engineering Competencies within
INCOSE
• New Systems Engineering Framework
• Terminology, definitions, and expectations
• Examples of Systems Engineering Models
• INCOSE Systems Engineering Competency
Framework ( ISECF )
• Conclusions
• Final Proposal
20. INCOSE BoD tasked CWG
20
In 2014, INCOSE leadership tasked the Competency Working Group
( CWG ) with two objectives:
• The first objective was to evolve the former INCOSE UK Competency
Framework to a globally accepted (i.e., approved for release as an
INCOSE product) and marketed standard competency framework,
based on systems engineering effectiveness, that could be used to
produce competency models tailored to the needs of organizations.
This is an important distinction, the competency framework is not itself
a competency model.
• The second objective was to create a globally used standard
assessment instrument/tool based on the competency framework
that is tailorable to the needs of the customer organizations.
21. Done so far and on-going activities
21
• Originally developed in UK ( 2005 )
o Adopted as an INCOSE Technical Product in UK
o Defines competencies of a Systems Engineer
o In use by UK industry and Government.
• Version 1.0 ( 2018 )
o Evolution to a role-based competency framework that is extensible,
scalable, and can be tailored adding the Concepts of Roles and
Activities.
o Enhance the proficiency levels by adding a new level: Senior Practitioner
• On-going ( 2020 )
o Assessment Guide Development
o Use cases
22. Contents
22
• Introduction
• Systems Engineering Competencies within
INCOSE
• New Systems Engineering Framework
• Terminology, definitions, and expectations
• Examples of Systems Engineering Models
• INCOSE Systems Engineering Competency
Framework ( ISECF )
• Conclusions
• Final Proposal
23. Competency
• A measure of an individual’s ability in
terms of their knowledge, skills, and
behaviour to perform a given role
Holt and Perry (2011)
23
24. Competence vs Competency
• Competence – the ability to do something well;
• Competency – an important skill that is needed to do a
job.
The key difference here is that competence reflects the
total ability of the individual, whereas a competency is a
single skill; (hopefully) one of many that the individual will
hold. The sum of an individual’s competencies will make up
their competence and it is these individual competencies
that are assessed to provide an overall indication of
competence.
Holt and Perry ( 2011)
24
25. Capability vs Competence
• Capability describes the ability of an organization or
organizational unit.
• Competence describes the ability of an individual
to do something.
Holt and Perry ( 2011)
25
28. Future of Systems Engineering
Competencies
F R O M
• The competency of today’s systems engineer vary
significantly in the depth and breadth of their
systems engineering knowledge. Their
competencies are often based on their domain
specific engineering background.
TO
• The expected competencies of a systems engineer
will be more consistently defined and broadened to
support the expanded systems engineering roles.
28
INCOSEa ( 2014 )
30. Roles and Competencies
• A typical systems engineering role varies from
managing requirements to being the technical
leader on a project.
• A job role is a description of what a person does. A
job title is a convenient name for a role.
• A role is the part that is played within a specific
work process within the company.
30
32. Examples of SE Roles
32
Roles Focused on the System Being Developed:
• Concept Creator
• Requirements Owner
• Systems Architect
• System Integrator
• System Analyst
• Detailed Designer
• V&V Engineer
• In-Service Support Engineer
Roles Focused on SE Process and Organization:
• Systems Engineering Capability Manager
• Process Engineer
Roles Focused on Teams That Build Systems:
• Customer Interface
• Technical Manager
• Information Manager
• Coordinator
• Instructor/Teacher
33. Contents
33
• Introduction
• Systems Engineering Competencies within
INCOSE
• New Systems Engineering Framework
• Terminology, definitions, and expectations
• Examples of Systems Engineering Models
• INCOSE Systems Engineering Competency
Framework ( ISECF )
• Conclusions
• Final Proposal
34. 34
Examples of Competency Models
DAU Systems Planning, Research, Development and
Engineering (SPRDE) APPEL Model for Systems Engineers NASA
US Navy’s SE Competency Career Model (SECCM) MITRE Systems Engineering Competency Model
35. Competency Models/Frameworks
are used ( Uses Cases )
35
• Recruiting
• Assessing Candidates
• Improving Education and Training Programs
• Identifying Resources for Professional Development
• Aligning Curriculum
• Developing Career Paths
• Others
36. Contents
36
• Introduction
• Systems Engineering Competencies within
INCOSE
• New Systems Engineering Framework
• Terminology, definitions, and expectations
• Examples of Systems Engineering Models
• INCOSE Systems Engineering Competency
Framework ( ISECF )
• Conclusions
• Final Proposal
37. Why was the ISECF created?
• The INCOSE Competency Working Group (CWG)
produced the framework to improve the practice of
Systems Engineering.
• The framework along with adoption of effective
competency management approaches is intended
to be used by customer organizations to produce
competency models specifically tailored to their
unique needs.
37
38. Aligned with
• US Navy’s SE Competency Career Model (SECCM)
• DAU Competency Model and Acquisition Workforce
Qualification Initiative (AWQI)
• INCOSE Systems Engineering Handbook V 4.0
• INCOSE Professional Development Initiative
• Systems Engineering Research Center’s Helix Study
• Systems Engineering Body of Knowledge (SEBoK Part 5)
38
43. Steps to create a Role Profile using
ISECF
43
INCOSEb (2018 )
Copyright by INCOSE. All rights reserved.
44. Mapping of SE Handbook Processes to
Framework Competencies
44
INCOSEb (2018 )
Copyright by INCOSE. All rights reserved.
45. Comparison of SEP Technical Areas to
New Framework Competencies
45
INCOSEb ( 2018 )
Copyright by INCOSE. All rights reserved.
46. How will the ISECF help me?
• The framework is expected to be tailored to suit the
application and domain in which it is applied,
combining competencies identified herein with
others taken from complimentary frameworks (e.g.
Program Management, Human Resources,
Aerospace, Medical), or generated
organizationally, to define the required knowledge,
skills and behaviours appropriate to an area or role.
46
47. Contents
47
• Introduction
• Systems Engineering Competencies within
INCOSE
• New Systems Engineering Framework
• Terminology, definitions, and expectations
• Examples of Systems Engineering Models
• INCOSE Systems Engineering Competency
Framework ( ISECF )
• Conclusions
• Final Proposal
48. Conclusions
• INCOSE Competency Framework creates generic role
statements embedding Systems Engineering
competencies into the people that make up the
enterprise.
• Role statements can be considered the “requirements” for
the individuals who make up the enterprise (the system).
• A role statement must be a combination of describing
what the role does (activities) and the competencies
(knowledge, skills, abilities & behaviors) that the
individual needs to perform the activities.
• INCOSE Competency Framework is only a guide – the
definitions of Systems Engineering roles must be consistent
with the HR policies of the organization.
48
49. Contents
49
• Introduction
• Systems Engineering Competencies within
INCOSE
• New Systems Engineering Framework
• Terminology, definitions, and expectations
• Examples of Systems Engineering Models
• INCOSE Systems Engineering Competency
Framework ( ISECF )
• Conclusions
• Final Proposal
50. Final Proposal
• AEIS BoD ( Spanish Chapter of INCOSE ) is tasking members to
set-up a national Competency Working Group.
• The scope is : Understanding of practice in our country in all
domains and sectors, their specific needs of systems
engineering practitioners, promote the systems engineering
career path in our organizations, guide for systems engineering
development and adaptation of ISECF to our reality.
I encourage you to participate in this initiative
If you decide to participate! Send us an e-mail
contact@aeis-incose.org
50
