SISTEMI ZA BRZI RAZVOJ PROIZVODA - masfak.ni.ac.rs · Prof.dr Dragan Domazet Simultano projektovanje proizvoda - PDM sistemi 4 - 2 Concurrent Engineering Technology 1 Product & Process

Prof.dr Dragan Domazet Simultano projektovanje proizvoda - PDM sistemi 4 - 1

SISTEMI ZA BRZI RAZVOJ PROIZVODA

SIMULTANO PROJEKTOVANJE-izvodi sa predavanja-

Treće predavanje

Prof. Dr. Dragan Domazet

KATEDRA ZA PROIZVODNO MAŠINSTVO


Concurrent Engineering Technology

1 Product & Process Models

2. Model Data Exchange and Sharing

3. Virtual Teaming

4. Workflow Management

5. Product Data Management Systems • Functionality of PDMSystems

• The Architecture ofPDM Systems

• Implementation ofPDM Systems

• Future Directions


Product Data Management Systems

Functionality of PDM Systems


Problem Addressed

– there are a lot of data & documents– used by many people in different

functions– used by many computer programs

and on different computers– has several different definitions

(representation models) – exists in many different versions– has multiple relationships and

meanings,– may need to be maintained for many

years


The Engineering Environment Without PDM

• Data is lost and not secure• Data cannot be found. Time is

wasted searching for data• Data does not correspond to

the product• Unnecessary copies of data

are maintained, data is not shared.

• Copies of data conflict. Data ownership is not clear.

• Islands of automation abound.

• Inter-functional communication of data is slow

• Transfer of data on paper is slow

• Review and approval

• Engineering change management is too slow

• Engineering changes are not controlled or coordinated

• Versions are not properly managed

• Configuration information does not correspond to reality

• Technical manuals are out of date

• Tractability cannot be maintained

• Leads times are unnecessary long

• Project managers lack up-to-date status


Solution: Product Data Management

• PDM encompasses the integration and management of:– processes, – applications, and – information (documents, files, databases)

that define products across distributed systems and various media in a company

ProcessesApplications

Data


Objectives of PDM (EDM/EWM)

• Objectives:– to improve product quality– to reduce lead times

• Approaches:– to increase the productivity of individual engineering

activities– to improve the coordination between activities through

concurrent engineering• Factors that make both data and workflow more

difficult to control:– High volumes of data easily produced with computers– Increased customization of products– Increased role of suppliers in engineering process– Pressure to improve engineering productivity


PDM Definition

• PDM is a tool that helps the enterprise, engineers, and others to manage both data and the product development process.– Keep track of mass of data and information required to:

• design,• manufacture or build, and • support and maintain products.

• PDM is a software-based technology that is used to manage all– Product-Related Information and – Product-Related Processes

Data Processes


Data & Process Integration

• CAD/CAM/CAE files• bill of Material (BOM)• configurations• business Documents• sales Order• spreadsheets• cost and vendors status• etc

• procedures• rules and routines relative

to approvals• authorizations• security• business standards and

practices• workflow• organizational relationship

and etc

Data Processes


Why To Use PDM?

• Control of engineering data• Quality of engineering data• Reuse of engineering• Security of engineering data• Availability of engineering data• Control of engineering workflow• Support of new engineering

strategies


Issues Resolved with PDM Systems

• Diversity and volume of data• Multi-user, multi-organization environments• Multi-application, file-based environment• Multiple data definitions• Multiple representation of data• Multiple versions of data• Multiple relationships• Meaning of data• Life cycle data• A complex but logical environment


Functionality of PDM Systems• Encompass all data associated with products• Support of all the processes in the cycle• Linking people, processes, and products• Define the responsibilities and data access of

each person in an organization• Link groups and individuals to the appropriate

process steps that make up the overall life cycle of a product

ProcessesProcesses

Product DataToolPeople


Benefits

• Shorter product development lead times• Increase productivity• Significant time-to-market compression• More and new product are introduced• Cost saving

– optimized the re-use of parts– reduce engineering changes– reduce paper and administration tasks– high-speed electronics data sharing


PDM Functions

Electronic Data Vault Meta Database

Administration

Product Structure Management

Configuration Management

Workflow Management

Classification & Retrieval

Project Management

Communication & Notification

Data Transport & Translation

Viewing & Markup

IntegratedApplications

Use

r Int

erfa

ce


Electronic Data Vault

• Electronic data vault functions:– store and manage copies of application files– security/data access control– Keeping a single master copy of the data

• all changes to it can be monitored, controlled, and recorded,

• ensuring the integrity of the data at the time it is required• Make right data available automatically• Duplicate copies are distributed

PartCAD File Process

PlanNC

ProgramsProduct

Documents

Other Data(BOM etc.)


Electronic Data Vault

• Electronic data vault functions:– store and manage copies of application files– security/data access control

• Two approaches:– linked approach:

• files are are managed without first moving them in a centralized location - only meta data are centrally located

– managed approach:• files are kept in a centralized location and copied to

locations where needed


Managed Data

Data ItemsData Itemsreferences

PartCAD File

ProcessPlan

NCPrograms

ProductDocuments

Other Data(BOM etc.)

records


Folder

Dat

a Fi

les

Data Repository

Meta Database

• Similar to a card catalogue in a library– stores information where the files (documents,

CAD/CAM files) are physically stored– metadata = data about other data– stores also attributes about files

Folder

Dat

a Fi

les

Data RepositoryFile attributes:• file name• version• creation date• location• owner ..

PDM Server

Meta Database

pointer


Meta Database

PDM Server

Check-in Operation

Folder

Dat

a Fi

les

Data Repository

Transfer ofData File

PID

Check-in Request (PID)

• Access &changecontrol

• Versionmanagement

Version graphs

put reference


Meta Database

PDM Server

Folder

Dat

a Fi

les

Data Repository

Check-out Operation

PID

Check-out Request (PID)

Transfer ofData Item Copy

• Lock dataaccess

Check-out


Workflow Management Functions

• Notify users of work to be done• Change ownership of an object• Examples: design change process

DesignerDesigner

DesignDesignManagerManager

DrawingDrawing

11

ProcessProcessPlannerPlanner

ReleasedReleasedDrawingDrawing

22

33

PurchasingPurchasing


Workflow Management

• Controls and coordinates the engineering process

• Manages the engineering change process and provides version management

• Assigns tasks to individuals, informs them of the resources to be used and the procedures to be followed, initiates the associated actions

• Distributes data and documents to the individuals as needed


Workflow Management

• Addresses:– the impact of tasks on data,– the flow of data between people, and– tracking of all events that happen

• creation, update, deletion, distribution, release

Activity-1 Activity-2 Activity-3

Tool-1 Tool-2 Tool-3

DB-1 DB-2 DB-3

Workflow Management System


Workflow

• Workflow definition:– the automation of a business process, in whole or part,

during which documents, information or tasks are passed from one participant to another for action, according to a set of procedural rules

Activity 1 Activity 2 Activity 3info infodoc doc

start

doc doc

endBusiness Process

Work Flow Management System ProcessDefinition

Application Application Data


Terminology

Business ProcessBusiness Process

Process DefintionProcess Defintion

ActivitiesActivities

ManualActivitiesManual

ActivitiesAutomatedActivities

AutomatedActivities

Workflow ManagementSystems

Workflow ManagementSystems

Process InstancesProcess Instances

Activity InstancesActivity Instances

WorkItems

WorkItems

InvokedApplications

InvokedApplications

is managed by

is defined in a

composed of

which may be

or

used to create & managevia

include on or more

which include

andor

tasks, docs,info tools, applications


Process & Worklist Structures

A

B

CD

A

B

CD

A

B

CD

A

B

C E

D

A

B

C E

D

Work List 1Work Item 1Work Item 2Work Item 3

Work List 2Work Item 21Work Item 22Work Item 23

Process Definitions Process Instances Worklists

A

B

A1

A2

B1


Workflow Interoperability Scenarios

Process A Process BChainedServicesModel

Process A Process BNested

(Hierarchical)Sub-processes

Model


Workflow Interoperability Scenarios

Process A Process B

SynchronizationPoints

A1

A2

B1 A3

B2

Conected Indiscreet (Peer-to-Peer) Model

ParallelSynchronized

Model


Classifications of Workflows

• Production Workflows (e.g., PDM)– involve repetitive and predictable business processes– access to multiple information systems– ordering and coordination of tasks are automated– retrieve data for making decisions– control task execution with litele or no human

intervention

ComplexTask

SimpleTask

Low HighTask structure

Administrative

Ad Hoc

Production



• Production Workflows– highly structured– process centric– client/server architecture

• Collaborative and Administrative Workflow (Groupware)– groupware with workflow features– project centric– for small-to-moderate size group interacting on shared

database• E-Mail Workflows

– a structured process that involves a small number of steps, but initiated on a random basis

– ad hoc workflow



CSCW

Commercial WFMS Commercial TransactionProcessing Systems

(DDBMS, TP monitors)

Transactional Workflows

• human must ensurethe consistency of results

• have no real knowledgeof the semantic of the informationbeing processed

• access HAD info systems• little or no human intervention• concurrency control and

recovery• have more knowledge of

information semantic

• may involve human• require access to HAD systems• support selective of transactional properties

Human-Oriented

System-Oriented


Product Structure Management

• Build product structures by:– describing the relationships

of parts and – linking them together based

on relationship rules• These links connect:

– components to their use in multiple products,

– people to the products they design, approve, and release

– products to the processes used to create, release, and manufacture them

Product

Components


Product Structure & BOM Views

• Relationship between assemblies and the parts and associated data

• Allows:– a complete bill of material (documents & parts)– associating attributes with both parts and part-to-part

relationships– attributes to part or to specific revisions or to a specific

use of a part– “as-designed”, “as-build”, etc. views

Product Data“as-designed” BOM

“as-build” BOM

Designer

ManufacturingEngineer


Configuration Management

• Specifies a product structure with specific versions of its components.– Configuration rules

• Revision/version control• Effectivity management• “where-used” searches• Multiple bill of material views• Support alternate parts

A

B

C

B.1 or B.2

C.1 or C.2

DE

Alternateparts

Versions


Configuration Design

ConfigurationDesign

Elements

Relationships

Configuration

Requirements Constraints

Resource Mechanism

• Design activity of determining a set of elements and their relationships to create an arrangement that satisfies all the requirements and constraints


Classification & Retrieval Service

• Quick retrieval: Classification needed• Provide for information of similar types

to be grouped together in categories• Each part can be given its own set of

attributes• Classifications may have additional

attribute types (same for every part in the group)


Why Classification?

Supplier nameCostOrder lead time

Attributes for Purchased parts Attributes of Document class

Vendor specificationDrawingSolid model

• Attributes allow easy part/document retrieval– can be automatically extracted from CAD models

• External component libraries, standard parts, design retrieval:– enable greater reuse of existing design

information and increased product standardization


Project Management

• Most PDM systems provide only minimal project management functionality– such as workflow activity status information– trigger communication with late tasks

• Resource scheduling and task breakdown– critical path analysis

• Integration with project management packages


Communication and Notification

• PDM communication services:– sending and receiving data among different

integrated applications (internal & external)– virtual project folders– on certain events, rout information to other

users for review, approval, and comments• Notification of users (messaging):

– notify users when they have a task to perform– or when a change is proposed or implemented– may use interfaces to standard E-mail systems


Data Transport Service

• End users do not need to know where the information physically resides

• Data Transport utilities provide:– security, file backup and recovery, and file

archiving and restoration• Isolate the user from network and

operating system commands:– moving or copying files (triggered by an event

or on user request)– routing files to the appropriate data translators

when necessary


Data Translation Service

• Translation functionality:– data generated by dissimilar

applications will be converted for use by additional applications

– usually a viewing tool is also integrated• Information may be partially lost

Application AApplication A Application BApplication BDataTranslator

DataTranslator


Viewing and Markup Services

• Users can view, mark up, and convert raster images.

• Capabilities:– multiple standard file viewing support

• STEP, IGES, DXF, HPGL, TIFE– native CAD file viewing– annotation or markup of drawings/documents– integration with third-party viewing software


Administration

• Administration functions:– adding users– defining users security level– assigning users to groups– adding data about users– additional utilities:

• network maintenance• applications security administration• backup, recovery, and archive.


Hardware Elements

• Heterogeneous, client/server or network environments

• Server capacity: a single one is not usually enough– must store references (not files) to data that

are stored somewhere else in the LAN– it affects security requirements, performance,

system administration• Communication bandwidth: may be

critical



The Architectureof Product Data Management Systems


PDM System Architecture

SystemAdministration

Manager

Product & FWStructureDefinition

WorkflowControlModule

ConfigurationManagement

Module

Interface ModuleUser

InterfaceInterfaced Applications

Infrastructure

Files

Database

Documents

Database

Information Warehouse ManagerInformation Warehouse Manager

Information Warehouse(Meta Database)

Information Warehouse


Basic Components of a PDM System• Information Warehouse (Repository, Library):

– store a large volume of information on different medium– need not be physically centralized, but provides centralized control

over distributed data with different representation (data) models– information is is various state (in-process, in-review, released)

• Information Warehouse Manager:– controls and manages the information in the Information Warehouse– is responsible for data access, storage and recall, information

security and integrity, concurrent use of data, and archival andrecovery

– works in a multi-vendor distributed computing environment– provides check-in/check-out facilities of files– supports:

• private databases (single-user), • group- and project databases (multi-user linked to project lifetime), and• product databases (multi-user, existing released products)


Basic Components of a PDM System• Infrastructure:

– basic computer and communication hardware and software– local- and wide area networks (LAN/WAN) for both short

transfers (messages) and long transfers (files)– workstations, PCs, data servers, routers, gateways, printers,

scanners• System Administration Manager:

– to set up and maintain the configuration of the system, – to define users, groups, projects, workspaces– to assign and modify access rights

• Interface Module:– supports user queries, menu-driven and form-driven input,

and report generation– provides interfaces for programs such as CAD, document

scanning, electronic publishing, and MRP2


Basic Components of a PDM System

• Product Structure and Workflow Structure Definition Module:– defines the structure of the information and processes to be managed

by the PDM system– the workflow is defined as a set of tasks characterized by resources,

events, associated information, responsibilities, decision criteria, procedures to be used, and standards to be applied

– the workflow may describe the entire product life cycle, or a individual process, with different level of details (may be split in projects)

– the product structure defines all the information describing a product– events mark the end of one activity and beginning of another activity– events must be identified and included in the workflow definition

together with the appropriate notification messages– formal description of the workflow is usually realized worth object-

oriented methodology.


Basic Components of a PDM System

• Workflow Control Module:– controls and coordinates the engineering process– manages the engineering change process and provides version

management– it controls the progress of projects in an event-driven mode– it maintains status information on ongoing projects– assigns tasks to individuals, informs them of the resources to be

used and the procedures to be followed, initiates the associatedactions

– it distributes data and documents to the individuals as needed– when the task is finished it can request a review of the solution and

initiate the next task– monitors the occurrence of events and sends the appropriate

messages– transmits the engineering change requests and change orders– distribute and handle notifications (downstream-upstream info)


Basic Components of a PDM System• Configuration Management Module:

– used to describe and maintain the exact structure of all products in the system throughout their life

– relates components, subassemblies, and assemblies– supports multiple assembly levels, multiple hierarchies, and multiple

membership.– maintains the complete history of the product through design,

manufacture, and delivery and the status of all information– maintains the configuration of a given end product by managing all the

information needed to produce the part (configuration items)– configuration items include all the technical documentation necessary to

specify, build, test, install, operate, and maintain the product (bill of material data, specifications, CAD models, drawings, list, programs, analysis results, reports, part lists, process plans, NC programs and manuals)

– supports multiple versions and alternatives of data– offers the possibility to navigate product structure and traversing the

workflow


Application Program Interfaces

• PDM and applications need to have application program interfaces (APIs)– set of operations that can be called from an external

program to perform a function of an application

EnterprisePDM

PDMInterface

check-in event

check-in requestfile_check-inupdate correspondingenterprise item

CADCADFiles

EnterpriseMetaData

CAD API:file_check-in…..

PDM API:check-in_confirmed...

check-in_confirmed


User Interface

• Refers to the overall look and feel of the PDM application

• This encompasses:– menus, toolbars, dialogue-boxes,…– on-line user guides, context sensitive help– browsers

• Different for different type of PDM users• Current trend: Web-enabled GUI


Types of PDM Systems

• Engineering Document Management Systems:– primarily address alphanumeric data forms/documents,

but can also incorporate drawings as well– scan and capture existing documents– control document access– create new documents– store and retrieve documents– archive, display, manage and modify documents– manage documents pages– distribute documents– print and plot documents– manage the workflow– provide system support– generate reports– provide external interfaces


Types of PDM Systems

• Engineering drawing management systems:– convert existing drawings to electronic form– store and retrieve drawings– set up index/catalog facility– define attributes– provide secure environment for drawings– manage, archive, enhance and display drawings– edit, mark up (redlining), and modify drawings– distribute, print and plot drawings– convert raster data to CAD format– manage the workflow– generate reports– provide system management– provide external interfaces


Types of PDM Systems• Engineering Data Management Systems:

– primarily address digital engineering data (CAD files)– store and retrieve data (“electronic vault”)– provide index/catalog facility– control data access– define attributes– define relationships– distribute data– manage data– maintain audit trail– manage configurations (“as-planned”, “as-built”,

“where-used” lists)– manage the workflow– provide system management (backup, recovery…)– generate reports– provide external interfaces


Benefits of Implementing PDM

• Reduce the time to introduce new products (at least 20%),• Reduce the cost of developing new products (at least 10%),• Reduce the cost of new products, • Reduce engineering change handling time (at least 30%),• Reduce the number of engineering changes (at least 40%)• Improve the quality of products and services• Improve the flow, quality, and use of engineering information

through the company• Provide improved management of the engineering process

through better control of engineering data, engineering activities, engineering changes, and product configurations


Enabler of Concurrent Engineering

• PDM provide team members access to all data, to the latest versions, at all times– inconsistent designs can be avoided – fewer design problems, less reworks, fewer ECOs

(engineering change orders)– more designs done right the first time.

• PDM/Workflow service:– supports concurrent task management– reduced time-to-market by making data instantly

available, reducing ECOs


Improved Design Productivity

• Increase of productivity of engineers:– correct tools to access data efficiently– reduced time for handling the information (by up to 80%)

• Improved use of standard parts• Better information exchange with partners and

suppliers• Identification, reuse, and modification of existing

(similar) designs• Easy access to reference & project documents


Better Management of Engineering Change

• PDM manages multiple revisions and versions of any design– reduction in the number of changes and

time needed to respond to a request for change

• Subcontractors can be tied into the PDM system:– can have access to the latest product

changes and specifications



Implementation of PDM Systems


Determining Needs for PDM

• A thorough understanding of the business process and addressed issues

• Need for a clear definition how a PDM system is to be applied and what business issues it will address– it can help vendors to propose a

tailored solution• Detail requirements will help

evaluation of vendors


Planning to Use PDM Systems

• PHASE 1:– Project start-up– Understanding PDM– Description of the current

situation• functions & info flows• creators & users of information• organization of engineering• product & project life cycles• eng. info management &

process• current methods of creating,

com-unicating and storing eng. info

• information models– Competitor’s use of PDM– User requirements– Business objectives and PDM– Understanding PDM solutions

– The IT competence of the company

– Sizing and grouping– The features required– Scenarios for PDM– Prototyping and

benchmarking– Developing the PDM strategy– Business benefits of PDM– Organizational issues– Architectures– The overall implementation

plan• Phase 2:

– Detailed design and implementation

• Phase 3:– Use of PDM


PDM Requirements (1)

• Scope of the implementation– enterprise vs. workgroup– single department or integrated through

several departments• Makeup, size and geographical

distribution of the intended end users– number of users (initially, and long-term)– technical expertise of user base, usage

requirements– physical location of PDM users



• PDM functions needed and how they will be applied:– Which users need which functions?– Relative priority of functions– Is PDM part of a BPR effort?

• User interface expectations• System architecture and operating

environment preferences or requirements– network, existing HW, OS for PDM



• Interfaces to legacy systems– MRP, corporate databases updates from

PDM?• Integration to other related applications

(CAD, CAM)– How tight integration is needed?

• Administrative tools and utilities needed• Types and volumes of data to be managed• Types and volumes of data to be migrated

– What type of data conversions are necessary?



• Amount of expertise/consulting expected from vendors

• Company and industry standards that must be met

Most PDM products are good. But, to choosethe right PDM configuration and customizationfor each business environment and PDMobjectives, is the challenge.

Most PDM products are good. But, to choosethe right PDM configuration and customizationfor each business environment and PDMobjectives, is the challenge.


Phase 2: Implementation of PDM Systems

• PHASE 2: Detailed Design and Implementation– The detailed implementation plan

• should identify short term activities– Detailed architectures– Logical database design

• for each file, the most important identifiers have to be identified– Reorganization of engineering workflow

• examination and improvement of the workflow, • definition of the individual tasks, events, and control levels

– Organizational issues• PDM policies and working procedures, training, support team

formation– Technology issues

• in-house tailoring and development of SW, systems interfaces• system administration and management procedures

– Bringing PDM on line


Logical Database Design

• Some typical data identifiers:– name– type– format– family– descriptor– location– status– release level– owner– version– creator– reviewer– date– access rights– source

– structure– dependencies– classification– usage– options


Logical Database Design

• Some drawing identifiers:– Part number– Drawing number– Drawing type– Drawing title– Page number– Revision level– Drawing scale– Drawing format– Drawing size– Drawing owner– Date created– Date modified– Date reviewed– Date released– Release procedure– Reviewer

– Releaser– Contact name– Standards– Procedures

• Some part identifiers:– Part number– Part description– Drawing number– Units of measure– Revision level/status– Dependencies– Creating system– Part superseding– Part superseded– Make/buy source– Cost– Lead time


Phase 3: Use of PDM Systems

• PHASE 3: Use of PDM– Detailed installation plans– Development and purchase of hardware and software– Integration of the solution– Training of managers, users, and support staff– Development of procedures and standards– Test and acceptance of the solution– Initial use of the system– User and manager feedback– System use monitored, compared to expectations– Necessary modifications made– Maintenance and update– Communication of success– Progress review– Report to management


Hints for Successful PDM Implementation

• Gain and maintain top management commitment• Involve and support all functions that use engineering data• Find and encourage champions and change-makers• Identify and disarm opponents• Understand business goals. Plan for business benefits.• Keep the business benefits of PDM in mind• Plan top-down, implement bottom-up.

– the business benefits -> workflow -> entities attributes• Keep the project plan and timetable visible• Understand and do not ignore the organizational issues


Hints for Successful PDM Implementation

• Develop and communicate an understandable PDM vision.• Develop and communicate an understandable PDM

architecture• Implement incrementally. Initiate pilot studies where

possible. • Make sure there will be some early success• Aim for evolutionary product data definitions• Remove or reorganize wasteful parts of the process• Automate activities along the product life cycle• Limit the number of databases. Link activities to

databases.• Use standards where possible.• Minimize internal IT development effort.


Recommendations

• Plan long-term, but start small– set a reasonable, short-term goal for the

initial implementation– the project scope can expand in other

areas of organizations later– allow for cultural changes to take place

gradually• Understand and document the

current process– improve it before automating it



Future Directions


Trends in PDM Systems Development

• Integration and interoperability between heterogeneous PDM systems

• Fine-grain data management• PDM and Collaborative Product

Commerce (CPC)


PDM Integration

Manufacturer

PDM System A

Supplier X

PDM System B

Supplier Y

CAD System

• Documents• Data• Notifications• Interaction

messages

Specific Problems:• Frequent requirement changes• New systems to integrate• Short implementation time frames


OMG PDM Enablers

Manufacturer

PDM System A

PDM Enabler

Supplier X

PDM System B

PDM Enabler

• Sharing of services from different PDM systems• Exchange of information and processes

(Moving PDM data from one PDM system to another)

Request for Engineering ActionEng. Change Order or Eng. Change

Release to ManufacturingDocument Management

Product Structure DefinitionEffectivity of Products

Configuration ManagementTest, Maintenance & Diagnostic

Gluing Software

Many different requirements, changing frequently


Why Fine Grain Data?

100%

0%

Fine-grain information

Complete Information

Activity 2

Activity 1

InformationCompleteness Cycle-time saving

InformationCompleteness

100%

0%∆T

Implement Concurrent Engineering

Activity 2PREREQUISIT FOR

CONCURRENT ENGINEERING


Why Fine Grain Data?

0%

Complete Information

Activity 2

Activity 1

Cycle-time saving

InformationCompleteness

100%

0%∆T

Implement Concurrent Engineering

Activity 2PREREQUISIT FOR

CONCURRENT ENGINEERING


Trends in Industry

SCM ERP CRM

Front EndBack End

CPC

CPC= Collaborative Product Commerce

CPC

PDMVisualizationSourcing

LifecycleSupportCAD/CAM

ProcessModeling

MfgPlanning

ProductPlanning

CPC Product CollaborationEntry Points

Aberdeen Group

CPC: a class of SW and services that uses Internet technologiesto permit individuals…to collaboratively develop, build, and manageproducts throughout their entire life cycle.SCM = Supply Change ManagementCRM = Customer Relation ManagementERP = Enterprise Resource Management


Collaborative Product Commerce

• Operates as a command center:– by sharing product information with existing ERP, SCM,

CRM and e-commerce systems• CPC encompasses of existing sub-markets:

– enterprise application integration (EAI)– visualization– product data management (PDM)– virtual product data management (VPDM)– component supplier management (CSM)– document management– project management– CAD/CAM/CAE– ERP integration



• CPC flexibility:– allows users to access, manage, view and publish

product and process information - regardless of location or format - with a simple Web browser

• CPC provides:– a federated, web-centric technology needed– to find, manage and use information in a dispersed

environment– Databases, applications and processes throughout

the enterprise and its supply chain are seamlessly linked together in a federated environment.



• Gartner Group: CPC opportunities include:– collaborative product development, – customer-driven design– collaborative product/component sourcing– product commerce portals– customer self-service applications

• Aberdeen Group:– CPC will provide a dynamic, Internet-based,

inter-enterprise business infrastructure that links product and process information and applications across boundaries of internal organizations as well as suppliers, partners and customers.