Carlos Coutinho Zheng Jiang

The C2NET Collaboration Tools is responsible for the C2NET support on collaboration for the supply chain planning processes.

This Major C2NET module is subdivided in lower-level modules:

  • Monitoring Plan Execution - AA aims at supporting the monitoring step. The core of this component is the “models manager” sub-component which maintains the views of the situation. It receives data and event flows coming from the “Data Storage” and apply business rules to generate high level situational information (risk appearance, risk occurs, breakdown, ...). These informations gathered with informations of the knowledge base enables the interpretation engine to build the models of the situation. The component also provides added value services: detection service, adaptation service, and assessment service that are required by the analysis of the situation.
  • Monitoring Plan Execution - MD aims at supporting the monitoring step. The core of this component is the “models manager” sub-component which maintains the views of the situation. It receives data and event flows coming from the “Data Storage” and apply business rules to generate high level situational information (risk appearance, risk occurs, breakdown, ...). These informations gathered with informations of the knowledge base enables the interpretation engine to build the models of the situation. The component also provides added value services: detection service, adaptation service, and assessment service that are required by the analysis of the situation.
  • Orchestrating Planning Process aims at supporting the design process. The core of this component is an orchestration engine that is in charge of orchestrating a process that will invoke C2NET collaboration services either provided by the UCP open PaaS (email, chat, etc.) or OPT (call for optimization tasks), but also external services (visio-conference for example), or user interactions (plan viewing/edition/validation). The component also integrates a “negotiation process modeller” that generates the BPN2 file that can be processed by the orchestration engine.

Additionally, this page includes a Tickets entry to handle specific issues regarding this module as a whole (which may include management, integration, new features, etc.).

Module Development:

Responsible: Armines