CON FLOW - TU Clausthal · A pragmatic overview of Product Data Management This chapter gives a...

CON FLOWConcurrent Engineering Workflow

CONFLOW - a project funded by the Commission of the European Communities under the INCO-Copernicus programme (project no. 960243)

Partners:

• Technische Universität Clausthal, Germany• University of Wales Cardiff, United Kingdom• Mummert + Partner Unternehmensberatung AG, Hamburg, Germany• University of Rousse, Bulgaria• Technical University of Budapest, Hungary• ZITA Ltd, Rousse, Bulgaria• SAGE Ltd, Budapest, Hungary

Capabilities of the Product DataManagement System

Compiled by:

Dr. Tamás Márkus

Zoltán Szécsi

SAGE Ltd., Budapest

Deliverable No.: 2.2

Document No.: CONFLOW.97.10

Status: public

Capabilities of the Product Data Management SystemCON FLOW

CONFLOW.97.10 2

Preface ........................................................................................................................................ 4

1. A pragmatic overview of Product Data Management................................................................. 5

1.1 The technology................................................................................................................... 7

1.1.1 Data management........................................................................................................ 7

1.1.2 Process management ................................................................................................... 8

1.2 The recent level of PDM functional capabilities.................................................................. 10

1.2.1 User services............................................................................................................. 10

1.2.2 Utility services........................................................................................................... 11

1.3 The benefits of PDM systems ........................................................................................... 12

2 Analysis of PDM systems ........................................................................................................ 14

2.1 CMS (WOR95, WOR97) ............................................................................................... 14

2.1.1 Application Servers ................................................................................................... 15

2.1.2 Client Applications .................................................................................................... 18

2.1.3 Integrations ............................................................................................................... 19

2.1.5 CMS Three-Tiered Architecture................................................................................ 20

2.1.6 New features of CMS Release 7.0 ............................................................................ 21

2.2 Metaphase Series 2 (SDR97)........................................................................................... 22

2.2.1 Object Management Framework............................................................................... 23

2.2.2 Life Cycle Manager................................................................................................... 24

2.2.3 Product Structure Manager........................................................................................ 28

2.2.4 Part Family Manager ................................................................................................. 28

2.2.5 Advanced Product Configurator ................................................................................ 30

2.2.6 Change Control Manager .......................................................................................... 34

2.2.7 Image services........................................................................................................... 36

2.2.8 Integrator Toolkit ...................................................................................................... 37

2.2.9 Application Interfaces................................................................................................ 39

2.3 OPTEGRA (COM97) ......................................................................................................... 41

2.3.1 General new features and functions ............................................................................ 41

2.3.2 Information Management ........................................................................................... 42

2.3.3 Workflow Management............................................................................................. 42

2.3.4 Configuration Management ........................................................................................ 42


CONFLOW.97.10 3

2.3.5 New Optional Modules ............................................................................................. 43

2.3.6 Integration................................................................................................................. 44

2.4. Pro/PDM and Pro/INTRALINK..................................................................................... 46

2.4.1 Pro/PDM (PTC95) ................................................................................................... 46

2.4.2 Pro/INTRALINK (PTC97) ...................................................................................... 48

2.5 Basic PDM functionality of SAP R/3 (ROGO97).............................................................. 52

2.5.1 The SAP R/3 System................................................................................................ 52

2.5.2 Document Management............................................................................................. 52

2.5.3 Product Structure Management.................................................................................. 58

2.5.4 Classification Management......................................................................................... 66

2.6 SherpaWORKS97 (SHE97a) .......................................................................................... 74

Figure 2.27.Sherpa environment at Morton Automotive Co. (SHE97b)............................... 74

2.6.1 Sherpa/IPD (Integrated Product Development) .......................................................... 74

2.6.2 SherpaWORKS for Product Teams .......................................................................... 77

2.6.3 Sherpa/WEB............................................................................................................. 78

2.6.4 Sherpa/Explorer ........................................................................................................ 78

2.6.5 Sherpa PDM@Net ................................................................................................... 78

2.6.6 Sherpa/SFC (Foundation Class) ................................................................................ 80

2.6.7 Sherpa/Integrator Mentor Graphics............................................................................ 80

2.6.8 Sherpa/Integrator for Pro/ENGINEER ...................................................................... 81

2.6.9 Sherpa/View for Rosetta ........................................................................................... 81

2.6.10 Sherpa/REPORTS .................................................................................................. 83

2.7 WorkCenter (AUT97) ..................................................................................................... 85

2.7.1 General features ........................................................................................................ 85

2.7.2 WorkCenter 1.2a Features........................................................................................ 89

2.7.3 WorkCenter for the Web .......................................................................................... 91

2.7.4 Key benefits of WorkCenter...................................................................................... 92

3. Selection and implementation of a PDM system....................................................................... 93

3.1 Preparations for a PDM Project ....................................................................................... 93

3.2 Choosing the PDM system............................................................................................... 95

3.3 Introduction strategies....................................................................................................... 95

References................................................................................................................................. 97


CONFLOW.97.10 4

Preface

This work is Deliverable 2.2 of the Conflow project. The work gives an industrial practice oriented'pragmatic' overview on the basic PDM functionalities, then the capabilities of seven major PDMsystems are analyzed. The PDM functionalities of the SAP R/3 system are also discussed.

Finally practical tips are discussed for the systematic preparations for a PDM project and for theselection and implementation of a PDM system.


CONFLOW.97.10 5

1. A pragmatic overview of Product Data Management

This chapter gives a brief overview on the history of product data management and an industrialapplication oriented approach to the principles of PDM (GAS96, HEW96, MIL97, PHI96).

During the last decade, the manufacturing industry has made significant investments in usinginformation technologies (IT) to automate various processes in the product life cycle. This demandhas nurtured the rapid growth of the computer-aided design, manufacturing, engineering, andcomputer-integrated manufacturing (CAD/CAM/CAE/CIM) market since the late 1970s. However,this trend has also resulted in a phenomenon known as "Islands of Automation," which continues toplague the manufacturing industry. This phenomenon can be characterized by the following:

• Maintenance of incompatible computer systems which are developed and supported by differentorganizations for engineering design and product release.

• The need to retain separate views of the product structure using Engineering and ManufacturingBill of Materials (EBOM and MBOM).

• Generation of huge amount of product design data within a short period of time that makesmanual control of these data extremely difficult if not impossible.

• Proliferation and maintenance of translators between incompatible systems.

As a result of this phenomenon, the soaring maintenance cost for legacy systems constitutes a majorinformation systems (IS) expenditure for a typical manufacturing company. Consequently the ISfocus has started to shift from acquiring new and/or more advanced tools (i.e.,CAD/CAM/CAE/CIM applications) to managing data-sets generated by the existing tools.

Starting in the mid 1980s, a new class of applications called Engineering Data Management (EDM)emerged. EDM applications have a common purpose of providing configuration management toengineering data sets and the intent to start bridging the gaps between islands of automation.Configuration management in this sense represents a disciplined approach to define elements ofproduct engineering data, to control its change, and to track the changes made. EDM started out asa set of adjunct functions to the existing CAD/CAM/CAE tools packaged in the same application.But this inherently limited its use because only data generated by the CAD/CAM/CAE tools in thesame application can be managed. Subsequently, a type of standalone application, called ProductData Management (PDM), entered the market trying to alleviate this limitation.

Before to review the general capabilities, let us recall the definition of PDM from CIMData.

PDM is a technology that is used to manage:

• All product related information: any information that describes the product including informationsuch as part information, configurations, documents, CAD files, authorization information, etc.

• All processes related to the product: both definition and management of the processes includingauthorization and distribution information.

This relatively simple definition provides a broad view of the scope of PDM technology and itsapplication to industry. Single definition has not exist yet, the list of basic modules comprising a PDMsystem also varies (Table 1.1) The capabilities provided as part of PDM systems fall into fiveprimary user-oriented functional areas (and a number of utility-oriented areas): data vault and


CONFLOW.97.10 6

document management, process/workflow management, product structure management,classification and retrieval, and program and project management.

Table 1.1 Modules of a PDM system (PIMA96)

Although PDM is certainly not new, having its developmental roots 10-15 years ago, there havebeen many extensive changes and improvements to this technology over the last couple of years. Thechanges have been driven by, and have resulted in, the growing acceptance of PDM as an essentialtechnology for major industrial organizations. PDM has finally been recognized for what it is anenabling technology. PDM is used to enable the implementation of a variety of different managementprograms such as business process re-engineering, concurrent engineering, CALS, ISO certification,etc.

Recognizing PDM's role as an enabling technology, this also implies that the benefits resulting fromPDM implementations do not just result from the PDM technology, they result from the totalinitiative. Thus, PDM benefits are often seen in the form of the results of a 'concurrent engineering'implementation, or some other major program. Relative to this challenge, one of the big changes thathas occurred over the last one to two years has been the availability of real metrics - that is, theresults of PDM implementations.


CONFLOW.97.10 7

1.1 The technology

One of the typical problems is to maximize the time-to-market benefits of concurrent engineeringwhile maintaining control of the data and distributing it automatically to the people who need it andwhen they need it. The way PDM systems cope with this challenge is that master data is held onlyonce in a secure 'vault' where its integrity can be assured and all changes to it monitored, controlledand recorded.

Duplicate reference copies of the master data, on the other hand, can be distributed freely, to usersin various departments for design, analysis and approval. The new data is then released back into thevault. When a 'change' is made to data, what actually happens is that a modified copy of the data,signed and dated, is stored in the vault alongside the old data which remains in its original form aspermanent record. This is the simple principle behind more advanced PDM systems.

Figure 1.1 Functional view of a PDM system

1.1.1 Data management

Data management systems should be able to manage both attribute and documentary product data,as well as relationships between them, through a relational database system. With so much databeing generated, a technique to classify this information easily and quickly needs to be established.

Classification should be a fundamental capability of a PDM system. Information of similar typesshould be capable of being grouped together in named classes. More detailed classification would bepossible by using 'attributes' to describe the essential characteristics of each component in a givenclass.

Classification of components

Components are entered in the database under a variety of classes which suit the business needs.Classes themselves can be grouped together under convenient broad headings. This allows all thecompany's working stock of components to be organized in an easily traceable hierarchical networkstructure. Each part can be given its own set of attributes. Additionally, some systems allow to


CONFLOW.97.10 8

register that certain components are available with specific 'optional' attributes. This can be invaluablein controlling Bills Of Materials (BOMs).

Classification of documents

Documents relating to components and assemblies can be similarly classified. Each document canhave its set of attributes - part, number, author, date entered. And, at the same time relationshipsbetween documents and the components themselves can be maintained. So, for example, a dossierfor a specific 'bearing assembly' could be extracted, containing 2D drawings, solid models, and finiteelements analysis files.

PDM systems vary greatly in their classification capability. Some have none, others support theability to define a classification only at the time when the database is implemented. More recentPDM systems have provided a capability that can be defined and modified at will as the demands ofthe organization change.

Product structure

The third way product data can be accessed is by product structure. For any selected product, therelationship between its component assemblies and between the parts that make up these assembliesshould be maintained. This means that a complete Bill of Materials can be opened, includingdocuments and parts, either for the entire product or selected assemblies. One distinct advantage isthe ability to hold not just the physical relationships between parts in an assembly but also other kindsof structures; for instance, manufacturing, financial, maintenance or document relationships. So, it ispossible for specialist team members to see the product structured from their point of view.

Querying the data

There is a need to be able to 'get at' the components and assembly data by a variety of routes. Onecan move up and down a classification tree; pick the way through a product structure; simply call-upthe data needed by searching for it by name or part number, or search for groups of data byspecifying an attribute or combination of attributes.

1.1.2 Process management

Process management is controlling the way people create and modify data i.e. process managementaddresses the impact of tasks on data.

Process management systems normally have three broad functions:

1. They manage what happens to the data when someone works on it. ('Work Management'.)

2. They manage the flow of data between people. ('Workflow Management'.)

3. They keep track of all the events and movements that happen in functions 1 and 2 during thehistory of a project. ('Work History Management'.)

PDM systems generally vary widely in how they perform these functions.

Work management

The engineering objects go through hundreds of design changes during the course of development,each involving far-reaching modifications to the underlying engineering data.


CONFLOW.97.10 9

A PDM system offers solutions by acting as the engineer's working environment, capturing all newand changed data as it is generated, maintaining a record of which version it is, recalling it on demandand effectively keeping track of the engineer's every move.

When a design modification is carried more is required than just the original design and theEngineering Change Order (ECO). Many documents, files and forms may need to be referred to andother members of the design team involved, too. Current PDM systems cope with this requirementwith varying degrees of success. One approach is that which emulates paper-based processes byusing what are known as 'user packets'.

The packet allows the engineer to manage and modify several different master documentssimultaneously as well as providing various supporting documents for reference. This approach alsosupports the concurrent engineering principle. For example, although only one user can be workingon a 'master' design, team members working on the same project can be instantly notified that thereis an updated master design, and reference copies of it will be made available to them in their ownpackets. A given packet can be worked on only by the user to whom it is logged out, but its contentscan be looked at and copied by everybody with the necessary access permissions.

Workflow management

Packets have the advantage of making it easy for team members to share meaningful groups ofdocuments, but they are useful for another reason, too. They make it possible to move work aroundfrom department to department, or from individual to individual in logically organized bundles.

During the development of a product many thousands of parts may need to be designed. For eachpart, files need to be created, modified, viewed, checked and approved by many different peopleseveral times and each part may call for different development techniques and different types of data.The work on any of these master files will have a potential impact on other related files. Product datamanagement handles and keeps track all of these.

Most PDM systems allow the project leader to control the progress of the project via 'states' usingpre-determined 'triggers' and a routing list which may vary according to what type of organization ordevelopment project is involved. The way systems differ is in how much flexibility they permit withinthe framework discipline. The most rigid systems are based on procedures. Every individual or groupof individuals is made to represent a state in a procedure - 'Initiated', 'Submitted', 'Checked','Approved', 'Released'; a file or record can't move from one individual or group to the next withoutchanging states. Some systems make it possible to give the task an identity of its own, separate fromthe people working on it.

Most systems allow the up-to-date status of the entire task, with all supporting data, to be trackedand viewed by authorized individuals at all times. A packet represents one task in a productdevelopment project, which may consist of many thousands. Each packet follows its own routethrough the system but the relationship between packets also needs to be controlled.

The coordination of such a complex workflow needs the knowledge of the interdependencies of thetasks to match the way the individual project is structured. Some systems are not easy to customizein this way. Others have the ability to create a hierarchical relationship between files.

Work history management

Product data management systems keep comprehensive database records of the current state of theproject and they record the states the project has been through. Consequently they are a potentiallyvaluable source of audit trial data. The ability to perform regular process audits is a fundamental


CONFLOW.97.10 10

requirement for conformance to international quality management standards such as ISO 9000 seriesor EN29000.

Many times 'back-track' is needed to specific points in a project's development where a problemarose, or from which the designer can start a new line of development. Project history managementhandles this task.

Some systems record only the changes in ownership of documents, then ownership can be traced ata specific point in time, but not the modification itself. Others have the ability to record changes butmay do so as a series of 'snap-shots' taken only when a file changes 'state'. This can leave large gapsin workflow history as a user may have been making modifications to a design for several weekswithout any change to its state. Some systems provide an historic record which is like a 'movingpicture' by allowing the users to record changes to any selected system-defined level.

The level of historical tracking, as well as providing comprehensive auditing and permitting the activemonitoring of the individual performance are the key capabilities during time-critical projects.

1.2 The recent level of PDM functional capabilities

Functional capabilities fall into two basic categories - user and utility. The current state of thesecapabilities is as follows:

1.2.1 User services

Data / document management

Good support is provided for these basic capabilities. Vault management with versioned part-document/data relationships and solid user access authorizations are readily available. Distributedvaults are very common and can be accommodated by any system seriously focused on large scaleimplementations

Process/work flow management

Basic capabilities have been around for some years, but we are currently experiencing a majorimprovement in general support. The impact of specialized "work flow" packages and the gradualmerging of document focused suppliers is having a positive impact on developments. Graphical userinterfaces were delayed, but now we have experience the proliferation of this technology.

Product structure management

This area has undergone much change over the last years as suppliers focused on improving theircapabilities. Today, we use systems with more robust management features. Currently, a weaknessin some of the systems is that the management of configuration modifications is not integrated withchange management capabilities.

Classification

Most systems provide capabilities to define organization specific attributes for "objects" such asparts, and the to search / identify parts (or other objects) through these attributes. The best of thecommercial systems offer extensive capabilities to define and manage classification structures (suchas part families) and then attach specific objects (such as parts) to appropriate classes.


CONFLOW.97.10 11

Program management

This area has not yet been addressed by many commercial systems. The most frequent approach isan integration with some project management application.

1.2.2 Utility services

Communications

Capabilities to support communication within PDM systems are good, full support in this area is athand.

Data transport and translation

There are not many differences between the best systems in this area and it is generally wellsupported.

Image services

In the last two years these capabilities have become standard in many PDM implementations. MostPDM suppliers now offer image services themselves or in co-operation with third party imageservices suppliers.

Administration

Features for system tailoring (such as user interface or terminology modification) are now muchbetter supported and additional capabilities are expected. PDM related system managementcapabilities such as configuration specific archive and restore are not yet widely available, althoughthey are certainly available from some sources.

Web technology

One of the latest issues in PDM industry is the impact of web browsers. This technology is gettingattention, and is being recognized as a powerful way to access a broad range of data inmanufacturing enterprises. Web browsers being utilized with PDM applications are just modifiedversions of the ones used with the Internet's World Wide Web: including Netscape, Mosaic, andNavigator. But they are not so much being used to access the Internet as they are being directed atdata inside their own company. They are accessing the Intranet of interconnected computers within acompany.

The power of web browsers in PDM is that users can quickly and easily access many differentsources of data and display this information on the screen at the same time. This includes not onlydata from the PDM system, but also information from MRP, the shop floor, parts managementsystems, purchasing, finance, shipping, and legacy systems. Data displayed on these PDM browsersis not truly integrated, of course. In most cases, databases remain separate and may not be linked,associated, or validated in any way. However, it provides a way of consolidating this information ina single place for people who need it, and this is a first step in the process toward integration.

Every major PDM vendor now has a focused program to make browser technology part of theirproduct suites.


CONFLOW.97.10 12

PDM capability improves

Although there are still weaknesses, we must experience the improvements that have been made incommercial PDM systems over the last years and the additional improvements that are expectedover the coming near future. PDM systems are improving quickly and are becoming more capable ofsupporting production implementations.

1.3 The benefits of PDM systems

Reduced time-to-market

This is the major benefit of a PDM system. Three factors serve to place limits on the speed withwhich a product is brought to market. One is the time it takes to perform tasks, such as engineeringdesign, and tooling. Another is the time wasted between tasks. And the third is time lost in rework.

A PDM system can do much to reduce all these time limitations.

• It can speed up tasks by making data instantly available as it is needed.

• It supports concurrent task management.

• It allows authorized team members access to all relevant data, all the time, with the assurancethat it is always the latest version.

Improved design productivity

Product Data Management systems, when driving the appropriate tools, can significantly increase theproductivity of users. With a PDM system design process itself can be dramatically shortened.

Another factor is that designers should spend more time actually designing. Statistically a designengineer would spend as much as 25-30% of his time simply handling information; looking for it,retrieving it, waiting for copies of drawings, archiving new data. PDM removes this dead time almostentirely

A third major time saver is the elimination of the 'reinvented wheel' syndrome. The amount of timedesigners spend solving problems that have probably been solved before, is notorious. It is oftenconsidered quicker to do it again, than to track down design elements that could be re-used. With aPDM system, however, the identification, re-use and modification of existing similar designs shouldbecome routine.

Improved design and manufacturing accuracy

An important benefit of PDM systems is that everyone involved in a project is operating on the sameset of data which is always up to date. Working on a master file it is known that it is the only one;viewing a reference copy a replica of the latest master is used. So overlapping or inconsistent designsare eliminated - even when the project people are operating concurrently. This leads to far fewerinstances of design problems that only emerge at manufacturing or quality assurance, fewerengineering change orders (ECOs), more right-the-first-time designs and finally a faster path to themarketplace.


CONFLOW.97.10 13

Better use of creative team skills

Designers are often conservative in their approach to problem solving for no other reason than thetime for exploring alternative solutions is too long. The risks of spending excessive time on a radicallynew design approach which may not work would be unacceptable.

PDM opens up the creative process in three important ways:

• First, it keeps track of all the documents and test results relating to a given product change,minimizing design rework and potential design mistakes.

• Second, it reduces the risk of failure by sharing the risk with others and by making the dataavailable to the right people fast.

• Third, it encourages team problem solving by allowing individuals to bounce ideas off each otherusing the packet-transfer facility, knowing that all of them are looking at the same problem.

Comfortable to Use

Although PDM systems vary widely in their levels of user-friendliness, most set out to operate withinthe existing organizational structure of a product engineering operation, without major disruption. Thesystem should, in fact, make familiar tasks much more user-oriented than before. When users wish toview information on a PDM system, the application is loaded automatically, and then the document isloaded. In a conventional working environment, users would either have to be much more skilled ataccessing the information or be prepared to accept it in a much less flexible form.

Data integrity safeguarded

The single central vault concept ensures that, while data is immediately accessible to those who needit, all master documents and records of historical change remain absolutely accurate and secure.

Better control of projects

Product development projects are almost invariably late not because of bad planning but becausethey routinely go out of control. The volume of data generated by the project rapidly grows beyondthe scope of traditional project management techniques. The greater the competitive time pressures,the greater the scope for inconsistency, and likelihood of rework. PDM systems enable user to retaincontrol of the project by ensuring that the data on which it is based is firmly controlled. Productstructure, change management, configuration control and traceability are key benefits.

Better management of engineering change

A PDM system must allow creating and maintaining multiple revisions and versions of any design inthe database. This means that iterations on a design can be created without the danger that previousversions will be lost or accidentally erased. Every version and revision has to be 'signed' and 'dated',removing any ambiguity about current designs and providing a complete audit trail of changes.

A major step toward total quality management

By introducing a coherent set of audited processes to the product development cycle, a PDMsystem goes a long way towards establishing an environment for ISO9000 compliance and TotalQuality Management (TQM). Many of the fundamental principals of TQM, such as 'empowermentof the individual' to identify and solve problems are inherent in the PDM structure. The formalcontrols, checks, change management processes and defined responsibilities should also ensure thatthe PDM system contributes to the company's conformance with international quality standards.


CONFLOW.97.10 14

2 Analysis of PDM systems

The PDM market has been dramatically growing, many systems are available with varyingcomplexity of capabilities. The number of different system brand is well over 50.

In order to give a reasonable introduction into the world of these systems, in this chapter six (actuallyseven) PDM systems are discussed. The depth of analysis is heavily depending on the availableinformation, generally the sources of the supplier companies were used.

The systems are:

• CSM (Workgroup Technology)

• Metaphase (Metaphase Technology

• Optegra (Computervision)

• Pro/PDM and Pro/Intralink (Parametric Technology)

• Sherpa Works (Sherpa Systems)

• WorkCenter (Autodesk)

Because of the specific needs of the CONFLOW project, the PDM functionality of the SAP R/3system is of primary importance for the participating partners. The analysis of the SAP R/3 PDMcapabilities - Chapter 2.4 of this work- is an unchanged citation from (ROGO97).

The recent CONFLOW research of Technical University of Budapest (Deliverable 2.3) gives adetailed analysis of Workflow management, this functionality of SAP R/3 has not been discussed inthis work.

2.1 CMS (WOR95, WOR97)

The overview of Workgroup Technology's CMS PDM products family is based on the capabilitiesof Release 6.0, but the basic innovations of Release 7.0 (issued in April 1997) are also mentioned.


CONFLOW.97.10 15

Figure 2.1 CMS Family of Products

2.1.1 Application Servers

CMS/Server

The core of the CMS product family, CMS/Server provides comprehensive networked documentand release management, including vault management, version control, security, administration, andreporting.

Document Management

CMS manages the entire set of documents created during the product design and manufacturingprocesses. Files generated by the CAD, CAE, CAM and Technical Publishing applications can beeasily added from the user's desktop by using the intuitive CMS interface.Once in CMS, documents are available from any client using UNIX, Windows, Windows NT, orMac OS. Access to these documents is controlled by CMS security, which allows user to assign aunique set of permissions to each class of object.


CONFLOW.97.10 16

Figure 2.2 Product configuration in the CMS Desktop

Release Management

CMS release management provides a three-state model starting with work in progress. When userssubmit work for approval, the reviewers are notified, and the work is temporarily locked from furthermodification. Once approved, the configuration can not be changed without creating a newreversion. CMS supports configurations of part to part, document to document, and part todocument relationships.

Release management gives the ability to freeze all of the above configurations at the time of release.Users are then able to easily retrieve any of these released configurations.

Vault Management

The Vault Server manages location of all the files added to CMS. The user can distribute the VaultServer anywhere on the local or wide area network. A simple rules file determines in which vaultserver a file will be stored. Therefore files can be distribute files and among site locations to optimizenetwork file transfer rates.As an option, CMS allows storing the files managed by CMS in a compressed format. Differentcompression algorithms can be specified for each type of file.


CONFLOW.97.10 17

Database Options

CMS is designed to run on either Oracle or Sybase.Features:• Version control for all document types• Release management of product and document configurations• Auto launching of documents into preferred viewers• Intuitive interface from UNIX, Windows, Windows NT and MacOS clients• Supports process management through integrated workflow• Supports tight integration to popular applicationsBenefits:• Simple search and retrieval of documents from your desktop computer promoting design re-use• Complete accountability of all document modifications supporting ISO 9001 certifications• Protection from unauthorized change• Quick and easy on-line viewing of documents, reducing the need form time consuming and error

prone paper based information distribution• Retrieval of released configuration baselines enables concurrent engineering• Process optimization through workflow analysis• Synchronization of information between CMS and integrated applications

CMS/Replication Server

The CMS/Replication Server allows user to distribute read-only copies of files over the network forquick access. There are two primary uses for the CMS/Replication Server. If the users need to runCMS from multiple locations over a wide area network traffic can be minimized by replicating read-only files at each site. The replication server also provides quick access to reference files over a localarea network.Features:• Replication of files to remote locations.• Rules-based file replication.Benefits:• Provides extremely fast access to read-only files.• Minimizes traffic over wide area network.

CMS/Launch

CMS/Launch allows the user to register applications for any of the files which is managed in CMS,including word processing documents or spreadsheets on the user's Windows PC. CAD drawingscan be viewed in their native application, or a raster image in a viewing package. CMS/Launch alsoprovides a mechanism for running user's own programs or scripts to run against a fileFeatures:• Automatic recognition of files based on a user-editable rules file.• Simple registration of viewing applications.• Launching files into preferred viewers by file type.• Printing files by file type.


CONFLOW.97.10 18

Benefits:• Files can be viewed from any platform that runs a standard viewer.• Facilitates review and approval cycle.

CMS/Clients

CMS is able to run on all major platforms, including: CMS/Windows, CMS/MacOS, CMS/Motif,CMS/ASCII, CMS/NT.

2.1.2 Client Applications

CMS/Workflow

CMS/Workflow is a flexible process management application that allows the modeling of thebusiness processes for CMS- managed information. Documents can be routed through the user'sCMS-defined work flows to ensure that all personnel involved in the process are assigned to thecorrect task.Reports provide information about the status of all active workflows. The review of completed workflow statistics is also possible to identify problem areas.Features:• Simple in-basket metaphor.• Automatic routing of tasks and related documents with live status checks.• Electronic sign-off with audit trail.Benefits:• Ensures tasks and related documents reach the appropriate people at the right time.• Enables managers to monitor project status in real time.• Supports ISO 9001 certification and other regulatory compliance requirements.

CMS/DocuNet

CMS/DocuNet is an application that automatically and securely distributes CMS- controlledinformation over the Internet to remote sites or to World Wide Web servers. The files that aretargeted for remote sites are first converted to the format needed by the receiving location. After thefile is successfully translated, CMS/DocuNet decomposes the file into packets, encrypts them, andsends them to the destination over the Internet using standard e-mail. Once all packets are deliveredto the client site, the file is reassembled and confirmation is sent back to the source location, whichmaintains a log of the transaction.For data targeted for distribution to World Wide Web servers, CMS/DocuNet automaticallyconverts the files to HTML format and routes them either to a secure Web server inside the firewallor to a public Web server. In either case, access to CMS-controlled information is possible fromlow-cost Web browsers.Features:• Tamper-proof security based on the MD5 checksum and DES algorithms.• World Wide Web data management.


CONFLOW.97.10 19

Benefits:• Data distribution in minutes vs. days with traditional express mail.• Extends ISO 9001 certification out to supplier sites• Access to controlled information from low cost Web browsers.

Ability to get back to information which was on the Web server at a particular time.• Guaranteed data integrity through automatic detection and correction of transmission errors.

CMS/EZVue

CMS/EZVue is a CMS-integrated viewing application designed for instant usability. The interface isdesigned around three basic functions: finding the file in the database by using a basic query search,viewing the document (with panning and zooming capabilities), printing or plotting the document (withoptional stamping of attribute data).Features:• File formats supported: DXF, HPGL, IGES, CGM and PostScript.• Supported on UNIX workstations, PCs and Macs.Benefits:• Learn to use in minutes• Low cost access to CMS-controlled information• Eliminates the need for paper documents.

CMS/PreviewMark-up

The CMS/Preview Mark-up application links CAD drawing files in CMS with overlay/redline filescreated with Preview from Rosetta Technology. CMS/Preview Mark-up can be launched either as astand-alone application or from within CMS, and automatically retrieves associated overlay/redlinefiles when the drawing file is displayed.Features:• Tight integration between CMS and Preview, from Rosetta Technology.• Automatic linking of CAD drawing files with overlay/redline files.Benefits:• Supports a paperless work flow environment.• Ensures that overlay/redline files are current and accurate.

2.1.3 Integrations

CMS/Pro

CMS/Pro is an integration with Pro/ENGINEER. All Pro/ENGINEER configurations are managedby CMS with the automatic extraction of relationships and attributes.eatures:• Supports all Pro/ENGINEER structures.• Supports simplified reps.• Manages entire design release process.


CONFLOW.97.10 20

• Views Pro/ENGINEER data on PCs and Macs.Benefits:• Maintains complete integrity of• Pro/ENGINEER configurations.• Enables concurrent engineering and the master model concept.• Saves time retrieving released baselines to support ECO process.

CMS for Mentor Graphics

CMS for Mentor Graphics is an integration with Design Architect and BoardStation from MentorGraphics Corporation. It manages in-progress work for schematic capture and board layoutapplications.Features:• Integrated with Mentor Graphic's Falcon Framework.• Automatic building of design configurations for PCB, schematic, simulation, and viewables.• Automatic transfer of Mentor Graphics properties.Benefits:• Simplifies the Mentor Graphics design configuration seen by the user.• Provides database-wide parametric searches promoting design reuse.• Reduces non value-added engineering.

2.1.4 Programmatic Interfaces

CMS/API

CMS/API is a C-based programmatic interface that allows to access CMS user functions as part ofa client program. For example, CMS/API programs can batch load large amounts of data,automatically update information in CMS, based on given events, export CMS information to otherapplications and create simple interfaces for limited access users.

2.1.5 CMS Three-Tiered Architecture

The three tiered architecture is based on three Data Servers: the Relational Database Server, whichruns on either Oracle or Sybase, stores all the object data, including attributes, associations andpermissions. The Vault Server is a socket-level file repository that stores all versions of the physicalfiles added to CMS. It can be distributed over local and wide area networks. The optionalReplication Server replicates files at remote locations in order to reduce network traffic.The Application Server is the PDM engine that connects the client interfaces to the data servers.The server can run from all of the supported UNIX platforms.


CONFLOW.97.10 21

The Client Applications are programs that supply you with a simple user interface on your platformof choice. They connect to the application server via a TCP/IP connection.

Figure 2.3 CMS architecture

2.1.6 New features of CMS Release 7.0

CMS 7.0 is based on Collaborative Work Management, a patent-pending technology that allowspeople to effectively collaborate during all phases of product development; including the early pre-release stages, which product data management (PDM) and workflow providers have largelyignored.

This technology provides users with real time visibility into the state of completion of deliverables aswell any dependencies a deliverable may have on others. This is accomplished through a tightcoupling of document and process management by embedding the process in the deliverable. Inother words, a deliverable becomes "intelligent" and "knows" what steps it must follow during itslifecycle.

CMS 7.0 is designed to specifically address the process-driven requirements in implementing ISO9000, QS-9000, US FDA Quality System Regulations and European CE Mark Medical DeviceDirectives. It accomplishes this by modeling and institutionalizing processes, maintaining audit trailsand keeping process and product information tightly coupled.


CONFLOW.97.10 22

Key Features

Stage Based Process Modeling: CMS 7.0 focuses on managing project and product deliverables.Each deliverable has process stages and control gates that define its process throughout its lifecycle.For example a CAD drawing may have three stages: create, review and release, which are userdefinable. In CMS 7.0 these stages are built into the definition of the drawing and dictate the processit will follow.

Process Synchronization: CMS 7.0 allows the user to define rules that prevent a process fromproceeding to the next stage if certain predefined conditions are not met, enabling downstream workto be based on accurate and complete information.

Real Time Project Tracking: CMS 7.0 is designed to provide visibility to latest status of any or allproject deliverables. As work on a particular deliverable is completed it is moved forward to thenext stage of its process. CMS 7.0 keeps track of this progress as it occurs, including anyunanticipated ad-hoc activities. As a result it is possible for anyone working on the project to quicklydetermine who is working on what, where everything is located and when work was completed.Project managers can quickly scan the project deliverables and determine if the project is onschedule and if not, what is holding it up. Regulatory compliance managers have a complete audittrail of all work actually done, which can be used as verifiable evidence for audits.

2.2 Metaphase Series 2 (SDR97)

Metaphase Series 2 of ParametricTechnology is an enterprise-level product data management(PDM) system with functionality in all major application areas:• Product Data Management

• Document Management and Documentation Control

• Configuration Management

• Imaging/Workflow

• Review/Approval Cycles

• Work Assignments

• Business Process Re-Engineering

• Change Impact Analysis

• Change Control

• Regulatory Compliance

• ISO 9000 Quality Assurance

• CALS/CITIS

• MIL STD 973

• Concurrent Engineering

• Application Encapsulation


CONFLOW.97.10 23

The common basic features include as follows:

Advanced architecture. Metaphase Series 2 features a modular software architecture thatcombines an advanced object-oriented environment with a relational data base commonly used tosupport production enterprise-level applications. Metaphase Series 2 manages all data, relationshipsand processes of objects so that users can interact with the software intuitively and manage the PDMsystem easily. The client-server design allows Metaphase Series 2 to be easily implemented amongdistributed engineering and manufacturing locations, across a wide range of hardware platforms andsoftware applications.

Ease-of-use. A graphical user interface enables users to define, locate and use data efficiently, whilegraphical browsers and feedback tools allow them to navigate through complex data models.

Complete functionality Metaphase Series 2 provides a complete range of integrated applications,extensive facilities for advanced operations such as managing workflow, product structures,classification, application encapsulation, configuration management and imaging.

Open and flexible: Metaphase Series 2 has a powerful open architecture, application programminginterfaces (APIs) and an integrator toolkit which makes the system easy to customize and adapt tosite-specific requirements. Metaphase APIs allow companies to tailor the PDM systems to theirunique operations and encapsulate existing software applications. Manufacturers can integrate datafrom CAE/CAD/CAM software, business applications, MRP packages, document management andimaging systems and customer-proprietary programs used in the product development process. Asusers extend the system to meet their own unique requirements, compatibility with the rest of theMetaphase Series 2 is maintained.

2.2.1 Object Management Framework

This software is the OM framework, creating a graphical computing environment to help userswithin the Object Management Framework

OMF is designed to bring together the tools and information that professionals require to completetheir mission-critical activities on a daily basis. This framework provides transparent, network-wideaccess to information so that user can share and reuse this valuable corporate resource.Within OMF, each document or piece of information is represented as an object -- a self-containedunit of data that contains additional pieces of information that describe it and control its behavior.This structure provides users with intuitive access to the system; administrators with increasedflexibility; and customizers with more efficient tools and methods for their work.All objects - applications, data files, data base entries, users, and other types of administrative datamanaged within the framework - are represented by icons and can be manipulated by simple point-and-click actions. Specifically designed to provide user with a pleasant, productive environment andenhance communication and sharing of information, the framework allows user to quickly locate andaccess the data needed.The framework also provides critical services to users. Control functions such as check-in/check-outensure that all information is current and accurate. Histories and audit trails allow managers tomonitor business processes and ensure that company policies are followed. Flexible features allow


CONFLOW.97.10 24

the enterprise and its constituent organizations to configure the system according to their specificbusiness needs.The use of objects as a method for managing corporate information will produce benefits. Managerswill have increased access to information and more control over critical business processes.Administrators or customizers will be able to quickly make changes to match the company's growthand evolving needs.

Enterprise-Wide Implementation FeaturesAdvanced Architecture: OMF combines an object-oriented architecture with the performance of arelational data base commonly used to support enterprise-level, production applications. Metaphasemanages objects, all data, relationships and processes, and the user interact with the softwareintuitively and manage the PDM system easily.Rules Base: This technology is an engine which allows all rules which drive the system to beestablished by the customer rather than "hard-coded" into the system. Rules are used for several keypurposes:• Security rules control who can access objects and methods (actions) against those objects• Notification rules control who gets notified when various events occur within the system• Data organization rules control the physical organization of files placed into a "logical" vault.In addition, through a dynamic data dictionary the user can easily define and modify object attributeinformation.Fully Distributed System: A fully distributed system is necessary for multi-site PDMimplementations. OMF supports a distribution model which not only supports the distribution ofphysical files, but also allows multiple PDM data bases to coexist and inter-operate in a peer-to-peerfashion.

2.2.2 Life Cycle Manager

LCM software allows the user to manage the product data. Not only does it keep a historical recordof product changes from initial release to obsolescence, this module also manages the workflow bycapturing and enforcing the detailed processes which must be completed as the product movesthrough development.Life Cycle Manager (LCM) software is a comprehensive tool created to address the electronicrouting and workflow needs of business in today's competitive environment. LCM uses an advancedapproach to create and execute workflows that allow for the management of an object from conceptto obsolescence. The entire life cycle of the object can be represented using a single, comprehensivelife cycle definition that maintains continuity; or through a series of focused life cycles that addressspecific business problems.

Managing Change to Product DataA critical aspect of configuration management is the management of changes that are performedagainst the product structure and the supporting product definition information. During the initialphases of new product design, it is likely that critical design parameters are changing on a daily basis.At this time, change control is an informal process. The engineer who is in charge of the design may


CONFLOW.97.10 25

hold sole responsibility for the decision to incorporate any changes. At these early stages, there istypically no impact to other products or processes as changes are incorporated.However, as the design progresses and other people and processes become dependent on thedesign information, more formal change control procedures become a strict necessity to preserve theintegrity and productivity of the overall process. As part of a defined "Life Cycle," the LCM canenforce customer-defined processes which are used to move objects through the various stages oftheir overall life cycle. LCM ensures that objects get promoted to the next customer-specified state(e.g., "Class B" or "Pre-Production") or are automatically baselined so that they become subject toformal revision and change control procedures. LCM allows the customer to define rules whichspecify workflow, state changes, and security as part of a life cycle definition.When changes are made to baselined product definition data, LCM provides online forms whichmay be used to identify the proposed change, the reason for the change, impact of the change, orany other information that the customer desires. Metaphase provides user with easy customizationtools to design own form objects and object relationships (ECRs, ECOs, FCOs, waivers,deviations, etc.) to enable change control per established customer guidelines.Once a change has been requested, LCM provides workflow management mechanisms which willroute the proposed change past any affected parties to solicit their approval. LCM processesexamine rules to determine who is affected, what the workflow is in terms of parallel and serialreview steps, and voting rules required to approve the change (e.g., majority approval, unanimousapproval, etc.). Additionally, ad hoc routing provides the flexibility for users to construct informalroutings for work objects to share their own set of users. Events within an LCM process or life cycleconsult customer-specified rules and generate automatic notification via e-mail to interested parties.

Life Cycle Building BlocksThe first step to improving operational effectiveness is understanding the business needs anddeveloping efficient processes to support them. LCM gives each business an array of tools withwhich to model these processes, link them together and automate them, and provide a permanentonline record of information about them so that they can be audited and enforced. Each activitydefined by the life cycle can be verified through an online record of transaction and the businessobjects that have passed through the life cycle.A user with the authority to create or alter life cycles and their life cycle components can access theLife Cycle Administration browser from the home browser. Working within LCM, the first step increating a life cycle is creating the underlying processes that will make up the life cycle. Oncecreated, processes can be modified or otherwise manipulated from the action menu of the Life CycleAdministration browser and combined to form life cycles. Processes and all other components of lifecycles are all tracked as objects within the Object Management.Graphic tools make possible to define workflow processes and define and connect tools using theease of drag and drop. Once objects have been submitted to these processes, the user is able tographically view the position of the object in the cycle and double-click for more details regardingany step.

ProcessesProcesses are the building blocks of any life cycle. The Life Cycle Manager provides four basictypes of processes that can be developed and combined to fit any business situation:


CONFLOW.97.10 26

• review/approval• work assignment• condition• automaticEach type of process can be created from scratch, copied from an existing process, or altered fromthe Life Cycle Administrator window. Processes of all types may be reused an unlimited number oftimes.The administrator can control who is allowed to submit objects to a life cycle and what types ofobjects may be submitted. For example, the administrator may specify that only members of aparticular department can submit a particular type of object to a specific life cycle. When combinedwith the enterprise rule processor that is part of OMF, these controls become quite powerful. Forexample, only specifications that have a state of working or rejected will be allowed to go throughthe specification review process.A variety of parameters are used to define the four types of processes described below. Theseparameters will help managers to define the exact process that will best serve their business model,and are described in some detail.Review/Approval Processes are used whenever an object must be routed to one or more peoplefor review or approval purposes. The objective of such a process is generally to gather concurrenceon the content of an object or to fulfill the requirement that an authorized manager has approved anobject. Review/approval processes may be defined with either serial or parallel steps, or acombination of the two. The administrator may also select voting rules and a number of otherparameters to develop the appropriate process to address each business problem.Assignment Processes are used to route an object to a particular participant in the life cycle toperform a specific task, such as conducting a feasibility study or creating a conceptual model of aproposed product. The assignment portion of a life cycle is often used in conjunction with projectmanagement software to "push" projects through their milestones with an eye toward the critical path.Like other types of processes, assignment processes maintain full documentation of their execution.Condition Processes are processes that return either a true or false value (based on an object'sattributes) and are used as a branch between related processes. The conditional process allows theadministrator to create options at any given step in a life cycle, depending on the outcome of aprevious process, the characteristics of a particular object, or business rules.Automatic Processes execute within Metaphase Series 2. Each automatic process may access aninternal system function, send a message to an external system such as an outside data base, orautomate the interaction between Metaphase Series 2 and other applications. Processes of this typemay be used in a variety of ways to enhance the effectiveness of business processes being modeledusing LCM. LCM includes a variety of options, such as branching, that allow one workflow toaddress many scenarios, based on site-defined conditions.

Process ParametersEach of the four types of processes is defined by a set of parameters, some required and someoptional. By combining these parameters, the administrator can shape the process to suit eachbusiness situation. The most commonly used parameters are detailed below.Participants: In most implementations, every user of the Metaphase suite will be a participant in oneprocess or another. Only review/approval and assignment processes truly have participants, since


CONFLOW.97.10 27

they are the only types of processes requiring human interaction. Each instance of these processescan involve any number and combination of users as participants. Participants may be defined asgroups or individuals and assigned roles as necessary.Each participant in a review/approval or assignment process is given one or more tasks in theprocess. Assignments have been flexibly implemented so that they can serve as logical place holdersfor different participants in different situations. In a review/approval Assignments: process,assignments are focused to support the timely execution of well-defined, repetitive workflows. In awork assignment process, tasks are open-ended to support a wide range of tasks and address amore dynamic set of one-of-a-kind activities.Comments: Each participant may offer comments on items as they move through each process. Forexample, after rejecting an object, the participant will probably want to cite the reason for therejection so that the object can be sent back to an earlier participant and the object can be correctedto meet the approval criteria.Calendars: Each process may be assigned a calendar which reflects the corporate work schedule.Calendars are used to ensure that processes are executed in a timely fashion. Administrators canassign a time limit to individual steps in a process and then define an alternate action if the time limitexpires prior to the completion of the step.Electronic Sign-off: For approval processes, the administrator can designate participants who havesignatory responsibility for an object's approval. Electronic sign-off provides a record that theparticipant has indeed reviewed the object or its contents and is satisfied that the object has met allcriteria for it to move on to the next stage in its life cycle.Voting Rules: For each review/approval process, the administrator can designate a set of formalvoting rules that describe how many approvals are necessary for the object to move to the nextstage, or under what conditions participation is expected. The administrator may define whether ornot a given reviewer or set of reviewers are required to vote on the object. Additionally, theadministrator may require that an object complete the review process, even though it has beenapproved or rejected according to the formal rules that have been established.Vault: An important protection in any workflow system is that the baseline information remainunchanged while it is in a process. LCM allows the administrator to designate a secure vault for allobjects in process. At the administrator's discretion certain users or groups may be allowed writepermission to objects, if appropriate, as in the case of a work assignment process.State: As an object completes each process in its life cycle, a descriptor called "state" is used tosignify that it has met certain criteria or that certain events have transpired. If the object is a project,for example, it may be assigned a state of planned. Once planning has been completed and theproject plan is being electronically routed for review, its state would change to in review. As projectmilestones are reached, individual tasks in the process might be assigned the state completed, and soon until the project has been finished. The use of state in this manner provides very useful informationfor those who need to track project progress and assure completion by a given deadline. State mayalso be used to control access to objects and as a mechanism for using condition processes.Notifications: As events in a process or life cycle transpire, there may be a need to notify variousparticipants or others in the organization regarding them. LCM provides an easy-touse facility forthe administrator to set up notification schemes using e-mail or a built-in notes facility.


CONFLOW.97.10 28

ResultsImplementation of the Life Cycle Manager results productivity improvements for entire organizationsbecause cooperative processes such as reviews become a natural part of a routine. In addition, theautomatic enforcement of policies and rules ensure consistent results. Online records kept by the LifeCycle Manager provide verification and accountability at all organization levels.

2.2.3 Product Structure Manager

In the very early phases of new product design, engineers begin the design by sketching out astructure for the product which identifies the major components and systems that will combine tocreate the desired product. For each component, existing standard parts and previously designedcustom parts must be evaluated for their ability to provide the necessary function. In those cases forwhich no existing alternative can be identified, the engineer must specify that new parts should becreated, and the details of the structure begin to emerge.Product Structure Manager (PSM) software provides the mechanism to capture and manage as-designed product structures with ease. PSM allows for the creation and re-use of unlimited numbersof parts and assemblies, to provide for many different variations of a basic structure or the creationof complex, one-of-a-kind structures. Product structure information can be captured fromapplication sessions automatically or is easily loaded via the powerful user interface. The intuitivegraphical object browsers of Metaphase Series 2 provide a simple mechanism for viewing andmanipulating product structures.

Managing Product Definition DataBeyond the structure of the product, there is a wealth of additional information that is used to defineand support each component and structure. For each new part to be, engineers need to createmodels and designs which provide adequate description of the parts to allow for their subsequentfabrication and assembly. Existing parts may be supplied with their own set of descriptive informationand files.The Object Management Framework creates environment for the management of product definitiondata. This system allows users to create, store, relate, locate, and use electronic and hard copyproduct information. Information may be in the form of "data objects" or files, or may be in the formof "business objects" such as engineering change orders. All usage of data and business objects issubject to the rules of the system which are established by the system administrator. Via integrationto the applications that create the data, much of the relevant information about the data can becaptured automatically.When coupled with PSM mechanisms for managing the EBOM, the system has the capability to notonly manage the product structure but to associate the appropriate supporting information to eachpart component. The combination of the "as-designed" structure and all supporting information formsthe initial configuration of the product. Such structures are typically depicted in graphical form.

2.2.4 Part Family Manager

As manufacturers move to shorten design cycles and lower overall production costs by implementingProduct Data Management, a logical place to look for efficiencies is in the area of part family


CONFLOW.97.10 29

management. Companies need a way to lower design and manufacturing costs by improving theirusers' chances of finding the parts that they need for their designs, thereby promoting the reuse ofexisting parts. To do this, sites need a way to group together parts that have a similar design orfunction. The Part Family Manager (PFM) module lets companies group parts into families andspecify values for the characteristics associated with that part family. As a result, designers will beable to more quickly find parts that meet the requirements of their designs.

Extending Object and Class DefinitionThe Metaphase PFM module extends the basic Metaphase object and class definition by providingseveral new item and relation classes enabling companies to build part family hierarchies and assignparts to those families.Families are organized in a hierarchical fashion, meaning that a family consists of sub-families. Afamily that has sub-families is called a "Branch Family," otherwise, it is called a "Leaf Family." ThePFM Family-to-Family relation links branch family items with their sub-families. The Family-to-Family relation is one-to-many. Branch families have zero, one or many sub-families. A sub-familyhas one and only one parent family.The PFM Family-to-Part relation allows users to assign parts to a part family. The Family-to-Partrelation is many-to-many. Families may have zero, one, or many parts; and parts may belong to zero,one, or many families.Each family item in the data base is associated with its own Family-to-Part relation class. An attributeof the family object identifies the corresponding Family-to-Part relation class. Thus, a family item"knows" the type of relation that it needs to construct when a user assigns a part to it.To add a part to a part family, the user simply drops a Part icon (or a Part Master icon) onto aFamily icon. The system displays a dialog box allowing the user to enter the necessary part familycharacteristic information.

Simplifying Part Family ManagementCompanies have probably identified many part families that they use. It would not be uncommon fora site to define several hundred or even a few thousand part families. To simplify this managementtask, the PFM includes features that facilitate and simplify the process of setting up a part family.PFM supplies a utility that creates the appropriate Family items and Family-to-Family relations in thedata base given the part family specifications provided by a customizer using MODeL (MetaphaseObject Definition Language) statements. This utility not only eliminates what would appear asredundant work to the PFM customizer, but it also ensures that the part family definitions stored inthe data base are in sync with those provided in MODeL.PFM methods use dialog boxes and browsers that determine at run time the part family informationthat needs to be presented to the user. As a result, customizers need not define static dialog boxesand browsers for each of their Family-to-Part relation classes. Since the number of dialog boxes andbrowser could have run into the thousands, this feature not only reduces the size of the MODeL filebut it also eliminates some long and tedious customization tasks.


CONFLOW.97.10 30

2.2.5 Advanced Product Configurator

Configuration management is one of the most difficult challenges facing industry today.The creation and maintenance of product configurations and their related supporting documents haslong been a critical issue for aerospace and defense contractors and many discrete manufacturers,but it has also become a key concern for all those who participate in regulated industries:telecommunication services, utilities, transportation, chemical, pharmaceutical, health care, andmedical devices.Companies are realizing that the continued introduction of new products, coupled with the ongoingevolution of existing products, results in an information management burden. They struggle to dealwith issues regarding the management of product configurations (and related documentation) that areunder development and delivered to the field. The result can be a situation in which it is nearlyimpossible to determine the correct component parts, the correct versions of each component, andthe correct supporting information required to complete individual manufacturing and maintenancetasks.The Metaphase software application suite contains many features which address problems related tomanaging evolving product configurations. In addition to supporting object management featuresadded throughout the application suite, Metaphase contains two modules known as the ProductStructure Manager (PSM) and the Advanced Product Configurator (APC) to specifically addressconfiguration issues. The enhanced process and program management capabilities found in the LifeCycle Manager, also assist in providing the only true end-to-end configuration management solutionavailable.In the very early phases of new product design, engineers begin the design by sketching out astructure for the product which identifies the major components and systems that will combine tocreate the desired product. The PSM supports this activity.As the product definition begins to solidify within engineering, the manufacturing engineers begin theprocess of production planning during which changes to the structure may be incorporated tofacilitate production. The APC has several features to support this phase of product development.

View ManagementManufacturing engineers must consider additional information when planning how to manufacture theproduct; examples include manufacturing capabilities, physical assembly possibilities, and theavailability of parts. When this new information is integrated into the design, the result can be adifferent view of the structure of the product. The same piece part components are used, but theirstructure may be different.The Advanced Product Configurator provides the ability to derive a new view (e.g., "as-planned")from an existing structure (e.g., "as-designed"), and then to make modifications to the new view thatare view-dependent. Modifications which are made to links in the structure that are not deemed tobe view-dependent will affect both views. It is possible to derive additional views either from theinitial view, or from views which were subsequently derived from it.Any view-independent changes that are performed to the structure in the base view are propagatedautomatically to any other views which have been derived directly or indirectly from the base view.View-dependent changes are not propagated. Changes performed on a derived view do notpropagate to views from which it was directly or indirectly derived.


CONFLOW.97.10 31

Effectivity ManagementAnother important aspect of production planning is deciding when to "roll in" changes to variousparts which are used within the structure of the product. When engineers design an assembly, theywill specify the component parts whose characteristics satisfy the form, fit, and function requirementsof the design. However, several versions of each component part may exist--each of whichinterchangeably matches the requirements of the design. It becomes a manufacturing planning activityto determine which of the component parts are "effective" or appropriate for a given time or productinstance.The methodology for planning which revision of each component should be used (e.g., which revisionis "effective") for any given instance of the product varies by company and by product type, butrepresents the real beginnings of the configuration management challenge. Effectivity planning may bedone in various fashions, with "revision level effectivity," "effectivity by date," and "effectivity by serialnumber" being the most common.

Revision-Level EffectivityFrom a product structure modeling standpoint, Metaphase recognizes "part item" and "part revision"concepts. During the initial or conceptual structuring of the product, Metaphase Series 2 allows theuser to specify the product structure without having to specifically identify which component revisionswill be used at each level.Links which connect assemblies to components to form product structures actually connect acomponent part revision to a component part item. Then, effectivity information can be supplied toidentify the conditions for determination of the effectivity of each component part revision. Thiscreates a situation in which the structure of the product may vary greatly depending on the effectivitycontext in which the structure is examined.Given an effectivity context which identifies the date or serial number in question, the APC is able toreconstruct the desired structure by determining the appropriate part revisions which are effective inthe given context. Once the appropriate part revision is identified, the structure can be traversed tothe next level, where the same decision logic may be repeated. Obviously, the structure changes asthe navigation context changes.

Effectivity by DateDate effectivity is useful when several interchangeable revisions have been made to a part over time.

Effectivity by UnitIn addition to effectivity by date, the APC supports "effectivity by unit" (e.g., "effectivity by lot" or"effectivity by serial number"). This type of effectivity allows the system to maintain and reconstruct aconfiguration that was utilized in a certain identified instance of the product such as a specific lot or aspecific serial number.The APC stores this effectivity information as attributes of links and also as attributes of parts in thecase of serialized parts such as end items or configurable items. The attribute on the link objectcontains a reference to the end item (which may also be a Configurable Item), to the beginning unitnumber, and to the final unit number (may be open-ended). It is pos-sible to connect the componentto the assembly with multiple parallel links which indicate that the component is effective for morethan one range of assembly unit numbers.


CONFLOW.97.10 32

Part SubstitutionIn many products, it is acceptable to replace certain components with other parts that adequatelyaddress the requirements for form, fit, and function. For example, during manufacturing planning itmay be decided that certain similar components may be used instead of those which were originallyspecified by the engineering designs. In some cases, certain parts may vary from one country toanother to accommodate requirements for local part content. In other cases, parts may be replacedsimply because a less expensive alternative is found which adequately performs the required service.The APC supports concepts such as "substitute parts" and "alternate parts."

Alternate PartsWhen a certain part can replace a given part in any assembly which utilizes the given part, that part isknown as an alternate part. The APC identifies alternate parts by forging a relationship between theoriginal part item object and the alternate part item object which may legally act as its replacement.

Substitute PartsWhen a certain part can replace a given part, but only in a particular assembly which utilizes the givenpart, that part is known as a substitute part. The APC identifies substitute parts by forging arelationship between the link from the specific assembly to the original part item object and thesubstitute part item object which may legally act as its replacement.

OptionsWhen products are configured, it is typical that certain components may be optionally added orremoved at the customer's request. The core set of components typically represents some type ofgeneric product configuration from which a customer-specific configuration may be derived fordelivery to customers. In the bicycle example, the basic configuration of the product might notinclude fenders, while an optional configuration of the bicycle might incorporate such features.From a configuration management standpoint, there are two challenges to the use of options withinproduct structures. The first challenge is to adequately communicate which valid options exist toassist in the process of configuring the product to the customer's needs. The second challenge is tobe able to produce the exact configuration of components that should be assembled to create theexact product which addresses the customer's needs.Options are managed as a set of quantity differences that may affect the product structure at multiplelocations. Each set of quantity differences which are applied together is given a name which becomesthe name of the option. Links to parts which are optional within the generic structure may be includedin the definition of the generic structure, but their quantity is set to zero. When an option condition isapplied to the structure, the option condition may cause quantity changes to various links at variouslevels throughout the structure.

Structure Creation and ManipulationThe APC provides extensive capabilities to create and modify structures via direct manipulation ofpart icons. For example, to create an assembly, the user need only to select icons which representcomponent parts and drop those components on to the desired assembly via the mouse. Drag-and-drop manipulation is the primary user interface mechanism for constructing new structures ("build-up"), for modifying structures ("tear-down"), for modifying derived structure views, for associating


CONFLOW.97.10 33

substitute and alternate parts, for associating parts with suppliers, and for associating parts with partfamilies. Actions which are valid to be performed against a part may be accessed via context-sensitive pull-down menus. Viewing the detailed information regarding a part is done via pop-updialog boxes.

Configuration ContextThe APC provides the ability to reconstruct specific configurations such as those required to addressthese questions:• What configuration of parts comprises product Nxyz• What configuration of parts went into product built on yyyy-mm-dd• What is the correct configuration for the next product on the line?• What is the current released configuration for the tail assembly?• What was the original configuration released by engineering?• What is the "latest and greatest" configuration of the engineering design?• Is the manufacturing configuration functionally equivalent to the engineering design?• When should we roll in this change?• What parts were affected by this change?• What configuration did we actually ship to the customer?

To do this, the APC performs product structure manipulation, reconstruction, and display within a"configuration context" which has been established by the user. Elements of the configuration contextmay include specification of the:• Configurable item of interest.• Effectivity context-either by date, by unit, or by revision.• View context.• Option context.• Life cycle context.• Alternate and substitute context.

All manipulation and navigation of structures via the object browser is conducted within the confinesof an established configuration context. For example, the configuration context is established by theuser prior to the construction of an assembly, such that the correct effectivity, view, and optioninformation can be added to structure link objects as they are created. By varying the configurationcontext, the user can use the object browser to quickly seek answers to the types of questions posedabove. The configuration context is clearly shown to the user to eliminate any question as to theconfiguration being displayed. Users may retain the given configuration context from one session tothe next.


CONFLOW.97.10 34

2.2.6 Change Control Manager

The product development process is never really finished. From the time a new product isconceived, until it is no longer supported in the field, the process of change is on-going. Before thefirst production unit is shipped, there will typically be an engineering change under consideration. It isevident that the paper based systems of the past are not sufficient to control product changesgenerated in an electronic design environment. Without a corresponding electronic changemanagement system, the process will rapidly run out of control, causing larger problems as designmodifications pass through manufacturing to customers.

Managing Engineering ChangeEngineering release and change systems implemented using paper forms and interoffice mail areinefficient and slow. The sequence of events is often interrupted when large numbers of changesaccumulate on one person's desk or when key people are not available. Without an electronictracking system, no one knows where to find a specific change without tracking it by number fromperson to person. Often there are multiple changes for the same component progressing through thesystem at the same time, causing more confusion and delays. The effects of a change may have anegative impact on other parts or products which is not foreseen because complete information is notavailable. After the change is implemented, the paper system has no convenient method to recreatethe analysis which resulted in the change. Much of the input to design and manufacturing decisions isscattered throughout the company in paper files, or lost. The loss of supporting data makes it morelikely that a change back to the original configuration will be proposed in the future, requiring theengineering analysis to be performed a second time. The net result is that updating the documentationis often more costly than the change itself.Change Control Manager has been designed to takes advantage of the electronic product datamodel, and the capabilities of other Metaphase software tools, to create electronic engineeringrelease and change processes. These electronic processes capture the company's best engineeringpractices without the inefficiencies of inherent to paper-based change systems. In addition, LifeCycle Manager (LCManagement System) expedites the approval process electronically, allowingparallel processing of change orders.

Metaphase Enabled Change ControlThe general description of a change process using Metaphase Series 2 has five basic steps asfollows:• Create a Change Proposal• Create a Work Order• Write Specific Work Instructions• Implement the Changes• Obtain Release ApprovalThis sequence of events holds true regardless of the nature of the change being implemented anddescribes the operating philosophy behind the Change Control Manager.A Change proposal is usually either a request for an enhancement to the product or a description ofa defect. In either case, the engineering change proposal includes a description of the proposed


CONFLOW.97.10 35

change proposal and information stating the rationale for the change. After the change proposal abusiness item containing this information is created, and the supporting documentation and identifiedMetaphase PSM components or assemblies are related to the proposal using a graphical drag anddrop operation.Typically, the change proposal will go through a life cycle, giving all interested reviewers theopportunity to support or reject the proposal. This is the first opportunity to give downstreamdepartments the chance to review proposed changes in order to have early input to the designprocess. Reviewers of the change proposal may or may not have the opportunity to vote on itsacceptance. Each change proposal will typically progress through states such as receive the status;proposed, approved, rejected, or authorized implement. Definitions for these states may bedetermined by the administrator of the change control system. If the change proposal is accepted, itgoes on to the next step which determines what should be done to address the requested problem orenhancement.A Work order is a business item which responds to an approved change proposal by describing asolution. Often the change proposal implies a specific solution; however, it deals more with "What" todo rather than a description of the problem. The work order does not specify how the work is to bedone, it simply tells what the results of the work will be. In addition, the work order will often expandthe scope of the requested change to other affected or similar parts.Work instructions add the "How" information to the change control process. All of the requiredtasks may not be known at the time the initial work instruction set is created in design. Other peoplerepresenting different departments may add additional work instructions. To facilitate this interaction,proposed work orders and related work instructions can be processed through a life cycle wherereviewers determine the impact of the change on their product description data. Reviewers willtypically include design engineering, manufacturing engineering, tool design, production and inventorycontrol, purchasing, and any other department potentially affected by the change. Those reviewerswhose areas are not impacted by the change would simply approve with no impact.It may be necessary for the work order to go through multiple cycles of review and modification. Forexample, a particular design solution may add significant manufacturing cost to the product, making itunacceptable. In this case, the work instruction to modify the design would have to be altered andpassed to manufacturing again in order to successfully complete the life cycle and authorize the workorder. Using the graphical user interface, work instructions are dropped on work orders to establishthe "Has Work Instruction" relationship.The authorized work order and approved change instruction are required before the designer mayproceed with the work order. This extra measure of security prevents unauthorized changes.Designers create and revise business items and check out and modify data to implement the changespecified by the work order and work instructions. As business and data items are modified oradded, the relationships to the work instructions and work orders are maintained, providing anexcellent way to track the progress of the change through the system.The final step in the process sends the modified and added business and data items through a lifecycle to approve the changes. This step is the same whether or not companies employ strict changecontrol. Upon approval, the new and modified business and data items pass to a released vault area,and the change becomes the new baseline. After the work is complete, the newly baselined businessand data items continue to refer to the work instructions and work orders that generated them. Thisprovides a valuable historical picture of the evolution of the design which allows users to learn fromdesign approaches which have been implemented in the past.


CONFLOW.97.10 36

2.2.7 Image services

IS software manages raster images as controlled objects, enabling user to view, edit, markup, andprint raster images, as well as add free hand, textual and geometric redlining information.Metaphase Series 2 Image Services software enables user to easily distribute, view and comment ontechnical drawings and product documentation. From design workstations to the manufacturing floor,Image Services provides access to electronic data and creates a paperless environment. The ImageServices modules are:• View Only• View and Annotate• View, Annotate and Measure

View OnlyImage Services lets user view documents and drawings represented in both standard raster andvector data formats. User can initiate an imaging session, as well as retain the objects, drawings andtheir relationships for future reference. This sophisticated feature eliminates duplication of labor whenassembling drawing, and document packages.Image Services accepts raster images in any size or density, provides a full range of navigational aids,and supports a wide array of printers and plotters. A high-performance graphics engine enablesusers to compare revision levels, and to create an assembly of components.The View Only module supports:• Zoom, pan, mirror, rotate• Adjust scale and origin for comparison and assembly functions• Multi-sheet/multi-document display• Tiled windows• Assemble and adjust mating components• HPGL plotter, PostScript, and MS Windows printer support• Multiple data types for import: CCITT (Group 3&4), TIFF, and MIL-R-28002 files; CGM;

AutoCAD DXF files; PostScript; Sun Raster; HPGL• Layer and entity discrimination• Selectable print area.

View and AnnotateIn addition to the capabilities provided in View Only, View and Annotate lets users mark up andmake notations, without modifying the original document. Using transparent electronic overlays,View and Annotate makes it easy to draw lines, circle, arcs, text, and pointers, and add freehandnotes.• Multiple line font• User-defined text sizes, line widths, and opaque text• ANSI drafting symbols including feature control symbols• Annotation file editing capabilities, including erase, move, and duplicate


CONFLOW.97.10 37

• Compound annotations, including bundles of raster and vector data, text documents, and theirannotations

• Overlay output in IGES or DXF for transfer to CAD• Annotation template builder• Unlimited number of annotations per drawing.

View and Annotate functions are integrated with the functions of the Life Cycle Manager module sothat during a review process, raster images of documents or drawings can be retrieved and markuplayers saved as comments.

View, Annotate and MeasureThe View, Annotate and Measure module lets users manipulate, measure, and analyze specific partsand components. For raster-based images, Visual Measure Mode provides approximate pixel-to-pixel linear, radial, and angular measurement. For intelligent vector data, Exact Measurement Modeallows users to select entities, and precisely measure linear, angular, and radial distances. Both visualand exact measurements can be captured onto overlays for future reference. Supporting all CALSgraphic standards, View, Annotate and Measure provides selectable view generation of 3D models,optional surface mesh generation, and exact measurement from CAD-defined entitiesMIL-D-28000IGES• JEDMICS image format• CALS Class I and II standards• Exact distance, radial, angular, and baseline measurements• Approximate scaled measurements of raster images• Drawing scale selection• Measurement precision selection• Metric and English units• 3D view generation with surface mesh rendering.

Supported File FormatsThe graphics engine supports an array of file formats, allowing users to tailor Image Services to meettheir varied and varying requirements, including simple viewing for reference purposes only,sophisticated access to the underlying intelligence in data, and data conversion for performanceimprovements and enhancements. Image Services flexibly accommodates a full range of data types,from raster to vector, 2D and 3D graphics, single-page or multi-page documents, and bothwireframe and reinforced model geometry.

2.2.8 Integrator Toolkit

Integrator Toolkit software helps to adapt the system to the user's unique business requirements bymodifying existing capabilities. It also allows to encapsulate other software tools and applications tomake them easily accessible.The software contains a set of tools which may be used to add custom functionality, tailor thefunctionality of the standard modules, or create interfaces to external applications or systems. The


CONFLOW.97.10 38

Integrator Toolkit allows user to encapsulate local software tools and applications into MetaphaseSeries 2.The Integrator Toolkit also allows extension of the functionality of the system itself, including re-definition of the object model used to store product information. The Integrator Toolkit includes userinterface localization and internationalization capabilities, API access, and full documentation of allintegrator tools.The Integrator Toolkit consists of open APIs, GUI development tools, and other tools to ensure thatboth user and enterprise needs are addressed. These tools, when combined with the MetaphaseSeries 2 architecture, provide unparalleled flexibility:• Operating System Interface API• User Interface API• Data Base Interface API• Network Interface API• Object Dictionary• Dynamic Rules Processor

Object DictionaryThe storage and maintenance of the object class hierarchy is accomplished through the use of adynamic object dictionary. This dictionary is delivered pre-populated with standard objects. Withcustomizable attributes and objects, Metaphase will apply the user's terminology, formats, standards,valid values, numbering schemes, and screen layouts. Aspects of attribute or object customizationinclude:• Object type definition• Attribute definition and prompts (customizable for each document type)• Attribute formats (alpha, numeric, alphanumeric)• Legal (valid) values• Screen definition and layout.The object dictionary also defines the objects and relationships (and constraints), and identifies keyattributes, rule attributes, and other descriptive attributes for each entity and relationship.

Dialog Box Layout EditorThe dialog box layout editor allows user to create new dialog box definitions as well as modifyexisting ones. The user interface allows for the localization or internationalization of prompts, menus,help and error messages, and all other displayed text.

Object Method APIThe Object Method API provides access to high-level object methods from either the C language oroperating system command level. This API performs data base and function services for objects in ahigh-level object oriented manner.


CONFLOW.97.10 39

Programmatic APIThe programmatic API provides C language access to the internal APIs of the Metaphase Series 2system, including the data base API, user interface API, operating system and utility API functions.

Object BrowserThe object browser toolkit provides the capability to create new object browser windows thatprovide a graphical front-end to external information systems such as MRP. This toolkit provides thebasis for the object browsers in Metaphase system.

Encapsulation GeneratorThe Encapsulation Generator allows the integrator to describe, via the user interface, eachapplication and associated data objects and parameters. The encapsulation for that application isthen generated automatically, but can be further modified to meet site requirements. The ObjectMethod API provides an interface that external applications may call to register, update, andmanipulate data objects. This interface is callable from the OS command line level (i.e., from a shellscript), eliminating the need for programmatic linkage between the application and the Metaphasesystem.

2.2.9 Application Interfaces

Application Interfaces software allows the linking of all the components of the enterprise, includingMRP and imaging applications, as well as programs such as I-DEAS Master Series, AutoCAD,Pro/ENGINEER, Alpharel/Optigraphics, Framemaker, and BoardStationThe Metaphase software is designed to work cooperatively with external applications so that usersare provided with transparent and immediate access to the application functionality they require. Thisis done through encapsulation of the external applications.Encapsulation involves identifying the rules associated with each application and the types of dataobjects it produces, and then prescribing parameters for application launch and automatic metadatatransfer from the application or system to the underlying PDM repository. Once encapsulated,Metaphase Series 2 acts as a common graphical front-end or environment for the access and usageof the applications.

Designed for UsersEach Metaphase Series 2 application interface is designed around the particular needs of a specificapplication user. Metaphase Series 2 provides a common starting point for all application users. Forothers, it is unobtrusive and represents new features from within the application itself. The interface isdesigned to be consistent with the environment to which the user is accustomed, so that little or notraining is necessary.Each interface is designed to interact uniquely with the characteristics of the specific application. Ifthe application uses complex file structures, or creates its own product structure, Metaphase Series 2captures these characteristics to ensure consistency. It will provide transparent network access tofiles required by the application, even when the application itself does not do this.


CONFLOW.97.10 40

Cost EffectiveStandard, supported interfaces represent an extremely cost-effective solution to application-specificproblems. They leverage the combined common requirements of all the application users, saving thecorporation the cost of duplicating the integration effort.The timely accommodation of new releases of individual applications and operating systems savesthe organization crucial implementation time, as well as the extensive cost of maintaining internallydeveloped interfaces.

Enhanced ProductivityThe easy-to-use interface is the same across a wide variety of platforms. Corporate standards andprocedures for creating and using data become a part of the system and are automatically enforcedto ensure consistency within the enterprise. Changes to all data files are tracked in real time toprovide up-to-the-moment information to all users. The comprehensive Metaphase environmentensures full reuse of data. The entire enterprise, including suppliers and even customers, become anintegrated whole so that product life cycle costs and time-to-market are reduced while quality ismaximized.

Application Interface LibrarySDRC and their technology partner, Metaphase Technology, Inc., develop, maintain, and support alibrary of standard interfaces for popular commercial products. The library includes interfaces for:• I-DEAS Master Series• Alpharel Imaging• Pro/ENGINEER• SAP• AutoCAD• FrameMaker• Mentor Graphics


CONFLOW.97.10 41

2.3 OPTEGRA (COM97)

Computervision's Optegra Revision 2.0 consists of three solutions: information management(Optegra Vault and Distributed Vault), task-based workflow management (Optegra Workflow) ;and configuration management (Optegra CM)

2.3.1 General new features and functions

EPD Connect provides a common interface with a Windows 95 look for all enterprise computing. Itconnects all users to information, to each other, and to the processes in which they participate. It alsofunctions as a common on-line work environment, supplying users with the software applications theyneed and engaging them in their work processes.

EPD Connect consists of multiple information pathways or views that are mutually interactive, so thata change in one results in real-time updates in the others.These pathways are:• The Information Browser - the gateway to all personal, company, supplier, and other external

information• The Product Structure View and the 3D Viewer - complementary views of product structure (a

tree representation and 3D model, respectively) for browsing, visualizing, and understandingcomplex structures and accessing related information

• User's Process View - where users can access Optegra's workflow and see graphical roadmapsof the sequence of their project tasks

• User Application Workspace - where the pertinent information and applications appropriate tothe user's job appear

The consequent benefits:• Improves the visibility of work status, complex product assembly information, and key product

attributes (for example, planned versus actual resources) for easy tracking• Integrates all functions and suppliers in the extended enterprise, not just traditional engineering,

with existing and up-to-date, evolving product information - improving productivity• Makes concurrent team work standard and optimizes collaboration - by connecting team

members to one another and to relevant, up-do-date product information• Delivers the right information and applications to the work environment at the right time - to

improve productivity and coordinate teamwork across the enterprise

Message-Based Communication Bus allows third-party applications to communicate directlywith Optegra Workflow, Navigator, Visualizer, Explorer and the Product Structure View and 3DViewer in EPD Connect. As a result, users can access these Optegra capabilities while workingwithin their other applications. Also, because of this integration, changes made to data in theseapplications result in real-time updates in the Optegra modules.

Common Platform and Oracle Support. All modules of Optegra 2.0 run on the same version ofOracle (7.3.2) and the same version of the operating systems supported by Optegra, simplifyingsystem administration and configuration.


CONFLOW.97.10 42

2.3.2 Information Management

Ease-of-Use Enhancements• Common login. Users can log into one Optegra solution - Optegra Vault, Optegra Workflow, or

Optegra CM - and Optegra will log them in to the others, as needed.• Common installation. All three Optegra solutions can be loaded from a single source disk with a

single directory - simplifying installation.• Common license management for all three Optegra solutions

Unit-of-Measure Attribute. Companies can now elect as an attribute the unit of measure in whichlength, temperature, and weight are stored in the database. Once the unit of measure is chosen,Optegra automatically converts other units of measure used by individuals to the elected attribute forstorage, establishing consistency across different departments and global sites and saving conversiontime. It also automatically converts back to the original unit of measure for presentation to users.

Access and Security Enhancements. Companies can establish access rules for specific attributesseparate from the access rules for items with which those attributes are associated, for greatercontrol of information. For example, authorization to access and change an assembly's priceinformation may be restricted to a different set of people from those authorized to access and changethe assembly design.

2.3.3 Workflow Management

Icon Manager feature allows users to create libraries of icons with images they have selected. Italso allows them to redefine the standard, 'default' definer palette icons.

API Enhancements allow users to access Optegra Workflow screens and launch its capabilitieswhile they are working within other applications - saving time.

2.3.4 Configuration Management

Freeze and Unfreeze on Items and ECOs. This allows companies to freeze an item or ECO(engineering change order), preventing further modifications - to preserve the integrity of thehistorical design data. It also provides a highly restricted capability to unfreeze the item or ECO, forcases of mistaken freezes.

ECO and Item Revisions . With this new capability, authorized users can freeze and release anitem or ECO for manufacturing, then create revisions that evolve it, each with a separate, individualalphanumeric identifier. This capability preserves the integrity of the historical design data of thefrozen, released item; allows the design to be evolved in revisions; and, through the unique identifier,provides a tracking mechanism for inventory, maintenance, and legal purposes.

Date, Number, and String Effectively. In addition to specifying effectively by dates, authorizedusers can specify effectively as numbers and alphanumeric strings, such as lot and serial numbers.This enhancement also allows authorized users to define flexible effectively filters, which now can


CONFLOW.97.10 43

include wild cards, for viewing product structures. These filters determine what product informationis visible and what is hidden when viewing the product structure tree.

Relationship Constraints. Authorized users can specify the types of relationships that can beapplied to types of items, and, thereafter, Optegra catches and prevents instances that violate theseconstraints. As a result, this capability helps to prevent problems by preserving design intent andenforcing uniformity of usage across a geographically dispersed design-build team.

2.3.5 New Optional Modules

Optegra includes a family of scaleable CM (configuration management) products based on theCMstat V5 configuration management system developed by CMstat, Inc. These applications allowusers to create, modify, interrogate, visualize, and manage a product and its supporting data anddocumentation throughout its life cycle: from initial requirements definition through on-going customermaintenance. The family consists of the three software packages, which all integrate with and areaccessible from EPD Connect.

Optegra Advanced Configuration Management module supports a history and audit trail of alldata originated, created, and revised throughout the product life cycle. It maintains the relationshipsamong all documents, their status, and associated items/parts. Users can access information bydocument number or part number.

Optegra Advanced Configuration Viewer. This entry-level tool is a general-purpose browser forconsumers of configuration management information. The viewer• Improves product quality through clear, concise, valid data• Reduces the cost of implementing change through change impact assessment and a 'closed loop'

process• Improves the visibility of and access to product documentation and pending change activities• Accelerates new product development, for shorter time-to-market cycles• Facilitates the implementation of enterprise-wide concurrent engineering

Optegra Advanced Configuration Exchange. This module allows companies to take data filesstored in relatively inaccessible legacy systems and transfer them into a convenient, easily-accessedCM/PDM systems that provides data validations and rules to maintain data integrity. It also:• Completes data migration in days or weeks instead of months or years• Allows users to import and export data using one of several industry-standard formats• Allows users to easily access and share engineering data widely, throughout the enterprise

Optegra Classification Management System. This component classification provides engineeringand procurement departments with a consolidated view of technical and business information forcomponent parts and suppliers, significantly reducing design-to-manufacture time, optimizing supply-chain relationships, and increasing return on information. Based on the Aspect Explore system(developed by Aspect Development, Inc.), and integrated with and accessible from EPD Connect,this product allows users to rapidly and effectively access a complete and virtually limitless electronicvault of existing component information. As a result, it:


CONFLOW.97.10 44

• Eliminates man-hours wasted developing previously designed components and maximizes designreuse

• Reduces the man-hours previously spent searching for component information using a lessautomated retrieval system

• Reduces the costs associated with using lower-quality products because information on higher-products was not available

2.3.6 Integration

Optegra Interface software provides point-and-click access to Vault services from withinCAD/CAM software such as Autodesk's AutoCAD, IBM's CATIA, Parametric Technology'sPro/ENGINEER, and Computervision's CADDS, MEDUSA, and DesignPost Drafting. OptegraInterface software provides a predefined set of rules which define the collection of files that make upa part or assembly for a particular application, so that they can be manipulated as a single unit.

Interface for Pro/Engineer

The Optegra Interface for Pro/ENGINEER allows users to store, retrieve, and query their parts,assemblies, drawings, layouts, user-defined features, and formats within the Vault. When used inconjunction with Navigator, users can display and navigate a Pro/ENGINEER assembly andgenerate comparison reports such as planned-versus-actual cost and weight.Optegra Interface for Pro/ENGINEER provides access to all of Vault's data and releasemanagement services. From within their Pro/ENGINEER application, users can complete tasks suchas drawing location, check-in/check-out, design reviews, and messaging. This interface works withthe client communication subsystem so that users can effectively secure their valuable designinformation.Optegra Interface for Pro/ENGINEER, with the client communication subsystem, allows users whohave signed onto the Vault server to have access to this database of engineering information. If theuser has the proper authority, the Vault server delivers a copy of the requested data object, includingthe object's metadata, which describes each data object's characteristics (such as storage, location,owner, version) and locks it from modification by other users. Other users can obtain a copy of theobject to read it, but no one else can modify the object until it is checked back into the database.

Benefits:• Allows direct access to Vault services from within Pro/ENGINEER and the manipulation of

multi-object parts, assemblies, layouts, user-defined features, and formats as a single unit• Provides ability to automatically trigger events before and after object check-in and check-out.

Features:• Point-and-click access to Vault data and release management services from within

Pro/ENGINEER.• Predefined rule base defines the collection of objects that make up a Pro/ENGINEER part,

assembly, drawing, layout, format, and user-defined feature so they can be manipulated as asingle unit.

• Automatic maintenance of parent/child relationships and revisions between objects.


CONFLOW.97.10 45

• Triggers the execution of predefined pre- and postprocess routines upon object check-in andcheck-out for STORE, REPLACE, GET, and READ commands (e.g., Pro/BATCH processingof export items).

• Provides filter for viewing list of objects from local disk or Vault using the Pro/ENGINEERobject type selected by the user (e.g., all, part assembly, drawing, layout, format, and user-defined feature).

• Capture property information from Pro/ENGINEER parts and assemblies enabling efficientassembly navigation.

• Cleans local disks (automatically purges old versions after initial store operation).• Supports the automatic (e.g., RENAME) and manual (e.g., COPY) renaming of components

when referenced within assemblies and within parametrically associated PTC objects.

Platforms supported• Supports Pro/ENGINEER objects for Revisions 10 through 17.• Requires access to one or more of the following: EDMClient(tm), EDMNavigator(tm), Locator,

Configuration Access 2.0, or Navigator.• Runs on Sun Solaris 2.3, SunOS 4.1.3, HP-UX 9.0.5, IRIX 5.2, IBM(r) AIX(r) 3.2.5 and AIX

4.1, and Windows NT• Requires EDMVault(tm) 5.1.2 or above; Optegra Vault 1.0 or above.

MRP Interface for SAP R/3

This interface provides on-line, bi-directional data exchange between Optegra and SAPenvironments, allowing Optegra to request services or exchange data with SAP's ProductionPlanning (PP) and Material Master (MM) modules. As a result, users can transfer engineering data,such as an engineering bill of material (BOM), into the SAP database; locate and launch SAPtransactions; and place specific SAP data under the control of Optegra.

Benefits:• Provides one-to-one mapping between data objects created and managed within Optegra and

those created and managed within SAP (e.g. SAP material, SAP BOM, and SAP document)• Allows users to trigger events before and after changing an object• Synchronizes product information between the two platforms• Associates photorealistic geometric information with the appropriate product structure (when

used with the Optegra Visualizer)

Features:• On-line, bi-directional data exchange between Optegra and SAP for transactions initiated by

Optegra users• Pre-defined rule base -- defines the collection of Optegra objects that makes up an SAP

material object and SAP item master object. This information can be transformed into an SAPmaterial BOM object, SAP technical BOM object, and SAP engineering BOM object.

• Reserved SAP material number generated for each new object created in Optegra• Automatic updating of an object and associated attributes within SAP when the object is

updated within Optegra


CONFLOW.97.10 46

• Queries of single-level, multi-level, and summarized SAP BOMs• Context-sensitive SAP help

System requirements:• SAP R/3 Version 3.0c or above• Optegra modules 2.0 or above• Optegra Vault and Optegra Navigator• Optional modules: Optegra Locator, Configuration Master, Optegra Visualizer, and Optegra

Explorer

2.4. Pro/PDM and Pro/INTRALINK

Parametric Technology's Pro/PDM has been developed to handle complex PDM functions,Pro/INTRALINK system is designed to manage and enhance concurrent development environment.

Pro/INTRALINK was released in May 1997, consequently deep industrial experiences have notbeen accumulated yet on their coexistence or on the change process from PDM to INTRALINK.This issue was one of the hot topics at the Pro/E Users' '97 Conference, because Pro/INTRALINKhas been developed from the ground up with now start point with Pro/PDM (SHEA97).

2.4.1 Pro/PDM (PTC95)

PTC's product data management system specifically manages Pro/ENGINEER's feature-based, fullyassociative environment. By permitting simultaneous modifications, identifying potential conflicts, andcoordinating changes for integration, Pro/PDM supports true concurrent engineering.


CONFLOW.97.10 47

Figure 2.4 Pro/PDM search layout (early version)

Figure2.5 Pro/PDM: database using(DEM97)


CONFLOW.97.10 48

Figure 2.6. Pro/PDM authorizations (DEM97)

Pro/PDM encourages concurrent modifications by providing simultaneous data access to all teammembers. At the same time, approval sequences permit early recognition and easy resolution ofconflict, facilitate integration, and ensure that only approved revisions enter the database. Thiscombination of concurrent data access and established approval procedures improves productivity,reduces time to market, and enables engineering teams to work together more effectively than everbefore.

By expanding Pro/ENGINEER's technology into information management, Pro/PDM meets therequirements of parallel product development. Taken together, Pro/ENGINEER and Pro/PDM canmake concurrent engineering for any manufacturer.

2.4.2 Pro/INTRALINK (PTC97)

OverviewPro/INTRALINK is designed to provide tools to manage concurrent development environment. Itsopen architecture and web-accessibility enable the sharing of information throughout all organizationsinvolved in the product development process.Aspects of three traditional management systems - Product Data Management (PDM),Configuration Management and Software Source Control - have been incorporated intoPro/INTRALINK to create an environment in which individuals may work simultaneously oninterrelated information with complete awareness of concurrent activities.


CONFLOW.97.10 49

Users need an environment which allows them to simplify and locally manage their own work, as wellas communicate real-time development activities to everyone involved in bringing a product tomarket. To achieve this, it is necessary to have an information management system which is tightlyintegrated with the design environment and based on an architecture which facilitates communication.

Integrated environmentPro/INTRALINK's unique, integrated environment provides complete management of theconcurrent development environment while imposing minimal restrictions and overhead on designactivities. The Pro/INTRALINK environment provides a centralized database, as well as personalwork areas for each user to facilitate the flow of interrelated information among users.Commonspace. Based on the industry-leading Oracle Relational Database Management System(RDBMS), the Pro/INTRALINK environment provides a centralized database, calledCommonspace, as well as personal work areas for each user. Commonspace is used as a collectionpoint to organize all development activities. It also serves as the location from which all productinformation is communicated.Workspace. The personal work area, known as Workspace, helps users manage their work inrelation to others. It maintains all local design changes and allows users to work independently, whileopenly communicating to, and receiving information from Commonspace. This "real-time"communication and exchange of information allows intelligent design decisions to be made morequickly from a product's inception.

File vaultsPhysical files, which are represented by objects, are stored in file vaults. Multiple vaults may beestablished within the Pro/INTRALINK environment, providing storage and access within closeproximity to areas of high usage.

Open ArchitecturePro/INTRALINK provides an open architecture that facilitates the sharing of up-to-date productmodel information among various organizations involved in the product development process. Theopen set of Application Programming Interfaces (APIs), contained in the Pro/INTRALINK Toolkit,enables other information systems to access, query and manipulate information within thePro/INTRALINK environment, improving the flow of information throughout the entire productdelivery process. Pro/INTRALINK's Web-based interface provides the necessary components todynamically access and query information within the Pro/INTRALINK environment, extending thevalue of this information to organizations outside engineering. Using the Pro/INTRALINK Toolkit,customers can extend these capabilities to create a unique environment in which everyone within acorporation can access information through a common interface, the Web browser.

Transparent Data ManagementPro/INTRALINK was optimized to work in conjunction with Pro/ENGINEER to enhance themanagement and communication of information within the concurrent development environment.Changes made in either the Pro/ENGINEER or Pro/INTRALINK environments are maintained inboth locations - significantly increasing user productivity. With Pro/INTRALINK, information


CONFLOW.97.10 50

management activities are incorporated into the design process, improving user productivity andaccelerating time to market.

Pro/INTRALINK ToolkitThe Pro/INTRALINK Toolkit provides a set of object-oriented application programming interfaces(APIs) for performing operations on the information stored within the Pro/INTRALINKenvironment.

Figure 2.7 Pro/INTRALINK Toolkit connectionsAs shown in the illustration, these APIs provide a common method for applications developed byPTC, customers, or PTC Cooperative Software Partners (CSPs) to access, query and manipulateinformation within the Pro/INTRALINK environment.The Pro/INTRALINK Toolkit provides complete access to the information withinPro/INTRALINK to perform such tasks as:• Identify one or more versions of an object• Determine the Bill of Materials for an object• Create, delete, or modify the relationships between objects• Create, delete, or modify the attributes for one or more objects• Check In or Check Out objects

Process Focused ApplicationsPro/INTRALINK consists of six application areas designed to address the specific managementneeds associated with a concurrent development environment. Each application area was developedto perform specific management activities with a minimal impact on the development process. The sixapplications are:• Application Manager• Pro/ADMIN• Pro/COMMONSPACE• Pro/LOCATE• Pro/WORKSPACE


CONFLOW.97.10 51

• Pro/PREFERENCE

Application Manager creates a single working environment for users. Each users' environment cabbe tailored to provide access to all the tools necessary to perform daily design activities. Applicationscan easily be accessed and managed through the Application Manager.The Pro/ADM application provides easy setup and maintenance tools for the Pro/INTRALINKenvironment. The folder tab interface defines easy access for updating settings over time.Capabilities provided by Pro/ADM:• File cluster and vault definition• Object types• Attribute definition (for objects, relationships, baselines, folders, users, groups)• Users• User groups• Roles• Release levels and schemes• Revision sequence• Administrator authorization• Attribute authorization• FoldersPro/COMMONSPACE is used to store, find view and modify information within the Commonspacedatabase. Typically modifications made in the Pro/COMMONSPACE application pertain to a singletask or all versions of an individual object. When multiple task or changes are planned, users willtypically use the Pro/COMMONSPACE application to identify the desired objects and then checkthe object out to their local Workspace database for modification.The Pro/LOCATE application assists users in finding objects within the Commonspace database.The Pro/LOCATE application allows users to define any known properties of the desired object andwill return all objects matching the criteria. To minimize searching efforts, user may establish a set ofstandard searches, which appear when first entering the Pro/LOCATE application.The Pro/WORKSPACE application is used to view and modify objects in the user's Workspace.Users will typically copy information from Commonspace to their Workspace to make modifications.Once all tasks have been completed by the user, the modified objects may be checked in toCommonspace as a single transaction.The Pro/PREFERENCE application provides users with tools necessary to define default systembehaviors at a system and user level. By defining default behaviors, the process for performing taskswithin Pro/INTRALINK can be standardized and performed in a minimal number of steps. Defaultsmay be established for Check in, Check out, Reports, Configurations and Table Displays.


CONFLOW.97.10 52

2.5 Basic PDM functionality of SAP R/3 (ROGO97)

2.5.1 The SAP R/3 System

The SAP AG is a software company with thehead quarter in Walldorf, Germany. SAPstands for ‘Systems, Applications andProducts in Data Processing’. The product R/3is a standard business software and is settled inthe area of MRP systems. The ‘R’ in theabbreviation stands for ‘real-time’ and means,that every change of the data is updatedimmediately. Another characteristic of thesystem is the client/server architecture. Thesystem is build up with different modules forevery business area, such as materialmanagement and production planning.However, because of the overlap betweenPDM and MRP systems, it includes already

PDM functions, such as document management, classification, product structure management andproject management. The next release will provide a stand alone PDM solution. In the followingsections the PDM capability of SAP R/3 release 3.0 C will be investigated to find out what isavailable so far. Basis of the description will be the ‘On-line Documentation’ of R/3, because allfunctions of the system are described there.

2.5.2 Document Management

The new challenges for the enterprises, such as increased complexity of products and increasedrequirements of the customers lead to more complex development tools and therefore to many digitaland non-digital data, such as drawings, word processing documents, NC programs and BOM’s.This data describes the products, the product development and change processes and the productmanufacture. It has to be maintained throughout the entire life-cycle, including the interchange of thedata between various development tools and the archiving of the data. Archiving of data is especiallyimportant because the product liability laws are becoming stricter. That is why a good documentmanagement system (DMS) becomes increasingly important for enterprises. In this section a surveyof the document management will be conducted.Some definitions used by SAP in connection with this capability will be given in section 2.5.2.1followed by the description of the system’s functionality in section 2.5.2.2.

R/3R/3Client / ServerClient / Server

ABAP/4ABAP/4

COCO

AMAM

PSPS

WFWF

ISIS

MMMM

HRHR

SDSD

PPPP

QMQM

FIFI

PMPM

Figure 2.8 Modules of SAP R/3


CONFLOW.97.10 53

2.5.2.1 Terminology Adapted by SAP

This section will give an introduction in the terminology of SAP.

Document

In the system R/3 a document isdefined as:

“Data storage medium containinginformation which is intended eitherfor the user or for transferringinformation between systems. It cancontain any type of storableinformation which describes anobject (for example, technicaldrawing, graphics, program, or textdocument)...” [SAP, 96] Allinformation about a document isstored in the ‘document inforecord’.

Document info record

In R/3 a ‘document info record’ is maintained for each document. It contains all information,descriptive and control, that is connected with the document, such as processing status, the storagelocation, as well as other administrative data. By creating a ‘document info record’ it is necessary todefine a key to identify the document. It consists of four parts: document number, document type,document part and document version. Only with this key it is possible to retrieve the document formaintenance, change or display.

Document number

The document number is the main part of the key. It is an alphanumeric field that consists of 25characters. It is feasible to assign the number externally, internally or mixed. External numberassignment means that the user is able to use his number key to identify the document. By usinginternal number assignment, the system assigns the next available number from the defined numberrange. This number range is defined during the customising.

Document type

The document type is an alphanumeric field of 3 characters. It has important control functions insidethe DMS. For example, it is possible to define for each document type a status network, screenlayout, number assignment, the used number range, version number assignment, revision levelassignment, storage in an archive and additional data. Furthermore it is possible to connect documenttypes with SAP-objects via object links, such as materials or equipment. In particular the statusnetwork is an important tool for the workflow management. Using settings in SAP Workflow, it is

SAP

document

Technicaldescriptions

Textdocuments

CAD-drawings

NC-programs

Programfiles

SAP objects• Material Master

• Equipment Master

• WBS Element

• ...

Object links

Figure 2.9 SAP Documents


CONFLOW.97.10 54

possible to define that any status change will automatically trigger a workflow task. All these settingshave to be done during the customising.

Document part and document version

The system provides the opportunity to share a big document in different parts and maintain itseparately. It is also possible to create different versions of one document. Versions are used torepresent the different change statuses of a document. However, all parts and versions of onedocument have the same document number to indicate they belong to the same document.

2.5.2.2 Functions of Document Management

R/3 supports the following functions of document management:

• Functions in the ‘document info record’:

− numbering, version management, audit function, classification, document hierarchy,

document search

• Internal systems:

− link to other SAP objects (material master, equipment master, functional location)

− engineering change management with integrated workflow, BOM’s, SAP workflow

• External systems:

− connection to workstation application, CAD systems, ArchiveLink

There are many ways to reach all these document management functions. However, this functionalitycan also be accessed from many other points, such as material master and equipment master,because it is a central function of the system. The following subsections will give an overview aboutthe information which is possible to maintain for a SAP document. Then a detailed description of themain capabilities of document management will follow.

2.5.2.2.1 Information in the ‘Document Info Record’

The basic screen of ‘document info record’ is shown in Figure 2.10. On this screen all information isentered that is connected with the document. On the top of the screen common data, such asdocument number, document type, document part and document version is displayed. Moving downthe document class and the class type of the document are shown. These are important fields if theclassification capability is used. The system sets automatically the accordant indicator if a documentstructure is defined or the document is marked for deletion. By using the CAD interface of R/3 tocreate or change the document from a CAD system, the CAD indicator will be set by the system.The next fields show the document description. It is possible to maintain this description languagedepended. That means a German user has the opportunity to get a German description of adocument that was created by an English user, if the German description was entered.


CONFLOW.97.10 55

If a status network for this document type is defined a document status can be entered. The systemshows all statuses that can be assigned. It is possible to display the network and the current“position” of the document in it. Other fields display the responsible user and the responsibledepartment. They can be implemented in the workflow. Furthermore it is possible to assign a changenumber for every ‘document info record’. If the ‘document info record’ is connected with the originalfile, such as a CAD drawing or a word processing document, the application type and anapplication-start-button is displayed. In other fields a superior document can be entered to representa document structure. All connected documents of the structure can be displayed by choosing thefunction ‘document structure’ from the pull down menu. From the basic screen it is possible to reachall connected SAP objects, such as material/equipment/BOM master, which have already beendefined. The change of documents can be executed with a reference to a change master. The changerecord information of the ‘document info record’ is a very important source, because all changeswith date and responsible user are recorded here.

Figure 2.10 Basic Screen: Create a Document

2.5.2.2.2 Document Version Management

Sometimes it is necessary to create document versions to represent the different change statuses of adocument. Creating a new version of an existing document is straight-forward. One way of doing thisis to display the document and choose the option ‘new version’ from the pull down menu. Then thesystem prompts to which directory the current version of the document shall be copied. The enteredpath and file name are automatically taken over in the head screen of the ‘document info record’. If


CONFLOW.97.10 56

objects, such as material master or equipment master are linked, the system will ask if theseconnections shall be copied, too. The version number will be assigned automatically by the system ifit is defined for the document type. After that all desired changes or enhancements can be done. Bychoosing ‘versions’ in the pull down menu, the system provides also a facility to get a summary aboutall existing versions of a document.

2.5.2.2.3 Document Status Management

If a status network is defined an user can determine only document statuses in accordance to it. Thisensures that the development or change process for every document is controlled. The statusmanagement is also an essential tool for the workflow management, because it is feasible to definethat every document status can trigger a special workflow task. Figure 2.11 shows an example of astatus network.

With different authorizations for the assignment it is possible to determine that a change has to beapproved by a superior user, for example the head of the department

2.5.2.2.4 Non-SAP Document Management

The non-SAP document management is very important, because most of the documents, such asdrawings, NC-programs and text documents are created in other applications. R/3 provides theopportunity to connect SAP documents with documents created by other applications. Thesedocuments are called original files. The file format of an original document is equal as long as theapplication is defined in the system.

Figure 2.11 Example of a Status Network


CONFLOW.97.10 57

By connecting a document with an original file it is necessary to enter the application type and thestorage of the files, such as data carrier and path. After entering all required data an application-start-button will appear. By double clicking it, the system will start the application and open the file toenable the user to maintain it.

However, the system does not realize whether the file has been changed. That means the user mustchange the document status manually to signify the change. To use the capability, the application andthe data carrier have to be defined during the customizing. Chapter 4 discusses the way of definingsuch applications.The opportunities to process an original file is illustrated in Figure 2.12. This figure shows also thestorage of the original files. The normal way is to store the data on the application server. If thedocuments have reached a status that has to be retained, for purpose of documentation or security,they can be stored in the SAP database, an optic archive or in an user defined vault. The accesspaths to these ‘storehouses’ have to be defined during the customizing and is not assessable from thedocument management menu. If the application is defined in the right order, there is also a possibilityto start, from a SAP session, a ‘clean’ application session, create a document and connect it laterwith a SAP document. To start a ‘clean’ session follow this path: Logistic - Central functions -Engineering - Extras - Start application

2.5.2.2.6 Connections to Other SAP Objects

The standard SAP system supports connections, called links, to many objects, such as materialmasters, work breakdown structure elements, equipment masters, ‘document info records’.Therewith it is feasible to get access to all these objects from the ‘document info record’. That meansa designer can display a material master and jump from there to the assigned document, for examplea CAD drawing, and maintain it depending on his authorization. However, there are tworequirements that has to be realized. The object must have a master record in the system and the

Figure 2.12 Process Opportunities for an Original File


CONFLOW.97.10 58

used document types must be connected with the required object. This has to be done during thecustomizing.

2.5.2.2.6 CAD Interface

In section 2.5.2.2.1 the CAD SAP interface is mentioned. This interface is used to enable datatransfer between the SAP and a CAD system. Two kinds of interfaces are provided, the dialogueinterface, and the remote function call (RFC) interface. In Table 2.1 both types are compared.

If a CAD system and SAP R/3 are connected via an interface, it is possible to create, out of theCAD session, for every part or assembly which is generated the material master and a ‘documentinfo record’. Furthermore it is possible to overtake the existing assembly structure in a bill ofmaterial.

There are some software suppliers that provide SAP-certified CAD-interface solutions. One of thesupplier is ‘Eigner+Partner’. They provide an interface to AutoCAD and PRO/Engineer. Thefollowing functionality are available from the CAD system [E+P, 96]:

• Management of R/3 attributes,

• Management of material master records,

• Create/change/display Bills of Material,

• Management of documents and document record information,

• Management of plant maintenance information,

• Access to the R/3 mail system.

2.5.3 Product Structure Management

Product structure management is an important component of production planning. All the data storedin BOM’s is used in various production planning activities, for instance, the design department canbase its work on bills of material, the material requirements planning explodes bills of material tocalculate order quantities on a certain date to minimize costs, and work scheduling uses bills ofmaterial as a basis for operation planning and production control. This section introduces productstructure management capability of R/3. At first some definition of terminology used by SAP will begiven.


SAP uses for the term BOM the following definition:

Bill of Material

A bill of material is a formally-structured list for an object (semi-finished or finished product) whichlists all the component parts of the object with the name, reference number, quantity, and unit of


CONFLOW.97.10 59

measure of each component. A bill of material can only refer to a quantity greater than or equal toone of an object.

Items

All elements of a bill of material are called items. They contain the information about the used objects

in the assembly and are organized in item categories in according to their features. These item

category have control functions within the bill of material management of R/3.

Two technical types of BOM’s are available to represent similar production alternatives:

dialogue interface dialogue RFC interface

Dialogue Is emulated in the externalapplication

SAP screens can be used

Active system R/3 System functions asdatabase server Externalapplication is the leadingsystem

R/3 System and externalapplication are active inalternation

Communication Via API calls in the SAP-CAD function library

Via Remote Function Calls(RFC)

Data transfer Via data strings with RFC data structures(fields, structures, tables)

Enhancements to interface User-defined APIs Integration of any dialogueRFCs or RFCs

Table 2.1 Comparison Dialogue - RFC interface

Variant BOMA variant BOM groups together several BOM’s to describe different objects, for example products,which have a high proportion of identical parts. A variant BOM describes the specific productvariant for each product, with all its components and assemblies.A variant can be created only from an existing BOM. This, for example, will be done when byreplacing of one component a new product is created. In Figure 2.13 a simple example is shown.


CONFLOW.97.10 60

Multiple BOM

A multiple BOM gathers together several BOM’s to describe one object (for example, a product)made up of different combinations of materials for different processing methods. Figure 2.14illustrates a multiple BOM. The two alternatives differ only from the quantity of a single component.

Configurable BOM

A configurable BOM is used to represent a product with many variants (such as the different modelsof a car type) in one BOM.

In this BOM are entered beside the materials used in all variant also all selectable components. Tocreate a BOM of one special variant selection parameter are used. This parameters, as known asobject dependencies, have to be defined and maintained.

Bicycle blue

Bicycle black

Frame blue Handlebar Gears

Frame black

Source: SAP AG

Figure 2.13 Example for a Variant BOM

Alternative 1

Alternative 2

Material A 10 litres Material B Material C

Material A 15 litres

Source: SAP AG

Figure 2.14 Example for a Multiple BOM


CONFLOW.97.10 61

BOM groups

A BOM group is used to group together material BOM’s which describe one product or severalsimilar products. A BOM group can contain:

• all variants of a variant BOM

• all alternatives of a multiple BOM

2.5.3.2 Functions of Product Structure Management

In R/3 the whole product structure management is processed by BOM’s. In accordance to the need,these BOM’s can be created for all SAP objects, such as materials, equipment and documents.

Material master BOM is normally used to describe the product structure. Possible entries arematerials and documents. However, for all entered items the material master and the document inforecord must exist. Materials are not only raw materials, but also semi finished or finished assembliesor products.

Equipment master BOM is used to describe the equipment structure

‘Document info record’ BOM is known as document structure and is used to describe a complexdocument structure.

The following subsections will introduce the basic potentialities of the R/3’s bill of materialmanagement such as, what purposes BOM’s can be used for and what reporting functions areavailable. The focus of the description lies in the object ‘material’.

2.5.3.2.1 Single Bill of Material

Creating a single BOM is straight-forward. After choosing ‘material BOM - create’ the desiredmaterial, the plant code and the BOM usage have to be entered. The plant code is only necessary ifthe BOM shall be valid for a special plant. BOM’s can also be created by copying existing BOM’s.On the next screen all desired components, called items, with quantity and unit of measure areentered in a table. It is feasible to maintain for every item a special screen where additional data isdetermined. On another screen the BOM header can be maintained.Here the name of the BOM and the BOM group can be determined. The change of a BOM can beexecuted in reference to a change number. An example of a BOM is shown in Figure 2.15


CONFLOW.97.10 62

Figure 2.15 Example for a Single Material BOM

2.5.3.2.2. Configurable Bill of Material

In section 2.5.3.1 the configurable bill of material is mentioned. In this section a more detaileddescription is given Figure 2.16 shows an example of a configurable product.

Figure 2.16 Example of a Configurable Product

A configurable BOM contains information about all variants of this product. By displaying a BOMfor a special variant the system determine automatically the right components in accordance to theconfiguration profile. Normally, all possible components, non-variable and variant parts, have to beentered. To every variant part a special selection criteria is maintained. Entering all variant parts withthere selection criteria can be very expendable. To reduce the effort of maintenance it is feasible touse the classification system of R/3 and enter class items in the BOM. This classes contain thematerials with their characteristics and possible characteristics values. By configuring, special valuesfor this characteristics can be assigned and determine therefore the variant. Furthermore there is thepossibility to define dependencies between the objects. That means, for example, if component A1 ischosen only component B1 is possible and component C3 is impossible.


CONFLOW.97.10 63

2.5.3.2.3 Views of Bills of Material - BOM Usage

Every department has its peculiar view of the data and may not need all information available. Forexample, the calculating department needs only the components of a product that are cost relevant.To consider this fact, there are two opportunities available. First, it is feasible to create BOMs for

every area in the company inaccordance to the special needs. TheseBOM’s have no connections amongthemselves and are maintainedseparately then. Figure 2.17 shows thesix different kinds of BOM’s that areprovided by the standard system. Forevery view it can be defined that alsoitems which are relevant for other areascan be entered. Otherwise, one bigBOM, which includes all requiredinformation, has to be created. In thisBOM are entered all components of aproduct. To signify their relevanceseveral indicators are set. By explosionof the BOM you can define thedemanded/peculiar view of the BOM.All other materials/components are thenfaded out.

Figure 2.17 The Six Standard Views of BOM’s


CONFLOW.97.10 64

2.5.3.2.4 Reporting Functions

The system supports some reports functions to evaluate the information of a bills of material,including:

• Where-used lists,• BOM explosions,• BOM comparisons.

Where-used lists

The ‘where-used list’ gives an easy overview of what products that a material is contained. Thishappens by displaying of all BOM’s which contain this component. The function is also available fordocuments and classes. However, before the list can be generated some selection criteria have to beentered. This determines how the list will be displayed. A search can be executed directly over thematerial or indirectly over the class. Furthermore the range of search can be restricted by entering theplant, item category and BOM usage. For example, it can be determined that only BOM’s of aspecial plant, with relevance for costing are considered. The system determines then only the BOM’sin that the item has these attributes. In Figure 2.18 an example of a list is shown. By selecting oneBOM and choosing the button ‘Item’ or ‘Detail’ the system jumps to the basic screen of the item orto the material master record of this material.

BOM explosions

Bill of material explosions are used to display what materials belong to the product. There are twodifferent options to uncompress a BOM, structure reporting function, such as ‘multi-level BOM’,and quantity based function, such as ‘summarized BOM’. After selecting the desired explodingfunction the user has the possibility to choose the demanded view of the information, for example, thedepartment of production planning want to see only the components which are relevant forproduction orders. Figure 2.19 shows an example of a multi-level BOM. Because this presentment isnot very clear it is feasible to use a graphic editor of R/3 to display it. From both representations the

Figure 2.18 Example: Where-Used List


CONFLOW.97.10 65

user can go to the material master record or to detailed information about the items. It is alsopotential to go to the ‘where-used list’.

BOM comparisons

Another possibility to evaluate information is the comparison of two BOM’s. There are two ways toexecute it, the summarized and the differentiated comparison. With the first possibility the quantity ofeach double found component are added. Otherwise, each occurring component is displayedseparately. In addition it is feasible to determine the detail which have to be compared. The systemchecks the BOM in accordance to these details. A ‘flash’ means no conformity, an ‘=’ means equalin accordance to the chosen detail and an ‘≠’ means similar but not equal. The result of a BOMcomparison is displayed in Figure 2.20.

.

Figure 2.19 BOM Explosion Multi Level


CONFLOW.97.10 66

2.5.4 Classification Management

Within the modules of R/3 a lot of data is created and stored in the database. In order to find thesedata as quickly as possible, most of the modules provide a classification system for the used objects.These objects are grouped together by similar attributes and therefore it is easier to find themwhenever required. In addition some functions use classification to create variants or configurationsdependent on special values for defined attributes.To use the classification functionality the classes and characteristics have to be maintained first. Thesefunctions are merged in the classification system of R/3 to ensure a consistent allocation of objects toclasses.The classification management is reachable from the main screen via Logistic - Central Functions.


To get familiar with the classification system of SAP R/3 this section describes the most used terms.

Class:

Objects, such as material or documents, with similar attributes described by characteristics aregrouped together in classes. Each class belongs to a class type to control which objects can beallocated, which screens are available to maintain the allocation, and whether multiple allocations areallowed.

Figure 2.20 BOM Comparison Result: Summarised


CONFLOW.97.10 67

Characteristic:

Characteristics are the properties of an object, such as length, volume or colour. They are used todescribe the attributes of objects by assigning values when the objects are allocated to a class. Tosimplify the assignment of values it is possible to define the data type of the characteristic, such ascharacter or numeric, or to specify the allowed values by naming some values or intervals. Thesevalues are shown during the allocation as possible entries.

Correlation between class type, classes and characteristics:

Characteristics are created independently from classes or class types. Therefore it is possible to usethem in different classes and even in different class types. As long as they are used in classes of thesame class type the value assigned to an object classification is the same in every class, respectivelychanges in one class causes automatically the same changes in all other classes using the samecharacteristic.If the characteristic is used in classes of different class types, there are no connections between thevalues. That means it is possible to assign different values for an object for the same characteristic indifferent classes.To set up a class hierarchy it is possible to restrict the value set of a characteristic for each class.Before setting up a classification system two requirements have to be fulfilled.• Only classifiable objects can be allocated to classes. Therefore the object type of these objects,

such as material or document, has to be defined as classifiable.

• Class types for creating classes have to be defined for these object types.

Both requirements can be maintained in the classification section of the customizing IMG (Tools -Customizing - IMG - Cross-application - Classification).

2.5.4.2 Functions of Classification System

To use the classification within the other modules of R/3 the basic set up has to be done in theclassification management. In addition different objects can be centrally allocated to classes. Asshown inFigure 2.21, these main functions are:• Characteristics maintenance (data type, value set),

• Class maintenance (assign characteristics, restrict values),

• Set up a class hierarchy,

• Classification of objects,

• Object search.

These functions will be described in the following subsections.


CONFLOW.97.10 68

2.5.4.2.1 Characteristic Maintenance

Figure 2.22 shows the basic data screen for maintaining characteristics. That includes generalinformation, such as name, description and group of the characteristic.

The more important field for controlling the use of this characteristic is the data type. With the datatype the user input is determined, especially what kind of data can be assigned, such as numbers orcharacters, and if multiple values are allowed. In addition to the data type numeric, a field appearsfor enabling value intervals as input. To restrict the number of values for this characteristic theallowed values can be defined and are available as possible entries, when an object will be allocatedto a class using this characteristic.

If an attribute is used for classification which is already maintained in one of the R/3 modules , suchas weight or basic material, the characteristic can refer to the master data table field in which thevalue is stored. This ensures that always the right value is automatically assigned to an object and thedata need not to be stored redundant. The reference can be maintained in the additional data screen.

With the interface control the entry field for value assignment is defined. There are possibilities tohide this characteristic or lock the field for manual user entries. In addition an indicator for requiredentries can be set. That means if an object will be allocated to a class with this characteristic a valuehas to be assigned.By restricting a characteristic to specified class types problems with different values in different classtypes can be avoided.

Figure 2.22 Maintain Characteristic: Basic Data


CONFLOW.97.10 69

2.5.4.2.2 Class Maintenance

Beside the general data, such as name, class type, description and administrative data, the basicscreen for class maintenance, as shown in Figure 2.23 , contains statements for allocation objects.‘Same classification’ considers the fact that it might be possible to allocate objects with the samespecification in one class. The system reaction for that case can be set with the radio button in thissection of the screen. If it is set to ‘Error message’ objects with exactly the same values can not beallocated to one class.

Another feature of classification management is maintained with the ‘organizational area’. Like insome other modules of R/3 the classification system supports different views for object allocationand value assignment. That means special characteristics are relevant for different departments, suchas design or purchase, and only these departments have the authorization to maintain thesecharacteristics.

Characteristics can be assigned to a class in the ‘Characteristics’ screen. If the class is part of a classhierarchy the screen shows also the inherent characteristics from the superior class. In addition it ispossible to restrict or overwrite the value for a characteristic for this specific class.In the‘Catchword’ screen, several synonym words can be defined for describing a class. Thesecatchwords enable to retrieve classes later using a match code. The description on the basic datascreen is used as the first catchword.

Figure 2.21 Classification Functionality of SAP R/3


CONFLOW.97.10 70

If the class according to a specific standard, such as DIN, ISO or EU, number and description of thestandard can be entered.

2.5.4.2.3 Set up a Class Hierarchy

To built up a class hierarchy classes can be allocated to other classes via Classification -Allocation - Maintain - Objects to class. First the superior class has to be specified. Thensubordinate classes can be allocated to this class. By using multiple allocations an entire hierarchicalnetwork can be created.

A few points have to be considered when setting up an hierarchy, such as assigning characteristicvalues in a class hierarchy, inherent characteristics and multiple classification.

Figure 2.24 shows an example of an hierarchy with classes, their characteristics and the allowedvalues. The characteristic value assignment for classes within the hierarchy does not affect theindicator for single or multiple value assignment of the characteristic. Although the characteristic‘Thread type’ allows only single value assignment, multiple values, such as metric, trapezoid,imperial, can be defined as possible entries. However, when an object is allocated to the class‘Fasteners’ the ‘Thread type’ has to be specified with only one value from the value set.As shown in Figure 2.23 characteristics are inherited from the superior class to subordinated classes.The class ‘Bolts’ is allocated to the class ‘Fasteners’ and the value of the characteristic ‘Threadtype’ is restricted to metric. In the lowest class ‘Hexagonal bolts’ the characteristic ‘Thread type’ is

Figure 2.23- Basic data screen for class maintenance


CONFLOW.97.10 71

not available for entry on the characteristic value assignment screen, but it is displayed with the valuemetric. The characteristic and its value are inherited from the superior class.If a class has more than one superior class all characteristics are inherited and all characteristics areavailable for value assignment. As already mentioned above special attention has to be paid whenassigning objects to classes of different class types, because it is possible to enter completelydifferent values for the same characteristic.

Figure 2.24 Example for a Class Hierarchy

Source: SAP AG


CONFLOW.97.10 72

2.5.4.2.4 Classification of Objects

There are to different ways for classifying an object. First any object can be allocated centrally withinthe classification management via Classification - Allocation - Maintain - Object to classes, thatmeans one object to different classes, or ... - Objects to class, which means different objects to oneclass.The other way is to use the classification function within the other modules of R/3, as shown in Figure2.25 for the module ‘Material Management’. However, the result is the same and the objectallocation includes the same features.When allocating an object to a class all characteristics of the class are shown. Predefined values areavailable as possible entries and can be selected for evaluating the characteristic. If required entriesare missing the system reacts with an error message.

Figure 2.25 Classification within the Material Master Record

2.5.4.2.5 Search for Object

The search of objects is a function of the central classification module. To find objects within theclassification system, an initial class is required first from which the survey should start. The systemshows all the objects that are allocated to this class. If the class is part of an hierarchy allsubordinated classes are shown also. It is possible to choose one subordinated class to continue thesearch at the next level below the actual class. Together with the possibility to go back to theprevious level it enables to survey the whole structure.


CONFLOW.97.10 73

To restrict the results of a search the assigned characteristics of a class are shown and specific valuescan be entered. Independent of the single or multiple value indicator a set or interval of values can beused to look for special objects that fulfil the search criterion. Values for one characteristic arelogically connected with ‘or’, that means objects are listed that contain any of the entered values.Assigned values for different characteristics are logically connected with ‘and’, which means thatobjects are only listed if they have one of the values of each characteristic.Figure 2.26 shows an example for logically combination of values for different characteristics and theresults.

Class ABC

part 1characteristic 1: Acharacteristic 2: 1

part 2characteristic 1: Bcharacteristic 2: 2

part 3characteristic 1: Acharacteristic 2: 2

Search 2characteristic 1: A,B

charactersitic 2: 2

Result 2part 2part 3

A or Band 2

Search 3characteristic 1: Acharactersitic 2: 2

Result 3

part 3

Aand 2

Search 1characteristic 1: A, B

charactersitic 2:

Result 1part 1part 2part 3

A or B

Figure 2.26 Logical Combination for Object Searches


CONFLOW.97.10 74

2.6 SherpaWORKS97 (SHE97a)

Sherpa Systems Corporation's WORKS97 PDM product family is considered to meet therequirements of the PDM II. functions (the next generation of product data management software).This system offers solutions rather than a PDM "toolkit." The domain expertise of the software isacquired through developing production systems that implement integrated product development forcompanies in a wide variety of industries. As a result, these off-the-shelf applications contain anestimated 90% of the functionality most users need. With minor configuration work of flippingsoftware switches rather than building code, systems move into production very fast.

Figure 2.27.Sherpa environment at Morton Automotive Co. (SHE97b)

2.6.1 Sherpa/IPD (Integrated Product Development)

Sherpa/IPD enables Integrated Product Development (IPD) and also supports and enforcesstandardized processes for each stage of the lifecycle. It handles multiple data types within itscomprehensive standard data model and links all IPD team members throughout the virtual enterpriseSherpa has gathered international users' domain expertise and incorporated it into this Commercialoff the Shelf (COTS) application. By the mid-1990s, Sherpa and its leading-edge customers beganto realize that if the functionality of PDM systems were significantly enhanced, those systems couldhelp companies meet emerging market demands for a more comprehensive approach to themanagement of data.


CONFLOW.97.10 75

Sherpa's PDM supports:• Product Life Cycle. From the requirements (or bid) phase, through concept, design,

manufacture, and sales and support, IPD enables companies to manage each of these phasesand the transitions between them. Also known as concurrent engineering, IPD involves staff frommanufacturing, sales, and support early in the design phase.

• Information Complexity. Data classes include mechanical and electronic hardware designs,embedded software, complex documents, project management, engineering change, data frommarketing, purchasing, planning, and finance systems, and information related to selling andservicing the finished products.

• Extended Enterprise. Extending data and processes to customers, contractors, suppliers and tousers and organizations which may be involved with the product.

Sherpa/IPD provides a data model that supports all types of product data including hardware,software, drawings, documentation (including HTML and SGML), specifications, engineeringchange, and project management data. It manages the relationships between data objects andprovides secure data access. The IPD data model is the core of Sherpa/IPD functionality andconsists of the following object classes:• Work. Work incorporates the STEP AP203 'Work Order' and 'Work Request'. It manages

all types of work that affect the product. This includes tasks, contracts, change proposals,deviations, waivers, stop orders, Engineering Change Requests, Engineering Change Ordersand unincorporated changes. The work object enables program or project management byproviding Work Breakdown Structure (WBS) management and requirements traceability.

• Product. The product data includes hardware, software and materials. The hardwareproduct is subdivided into types including detail parts, assemblies, subassemblies, end items,packaging and component parts. Product software includes source, object or executableembedded software and relates the software components directly to the hardware that itcontrols. Materials are also tracked via the product object.

• Model. The Model object captures complex software objects from design tools. Thisincludes 3D solid models, behavioral models of electronic systems, thermal models andCASE tool data. Models present the design engineering view of the product data.

• Process. The process object manages any process that affects product data. This includeswork instructions, manufacturing processes and ISO 9000 processes. Examples of processdata include bonding, soldering, assembling and handling.

• Document. The Document object includes drawings, specifications, manufacturing workinstructions, standard or custom notes and customer documentation. These documents maybe files that are of any format.

• Enterprise. The Enterprise object represents any type of individual, department or companythat comes into contact with the product data. This includes contractors, suppliers,customers, partners, internal departments and individuals.

• Collection. The collection object provides support for baselines and data management (ordata delivery). Baselines include configuration baselines such as functional, allocated andproduct baselines. It provides a 'snap shot' of the product data at a given time, such as at theend of a life cycle phase. Data management or data delivery functionality provides MIL-STD974 CITIS support for CDRL's and SDRL's.


CONFLOW.97.10 76

Extended Enterprise

Sherpa/IPD manages not only department and corporate data, but also provides secure, remoteaccess of data to contractors, suppliers, customers and other businesses that require visibility ofproduct data. This allows integrated product team members to be geographically dispersed whileproviding everyone with the same data. Sherpa/IPD facilitates the communication between teammembers by providing electronic approvals of all types of product data.Electronic overlay can be used with view/markup functionality, Sherpa's World Wide Web interfacefacilitates this access. Sherpa/IPD also offers users the ability to create ad-hoc and pre-configuredreports from within the IPD database. In addition, reports may be generated from MRP and ERPsystems through an ODBC access.

Configuration and Change ManagementSherpa/IPD provides Configuration Management (CM) of product data by enabling compliance withISO 9000 and MIL-STD 973. The application manages product configurations throughout theproduct life cycle. These configurations may include date and/or serial effectivity effective on the enditem, configuration item or affected item. Sherpa/IPD also manages integrated change and providessupport for variances and unincorporated changes.

Program and Project ManagementSherpa/IPD manages contracts and Requests for Proposal (RFP) and enables project managementusing its Work Breakdown Structure (WBS) functionality. This allows specific tasks to be managedindividually and provides requirements traceability of product data back to the original contract. Itfacilitates the request, initiation, implementation and incorporation of changes so that team memberscan create, modify, review and access the correct product information.

Data Management or Data DeliverySherpa/IPD provides CITIS support for CDRL/SDRL's compliant with MIL-STD 974. This allowsboth military and commercial customers to deliver product data to their customers using a standard,well-defined process. This functionality automates the data submittal tasks and provides reports andtraceability of the deliveries.

Product Development ProcessThe product development process supported by IPD provides a structured, flexible mechanism tomanage product development. Teams begin with a contract or statement of work. They may thenplan an overall product structure (including parts, software, and processes) for the final product andprovide the design elements (such as models, drawings, specifications, notes, and analyses) tosupport it. When the design elements are complete, the team can release the product structure. Asthe product structure is completed, the team can close the work to signal its completion. The qualityof the product development process is assured because this structure integrates all objects and theirworkflows, ensuring that the proper objects are completed before dependent objects can bereleased.


CONFLOW.97.10 77

Integrating Other Tools & ApplicationsSherpa/IPD provides integrations to a set of tools that process product information. These toolsinclude CAD, CAE, CASE, MRP II, ERP, viewing and markup tools, report, document andcomponent information systems. These integrations are possible using Sherpa's standards based,CORBA & OLE compliant Object Request Broker (ORB) architecture.

2.6.2 SherpaWORKS for Product Teams

This application meets the needs of program managers & supervisors whose primary tasks are thereview and approval of product data. Product Teams enables searching, browsing of metadata andstructure, review and approval, and provides history information of every PDM object. It providesview/markup functionality and browsing of file data of appropriate Sherpa object.Product Teams also provides complete document object functionality including create, modify,checkout/in and attaching to other data objects. It provides the ability to initiate change by creating awork authorization object. It will support the creation of a work breakdown structure, the workauthorization's association with those responsible for performing the work, and the ability toreference the data that needs to be changed.This application solves 100% of specific users' requirements out of the box. Specific users include:design engineer; manufacturing engineer, program manager, supervisor, purchasing, shop floor, datamanagement, and configuration managers. It is a native 32 bit Windows 95 application. Users canexpect the performance to be comparable to any common front-end application under Windows.

Tools to quickly search, access and view the data:Sherpa/Browse allows users to search product data by attribute or configuration, and save changesfor later use. Easy-to-use notebook analogy lets users access information quickly, and configure datafor viewing in a familiar format.Sherpa/Review features an Inbox, which is used to notify users about specific tasks or actions theyare queried to take. Users can approved or reject data items as they move through the productlifecycle. Integration with Rosetta's PreVIEW tool for viewing and mark-up of product data, thiscomponent lets users suggest changes and share them with colleagues without permanently modifyingthe original data., maintaining a complete history.Sherpa/Document Management allows users to manage their documentation throughout thelifecycle of the product. It provides full document support, including create, save-as-of informationand file data. It also launches the native PC-based tool and can manage individual files separately.Sherpa/Change Initiator initiates changes to product data and identifies who will make the changes.It also identifies the data that requires modifications, and enables users to make indirect mark-ups todata, relating modifications back to the change.Sherpa/Project Management allows users to manage tasks by introducing new tasks into thesystem and linking them to assemble a Work Breakdown Structure. It allows the user to assignownership of each task, track progress throughout the task's lifecycle and manage specificmilestones.


CONFLOW.97.10 78

2.6.3 Sherpa/WEB

Sherpa/WEB is designed for organizations expanding their Sherpa implementation. Sherpa/WEB isan integration between Netscape's Commerce Server and Sherpa's PDM server using SherpaFoundation Classes CORBA libraries. The integration includes HTML screens and JAVA appletsfor Sherpa/IPD and Sherpa/PIMS functionality. Configurations of the standard HTML search andrecord windows can be set at individual users' sites.Additional features include:• Secure connections and communications with user authentication and encrypted transactions• Adherence to same user access rights and privileges as in the SHERPA server• the ability to list PDM objects/metadata, browse references and look at individual PDM object

data• HTML browser support• "In-Box" capability which holds messages and pending work

Security

All user communications between the Netscape Browser must pass through the Netscape® SecureCommerce Server.

2.6.4 Sherpa/ExplorerSherpa/Explorer provides access into 3D PDM geometric viewing without having the associatedinitiating tool (CAD/CAM/CAE) loaded onto the user's desktop or laptop.Product Structures allow for all information about a product to be broken down and grouped in alogical fashion. Meta information (data sheets, supplier lists, etc.) can be stored in the componentpart to which it applies. This eliminates the need for running additional queries to track down neededinformation. By using the task bar, the user can switch between different viewers to see various metainformation. The 3D model viewer can be used to locate a component in the Product Structure Tree.Once the component is located, the user can easily switch to the RTF document viewer to access alldocuments associated with this component. By then switching to the OLE viewer the user can viewan Excel spreadsheet of sales records for this component.

2.6.5 Sherpa PDM@NetPDM@Net has been developed to specifically allow the connection of multiple sites and theextended enterprise using private lines or the Internet/Intranet. It allows the user to browse, searchmetadata, create, modify, delete, save-as, reserve, unreserve, check-in, check-out and Copy-outfiles, Create Work Authorizations and ECRs and ECO record types, signoff and route (ad-hoc)information to other PDM users.For product structure, the user can browse structure, references, where-used, change structurethrough attach and detach. For lifecycle management browse and approve, reject, promote, demote,add signature, remove signature, reassign signature for ad-hoc routing. PDM@Net is able to View/Annotate using Rosetta's viewing tool. It is compatible with both Sherpa/IPD and Sherpa/PIMSenvironments. HTML and JAVA is used to configure specific requirements. PDM@Net contains aset of HTML screens which support data models for Sherpa/IPD & Sherpa/PIMS.


CONFLOW.97.10 79

Operations On Record Files• Search for record objects - provides the ability to find a data object, or set of data objects

matching a certain criteria in the database.• Browse metadata - provides the ability to view existing data object metadata. All metadata

associated with the record object is viewable including record table metadata relatedinformation. The user will see the history & revision history of the creation and last modificationof a data object.

• Create/modify/delete - allows the creation of new documents, work authorizations and newattributes. Users may modify objects, change attributes and modify reference & file attributes aswell. Delete allows the user to remove a specific data object.

• Check-out and check-in - Checkout brings the data object to the user and copy the files to alocal storage for modification. Check-in adds the modified file back to the data object. Tools willbe launched on checkout.

• Save-as - allows the user to create a copy of an existing data object.• Add file/remove file - allows the addition of file to a record object, including the ability to set file

metadata attributes. Files may have a tools associated with them. Remove file provides the userto remove files from a record object.

Operations On Product StructureThe user is able to browse structure with a fully supported Java graphical browser. This browsersupplies the display of the metadata for records and references.• Browse references - allows users to see the reference information in various levels of structure.

Supports both Java and HTML table format.• Browse where-used - allows users to see the reference information by looking up the structure• Explode/where-used - provides the ability to explode product data. Filtered where-used

provides ability to do a where-used on product data.

Operations on Changing Product Structure• Attach - creates a reference form an existing data object to the current data object. Use may

add reference attribute information.• Detach - removes a reference from an existing data object to the current data object.

Operations On Lifecycle Management• Browse lifecycle - view the lifecycle for a given data object in both graphical JAVA applet &

non graphical form. This function shows the approval and rejection history of each data object.All the information is available for the promotion and demotion of the object as well.

• Changing lifecycle - provides configuration integrity rules. No operation is permitted to violatedata synchronization rules.

• Approve/reject - checks off a check on the lifecycle, auto-promote on approve is supported.• Ad hoc routing - includes add/remove/reassign signature for ad-hoc routing.


CONFLOW.97.10 80

Sherpa/PDM@Net is able to View/Annotate using Rosetta's PreVIEW viewing tool. This product iscompatible with both Sherpa/IPD and Sherpa/PIMS environments. Users without native toolsloaded on their clients can be full participants in product development by utilizing this tight integrationto Rosetta

2.6.6 Sherpa/SFC (Foundation Class)Sherpa/SFC is an object-oriented class library that complies with the industry-standard objectcommunication protocols, CORBA (Common Object Request Broker Architecture) and OLE(Object Linking and Embedding). It is also the infrastructure for Sherpa/WORKS.

Sherpa/SFC Features include:

RECORD base class

Over 200 methods and attributes help developers handle fundamental data vaulting, workflow, andobject relationship manipulation:

Vaulting methods include Check-In, Check-Out, Cancel Check-Out, Is Checked-Out, Copy-Out,Create, Delete, Modify, Reserve, Unreserve, Is Reserved, Save, and Update.

Workflow methods include Approve, Reject, Demote, and Promote

Configuration management support for structure browsing and integrated change management,including up & down traversal for explosions and where-used. These configurations may include dateand/or serial effectivity effective on the end item, configuration item or affected item.

FILE class

It has its own attributes and methods which can be contained within RECORD objects to enabledevelopers to add and remove data files from RECORD objects

REFERENCE base class

Provides attributes and methods to allow connecting references between RECORD objects

MESSAGE CATALOG class

Allows access to locale-specific message catalogs to enable applications developers to displaymessages in a user's local language

2.6.7 Sherpa/Integrator Mentor Graphics

Provides supported interface between SherpaWORKS and Mentor Graphics' Falcon Framework®,maintaining concurrent design environment provided by the Mentor Graphics Design Manager™(DMGR).

Specifications• Secure storage and access control to Mentor Graphics design data and related records, attached

files, and attribute data including: - Project/Product records- Viewable images- Derivedmanufacturing files- Bills of Material


CONFLOW.97.10 81

• Management of file and data relationships and dependencies• Engineering change and release control• Inexpensive enterprise viewing of files• Product Data Management operation support including:- check-in- check-out- cancel check-

out- checkpoint- copyout

2.6.8 Sherpa/Integrator for Pro/ENGINEERThis is a supported interface between Sherpa and Pro/ENGINEER, with full configurationmanagement & version control for Pro/E design files giving support for both Sherpa/IPD andSherpa/PIMS data models.Features• Secure storage for Pro/ENGINEER files• Management of object associativity and dependencies• File access control• Release and control of objects and grouped objects• Cascaded operations on assemblies, including Check-In, Check-Out, and Copy-Out• Parameter transfer• Specific check-in• Level-by-level checkout• Auto-numbering• Support for suppressed parts• Family table & generic model support• LAYOUT file support• Locking (reserving) of objects• Reserving of objects during modification• File search options, by owner, part number, etc.• Full functionality of Pro/ENGINEER• Full documentation and support• Sherpa/IPD data model compliant

2.6.9 Sherpa/View for RosettaThe Sherpa/View for Rosetta manages electronic handling , distribution and review of documents,charts, and drawings, including 3D CAD models.

Sherpa/IPD Integration

Within the Sherpa/IPD environment, Rosetta PreVIEW PDF and PreVIEW Conference provide thefollowing functionality:• Viewing files attached to record.• Viewing files from several records.


CONFLOW.97.10 82

• Marking up single-page file.• Marking up multi-page file.• Saving fast viewing images.• Automatic creation of PDF files.• Printing files directly from Sherpa• Printing files with control stamps.

With Sherpa/View's integrated graphical user files are quickly viewable via the View button, withmanipulation via familiar drag-and-drop and copy-out procedures. Markup tools are also drag-and-drop activated, with automatic commitment of changes. When accessing multiple files simultaneously,access is provided by selecting from among viewlist entries. PDF files are created on demand. Filesmay be printed directly from Sherpa by making viewlist entries and activating the print tool; whencontrol stamps are requested, users are prompted to enter custom stamp content.

Sherpa/PIMS Integration

When integrated within the Sherpa PIMS environment, Rosetta PreVIEW and PreVIEWConference modules provide the following functionality:• Viewing files attached to record.• Viewing files from several records.• Adding files to view session.• Marking up a single-page file.• Marking up a multi-page file.• Printing files directly from Sherpa.

Rosetta for Sherpa/PIMS features a graphical user interface which is easy to learn and use. Whenselecting and viewing, for example, access is provided via View button, and familiar drag-and-dropor copy-out procedures. A separate markup menu provides access to marking functionality, with theability to create and revise marking before committing to them. Printing of files is triggered via drag-and-drop on the Print button.Benefits:

• Makes Rosetta's viewing and markup capabilities readily available within the Sherpaenvironment.

• Standards-based: Leverages Adobe PDF technology for viewing of both textual and engineeringdocuments with their original formatting intact.

• Reduces paper: On-line viewing and markup reduces the time and expense of handling paperdocuments.

• Decision-support: With easier, faster access to information, users can make better decisions --and respond more quickly to change.

• Enterprise competitiveness: Facilitates the flow of information -- through the product lifecycleand across the extended enterprise.


CONFLOW.97.10 83

• Future-ready: Object technology and architecture make it easy to add new functionality as itbecomes available.

• Offers Sherpa/PIMS and Sherpa/IPD users easy access to on-line view, markup, print andconversion capabilities of Rosetta's PreVIEW product family.

• Facilitates viewing of text and graphic data on popular PC and workstation platforms -- withoriginal formatting intact.

• Allows users to access electronic annotation capabilities without leaving the Sherpa PDMenvironment.

• Eliminates roadblocks to faster, better design, revision and project management.

2.6.10 Sherpa/REPORTSSherpa/Reports provides three applications in one integrated solution:Safari Report Writer generates reports under Windows 3.1, Windows 95 and NT. Safari servessmall and medium-size reports at the client level. Once reports are generated, they may be saved tofile or printed.RPW is a character-based report writer for UNIX platforms. It accommodates large reports thatcannot be executed on a PC. A multi-level bill of materials for an aircraft, for example, may beseveral hundred pages long and take hours to generate. Such reporting may be handled mostefficiently in batch mode at the server level.UDMS Server is a UNIX server-based data dictionary and reporting engine which runs inconjunction with Sherpa/Server. UDMS manages user access to data and report definitions as wellas the filtering, sorting and collection of data.

Object-Oriented Data Dictionary

The UDMS data dictionary contains all specifications referenced by users of the system. Datadefinitions (e.g. record, view, alias) and module definitions (e.g. report, export, extract and graph)are included in the dictionary. Each definition is assigned a unique name and associated securityparameters. The specifications -- called records -- can be automatically extracted from existingsources through the auto-load process, or defined manually. Expressions can be used in the creationof record definitions to establish persistent calculated fields which can be later used in all read-onlyoperations, saving valuable time for users. The dictionary can also contain supplementary informationto assist users in working with the underlying data, such as field-level help text and validation. Up to32 individual records can be combined to create views, which logically link the values in separaterecords to form a virtual relational table which may be manipulated using UDMS tools. Views canjoin information from multiple heterogeneous data sources simultaneously -- allowing users tocombine data from indexed, hierarchical and relational databases.

Client/Server Efficiency

The combination of Safari and UDMS Server enables Sherpa/Reports to handle data collection andsorting at the server level. This minimizes the workload on the desktop processor and reduces theamount of information placed on the network. Once data is consolidated, it moves to the clientwhere it may be further filtered, sorted and summarized using Safari's scripting language.


CONFLOW.97.10 84

Query Control and Security

Sherpa/Reports allows user to establish query limits for both read and qualification, and these limitscan vary by department, group or individual. Because users access data through the centralSafari/UDMS dictionary, it is easy to add an additional layer of data security onto existing databasemechanisms. Unlike ODBC interfaces, which typically require multiple passwords for separate datasources, Sherpa/Reports requires only one password for access to its dictionary and associated dataretrieval mechanisms.

Extensive Reporting Capabilities

Sherpa/Reports provides users with a broad range of report types and formats for all kinds ofroutine and special-purpose reporting.

Pre-configured reports

Out-of-the-box reporting capabilities enable you to generate a variety of pre-configured decision-support documents, including reports, which monitor and summarize:• Work Authorization Reports• Engineering Change Requests• Engineering Change Orders• Bills of Material• Bill of Material Difference Reports• Where-Used information• Vendor information• Approved Part List• Contract Status Report


CONFLOW.97.10 85

2.7 WorkCenter (AUT97)

AUTODESK's WorkCenter software is a Windows-based client server product for managingtechnical documents and automating workflow, focused on the needs of the design team.

Figure 2.28. WorkCenter screen (AUT96)

2.7.1 General features

Technical Document and Workflow ManagementWindows-based WorkCenter® software is an easily customized system for managing technicaldocuments and automating workflow within design teams. The product fully integrates with forWindows, providing a seamless and productive environment for the AutoCAD user.

Multiuser Storage and AccessWorkCenter software stores and organizes documents in a central storage facility, or "vault," andprotects them from unintended or unauthorized use and misuse. Allows access to documents in thesystem only through WorkCenter and WorkCenter-integrated applications. Treats as new revisionsdocuments that are retrieved for editing. Automatically sets aside documents for archiving. Featuresaccess privileges ranging from open to high-level security. Allows you to vary access rights byindividual, workgroup, document, and so on.

OrganizationWorkCenter gives the user four options for easily viewing information: Workspace lets to see anydocument. Catalog shows all documents in the system. Search allows to locate documents usingselected criteria. In-Box handles user's workflow messages.


CONFLOW.97.10 86

WorkCenter software also lets user group related documents into directory-like hierarchies, calledSmartView folders, and assign descriptive information to folder documents through custom ProfileCards. Easily restructure SmartView folders at any time. List related documents, such as AutoCADXrefs (external references). Use document names of up to 254 characters.

SearchLet the user use Profile Cards to conduct searches based on whatever information he/she has (e.g.,job-creation dates, job numbers). Employ partial search criteria and wild cards. Create and savecustom searches to meet reporting requirements.

Revision ManagementWith WorkCenter user can automatically save, track, and organize all revisions of catalogeddocuments.Specify the maximum number of revisions to be saved online. List particular document revisions,such as all documents edited by a certain user. Ensure, via the Revision Selection Rule, that userswork with the correct revision (one approved for their use) or the most current working revision.

Figure 2.29.WorkCenter document revisions window (AUT96)

Multiformat ViewerWorkCenter software lets user to view files in more than 170 different formats—without checkingout the document and independent of the software application that created it. Viewing does not altera document and can be performed at any time. Viewable file types include word processing,spreadsheet, database, bit map, vector, and archive (.ZIP), as well as DWG, DXF, and HPGLformats. The Previewer places a "live" preview of any type of document on a Profile Card. TheCAD Viewer includes layer and block filters, measuring utilities, and display-list capabilities.


CONFLOW.97.10 87

Redline and Compare CAD FilesRedline DWG, DXF, and HPGL files onscreen, without checking out or modifying the original. Saveredlined documents and link them to the original documents. Use tools such as lines, circles, leaders,cloud-shaped polylines, rectangles, sketches, text, and "note cards" when redlining. Highlightdifferences across DWG file revisions with the DWG Compare Utility.

Workflow AutomationWorkCenter software can automate workgroup task assignment, routing, and response.

Work Request and Document RoutingYou can route documents in parallel (everyone at once) or serially (one person, then another) andattach working and reference-only documents.Include task instructions, check-off responses, anddue dates. List and modify outstanding workflow requests. Save partially completed requests(including distribution lists, reference documents, and instructions) as templates, and reuse them later.

Figure 2.30. WorkCenter Work Request Dialogue Box (AUT96)

Routing ResponsesWork requests appear in a WorkCenter user's In-Box. The user can then complete the request, holdor reject it, or ask for more information.Electronic sign-offs (approvals) advance documents to the next design phase; sign-offs are tracked.Responses to work requests can contain comments; responses are tracked.

NotificationsWorkCenter automatically informs users when a specified action—such as check-in, check-out, orapproval of a document—has been taken; notification appears in the user's In-Box.


CONFLOW.97.10 88

Figure 2.31. WorkCenter User/Group setup dialog box (AUT96)

Figure 2.32. WorkCenter User/Group configuration dialog box (AUT96)

AutoCAD Software IntegrationWorkCenter fully integrates with AutoCAD software for Windows. Readily access all storeddocuments from within AutoCAD. Track and manage two-way relationships between Xrefs andblock-source files.Open related files (such as an Xref or a block source) from within WorkCenter orAutoCAD. List all blocks and Xrefs within a specified AutoCAD document, even without AutoCADsoftware. List all AutoCAD documents containing a specified block or Xref.


CONFLOW.97.10 89

Custom CapabilitiesOrganize documents using predefined, industry-specific category fields and terminology, orimplement own criteria. Make use of three custom templates: Mechanical Design; Architecture,Engineering, and Construction; and Standard. Set and save user-interface elements (e.g., ProfileCards, column headings) and system behavior. With the Customization Template Capture feature,save a custom template for duplication during the installation of another WorkCenter system. Systemadministrators can standardize tools and Profile Cards system wide.

Ease of UseEmploy ODMA (open database management API-compliant programs for opening and managingfiles, without customization or command interception. Access WorkCenter software directly from theOpen command in most Windows applications. Enjoy the fully Windows-compliant, user-intuitiveinterface. Access from one CD-ROM client/server software for all platforms. Benefit from onlinedocumentation and Help. Identify different applications as editing tools for different document types;organize documents by type. Bulk-load groups of files. Developers benefit from an API (applicationprogramming interface) that supports independent-developer applications.

2.7.2 WorkCenter 1.2a Features

Ability to Access Xrefs Directly from the "Vault"Feature:

Users can view related documents, such as AutoCAD® Xrefs, directly from the "vault." Thesefiles do not have to be copied from the vault into the users' workspace.

Benefit:This capability will not only reduce the time required to access a document, but will also speednetwork traffic and reduce storage requirements on the client hard drive.

Multiple-Document Access List EditingFeature:

The system administrator has the ability to select a group of documents and simultaneouslychange the access rights to each of them.

Benefit:Streamlines the administration of access rights.

Multiple-Document Profile Data EditingFeature:

The user can simultaneously change the document profile information for a selected group ofdocuments.

Benefit:Makes it easier to modify or update WorkCenter document information. For example, you caneasily make design-phase updates to a group of documents.


CONFLOW.97.10 90

Support for Multiple Shelf ServersFeature:

WorkCenter Release 1.2a incorporates the enhanced functionality previously available throughthe Extended Edition of Release 1.1. It provides an additional storage manager that allows theadministrator to store documents on shelves on multiple Windows NT Servers on a single localarea network.

Benefits:Distributes the transaction volume, which reduces network traffic and enables more users toaccess the system. Provides additional shelf storage capacity, enabling users to manage a greaternumber of documents.

Enhanced Viewing CapabilitiesFeature:

• The viewer is equivalent to Autodesk® View Release 1.1 and includes the followingenhancements:

• Support for special characters.• Support for AutoCAD Release 13 tolerance objects.• Frozen layers in AutoCAD Release 13 viewports will not be visible.• AutoCAD SHX fonts, including pathname.• Embedded text-formatting codes.• Raster image rotation.• Support for viewing Mechanical Desktop™ drawings.

Benefit:Users will be able to view AutoCAD Release 13 drawings better, except for related object-snapfunctions.

Application LinkingFeature:Application Linking allows you to open and save WorkCenter documents directly from within anyprogram that uses the Windows Common Dialog interface. This feature (previously called PassiveIntegration), which was provided in earlier WorkCenter releases for Windows 3.1x, is now fullyfunctional in the 32-bit Windows NT environment. In addition, a new interface that simplifies theuser's control of Application Linking also allows precise control over WorkCenter software'sAutoCAD integration and ODMA-based application linking.Benefits:

Customers can use a variety of programs and can open and save files via WorkCenter, insteadof using another file system. Customers can easily specify which programs link to WorkCenterand can customize the associated link characteristics.

Addition of Platform-Specific InformationFeature:

Platform-specific information for Windows 95 and Windows NT 4.0 clients has been added tothe printed and online documentation, which allows all client platforms to be covered with asingle set of documentation.


CONFLOW.97.10 91

Benefit:Users will be able to operate WorkCenter on any client platform using a single set ofdocumentation.

2.7.3 WorkCenter for the Web

WorkCenter for the Web, a new Internet server software product, is the latest addition to theAutodesk Data Management product family, which also includes WorkCenter and Aotodesk Viewsoftware. Designed to extend the reach and impact of the user's WorkCenter-managed design dataand drawings, WorkCenter for the Web provides controlled access to drawings and data organizedin a WorkCenter vault—without losing any of the advantages of WorkCenter-based security. Easyto install, with a simplified user interface, WorkCenter for the Web makes it possible for authorizedusers-no matter where they are or which platform they use-to search, view, and copy WorkCenterdrawings and related documents. All they need is access to the Internet or the corporate intranet anda Netscape Navigator or Microsoft Internet Explorer browser.

With WorkCenter for the Web, the extended design team can stay in touch with a design project asit evolves. Its members can Conduct simple or advanced searches. Access stored searches. View,zoom, pan, or copy any design document, including all layers. View profile cards based onWorkCenter profile data. Copy out a drawing and all its Xrefs into one self-extracting file.

WorkCenter for the Web utilizes WorkCenter Log-on username and password, as well asWorkCenter revision selection and access control. To further enhance the ability to work with DWGfiles, team members can configure browsers to work with the included Autodesk View DwgXplugin. To view DWF files, the new Internet file format from Autodesk, they can download theincluded.

Complete Solution

WorkCenter for the Web, along with Windows based WorkCenter software, Autodesk View, andAutocad software, is the complete Autodesk data management solution.

WorkCenter is an easily customized system for managing technical documents and within small orlarge design teams on the same LAN and platform. It lets a workgroup flexibly organize documentsaccording to individual needs; checks files in and out of secure, central storage; and effectivelymanage revisions over time. Its workflow-automation tools facilitate electronic notification,distribution, and approval. WorkCenter software also offers extensive CAD redlining and viewingcapabilities and enables viewing of more than 100 file formats, including text, spreadsheet, graphics,database, and CAD files. Fully integrated with AutoCAD software and compatible with AUTOCADLT software, WorkCenter can manage virtually any electronic document.

Autodesk View provides quick, accurate access to DWG files, plus more than 200 other fileformats, including most popular database, spreadsheet, word processor, and presentation formats,so users can view, redline, and annotate CAD drawings and raster images. WorkCenter for the Webusers can copy out files they want to manipulate and use Autodesk View to view and redline.


CONFLOW.97.10 92

2.7.4 Key benefits of WorkCenter

• WorkCenter organizes user's technical documents, making all the information available to theentire design team.

• It includes all the tools necessary for searching, retrieving, and sharing these documents.

• WorkCenter software's revision control capabilities assure that users always have access tothe correct revision of a document, independent of where they work in the overall designprocess.

• WorkCenter document-level configuration management capabilities allow you to organizeeven the most complex design documents while maintaining them historically, helping you tomeet ISO 9000 requirements.

• WorkCenter Workflow automation capabilities provide document routing and electronicsign-off capabilities—fully linked to the document management facilities. This gives designteams the ability to move documents through their process and provide audit trails and statusinformation on their progress.

• WorkCenter is fully integrated with AutoCAD software to streamline operations—users canpull up WorkCenter documents from within AutoCAD and AutoCAD can be launched fromwithin WorkCenter.


CONFLOW.97.10 93

3. Selection and implementation of a PDM system

A brief overview follows on the practical advises and recommendations of industrial companies,concerning PDM project preparation, PDM system selection and system implementation. The topicshave library wide references, here the basic and typical clues are summarized only, pointing out thecommon and general nature of PDM technology.

3.1 Preparations for a PDM Project

Many successful organizations progressed through the same basic pre-implementation steps in thepast. The experiences recommend a serial set of (many times overlapping and/or repeating) activities(RUD95, MIL96).

Assemble a Core Team.

The same core team of people is needed throughout the process to drive the implementation,maintain continuity, and ensure everyone has an input. Don't make the group so large that it getsdelayed in bureaucracy, but have all areas adequately represented including both user groups andinformation technologists (a group of 4-5 people is recommended). User members should includepeople who can understand and represent the breadth of the organization's product development andproduction processes.

Educate the Organization.

Education is a long-term, continuing process and is particularly important at the outset to understandbusiness issues addressed by PDM The core team should pursue many activities. Participate incourses, attend industry conferences, read articles, and ask questions. Learn not only abouttechnology, but about which companies (particularly the competitors) are using PDM, what benefitsthey're obtaining, what problems they're having, and what kinds of management approaches they'reusing. Spread the knowledge gained by the core team into the rest of the organization.

Establish Objectives.

Now establish objectives in terms of why the organization wants to get into PDM. Ask what taskstry to accomplish and what problems you're try to solve. Objectives should be business-oriented,broad organizational goals such as reducing turnaround times or lowering costs. In many cases,objectives are already known, since they were the motivation for considering PDM in the first place.At this point, determine metrics to gauge PDM performance. These must be measurable parameterssuch as cost to process an engineering change order or time to develop a product. Metrics arecritical and should be uniquely determined to reflect critical success factors for the business.


CONFLOW.97.10 94

Create a System Vision.

A vision is now created for the technology needed to meet the objectives. Essentially, this is aroadmap that outlines the scope of the system (how big it is and what it covers) with a realistic list ofmilestones defining the path to take. An important part of this step, and others along the way, is acareful evaluation of work processes at the company with the aim of refining them so workers can dotheir jobs better. If full-scale process re-engineering efforts are underway, this analysis providesvaluable input clarifying PDM's role in enabling the improved processes.

Analyze Costs and Benefits.

At this point, a general cost/benefit analysis can be performed to determine if the time and expenserequired are justified. Costs must include not only software and technical infrastructure, but alsocustomization, installation, training, education, business process impacts, meetings, travel, etc. Besure to include internal costs as well as external expenditures.

Define Requirements.

Determine in detail how the system should perform to meet the objectives and satisfy the vision.Typically, this includes individual capabilities (e.g., workflow capabilities, data/document accesssupport, integration with CAD, bill of material needs, etc.) that determine which type of PDMtechnology is appropriate. Also define the infrastructure needed including networks, E-mail, desktopcomputers, and servers. The scope of the implementation should be clear, including location anddistribution of users.

Select a System.

Having defined what the system will do, start evaluating products and vendors to see how theircapabilities match to the needs. A detailed cost/benefits analysis should be done at this time. Inselecting the system, meet at length with vendors. Remember that this is not only the buying off-the-shelf software but rather are entering into a long-term partnership with a company that will help tailorthe system, continue to improve it over time, and provide critical applications support.

Ask for references - then follow up.

Visit companies that have made the leap to PDM. It's the best way to confirm how a vendor and itsproducts and services stack up. If a supplier can't supply references, then there emerges a seriousconcern about its ability to deliver successful solutions.

Launch the Implementation.

Now you can purchase a system and put it in place. Start with a pilot system on a limited basis,expand to a larger production system when kinks are worked out, then integrate PDM into the workprocess. Continually monitor metrics to keep the process on track.


CONFLOW.97.10 95

3.2 Choosing the PDM system

The user should understand his/her own specific requirements and a careful match is needed with thecapabilities of the PDM product offered by the suppliers. The following areas are the Major factors(CIM96):

Differences in the products:

• Architecture Is the system easy to extend, is it open, can it evolve over time and accommodatethe needs?

• Distributed Environment How does the system support distributed implementations, and is itable to be extended over time as the user's implementation grows?

• Functionality How well and in what manner does the system support the functions that areimportant to the user, both now and throughout the implementation?

• User Interface If users can not (or will not) use it, the system is useless; how easy is the systemto use, and how can the interface be tailored to fit different kinds of users?

• Heterogeneous platforms Is support provided for platforms that are important to the user?

• Application interfaces What interfaces are provided already, are they robust enough, what helpis available from the supplier and what tool kits are provided for extensions?

Company differences:

• Industry position What role does the supplier play in the PDM industry, are they a leader or afollower, are they heading in a direction that corresponds with yours?

• Industry focus Does the supplier understand the user's industry sector and its unique needs, orare they continually trying to put the buyer into a different mould?

• Geographic focus What is the geographic scope of the planned implementation and what kindof support is needed in various locations, and is the support available ?

• Distribution and support How does the supplier support their product, what kind of servicesare offered, and what do the user want and need?

• Market experience How much experience does the supplier have already, can they lead thebuyer through the difficult spots, or is he/she going to be their first client- perhaps being used as atraining ground for the new support team?

3.3 Introduction strategies

At least three strategies have been identified (PIMA96). The different complexity levels of a PDMintroduction are shown in Figure 3.1


CONFLOW.97.10 96

Figure 3.1 Strategies for the introduction of the total PDM technology

First strategy is to let the system manage the required documentation for a project, and graduallyextend the use to configuration management and standard workflows like engineering changemanagement and release processes. The advantage of this method is that the full functionality of thePDM system can be implemented in a relatively short time. A risk with this strategy is that the systemmay not be completely developed to give full support as the complexity increases. This strategy isalso probably most cost demanding, since much customization is required.

Second strategy is to start with the configuration management at first, and add the documentmanagement and workflow functionalities later on. This strategy is used when the primary goal is tointegrate PDM with CAD systems.

Third strategy is to transfer the companies' archive to digital format, and thereby enable a fastaccess to the documentation, which is illustrated as the Life Cycle Data Management in Figure 1.One disadvantage with this method is that the PDM system can end up as an ordinary databasesystem. A more complex approach is to use the workflow functionality for the distribution ofdocuments.

A recent study performed in Sweden shows that the probably commonest way for the introduction isto let a PDM pilot project apply one of the above mentioned strategies and evaluate benefits andmistakes, so that the full implementation can be performed as smoothly as possible. The level ofcomplexity for the pilot project is incrementally increased together with the PDM maturity of theusers and the development of the product. Regardless which strategy is chosen for the introduction,the documents can be kept in the PDM system for the life cycle management of the productdocumentation.


CONFLOW.97.10 97

References

AUT96 'Autodesk WorkCenter® and ISO 9000. Autodesk White Paper' ©Autodesk, Inc.1996 http://www.autodesk.com/support/techdocs/center.htm

AUT97 'WorkCenter®' ©Autodesk, Inc. 1997http://www.autodesk.com/products/datamgmt/workcent/

CIM96 Choosing the right PDM Product' © CIMData 1996http://www.std.com/Newbury/CIMData/pages/choosing.htm

COM97 'OPTEGRA® Revision 2.0 (overview)' © Computervision Corporation 1997http://www.cv.com/CV/Solutions/PDM/datasheets/ov9012.html

DEM97 Jane DEMMER: 'Using Pro/PDM & Netscape for Geometry Management'Presentation at Pro/USERS' Conference Orlando 1997.

GAS96 Bill GASCOIGNE: 'PDM: The Essential Technology for Concurrent Engineering' ©PDM Information Center 1996 http://www.pdmic.com/articles/artetfce.html

HEW96 'Understanding Product Data Management' from Hewlett Packard Company, ©PDM Information Center 1996 http://www.pdmic.com/undrstnd.html

MIL96 Ed MILLER: 'Getting Started in PDM' ©CIMData 1996http://www.std.com/Newbury/CIMData/pages/emcaep13.htm

MIL97 Ed MILLER: 'An Inside Look at Product Data Management' ©CIMData 1997 http://www.std.com/Newbury/CIMData/pages/pdm-cae.htm

PHI96 Mike PHIPOTTS: 'The Benefits of Product Data Management' © CIMData1996 http://www.std.com/Newbury/CIMData/pages/benefit1.htm

PIMA96 Peter PIKOSZ - Johan MALMQVIST: 'Possibilities and Limitations when UsingPDM Systems to Support the Product Data Process' Chalmers University ofTechnology, Göteborg, Sweden 1996http://www.mvd.chalmers.se/~pikosz/research/NordDesign96/pdm96.fm.html

PRO97 'Pro/INTRALINK™ Functional Overview' © Parametric Technology Corporation1997.

PTC95 'Pro/PDM Product Information' © Parametric Technology Corporation 1995http://www.ptc.com/products/info

ROGO97 Christian ROTHER - Michael GOLTZ: 'Workflow Management of EngineeringChange Process. A Concept, Based on the Product Data Management Facility ofthe SAP R/3' Diplomarbeit/Dissertation August 1997. Technische UniversitatClausthal Institut für Maschinenwesen/University of Wales, College of Cardiff,School of Engineering, Division of Systems Engineering


CONFLOW.97.10 98

RUD95 Michael RUDY: 'Ten Steps to Ensuring a Successful PDM Project' ©PDMInformation Center 1996 http://www.pdmic.com/articles/art10stp.html

SDR97 'Metaphase Series 2' © Structural Dynamic Research Corporation 1997http://www.sdrc.com/pub/catalog/metaphase/

SHE97a 'Sherpa WORKS97' © Sherpa Systems Corporation 1997http://www.sherpa.com/products/

SHE97b 'Challenges in Implementing a World-wide PDM Solution' © Sherpa SystemsCorporation 1997 http://www.sherpa.com/successstories/morton/

SHEA97 Allison SHERIDAN: 'Mission Debriefing. - Highlights of Pro/USERS' 1997Conference, Orlando http://www.prouser.org/97conf/official.htm

WOR95 'CMS' © Workgroup Technology Corporation 1996http://www.workgroup.com/cms.html

WOR97 'News: Product Release CMS 7.0'© Workgroup Technology Corporation 1997http://www.workgroup.com/cms7ann.html

CON FLOW - TU Clausthal · A pragmatic overview of Product Data Management This chapter gives a...

Documents

Transcript of CON FLOW - TU Clausthal · A pragmatic overview of Product Data Management This chapter gives a...