DesignState Intralink to Agile Demonstration

Zero Wait-State Company Confidential

Agenda– Definition of Zero Wait-State– Zero Wait-State in Product Development– About ZWS– DesignState Architecture– ZWS Engagement Model– Demo– Next Steps– Discussion

What is Zero Wait-State?

Wait-state: a time-out period during which a CPU or bus lies idle. Wait states are sometimes required because different components function at different clock speeds.

Zero Wait-state: an environment in which a CPU can process information at its optimal speed without having to wait for other components to catch up.

What is Zero Wait-State in Product Development?

Wait-state: Unnecessary delays in the product development cycle.

Zero Wait-state: An environment that is fully optimized to eliminate unnecessary delays in the product development cycle.

Email

FTP

Courier

ProposalsCustomer Requirements

Part DesignsBoMsChanges

CustomConfigurations

RequirementsDesign Feedback

Field Notices

ModelsDrawingsSimulations

ConceptsRequirements

Market RequirementsBrochures, Data Sheets

Preferred PartsApproved Vendors Feasibility

FeedbackTooling DesignsWork InstructionsNC Programs

Customer Concerns

Failure Reports

User, Service Manuals

SneakerNet

Distributed MfgDistributed Mfg

SupplierSupplierSupplierSupplier

SupplierSupplier

Distributed MfgDistributed Mfg

Distributed MfgDistributed Mfg

CustomersCustomers

CustomersCustomers

CustomersCustomersCaptiveODC

CaptiveODC

OffshoreDesign Partner

OffshoreDesign Partner

LocalDesign Partner

LocalDesign Partner

ManufacturingManufacturing

ServiceService

ProcurementProcurement

EngineeringEngineering

MarketingMarketing SalesSales

TechnicalIllustrations

Wait-States in Product Development

• Executing a change when necessary files live in multiple systems…

• Creating new parts from scratch when you know they already exist (but are WAY too hard to find)…

• Everyone asking engineering to do something for them (e.g. create a photo rendering or a “simple” view of a design for making a technical illustration)…

• Tracking the impact of one change across a full product platform…

• Figuring out who has the latest version of “xyz”…

• Managing the work of many partners simultaneously and making sure they are working on the right data…

These are just a few examples, do you have any others?

About Us

• Operating since 1999• Over 150 customers both small and

large• Partnerships with key technology and

service providers (PTC, Oracle, Microsoft, VMWare)

• Domain Experts in Product Development solutions

• Extensive background in software development and deployment

Zero Wait-State Company Confidential

Slide 7

DesignState Windchill to Agile (WC2A) Capabilities

• DesignState WC2A– Transfers BOM Structure from Windchill to Agile– Supports publication of native data or viewable formats

into Agile– Publication can be interactive or event driven– Publications are maintained in the synchronization log for

accuracy– Compatible with Agile’s change management functionality

• Can initiate, drive, and report on the change process between the two systems

• Maintains control and synchronization during the change process

Slide 8

DesignState Architecture & Process Flow

DesignState

State Change Rules Engine• Synchronization• Transformation

ECO Created

ECO Released• Part number assigned• Released State

DesignState communicates with PDMlink utilizing the API

DesignState communicates with Agile through the Agile SDK Connector

Policies dictate when information is published and how the information is transformed

Slide 9

ZWS – Webapp

ZWS – DesignState

Windchill Intralink

UGS Teamcenter

PDM Publisher

PFP

!Events

!Events

PD

M2A

gile

Intralin

kP

DM

2Ag

ileTeam

center

Event Queue

A~A

Synch-Log

View

MCAD Architecture

PLM API

Agile PLM

!Events

Pro/Engineer Intralink

System Overview

PartDummy.prtNO_PUB

Assembly

top_boom.asm3086071-101

Agile PDM

Drawingtop_boom.drw

3086071

Part: 3086071-101

Part: 3086072-001

Part: 3086073-001

DesignState

Native Pro/E Filetop_boom.drw

PART_NUMBER3086071

Native Pro/E Filetop_boom.asm

PART_NUMBER3086071-101

PartCam_plate.prt3086072-001

Doc: 3086071DOC

3086071.pdf

3086071-101.stp

Native Pro/E FileCam_plate1.prt

PART_NUMBER3086072-001

Create New

NR or ECO

Promote to Pending

Native Pro/E FileDummy.prt

PART_NUMBERNO_PUB

PART_NUMBER3086073-001

Native Pro/E FileLibrary.prt

PartLibrary.prt

3086073-001

Create/Update

Create/Update Object

Sync to File

Create/Update Object

Sync to File

Create/Update Object

Sync to File

No object published

Add to BOM

Library parts are not synchronized

Doc: PL3086071

Process Overview

AgilePro/E

• Explicitly published objects are added as affected items on COs.

• Files explicitly published together (same RTP form), are combined onto COs, if PA (Project) matches and require the same CO type (NR, ECO).

• If a CO exists which has the affected item listed on it already:• The CO will be Redlined/updated if it’s

not yet at the submitted state in Agile.• The publishing event will Cancel if it’s at

the submitted state or higher.

• Republishing Intralink objects to EXISTING Agile objects WILL NOT update attributes.• Items NOT from a Library folder will

redline DESCRIPTION on a C/O.

• Explicitly published objects are added as affected items on COs.

• Files explicitly published together (same RTP form), are combined onto COs, if PA (Project) matches and require the same CO type (NR, ECO).

• If a CO exists which has the affected item listed on it already:• The CO will be Redlined/updated if it’s

not yet at the submitted state in Agile.• The publishing event will Cancel if it’s at

the submitted state or higher.

• Republishing Intralink objects to EXISTING Agile objects WILL NOT update attributes.• Items NOT from a Library folder will

redline DESCRIPTION on a C/O.

Intralink

• Create/update Models/Drawings.• Build structure (CAD BOM).• Use the ‘Agile’ table to generate balloons

(assembly drawings) and ‘fix’ find numbers• Create a FN file (optional)

• Create/update Models/Drawings.• Build structure (CAD BOM).• Use the ‘Agile’ table to generate balloons

(assembly drawings) and ‘fix’ find numbers• Create a FN file (optional)

• Promote objects in CS, OR• Promote the objects during Check in• Promote ONLY the objects to be

explicitly published (on a C/O).

• Promote objects in CS, OR• Promote the objects during Check in• Promote ONLY the objects to be

explicitly published (on a C/O).

MCAD Interface• Checks for:• Parameter/attribute validity• Existing Agile Objects• Existing Agile C/Os

• Actions:• Objects created/modified• Objects synchronized• Viewables created/attached• Structure created/modified

• Check in modified objects • Use the Agile configuration table in Intralink to

easily check for parameter validity:• PART NUMBER• CAGE CODE• PROJECT• Description

• Check in modified objects • Use the Agile configuration table in Intralink to

easily check for parameter validity:• PART NUMBER• CAGE CODE• PROJECT• Description

Consistent Results

• Established processes leads to higher quality solutions and faster time-to-market

• Internal support infrastructure in place for quality customer relationship management

• Focused on providing tangible, measurable value to our clients

• Leveraging Industry best practices ensures high impact/low risk solutions

Zero Wait-State Company Confidential

Zero Wait-State Benefits

• ZWS methodology maximizes value for the client

• Tailored solutions impact critical issues • Domain knowledge ensures maximum results• Partnerships give clients access to best in

class resources and applications

Zero Wait-State Company Confidential

Next Steps

• Schedule a discovery workshop

• Map out key departments and personnel that can provide a full view of your product development process

• ZWS will conduct the discovery and gather data for a scope document

• ZWS will present scope document with recommended solutions.

• Client reviews results and recommendations