MechSignal IN DEV
Pilot conversations open

Discuss a pilot

We’re looking for a small number of manufacturers, plant maintenance teams and industrial service providers to help build and validate MechSignal on real equipment.

What a pilot involves

A scoped, measured trial on a few machines

  1. Fit assessment

    A conversation about your equipment, existing data sources and maintenance process. If it isn’t a good fit, we’ll say so.

  2. Scope & data connection

    Agree a small set of assets, success criteria and data-handling terms. Connect data with your IT/OT teams.

  3. Baseline & review

    Build baselines, raise flags, and have technicians record what they find on inspection.

  4. Joint evaluation

    Review flags against inspection outcomes together — useful flags, false alarms and misses — and decide next steps.

A good fit usually means

  • Rotating or process equipment that matters to production
  • Existing sensor data, or willingness to add sensors to a few machines
  • A maintenance contact who can review flags and record findings
  • Interest in shaping an early product, with realistic expectations
Pilot terms, timeline and any costs are [to be confirmed per pilot]. MechSignal is in development and will not replace your existing safety systems or inspection schedule.

Tell us about your equipment

Fields marked are required.

Equipment types of interest

Helps us judge fit early. Choose the closest option.

Thanks — your enquiry is ready to send. Online submission isn’t connected yet, so nothing has been sent. Open it as an email to send it to pilots@mechsignal.example.

Privacy: [Link to privacy notice]. This form does not store or transmit data; it only drafts an email in your mail client.