advanced manufacturing systems design © 2000 john w. nazemetz lecture 11 topic : information...

Advanced Manufacturing Advanced Manufacturing Systems DesignSystems Design

© 2000 © 2000 John W. NazemetzJohn W. Nazemetz

Lecture 11 Topic :Lecture 11 Topic : Information Information Exchange in a Virtual WorldExchange in a Virtual World

Segment A Topic:Segment A Topic: Virtual Enterprises Virtual Enterprises

Computer Integrated Manufacturing Systems © 2000 John W. NazemetzSlide 2

ADVANCED ADVANCED MANUFACTURING MANUFACTURING SYSTEMS DESIGNSYSTEMS DESIGN

Information Exchange Information Exchange in a Virtual Worldin a Virtual World

Virtual EnterprisesVirtual Enterprises


OverviewOverview

• Overview of Virtual EnterprisesOverview of Virtual Enterprises– Definition

– Forces Behind Formation

– Key Elements in Virtual Enterprises


DefinitionDefinition

• Virtual Enterprises are seamless, Virtual Enterprises are seamless, data- platform-independent data- platform-independent integrations of multiple, legally-integrations of multiple, legally-distinct, geographically distributed distinct, geographically distributed business entities who use information business entities who use information technology in the execution of tasks technology in the execution of tasks and/or realization of products during and/or realization of products during the product life cycle.the product life cycle.


Definition – Key Wording Definition – Key Wording (1)(1)

• Virtual Enterprises are Virtual Enterprises are seamless, seamless, data- platform-independent data- platform-independent integrationsintegrations of multiple, legally- of multiple, legally-distinct, geographically distributed distinct, geographically distributed business entities who use information business entities who use information technology in the execution of tasks technology in the execution of tasks and/or realization of products during and/or realization of products during the product life cycle.the product life cycle.



• Virtual Enterprises are seamless, data- Virtual Enterprises are seamless, data- platform-independent integrations of platform-independent integrations of multiple, legally-distinct, multiple, legally-distinct, geographically distributed geographically distributed business entitiesbusiness entities who use who use information technology in the information technology in the execution of tasks and/or realization execution of tasks and/or realization of products during the product life of products during the product life cycle.cycle.



• Virtual Enterprises are seamless, Virtual Enterprises are seamless, data- platform-independent data- platform-independent integrations of multiple, legally-integrations of multiple, legally-distinct, geographically distributed distinct, geographically distributed business entities who business entities who use use information technology in the information technology in the execution of tasks and/or execution of tasks and/or realization of productsrealization of products during during the product life cycle.the product life cycle.



• Virtual Enterprises are seamless, data- Virtual Enterprises are seamless, data- platform-independent integrations of platform-independent integrations of multiple, legally-distinct, multiple, legally-distinct, geographically distributed business geographically distributed business entities who use information entities who use information technology in the execution of tasks technology in the execution of tasks and/or realization of products and/or realization of products during during the product life cycle.the product life cycle.


Why Form? (1)Why Form? (1)

• Businesses Focusing on Key/Core Businesses Focusing on Key/Core Business Business – Build Expertise

• Integration Expertise• Execution Expertise

– Exploit Expertise• Expertise -> Efficiency• Ability to Collect Experiences/Learning• Competitive Advantage

– Maintain Utilization of Resources



• Businesses Not Able/Desired to Do Businesses Not Able/Desired to Do “Whole Job”“Whole Job”– Role of Integrator

• Life Cycle Perspective

– Technical Experts• Narrower Focus• Needed Expertise is Project/Product Specific• Very Expensive to Maintain All Possible

Expertise

– Need/Desire to Stimulate/Provide Competition (US DoD)



• Lack of Expertise in FirmLack of Expertise in Firm– Too Costly to Develop/Maintain

• Insufficient Learning• Value to Other Firms

– Competing Projects/Demand on Resources

– Dynamic Demand for Expertise (Risk)



• Distance Independent CommunicationDistance Independent Communication– Technical Feasibility

• Infrastructure Established– Internet – Interactive, Supports Multi-Media– Communication Tools Available– Available in Real Time

– Economic Feasibility• Internet Use Inexpensive• Tools Widely Available, Low Cost/Free

– Operational Feasibility• Personnel – Have Accepted Use of Technologies


Key Elements in Virtual Key Elements in Virtual Enterprise Formation Enterprise Formation

(1)(1)• Mutual Coincidence of Mutual Coincidence of

Want/CapabilityWant/Capability– Different Abilities

• Ability to Identify “Players”Ability to Identify “Players”– Means of “Mapping” Needs to Providers

• A Communication InfrastructureA Communication Infrastructure– Interactive– Multi-Media– Low Cost (Acquisition/Use)


Key Elements in Virtual Key Elements in Virtual Enterprise Formation Enterprise Formation

(2)(2)An Common Execution StrategyAn Common Execution Strategy

– ISO 9000– Mil-Stds– Product Standards

• Mutual Means for InteractionMutual Means for Interaction– Common Terminology/Vocabulary– Internet (Medium)– ANSI x.12 Standards (Business

Transactions)– STEP, XML, SGML (Data Exchange)




Segment A Topic:Segment A Topic: Virtual Enterprises Virtual Enterprises

END OF SEGMENTEND OF SEGMENT




Segment B Topic:Segment B Topic: Virtual Enterprise Virtual Enterprise Evolution Evolution




Virtual Enterprise EvolutionVirtual Enterprise Evolution


OverviewOverview

• Context of Virtual Enterprise Context of Virtual Enterprise OperationOperation

• Evolution of Virtual EnterprisesEvolution of Virtual Enterprises– Steps to Virtual Enterprise

• Universal Applicability of the Universal Applicability of the Virtual ParadigmVirtual Paradigm


Operational ContextOperational Context

• Product Life CycleProduct Life Cycle– Sequence of Iterations of Activities– Many Information Sources Needed at

Various Points in Cycle

• Supply ChainSupply Chain– Legal and Technical Relationships– Independence/Dependence of Links


Context: Product Life Context: Product Life CycleCycle

• Temporal Distribution of Activities/ Temporal Distribution of Activities/ Need for (Geographically Distributed) Need for (Geographically Distributed) ExpertiseExpertise– Design/Redesign

• Concurrent Engineering–Input from Other Phases

– Production (Product, Production Facility)• Original Product/Spares/Revisions

– Use/Maintain• Test/Feedback• Input for Revisions

– Disposal


Context: DoD Supply Context: DoD Supply ChainChain

Customer

Order

DLA

Technical Data

Bidders

DLA Contract

Prime

Suppliers

Subcontractors

PRODUCT


Evolution of Virtual Evolution of Virtual EnterprisesEnterprises

Electronic DataElectronic DataInterchangeInterchange

Integration of EDIIntegration of EDIInternal SystemsInternal Systems

Technical DataTechnical DataInterchangeInterchange

Product/ProcessProduct/ProcessData Driven Data Driven

ManufacturingManufacturing

DistributedDistributedCollaborativeCollaborativeEngineeringEngineering

Network BasedNetwork BasedOutsourcingOutsourcing

Virtual Virtual EnterpriseEnterprise

Network EnabledNetwork EnabledBusiness PracticesBusiness Practices


Virtual Enterprises – Virtual Enterprises – Evolution (1)Evolution (1)

• Electronic Data InterchangeElectronic Data Interchange– E-mail/Fax/Phone/Internet/Voice Mail

• Digital Networks• Synchronous/Asynchronous

– File Exchange• Media/File Copy and Exchange• Mail Attachments• File Transfer Protocol (FTP)

– Concerns• Master Copy

Location/Synchronization/Formats


Virtual Enterprises – Virtual Enterprises – Evolution (2a)Evolution (2a)

• Integration of EDI and Internal Integration of EDI and Internal SystemsSystems– EDI Integrated with MRP and CAD/CAM

Systems• Access Granted to Internal Databases

– Read Only– Read/Write

• Information on CAD Model/Status/Resources

– EDI Integrated with Financial Systems• Paperless Exchange of Authority to Proceed• Electronic Monetary Exchanges


Virtual Enterprises – Virtual Enterprises – Evolution (2b)Evolution (2b)

• Integration of EDI and Internal Integration of EDI and Internal SystemsSystems– Concerns

• Master Records• Synchronization• Firewalls/Security

– Direct Access to Data– Request/Make Available or Send

• Common Formats/Software and Hardware– Restricted to Single Vendor/Common Systems

• Little Law in Area



Technical Data ExchangeTechnical Data Exchange– Data Interchange Among Heterogeneous

Systems Using STEP, IGES, SGML, XML, EDI Transaction Sets• Make Data Format and Vendor Application

Independent

– Enterprise-Wide Technical Data Repository

– Concerns• Neutral Format Availability/Use/Conformance• “One Solution Fits All”



Product/Process Data-Driven Product/Process Data-Driven ManufacturingManufacturing– CAD Model => Basis– Numerical Control Systems– MRP/PDM/ERP– CAPP Systems– Equipment Capability/Status/Cost

• ConcernConcern– Proprietary Data/Competitive

Advantage



• Distributed Collaborative Distributed Collaborative EngineeringEngineering– Integrated Product Teams (Concurrent

Engineering)– Virtual Prototyping over Network

• Real Time Interchange/Cyclic Exchange

– Concerns• Distribute Responsibilities• Collective Responsibilities• Conflict Resolution/Management

– Issue Logs, …



Network Based OutsourcingNetwork Based Outsourcing– Whiteboarding over the Network

• Electronic Equivalent of “Back of Envelope and a Handshake”

– Value Added Networks– WWW (Bi-directional) Homepages– Electronic Bidding– Purchase of Capacity and “External”

Scheduling



• Virtual EnterpriseVirtual Enterprise– Network Based International Business

Alliances– Simultaneous Data Exchange/Sharing

over Multiple Locations and Organizations

– Electronically (Real Time) Management of Entire Supplier Chain

– ERP– Dynamic Partnering


Universal Applicability Universal Applicability of Virtual Paradigmof Virtual Paradigm

• All Activities of Product Life Cycle Must All Activities of Product Life Cycle Must be Executed for All Productsbe Executed for All Products

• Execution of Life Cycle Tasks Benefit Execution of Life Cycle Tasks Benefit from Use of Electronic Interactionfrom Use of Electronic Interaction– All Organizations Distributed

Geographically– Asynchronous Electronic Exchange is Part

of Standard Operating Procedure of Business

– Costs Are Reduced/Product Enhanced by Exchange




Segment B Topic:Segment B Topic: Virtual Enterprise Virtual Enterprise Evolution Evolution





Segment C Topic:Segment C Topic: Concepts of Data Concepts of Data




Concepts of DataConcepts of Data


OverviewOverview

• DefinitionsDefinitions• Data TypesData Types• Open System Interconnection Open System Interconnection

ModelModel• File StructuresFile Structures• Mark-up LanguagesMark-up Languages


DefinitionsDefinitions (1) (1)

• DataData– 1. Collection of Facts

– 2. The symbolic representation of facts that a) can be recorded, b) have implicit meaning, c) can be used for reasoning, calculation, communication, and storage

– 3. Representation of facts, concepts, or instructions in a formal manner suitable for communication, interpretation, or processing by human beings or computers.


Definitions Definitions (2)(2)

InformationInformation

– 1. Set of Facts Organized to Facilitate an Action or Decision

– 2. The communication and interpretation of an organized collection of related data in an established context.

– 3. Facts, Concepts, or Instructions


Background – Data Background – Data TypesTypes

• DataData– Document Data (Business Data)

• Business Documents (Memos, Letters, etc.)• Contractual Documents (Orders, Payments,

etc.)

– Technical/Graphical Data (Technical Data)• CAD Models/Engineering Drawings• Technical Documents (Specifications,

Manuals, etc.)

• Meta-DataMeta-Data– Data About Data

• Identification/Version/Semantics/Structure


Product DataProduct Data• Any/All Data Associated with a Any/All Data Associated with a

Product and its Production FacilitiesProduct and its Production Facilities– Documents

• Organized Bodies of Text and Illustrations• May be Commonly or Formally Defined

– Technical Data• Organized Bodies of Numerical and Graphical

Information• Defined by an Governing/Controlling Body,

Application Program, Accepted Standard

– May/May Not be in Electronic Form


Meta-Data Meta-Data (1)(1)

• IdentificationIdentification– Destination/Source– Date/Time, …

• StructureStructure– Application Program Data File/Format – Document Type Definition (DTD)– File Format Used (Format, Version)

• Content/SemanticsContent/Semantics– Meaning/Data Names and Types


Meta-Data Meta-Data (2)(2)

• IntegrityIntegrity– Number of Pieces/Segments– Length/Transmission– Hash Totals

• PresentationPresentation

• Meta-Data in Headers, Trailers, Meta-Data in Headers, Trailers, and Mark-up (Tags) and Structureand Mark-up (Tags) and Structure


Elements of Data Elements of Data ExchangeExchange

• Recognition of Mutual Need/Desire/ Recognition of Mutual Need/Desire/ Benefit of Data ExchangeBenefit of Data Exchange

• Common Mechanism for Exchange Common Mechanism for Exchange and Use of Dataand Use of Data

• Common Understanding of Meaning Common Understanding of Meaning and Interpretation of Exchanged and Interpretation of Exchanged Data Data


Recognition of Mutual Recognition of Mutual Need/Desire/BenefitNeed/Desire/Benefit

• Industrial Data -> Economic BenefitIndustrial Data -> Economic Benefit– Avoidance of Re-creation– Avoidance of Re-entry– Avoidance of Errors

• Interpretation• Recording/Entry

– Facilitate (Informed) Decision Making


Common Mechanism for Common Mechanism for Exchange and Use Exchange and Use (1)(1)

• Mechanism/ModelMechanism/Model– Open Systems Interconnection (OSI)

• Breaks Exchange into Pieces for Transmission• Controls Transmission• Allows Re-Grouping for Application Use

• ApplicationApplication– Program Specific Functionality/Algorithm

• Expects Particular Data/Symbology/Relationships

• Expects Particular Data Format(s)• Expects Particular Data Sequence/Identification


Common Mechanism for Common Mechanism for Exchange and Use Exchange and Use (2)(2)

• Common Data ModelsCommon Data Models– Use International Standardization

Process to Achieve Consensus on Content, Structure, and Terminology of Data Model/Schema for Industrial Data to be Exchanged.

– Make Data Model Available for Application Developers Use in Commercial Software

– This is Goal of ISO TC184/SC4 – Industrial Data and ISO 10303 (STEP)


OSI ModelOSI Model

Presentation

Application

Session

Transport

Network

Data Link

Physical

Presentation

Application

Session

Transport

Network

Data Link

Physical

Source

Destination

DATA DATA FLOWFLOW

TR

AN

SP

OR

TA

PP

LIC

ATIO

N

TR

AN

SP

OR

TA

PP

LIC

ATIO

N


File StructureFile Structure

• Header Section 1Header Section 1– OSI 4-6– Transmission Data

• Header Section 2Header Section 2– OSI Layers 1-3– Application

Identifiers

• Data SectionData Section– Application Specific

Data

• Trailer SectionTrailer Section


Section/Data StructureSection/Data Structure

<Section Start><Section Start><Element 1 Start >

<Field A Start>DATA</Field A End><Field B Start>DATA</Field B End>

</Element 1 End><Element 2 Start >

<Field X Start>DATA<Field X End><Field Y Start>DATA<Field Y End>

</Element 2 End>

</Section End></Section End>


Data and its Data and its OrganizationOrganization

• Field Separation Codes/SymbolsField Separation Codes/Symbols– Blanks– Commas– Semicolons– Periods– Carriage Returns– Symbols (#001, …)– Tags (Headers, <Start>, </End>)

• Concept of “Mark-up” Languages


Mark-Up LanguagesMark-Up Languages

• Use Tags to Separate ElementsUse Tags to Separate Elements– First Tags Short (Reduce File Length/

Storage Requirements)– Transmission Speeds Increase and

Storage Costs Fall– Incorporate Semantics (Meaning) in

Tags• Standard Generalized Mark-up Language

(SGML)• HyperText Mark-up Language (HTML)• eXtensible Mark-up Language (XML)


Mark-Up Example Mark-Up Example (1)(1)

DRAFT DRAFT DRAFTDRAFT DRAFT DRAFT

OKLAHOMA STATE UNIVERSITY OKLAHOMA STATE UNIVERSITY

COLLEGE OF ENGINEERING, ARCHITECTURE AND COLLEGE OF ENGINEERING, ARCHITECTURE AND TECHNOLOGYTECHNOLOGY

FACULTY COUNCILFACULTY COUNCIL

Meeting Minutes (4/16/99)Meeting Minutes (4/16/99)

Attendance:Attendance:

Rob Whiteley Rob Whiteley Chair Chair PresentPresent

Greg Wilber Greg Wilber Vice Chair Vice Chair AbsentAbsent

… …


Mark-Up Example Mark-Up Example (2)(2)

<html xmlns:v="urn:schemas-microsoft-com:vml"<html xmlns:v="urn:schemas-microsoft-com:vml"

xmlns:o="urn:schemas-microsoft-com:office:office"xmlns:o="urn:schemas-microsoft-com:office:office"

xmlns:w="urn:schemas-microsoft-com:office:word"xmlns:w="urn:schemas-microsoft-com:office:word"

xmlns="http://www.w3.org/TR/REC-html40">xmlns="http://www.w3.org/TR/REC-html40">

<head><head>

<meta http-equiv=Content-Type content="text/html; <meta http-equiv=Content-Type content="text/html; charset=windows-1252">charset=windows-1252">

<meta name=ProgId content=Word.Document><meta name=ProgId content=Word.Document>

<meta name=Generator content="Microsoft Word 9"><meta name=Generator content="Microsoft Word 9">

<meta name=Originator content="Microsoft Word 9"><meta name=Originator content="Microsoft Word 9">

<link rel=File-List href="./April%2016%201999_files/filelist.xml"><link rel=File-List href="./April%2016%201999_files/filelist.xml">

<link rel=Edit-Time-Data <link rel=Edit-Time-Data href="./April%2016%201999_files/editdata.mso">href="./April%2016%201999_files/editdata.mso">


Mark-Up Example Mark-Up Example (3)(3)<meta name=Template content="C:\Program Files\Microsoft Office\<meta name=Template content="C:\Program Files\Microsoft Office\

Office\html.dot">Office\html.dot"></head></head>

<body bgcolor=white lang=EN-US link=blue vlink=purple style='tab-<body bgcolor=white lang=EN-US link=blue vlink=purple style='tab-interval:.5in'>interval:.5in'>

<div class=Section1><div class=Section1>

<h2>DRAFT DRAFT DRAFT</h2><h2>DRAFT DRAFT DRAFT</h2>

<p><b><i><span style='font-size:18.0pt;font-family:"Comic Sans <p><b><i><span style='font-size:18.0pt;font-family:"Comic Sans MS";color:yellow'>OKLAHOMAMS";color:yellow'>OKLAHOMA

STATE UNIVERSITY <FO NT STATE UNIVERSITY <FO NT SIZE="+2"><o:p></o:p></span></i></b></p>SIZE="+2"><o:p></o:p></span></i></b></p>

<p><span style='font-size:13.5pt;font-family:"Comic Sans <p><span style='font-size:13.5pt;font-family:"Comic Sans MS"'>COLLEGE OFMS"'>COLLEGE OF

ENGINEERING, ARCHITECTURE AND TECHNOLOGY<br>ENGINEERING, ARCHITECTURE AND TECHNOLOGY<br>FACULTY COUNCIL</span> </p>FACULTY COUNCIL</span> </p>


Mark-up Concepts Mark-up Concepts (1)(1)

• In Addition to Identifying In Addition to Identifying Fields/Elements, Document Fields/Elements, Document Structure Can be Defined Through Structure Can be Defined Through “Mark-Up”“Mark-Up”

• Each Field/Element Can Be Each Field/Element Can Be Associated With a Presentation Associated With a Presentation Format/StyleFormat/Style


Mark-up Documents Mark-up Documents (1)(1)<Book>

<Cover><Front Matter>

<Title Page><Table of Contents><Abstract>

<Body><Chapter 1><Section 1> …

<End Matter><Glossary><Index>

<Cover>

<Letter><Letterhead><Date><Inside Address><Salutation><Body>

<Reason For Letter><Discussion><Social Closing>

<Closing><Signature/Name><Title><Enclosures>


Mark-up Documents (2)Mark-up Documents (2)

• Style Document Provided on Style Document Provided on Website for PapersWebsite for Papers– Defines Presentation Format

• Layout and Content of Report– Title Page, Table of Contents, …

• Text Font, Size, Bold, ….

– Defines Content/Sections– Can be Converted to .html Format

• .html Dynamically Recognizes Display When Formatting vs. .doc Which Uses Paper/Page Layout


Mark-up Concepts Mark-up Concepts (2)(2)

Semantic Meaning Can Be Embedded Semantic Meaning Can Be Embedded in the Mark-upin the Mark-up– Tags Describe/Define Meaning of Data

in Field

• Data Between Tags Can be the Data Data Between Tags Can be the Data or a Reference to Data Locationor a Reference to Data Location– Enables Single Location/Instance of

Data– Ease of Maintenance


Semantic Mark-Up Semantic Mark-Up ExampleExample

Example STEP(like) FileExample STEP(like) File#1=application_context (FEM Analysis);#1=application_context (FEM Analysis);

#2=(application_protocol_definition#2=(application_protocol_definition

(ap-jwn1,1999,v0.5,#1));(ap-jwn1,1999,v0.5,#1));

#3=(application_context-#3=(application_context-element(‘automotive’,#1)element(‘automotive’,#1)

product_context(‘newtruckdesign));product_context(‘newtruckdesign));

……..

Tags correspond to Elements in Tags correspond to Elements in Data ModelData Model


Common Common Understanding of Understanding of

Meaning/InterpretationMeaning/Interpretation• OntologyOntology

– The meaning of data or knowledge (semantics) and the understanding of the background needed to draw proper inferences about the use of the data or knowledge.

– For communication to occur, a common ontology must be present.




Segment D Topic:Segment D Topic: Concepts of Data Concepts of Data


advanced manufacturing systems design © 2000 john w. nazemetz lecture 11 topic : information...

Documents

information technology

data platform

product life cycle

distributed business

virtual world segment

formation key elements

nazemetz lecture