Connectors and Imports

ECM can receive documents through direct upload, mobile capture, import sessions, and managed connectors. Use connectors and imports when documents already live in another system but need to become governed context for FactVerse operations.

Prerequisites

Before configuring a connector or large import, confirm:

Requirement	Notes
Source owner	A business or IT owner can approve source access and source scope.
Credentials	Access is provided through the customer's approved credential process.
Target folder	Imported files have a planned ECM destination.
Metadata plan	Owner, document type, classification, tags, and links can be assigned or reviewed.
Validation owner	A person or team will review imported content before operational use.

Source data

Typical source data includes file names, paths, file content, timestamps, source owner, source system metadata, and business identifiers such as asset, work-order, project, or site names.

Import flow

Source planning

Before importing, confirm the source and ownership model.

Question	Why it matters
Which system owns the source document?	Avoids confusion between source-of-record and ECM working copy.
Which folder should receive the document?	Keeps imported documents usable by operations teams.
Who validates imported content?	Prevents unreviewed files from becoming official evidence.
How often should the source sync?	Aligns with operations and compliance expectations.
Which metadata should be mapped?	Enables search, tags, links, and AI workflows.
Which files should be excluded?	Keeps draft, obsolete, private, or irrelevant files out of ECM.

Common source types

Source	Typical content	Notes
File server	Manuals, drawings, project handover folders	Start with a narrow folder and validate naming.
SharePoint or document system	SOPs, policies, training files	Confirm source ownership and approval state.
EAM or CMMS	Work-order attachments, service reports	Link imported files to assets and work orders.
Mobile capture	Photos, field notes, repair evidence	Validate location, asset, work order, and timestamp.
Project archive	Commissioning, acceptance, vendor packages	Use a handover owner and review checklist.
Compliance repository	Certificates, audit support, signed records	Apply classification and retention expectations.

Connector setup checklist

Step	Check
Define source	Source system, folder, credentials, and owner are known.
Test access	Connector can reach the source with approved credentials.
Choose target	Imported files land in a planned ECM folder.
Map metadata	Title, document type, owner, tags, classification, and related object can be assigned or reviewed.
Validate sample	A small sample imports correctly before a large sync.
Review access	Folder and document permissions match the intended audience.
Record sync	Sync time, result, and rejected files are visible.

Imports and upload sessions

Use resumable upload sessions for larger files or unstable networks. After upload, verify the document record before routing it into operations.

Check:

• file completed successfully;
• title and type are correct;
• preview or download works for the right users;
• failed chunks or duplicate uploads are resolved;
• the final version is the intended one;
• the document is tagged and linked.

Validation after import

Imported documents should be reviewed before they become official workflow context.

Validation checklist:

• source path and file name are traceable;
• owner is assigned;
• obsolete or duplicate files are marked for cleanup;
• sensitive documents are classified;
• required tags are applied;
• asset, area, work-order, or project links are correct;
• sample users can find the files through search;
• audit records show import and review activity.

Working with DFS

ECM manages documents and evidence. DFS manages operational data feeds and governed datasets. Many projects use both:

Need	Use
Equipment manuals, drawings, photos, SOPs, certificates	ECM
Sensor history, asset tables, work-order fields, BMS points	DFS
AI Agent workflow that needs documents and data	ECM plus DFS
Compliance package with readings, work orders, and evidence files	ECM plus DFS

For data preparation, see Data Fusion Services.

Troubleshooting

Symptom	Check
Connector cannot connect	Credentials, network allowlist, source URL, and tenant environment.
Files import to the wrong folder	Connector mount target and folder mapping.
Imported files are hard to find	Metadata, tags, title quality, and linked objects.
Duplicate documents appear	Source path rules, naming, and version strategy.
Preview fails	File format, file size, conversion support, and access rules.
Sync history shows rejected files	File type, permission, size, duplicate rule, or validation policy.
AI Agent cannot use imported files	Access, indexing status, classification, and version readiness.