masfak_simultano_projektovanje2

7/29/2019 masfak_simultano_projektovanje2

1/70

Dr. Dragan Domazet SISTEMI ZA BRZI RAZVOJ PROIZVODA 2002 1 - 1

SISTEMI ZA BRZI RAZVOJ

PROIZVODA

SIMULTANO PROJEKTOVANJE-izvodi sa predavanja-Drugo predavanje

Prof. Dr. Dragan Domazet

KATEDRA ZA PROIZVODNO MAINSTVO


2/70


Concurrent Engineering Technology

1 Product & Process Models

2. Model Data Exchange and Sharing

3. Virtual Teaming

4. Workflow Management

5. Product Data Management Systems

Data Exchange STEP standard XML Data Sharing


3/70


Model Data Exchange and Sharing

Data Exchange


4/70


Data Exchange

Complexity FunctionalityCollaborative Product

Development Environment

Company A Company BDatabase

Data

Sharing

DatabaseCompany A Company B

Groupware

CollaborativeGroup Design

Company A Company BPDM

SystemPDM

SystemCollaborative Product

Development

Company A Company BData FileData

Exchange

Information Exchange

Company A Company BAgent-based systemIntelligent CollaborativeProduct Development

Knowledge Sharing


5/70


Information Exchange Information exchange implies that a copy of the

source information as a package is handled from

one source to another.

Application

A

ProductDatabase

Application

B

ProductDatabase

Product

DescriptionExchange File


6/70


Requirement 1: Common Syntax If the information (the exchange file) is not in a

format understandable by the receiver, it has to

be translated into the correct format.

ApplicationA

ProductDatabase

ApplicationB

ProductDatabase

Product

DescriptionExchange File

(Neutral Format)

Translator Translator


7/70


Requirement 2: Common Semantic Applications have to use schematically

equivalent data schemas

ApplicationA

ShapeForm Features

Tolerances

ApplicationB

Shape

ProductDescriptionTranslatorTranslator TranslatorTranslator

Information lost:Form featuresand tolerances


8/70


Requirement 3: Adequate Exchange Standard

The neutral (exchange) file has to

support data semantic ofapplications product models

ApplicationA

ShapeForm Features

Tolerances

ApplicationB

ShapeShape

DataDataTranslator Translator

Information lost:Form features

and tolerancesShape

Form FeaturesTolerances

Example: IGES


9/70


Loss of Information During Data TranslationData Set Types

of System 1Data Set Types

of System 2

Data types that can not be exchanged

Data types that can be directly exchanged

Data Set Types

of System 1 Data Set Types

of System 2

Data types that can be exchanged using standard data models

If necessary, the standard data model may be extended to satisfy requirements

Data Types

of the Standard

Data Model


10/70


Standard vs. Direct Interfaces

30 Direct Interfaces Needed 12 Standard Interfaces Needed

StandardData

Model

Standard (or neutral) data models reduce significantly the numberof interfaces

Number of Interfaces = n(n-1) Number of Interfaces = 2n

DXF (Autodesk)IGES( ANSI)

STEP (ISO 10303)

A CAD/CAE system

Data translation in two directions

Legend:Standard Data Models:


11/70


Benefits of Standard Interfaces Minimal number of data translations (4)data model 1 -> standard data model -> data model 2

and back Minimal number of glue software (interfaces)

Maintenance cost is reduced

Easy integration of new applications or newversions of the existing ones.

No loss of information, if standard/neutral datamodel defines all data types needed for theexchange


12/70


Data Sharing = Data Consistency If a data object is distributed, an automatic

update across the network must beprovided when a change is specified.

Application A Application B

Design Change Design ChangePropagation

Database


13/70


Data Exchange Standards STEP:

standard for product data exchange

IGES: exchange of mechanical drawings, wireframe 3D models

and 3D surface and solid geometric entities

EDIF (Electronic Design Interchange Format): developed for electronic sector transfer of logic models, schematics, netlists, and mask

layout

XML - a generic data exchange standard Many more..


14/70


Data Exchange: Standards of Interest

STEPData File

STEP TranslatorsFor Product Data Exchange:

STEP Application Protocols: Information models for specific industries

For Any Data Exchange:

XMLDocumentApplication

A

Application

B

XML Adapters (Parser)

XML:the universal format for data interchange (self-describing)

DTD

CAD A CAD B


15/70



STEP Standard!

How to exchange product data

between different systems?


16/70


Solution: STEP Standard

STEP is an international standard (ISO10303) for product data exchange andsharing.

It provides neutral product representation

methodology, capable of providing acomplete definition of product informationcovering the products life cycle.

The product representation provided bySTEP is computer interpretable.


17/70


STEP Standard

STEP: Standard for the Transfer and Exchange of Product data)

STEP is an international product standard (ISO 10303) for

developing a complete and integrated product description in aneutral format.

STEP is completely capable of representing product definitiondata throughout its life cycle

STEP provides for information sharing and this is made possiblethrough the use of standardized constructs

STEP employs a methodology that includes: the use of reference models,

formal definition languages, and an integration architecture.


18/70


Objectives

Objectives to be achieved by informationexchange/sharing standards: to generate information only once and

minimize duplication effort;

to eliminate inefficient processes and minimize

transaction times and costs; to provide correct information to the project

team at the right time; and

to establish a performance-based managementsupport system.


19/70


Product Life Cycle Support

Product

Design

Product

Analysis

Quality

ControlProcess

Planning

MRP

Scheduling

Process

Simulation

ManufacturingAssemblyTestingDelivery

Maintenance

Recycling STEPInformation

Tool/Mold

Design


20/70


STEPApplication Protocols define the scope, context, and information

requirements for a particular application

ApplicationA ApplicationB

STEPFile

STEP Interface STEP Interface

STEP AP203Schemas

STEP AP203Schemas

eg.: AP203


21/70


Support of Heterogeneous Environments STEP supports different hardware and software platforms,

i.e. heterogeneous environments

STEP-compliant applications can exchange or shareinformation, regardless of software or hardware vendors.

Thisprotects users from the dependency of only onevendor.

This supports collaboration and information exchangebetween suppliers and manufacturers.

Application A

ProductDa abase

Application B

ProductDatabase

ProductDescription

Exchange File

CAD System 1 CAD System 2


22/70



XML


23/70


XML: Extended Markup Language

ORDER

SOLD-TO SOLD-ON ITEM

PERSON

NAME ADDRESS

BOOK PRICE

AUTHOR TITLE

GIFT

Elements

Dragan DomazetLeonie Hill 16

19990815

$100

XML Makes You RichBill Gates

Pen

Dragan DomazetLeonie Hill 16

19990815

$100

XML Makes You RichBill Gates

Pen

My XML File: Structured Data (Smart Data)DTD: Document Type Definition


24/70


Scenario: I Want to Order a Book

XML Parser Application

I know XML!Or

MS Word may convertmy message into XML document

I interpret XMP! C++

[email protected]

XML Doc

My OrderE-mail

DTD


25/70


Difference of XML vs HTML

New tags (XML elements) and theirattributes may be defined

XML allows business data to be searched

XML is self describing

Applications: e-commerce, business-to-business, middle tierdata sharing


26/70


XML Data Sharing

XML Data

ApplicationServersThin Clients


27/70


XML Server Role

XML Request

XML Data

XML Data

Applications

Thin Client

XML Server


28/70


Example:On-Line Catalog System

ProductDatabase

InventoryDatabase

TransactionProvider

XML Data Server

Application Servers- use unified logical data vie

Clients

XML XML XML

XML Adapter XML Adapter XML Adapter

XML elements are labeled

with self-describing tags

Data objects can bedynamically evaluated asthey are received

XML Data

High speed accessto the data

Support schemachanges on the fly

Served to multipleapp servers


29/70


An Example: eXcelon XML Data Server

D

OM Java

Extension

XML XQL

ODBC OLE DB XML

Mainframe Database

High-speed query accessto XML data store

Use of dynamic data data objects may be

changed on the fly

Updates the data object

without disrupting theexisting structure

Distributes data across themiddle tier

Application Servers, Clients


30/70


DOM:Document Object Model

DOM is a platform- and

language-neutral interface that will allow programs and

scripts to dynamicallyaccess and update the

content, structure and styleof documents.

ProgramsScripts

DOM Interface

XML orHTML

Document

Access andupdate

Change:- content- structure- style

E.g. Java


31/70


XML Features

Searching Smart Client

DocumentData

ApplicationData

Desktop Effective searching, queryingand manipulation of data

DocumentManagement

App ServerIntegration

Servers An efficient storage formatfor hierarchical dataNo need of conversion to rowsand columns

DocumentData

StructuredDataStorage A universal format for data interchangebetween application servers


32/70



Model Data Sharing(Model Management)


33/70


Data Exchange




DataSharing


Groupware



SystemPDM


Development


Exchange



Knowledge Sharing


34/70

Dr. Dragan Domazet SISTEMI ZA BRZI RAZVOJ PROIZVODA 2002

Challenges for CE Technology

Sharing of information poses several obstacles: the incompatibility of data formats (models) and tools

used in different perspectives (applications), the absence of a common data model to unify the

product definition in multiple perspectives,

the inability for the data to be accessed from target CAD

file or repository and made available locally at usersworkstation,

the lack of transparency in data access when the actualdata are lying in many different distributed databasesand CAD files,

the lack of standards for data interchange to overcomethe incompatibility of basic hardware and software


35/70


Data Consistency Requirement:

Data Sharing

Data exchange is mainly needed for supporting loosely coupledengineering activities.

For tightly coupled activities and support of teamworks, datasharing is more appropriate

Data sharing: all product information should be integrated: a data object may have multiple copies, but they all should have

only one logical address, its integrity and consistencymust be maintained

pager_cover pager_cover

update

propagate

database 1 database 2


36/70


Data Sharing

DataData

All use the same data repository Only one (master) data item exists Can access any piece of data

Concurrent data access Data security, consistency & integrity


37/70


Product Information Sharing

Only the productinformationsharingcanprovide goodteam integration,coordination,cooperation, andcommunication -all important CErequirements

All use the samedata objects

Designer

Design

Analyst

Process PlannerMaintenance Engineer

Product Model

F


38/70


Data Servers & Databases

In an integrated environment, some of the product definitionattributes are shared, imported from a common database

Data are stored in the database and retrieved from the database

according to the structure described in the data model pr theschema of the database A design data server:

is the data management layer of the database, applications directly interface with the server to request data

management activities retrieves and updates the product data in the database

Global and local data models Data model of the group workspace:

is global relative to the local data models of the private workspaceof its users is local relative to the global data model of the project workspace

that encloses the group workspace


39/70


Concurrent Engineering Technology

1 Product & Process Models

2. Model Data Exchange and Sharing

3. Virtual Teaming

4. Workflow Management5. Product Data Management Systems

Virtual Teams Groupware Technology


40/70


Virtual Teams

Virtual Teams


41/70


Virtual Team

Virtual team: the formation and operation of a team of distributed

participants on an integrated product development project

who are virtually collocated they share data, communicate, and coordinate their work

using computer network and information technology as theessential means of accomplishing the close team worknecessary for CE

have group transactions like meetings, notifications,scheduling of work, propagation of results etc.

For CE, the Virtual Team: consists of team members in different perspectives of the

product development, wielding powerful CAD/Cae tools in

their private workspaces, but publishing their results to ashared information bases the communication incurs no time delays; it is multi-way and

interactive


42/70


Virtual Team Approach

Design

Analysis Manufacturing

Materials

ManagementMarketing

UnifiedProductConcept

Network


43/70


The Virtual Team Concept

The Virtual Team concept: Getting things done in concert by a group of experts who each

bring a unique viewpoint to the project

They have their roles well established and arrive at a sharedview of their goals as a team The team is thrown together for long sessions of intense

exchange and thinking They form and dissolve as soon as the mission is

accomplished Supporting technology:

It is not only sending electronic mail and transmitting datafiles

it is a new groupware the software & hardware tools that serve a group and are

exercised in a group and allow a group to go through all thestages of decision making


44/70


Virtual Team Model

Two basic capabilities are needed: a central repository of shared data

whenever information is to be shared it is placed there, and

automatically becomes accessible to entire team a coordinating framework

to enable a project leader to communicate tasks, goals, and deadlines,

cause the individual decisions to propagate their influence throughoutthe team

will force team to render consistency to their decisions from time totime, and thus achieve consensus

Product Data Model CoordinatorData

versionsWorkflows

What? How? When?


45/70


Potential Benefits of Virtual Teaming

There is no limit in location or composition ofteam members

There is rapid propagation of information anddecisions across all team memberselectronically.

Role clarityacross disciplines is embedded in thenotation of data ownership within the commondata model.

There is great flexibilityin constituting and

reconstituting the team as the needs of theproject change over time.


46/70


Virtual Teaming

Groupware Technology

Groupware: The computer-based systems that support groups of peopleengaged in a common task (or goal) and that provide an interfaceto shared environments


47/70


Groupware




DataSharing


Groupware



SystemPDM


Development


Exchange



Knowledge Sharing


48/70


Groupware Definition

Group interaction issues: communication, collaboration, demands that people share information coordination

The goal of groupware is to assist groups incommunicating, in collaborating, and in

coordinating their activities Groupware: computer-based systems that support groups of people

engaged in a common task(or goal) and that provide aninterface to a shared environment

Real-time groupware: supports simultaneous activity


49/70


The Groupware Spectrum

Common TaskDimension

Shared EnvironmentDimension

Electronic Classroom

Electronic Mail

TimesharingSystem

Software ReviewSystem


50/70


Groupware Time Space Taxonomy

Face-to-faceInteraction

AsynchronousInteraction

SynchronousDistributedInteraction

AsynchronousDistributedInteraction

Same Time Different Time

Same Place

Different Places

Location

Time


51/70


Groupware Principles

Groupware systems: computer-based systems that support groups of people

engaged in a common task (or goal) and that provide aninterface to a shared environment

Shared direct manipulation principles: sharing objects of interest

providing awareness of the actions of the group (commontask)

Who is issuing the change and when

to understand why this change is being done


52/70


Components of Groupware System Communication channels:

textual, audio, visual

to coordinate and communicate Group editors (used by applications):

text, sketch, drawing, 3D model/design..

Shared database, shared object

G C


53/70


Groupware Components

3D CAD 2D Drawing DocumentMulti Media

CommunicationSystem

Log

Shared Editors

Real-time

Real-time(synchronous)orAsynchronous

GroupGroupMembersMembers


54/70


Application-Level Groupware Taxonomy

Message Systems: supports the asynchronous exchange of textual messages between groups of

users

electronic main & bulletin board systems

Multi-user Editors: a group jointly composes and edits a document

allow a group of people to edit the same object at the same time

the object is usually divided into logical segments

concurrent read access to any segment, but only one writer per segment(mangoes locking and synchronization, notifications)

Group Decision Support Systems and Electronic Meeting Rooms: provide computer-based facilities for the exploration of unstructured problems

in a group setting

the goal is to improve the productivity of decision-making meetings EMR: a set of workstations that communicate offer a LAN and run SW tools for

electronic brainstorming, stakeholder identification and analysis


55/70



Computer Conferencing: the computer serves as a communication medium Real-Time Computer Conferencing:

allow a group of users to interact synchronously through theirworkstations (e.g., replicated windows)

Computer Teleconferencing: telecommunication support for group interaction and video

conferencing

provides workstation-based interface to a conference interaction occurs between large common areas ate each site, butparticipants can access video channels through their officeworkstations

Desktop Conferencing: uses workstations as the confines interface, but also runs

applications shared by participants supports multiple video windows per workstation display of dynamic views of information and dynamic video images

of participants


56/70



Intelligent Agents: non-human participants in an electronic meeting or group

application

are responsible for a specific set of tasks, and the user interfacemakes their actions resemble those of other users object wrappers - an object interface to legacy systems

Coordination Systems: coordination problem:

integration and harmonious adjustment of individual work effortstoward the accomplishment of a larger goal

allow individuals to view their actions, as well actions of others,within the context of the overall goal

systems may also trigger users actions or by generating automatic

reminders and alerts can be categorized: form (routing documents), procedure

(programmable processes), conversation, or communication-structure oriented (role relationships)

Real Time CSCW Systems


57/70


Real-Time CSCW Systems

Shared text editors

Freehand sketching systems

Structured drawing programs

Group-supported systems Technical issues: synchronization,

concurrency

communications registration

CSCW:CSCW: ComputerComputer--Supported Cooperative WorkSupported Cooperative Work

Shared Editors


58/70


Shared Editors

General purpose editors

Bitmap editors as sketching tools

Structured drawing editors

Domain specific editors

CAD systems, music editors,

SHARED MANIPULATION

shared or sliced layers

Layer

Slices

G D i I


59/70


Groupware Design Issues

Concurrency Control need to resolve conflicts between participants simultaneous

operations

explicit locking and transaction processing in databaseoperations are nor appropriate for groupware Responsiveness:

two properties are required: a short response time and a shortnotification time

Group Interface: based on group windows one users actions must be immediately seen by others

Wide-Area Distribution: transmission times and rates for WAN tend to be slower than for

LAN communication failures are more likely - need for resilientconcurrency control algorithms

G D i I


60/70



Data Replication: data may be replicated in order to obtain a short response time

Robustness:

the recovery from unusual circumstances (component failures, orunpredictable user actions) the systems concurrency control must adapt to system reconfigurations

Concurrency control methods: Simple locking: two phase locking

problems: response time, data locking granularity, the timing of lockrequests and releases flexible locking mechanisms are needed: soft locks etc.

Transaction mechanisms: distributed concurrency control algorithms are difficult to implement,

incurring a cost in user response time other methods: timestamps, long transactions are not well-suited to

interactive use, short transactions are too expensive groupware systems must make each users action visible to others

G D i I


61/70



Turn-Talking Protocols: such as floor control, is limited to those situations in which a single

active user fits the dynamics of the session ill-suited for sessions with high parallelism

Centralized Controller: receives user requests for operations and broadcasts these requests to

all users since the same operations are performed in the same order for all users,

all copies of the data remain the same

problems: bottlenecks, responsiveness is lost, the interface must belocked of a user issuing a request

Dependency Detection: uses operation timestamps to detect conflicting operations, which are

then resolved manually

no synchronization is necessary, but is vulnerable to user error Reversible Execution:

operations are executed immediately, but it can be undone later ifnecessary



62/70



Operation Transformations a dependency-detection solution with automatic. rather

than manual, conflict resolution

when an operation is requested, it is immediatelyperformed on the users copy

it broadcasts the operation along with a state vectorindicating how many operations it has recently processedfrom other workstations,

each copy has its own state vector, with which it comparesincoming state vectors

if the received and local state vectors are equal, thebroadcast operation is executed as requested

otherwise, it is transformed before execution the specific transformation is dependent on operation type

and on a log of operation already performed.

Groupware Tools


63/70


Groupware Tools

GroupSketch

GroupDraw

GroupText

GroupCAD

Image Voice Vote Project

Management

Groupware Tools

CSCW: Computer-SupportedCooperative Work

AsynchronousTeam Work

Same

Different

Real-timeMeeting

Virtual Team Members

Information Search and Retrieval

Requirements


64/70


Requirements

Support for gesturing multiple cursors

Support for graphical annotation Structuring group processes

methods for keeping the group on task

Provide various floor control policies

Support different registration methods Support latecomers to the conference

Integration with conventional ways of doing work

Integrate other forms of communication Allow use of single-user applications

Requirements


65/70


Requirements

Technical support of multiple and distributedprocesses Provide processes for basic conference management Provide a robust communications infrastructure

centralized architecture - simplifying concurrency

replicated architecture - more efficient and robust

Provide support for persistent sessions

Technical support of a graphical model Provide primitives to a shared graphical library

Provide object concurrency control Separate the view of an object from it underlying

representation

Propagation of Events


66/70


Propagation of Events

A

B

A

B

DrawLine(UserID,X1,Y1,X2,Y2)

Computer AComputer A Computer BComputer B

Input Output

Notification(DrawLine Event Broadcasting)

Group CAD


67/70


Monitor APlatform A

Monitor BPlatform B

Shared Database

Group CAD

Decisions are made

faster - in real time No waiting

Real-Time Groupware Concepts


68/70


Real Time Groupware Concepts

Shared context: a set of objects where the objects and actions

performed on the objects are visible to a set of users

Group window: a collection of windows whose instances appear on

different display surfaces

Telepointer: a cursor that appears on more than one display and that

can be moved by different users

View: a visual, or multimedia representation of some portion

of a shared context

Real-Time Groupware Concepts


69/70


Real Time Groupware Concepts

Synchronous interactions: people interact in real time

Asynchronous interactions: people interact over an extended period of time (e-mail) Session:

a period of synchronous interaction supported by a

groupware system (e.g., group discussion) Role:

a set of privileges and responsibilities attributed to aperson, or sometimes to a system module

Groupware Implementation


70/70


p p

CentralCentralProgramProgram

ReplicatedProgram

ReplicatedProgram

ReplicatedProgram

ReplicatedProgram

Centralized Architecture Replicated Architecture

masfak_simultano_projektovanje2

Documents