CIXS Common Information exchange Specification. Cisco adoption of open standards

Size: px

Start display at page:

Download "CIXS Common Information exchange Specification. Cisco adoption of open standards"

Alexander Garry Evans
10 years ago
Views:

1 CIXS Common Information exchange Specification Cisco adoption of open standards John Varughese Data Architect, Enterprise Architecture, OAGi Board Member Cisco Systems March,

2 Background & Evolution of CIXS Customer, Partners, Vendors B2B Orders, Invoices, PR, PO, Remittances B2B Standards, Fax, , etc. Cisco uses industry agreed standards Standards for both Framework & Payload Standard: B2B Standards Process Integration A2A Customer Validation, Get Address Info Messaging, Web Services Lack of agreed standards across the enterprise Framework & Payload Standard: CIXS Data Integration ETL Bulk Data movement between applications EDW, Data marts, ODS Lack of agreed standards across the enterprise Payload Standard: CIXS, ERD 2

Validation, Get Address Info Messaging, Web Services Lack of agreed standards across the enterprise Framework & Payload Standard: CIXS Data

3 Application Integration Landscape SJxxxx CRMxxx HRxxx HRxxx WIPS WIPS CUSTOMER Costly Complicates Disaster Recovery Solutions SJOExxxx BVOExxx ODS ODS EDW EDW Maintenance is a challenge OE Systems Not Scalable Increase Release Management complexity Impact Analysis is made difficult 3

BVOExxx ODS ODS EDW EDW Maintenance is a challenge OE Systems Not

4 Mappings in Application Integration One UNIQUE set of mapping unit needs to be created between EACH pair of applications CUSTOMER ERP 4 * (4 1) = 12 4 applications to integrate can result in 12 DISTINCT integrations / transformations B2B EXTERNAL Exponential growth PARTNER DB 10 * (10 1) = applications to integrate can result in 90 DISTINCT integrations / transformations 4

12 DISTINCT integrations / transformations B2B EXTERNAL Exponential growth PARTNER DB 10 * (10

5 Where Are Your Support Money Going? * MAINTENANCE consumes between 60 PERCENT and 80 PERCENT of a typical product's TOTAL software lifecycle EXPENDITURES E-CUSTOMER ERP Hypothetical 1 Interface or transformation Num System s 1 to 1 1 to 1 ~ $100 Annually 1 0 $ $2, $9,000 B2B EXTERNAL Distinct interfaces each requiring Analysis Design Build Test Release Support PARTNER DB $21, $38, $60, $87, $119, $156,000 N * (N -1) * Yau, S. S. and T. J. Tsai, "A Survey of Software Design Techniques," IEEE Transactions on Software Engineering, 5

Interface or transformation Num System s 1 to 1 1 to 1 ~ $100 Annually 1 0 $0 5 20 $2,000 10 90 $9,000 B2B EXTERNAL Distinct interfaces each requiring

6 Common Information exchange Specification (CIXS) Reduces Number of Mappings With a common internal definition the number of interfaces and transformations are DRAMATICALLY reduced n * 2 instead of n * (n-1). CUSTOMER ERP CIXS 4 * 2 = 8 4 applications integrated using this technique can result in a maximum of 8 DISTINCT integrations / transformations B2B EXTERNAL PARTNER DB Reduced Mappings 10 * 2 = applications integrated using this technique can result in a maximum of 20 DISTINCT integrations / transformations 6

CUSTOMER ERP CIXS 4 * 2 = 8 4 applications integrated using this technique can result in a maximum of 8 DISTINCT integrations /

7 Reduce support money by using of data standard * MAINTENANCE consumes between 60 PERCENT and 80 PERCENT of a typical product's TOTAL software lifecycle EXPENDITURES CUSTOMER B2B EXTERNAL Reduced number of interfaces Reduced analysis due to common definition - CIXS Mapping done once Build once Test Release Support fewer mappings ERP PARTNER DB Hypothetical 1 Interface or transformation ~ $100 Annually Num Systems 1 to 1 CIXS 1 to 1 CIXS Diff $0 $0 0% $2,000 $1, % $9,000 $2, % $21,000 $3, % $38,000 $4, % $60,000 $5, % $87,000 $6, % $119,000 $7, % $156,000 $8, % N * (N -1) N * 2 * Yau, S. S. and T. J. Tsai, "A Survey of Software Design Techniques," IEEE Transactions on Software Engineering, 7

Annually Num Systems 1 to 1 CIXS 1 to 1 CIXS Diff 1 0 0 $0 $0 0% 5 20 10 $2,000 $1,000 200% 10 90 20 $9,000 $2,000 450% 15 210 30 $21,000 $3,000 700% 20 380 40 $38,000 $4,000 950% 25 600 50 $60,000

8 Integration Scenario - I Portals & Mobility: With a common internal definition the number of interfaces and transformations are DRAMATICALLY reduced B2B EXTERNAL B2B B2B Standards Standards System A System B Web Application Mobile devices 8

transformations are DRAMATICALLY reduced B2B EXTERNAL B2B

9 Integration Scenario - II Distributed business data objects: With a common internal definition the need of REPLICATION reduced B2B EXTERNAL B2B B2B Standards Standards System A System B Web Application Aggregator 9

of REPLICATION reduced B2B EXTERNAL B2B B2B Standards

10 Integration Scenario - III Business Rule Engine: A common internal definition is a critical component for successful business rule engine implementation B2B EXTERNAL B2B B2B Standards Standards System A System B Web Application Business Rule Engine 10

business rule engine implementation B2B EXTERNAL B2B B2B

11 Integration Scenario - IV Usage in Data Warehouse: Usage of common data definition enables the data warehouse to be real-time, in-turn provides real-time BI System A System B ETL EDW 3NF ETL EDW Published System C 11

warehouse to be real-time, in-turn provides real-time

12 A Few CIXS Business Data Objects Enterprise CIXS (Example) Sales Agent Product Pricing Employee Opportunity Quote Sales Order Contract Sales Territory Partner Customer Product Discounts Promotions Contact Shipment 12

Opportunity Quote Sales Order Contract Sales

13 CIXS & Data Management Framework Why? Definition What? Business Process Policies How? Where? System Of Record Trustee & Stewards Who? 13

14 Cisco s Experience of Adopting OAGIS Increase data quality by using commonly understood definition of data Reduce development time for integration, by reuse of mapping units Reduce data redundancy by enabling real-time aggregation of business data objects Enable loose coupling, gives independency for application and database changes Data Governance Data Governance made possible by defining System of records 14

enabling real-time aggregation of business data objects Enable loose coupling, gives independency for

15 Q & A 15

16 16

SAP Business Warehouse Powered by SAP HANA for the Utilities Industry

SAP White Paper Utilities Industry SAP Business Warehouse powered by SAP HANA SAP S/4HANA SAP Business Warehouse Powered by SAP HANA for the Utilities Industry Architecture design for utility-specific