In this final lesson of the third module of the course, MBSE,
and the digital thread,
we're going to focus on realizing a Model-Based Enterprise.
When we think about steps to go from where we are to realizing a Model-Based Enterprise,
it may be unclear how to proceed.
A Model-Based Enterprise has clear benefits.
However, it might seem daunting to implement.
MBE seems very idealistic,
and for a small business,
the idea of a Model-Based Enterprise might seem like an unnecessary investment.
However, studies have shown that small businesses
can achieve MBE without a significant investment.
My suggestion would be to think about a road map as a pathway,
rather than a dramatic step change.
So, Model-Based Systems Engineering,
just like systems engineering itself,
is intended to be scalable and tailorable,
and there is no one size fits all.
Model-Based Systems Engineering, like systems engineering,
should begin with your purpose and it's a business value.
Are you after quality?
Are you after responsiveness? After agility?
After innovation?
Whatever you pick helps define your implementation of Model-Based Systems Engineering.
Now, Model-Based Systems Engineering sounds like
a technology and a technical problem – it's not.
It's an organizational change initiative
because it's all about how you represent knowledge.
It may sound daunting,
but realize you're already dealing with that information.
The question is, are you capturing it?
And, you begin what's called progressive elaboration.
You capture the most critical information first,
given the nature of your problem,
given the specialties that are involved,
and given your business objective.
And, you expand it progressively over
time to get the right fidelity of information for your purpose.
One of the places where organizations and practitioners go wrong,
is they try to so-called boil the ocean.
They try to model everything and you absolutely can't model everything,
you can't capture everything.
What you have to do is use good engineering judgment,
to capture the right information,
the right top level architecture,
the right detailed information – where you're injecting new technology,
where you have new requirements,
where you have risk,
where you have high consequence of failure.
So, don't boil the ocean.
Simplify it, and then progressively expand.
And that's really the path to success with Model-Based Systems Engineering.
From the perspective of a small company,
if they're using a CAD tool,
it can be integrated into an MBE framework.
If we're just initially looking at CAD files,
we need to start to integrate that file into a 3D technical data package,
where the files are clearly annotated and defined.
That approach should replace
the traditional 2D drawing-based technical data package
and must contain all related data.
The idea is that,
this technical data package will provide the foundation for reuse,
throughout the product life cycle.
After the model is created,
the organization must make use of the digital thread,
and this can be done by sharing or updating information over a network.
If we begin to focus on one source of data,
then we need to have a mechanism to reliably share model information between departments,
and then, the model is adapted and augmented throughout the life cycle.
As I mentioned earlier,
this is an on ramp towards creating a Model-Based Enterprise.
After the organization transitions to communicating via annotated files,
there can be a shift towards a reference model centric approach.
Where 2D and 3D drawings are simply presentations or views of the reference model.
In this approach, the reference model may initially be a specific folder,
that is version controlled in a product data management system.
All analysis information begins to be generated off of the 3D master model.
Starting to incorporate the practices that enable Model-Based Enterprise.
Capturing and versioning intermediate models where required.
Moving up in MBE capability means bringing in
tools where appropriate to increase efficiencies,
and increase performance, and thinking strategically
about improving how you organize information in a structured manner.
Industrial engineering, systems engineering,
industrial and systems engineering.
They are commonly used terms that we have
to peel back to make sure that we truly understand.
Industrial engineering and systems engineering are classically two different things.
Industrial engineering, when it talks about systems,
often talks about manufacturing systems or management systems.
When systems engineering talks about systems,
it's much more generic.
It could be the enterprise,
it could be the product,
it could be the production system.
Systems engineers are often focused on process and big principles.
So, they are different things.
One of the problems is the terminology is very overloaded,
and you have to peel back to the next level to understand which are we talking about.
This lesson, really briefly,
gives you an overview of the next steps towards a Model-Based Enterprise.
The next module presents a very granular view of the components of MBE,
in the form of a capability index that can be used to evaluate your readiness for MBE,
and identify opportunities for MBE growth.
As you go through the next module,
think about how changes in your organization's practices,
could result in benefits of using the MBE approach.
Ken EnglishDeputy Director
