Systems Modeling Pre-study Approach

1. Systems Modeling Pre-study Approach How to identify needs to make valid improvements within the organization WORLD CLASS – through people, technology and dedication

2. Introduction The purpose of the Systems Engineering Study Group is to • Exchange experience between people who are interested in Systems Engineering or who have the intension to become a Systems Engineer. We want to share? • An approach for identifying and clarifying the needs for Systems Modeling within the organization as basis for concept selection. Why do we want to share this experience? • Our approach proved to be both time efficient and effective and we think it can be useful for other Systems Engineers.

3. The full picture

4. Mantra In Kongsberg Maritime we believe in involving and listening to stakeholders, in topics that matter to them, in order to make decisions for improvements that are valid and based on knowledge. Why did we use this mantra? The mantra in itself is not true. However, “a lie told often enough becomes the truth.” – Lenin (Proof by Assertion)

5. Approach Abstract • Define hypothesis • Define stakeholders • Plan interviews • Perform interviews • Analyze results • Concept selection

6. Define Hypothesis Defining the scope enables you to ask the right questions and look for useful results. Define a an area of improvement • How to model system so that we can improve • Communication of system knowledge • Capture of system knowledge • Development of systems Proposed improvement • We had an idea that we have a need for more consistent systems modeling.

7. Define Stakeholders To get a balanced picture of the needs, and to make use of the knowledge and experience of the people within the organization. Lifecycle and cross functional perspective

8. Stakeholders • Project Manager, Technology Platform • Product Manager, Safety Product • Student/Tester, Systems and Project Management • Developer/Architect, Technology Platform • Manager, P&D Management Group • Developer/Architect, Application Development • Test Manager, Release and Test Group • Lead Engineer, System Support DP • System Architect , Systems and Project Management • Project Manager , Systems and Project Management • Technical Lead, Safety Subsea • Student/Engineer, DP Application • …

9. Plan Interviews To be able to ask the right questions in the interviews and to get quantifiable data. Ask validating questions • How do you obtain knowledge about the systems that KM makes? • Are you satisfied with the form in which knowledge about the systems that KM makes is presented? • Do you think engineers need training in making or reading system models? • Do you think system models for different systems in KM are made in a consistent matter today? And clarifying questions • What criteria do you think is important when choosing a system modeling language?

10. Face to Face and One on One Interviews To simplify the organization of meetings, get uninfluenced opinions from each stakeholders, and to keep focus during the interviews. We enabled continuous improvement of the interview plan by debriefing in the study group in-between interviews.

11. Analyze Results To be able to find the significant results and correlations between them from the interview data. • We have found that most engineers asked (95%) obtain their system knowledge by talking to colleagues. • We found that many engineers asked (85%) are not satisfied with the form in which they find system knowledge in Kongsberg Maritime. • A majority of the engineers asked (80%) would like system knowledge to be found in models. • All engineers asked prefer consistent systems modeling, and think systems are modeled inconsistently in KM today. • Every engineer asked thinks that engineers need training in making and reading system models.

12. Concept Selection with Pugh Matrix To be able to choose a concept based on weighted stakeholder criteria. Research multiple concepts • What is academic literature saying • What is best practices saying • What are the experiences within the organization • What is done on cooperating companies

13. Pugh Matrix

14. Summary Shut up and listen to the stakeholders!

15. Know your Audience Different audiences have different interests and needs different presentation approaches and information. We have presented the pre-study to these audiences: • Internal review • The entire study (why, how, what) • Program & Product Management • Results from pre-study (how, what) • Systems Engineers and Project Managers • More focus on the chosen concept (how, what) • Entire Product and Development department • Pre-study methodology (why, how) • Appeal to stakeholders • SESG • Pre-study methodology (why, how) • Appeal to peers

16. Conclusion By using the methodology described • We were able to perform the pre-study in one month, with two people working 10% each. • We found that there is a need for a common systems modeling language in Kongsberg Maritime, and that SysML best fit the stakeholder needs. Our next steps • Definition of a systems modeling language guideline • Pilot project

17. Kongsberg Maritime

18. WORLD CLASS – through people, technology and dedication www.kongsberg.com