Skip to content
MLNetworks
Talk to an Expert

Professional Services

Your first workflow, set up with you.

Professional Services is the MLNetworks team that scopes your first workflows, connects your data and trains your people, from the first sites to rollout.

MLNetworks specialists scope one workflow with your NOC and field teams, hook up the data feeds it needs, configure it and train the people who will use it.

Talk to an Expert

First workflow

Site power incidents

Ridgeview RDG-0417

Configure

How an engagement runs

  1. Discover

    Discovery and workflow scoping

  2. Connect

    Data and system integration

  3. 3

    Configure

    Configuration and access setup

  4. 4

    Onboard

    Team onboarding and training

  5. 5

    Expand

    Ongoing support and expansion

Scope and timing agreed for each deployment

From scoping to a workflow in use

  1. 01

    Scope the first workflow

    We start with one question your team needs answered, the data behind it and who is involved. The scope is written down and agreed before work starts.

    Scoping sheet

    Site power incidents

    Ridgeview RDG-0417

    Draft for agreement

    The question to answer

    Which power events at a site need action, and what should the team do next?

    Data sources, by category

    • Alarm and fault systems
    • Site controllers and telemetry
    • Site and asset records
    • Work orders and tickets

    Who is involved

    • Control room operatorReviews incidents
    • Field supervisorApproves site work
    • Site data ownerConfirms records
    • AdministratorManages access

    Out of scope is written down too.

  2. 02

    Hook up the data it needs

    Each source is agreed by category, then checked with your team. We call a source supported only once it is validated.

    Integration checklist

    Site power incidents

    Ridgeview RDG-0417

    Source categoryStatus
    • Alarm and fault systemsValidated
    • Site controllers and telemetryIn validation
    • Site and asset recordsAgreed
    • Work orders and ticketsAgreed

    Status

    AgreedIn validationValidated

    Integration scope is defined for each deployment.

  3. 03

    Train the people who will use it

    Training follows the roles in your operation. Each role learns its own part of the workflow.

    Onboarding plan

    Site power incidents

    • Control room operator

      Planned

      Learns

      Reading an incident, its cause and evidence

    • Field supervisor

      Planned

      Learns

      Approving or rejecting a proposed action

    • Site data owner

      Planned

      Learns

      Keeping site records current

    • Administrator

      Planned

      Learns

      Roles, access and settings

    Sessions follow your roles and your shifts.

We start from the systems you already run

Integration scope is defined for each deployment, and each source is validated with your team before it is named as supported.

  • Alarm and fault systems
  • Site controllers and telemetry
  • Site and asset records
  • Work orders and tickets

Set up for your shifts, ready for the next workflow

  • Access by role

    ViewChangeApprove
    • Control room operator
    • Field supervisor
    • Administrator

    Example only. Roles are set for each deployment.

    Configuration and access, by role

    We configure the workflow to your operation and set who can view, change and approve, role by role.

  • Workflows for this operation

    • Site power incidentsIn use
    • Next workflowBeing scoped
    • Later workflowNot started

    Support after the first workflow

    Once the first workflow is in use, we support it and plan the next with you.

The first workflow is the starting point

Get one workflow running, then add the next on the same sites and assets.

Network Monitoring & Incident Response

Site power incidents

Ridgeview RDG-0417

Workflow state

  1. Scoped

    Agreed with your team

  2. Connected

    Sources validated

  3. In use

    Teams onboarded

Next workflow

How we work with your team

  • Scope before work

    What is in and out of scope is written down and agreed before any feed is connected.

  • Sources named when validated

    A source is listed as supported only after we have checked it with your team.

  • Your team stays in charge

    Your people approve actions and own their systems. We set up and support. We do not run your operation.

FAQ

Questions from operators

What does an engagement include?

Five areas of work: discovery and workflow scoping, data and system integration, configuration and access setup, team onboarding and training, and ongoing support and expansion. The mix depends on your deployment.

How long does it take and what does it cost?

Scope and timing are agreed for each deployment, after we understand your workflow and your systems. We do not quote either before that.

Do we have to start with every workflow?

No. We suggest one workflow first, then others once the first is in use.

Which of our systems can you connect to?

That is defined for each deployment. We validate each source with your team before we name it as supported.

Who owns the decisions and the data afterwards?

Your team. People approve proposed actions, and your own systems stay the record for their data. The details are written into the scope.

Professional Services

Which workflow would you like to start with?

Bring a real case. An MLNetworks expert will walk through it with you.

Talk to an Expert

More of the platform

Every part uses the same sites and assets. Start where the need is greatest and add the next when you are ready.