How do you make systems engineering work for you?
Collaboration is systems engineering
Systems engineering often regarded as one of the disciplines, but it is not. It's about collaboratiion of the other disciplines. And if you work together, you are already using it. The question is not whether you do it, but whether you let it work for you. Systems engineering will work for you if it is an integral part of the job. It's like quality or safety, you can't do it on the side. You do it together.
The basis is that a result consists of parts. Systems engineering helps to control the division, execution and aggregation of work. It is always intertwined with the working method. How you divide the system and how each part performs determines the performance of the whole system. That starts with agreements between experts. Agreements about who does what, who needs and supplies what information and which working method is used. The expert is central.
These agreements are the basis of the structure of every project, they determine the process quality. Agreements follow from requirements, regulations, our own working method or from standards. Standards are essential to facilitate collaboration between organizations. Agreements change and new agreements are added. For example because of new requirements or because you learn new things. One of our users aptly described it as; "In principle it is a growth document". Being able to adapt is to be able to improve.
KE-chain and systems engineering
The core of KE-chain is to connect different disciplines in an environment in which they can exchange key information with each other. It is an integrated environment in which the systems engineer facilitates the collaboration of the experts. Anyone can see the latest information in the project anytime, anywhere.
Finding the information that is relevant to you quickly is becoming increasingly important with increasing digitization. Our experience of highly digital working methods showed us that there is so much data that everyone gets lost, often including the systems engineer. In KE-chain, each expert has their own list with direct links to their own information.
The common thread in all our implementations are data and process standards. These are always different and in the implementation they often deviate to actually use it. This applies to projects in all industries we work with, including; infrastructure, aerospace, energy and automotive. That is why you can build your own data model in KE-chain. With the API you can make all the links you want.
We started with KE-chain because we believe that experts don't need a system that tells them how to work. But that our users want to determine this themselves and can also organize and manage it themselves. In KE-chain you can therefore do the entire design visually, without code.