Lesson three of this module of

model-based enterprise self assessment is

focused on configuration management and document management.

configuration management, also known as CM,

controls different configurations of a product design.

Document management, or DM,

gathers documentation for each configuration that then can be distributed.

As the level of our model-based enterprise assessment increases,

the activity within this tool set will also increase.

So, when we look at the change management and

the document management activities within the MBE Assessment Tool,

we have four focus areas: release and change processes,

CM vault management, collection of elements into a TDP,

and the management of the TDP.

Considering the first focus area,

release and change processes,

we can see that levels zero,

one and two all have the same expectation,

that you're using some form of drawing

based and manual configuration management and document management processes.

At level three, there is a shift to a model-based approach,

but we are still using manual configuration management and document management processes.

At level four, we're starting to increase the automation in

the configuration management and document management processes.

We are still using model-based processes that are

manual but some configuration management processes are controlled.

For level five, we are still looking at model-based,

but now all configuration management processes are controlled within the PLM system.

At level six, continuing to use model-based designs,

all of our configuration management processes derive from

the PLM and automation will be completely supported.

The second focus area of configuration management and design management activities,

another way you can think of this is,

as PLM, is change management vault management.

In other words, where is all this information being stored?

For this area, level zero and one have the same requirements.

2D drawings and supplementary data are managed in a manual vault and database.

Information is managed in a separate database or repository outside of PLM.

In other words, zero percent of it is in the PLM.

And as a result, models are not well managed or not managed at all.

For level two, 2D, 3D,

and the supplemental data is still managed in

a separate database outside of the PLM system.

We can consider this as being up to 25 percent of the content in the PLM.

Change management is managed mostly within a separate database.

Some models, not all,

are managed within the PLM system.

For level three, 2D and 3D supplemental data is managed in a manual vault and database.

This is where we are now increasing to 50,

to 75 percent in the PLM.

Change management is still managed mostly within a separate database.

At level four, 2D and 3D are managed within a PLM.

We realize, at this point,

in level four there's likely minimal 2D PMI information because we're

really focused on completely relying on models to communicate design intent.

There is some supplemental information in the PLM,

and the change management process might still be manual.

We have been able to transition at this point some change management into the PLM system.

At level five, we are looking at all of our data fully managed by the PLM system.

This includes all data and change management processes controlled within the PLM.

And at level six, we're still fully managed within a PLM system and we have

augmented that with automated supporting routines that help us through our processes.

The next subcategory of the change management and

document management activities focuses on

the technical data package or TDP and the collection of elements into the TDP.

For this subcategory, levels zero, one,

and two have the same requirement or expectation.

This is, an ad hoc manual approach is used to collect elements of 3D TDP data,

in other words, digital and physical data.

At level three, we start to have a more structured process,

still manual, but we're collecting digital 3D TDP data.

At level four, we begin to reap the true benefits of a singularity of data by enabling

a semiautomated collection of digital 3D TDP data by the PLM system.

Levels five and six have similar focuses: the automated

collection of digital 3D TDP data by the PLM system.

The final subcategory of

configuration management and design document management

activities is the management of TDP.

At the most basic level, level zero,

we have no process to manage or deliver 3D TDP data.

Levels one and two have the same requirement.

There is an ad hoc manual digital or physical delivery of 3D TDP data.

Levels three and four look at a structured digital delivery of full 3D TDP data.

And level five has the same requirement as level six with respect to management of TDP,

where there is an automated digital delivery of the full set of

3D TDP data by the PLM system.

This lesson should give you some understanding of the different aspects of

change management and document management

and how this fits into a model-based enterprise.

We've gone through design activities,

shifted to configuration management and document management.

Now, we get to planning the manufacturing or planning the production of the product.

That's the topic of the next lesson of this module.

Configuration Management and Document Management

MBSE: Model-Based Systems Engineering

Meet the Instructors