Data Templates are used to transfer the customer data into OpsVeda. They paint the picture of the customer’s supply chain using the data points and terminology that the customer is accustomed to. It is vital that we receive good data, since: good data in = meaningful intelligence out.

It is vital that we identify the OpsVeda champion early in the process as this person will be the liaison between the customer and OpsVeda. This champion is a person from the customer’s organization and will likely be the “super user” of the OpsVeda system post implementation. This champion knows the business from start to finish and has a good relationship with several key departments within the customer organization. They are familiar with, and accustomed to, reporting fields and KPIs of the customer so that once the system is launched with the customer data, they can start refining it to derive greater value for the customer. They will also be the key JUNI configurator.

OpsVeda users are anyone in the company that need information for either transactions (customer service) or reporting (business analyst). Limited users are those who need high level reporting that can be delivered directly to their respective email inbox using alerts and the Customized Reports feature of OpsVeda. Limited users do not have the ability to directly log into the OpsVeda web application, but may access limited functionality via the mobile app.

JUNI is where the magic happens. JUNI is an AI assistant that enables a customer user to create and customize storyboards. It allows the customer to paint their own picture with the data that they are putting into OpsVeda.

Trial instances are similar to production instances except that there are limits on how much data one can upload or how many monitoring business objects can be seen in the OpsVeda dashboard.

We suggest having input from all areas of the customer’s business depending on how they intend to use OpsVeda to provide comprehensive end-to-end visibility. We recommend identifying someone who understands the business requirements in terms of what is required from the OpsVeda system. Often this person is the one who creates the flow from the customer to OpsVeda. In most cases this will be someone from IT, or a business analyst. We also highly recommend having a champion who remains active throughout implementation.

Data mapping is a representation of data from the source to OpsVeda. It entails using the data provided by the customer and mapping it in a field-specific manner within OpsVeda. On the other hand, process mapping is based on business requirements. It defines the actions that must be taken within the OpsVeda system. In other words, it defines what should happen within OpsVeda once a user executes an action.

The customer champion(s) will need to be available for daily sessions with the OpsVeda team during the course of the implementation. They will also need to engage the key business users (recommended cadence is weekly, at a minimum) to ensure that the path is clear and usable for all intended users. While this is a commitment upfront, the fully deployed solution will provide a streamlined process that will reduce time spent on reporting and internal communication at all levels.

We use the “train the trainer” method. OpsVeda will provide end-user training for champions and “super users” as well as provide reference documentation to be used by all users. OpsVeda will also be training the champion(s) to be OpsVeda admin users and JUNI configurators. The champion will then be able to use the power of JUNI, set up new users and perform the necessary tasks pertaining to updating backend configuration, as required.