Definition of the "Proof Of Concept", better known by its Acronym "POC".
The process of selecting a software publisher is a key step in the choice of implementing an IT tool. Between the initial need, the presentation of ready-to-use tools, demonstrations and production start-up, the "Proof Of Concept" is a necessary step for the comparison and the choice of the tool that best meets the requirements and integrates best into the IS.
A POC, should be used as a step in the implementation project. It allows the evaluation committee to focus on the real understanding of the capabilities of the tool and the editor. In the purchasing cycle, the POC stage allows the company to focus on key topics, create the conditions for better adoption by the user community, initiate change, implement best practices and lay the foundations for successful deployment.
The unfolding of a POC
It all starts with the framing of the POC.
This step allows to frame the perimeter of the POC in order to be able to test the solution in the best conditions. The evaluation committee will be able to give the key and/or prohibitive subjects for the choice of the solution. COSERVIT will propose scenarios adapted to the final context. Once the framing has been carried out, the POC will enable ServiceNav to be positioned in front of all the situations set and mandatory for validation.
Generally, ServiceNav POCs are deployed on a reduced perimeter of the IS in production. As ServiceNav is an "Agentless" supervision solution, it listens to and reads PLCs and makes hardware and software feedbacks. It has no impact on normal operation and can therefore analyse real data in order to be able to position itself in production operating situations.
The Kick-Off
At the end of this framing, the POC follows a process of Project and so starts with a kick-off.
The role of the kick-off is to identify the consultant in charge of the POC, and to read/adjust the schedule proposed by the latter. For the consultant, it is the occasion to present the technical prerequisites (dimensioning of the VMs, Prerequisite on equipment to be supervised, ...) and to present its schedule, according to the technical and organizational constraints.
Deployment
Following the kickoff and the supply of the VM(s) by the customer, the installation of the ServiceNav Box is carried out. Its role will be to collect data on the supervised equipment and services.
At the end of this installation, a census of the park to be supervised (defined during the framing) is carried out by the client project manager and the consultant.
The consultant introduces here good practices, which will be profitable in the long term:
- To fill in the supervisory accounts at the highest possible level
- Standardize naming
- Define labels on equipment if relevant
- Only put in supervision what is necessary
At this stage, the supervision tool is populated, it becomes possible to refine the controls (thresholds, arguments) and to define notification policies.
The challenge here is to reduce "noise" and false positives:
- Notify only major alerts, and on appropriate contacts
- Define appropriate thresholds
Once this work is done, an analysis of user services, weather and reporting needs (Reports and Dashboards) should be carried out.
The aim here is to identify groupings of equipment and services, in order to constitute user services, which will allow a high level of supervision that can be shared with end users via the weather services.
Once this architecture is in place, supervision is operational. It remains to identify with the operational users and managers the reporting needs, and the monitoring mode (TV screen, PC, PDF mail reports) in order to define adapted dashboards and reports.
Validation of the POC
Once the POC has been implemented, all the situations defined during framing will have been tested. Their results will therefore guide the validation or rejection of the solution.
How long do I need to book?
The ServiceNav product is optimised and our consultants are trained to ensure that the deployment of your supervision is as efficient and rapid as possible, while remaining of the highest quality. It only takes a few days to put a fleet into supervision and create the first dashboards and user services, when the prerequisites are met.
Once the solution is deployed, it is also easy to bring it to life, thanks to the numerous mass processing functionalities, the model-based approach (services and equipment), and an efficient and responsive support platform.
Within the framework of a POC, the time of availability of our Service Nav tool is generally for a month.
