SESG Summary and conclusion

1. SESG Summary and conclusion • 29.11.2012 @ Hibu • 2pm – 5pm

2. SESG numbers and data • SESG facilitators: 3 • Coffee with cookies available: Yes  • Duration: 3hours and 10minutes • Participants: 21 (people from industry and academia) • Presentations: 3 (37 slides total) • Presenters: 4 (all from industry) • Workshop groups: 4 • Posters with group feedback: 6

3. SESG| | The Systems Engineering Study Group meets at Buskerud University College (BUC), Kongsberg, Norway. The objective of the meetings is to exchange experience between people who are interested in Systems Engineering or who have the intend to become a Systems Engineer. The SESG discusses one theme per meeting, the subjects are one of many SE aspects. We have two to three meetings per year Systems Engineering Study Group 2012 The SESGwould like to inviteyou to thenextmeeting 27th November at Hibu University College, 2pm to 5pm. Presenters: Aksel Bondø & Daniel August Jensen The Pre-studyApproach Svein Erik Søgård ModelingLanguageReferenceModelDefinition Johan Grønvall How to Present to (Top) Management 1 2 Topic: ”How to get acceptance for systems modeling from management” Description: Many systems engineers have a dream of sharing system knowledge in their company using system models. This requires major changes in an organization and often requires support from management. How do you get management of your company to give you the chance to try out systems modeling in the organization? This falls SESG presenters will share with you their experience on this specific topic. 3 Afterthepresentationswewillarrangegroups and facilitate a workshopwithtasksrelated to thespecifictopic.

4. Workshopquestions • Q1: • How would you present to convince Management to let you try systems modeling in your company? • Q2: • How would you proceed to get acceptance for systems modeling in your organization, and what factors are important? • Give examples. • Q3: • How would you proceed after having gotten acceptance for systems modeling? • How would you organize your systems modeling effort? • Where would you start your modeling effort? System or sub-system? • Q3: • How do you know that your systems modeling effort has been successful?

5. Workshop results • Group 1 • Q4 • Parameters: Time, cost, quality, amount, satisfactory • Mean of measurement : two pilot projects run in parallel, one without and one with the use of SysML • Analysis: NPV (Net Present Value) benefit/cost and Monte Carlo • Q1 • Identify stakeholders • Analyze stakeholder needs • Make communication plan • Execute communication plan • Convince/influence management before meeting

6. Workshop results • Group 2 • Q3 • Start with a bird perspective • Limit the scope with a specific and not to big of a project • Calculate the need for some reverse engineering, meaning creating a set point • Limit the amount of diagrams • Build a small team first (these are important people to use in future projects as coachers) • Start with specific problems/projects with relevant tasks • Q4 • The model is used in every project. Count the number used as a mean to measure • The model is self-explanatory  new employees (important with precise information) • Define the success up front • Create reusable models, module based design to create/increase the interaction between disciplines • Try to measure the level of abstraction. Identify the level of where one should stop the abstraction • Identify the value of the model used • Identify and specify stakeholders upfront, try to measure the benefit

7. Workshop results • Group 3 • Q1 • Define scope on what to model • Identify the correct management level to “attack” • Identify core values/key drives • Present short term benefits • With a “model based world” one is able to utilize new employees faster • Become more efficient by re-using models • Target the “decision makers” in the company • Try to show dedicated cost- usefulness analysis using system modeling • Q3 • Pilot project • Regularly present progress and experience to management and to other division/levels • Use within a core project team (5-10 member) • Apply on a “small call” system project that has a clear and defined scope • Create a modeling process and a reference model to use • Establish a model responsible role within the project • Continuously review the system models made • Reflect/align the project group every day using 15min morning meetings

8. Workshop results • Group 4 • Q1 • Describe what business needs that will be solved • Describe the reason and concerns behind and for the current situation • Present specific examples, perhaps based on own experience • Describe the thought benefit of the future modeling effort • Describe the work method and process • Q4 • Identify stakeholders • Conduct interviews • Make and document observations

9. SESG feedback + and - • + • New knowledge gained • Relevant and interesting topic (presentations) • Networking, learn and share knowledge • Positive to see presentations on executing presentations better • Raise the need for system modeling again • Workshop with good discussions • - • To much theory with new terms, somewhat unclear • The SESG invitation could include a short abstract of each presentation • Plan more time on the workshop part • The presentation about the SysML was to complex • The workshop tasks could be more specific and “crips”

10. Conclusion(s) • Identify stakeholders and their needs • Describe as-is situation along with key business drives and needs • Make a clear short term plan for a “small” pilot project with a clear scope when it comes to type of system/subsystem and with a integrated group of people • Continuously review and validate models and modeling effort