Plant maintenance software: how to choose a system that brings order to work orders, assets and costs

Plant maintenance software helps industrial organisations plan, execute, document and analyse maintenance work. It typically covers work orders, preventive maintenance schedules, an asset registry, spare parts inventory, mobile access, reporting and maintenance KPIs.

In practice, software of this class is most often referred to as a Computerized Maintenance Management System (CMMS). In larger organisations it may form part of a broader Enterprise Asset Management (EAM) system, and in data-driven environments it works alongside an Asset Performance Management (APM) layer.

What is plant maintenance software?

Plant maintenance software is a system that supports the daily work of a maintenance function: from the moment a problem is reported, through the work order and the schedule, to spare parts, costs, reports and the asset’s service history.

Its primary purpose is to bring order to information that, in many plants, is scattered across spreadsheets, paper forms, email, technicians’ personal knowledge, the ERP system, technical documentation and failure records.

A typical system of this class allows an organisation to:

• create, assign and close work orders;
• plan preventive maintenance (PM);
• maintain an asset registry and equipment hierarchy;
• manage spare parts and MRO inventory;
• record labour hours, parts used and failure codes;
• handle requests raised by production;
• support technicians in the field through a mobile app;
• report maintenance KPIs such as MTTR, MTBF, PM compliance, backlog and cost per asset;
• integrate data with ERP, SCADA, DCS, IoT and an industrial data platform.

PM stands for preventive maintenance: planned inspections, checks and servicing carried out before a failure occurs. In this model the system can generate work orders automatically based on a calendar, running hours, distance travelled, a production cycle or another operating meter.

CMMS, EAM and APM – how they differ

CMMS, EAM and APM are related software categories, but they differ in scope. A CMMS brings order to operational maintenance, EAM covers the full asset life cycle, and APM focuses on asset performance, reliability and analytics.

Dimension	CMMS	EAM	APM
Full name	Computerized Maintenance Management System	Enterprise Asset Management	Asset Performance Management
Primary purpose	Day-to-day maintenance operations	Managing the asset across its full life cycle	Optimising asset reliability and performance
Typical features	Work orders, PM, parts inventory, basic reporting	CMMS plus capital planning, depreciation, procurement, regulatory compliance	Condition monitoring, predictive analytics, risk-based maintenance
Typical users	Technicians, planners, maintenance managers	Maintenance, finance, procurement, compliance, asset management	Reliability engineers, analysts, data teams
Data scope	Work order history, failures, parts, labour hours	CMMS data plus financial, regulatory and life-cycle data	Sensor data, failure patterns, analytical models
Deployment model	Standalone system or module	Enterprise system, often tied to ERP	Analytical layer above CMMS/EAM and IoT data
Relationship	The operational layer	An extension of CMMS across the asset life cycle	The analytical and optimisation layer

In practice the boundaries between these categories are fluid. Some CMMS products include EAM elements, and some EAM systems include CMMS functionality. APM, in turn, rarely replaces a CMMS – it draws on CMMS data alongside process, measurement and diagnostic data.

For an industrial plant, therefore, the key question is not “which acronym is best” but: how much maintenance and asset management scope do we actually need?

Who uses plant maintenance software?

Plant maintenance software serves several user groups: technicians, planners, maintenance managers, production, the storeroom, procurement, finance, reliability engineers and plant leadership.

Each group uses the system differently.

Role	Typical needs
Maintenance technician	Work order list, instructions, parts, documentation, photos, failure history
Planner	Schedules, resource availability, backlog, production windows
Maintenance manager	KPIs, costs, priorities, PM compliance, reactive work
Production	Reporting breakdowns, work status, planned shutdowns, priorities
Parts storeroom	Minimum and maximum levels, reservations, consumption, purchase orders
Procurement	Suppliers, purchase orders, parts costs, ERP integration
Reliability engineer	Failure history, MTTR, MTBF, cause codes, trend analysis
Plant director	Availability, costs, risk, the impact of maintenance on production

A well-chosen system should be more than an administrative tool for the maintenance department. It should connect technical work, planning, asset data and management information within a single process.

Core CMMS features

The core features of a CMMS are work order management, preventive maintenance scheduling, an asset registry, spare parts management, mobile access and KPI reporting.

Feature	Description	Key data or outcome
Work order management	Creating, assigning, executing and closing maintenance tasks	Labour hours, parts used, failure codes, timestamps
PM scheduling	Automatic triggering of preventive work by time, meter reading or event	PM work orders, PM compliance, inspection plan
Asset registry	Hierarchical database of equipment, systems and components	Nameplate data, history, documentation, criticality
MRO parts inventory	Managing parts used in maintenance, repair and operations	Minimum and maximum levels, stock turnover, part-to-asset links
Mobile access	Technicians working at the equipment on a phone or tablet	Photos, code scans, statuses, notes, signatures
Reporting and KPIs	Maintenance dashboards and operational analytics	MTTR, MTBF, backlog, cost, PM compliance
Integrations	Connections to ERP, SCADA, DCS, IoT and a data platform	Consistent data flow between systems

Each of these features should be assessed as more than a yes-or-no checkbox. What matters is whether it fits the way the plant works, whether it is genuinely usable for technicians, and whether it produces the data needed for decisions.

Work order management

Work order management is the process of creating, approving, planning, assigning, executing, closing and reviewing maintenance tasks.

The work order is the basic operational unit in a CMMS. It records what needs to be done, on which asset, at what priority, by whom, when, using which parts and with what result.

A typical work order life cycle looks as follows:

request → approval → planning → assignment → execution → closure → review

At a minimum, the system should record:

• the asset identifier;
• a description of the problem or task;
• the work order type;
• the priority;
• the person or team responsible;
• the date raised;
• the start and completion dates;
• labour time;
• parts used;
• the failure code;
• the cause;
• a description of the work performed;
• photos or attachments;
• the closure status.

Work orders feed many maintenance KPIs: mean time to repair, first-time fix rate, PM compliance, backlog age, cost per asset and the share of planned work. If work orders are closed without reliable data, KPI reporting quickly loses credibility.

Preventive maintenance scheduling

Preventive maintenance scheduling allows work orders to be created automatically on the basis of elapsed time, distance, running hours, a production cycle or an event.

The most common PM trigger types are:

Trigger type	Example	Typical application
Calendar-based	Every 30 days	Routine inspections, lubrication, safety checks
Meter-based	Every 500 running hours	Machines with variable utilisation
Event-based	After every production campaign	Batch lines, cyclical processes
Combined	Every 30 days or every 500 hours, whichever comes first	High-criticality assets

A PM schedule has to balance cost against risk. Work carried out too frequently drives cost, ties up the team and can introduce unnecessary intervention into a machine. Work carried out too rarely increases the risk of breakdown, deteriorating MTBF and reactive work.

A CMMS can generate work orders automatically as an inspection date approaches or when a meter reaches a defined value. Planning then no longer depends on individual memory or manually maintained spreadsheets.

Asset registry and equipment hierarchy

The asset registry is the central database of all equipment, installations, systems and components subject to maintenance.

A well-structured asset registry should follow a hierarchy, for example:

location → site → area → system → equipment → component

For each asset it is worth holding:

• the name and identifier;
• the manufacturer;
• the model;
• the serial number;
• the installation date;
• the location;
• technical documentation;
• instructions;
• drawings;
• spare parts;
• work history;
• failure history;
• the criticality classification;
• related procedures;
• related work orders.

The asset registry is a precondition for an effective CMMS. If equipment is not described correctly, work orders will not be assigned properly, the PM schedule will be incomplete, and failure history will not be analysable.

Asset criticality classification can support Reliability-Centered Maintenance (RCM). In that approach the maintenance strategy depends on the asset’s function, the consequences of failure and the risk to production, safety and cost.

Spare parts and MRO inventory management

Spare parts and MRO (maintenance, repair and operations) inventory management covers the parts, materials and consumables used in maintenance, repairs and day-to-day technical operations.

A CMMS can support:

• a parts catalogue;
• part-to-asset links;
• minimum and maximum stock levels;
• reorder points;
• reserving parts against a work order;
• barcode or QR code scanning;
• consumption history;
• suppliers;
• parts costs;
• integration with procurement and ERP.

Parts availability has a direct effect on mean time to repair (MTTR). If a technician knows the cause of a failure but does not have the required part, the equipment stays down and the outage lengthens.

At the same time, excessive spare parts stock means capital tied up on the shelf. The system should therefore help balance two objectives: availability of critical parts and control of inventory cost.

Mobile access for technicians

A mobile CMMS lets technicians handle work orders directly at the equipment – on a phone, a tablet or an industrial terminal.

Mobile access matters most where technicians work in the field, across large production halls, on multi-area sites, in distributed infrastructure or on assets that are difficult to reach.

Useful mobile capabilities include:

• a list of assigned work orders;
• changing work status;
• access to documentation;
• photos and attachments;
• barcode or QR code scanning;
• time recording;
• confirmation of parts used;
• checklists;
• signature capture;
• offline working with later synchronisation.

Mobile access also affects data quality. The technician no longer has to transcribe notes at the end of a shift, and information on time, parts and work performed reaches the system much closer to the moment the work was actually done.

Maintenance reporting and KPIs

Reporting in a CMMS should cover both current work order execution and the maintenance KPIs that show reliability, efficiency, compliance and cost.

KPIs typically reported in the system include:

• MTTR – mean time to repair;
• MTBF – mean time between failures;
• PM compliance;
• schedule compliance;
• backlog;
• the share of planned versus reactive work;
• wrench time;
• first-time fix rate;
• maintenance cost per asset;
• maintenance cost per unit of production;
• spare parts stock turnover.

Reporting on its own does not improve results. Value appears when KPIs have owners and targets and lead to action: a change of schedule, a reallocation of resources, additional diagnostics, root cause analysis, updated procedures or an investment in modernisation.

A CMMS provides operational data, but the full picture usually requires combining it with production, cost and measurement data. In that model an industrial data platform and production analytics can extend reporting well beyond work order history.

How to choose plant maintenance software

The choice between a CMMS and an EAM should follow from plant size, asset count, industry requirements, integration needs, how technicians work, the available budget, and the organisation’s maturity and data quality.

It is not worth starting with the question “which system is best”. The better question is: which system best fits our maintenance process, our asset structure and the way we make decisions?

Criterion	Questions to ask	Why it matters
Plant size and asset count	How many assets will be in the system? How many sites? How many users?	A small plant does not need a full EAM from day one, while a large multi-site organisation needs scalability
Industry and compliance	Do GMP, ISO 55001, audit requirements, electronic signatures or audit trails apply?	Regulated industries require change control, history and validation
Integrations	Should the system connect to ERP, SCADA, DCS, IoT, a data platform or finance systems?	Without integration, part of the data stays outside the process
Mobility	Do technicians work in the field? Is offline working required?	Mobile access determines adoption and the quality of execution data
Cost model	Does the organisation prefer operating or capital expenditure? Licensing per user, per asset or per module?	The pricing model drives total cost of ownership
Ease of use	What is the digital maturity of the user base? How much time can be given to training?	A difficult interface undermines adoption and data quality
Reporting and analytics	Which KPIs are required? Are dashboards, trends and management reports needed?	The system should support decisions, not just record keeping
Implementation support	Will the rollout be led by the vendor, a partner or an internal team?	This affects the timeline, the risk profile and the quality of start-up data
Security and access	Which roles, permissions and security policies are required?	The system reaches into infrastructure and process data, and incorrect permissions can allow unauthorised changes to schedules and asset records
Growth over time	Should the system serve one plant, or eventually several sites?	It is worth avoiding a solution that quickly becomes a constraint

A sound selection process should include requirements workshops, a list of use cases, a data assessment, vendor demonstrations, a pilot, an integration analysis and a realistic implementation plan.

Cloud or on-premise?

A CMMS can run as cloud software as a service (SaaS), on the plant’s own servers (on-premise) or in a hybrid arrangement.

There is no single best deployment model. The choice depends on security policy, IT requirements, budget, the number of sites, scaling needs and offline access requirements.

Dimension	Cloud SaaS	On-premise
Deployment model	Hosted by the vendor, accessed through a browser or app	Installed on the plant’s own servers
Cost model	Monthly or annual subscription, usually per user	Perpetual or project licence plus maintenance
Updates	Automatic, managed by the vendor	Manual, managed by IT
Customisation	Configuration within the platform	Scope for deeper customisation
Data control	Data in the vendor’s environment or a chosen cloud	Data in the plant’s own infrastructure
IT requirements	Lower on the customer side	Servers, backup, administration, IT resources
Scaling	Easier to add users and sites	Dependent on infrastructure
Offline access	Depends on the mobile app	Possible on the local network, but architecture-dependent
Typical fit	Small and mid-sized companies, multi-site organisations, fast rollouts	Large enterprises, environments with strict data control, isolated installations

For many plants the cloud model shortens time to value and reduces administrative overhead. On-premise deployment tends to be chosen where specific constraints apply around data, networks, cyber security or integration with plant systems.

What does a CMMS implementation look like?

A CMMS implementation covers needs assessment, vendor selection, data preparation, configuration, training, go-live and post-launch optimisation.

A typical project at a mid-sized plant may take three to six months. In a multi-site or enterprise environment it can take twelve to eighteen months, particularly where it involves ERP integration, migration of historical data and process standardisation.

Phase	Scope of work	Typical duration
1. Needs assessment	Scope, requirements, stakeholders, budget	2–4 weeks
2. Vendor evaluation	RFP, demonstrations, pilot, references	4–8 weeks
3. Data preparation	Asset hierarchy, PM schedules, parts catalogue, history migration	4–8 weeks
4. Configuration	Processes, roles, statuses, forms, notifications, permissions	2–4 weeks
5. Training	Administrators, planners, technicians, managers	2–4 weeks
6. Go-live	Phased launch, parallel running, user support	2–4 weeks
7. Optimisation	KPI review, user feedback, process adjustment, extended integrations	Ongoing

The biggest implementation risk usually lies not in the software but in data and processes. An incomplete asset hierarchy, out-of-date PM schedules, missing failure codes and inconsistent equipment naming can limit the value of the system from day one.

ROI from plant maintenance software

Return on investment in a CMMS should be assessed through reduced downtime, less reactive work, higher PM compliance, better technician utilisation, optimised spare parts and more reliable data for decision-making.

Implementation costs typically include:

• the licence or subscription;
• implementation services;
• data migration;
• process configuration;
• training;
• integrations;
• maintenance and support;
• infrastructure, where the system runs on-premise;
• mobile devices or code labels, where required.

Benefits can be measured through maintenance KPIs. The ranges below come from vendor implementation material and case studies, relate to individual projects and do not constitute an industry benchmark:

Benefit category	Example measure	Indicative effect
Reduced downtime	Improvement in MTTR and availability	20–50% reduction in downtime in selected cases
Lower maintenance costs	Maintenance cost year on year	10–25% reduction in maintenance costs
Better PM compliance	Planned work completed on time	15–30% improvement in PM compliance
MRO inventory optimisation	Inventory carrying cost	5–15% reduction in inventory costs
Workforce efficiency	Wrench time, less administration	More technician time on technical tasks rather than administration
Compliance and audit	Complete history of work orders and actions	Lower risk of documentation gaps

Payback at a mid-sized plant is often estimated at six to eighteen months, but it depends on the cost of downtime, the quality of input data, user adoption and the scope of the implementation.

It is worth avoiding ROI claims made without a baseline. Before implementation, measure the starting point: MTTR, MTBF, backlog, the share of reactive work, PM compliance, parts cost, labour cost and asset availability. Only then can the effect of the system be assessed credibly.

Integrating a CMMS with the data ecosystem

A CMMS should be part of a broader industrial data ecosystem rather than a separate work order database disconnected from production, automation, cost and condition monitoring.

Typical integrations include:

Integration	Data flow	Value
ERP	Costs, purchase orders, cost centres, procurement, suppliers	Consistency across costs, parts and purchasing
SCADA / DCS	Alarms, statuses, process events	Automatic requests or work orders raised from alarms
IoT sensors	Vibration, temperature, pressure, current, equipment condition	Triggering condition-dependent work
Data platform	CMMS data combined with production, quality and energy data	Cross-system analysis
Analytics	Dashboards, trends, deviations, prediction	Better maintenance decisions
Storeroom and procurement	Parts levels, reservations, purchase orders	Shorter repair times and better inventory control
Digital work instructions	Work execution procedures, checklists, standards	More consistent work order execution

Integration with SCADA systems and alarms can initiate work orders on the basis of technical events. Integration with sensors makes it possible to develop condition-based maintenance (CBM) and, with a longer data history and analytical models, predictive maintenance (PdM). Integration with analytics and a data platform allows failures, costs and availability to be compared against production context.

Smart RDM can act as a data and analytics layer complementary to a CMMS or EAM. It does not replace the CMMS as the system of record for work orders, but it can integrate maintenance, production, quality, energy and condition monitoring data to build a broader operational picture.

Vendor landscape 2026

The plant maintenance software market spans CMMS products for small and mid-sized plants, mobile-first solutions, enterprise EAM systems and analytical platforms that complement CMMS data.

Vendor	Positioning	Typical segment
MaintainX	Cloud CMMS with a mobile-first approach covering work orders, PM and team communication	Frontline teams and production operations
MAPCON	CMMS for manufacturing and facility management, covering work orders, PM and parts inventory	Manufacturing and technical facilities
Fiix (Rockwell Automation)	Cloud CMMS with analytics and links to the industrial automation ecosystem	Industrial plants and automation environments
UpKeep	Mobile CMMS for maintenance teams, assets, work orders and parts	Maintenance teams working in the field
Limble	Cloud CMMS for mid-sized manufacturers, with an emphasis on ease of use and PM automation	Mid-sized manufacturing plants
SAP PM	Plant Maintenance (PM) – the historic module name; within SAP S/4HANA it sits in the Asset Management scope and is tied to ERP processes	Large enterprises
IBM Maximo	EAM platform for multiple industries and locations, available in cloud and on-premise models	Enterprise organisations
Infor EAM	EAM system with industry editions for manufacturing, utilities, healthcare and infrastructure	Multi-site organisations
Coast	Maintenance management software covering work orders, PM and parts	Small and mid-sized operations
Smart RDM	Industrial data and analytics platform, complementary to CMMS/EAM	Organisations that need to combine maintenance data with production and analytics

This table is not a ranking. Some solutions focus on simplicity and mobility, some on enterprise integration, and some on data, analytics and the wider operational context. The choice should follow from process, scale, integration requirements and organisational maturity.

Common mistakes in CMMS selection and implementation

The most common mistake is treating a CMMS purely as an IT tool rather than as a change in the way maintenance works.

Typical problems include:

• selecting a system before the process has been put in order;
• no clear owner for asset data;
• an incomplete equipment hierarchy;
• failure codes that are too generic;
• no naming standards;
• migrating out-of-date data;
• an overly complex work order form;
• lack of adoption among technicians;
• rolling out without a mobile version despite field-based work;
• no integration with ERP, production or the parts storeroom;
• KPI reporting without defined targets;
• no performance review after go-live;
• treating the implementation as a one-off project.

A CMMS works well when it reflects the real way work gets done. The system should make work easier to carry out and to document, not simply increase the number of fields to complete.

How to start a system selection project

A plant maintenance software selection project is best started with a process workshop rather than with a list of vendor features.

A practical sequence:

1. Describe the current request and work order process.
2. Decide which assets are to be covered by the system.
3. Define the equipment hierarchy.
4. Check the quality of data on failures, parts and inspections.
5. Establish user roles.
6. Identify the KPIs that matter most.
7. Define mobile requirements.
8. Identify integrations with ERP, SCADA, DCS, IoT and a data platform.
9. Set security and compliance requirements.
10. Prepare the vendor selection criteria.
11. Run a pilot in a selected area.
12. Measure the results, and only then scale the solution.

The key question is this: which decisions and actions should the system support? If the answer is simply “we want a CMMS”, the project may end as a digital record book. If the answer concerns shorter MTTR, less reactive work, better PM compliance, tighter control of parts or credible KPIs, it becomes far easier to define the right scope and approach.

FAQ

What is plant maintenance software?

Plant maintenance software – also referred to as manufacturing maintenance software or industrial preventive maintenance software – is a system that supports the planning, execution, documentation and analysis of maintenance work in an industrial environment.

It most often covers work orders, preventive maintenance schedules, an asset registry, spare parts, mobile access, reporting and KPIs.

What is a CMMS?

A CMMS, or Computerized Maintenance Management System, is software for managing day-to-day maintenance activity.

It helps manage work orders, plan preventive maintenance, maintain an asset registry, control spare parts and report on performance.

How does a CMMS differ from an EAM?

A CMMS focuses on operational maintenance: work orders, inspections, parts and failure history.

EAM, or Enterprise Asset Management, covers a broader scope: the full asset life cycle, costs, procurement, regulatory compliance, depreciation and capital planning.

How does a CMMS differ from APM?

A CMMS manages maintenance work and documents what was done.

APM, or Asset Performance Management, uses data, analytics, condition monitoring and predictive models to improve reliability and reduce failure risk. APM usually complements a CMMS rather than replacing it.

What features should plant maintenance software have?

The core features are work order management, preventive maintenance scheduling, an asset registry, an equipment hierarchy, MRO parts management, mobile access, KPI reporting, user roles and integrations with other systems.

In more advanced environments, integrations with ERP, SCADA, IoT, a data platform and analytics also matter.

How do work orders work in a CMMS?

A work order in a CMMS usually moves through a cycle of request, approval, planning, assignment, execution, closure and review.

The work order records the asset, the priority, a description of the problem, the technician, labour hours, parts, failure codes, dates, status and completion notes.

How does a CMMS handle preventive maintenance?

A CMMS handles preventive maintenance by creating work orders automatically according to a schedule.

The trigger may be a date, running hours, distance, a production cycle or an event. The system helps monitor PM compliance and reduces the risk that planned inspections are missed.

What is an asset registry in a CMMS?

The asset registry is the central database of equipment, systems and components covered by maintenance.

It holds identification data, documentation, work history, spare parts, location, criticality classification and related work orders.

How do you choose the best plant maintenance software for manufacturing?

The best software is the one that fits the scale of the plant, the number of assets, how technicians work, integration requirements, the budget, the industry and the maturity of the organisation.

Rather than selecting a system on the basis of a feature list alone, assess the work order process, data quality, mobile requirements, integrations, KPI reporting and how easily users will adopt it.

Which CMMS is the best?

There is no single best CMMS for every organisation.

A small plant may need a simple mobile system; a mid-sized manufacturer may need a fast rollout and solid PM functionality; a large enterprise may need an EAM with ERP integration, regulatory compliance and multi-site support.

Does free CMMS software make sense?

Free or freemium CMMS software can be useful for small teams that want to bring order to basic work orders and simple schedules.

The constraints are usually limits on users, assets, reports, integrations, mobility, permissions and support. At greater scale, or where audit requirements apply, a paid solution is normally needed.

How much does plant maintenance software cost?

Cost depends on the licensing model, the number of users, the number of assets, functional scope, integrations, data migration, training and support.

Common models are per-user subscription, perpetual licence, per-module pricing, freemium or an enterprise agreement. Vendor price lists change frequently, so when comparing offers it is worth analysing the total cost structure rather than individual list prices.

How long does a CMMS implementation take?

A CMMS implementation at a mid-sized plant may take around three to six months.

In a multi-site or enterprise environment the project can run twelve to eighteen months. Data preparation usually takes the longest: the asset hierarchy, PM schedules, the parts catalogue and work history.

What is the return on investment in a CMMS?

Return on investment in a CMMS is measured through reduced downtime, shorter MTTR, better PM compliance, less reactive work, better use of parts and higher data quality.

Indicative effects include lower maintenance costs, improved PM compliance, reduced downtime and optimised MRO inventory. The actual outcome depends on the starting point, the quality of the implementation and user adoption.

Can a CMMS integrate with ERP?

Yes. A CMMS can integrate with ERP across costs, purchase orders, suppliers, cost centres, inventory and procurement.

Integration reduces manual re-entry of data and keeps maintenance work, parts consumption and costs consistent with one another.

Can a CMMS connect to IoT sensors?

Yes. A CMMS can receive data from IoT sensors or from a condition monitoring platform – for example vibration, temperature, pressure or equipment status.

Such data can trigger condition-based maintenance work orders, but it requires well-defined thresholds, rules and a response process.

How does a CMMS support maintenance analytics?

A CMMS provides data on work orders, repair times, parts, costs, failures, priorities and asset history.

Combined with production and measurement data, that information can feed dashboards, trend analysis, KPIs, assessment of failure costs and decisions on maintenance strategy.

Sources

1. ISO 55000 (terminology) and ISO 55001 (requirements) – asset management.
2. Industry material on CMMS, EAM and APM.
3. Market material on plant maintenance software and CMMS products.
4. Functional documentation of selected CMMS and EAM systems.
5. Industry material on preventive maintenance, work orders, MRO and KPIs.
6. Smart RDM internal material on industrial data, integration, analytics and asset monitoring.