The purpose of this deliverable is to give tools for verifying the implementation of C2NET pilots and the platform itself. C2NET has four pilots:
1. Automotive will automatically generate optimised plans and carry out collaborative production planning and synchronised replenishment planning of car components.
2. Dermo-cosmetics will facilitate the collaboration for an agile production and distribution of dermo-cosmetics.
3. Metalworking SME’s network will enhance collaborative purchases and transportation
4. OEM will focus on the interactions and transactions between the manufacturer of hydraulic and lubrication products and the supply chain interactions necessary to provide ordered products to customers.
Each pilot generated three to four validation scenarios and acceptance criteria for those. Validation scenarios are described with storyboards and step descriptions. Validation scenarios of each pilot are listed below:
Pilot 1, AUTOMOTIVE
- Validation Optimisation of the Injection Schedule
- Negotiation of NOVATEC Delivery Plan with FAURECIA
- Optimisation of NOVATEC Injection Master Plan
- Optimisation of NOVATEC Procurement Plan
Pilot 2, DERMO-COSMETICS
- Continuous Replenishment based on DIM and LOFP processes
- Agile Fulfilment Planning based on LDRP, WDRP and WOFP processes
- Dynamic Forecast and Replenishment based on DIM and DF processes
- Dynamic and Collaborative Shortage Prevention and Management based on LDRP, WDRP, MRP, MPS and WOFP
Pilot 3, METALWORKING SMEs
- Creation of a Collaborative Raw Materials Purchase
- Creation of a Collaborative Transportation Plan
- Creation of Machinery Scheduling Plans
- Management of Non-conformity Scheduling Plans
Pilot 4, OEM
- Inquiry, Quotation and Order Reception Planning
- Management of Production Planning
- Optimisation of Info Accessibility in Material Purchasing Process
Validation scenarios were mapped with the functional requirements (presented in deliverable D1.2 Detailed functional requirements for C2NET Platform) to analyse, if the identified validation scenarios cover the functional requirement classes adequately. Each validation scenario also provided their acceptance criteria to describe how the successful C2NET implementation will perform.
There was a tentative to use Manufacturing Service Tool Box (MSTB) Wiesner et. al. (2014), a result of the European project MSEE (Manufacturing SErvice Ecosystem, No 284860, FP7 FoF-ICT-2011.7.3), for describing the validation scenarios. Some partial models have been established for Pilots 1, 2 and 4. The modelling work will be pursued in WP7 (Pilots development) due to the limited time at this phase. In addition to the functional validation of identified scenarios, the feasibility of the C2NET platform was discussed and analysed. This feasibility analysis will be performed with a user questionnaire and Key Performance Indicators (KPI). The questionnaire will take place after the C2NET implementation among all the users of any C2NET pilot. The questionnaire will have closed questions with the Likert scale1, as well as open ones to find out potential improvements or new C2NET features to be implemented later.
Most of the business impacts already presented in the proposal were discovered to be unfeasible as we cannot prove that any decrease in stock level is dependent (only) on the C2NET implementation. Stock level varies during a month and between months. Also the time period required to measure credible stock levels does not fit in the timeframe of this project. The original business impacts of each pilot were taken as fundamental basis when measurable KPIs were created. For each KPI the current value (AS IS) will be measured before the implementation and the referring value after the implementation. The measurable KPIs are presented in the tables from Table 9 to Table 15 starting at page 57.
In the descriptions of the validation scenarios there were also expectations and requirements for interfaces, visualisation, access and C2NET configuration features. The identified validation scenarios (15) have over thirty separate and unique plan types. The configuration of a new plan (type) has to be easy for the Network Manager. The plans will be studied further in Work Package 4, which will specify and implement the C2NET Optimiser. All the findings will be discussed before the final architecture is fixed.