The figure shows the tools and services of the Business Operations Runtime component of the NEFFICS Platform. The figure highlights the existing assets (background) and the foreground developed (or planned) in the NEFFICS project. All of the tools and services are provided as online solutions in the Cloud. A short summary of the functionality of the tools and services are provided in Table 17.
The Internet of Services and Things (exemplified by COIN and ASPIRE) in the figure shows that general internet services can be used by the platform, and in particular that events from RFID and other sensors can be used as a source for automatic generation of challenges to the innovation community when certain operational situations occur.
- “Internet of Services” represents the concept of collaboration and interoperability with external or existing services on the internet. These services might be exposed by existing enterprise applications, or might be provided by business partners.
- “Internet of Things” represents the concept of collaboration with “smart objects” on the internet. An important aspect of this is, that “things” make themselves and their status known, so that “events” can be captured by a system, to e.g. trigger follow-up processes. A basic way to capture “things” identification and status is by using barcode readers. A more advanced way is to apply RFID tags, whereby RFID applications or services can transform signals into data that can be used to publish events, or that can be exposed by web services.
Table 17: Business Operations tools and services
|Tool/Service||Short Description||Availability Status|
|Inbox framework||Work-list and task management framework, supporting teams and users in organizing, monitoring and managing work that is generated by and in the context of model execution.||Background|
|Support for inter-enterprise (cross-network) business process management, centred around business documents on which network partners collaborate.||Background|
|Run-time framework for execution of UI models.||Background|
|Monitoring, based on Key Performance Indicators (KPIs), which monitoring might be based on business process monitoring data (from BPM engine), as well as from “business data” in enterprise applications, which might be either “existing”, or which are also “mashapp” applications that are developed in BOP.||Background|
& Rule Engine
|Engine that executes (“interprets”) Business Process models (from BPMN Process Designer), as well as a component that monitors and manages business processes, with focus on exposure and analysis of business process-related measurements, via both standard-available and custom dashboards (the latter by integration with BAM Dashboard). The Rule engine executes business rules and decision tables, from Rules and Decisions component. These engines are closely integrated with Inbox framework, for work distribution purpose.||Background|
|Engine that executes (“interprets”) Case models (from CMMN Designer), as well as a component that monitors and manages cases. This engine is closely integrated with Inbox framework, for work distribution purpose. As Case Management has particular focus on supporting knowledge workers in their human-driven processes, Inbox framework has been extended with particular support for “Case workers”, providing them with overview of Cases as well as overview of work within a Case. Specific “Case worker” needs has led to advancement of Inbox framework in general.||Background|
|Model-driven framework to support “master data stewardship”, with focus on “data life cycle management”, including support for “data quality management”. Support for data exchange (“Extract, Transform, Load”) is part of this framework.||Background|
|Integrated set of frameworks that together provides the distributed and SOA-based environment, that used to be called “Enterprise Service Bus” in the recent past, but that later on was called “SOA Grid”. It
has been optimized to the extreme, with focus on scalability, failover, guaranteed delivery, security, etc. aspects. SOA Models can be considered its design-time counterpart.
|Framework or “container” that provides complete support for hosting, exposing and executing (“interpreting”) Entities (from Entity Designer). It can be considered a model-driven, SOA-based, distributed, multi-tenant-enabled and standards-compliant “application server”.||Foreground – ready to use|