It isn't What that drives you or How that intrigues you
but the Why that compels you.
Technology is advancing, but the Why must remain the driving force in the scope of a project. Dreaming big is great when time and budget are thrown out the window. Showing What is possible means nothing when
it cannot be accomplished in a necessary amount of time. Even showing How it can be done, may not convince
anyone if they don’t see an advantage to the effort.
It is the Why that has to compel us to achieve the What through the How. Why draw on
paper when the information can be developed faster on a computer? Why draw multiple 2D views when a single 3D
view can create the same content? Why
design and then model the content separately when the design can aid in the
modeling? Why manually change sizing
when the design changes in the model can automatically provide the correct size
as controlled inputs change? Why
manually draft schedules when the schedules populate as model elements are
placed? Why even settle for one
manufacturer’s schedule when more standardized schedules are needed from
project to project? So, the
question becomes Who is going to provide this, What does it look like, How is
it accomplished and When will it be available?
What if the shared parameters were already out there? How could they be identified? How is it possible to know which ones to use? In a constantly growing library of shared
parameters, a collection of parameters began to rise to the top. These top parameters were found in multiple
families across many major manufacturers and companies.
The Master Library is based on the discovery of these parameters and
follows a Labeling Convention that identifies the purpose of each
parameter.
Hopefully, the Why becomes
evident and the What and How will follow.
- Craig
No comments:
Post a Comment