At the heart of the envisaged FIspace platform reside the Business-to-Business Core Modules. The B2B Core ensures that all information and status updates are provided to each involved stakeholder in real-time. The B2B core allows for the creation, management, execution, and monitoring of collaborative business processes in the FIspace platform. The B2B Core consists of two interrelated components:
- A Collaboration Engine that captures, in form of so-called Business Entities, the information that are to be exchanged among collaborating stakeholders along with status and control of the a collaborative business processes. The BCM component is responsible to orchestrate the different processes from different stakeholders and assure the correct sequence of the tasks execution;
- An Event Processing Engine that detects and analyses events coming from activi-ties in the collaborative processes or from IoT devices. The Event Processing Module (EPM) component monitors events and detect situations of interest, i.e., situa-tions that require appropriate reactions;
- Authoring tools: Both engines will be accompanied by respective authoring tools that allow defining business entities resp. event rules.
The BCM component is responsible to orchestrate the different processes from different stakeholders and assure the correct sequence of the tasks execution. The BCM is based on the entity-centric approach (for more details, please refer to the outcomes of the ACSI project. This approach relies on the notion of entities (aka, as business entities, artefacts, or dynamic artefacts, or business collaboration objects). These provide a holistic marriage of data and process, both treated as first-class citizens, as the basic building block for modelling, specifying, and implementing services and business processes. A (business) entity is a key conceptual concept that evolves as it moves through a business (or other) process. An entity type includes both a data schema and a lifecycle schema which are tightly linked. The data schema provides an end-to-end conceptual view of the key data for this entity type. The lifecycle schema of an entity type specifies the different ways that an entity instance might evolve as it moves through the overall process. In FIspace we will use the GSM (Guards, Stages, and Milestones) model to specify the lifecycle schema of the business entities.
The Event Processing Module (EPM) component monitors events and detect situations of interest, i.e. situations that require appropriate reactions. The events sources (aka events producers) can be the actual execution of the collaboration (i.e., the BCM), ex-ternal systems, or sensors. The EPM processes these events and by applying pattern matching derives situations of interest. Examples of situations of interest can be: Missing documentation at a certain point in time, a sensor reading outside a permitted range, a delay in a delivery. In general, we can distinct between situations that result from the actual execution of the process or collaboration and situations that result from external events (i.e., events coming from external systems or sensors). The EPM in FIspace supports two types of situation detection capabilities: reactive and proactive. Reactive rules analyse past events and derive situations by applying pattern matching over a single or a set of events over time. Proactive rules, on the other hand, relate to situations that are likely to happen in the (near) future. In general, we refer to proactive event-driven computing as the ability to mitigate or eliminate undesired states, or capitalize on predicted opportunities—in advance. This is accomplished through the online forecasting of future events, the analysis of events coming from many sources, and the application of online decision-making processes.
These two modules are connected each to the other and to the other FIspace components of the platform via the Component Service Bus (CSB).
You can find the FIspace B2B business architect manual here
You can find the FIspace B2B technical manual here.