Concurrent Engineering -which is now and then called
Simultaneous Engineering or Integrated Product Development (IPD) -was
demarcated by the Institute for Defense Analysis (IDA) in its December 1988
report 'The Role of Concurrent Engineering in Weapons System Acquisition' as a
deliberate approach to the combined, concurrent configuration of items and
their identified techniques, incorporating assembling and underpin. This
methodology is expected to create the planners, from the start, to recognize
all components of the item essence spin from origination with transfer,
incorporating value, cost, plan, and client prerequisites.
Concurrent Engineering is not a fast settle for a
group's situations and its not only a course to upgrade Engineering exhibition.
It's a business methodology that addresses paramount association assets. The
major target this business methodology expects to accomplish is enhanced item
growth exhibition. Concurrent Engineering is a lifelong system, and it ought to
be thought about just by conglomerations ready to make in advance financings
then after that hold up numerous years for lifelong profits. It includes major
organizational and social change.
The issues with feature growth exhibition that
Concurrent Engineering expects to overcome are those of the traditional serial
item growth prepare in which individuals from distinctive sections work one
after the other on successive stages of infrastructure.
In traditional serial growth, the feature is first
fully described by the configuration engineering division, after which the
assembling procedure is outlined by the production engineering branch, and so
forth. Generally this is a moderate, excessive and flat-value approach,
expediting a considerable measure of engineering alterations, processing
situations, item presentation delays, and a feature that is less focused than
wanted.
Concurrent Engineering carries as one unit
multidisciplinary groups, in which item designers from distinctive methods work
as one unit and in parallel from the begin of an undertaking with the
proposition of getting things right as speedily as could be expected under the
circumstances, and as right on time as could reasonably be expected.
A cross-utilitarian crew may hold agents of
distinctive methods for example frameworks engineering, mechanical engineering,
electrical engineering, frameworks producibility, manufacture producibility,
value, unwavering quality and maintainability, testability, fabricating,
drafting and layout, and project administration.
In some cases, just plan designers and producing
designers are included in Concurrent Engineering. In different cases, the
cross-utilitarian crews incorporate delegates from acquiring, promoting,
handling, value certification, the field and other practical assemblies. Once
in a while clients and suppliers are moreover incorporated in the crew.
In the Concurrent Engineering approach to
advancement, data is acquired from whatever number utilitarian zones as could
reasonably be expected when the determinations are finished. This effects in
the item improvement group unmistakably comprehending what the item needs
regarding mission exhibition, natural conditions throughout operation, plan,
and planning.
The Concurrent Engineering Approach to Design has a 3-D
Geometric
Data Base as the Hub
Multidisciplinary bunches acting as one unit
promptly in the workflow can take advised and concurred choices identifying
with item, process, cost and value issues. They can make barter-offs between
configuration headlines, part manufacturability, gathering prerequisites,
material requirements, unwavering quality issues, serviceability necessities,
and cost and time obligations. Contrasts are all the more effortlessly
harmonized at a young hour in outline.
Getting the outline right at the begin of the
infrastructure methodology will decrease downstream troubles in the workflow.
The necessity for costly engineering updates later in the cycle can be
lessened. Concurrent Engineering expects to diminish the number of upgrades, in
particular those coming about because of post-configuration include from
backing gatherings. By including the aforementioned aggregations in the
introductory outline, fewer cycles could be required. The major emphasess that
do happen will happen soon after the configuration gets last. The generally
speaking time taken to outline and produce another item might be generously
decreased if the two actions are completed as one as opposed to in progression.
The diminishments in configuration process duration that come about because of
Concurrent Engineering constantly diminish absolute item cost.
Concurrent Engineering gives profits for example
diminished item growth time, diminished configuration revamp, diminished item
advancement cost and upgraded correspondences. Samples from associations
utilizing Concurrent Engineering strategies show huge builds in on the whole
value, 30-40% diminishment in activity times and costs, and 60-80% decreases in
outline updates after discharge.
The execution of Concurrent Engineering locations
three principle zones: individuals, process, and engineering. It includes major
organizational adaptations on the grounds that it needs the incorporation of
individuals, business routines, and engineering and is subject to cross-useful
working and teamwork as opposed to the universal various leveled
conglomeration. One of the essential individuals issues is the structuring of
crews. Joint effort as opposed to single endeavor is standard, and imparted
informative content is the key to victory. Group parts should dedicate to
working cross-practically, be shared, and unvaryingly think and study. The part
of the guide is to supply the essential establishment and underpin for change,
instead of to advise the other group parts what to do. Teaching tended to at
getting individuals to work as one in groups plays a significant part in the
efficacious execution of Concurrent Engineering.
A sample of the utilization of Concurrent
Engineering could be discovered in General Electric's Aircraft Engines
Division's approach for the growth of the motor for the new F/A-18E/F. It
utilized a few arranged, multi-utilitarian configuration and infrastructure
crews to consolidation the outline and fabricating methodology. The crews
actualized 20% to 60% decreases in outline and obtainment process durations
throughout the full-scale segment tests which went before full motor trying.
Situations surfaced previous and were managed more prudently than they might
have been with the conventional improvement process. Process durations in the
configuration and manufacture of certain parts have dropped from an expected 22
weeks to 3 weeks.
An additional case concerns Boeing's Ballistic
Systems Division where Concurrent Engineering was utilized as a part of 1988 to
advance a versatile launcher for the MX rocket and was fit to diminish outline
time by 40% and require by 10% in manufacturing the model.
Polaroid Corp.'s Captiva moment zoom lens is
moreover the consequence of a Concurrent Engineering approach, subsequently of
which Polaroid was fit to make truly countless working models. All through the
procedure, improvement was took care of by cross-practical groups.
To be efficacious with Concurrent Engineering,
associations might as well at first:
·
contrast themselves with their best
contenders (i.e. benchmark)
- ·
improve metrics
- ·
distinguish potential exhibition
enhancements and targets
- ·
improve a clear Vision of the destiny
nature
- ·
get top administration help
- ·
get cross-utilitarian support
- ·
advance a clear Strategy to accomplish
the imagined nature
- ·
get top administration help
- ·
get cross-utilitarian support
- ·
improve a nitty gritty usage plan
- ·
get top administration help
- ·
get cross-utilitarian support
Concurrent Engineering is a business methodology,
not a snappy fix. It will take numerous years to achieve. Assuming that
administration doesn't have any chance or plan to experience the above steps,
then it is doubtful that Concurrent Engineering could be executed.
Numerous groups have situations presenting
Concurrent Engineering. Cautioning marks incorporate:
- ·
unwillingness to systematize Concurrent
Engineering
- ·
support of universal useful prize
frameworks
- ·
support of universal reporting lines
- ·
no educating in teamwork
- ·
unreasonable calendars
- ·
no adaptations involved with sources
- ·
a center on computerization as opposed
to process upgrade
To make Concurrent Engineering a true victory, every
bit of the indispensible qualified data concerning features, parts and forms,
needs to be ready at the correct time. A great deal of halfway-discharged
informative data needs to be traded under tightly regulated conditions. EDM/PDM
empowers Concurrent Engineering by permitting clients, if in humble groups or
expansive gatherings, to enter, circulate, store, and recover informative
content from a mixed bag of origins. EDM/PDM frameworks give architects and
venture bosses access and discharge control over activities and drawings, too
the capacity to track them.
Making Concurrent Engineering a victory is actually
an administration issue. Assuming that administration doesn't get it right then
its not heading off to matter much if EDM/PDM is utilized or not. Moreover,
EDM/PDM can give significant uphold to a fruitful usage of Concurrent
Engineering.
Why
do companies use concurrent engineering?
1)
Competitive
Advantage
The reasons that companies choose to use concurrent
engineering is for the clear cut benefits and competitive advantage that
concurrent engineering can give them. Concurrent engineering can benefit
companies of any size, large or small. While there are several obstacles to
initially implementing concurrent engineering, these obstacles are minimal when
compared to the long term benefits that concurrent engineering offers.
2)
Increased
Performance
Companies recognize that concurrent engineering is a key
factor in improving the quality, development cycle, production cost, and
delivery time of their products. It enables the early discovery of design
problems, thereby enabling them to be addressed up front rather than later in
the development process. Concurrent engineering can eliminate multiple design
revisions, prototypes, and re-engineering efforts and create an environment for
designing right the first time.
3)
Reduced
Design and Development Times
Companies that use concurrent engineering are able to
transfer technology to their markets an d customers more effectively, rapidly
and predictably. They will be able to respond to customers' needs and desires,
to produce quality products that meet or exceeds the consumer's expectations.
They will also be able to introduce more products and bring quicker upgrades to
their existing products through concurrent engineering practices. Therefore
companies use concurrent engineering to produce better quality products,
developed in less time, at lower cost, that meets the customer's needs.
The advantages of
Concurrent Engineering
Concurrent
engineering is a new and flexible way of developing products that allows the
company to gather information from all the parties including the customers and
dealers to concurrently design, build and market as one process. In concurrent
engineering product development, teams of manufacturing and design personnel
are not separated but work together on their tasks simultaneously. The teams
should also include employees from marketing, quality, packaging, and
maintenance that will need to communicate on a regular basis. Customer is a
crucial element that involved in the product development process from the
beginning till the end. Concurrent engineering helps a company to be sensitive
to customer's need by capturing the voice of internal and external customers
and converted it into specific predictable and measurable product
characteristics. A key enabling technology of concurrent engineering is Quality
Function Deployment (QFD). QFD is a structured approach to define customer
needs or requirements and translating them into specific plans to produce
products to meet those needs. The "voice of the customer" is the term
to describe these stated and unstated customer needs or requirements that can
be captured in a variety of ways such as direct discussion or interviews,
surveys, focus groups, or observations. There are some benefits of concurrent
engineering:
·
Maximizes Quality
One of the primary
advantages of concurrent engineering is the quality of the end product. Since
this strategy relies upon extensive product testing and utilizes known data,
the overall quality of products is optimized. It also limits the amount of
defective products that are created.
·
Faster Development
Another benefit is that
products can be designed, developed and created in a timely manner, which means
that products can hit stores and ultimately get into the hands of consumers as
quickly as possible. In a world with so much competition, this ability to
efficiently develop products is important.
·
Reduced Costs
Since the various
aspects of product creation are understood and optimized, there is also a
reduction in development and manufacturing costs, which is mainly due to
limiting the over spending that sometimes occurs with improper project
organization. Also, the potential for creating defective products is reduced,
which also saves money.
·
Happy Customers
The positive end result
of concurrent engineering is ultimately happy customers. Thanks to the
effective product development and creation strategy, customers receive top of
the line products. As a result, those customers are likely to spread the word
and bring in new customers. In the long run, this creates a loyal customer base
that can help a business thrive.
BASIC
PRINCIPLES OF CONCURRENT ENGINEERING
A set of basic
principles have been synthesized from Concurrent Engineering concepts and of
general principles of tackling “wicked” problems. The five principles are:
system thinking, continual improvement, empowerment, inclusion, and
reification.
System Thinking
System thinking is a
conceptual framework to see the whole patterns and to help the team effectively
change them. There are three principles to support system thinking. They are
separation of concerns, co-evolution, and protoiteration.
The principle of
separation of concerns is deeply ingrained in modern problem solving. The
application of this principle also is to break away from the linear thinking
and organize around an outcome rather than tasks. Such a simple change of
mind-set can help to both compact horizontal linear tasks, as well as to shrink
vertical management hierarchy.
For the co-evolution
principle, it suggests that many activities in system evolution are
interdependent and must be viewed as a whole. The requirements for large,
unprecedented systems cannot be fully understood until a substantial portion of
the system is implemented. Teams need to “co-evolve” the requirements and
architecture rather than doing it sequentially.
The protoiteration
principle suggests that iterative use of prototypes to understand a problem,
and hence, minimize the risk of major early commitment of development with
unknown risks. It uses multiple cycles of prototyping of building up
experiences for better management decision or goal definition.
Continual Improvement
This principle promotes
a philosophy of doing it right and getting it better. Attention for improvement
not only is focused on the product, but also on the process for producing the
product. This principle is the cornerstone of a quality conscious organization
and helps any organization move from a firefighting mode of “we do not know why
we have problems with quality,” to the prevention mode of “we know why we do
not have problems with quality”.
Empowerment
This principle
encouraged trusting individuals and teams of having the ability to do the right
things. The heroic acts by individuals or teams when their full potential is
tapped via empowerment are normal among people. However, empowering an
individual or team without a common alignment of purpose could be disastrous.
There are two supporting principles that have been suggested, that are
visioning and localness.
First, a shared vision
provides the necessary alignment of purposes of an individual to that of an
organization. Vision points to where one wants to be. It is this desire of
connectedness that calls out what was untapped potential in each individual
that is empowered.
Second, localness is a
common practice in Concurrent Engineering to locate multidisciplinary teams
physically together to facilitate better communication. This principle,
however, covers more than the physical location. It tries to answer the
question of “How to achieve control without controlling?” It supports the
notion of permitting rapid decision making while maintaining balance between
stability and growth of an organization.
The above three
principles support the empowerment principle in that visioning will help to
nullify the internal politics of an organization, and that visioning, together
with localness, will allow rapid decision making without sacrificing the long
term goals of the Organization.
Inclusion
Another trademark
approach of Concurrent Engineering is the deployment of interdisciplinary teams
with a focus on the customer. In the case of wicked problems, expertise is
usually scattered, and it needs to be brought together to bear on the problems.
The principle of
inclusion suggests a discipline of locating all stakeholders, assigning their
role, and defining communication channels among them.
Reification
This principle suggests
an open exchange of information, both to make the basis of judgement explicitly
and to communicate reasons and rationale. The notion of openness, both to speak
openly without fear, and the capacity to continually challenge one’s own
thinking, is critical in breaking down the defensive game playing that is
deeply ingrained in any organization.
