ENGINEER PERSPECTIVE

As an engineer you just want to do your work. You want to use tools that are most appropriate for the work you are doing. You do not want to be bothered by unnecessary (re)work caused by making data consistent or inefficient processes. It would be really beneficial for you to be able to reuse data from other parts of the engineering cycle, in order to assess the impact of changes.

Drivers:
  • Remove barriers in using engineering tools
  • Smooth collaboration with others in the engineering cycle
  • As few as possible errors and rework

CRYSTAL offers solutions that tackle the problems that engineers encounter

Each discipline uses its own set of tools and wants to keep it that way. One solution in which everyone uses the same tool is not feasible in practice and this tool simply does not exist. With the IOS it is possible for everyone to use their own tools with proprietary data formats but tools can understand each other’s data. If you want to switch from your current tool to another tool that is also easily done! Integration of the new tool in the complete tool chain is facilitated by IOS and a lot easier than before. Point to point tool integrations are no longer needed, only one IOS adapter needs to be built for the new tool.

“Can you imagine what kind of tools would be possible if the IOS would be industry wide applied? The seamless integration of tool chains will be facilitated, new tools adopting the changed conditions will arise, and the complexity of the development process during the whole product life cycle will be efficiently manageable.” (Bola Rotibi - Creative Intellect Consulting, Research Director)


Currently teams share information by manually creating document based reports or point to point tool integration. Collaboration is easier with the use of IOS, as workflows that were previously disjoint can be connected. Tools are able to understand each other’s data, which makes it possible to share, search, link, analyze, track, and review all available design artefacts across the lifecycle. When more information is available for everyone in the engineering cycle more transparency is created and better decisions can be made. This makes the design process more efficient, as the chance that the design does not meet expectations is decreased. This also implies less rework for the engineer.

IOS enables early collaboration in the development process. This results in early detection of errors that were previously only discovered later during integration. And even across projects data can be reused and shared when the IOS is implemented. Incremental development can therefore be achieved with less effort.

The impact of proposed changes is often uncertain. With IOS the impact of changes can be traced and made visible to all stakeholders. The IOS also makes it easier to document compliance to regulatory, industry or corporate standards.  As no longer a lack of integration between tools exists, artefacts can be traced throughout the lifecycle. With IOS this is no longer a manual process and the process is less error-prone.