Välkommen till årets upplaga av Nordic Systems Engineering (NoSE) Tour i Stockholm. Vår värd är KTH, institutionen för Maskinkonstruktion på Brinellvägen 85.

I deltagaravgiften ingår lunch, samt för- och eftermiddagskaffe.

För att anmälan krävs ett konto på incose.se. Om du inte är medlem så kan du enkelt skapa ett konto genom att följa dessa instruktioner. Sista anmälningsdag är den 17/5-2023.

Programmet 

09:00 – 09:15	Welcome by INCOSE Sverige
09:15 – 10:00	Ulf Carlsson and Jan Johansson	Enabling the Digital Thread – The Standards Framework for a Smart Industry
10:00 – 10:30	Coffee Break and Networking
10:30 –  11:15	Hendrik Dahmke	How I failed to establish a systems engineering team
11:15 – 12:00	Mike Johnson	Overcoming challenges to effectively implement Systems Engineering
12:00 – 13:30	Lunch and Networking
13:30 – 14:15	Erika Palmer	From the US to Norway and back again: a Systems Engineering Tale
14:15 – 15:00	Coffee Break and Networking
15:00 – 15:45	Erik Herzog, Torbjörn Holm, Judith Crockford and Jad El-Khoury	Towards Federated Product Lifecycle Management
15:45 – 16:00	Famous Last Words

 

Abstracts

Enabling the Digital Thread – The Standards Framework for a Smart Industry

Ulf Carlsson, ulf.carlsson@cag.se, Sweden, CAG Syntell AB

Jan  Johansson, jan.johansson@cag.se, Sweden, CAG Syntell AB

In today’s digital landscape, as well as that of tomorrow, standards will be of utmost importance to enable successful system lifecycle sustainability, from the concept stage to recycling. A well-defined information landscape is essential for the use of technologies such as digital twins, the internet of things, and additive manufacturing. Standardization of information will be the foundation of a successful digital collaboration.

This presentation will introduce the Scandinavian Smart Industry Framework (SSIF), developed with the purpose to form a common national basis that will enable the transformation towards a smart industry, i.e. the digitalization of industry by using standards and standardized integrated models for manufacturing and managing products over their life cycles. Also, SSIF aims to promote knowledge regarding which standards can be used to achieve a semantically interoperable information exchange.

The central part of SSIF describes the principles used to organize information in various content dimensions to enable a variety of specific implementation models, e.g. a system dimension based on ISO/IEC/IEEE 15288 is planned.

SSIF has been developed by Technical Committee TK 280 ”Industrial data and interoperability” of the Swedish Institute for Standards (SIS) as an input to ISO/IEC JWG 21 in its development of the Unified Reference Model for Smart Manufacturing, IEC/ISO 63339 ”URMSM”.

The Unified Reference Model for Smart Manufacturing (URMSM) terminology and structure comprises a set of common modeling elements, address aspects and perspectives of products and production. URMSM also provides the lifecycle considerations for developing standards and other specifications as well as principles for consistent, coherent, compatible specializations for relevant aspects of systems, products, and services within the industrial domain.

The models in the SSIF are created in the context of ISO/IEC JWG 21. In future versions of SSIF, the models will be illustrated for a wider audience and managed in a semantic model software, dimensions will be updated, and new dimensions can be added.

The JWG 21 work is supported by TK 280 ”JWG21 team” from KTH, LTH, Eurostep, Syntell/Saab Kockums, Volvo Cars. The development of SSIF has been conducted in close collaboration with Norwegian participants in ISO/IEC JWG 21. INCOSE is heavily involved in this effort led by Richard Martin.

How I failed to establish a systems engineering team

Hendrik Dahmke, hdahmke@live.com, Germany, in-tech

In my previous job, I had the opportunity to establish a new systems engineering team with the goal of implementing systems engineering principles and model-based systems engineering methodologies. The team was composed of individuals with diverse skills such as requirements management, software architecture, and agile coaching. We began a sample project to build a system that could assess air quality by identifying the CO2 content. Our approach was to learn by doing, utilizing the expertise of all team members and applying systems engineering in an agile environment.

In addition, with agile coaches we could identify both how systems engineering would be applied in a SAFe environment and how systems engineering could be done agile.

However, as the project progressed, I realized that I had made a critical mistake in not fully considering the importance of understanding the "why" behind our project. We had a project plan, we identified goals, and set a timeframe, but we did not fully understand the purpose and higher goal of the project. This lack of understanding led to confusion among team members and ultimately, the project was not as successful as we had hoped.

I wanted to establish systems engineering practices and certain requirements, which needed to be fulfilled in order to make this project a success. Never the less I could not see that I have failed to start with thinking about why we were working on this particular project in the first place. I could take this even further - If I had seen the “why”, I would have added some theoretical lessons about important next steps, which would have insured that all members of the project were on the same page.

The main lesson I learned from this experience is that systems engineering always starts with understanding the "why" behind a project. This includes understanding the requirements and goals of the system, as well as the needs and wants of the customer. By understanding the purpose and mission of a project, team members can work together more effectively towards a common goal. In addition, understanding the "why" also helps to prioritize and make important decisions regarding the project.

In my current job, I have incorporated this lesson by utilizing the 5-Why-Method to understand the purpose and mission of our systems engineering team. By reflecting on my failure and understanding the importance of the "why," I am now better equipped to lead and establish successful systems engineering practices within my company. I am also more conscious about making sure that the entire team understands the “why” behind the project, so that everyone is on the same page, and all actions are aligned to the our goal. Overall, understanding the "why" is a powerful tool that can lead to more effective and efficient systems engineering.

Overcoming challenges to effectively implement Systems Engineering

Mike Johnson, maj101@gmail.com, Switzerland, SE-Training GmbH

Each and every organization developing and maintaining technically complex systems, has a strong inherent need for applying Systems Engineering. Effective implementations are always unique, as there are challenging and often dynamic needs and constraints shaping the Systems Engineering solution.

Systems Engineering’s origin from the Aerospace and Defense Industries can be effectively utilized to bridge effective implementation into many other industries, most notably within highly regulated industries.

The presentation addresses why we must firstly understand where Systems Engineering has come from, to enable the identification of the obstacles that must be overcome for effective implementations.
From the US to Norway and back again: a Systems Engineering Tale

Erika Palmer, erika.palmer@gmail.com, United States, Cornell University

Systems engineering is often lost in translation between countries and continents. This is especially true in academia, where systems engineers need to transect disciplinary boundaries, each with their entrenched norms, philosophy and language. I've had my feet flittering between Norway and the US since the fortunate accident of getting "stuck" in Norway for love in early adulthood. My systems engineering journey developed between these two countries over the past 20 years, meaning that I am best described as a mixed heritage systems engineer. This is not only for geography reasons but also due to having both an engineering and social science academic upbringing. While this comes with great benefits, there are certainly a number of lessons that I have learned along the way. This talk explores this journey in terms of the dis/similarities of being a systems engineer between countries and disciplines as a researcher and academic. In addition to the ups and downs along the way, I will discuss how diverse perspectives will help foster an environment to support both INCOSE 2035 and the Future of Systems Engineering (FuSE).

Towards Federated Product Lifecycle Management

Erik Herzog, herzog.erik@gmail.com, Sweden, SAAB AB

Torbjörn Holm, torbjorn.holm@eurostep.com , Sweden, Eurostep AB

Judith Crockford, judith.crockford@eurostep.com, United Kingdom, Eurostep AB

Jad El-Khoury, jad.elkhoury@lynxwork.com, Sweden, Make Lynxwork AB

Product Lifecycle Management (PLM) is a key capability for any organization developing and/or maintaining complex systems. This presentation experience from activities implementing a modular architectural pattern for realizing a federated PLM capability from integrating multiple engineering discipline specific development environments. This open the possibility for replacement of individual environments, while maintaining the overall development system landscape. Thus, providing a desired flexibility in adapting to future organizational challenges at comparatively low cost.

The work presented has been carried out in the Heliple project, supported by Vinnova.