Information ArchitectureThe foundation for much of the
information system technology at TRW was the JCALS initiative and from EDM
capabilities. JCALS lends its relevance for producibility in data exchange and
transfer, systems database structures, information processing, and delivery of
deliverables in digital format. Without a JCALS-like capability and concurrent
engineering processes, the IPT's effectiveness is sub-optimal in a highly
competitive environment.

The producibility and supportability information architecture have a common
denominator, the Information Node which can be the Work Breakdown Structure
(WBS) or the Work Unit Code (WUC) for support aspects, as shown in Figure
E.12. All information pertinent to the producibility or supportability
characteristics can be readily captured in a WBS/WUC data element. This
architecture enables the producibility engineer to capture lessons learned and
develop the corresponding PDTRs. Included would be an engineering history as
well as the lessons learned to provide comprehensive traceability of the new
product lineage.

The integrated database, constructed from a combination of customer
provided and internal information systems, accelerates an in-depth
understanding of the nature of design-driven producibility requirements.
This database must include not only the producibility characteristics of the
prime hardware to its lowest indenture level (aircraft, train, commercial
generator, etc.), but all the related manufacturing equipment which, in some
cases, may be the real driver. For example, a sudden manufacturing equipment
failure or out-of-tolerance condition can cause a serious schedule impact on
the prime hardware, especially when failures occur during a critical stage
of the manufacturing process. In that case, an organized approach focusing
on the producibility elements, sub-elements, and information nodes is
necessary; consequently, the sub-elements would include Facilities,
Equipment, and Transportation, as illustrated in Figure E.12 . By
categorizing and linking the baseline with the project data as indicated
through the cell characteristics, the manufacturing equipment issues can be
nested in the same WBS that provides information for the prime hardware.

Studying the elements and sub-elements highlights that several levels of
integration should occur before a requirement set is conveyed to the design
organization, although subsequent design iterations are inevitable. But if
done rigorously and in a knowledge-aided team environment using comparable
techniques such as KPAT, the design should require minimal revisits and
corrective ECPs.

The use of the WBS, product categories, or other means enhances product
examination of the existing, comparative system, and genetic typing or
characterization of design attributes for the project. As the data for both
baseline (derivative, comparative) and the project (new, development, ECP)
is assimilated, analyzed, and formatted, it acquires dynamic information
attributes. These attributes may define areas such as surface features, hole
sizes, or corner radii. Using JCALS information technology, these attributes
are readily shared within the IPT. Added to this knowledge base is the input
from the domain expert, who in turn tailors the historical data through
analyses, such as trade studies or technology insertion, related to the
specific project and its features. Consequently, a combination of
manufacturing history and domain expertise engenders project design-to
information development, while helping evolve a corporate memory bank.
Information management, knowledge capture, and a dynamic system engineering
environment can result in predictable and supportable products.

Data dictionary terms are intended to be quantifiable with respect to
manufacturing events. For example, it should be possible to capture the
frequency, duration, and cost of a particular event such as anodize. The
shop work order may be a source of information that provides the frequency,
duration and cost characteristics of that event. Augmenting the data
dictionary, KPAT allows the data element directory to distribute, control,
and manage each design driver or PDTR with respect to the previously
mentioned information nodes.