There is no useful price without scope. A document-based review of one line and a multi-site assessment with field observations involve different effort. Vizory does not publish a validated price range here: generic amounts would imply false precision. For comparable proposals, define assets, decisions to support, available information and deliverable detail.
Factors that change the effort
- Asset count and diversity: a homogeneous family may allow sampling, unlike very different processes.
- Site complexity: redundancy, production dependencies, safety requirements and access constraints.
- Data quality: available extracts, comparable history, hierarchy and work-order quality.
- Required participation: interviews, trade validation, observations and owner availability.
- Requested deliverable: diagnosis alone, detailed technical rationale or implementation support.
A sample scope to include in a request
Teaching example, not a standard offer: assess maintenance management on one line, review its asset hierarchy, analyze representative history, observe a sample of interventions and meet operations, maintenance and procurement. The objective would be to prioritize gaps affecting availability and work readiness. The scope would explicitly exclude certification, statutory inspection and detailed modification design.
Deliverables to request
| Deliverable | Useful content |
|---|---|
| Baseline | Scope, method, reviewed data, limitations and traceable observations. |
| Maturity assessment | Defined criteria and evidence; distinguish perception from observed practice. |
| Prioritized findings | Consequence, urgency, effort, dependencies and confidence level. |
| Roadmap | Owner, resources, proposed timing and validation measures. |
A maturity score alone is insufficient. Ask for the observations explaining it and sampling limitations. Proposed savings must state assumptions and remain estimates until realized. Recommendations should distinguish immediate actions, projects requiring technical study and issues needing management decisions.
Compare proposals on the same basis
Check what is included: preparation, field time, travel, validation workshops and follow-up. Identify information to supply and your team’s required time. Ask how disagreements will be handled and who will approve the report. A cheaper proposal may simply provide less depth; a costlier one is not automatically better if its recommendations cannot be executed.
Technical assessment and conformity: do not confuse them
ISO 55001 defines asset-management system requirements. A reliability assessment may draw on them but does not automatically constitute a conformity audit or certification. Specify the references used and required expertise. The expected outcome is a clearer decision on next actions, not conformity claimed without appropriate assessment.