Powered by

SolutionRole in this use case
SpectraCollects telemetry from mobile and fixed equipment (engine, vibration, location) and environmental sensors (gas, dust, temperature).
ServyManages maintenance, breakdown and safety-related work orders, technicians, vendors and escalations.
OpsFormsPre-start inspections, safety checks, maintenance tasks and incident report checklists tied to assets and tickets.
OpsBotGuides crews with SOPs, emergency procedures and investigation playbooks based on historical cases.

How it works

Connect equipment & sensors

Mining equipment (trucks, shovels, conveyors, crushers, fans, pumps) and environmental sensors connected to Spectra.

Monitor health & environment

Spectra watches health indicators (temperature, pressure, vibration, hours), utilization and safety parameters (gas levels, dust, stability) continuously.

Detect failure risk & safety issues

Rules detect conditions indicating failure risk or unsafe situations; some conditions auto-create Servy maintenance or safety tickets.

Pre-start & periodic checks

Crews run pre-start and periodic checks using OpsForms — linked to assets and tickets, including photos and readings.

OpsBot for incidents

During incidents or complex problems, teams use OpsBot to retrieve SOPs, emergency procedures and lessons from similar past events.

Safety & performance dashboards

Supervisors see equipment health, utilization, safety incidents, response times and compliance to inspections in one view.

Problem → Solution

❌  Today✅  With Starlly
Health and safety issues sometimes noticed late due to manual checks and siloed systems.Spectra continuously monitors equipment and environment, highlighting early warning signs automatically.
Maintenance and safety actions tracked in paper logs or local systems.Servy centralizes all work orders and safety tasks with full traceability and escalation.
Pre-start checks and inspections vary by person or crew.OpsForms standardizes checklists and ensures completion with required readings and signatures.
Knowledge of how to respond to complex situations is uneven across crews.OpsBot makes procedures and experience consistently available to all crews instantly.

Benefits

Reduced safety incidents

Reduce risk of catastrophic failures and safety incidents through early detection and guided response.

Better equipment availability

Proactive maintenance improves equipment availability and reduces unplanned downtime in operations.

Stronger safety compliance

Enforced inspection requirements and digital records ensure compliance with safety regulations.

Faster incident response

More consistent handling of incidents through OpsBot-guided procedures and Servy task tracking.

Maintenance cost visibility

Clearer view of where maintenance budget and time are going across equipment and sites.

Consistent crew knowledge

OpsBot makes expert knowledge accessible to all crew members regardless of experience level.

What helped when

Step in the flowWhat happensSolution(s)
1. Monitor equipmentEquipment and environment data flows to central view continuously.Spectra
2. Detect conditionRules highlight unsafe or high-risk conditions for operator attention.Spectra
3. Create workMaintenance or safety tickets auto-created with context and priority.Spectra Servy
4. Execute workCrews use OpsForms for pre-start checks, inspections and corrective actions.OpsForms Servy
5. Guide responseOpsBot provides SOPs, emergency procedures and investigation guidance.OpsBot
6. Review & improveIncidents and patterns analyzed for continuous safety and performance improvement.Spectra Servy OpsForms

Frequently asked

Yes; data can buffer locally and sync when connectivity is available. Servy workflows also continue offline and sync on reconnect.
Not necessarily; we integrate where possible and add missing workflows and visibility on top of existing systems.
No; it can start small with one site and a handful of assets, then scale as value is proven.
OpsBot is trained on your manuals, SOPs and resolved case history — it improves as more incidents are captured and closed in Servy.

Next steps & pilot

How we run a pilot

  • Start with 1–2 sites or lines
  • Map assets & workflows with your team
  • Configure frameworks for your scope
  • Run for 4–8 weeks, measure & scale

Pricing approach

  • Platform fee per asset / site / user
  • One-time setup (discovery, config, training)
  • Optional managed services

Discuss the Mining Operations use case