1. ON THE ROAD TO BUSINESS APPLICATIONS OF SEMANTIC WEB TECHNOLOGY Sematic Web in Business - How to Proceed IASW2005 - 27.8.2005 Kari Oinonen Kiertotie 14 as 3, 40250 Jyväskylä, e-mail: karioinonen@kolumbus.fi

2. Purpose of the paper ● The purpose of the paper is to aid semantic technology to wider use in business applications.

3. Presentation structure ● Business applications and Semantic WEB ● Development trends and Semantic WEB ● On the need of general application and business framework ● Road Map Plan ● How to continue

4. Business applications and Semantic WEB ● General status of sematic Web in business applications ● Topics that slow down adoption of this technology into business use

5. Business applications and Semantic WEB ● Applications are existing: ● Public applications ● Industrial applications ● Applications that are not public ● General status of sematic Web in business applications

6. Business applications and Semantic WEB ● Topics that slow down adoption of this technology into business use: ● Complexcity of the technology or its usage. ● The technology and its potential is not yet generally known in business world. ● Publicly available technology examples are more or less trivial. ● Existing business applications and business models. ● Guarantee of investments in the technology. ● New application areas are not easy to recognice. ● Lack in the integration of problem, domain and technology expertice. ● General status of sematic Web in business applications

7. Development trends and Semantic WEB ● Life-cycle ● Dynamization ● Multiplication cycle ● Transition from macro to micro level ● Synchronization ● Scaling up or down ● Uneven development of parts ● Automation Ref. Altchuller, G. 1998 ● General technology trends:

8. Development trends and Semantic WEB ● Technology convergence in telecommunication. ● Internet infrastructure gaining importance. ● Changes in communication technology:

9. Development trends and Semantic WEB ● Complexity is increasing. ● Management of information related to several different life-cycle -phases of a product or service. ● Management of information belonging to different engineering disciplines. ● Management of information originally created and maintained in separate IT systems or solutions. ● Management of information originally created and maintained in different organizations. ● Changes in business needs:

10. On the need of general application and business framework ● More interoperability between semantic applications. ● Many of the needed tools in technology are available, but a common understanging of how to use those tools is lacking. ● Road map -process creates a more unified view of how the technology can or could be used best way. ● Road map -description aids other people to understand the technology, how it can be used, relations to other needed or beneficial technologies, where it can be used and what will be future development steps. ● Ontology management. ● Information security.

11. Road map plan ● Road map definition process ● Use suitable well defined format. ● See an example in the next slide. ● Have appropriate people and organizations involved. ● Look at interdepencencies.

12. 2 Theme current state 3’ Theme intermediate state 1 Theme vision Start from here Go to the current moment Move to the future The Roadmap ProcessThe Roadmap Documentation Steps to the vision Current state Positives, what is good, what we can, what exists Negatives, to be developed, restrictions Short term Medium term Long term Theme/Topic and its vision 2 Theme A current state 3 Theme A intermediate state 3’ Theme A intermediate state 1 Theme A vision 2 Theme B current state 3 Theme B intermediate state 3’ Theme B intermediate state 1 Theme B vision 2 Theme C current state 3 Theme C intermediate state 3’ Theme C intermediate state 1 Theme C vision 3 Theme intermediate state

13. Road map plan ● What semantic technology standards to use and where. ● Relations and connectability to existing standards like STEP or modeling activities like Epistle or CIM-OSA or RUBIC. ● Needed functionality. ● Guarantee of future compatibility ● User interfaces – multidimensionality. ● Information integrity and security. ● Other fitting or supporting technology. ● Road map and technology topic:

14. Road map plan ● Finding of information and recources. ● Classification of information. ● Information collection. ● Maintenance of information links. ● Information analysis based on other information or knowledge. ● Knowledge management. ● Road map and use cases -topic:

15. Road map plan ● The meaning of the technology in terms of costs and benefits for the end customer or user. ● The effects of sematic technology in service or knowledge business. ● Enterprise application integration or similar functionality. ● Life-cycle support of products and services. ● Network type of information models in heterogenous environment. ● Current and future needs in industry. ● The most promising application areas for the technology – business point of view. ● Road map and business and usage -topic:

16. Road map plan ● Existence of and applicability of existing ontologies. ● Possibilities to form ontologies based on existing terms and concepts in use. ● Need of more local ontologies still maintaining interoperability. ● Maintenance and ownership of ontologies. ● Coordination of ontologies management. ● Road map and ontology -topic:

17. How to continue ● Build a rough Road map plan by a small group of experts. ● Iterate and make changes as needed by input from industry, field experts and standards owners. ● Publish main results of the Roadmap.

18. Summary ● Business applications and Semantic WEB ● General technology trends and Semantic WEB ● On the need of general application and business framework ● Road Map Plan ● How to continue