Workflow

Analytics User Typical Workflow

The analytics user uses historical data to design and test analytics that identify important events in asset performance data. Many queries are open-ended and require significant, manual data import. Working closely with analysts, they also collaborate with engineering and product design teams to develop analytics. They also develop analytics for use by plant operations in detecting anomalies.

The following diagram represents a typical workflow using Application Analytics. The table following the diagram lists the functional tasks.

Figure: Analytic User Typical Work flow


Table 1. Functional Tasks
Task SetDescription
Manage Asset Filters (applicability)
  • Add, modify and delete asset filters for defining the asset applicability for analytic.
Manage Analytic Templates
  • Add, modify, and delete analytic templates in the analytic catalog.
  • Configure analytic templates.
    • Add supporting documentation.
    • Define the analytic inputs, constants and outputs.
    • Add an output event that matches an existing alert template.
Manage Orchestrations
  • Add, modify, and delete analytic orchestrations and data flows using existing analytic templates.
Manage Deployments
  • Add a deployment configuration.
  • Select assets for deployment.
  • Maps inputs and outputs definitions with tags and attributes for deployment.
  • Modify constants values if needed.
  • Add iterations to analytic orchestration steps.
Schedule Deployments
  • Add data interval (sampling) and execution time range.
  • Schedule deployments to run once, on demand .
  • Schedule deployments to run automatically on a specified date/time.
  • Review the deployment.
Monitor DeploymentsView the execution status of the deployments in the Deployments page.

For more information, refer to About Analytics Monitoring