1 / 28

Handling Distributed Data Case Study: Raytheon

Handling Distributed Data Case Study: Raytheon. Ross Scott CS561 04/01/04. Agenda. Description the problem space Attempt 1: Distributed Database Attempt 2: Data Warehouse Attempt 3: Federation Q & A. Program Management. Engineering. Supply Chain. Manufacturing. Finance.

yair
Download Presentation

Handling Distributed Data Case Study: Raytheon

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Handling Distributed DataCase Study: Raytheon Ross ScottCS56104/01/04

  2. Agenda • Description the problem space • Attempt 1: Distributed Database • Attempt 2: Data Warehouse • Attempt 3: Federation • Q & A

  3. Program Management Engineering Supply Chain Manufacturing Finance Problem Space Several functional disciplines that need to communicate with one another.

  4. Problem Space: Engineering SFDM ScanCenter PRO/I WebCitis WSTR RVT RDS ECMS Optegra RCT Rasters Mentor ACMS Mears TENS PRACS PEPS Vendor/ SCD CR DB AIMS TeamPort HAWK PATRIOT Standard- ization File H/W Classification DB EDIS Portsmouth POWER (SAP) BEIMS WebView Sherpa Portsmouth Sherpa SanDiego Procurement D ClearCase Shop Order Patriot Obsolesence DB WINS AutoCAD Doors Homogeneous Data Stored in Heterogeneous Systems

  5. Program Management SFDM ScanCenter PRO/I WebCitis WSTR RVT RDS ECMS Optegra RCT Rasters Mentor ACMS Mears TENS PRACS PEPS Vendor/ SCD CR DB AIMS TeamPort HAWK PATRIOT Standard- ization File H/W Classification DB EDIS Portsmouth POWER (SAP) BEIMS WebView Sherpa Portsmouth Sherpa SanDiego Procurement D ClearCase Shop Order Patriot Obsolesence DB WINS AutoCAD Doors Finance Problem Space Supply Chain Manufacturing Heterogeneous Data Stored in Heterogeneous Systems

  6. Program Management Program Management Program Management Program Management Program Management Program Management Engineering Engineering Engineering Engineering Engineering Engineering Supply Chain Supply Chain Supply Chain Supply Chain Supply Chain Supply Chain Finance Finance Finance Finance Finance Finance Manufacturing Manufacturing Manufacturing Manufacturing Manufacturing Manufacturing National Problem Space Homogeneous Data Stored in Heterogeneous Systems

  7. How Do We Handle This? Monolithic Server Distributed Database

  8. Monolithic Server • What is a monolithic server? - One single server for each primary business discipline MasterServer • Pros • - Simplified Domain Space • - Common Data Model / Common Process • - Lower system maintenance costs • Cons • - Cost of migration • - Loss of local control • - Slow to make changes to system Cost too prohibited to create a monolithic server.

  9. Distributed Databases • What is a distributed database? • - A collection of several different databases that looks like a single database to the user. • Pros • - Leverage existing investment • - Local control, enterprise visibility • Cons • - Complex to do data mapping • - Potential network latency issues What is the difference between Distributed Database vs Replication?

  10. System Requirements • Realtime • Manufacturing • Work in Process • Prototype Engineering Release Data Keep it simple. Prove the technology.

  11. Distributed Vaults • Start simple by combine homogeneous data in disparate systems Sudbury Tewksbury Optegra Optegra • Pros • - Distributed vault successful • - Each system has visibility into each system • - Both systems look like one • Cons • - Network Latency slows entire system performance- Slowdown makes system • unusable Network Latency creates too much downtime.

  12. Now What Do We Do? Data Warehouse

  13. Data Warehouse • What is a data warehouse? • “A data warehouse is a structured extensible data environment designed for the analysis of non-volatile data, logically and physically transformed from multiple source applications to align with business structure, updated and maintained for a long time period, expressed in simple business terms, and summarized for quick analysis.”

  14. Data Warehouse Intralink Optegra CIMMS FILESYSTEM Sherpa EDMS SherpaWorks RDM Metaphase

  15. Data Warehouse contd. Data Warehouse Florida Site ID: 87 Texas Site ID: 50 Arizona Site ID: 30 California Site ID: 40 Northeast Site ID: 20

  16. Data Warehouse Initial Search Detailed Page Obtain an Account View Drawing

  17. Data Warehouse • Pros • - Leverage off of existing investment • - Inexpensive to stand up • - 6 months to build • - 8 hours to bring on new site • -Network Latency not as critical • Cons • - Cannot support real-time Delete and Update 31 million unique rows loaded nightly!

  18. Federation • What is Federation? • The linking together of information management systems for the purpose of distributed, collaborative, product development. • The creation and use of a heterogeneous network of data and processes where portions of the network are managed by different systems, yet the user sees a unified whole • What is a distributed database? • A collection of several different databases that looks like a single database to the user.

  19. Federation: Data Network • What is the definition of a Data Network? • A network consisting of associations between data in distributed systems • Associations can be built using three techniques: • Links • Proxies • Replicas

  20. Client request Client request Client redirect Cost A DB DB Cost A A Run time Generated Replica Master Proxy Link Cost A Federation by Link Corporate Systems Mfg Center Firewall Firewall Sourcing Report Inventory Windchill Server ERP Server Part A Cost A File Vault

  21. Federation by Link • Best use of links • When remote system has a Web-based UI and supports URL references to its objects and user is comfortable with switching between applications

  22. Select Part where Name = B Client request Display attributes Proxy B Return Part B attributes DB DB B A Run time Generated Part B Run time Replica Master Proxy Link B Federation by Proxy Design Center Design Collaborator Firewall Firewall Structure Browser Windchill Server PDM System Part A Part B File Vault

  23. Federation by Proxy • Best use of proxies • For consistent user interface to data residing in multiple systems • To be assured that you are looking at the latest up-to-date data • When data is loosely coupled, infrequently accessed • When you need to modify remote data without conflicts • For relating dissimilar data types residing in external systems • For composing data from multiple external systems (composite types) • When data is frequently accessed in a read-only mode

  24. Client request Client request Display part or stream content file Display part or stream content file Replicate Part B and Doc C Doc C Content replicated DB DB C B C B Doc C Replica Doc C C C A Run time Generated Replica Part B Replica Master Proxy Link Federation by Replica Design Center Supplier Firewall Firewall Structure Browser Structure Browser Windchill Server Windchill Server Part A Part B File Vault File Vault

  25. Federation by Replica • Best use of replication • For consistent user interface to data residing in multiple systems • To maximize end-user system performance • To overcome availability, security, restrictions

  26. Federation: Process Networks • Federated data is of limited use without having the business processes involving the Federated systems also being able to interact • Process networks should support: • Workflow interaction • Activity in local workflow, initiates a workflow in a remote system • Remote approval of activities • Change process interaction • Local change order initiates change activity in remote system • Federated task lists containing items from multiple systems • Event-based interaction • Each system both publishes events and responds to events in other systems (JMS, MQ Series, etc)

  27. Questions? How would a middleware vendor define Federation? How would an end solution provider define Federation? Any Questions?

  28. Bibliography • Distributed Databases • Data Warehouses • Federation • Network Performance

More Related