Application Integration Framework for a Large Business Process Redesign Project

Transcription

1 Application Integration Framework for a Large Business Process Redesign Project Practitioner s Report OOPSLA 2000 Minneapolis, MN October 19, 2000 Jon Sholberg Boeing Commercial Airplanes Group Pg.1 11/1/00

2 Agenda The Information Technology situation DCAC/MRM overview Application Integration (AI) framework Lessons learned Future directions for the industry Future directions for The Boeing Company Summary Pg.2 11/1/00

3 The Information Technology (IT) Situation We are at an unprecedented flashpoint in the IT industry. Growth of business-to-business (B2B) e-commerce will change the whole pattern of industry and the IT infrastructure forever. The biggest IT problem today is seamlessly integrating disparate legacy applications with Web portals, Internet servers and commercial exchanges. Large companies require electronic collaboration with suppliers, partners and customers. They need to be able to connect their computer applications with any other computer application via the Internet. Pg.3 11/1/00

4 DCAC/MRM Overview Define and Control Airplane Configuration/Manufacturing Resource Management (DCAC/MRM) Configurator Product Data Manager () Computer-Aided Process Planner (CAPP) Enterprise Resource Planning (ERP) Architecture for DCAC/MRM s application integration began implementing in 1994 Pg.4 11/1/00

5 Business Process Redesign (BPR) Definition and Scope Process DCAC/MRM is Process-Driven Change Data Information Systems/Technology Pg.5 11/1/00

6 Business Process Redesign (BPR) Objectives DCAC/MRM Mission Fundamentally rethink and radically simplify the processes related to airplane configuration definition and production. The Approach Single Source of Product Data Simplified Configuration Management Tailored Business Streams Tailored Materials Management Single Bill of Material Eliminate Effectivity from Drawings TBS 1 Basic & Stable TBS 2 Previously Delivered Options Rate Schedule (Very Simple) Kanban (Simple) MRP II TBS 3 New/Unique Options (Complex) Pg.6 11/1/00

7 Pre-DCAC/MRM Integration Example BASS Spares Inventory PSOL OSCE MRA MAIDS OLS MSUP BLS PICS IBAS SOLS PCA MAST SMART Mainline Computing Systems (point-to-point) Pg.7 11/1/00

8 DCAC/MRM Integration CAPP Baan Metaphase Configurator AI Framework Legacy System Management Services Legacy Security Printing Looser coupled computing environment, minimal dependencies Pg.8 11/1/00

9 Critical IT Success Factors for DCAC/MRM Technology must not delay business process redesign Use best of breed Commercial-Off-The-Shelf (COTS) package Integrate COTS packages with existing production systems Establish and achieve system integration objectives Establish a solid foundation for the future Pg.9 11/1/00

10 System Integration (SI) Objectives Flexibility - accommodate future changes from both external and internal sources Scalability - accommodate current and future growth in users, transactions and data Reliability - provide consistent, dependable delivery of services Performance - must support health of the system, plus address end-user service level expectations Pg.10 11/1/00

11 Application Integration (AI) Pg.11 11/1/00

12 A Simplified View Application A Application B Data Data Exchange Data Pg.12 11/1/00

13 But It s Not So Simple Alarms Performance Mgmt Directory PKI Time Compression Message Integrity Filtering Fault Tolerance Store & Forward Publish & Subscribe Encryption Transaction Configurtion Provisioning Correlation Validation Data Format Resource Control Transformation Authentication Authorozation Activation Scheduling Timeout Augmentation Programmability Load Balancing Accounting Exception Messaging Event Routing Location Container Queuing Data Transport Quality of Service Multicast Addressing Pg.13 11/1/00

14 Adapters simplify data exchange allow developers to use their native application technology... Application A Application B Data Data... and hide middleware complexity. Pg.14 11/1/00

15 How simple? Pg.15 11/1/00

16 Language (Java) Based:.Part.Instance().update(partName, supplierco, note, partnum); File Based: fprintf(file, "%s^a%s^a%s^a%d^b", partname, supplierco, note, partnum); COBOL IMS: IMS TRAN GU ISRT IO-PCB ISRT ALT-PCB Stub Based ("Fill in the blank."): void ::Part::update (char *partname, char *supplierco, char *note, int partnum) { // Insert your code here. // Business logic only, no middleware code! return; } Pg.16 11/1/00

17 Transaction Profile Plus configuration & environment data Pg.17 11/1/00

18 Existing Adapter Types Pg.18 11/1/00

19 Interface Agreement Description of data + Transaction profile + Client & server adapter types Pg.19 11/1/00

20 How to Handle all the Integration Needs? Pg.20 11/1/00

21 Integration Strategies Business Applications ERP Integration Strategies N 2 2N Middleware Pg.21 11/1/00

22 N 2 Integration a.k.a Point-to-Point ERP BaaN to to BaaN ERP to BaaN ERP ERP BaaN to to to ERP Baan to BaaN ERP to to Pg.22 11/1/00

23 2n Integration ERP BaaN Client Adapter Client Adapter Client Adapter Mix... ERP BaaN Client Adapter Server Adapter & Match BaaN Server Adapter Server Adapter Server Adapter ERP Pg.23 11/1/00

24 Application Integration Capabilities Interoperability across technologies and applications Language, platform and application adapters No exposure of middleware, no CORBA coding required Highly distributed applications can run on any host Transparent transport of business data over middleware Server location Fanout Auditing and audit queries Transparent load balancing Fault tolerance with transparent failover Activation of transient processes System management Asynchronous and store-and-forward services File and resource management Public key infrastructure (PKI) security (soon) XML translators (soon) Pg.24 11/1/00

25 Positive Lessons Learned Distributed, object-oriented integration was successful using CORBA and messaging Loosely-coupled, stateless integration enabled COTS applications to be managed autonomously Tough objectives were met: flexibility, scalability, reliability and performance Defining and developing an application integration framework enabled both abstraction and enterprise-wide system and performance management capabilities CORBA and UML standards enabled code generation and assembly of components Using standard components, skilled developers were easier to find Partnering with suppliers was essential to success Pg.25 11/1/00

26 Less Positive Lessons Learned CORBA by itself was insufficient messaging required Standards develop slowly Many services were not readily available (and still aren t) COTS vendors didn t prioritize application integration until lately Integration technology evolved quickly ebusiness has altered integration expectations dramatically Information broker capabilities became mandatory Demands for seamless integration of all types were everywhere XML has recently become wildly successful Pg.26 11/1/00

27 Industry Future CORBA becomes infrastructure J2EE becomes the foundation for standards-based integration: application-to-application (A2A) - internal business-to-business (B2B) - external collaboration - virtual Canonical form of data passed within the middleware (XML) Ability to interface to everything from anywhere is becoming possible Pg.27 11/1/00

28 Next Steps Build upon the existing AI framework to embrace the new technologies Extend the existing architecture to easily facilitate ecommerce Unify integration both within The Boeing Company (A2A) and to outside entities (B2B specifically) Pg.28 11/1/00

29 Future Application Integration Framework Browser Security System Mgmt Personalization Audit HTTP WAP Portal Server Scalability Routing Security Mgmt Profile Mgmt Policy IIOP RMI DCOM HTTP SOAP XML Application Server (J2EE) Business Logic Deployment Session and Process Management Integration Server C++ EJB COM+ OS/390 MES SOAP XML other Data transformation Rules Engine Connectors ERP Enterprise to Enterprise MVS Pg.29 11/1/00

30 Summary Distributed object computing works with CORBA, if it is based on a solid enterprise architecture The demands of ecommerce widen the integration requirements domain dramatically New development for the enterprise is happening on the J2EE application server platform Using both environments together gives the architectural foundation for integration that ecommerce demands Pg.30 11/1/00

31 Thank you. Questions? Pg.31 11/1/00