Approach and experiences from an ATHENA viewpoint

1. Approach and experiences from an ATHENA viewpoint Position Statement for Networking session “Enterprise Networks: How to overcome the Obstacles to their effective Diffusion" Rainer Ruggaber, SAP IST 21.-23.11.2006 Helsinki, Finland

2. Note: taken from Maria-Jose Nunez (AIDIMA) eProcurement Pilot: Storyboard

3. Note: taken from Maria-Jose Nunez (AIDIMA) Pilot Goals • Become a more agile and efficient enterprise from the Suppliers’ and Retailers’ point of view • Address SMEs high “perception of risk” on investment • Investments must be very low and strongly “guaranteed” • Reduce order processing duration • Reduce the number of wrong orders • Improve internal organization integration

4. Major reduction in false/incorrect orders Better integration between internal systems Dramatic shortening of timefrom order to delivery Business Objectives Dramatic reduction in surplus stock in warehouse Ability to search new providers and apply selection criteria to rate those providers Note: taken from Maria-Jose Nunez (AIDIMA) Needs and expectations • Repetitive manual process for regular bulk orders: Repetition of periodic processing of similar or identical orders • Confusion resulting from poor product descriptions: Wrong products • Missing information: Ensure the integrity of orders and RFQs • Shortening Lag Time: Direct effect on the delivery date of the finished product • Time spent rating supplier

5. Industry Partners ATHENA – Fact Sheet Research Partners Vision: By 2010, enterprises will be able toseamlessly interoperate Approach: Interoperability must address all aspects of Enterprise collaboration Enterprise A Enterprise B Technology Providers Business Business Processes Processes Services Services Information Information • Some numbers: • 3 year project (started Feb 2004) • Budget of 26.5M€ (Grant: 14.4M€) • FP6 call 1

6. CBP Design Time: 3-Level Modeling Approach • Business level: • stakeholder: Business expert • business view on cooperation • e.g. ARIS • Technical level: • stakeholder: IT architect • bridging gap between business and execution level • SAP Research Tool Set • Execution level: • stakeholder: Administrator • executable business processes • e.g. BPEL, SAP Business Workflow

7. View Process Send RFQ Create Order Receive Order Conformation … Create RFQ Create Quotation Create Order Confirmation Receive Order Conformation RefineSolution … Cross-Org. Business Process (CBP) Create Quotation View Process Send Confirmation Create RFQ … Create Confirmation Calculate Production plan Create Quotation Receive Order Create RFQ Private Process … WebServices Process Abstraction Concept WebServices Create Order Select Supplier Compare Quotations Private Process Receive Order Conformation Create RFQ … Retailer Manufacturer

8. Future Technical Research Topics • Ensure appropriate levels of visibility of shared and private process parts during collaborative modeling • Propagation of changes: • CBP -> private processes • Private processes -> view processes -> CBP • Investigate additional operations for abstracting processes • Identify useful combination of modeling procedures • Refine transformations (down/up) between the process models on the different modeling levels • Integrate collaborative working environments with methods and tools for process modeling

9. Conclusions • Research Projects can • demonstrate what is possible • educate on concepts and technologies • indirectly help with the selection of operational solutions • experience with application of technology • It is difficult for Research Projects to • provide solutions / tools for operational environments • provide sustainable maintenance & support • provide detailed consulting on existing SW and its integration • Uptake of solutions is hindered • effort to teach & educate on concepts and tools • not “production ready” tools