Design%20anywhere,%20Build%20anywhere

1
Design anywhere, Build anywhere

• INTEROP ESA 05 Date 24/02/05
• Anne H Waywell

2
Overview

• Background
• Opportunity
• Strategy
• Approach
• Benefits
• Experience
• Conclusion
• Discussion

3
Background

• DNC Distributed or Direct Numerical
  Control 1980
• Machine instructions for NC milling machines
  transmitted over telephone
• Later evolved to mean system where a group of NC
  machines are connected to a central computer or
• A combination of computers are linked to one or
  more CNC machines by LAN
• CNC machines - tools that have a memory to
  control their operation
• NC programs are distributed to the memory of CNC
  machine
• ISO format most widely used
• Use of Standards promote interoperability
  vendor interpretation failed to meet expectations

4
Background

• FMS Flexible Manufacturing Systems 1985

• Arrangement of machines interconnected by a
  transport system giving flexibility to a variety
  of manufacturing operations. Transporter carries
  work to machines on pallets so that work-machine
  registration is accurate, rapid and automatic. A
  central computer controls both machines and
  transport system.

5
Background

• FMS Flexible Manufacturing Systems 1985
• The manufacturing environment considered totally
  automated into a lights out situation
• Proved possible only in limited manufacturing
  applications
• Still remains a goal to produce a fully
  integrated environment even across organisations
  today

6
Background

• OBA Overall Business Architecture 1983
• Took this philosophy to the factory level
• First generation integrated business system
  between design, planning, materials,
  manufacturing, procurement and invoicing
  application systems
• Individual applications
• Were locked together
• Difficult to maintain
• Inhibited business change
• Affected competitiveness of the business
• Were built to aid a discipline, not to integrate
  with other disciplines
• Information was locked into application
• Integration of these applications - expensive
  point to point interfaces

7
Opportunity

• Need for a more modular approach, where
• Data is seen as separate from application
• Information is key company asset and treated
  differently from application
• Data / information needs to be protected as it
  has a life expectancy
• Data standards are used
• XML-xx standards need to be developed like
  platform following STEP for exchanging data
  across PDM Systems via a neutral standard
• This approach was used for the next generation of
  integration for e-Business and outsourced business

8
Case Study - Opportunity

• Depends on interface between PDM and ERP Systems
• To transfer parts or BoMs to allow designed items
  to be manufactured
• Multiple PDM Systems were linked with multiple
  ERP Systems using point to point solutions
• Used Sherpa for PDM, Network MTO (Compass
  Contract) for ERP and Tibco as the Message Broker
• Launched a programme to replace Sherpa PDM System
  with single corporate Metaphase PDM System
• No interface existed between Metaphase and the
  ERP Systems
• Requirement for interface from Metaphase to any
  ERP system, supporting concept of Design
  anywhere, Build anywhere
• Transfer single parts, single level BoMs and
  multi level BoMs

9
Opportunity
Tibco
Tibco
Sherpa
ERP
Sherpa
ERP
Sherpa
ERP
Sherpa
ERP
Sherpa
ERP
Metaphase
Metaphase
ERP
ERP
ERP
ERP
ERP
10
Strategy

• Interface needed to be designed and data
  translations understood
• Previously used proprietary Message Broker and to
  meet needs of interfacing to an External
  Marketplace system
• New corporate Message Broker sought
• Known as Enterprise Application Infrastructure
  (EAI) (webMethods)
• Supports initiatives such as A2A, B2B, B2C, EAI,
  BPM, BPA, EDI
• Deliver true business driven end to end
  integration and interoperability between packaged
  and custom applications, mainframe system
  transactions (legacy), front and back office
  systems, Web services, business partners and
  human workflow

11
Approach
Tibco
Tibco
Sherpa
ERP
Sherpa
ERP
Sherpa
ERP
Sherpa
ERP
Sherpa
ERP
EAI
EAI
EAI
Metaphase
Metaphase
ERP
ERP
EAI
ERP
EAI
ERP
ERP
12
Approach
BOM
BOM
Application 2
Application 1
eAI Broker
PDM Metaphase EDS
IS Adapter
IS Adapter
ERP Network MTO Manugistics
Network Procurement Manugistics
UPLOADER
EXTRACT
e
Application 3
Return errors
webMethods BAE SYSTEMS eAI Backbone
Manugistics Uploader
Metaphase Extract
CSC eAI PDM Adapter
CSC eAI MTO Adapter
13
Metaphase to MTO Interface
Infrastructure
Infrastructure
Metaphase Server
MTO Server
ES (Enterprise Server)
Metaphase
IS Adapter
IS Adapter
Network Procurement
API
MTO
API
Metaphase Extract
MTO Adapter
PDM Adapter
Uploader
Adapter
IS Adapter
Generic eAI Services Log X-Ref

Application API
IS Adapter
IS Adapter
Broker pack Bridge
eAI Broker Server
14
Application 3
Application 2
BOM
BOM
Application 1
Production eAI Broker
PDM Metaphase EDS
ERP Network MTO Manugistics
IS Adapter
IS Adapter
Network Procurement
UPLOADER
EXTRACT
e
PRODUCTION
PRODUCTION
Return errors
FTP
PDM Metaphase EDS
Test eAI Broker
IS Adapter
ERP Network MTO Manugistics
IS Adapter
EXTRACT
Network Procurement
UPLOADER
e
TEST
TEST
Return errors
Metaphase Extract
CSC eAI PDM Adapter
CSC eAI MTO Adapter
webMethods BAE SYSTEMS eAI Backbone
Manugistics Uploader
15
Infrastructure
Infrastructure
Metaphase to MTO Interface
Production MTO Server
Production Metaphase Server
Metaphase
ES (Enterprise Server)
IS Adapter
IS Adapter
Network Procurement
MTO
API
API
Uploader
MTO Adapter
Metaphase Extract
PDM Adapter
Adapter
eAI Production Broker Server
Infrastructure
Infrastructure
FTP
Generic eAI Services Log X-Ref
Test MTO Server
Test Metaphase Server
ES (Enterprise Server)
Metaphase
IS Adapter
IS Adapter
Network Procurement
MTO
API
API
Adapter
MTO Adapter
Uploader
Metaphase Extract
PDM Adapter
Note Network Procurement not installed, but
Adapter has user defined option to specify
Generic eAI Services Log X-Ref
IS Adapter
IS Adapter
Application API
eAI Test Broker Server

IS Adapter
Broker pack Bridge
16
Benefits

• A single software solution in place, consisting
  of 4 modules, utilising the EAI solution, with
  separate paths as required for each business
• Software is easier to maintain
• Allows changes to the modules/adapters
  independently
• Allows legacy information to be stored in
  canonical form in neutral database
• Facilities developed for one site are available
  for other sites if required
• Solution supports the concept of Design
  anywhere, Build anywhere, reducing ordering
  times by 50 and reducing the number of internal
  buyers / procurement staff

17
Experience

• Now possible to link
• internal procurement systems i.e. SAP, BaaN,
  Network MTO to the External Marketplace System /
  Trading Portal (EXOSTAR) supplier catalogues,
  order parts and invoice totally electronically
• Internal HR Systems to external HR Systems

18
Experience
Internal
External
Avionics
EXOSTAR
EAI
EAI
Metaphase
ERP
EAI
ERP
EAI
ERP
ERP- MTO
UWS
EAI
Metaphase
ERP MTO
peoplePortal
Air Systems
ERP BaaN
CSS, RO
HR Systems
ERP SAP
19
Conclusion

• EAI is a strategic platform for information
  exchange between functional areas, within and
  external to an enterprise
• Promoted by Procurement for connecting to
  External Marketplace System and need to reduce
  costs
• Extended to support the outsourcing of HR
  Services
• EAI approach allows modular (component) building
  of a system that has a degree of dynamic
  reconfigurability to meet business need of
  delivering capability for a contract
• Minimal investment costs
• Only one new MTO Adapter ( may be an update to
  Uploader, dependent upon requirements)
• But it is at a price
• Adapter writing approx. 10 days effort
• Specification and understanding of the business
  rules approx. 8 weeks
• Clearly software is NOT a problem
• Business understanding - Modelling is

20
Discussion

• Anne H Waywell
• awaywell_at_csc.com
• Tel. No. 44 7769 725749

21
Experience. Results.