Use case for service operations
In this section we will be using a fictitious scenario to go through a complete configuration and execution of a model in Service Operations. The goal is to revisit all concepts and explanations given throughout the application user manual with a concrete example, thus illustrating all main concepts of the application and the way it would be used within this context.
An e-commerce site needs to monitor and manage its operation from three different perspectives: operational status, business performance and end-user experience. The goal is to create a comprehensive, multi-angled, detailed tool that touches upon those fundamental pillars while providing a top-down approach that satisfies summarized status reporting as well as very detailed analysis of issues and their root cause, hence helping operations and business organizations understand whether or not their individual goals are being met.
For the sake of simplicity, we will skip all aspects related to the data sources ingestion, using exclusively Devo’s demo.ecommerce.data data structure given the fact it is universally available in all domains.
Before starting, please review this list of pre-requisites:
You have credentials to access the Devo domain you want the model to run on.
Service Operations has been instantiated in that domain and is accessible by your user / role.
Should you require additional indications on how to install Service Operations in a domain, please refer to the installation chapter of this documentation.