CMMS Attachments and Evidence with ECM
Work orders often need documents: photos, service reports, SOPs, permits, safety records, checklists, and closeout packages. ECM provides the governed document layer that links those files to work orders, assets, providers, and review records.
Use this guide when CMMS Operations needs attachment sync, evidence review, closeout packages, or AI Agent document context.
Evidence Flow
Prerequisites
| Requirement | Why it matters |
|---|---|
| Attachment source | The team must know whether files come from CMMS, mobile field upload, file server, or document system |
| ECM folder plan | Files need a governed destination and owner |
| Metadata rules | Documents need type, source, owner, work-order ID, asset ID, and retention tags |
| Access policy | Sensitive service records and site documents need scoped access |
| File policy | File type, size, virus scan, conversion, preview, and retention behavior need review |
| Closeout requirements | The team must define which evidence is required before closing work |
Source Data Inputs
| Input | Use |
|---|---|
| Work-order ID | Links evidence to the maintenance record |
| Provider ID | Preserves the source system or contractor origin |
| Asset and location reference | Links files to operating context and digital twin views |
| Attachment metadata | File name, type, size, source path, upload time, owner, classification |
| File content | Photo, report, checklist, permit, SOP, manual, or closeout package |
| Review status | Draft, reviewed, approved, rejected, obsolete, or archived |
| Retention policy | Defines how long the document remains available |
Evidence Types
| Evidence type | Typical use |
|---|---|
| Field photo | Shows observed condition, completed repair, damage, or access state |
| Service report | Records technician work, diagnosis, parts, action taken, and recommendations |
| SOP or manual | Provides procedure context for review or AI Agent support |
| Checklist | Shows required steps and completion status |
| Permit or safety record | Supports work authorization and compliance review |
| Inspection record | Links field inspection results to work-order follow-up |
| Closeout package | Bundles outcome, evidence, and approval record for audit or handover |
Configure Attachment Handling
- Decide which attachment sources are in scope.
- Define ECM folders, document types, tags, and owners.
- Map work-order ID, provider ID, asset ID, and source file metadata.
- Configure import, upload session, or connector behavior.
- Test a small set of files from each source.
- Review preview, download, permissions, and search behavior.
- Link imported files to work orders and assets.
- Validate closeout rules and evidence packages.
Closeout Evidence Review
Before closing a work order, confirm:
- required photos or reports are attached;
- files open for the intended reviewers;
- service report belongs to the correct work order and asset;
- source path and upload history are traceable;
- obsolete or duplicate files are marked;
- sensitive documents have the correct classification;
- closeout package includes outcome and reviewer decision.
Expected Output
The evidence workflow should produce:
- linked attachments under the correct work order and asset;
- document metadata for source, owner, type, classification, and retention;
- preview and download access for approved users;
- evidence package for closeout or audit;
- ECM context available for AI Agent workflows when allowed.
Troubleshooting
| Symptom | Check |
|---|---|
| Attachment does not appear on the work order | Work-order ID mapping, provider ID, import status, and metadata rule |
| File cannot be previewed | File format, conversion support, file size, and access policy |
| Field upload fails | Network state, file size, file type, mobile permission, and upload session |
| AI Agent cannot read evidence | ECM access, indexing state, classification, and document readiness |
| Closeout package is incomplete | Required evidence rule, folder mapping, document type, and reviewer status |