Vous êtes sur la page 1sur 3

IMPLEMENTING

Lean Manufacturing Principles


in an A&D Environment

Lean manufacturing is a management philoso- Over time, lean has become somewhat of a
phy, enabled and supported by various tech- fuzzy umbrella for process improvements that
niques, to eliminate any form of non-value add- seek to eliminate waste and duplicate activities
ing activity. With terms like “lot size of one”, in operations. For many lean converts, Enterprise
“continuous flow”, and “pull production”, lean Resource Planning software, typically associ-
manufacturing has primarily been associated ated with large batch runs driven by production
with the factory floors of short run, repetitive planning and dedicated to achieving economies
manufacturers. In an Aerospace and Defense of scale, is antithetical to the principles of lean
(A&D), government regulations often impose manufacturing. But A&D is a unique environment
very different business practices than those fol- where the right ERP system not only works
lowed in the commercial sector. Can lean manu- within lean’s core concepts, but actually is the
facturing principles work in A&D? The answer only viable method for enabling them in the non-
is “yes”. Implemented via an appropriately manufacturing areas that are so essential to suc-
architected ERP system, lean manufacturing cessful defense contractors.
principles can and should play a crucial role in
A&D, particularly in reducing knowledge worker In Aerospace & Defense, more people and costs
and administrative waste, a huge component of are involved in Engineering, Project Manage-
cost in A&D environments. ment, Contract Negotiations, and Cost Account-
ing than in actual manufacturing activities on the
The practice of lean manufacturing got started shop floor. In this environment, progress pay-
in Japan in the 1950’s at Toyota Motor Com- ments, document control, and an extensive com-
pany. Seeking to reduce manufacturing costs, ponent audit trial (none of which would normally
Toyota set up a system in which demand directly be viewed as adding value to a product) are criti-
drove production. Each sale of finished goods cal components of the deliverable. This paper-
triggered a signal for replenishment. The signal work factory underpins every manufacturer pro-
cascaded back through the manufacturing pro- ducing goods for the government. The products
cess, at each step “pulling” a replacement for of this paperwork factory go through processes,
consumed inventory. This highly successful flow down time and often, unfortunately, rework,
manufacturing methodology dramatically drove much as do physical products. Superior perfor-
down lead times, transaction costs, and inven- mance here is where A&D manufacturers, so
tory, both within the factory walls and through- tied to these functions via regulatory require-
out the supply chain.

1
ments, can significantly pad or pare their mar- customer, contract, or project number. Systems
gins. If lean manufacturing is about using only designed from the bottom up for project control
what you need to get the job done and eliminat- avoid both the creation of additional databases
ing superfluous work and equipment, then and the need to tap into the GL to extract WBS
implementing vertical-specific ERP is only way data, by sending only costed journal entries to
to achieve lean in A&D’s major expense centers. the GL and the Actual Cost of Work Performed
from Receiving, Labor, WIP, etc., directly to the
Let’s take a few examples to illustrate: appropriate Work Breakdown Structure. Infor-
mation for progress payments (or Earned Value)
Progress Payments roll up in real time without unduly burdening
Imagine your company has just been requested other departments within the organization, or
to provide government regulators with full back- the system itself.
up to support the latest progress payment. With-
out project-oriented ERP, the workflow for the Inventory Integrity
request will start with the project manager, who Many A&D manufacturers produce products re-
will translate the request into report require- quiring project specific inventory items and, fre-
ments for the IT department: “I need to know quently, a full audit trail. Some face an even more
exactly what components have been purchased complicated situation by needing a mix of project
towards the project, how many are in WIP, how specific and stock items commingled for a single
many in inventory, and labor to date”. IT then end product. In both situations, many functional
builds the “bridge” between what your software areas within the organization, including Pur-
provides out of the box and the information that’s chasing, Receiving and Kitting will be forced to
required for the report. Not infrequently, this will somehow artificially tag items to specific projects
require manual reentry of data and/or the cre- (and, perhaps, specific warehouses). Account-
ation of additional databases outside of those ing and Finance also will need to design cre-
native to the software. When all is said and done, ative ways to track cost components.
the report may be reusable, but each time it’s
run, it will go to the General Ledger to gather its In a lean A&D environment supported by ap-
costing data. It won’t be up-to-date, since com- propriate ERP capabilities, inventory can be ac-
mercially-oriented software typically sends data cepted into specific warehouses, projects, and/
to the GL in batch mode. Even worse, it will have or work breakdown structures, or users can elect
exponentially multiplied the number of transac- to plan certain items without regard to projects,
tions the ERP system is handling, clogging its so that production or purchasing efficiencies can
arteries and slowing it down for the “real” work be maintained. All these capabilities are avail-
the factory needs to produce the goods. able without manual workarounds or a force fit,
creative misuse of the native capabilities of com-
ERP architected for project-oriented businesses mercial software.
completely avoids both the human and informa-
tion workflows detailed above. Industry-specific Throughout the paperwork factory in A&D
modules, including Work Breakdown Structure, plants, including order reporting, engineering
Project Control, and Design Engineering enable change control, and document control, ERP
multi-level cost collection and reporting by job,

2
systems fundamentally architected for project  Database proliferation
control can avoid or reduce:
 The number of transactions within the
 Management time dedicated to deter- ERP system (streamlined ERP function-
mine reporting requirements – project- ing increases the system’s overall speed
oriented software was built to automati- and efficiency)
cally configure to the report require-
ments of an A&D environment A&D manufacturers are typically working under
multiple-year contracts, tight security, classified
 IT customization set-up time to develop products, and exacting cost, inventory, and fin-
“work-arounds” ished goods auditability requirements. The
myriad reporting tasks imposed by such require-
 Manual pulling and entry of data into ments seem to preclude the implementation of
secondary data sources for standard many lean manufacturing initiatives. Yet success-
government reporting requirements ful companies in the A&D industry are reducing
costs in key functional areas through the imple-
 Initial customization costs, time, man-
mentation of an ERP system whose architec-
power, and/or dollar outlay required to
ture is native to A&D reporting requirements.
build the “bridge” or manually collect
information

Relevant Business Systems


12667 Alcosta Blvd., Ste 300 • San Ramon, CA 94583
Phone: 800.473.5382 • FAX: 925.867.3840
www.relevant.com • relevant@relevant.com

Vous aimerez peut-être aussi