Tsinghua University Service-Oriented Enterprise Coordination Prof. Dr. Yushun Fan Department of Automation, Tsinghua University, Beijing, China Feb. 15th, 2008

CIMS Introduction Implementation methodology Key technologies Agenda Conclusion

CIMS Introduction Integration and Coordination  Integration—technologies, methods  Coordination--objectives  Integration is the methods and technologies to be used to make the whole system coordination

CIMS Product Product develop ment Servic e C3P PLM buyer seller logistics Suppli er cust ome r Value chain Enterprise manufa cturing mana geme nt CRM SCM ERP MES PDM Enterprise Integration model-ISO TC 184

CIMS Why SOA “Today’s IT architectures, arcane as they may be, are the biggest roadblocks most companies face when making strategic moves.” –McKinsey “Flexible IT, Better Strategy” “Today’s IT architectures, arcane as they may be, are the biggest roadblocks most companies face when making strategic moves.” –McKinsey “Flexible IT, Better Strategy”

CIMS Why SOA  Today many IT infrastructures are rife with hard-wired connections that enable applications both in and outside of the enterprise to communicate. N * (N-1) connections  However, this hard wiring makes it difficult for companies to adapt business processes to changing needs and market conditions.

CIMS Why SOA  A recent survey of top Global 400 companies revealed  CEOs recognize that in order to quickly respond to increased globalization, economic volatility and drive growth they need a more responsive IT organization that can quickly adapt to changing business priorities;  an IT organization that is tightly aligned with business strategies in a cost effective manner;  and an integration environment that is secure and well managed.  Gartner expects that by 2007 in order to address these business challenges, most enterprises will have started down the path of enterprise-wide SOA.

CIMS Why SOA N connections  SOA leverages an organization’s existing investment by taking advantage of current resources, including developers, software languages, hardware platforms, databases and applications.  Organizations that properly used SOA achieved a 40- percent gain in development resource use, reduction in cost, reduction in risk and eased technical support management and monitoring.  The reduction in cost is exponential as the library of enterprise components grows.

CIMS SOA conceptual architecture ESB Routing Transformation Mediation Monitoring Security Publish/Subscribe QoS Service Integration and Orchestration Process Choreography Common Information Model Message Transformation Common Store User Interaction Services Application Components Events Partner Connections

CIMS Introduction Implementation methodology Key technologies Agenda Conclusion

CIMS System construction  The construction of SOA-based enterprise collaborative management system mainly can be divided into three stages:  Collaborative modelling Multi-views business modelling describes enterprise business MDA technology is used Business model is transformed into platform-independent business collaborative model Platform-independent business collaborative model is mapped into platform-specific business collaborative model

CIMS System construction  Service oriented information system construction Software modules in multi-enterprises information system are identified, encapsulated and published into services Build service components libraries The services in these libraries can be composed and choreographed  Collaborative operation and evaluation In the process of system operation, the performance of enterprises business process is monitored, analyzed and optimized by workflow management system.

CIMS Architecture

CIMS Construction implementation methodology

CIMS Introduction Implementation methodology Key technologies Agenda Conclusion

CIMS Collaborative scenario

CIMS Collaboration modes  Collaboration refers to four elements  Process  Role  Service  Data  Collaboration can be classified into collaboration between any pair of process, role, service, data:

CIMS Collaborative meta-model  Meta-model helps to establish an environment in which business knowledge can be captured and business rules can be traced from their origin be traced from their origin  It forms the foundation of collaborative modeling  Based on MOF, existing workflow meta-model

CIMS Collaborative modeling  Collaborative business model need to support complex collaboration relationships  Reflect enterprise business requirement  Keep the consistency between collaborative business model and business requirement  Model mapping method is used

CIMS Transformation process Collaborative Business Requirement Collaborative Model

CIMS Service matching & composition framework UDDIData mediation Ontology Abstract process definition Service matching & composition Monitoring & improvement Internet … S1 S2 Sn Process enactment Computing, logistics resources Services

CIMS Workflow in Service-Oriented Environments  Workflow in service-oriented paradigm presents some new characteristics:  Services are implemented by workflow  Workflow is just another kind of services  There are multiple processes running at the same time They communicate with event/messages and share the common resource or data  The processes change dynamically along with the change of services

CIMS Workflow in service-oriented environments

CIMS Service oriented workflow architecture

CIMS Application scenario

CIMS Introduction Implementation methodology Key technologies Agenda Conclusion

CIMS Conclusion  SOA based integration is a good way to realize enterprise coordination  The system architecture and implementation methodology of SOA-based collaborative management system are presented  Some key technologies are given  Collaborative meta-model technology  Collaborative modelling  Service matching & composition  Service oriented workflow

CIMS Thank you ！ 28