Engineering-led maintenance and operational control.

Plant management software developed from real maintenance engineering.

dMS originated in the mid-1990s as a practical system for maintenance, production and health and safety. Its engineering foundation still shapes a platform built around equipment, work, evidence, performance and responsibility.

Developed since the mid-1990s

Created in the workshop to improve maintenance, safety and plant performance.

dMS began as a practical plant management and operational control system rather than a generic software package assembled around a feature list.

The purpose was to reduce avoidable maintenance cost, prevent incidents and give management a clearer view of the work affecting plant performance. Equipment, maintenance plans, production information, materials, health and safety records and reporting needed to remain connected to the people responsible for them.

Seven years of development and practical implementation helped streamline the early system into an economical and usable management platform. That same approach remains central: configure the system around the plant, retain useful operational history and make information available for decisions.

What plant control means here: dMS manages maintenance, production, safety and operational information. It is not presented as PLC, SCADA or direct machinery-control software.

Mechanical maintenance work in an industrial environment
Engineering firstDeveloped around real maintenance work, plant responsibility and the evidence management needs to act.
01Plant utilisation

Make lost production, delayed work and operational constraints more visible.

02Performance efficiency

Use production and shift information to review how effectively units perform.

03Overall Equipment Effectiveness

Combine downtime and production handover values to support OEE reporting per Production Unit.

04Maintenance effectiveness

Plan work, control execution and preserve useful equipment history.

05Spares and materials

Control requisitions, receiving, inventory and issues against operational demand.

06Equipment life

Use recurring work, condition findings and history to support better long-term asset care.

07Production information

Retain Production Unit, downtime, reason, shift and handover information.

08Safety and quality

Support Health and Safety controls and ISO 9001 quality-management processes and records.

Original designer

Willie King brought maintenance-system experience into the design of dMS.

His background combined mechanical engineering, plant responsibility, maintenance-system implementation and direct experience of the difficulties users face when software is expensive, complex or detached from the work.

That experience shaped dMS as a practical and economical maintenance management tool for all levels of maintenance personnel, with the broader production, safety and compliance controls growing from the same operational foundation.

Design principleHelp people maintain the plant without making the software the main job.
Product principles

The platform follows a few durable operational ideas.

The modules differ, but useful industrial records share the need for clear context, responsibility, history and reporting.

01

Keep context attached

Work, findings, documents and history should remain connected to the person, equipment, sample or controlled record they describe.

02

Make responsibility visible

Operational systems must help the right people understand what is required, what is outstanding and what has been completed.

03

Build usable history

Completed activity should become evidence for future planning, review and improvement rather than disappearing into an archive.

04

Report for decisions

Dashboards and reports should reveal operational status and recurring concerns, not merely reproduce captured rows.

05

Respect specialised control

Maintenance, laboratory, medical and compliance records can share a platform without being treated as the same workflow.

06

Configure around the site

Implementation should reflect the organisation's assets, roles, records and responsibilities.

A maintenance-led platform

Maintenance and Reliability remains the centre of gravity.

Preventive maintenance, maintenance plans, work orders, equipment history, RCM/FMECA, KPIs, paper or paperless work and structural inspection management form the flagship product story.

The wider solutions extend that operational foundation into production utilisation and OEE, LIMS, Health and Safety, Quality, Material Control, Training and Competency, Medical Station and Firearm Compliance.

Explore the flagship solution
Maintenance & ReliabilityEngineering foundation
Production & OEELIMSSHEQualityMaterialsTrainingMedicalFirearm
Implementation approach

Start with the operational problem and build the controlled structure around it.

A strong implementation depends on accurate equipment, ownership, workflows and reporting requirements. Software does not repair an undefined process by politely existing beside it.

01

Understand the operation

Map the assets, people, records and decisions the system must support.

02

Define the controlled scope

Select the modules, workflows and information required for the first implementation.

03

Configure and validate

Align structures, access, forms and reports with responsible client users.

04

Train for real use

Teach users according to their roles and the work they will perform.

05

Review and improve

Use operational feedback and captured history to strengthen the implementation.

Industrial plant at night
South African operational experience

Built close to the industries it serves.

dMS is based in Gauteng and has been developed through decades of practical work around South African maintenance, production, safety, laboratory and compliance requirements.

The platform's value comes from combining software capability with an understanding that every useful record belongs to an operating process and a responsible person.

Explore industry applications
Practical implementation

Discuss the operation behind the software requirement.

Start with the maintenance, reliability, laboratory or compliance problem that needs stronger control.