Frequently Asked Questions

An EDMS is a system that captures, organizes, secures and tracks documents through their lifecycle, using metadata rather than folder locations to identify what a document is and who should access it.

• Centralizes contracts, drawings, policies and records in one controlled system
• Tracks who created, reviewed and approved each document, and when
• Replaces manual folder structures with searchable, rule-based organization

Learn more: electronic document management system

These terms overlap but describe different scopes of information management.

• DMS (Document Management System) - manages documents and their versions
• ECM (Enterprise Content Management) - a broader category covering documents, records, workflows and content across an organization
• CMS (Content Management System) - typically manages website or web content
• DAM (Digital Asset Management) - manages media files such as images, video and brand assets

Learn more: document management solution

Metadata-driven document management organizes information by what a document is (contract, invoice, drawing, project, client) rather than where it is saved. Each document is tagged with structured properties, so it can be found, secured and routed automatically regardless of folder location.

This is the model used by platforms like M-Files, and it is a core reason metadata-driven systems can replace shared drives without recreating the same folder chaos.

Learn more: metadata-driven document management

Version control automatically saves a new version each time a controlled document is checked out and edited, while keeping the full history available. This prevents multiple people from overwriting each other's changes and makes it possible to see exactly what changed, when, and by whom.

• Only the current approved version is shown to general users by default
• Previous versions remain available for audit or rollback
• Check-in / check-out locking prevents simultaneous conflicting edits

SharePoint organizes content primarily around sites, libraries and folders. M-Files instead uses a metadata-driven model, where a document is classified by what it is (its type, project, client, status) rather than which folder it sits in, and can appear in multiple relevant views without being duplicated.

In practice, many organizations use both together - M-Files can sit on top of or alongside Microsoft 365 to add metadata-driven classification, workflow and version control while keeping documents accessible through Teams and Outlook.

Learn more: M-Files document management

Common signals it is time to move on from shared drives and folder-based storage include:

• Staff regularly cannot find the current version of a document
• Duplicate copies of the same file exist in multiple folders
• There is no clear record of who approved a document or when
• Access permissions are difficult to manage or audit
• Growth, audits, or ISO 9001 requirements are exposing gaps in document control

Learn more: simple document management for growing teams

A CMMS (Computerized Maintenance Management System) is software focused on planning, tracking and recording maintenance work - work orders, preventive maintenance schedules, spare parts and technician activity.

Asset management software is broader: it also covers the full asset register, lifecycle, financial value and long-term performance of equipment, of which maintenance is one part. In practice, most organizations use a CMMS as the day-to-day tool that feeds their wider asset management strategy.

Learn more: CMMS solution

• Reactive - repairing equipment only after it fails
• Corrective - fixing a defect once it is identified, before full failure
• Preventive - scheduled maintenance based on time or usage, to prevent failure
• Predictive - maintenance triggered by real condition data (e.g. vibration, temperature) rather than a fixed schedule

Most organizations aim to shift from reactive toward preventive and, over time, predictive maintenance.

A CMMS reduces unplanned downtime primarily by making preventive maintenance easier to schedule, assign and track, so problems are caught before they cause failures.

• Automated PM scheduling reduces missed maintenance windows
• Complete asset history highlights recurring failure patterns
• Mobile work orders speed up technician response time
• Spare parts visibility avoids delays waiting for materials

Learn more: CMMS maintenance management

Modern cloud CMMS platforms are generally built to integrate with ERP systems (for purchasing, inventory and cost data) and with IoT sensors or condition-monitoring systems (to trigger predictive maintenance from real equipment data). The specific integrations available depend on the platform and your existing systems, so this is usually assessed during scoping.

There is no single fixed price - CMMS cost depends on factors such as:

• Number of users and technicians
• Number of assets and sites
• Deployment model (cloud, on-premise or hybrid)
• Integrations with ERP, IoT or existing systems
• Data migration, configuration and training needs

Talk to our team about your requirements for an accurate estimate.

Typical signs it's time to move on from spreadsheets include: maintenance history scattered across multiple files, missed preventive maintenance because nobody tracks due dates, no visibility into technician workload, difficulty proving compliance during audits, and growing numbers of assets that spreadsheets can no longer represent accurately.

Learn more: benchmark your maintenance maturity

A digital Permit to Work (PTW) system replaces paper permit forms with an electronic workflow for requesting, reviewing, approving, and closing out work permits - such as hot work, confined space entry, working at height, or electrical isolation.

• Routes permits to the right approvers automatically
• Flags missing hazard assessments or isolations before approval
• Tracks permit status, expiry and close-out in real time

Learn more: digital Permit to Work

Digital PTW improves safety by making it harder to skip required steps - approvals, isolations, and hazard checks must be completed in sequence before work can proceed. It also creates a complete, timestamped audit trail of every permit, which supports incident investigations and regulatory reporting.

Learn more: why permit coordination matters during shutdowns

The Occupational Safety and Health Act 1994 (Act 514) places a general duty on employers to ensure, so far as is practicable, safe systems of work - it does not name "Permit to Work" as a specific mandatory system for every workplace. Permit to Work is, however, a long-established control measure expected by DOSH (Department of Occupational Safety and Health Malaysia) and industry codes of practice for higher-risk activities such as hot work, confined space entry and working at height.

In short: PTW is best understood as regulatory-expected best practice under the general duty of care, not a single named legal mandate - and specific industries or activities may have their own additional requirements.

Source: DOSH (Department of Occupational Safety and Health Malaysia)

Yes. Digital PTW platforms are generally designed to be accessed from mobile devices on site, and contractors can typically be granted scoped access to submit and track their own permits without seeing unrelated company data. Exact permissions depend on how the system is configured for your site.

A JSA (Job Safety Analysis) breaks a task into steps and identifies the hazards and controls for each step - it is a risk assessment. A Permit to Work is the formal authorization process that confirms those controls (and any required isolations or approvals) are actually in place before work starts. In practice, a completed JSA is often a required input to issuing a permit.

Good practice is to retain the full permit record - request, risk assessment, approvals, isolation certificates, extensions and close-out - for a period consistent with your internal HSE policy and any applicable industry or insurance requirements. A digital PTW system keeps this trail automatically, which is typically far more complete than paper filing.

ISO 9001:2015 requires organizations to control "documented information" (Clause 7.5) - meaning documents and records must be identifiable, approved before use, protected from unintended changes, available where needed, and retrievable. The standard does not mandate a specific software tool; it defines the outcome, and organizations choose how to achieve it.

Learn more: how digital document management supports your QMS

No. ISO 9001 does not require any specific software, including an EDMS. It requires that documented information be controlled, and many organizations find that a metadata-driven EDMS is a practical way to meet those requirements at scale - particularly around approvals, version control, and evidence of who accessed or changed a document.

Importantly, using a tool like M-Files does not, on its own, make an organization ISO 9001 compliant - the organization's processes, controls and records still have to meet the standard's requirements. Technology supports compliance; it does not replace it.

• Provides a clear, timestamped approval history for each controlled document
• Makes it easy to demonstrate that obsolete versions are not in active use
• Speeds up locating requested evidence during an audit
• Supports scheduled reviews so documents don't silently go out of date

Learn more: ISO 9001 document control

ISO 9001 requires that obsolete documented information be identified and prevented from unintended use, while still being retained where needed for legal or knowledge purposes. In practice this usually means retiring the old version from active workflows, clearly marking or archiving it, and ensuring only the current approved version is visible to staff performing the work.

ISO 9001:2015 remains the current, valid version of the standard. ISO's technical committee has been working on a revision, with certification bodies indicating a new version is expected around late 2026, followed by a multi-year transition period once it is formally published. Organizations do not need to take action yet, but it is worth watching for the official ISO publication date rather than relying on preliminary estimates.

Source: ISO 9001 - Quality management systems

• Outdated procedures still in circulation on shared drives or in print
• No clear evidence of document review or approval
• Inconsistent versions used across departments or sites
• Missing or incomplete records of changes to controlled documents

AI-powered document management uses machine learning to help classify documents, extract key information, and answer questions about content - on top of the version control, security, and workflow capabilities of a standard EDMS. The goal is to reduce manual tagging and filing, and to make it possible to ask a system a question rather than search through folders.

Learn more: AI-powered document management

Yes, within limits. AI models can be trained or configured to recognize common document types (invoices, contracts, drawings) and suggest metadata such as document type, date, or counterparty, which significantly reduces manual tagging. Accuracy depends on document quality and consistency, so most implementations still include a review step for classification, at least initially.

Traditional search matches the exact words typed into the search box. AI-powered (semantic) search understands intent and context, so it can find relevant documents even when the wording differs, and in some cases can summarize or answer a question directly using the content of your organization's own documents rather than just listing files.

Learn more: the future of ECM, AI and emerging trends

AI readiness describes how well an organization's information is structured, tagged and governed - which determines how effectively AI tools can actually use it. Organizations with scattered files, inconsistent naming, and no metadata typically get poor results from AI, regardless of which tool they adopt.

• Consolidate documents out of disconnected drives and inboxes
• Apply consistent metadata and classification
• Establish clear access and governance rules before scaling AI use

Learn more: DMS & AI readiness assessment

Key risks include AI surfacing sensitive information to users who shouldn't see it if permissions aren't correctly configured, inaccurate classification or extraction being trusted without review, and data governance gaps when documents move into external AI tools. These risks are managed through proper access controls, human review of AI output where it matters, and choosing platforms that keep your data within your existing security model.

When knowledge lives only in one person's inbox or personal files, it typically leaves with them. Centralizing documents, decisions and project history in a searchable system - and using AI search to surface relevant past work - means that knowledge stays accessible to the team after someone moves on.

Learn more: what happens to your knowledge when a senior leader leaves

Workflow automation replaces manual, email-driven processes - like routing a document for review, approval, or sign-off - with a defined digital sequence that moves tasks automatically to the right person, sends reminders, and records every step. Common examples include document approvals, invoice processing, and change requests.

Learn more: workflow automation

A document is routed automatically to the correct approver(s) based on rules (department, value, document type), with reminders for overdue approvals and a full record of who approved what and when. Where legally required, electronic signatures can be added to formalize the approval.

Learn more: eSignature and contract management

Yes - automated workflows can help ensure that document review and approval steps required by ISO 9001 are actually followed consistently, and that each step is timestamped and recorded, which is exactly the kind of evidence auditors look for. As with any technology, the workflow still needs to reflect your actual approved procedure to count as compliant.

Every action in an automated workflow - submission, review, approval, rejection, comment - is logged automatically with a timestamp and user identity. This creates a complete audit trail without anyone needing to manually track it, and makes it far easier to answer "who approved this, and when?" months later.

Good candidates are usually processes that are repetitive, rule-based, involve multiple people, and currently rely on email or paper to move forward - such as document approvals, purchase requests, or change control. Processes that require significant judgment on a case-by-case basis are harder to automate fully, but can often still be partially streamlined.

• Time saved per approval cycle (before vs. after automation)
• Reduction in approval delays or bottlenecks
• Fewer errors from manual re-entry or lost documents
• Audit preparation time saved

Signs your organization would benefit from a document management system include: staff spending noticeable time searching for files, multiple versions of the same document in circulation, difficulty proving compliance during audits, and information that lives in individual inboxes rather than a shared, controlled system.

Learn more: take the free DMS & AI readiness assessment

• How well it fits your existing processes versus forcing you to change everything
• Integration with Microsoft 365, ERP, or other core systems
• Mobile access for field or on-site staff
• Vendor implementation and local support experience
• Total cost including configuration, migration and training, not just licensing

It depends on your IT strategy, regulatory requirements, and existing infrastructure. Cloud deployments typically reduce infrastructure overhead and support remote/mobile access more easily. On-premise deployments can suit organizations with strict data residency or network requirements. Hybrid approaches let some data stay on-site while other functions run in the cloud. There is no universally "correct" answer - it should match your actual constraints.

• Poor user adoption - staff quietly reverting to old habits
• Unclear ownership of the new system or process
• Trying to digitize a broken process instead of fixing it first
• Underestimating data migration and cleanup effort
• Insufficient training or change management

Digital maturity describes how far an organization has progressed from manual, paper- and email-based processes toward connected, automated, and data-driven ones. It typically spans document control, workflow automation, and data/AI readiness. A structured assessment benchmarks your current state against industry peers and highlights the highest-impact next steps.

Learn more: benchmark your digital maturity

Cost varies widely based on scope - the number of systems involved, users, data migration complexity, integrations, and how much process redesign is needed alongside the technology. Rather than a fixed figure, most engagements start with an assessment to scope requirements accurately.

Talk to our team about your specific requirements.

EPC and engineering projects generate huge volumes of drawings, specifications, RFIs, transmittals and revisions across multiple contractors and disciplines. Without controlled document management, teams risk working from outdated drawings, losing track of approvals, and facing costly rework or disputes. Project-based document control keeps every stakeholder working from the current, approved version.

Learn more: engineering document management

Manufacturers benefit from connecting maintenance management (CMMS) with document control, so equipment manuals, SOPs, and safety procedures are linked directly to the relevant asset and always reflect the current approved version. This reduces downtime from technicians working off outdated instructions and supports ISO 9001 and quality audits at the same time.

Energy and oil & gas operations typically combine two needs: controlled technical documentation (P&IDs, technical specs, compliance records) and digital Permit to Work for high-risk site activities. Bringing both under a connected digital system - rather than separate paper processes - improves visibility during shutdowns, turnarounds and routine operations alike.

Learn more: permit coordination during shutdowns and turnarounds

Data centres and logistics operators rely on continuous uptime, which makes maintenance history, warranty records, and technical documentation for critical equipment especially important. Linking asset records to maintenance schedules and controlled documentation reduces the risk of a missed inspection or an outdated procedure causing unplanned downtime.

Contractor documentation - insurance certificates, competency records, permits, method statements - is easiest to manage when contractors have scoped access to submit and update their own records directly in a shared system, with automatic reminders before expiry. This avoids the common problem of expired certificates only being discovered after an incident or audit.

Knowledge transfer improves when project documentation, lessons learned, and decisions are captured in a searchable, centralized system rather than left in individual inboxes or personal notes. This means a new team member - or a whole new project - can draw on what previous projects already learned, instead of repeating the same mistakes.

Learn more: why project delays are often an information problem