Skip to content
Indussbz
DATAData and security

Your maintenance record stays yours.

Equipment data describes how your plant actually runs, which makes it commercially sensitive. This page sets out exactly what the platform uses, how scores are produced, who can see what, and where the platform's authority stops.

Data positionAt a glance
  • OwnershipYours, at all times
  • ExportFull CSV, on demand
  • EncryptionIn transit and at rest
  • AccessRole based, per site
  • Shared with other customersNever
  • Sold or brokeredNever

What data is used

Nothing beyond what maintenance needs.

The platform asks for equipment and maintenance information. It does not require production recipes, financial records, customer data or personnel files.

DS-01

Asset register

Machine tag, type, line, criticality, install date, nameplate details.

DS-02

Runtime and meter data

Hour meters, shift runtime entries, temperature, pressure and current readings taken on rounds.

DS-03

Symptom reports

Operator and technician observations: noise, heat, vibration, leaks, intermittent faults.

DS-04

Maintenance history

Work orders, parts consumed, time to repair, findings and sign-offs.

DS-05

Spare parts data

SKUs, descriptions, bin locations, counts, minimum levels, consumption and receipts.

DS-06

Vendor records

Supplier names, part coverage, agreed lead times, your internal owner for the relationship.

How scores are derived

A score you can take apart.

A health score is only credible if someone can see what produced it. Every score opens into the inputs behind it.

  1. 01

    Establish the asset baseline

    The engine learns each machine's normal operating pattern from its own history rather than comparing it to a generic class average.

  2. 02

    Measure current deviation

    New runtime, readings and reports are compared against that baseline, weighted by how recent and how complete they are.

  3. 03

    Match against patterns

    Deviations are tested against known failure signatures such as bearing wear, filter restriction or seal degradation.

  4. 04

    State the confidence

    The score and any alert carry a confidence level reflecting pattern strength and the depth of history available. Thin data produces a lower, visible confidence.

Score explanation - CD-04Why 38
Vibration reports, last 6 shifts-24
Motor current vs baseline-18
Repair interval shortening-12
Runtime since bearing change-8
PM compliance, on plan+0
Score from 10038

Sample layout showing how a score breaks down. Every score in your workspace opens the same way, with the contributing inputs and their weight visible to anyone who can see the asset.

Practices

Stated plainly, without the certification theatre.

The controls below describe how the platform is built and operated. Where a formal certification is required for your procurement process, ask and we will tell you exactly what does and does not exist today.

Encryption in transit

All traffic between browsers, devices and the platform runs over TLS. Plain HTTP connections are not served.

Encryption at rest

Stored maintenance records, parts data and uploaded files are encrypted on disk.

Role-based access

Permissions by role and, on multi-site plans, by facility. A technician on one line does not see another plant's vendor terms.

Account controls

Individual named accounts, enforced password strength and session expiry. Shared logins are discouraged by design.

Change history

Edits to asset records, stock counts, minimum levels and approvals are recorded with the user and timestamp.

Tenant separation

Each company's data is logically isolated. No customer's maintenance data is visible to another, in any view or report.

Export on demand

Any view exports to CSV, including full event history. Leaving does not mean losing your records.

Backups

Regular automated backups with restore testing, so a lost record is recoverable rather than theoretical.

No data brokerage

Your data is not sold, licensed, brokered or used to build a product for anyone else.

The boundary

Indussbz flags and suggests. Your team decides.

This is a deliberate design limit, not a disclaimer. Software that overrides a technician standing in front of a machine is dangerous, and software that buys on your behalf is a liability.

  • Maintenance decisions rest with your maintenance team
  • Purchasing decisions rest with your approvers
  • Safety isolations and statutory inspections stay under your procedures
  • An alert is evidence to act on, not an instruction to follow

Ownership

Portable by default.

  • You own your asset register, maintenance history, stock records and vendor list
  • Export is available throughout the subscription, not only at the end of it
  • Exports include history and audit entries, not just current values
  • On cancellation, data remains exportable for the wind-down window set out in the Terms of Service

Downtime risk ticket

Put a number on the next breakdown.

96
M1
91
M2
79
M3
93
M4
94
M5
89
M6
Ticket: EstimateType: Unplanned downtimeStatus: Draft
40assets
5500
24h / month
2200
25,000INR
2,0005,00,000

This is an illustrative estimate based on typical patterns, not a live analysis of your equipment. It assumes a 20-35% reduction in unplanned downtime. Connect your maintenance logs for your actual numbers.

Hours you could win back

58-101h / yr

Downtime today
288 h / yr
Per machine
7.2 h / yr
Value at stake
INR 14.5 L-25.3 L