Channels ▼


The Big Picture On Complexity

How do you get the job done when a task is shared between several teams scattered around the world? A European R&D cooperation, the Eureka ITEA2 3D TestBench project, might bring a change in project managers' complicated lives.

The 3D TestBench project has been developed within the frame of The Eureka Cluster for software development ITEA 2: Information Technology for European Advancement. This pan-European cluster involves some of the mosst-preeminent companies in the sector and has already led some of the most ground-breaking innovations in the software-intensive systems and services sector.

To solve the problem of complexity might be one of the major goals of the 21st century: Human beings are exposed everyday to increasing amounts of information that we are unable to digest, and there are no signs of a downturn. In the technology field, this is translated into the high number of parameters to take into consideration, as development projects are getting bigger and often too complex to be grasped entirely by one single person.

In an engineering process, the stage referred to as the integrating phase — the point when the knowledge of different teams is put together into one single outcome — is posing a huge problem. Several research teams around the world are working on the development of what is called a "collaborative engineering environment" and are beginning to create the tools to facilitate the integrating phase.

The solution proposed by the team led by Andy De Mets, leader of the 3D TestBench project and R&D projects coordinator at Barco, is the integration of all the tools used by different groups into a single instrument, compatible with all of them. "In fact," says De Mets, "a lot of engineering tools and software are being used and these tools are not always conceived to interact with each other."The outcome of the project looks like a giant 3D screen or "wall" where all the stages of the engineering and product conception process are displayed. Change one aspect of the project and the modifications implied at all of its stages will show, highlighting potential conflicts. Of course the system developed within the 3D TestBench project needs to be adaptive. It does not consist of one single software source, it is rather "the wall and its workflow management tool that are at the heart of the system," says De Mets.

The first user of the new device was Fokker Elmo, a company specializing in aerospace engineering. It was the consortium's guinea-pig, supplying the model that allowed optimizing the workflow tool. Barco, a company specializing in visualization instruments, developed the 3D wall, working closely with NOESIS Solutions, LMS International, a simulation solutions provider. The Technical University of Delft in the Netherlands, and the Vrije Universiteit Brussel, Belgium brought in the academic background in complex project modelling necessary to develop the project. "The complementary expertise and enthusiasm of the human team-force that was brought together was a crucial aspect for the success of the project," says De Mets.

Possible applications are very broad, since the project represents the solution to a problem potentially faced by any type of organization. Companies having already contacted the research team members represent major players from the automotive industry and the energy market. De Mets envisions that with the international fragmenting of research teams and the trend for open innovation, the concept of a collaborative engineering environment will only become more central in the future and the system developed during the project will be employed by more and more companies.

[Click image to view at full size]
Seeing a project in 3D.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.