Project manager perspective

As a project manager, you want your team to release a good quality product in time and with minimal effort. This means that any overhead like managing system engineering tools is lost time. You may consider this an unavoidable reality – however, improvements are possible.

Drivers
  • Make my team more productive
  • Reduce time needed for managing project data across tools
  • Use the tools my team wants with minimal overhead time
  • Use the tools that have already proven to work

As a project manager, you often need to consolidate project information, which is usually stored in different tools. One recurring issue is that information stored in these tools usually diverges, what requires a lot of time for finding out which tool has the most accurate data and synchronizing the diverging data sets. As IOS is based on linked data, consistency of data is less of an issue, because data are not duplicated among the different tools. This implies no  need for synchronization, which makes the consolidation of data more efficient and which makes team members spend less time making data consistent. This takes a lot of overhead out for using your tools in parallel. Any tool, even a web browser, Excel or PowerPoint can have a query on IOS compatible data, as long as the query has the right syntax.

IOS allows you to use the tools that you want or that have been proven to work. There is no need for changing that. If a tool is IOS enabled, then it is possible to link its data to other tools in your tool chain which also uses the IOS. If the chosen tool is not yet IOS- enabled, then you would need to invest in the creation of the adapter, but this has to be done just once.

Furthermore, the IOS uses existing standards, like FMI for simulations, which are well received and widely adopted in automotive, aerospace and control engineering in general.

Questions from project managers perspective

Project manager His internal client (e.g. development manager)
I want to start using tool x. Why? The old tools do not work anymore?
It brings this great feature that will save me a lot of time dealing with product variants / simulation management / other engineering tool function. A true head ache topic, for sure. How will this help?
Well, the tool uses IOS which means that data is linked, not copied. So a variant will point to the same design data that underlies all variants. No local versions of a component for a variant anymore. Well, the tool uses IOS which means that data is linked, not copied. So a variant will point to the same design data that underlies all variants. No local versions of a component for a variant anymore.
You’re right, the deadline is tight. I want one guy to work on it for two months with a go / no-go after 1 month. In the end, I expect it to save me time. So fast? Is this realistic?
The tool is provided with a sample integration guide. It links to my existing data. It seems not overly complicated. That’s what they always say.
Indeed, that’s why we have the go / no-go at one month. Okay, it’s your project. You get one month’s budget.
Thanks. I think it’s worth the risk. Keep me posted.