“DIP Integrated Project Proposal Meeting” Frankfurt, 17th January 2003 Alessandra Bagnato

1. “DIP Integrated Project Proposal Meeting”Frankfurt, 17th January 2003 Alessandra Bagnato International R&D Area TXT e-Solutions SpA, Milano (Italy)

2. TXT - Key facts & Figures • TXT e-solutions (TXTS) • Quoted at Milan stock exchange • Year 2001 facts and figures • Revenues: 30 M€ (42 M€ est 2002) • TXT personnel • 350 employees (400 est 2002) • TXT offices & hubs • Italy: Milan Turin Genoa Bari Rome • France: Paris • Germany: Frankfurt • Spain: Barcelona • UK: London • More info on our web site: http://www.txtgroup.com

3. DivisionalR&D DivisionalR&D DivisionalR&D EC ProjectsSC&CM EC ProjectsMCM EC ProjectsPRS Int. R&D Area TXT R&D Structure Applications for the media & editorial industry Professional services SC&CM applications for manufacturing & service enterprises EC Projects Follow-ups SC&CM Division MCM Division PRS Division

4. TXT Contribution to DIP idea The holistic approach proposed in DIP (Data, Information & Process Integration) could be described in terms of an Ontology-based Intelligent Infrastructure, which could be seen both intra- and inter- Organisations.

5. Enterprise Intelligent Infrastructure • An Intelligent Infrastructure (II) is a layered representation of an Enterprise in various forms and formats. • Depending on perspective it can have a varying number of layers and architectural levels (views). • The systems engineering perspective identifies four layers, while the business manager is concerned with these three: Business Model, Enterprise Knowledge ICT (Applications and Data). • A simplified picture of an Enterprise Intelligent Infrastructure could be the green arrow in the following schema Processes Business Knowledge Knowledge Ontologies Semantics Applications Applications

6. Common services provided • An infrastructure provides common services such as: • ensuring the location of components within whatever "coordinate system" is pertinent, • providing access or interconnection, • providing isolation, and • ensuring stabilitythroughout a dynamic scenario of traffic, wear, contextual changes and internal innovations. (From the EXTERNAL Project) • A semantic layer is necessary (in order to be properly understood and mutually inter-operated) for • Business Process Management (including inter-connection and co-ordination) for eCommerce, • Knowledge Management (including the whole K life cycle) • Enterprise Applications Integration, both inside the Enterprise and outside it (extended enterprise).

7. Semantic Web Services and DIP (1/2) • We can identify 3 atomic SWS classes: • SWS for e-commerce (Business Process Mgmt), which are able to harmonise, coordinate and optimise BPs. They will include Modelling (templates fusion), Simulation (performance indicators), Planning (resources optimisation) and Actuation (workflow and document management) Web Services. • SWS for KM, which are able to support the Knowledge life cycle. They will include K creation, K classification, K usage, K sharing and K transferWeb Services. • SWS for EAI, which are able to integrate different functions implemented by different EIS. They will include ERP (ordering, invoicing, billing), SCM (procurement, partners selection, production planning & execution), CRM (help desk, maintenance, post-sales) Web Services.

8. Semantic Web Services and DIP (2/2) • DIP innovation is in complex SWS classes: • SWS for Inter-layer Integration, which are able to handle all the mutual, dynamic interactions among atomic SWS: • Processes which change K Assets (new skills required, new competencies); • New Knowledge Assets which imply modifications in the Business Processes (i.e. a new product, a new procedure); • New Applications which affect both Business Processes and Knowledge Assets (i.e. a new Production Scheduler, a new Resource Manager); • New Business Processes and Knowledge Assets which imply modifications in the ICT level (i.e. the adoption of B2B e-commerce, the adoption of a common standard format or procedure). • SWS for Inter-company integration, which implement an Inter-Enterprise, Ontology-based IntelligentInfrastructure, to integrate the previous 4 SWS classes with experience, common sense and commercial strategies. In a typical B2B e-commerce scenario, they will include Selling, Buying and Negotiation Web Services.

9. The following picture represents the last scenario of Ontology-basedInter-Enterprise Intelligent Infrastructure. Ontology-basedInter-Enterprise Intelligent Infrastructure

10. TXT envisaged role in DIP • Owing to our recent research activities concerning • the Intelligent Architecture for product inter-company configuration (IST-1999-10390 LIAISE), • the Semantic Inter-operability of Enterprise Applications & Software (IST–2001–37368 IDEAS) • the Collaborative paradigm applied to e-commerce (IST-2001-37493 COMPANION), • TXTwould like to play the following role: • WP4 Integration: WP Leader; • WP3-WP6-WP7: Contribution; • WP8: Exploitation of Results in Italy and South Europe.

11. Thank You ! Alessandra Bagnato, TXT e-solutions Email: alessandra.bagnato@txt.it Tel.: +39 010 46103.78 Mobile:+39 348 6913749