PageSourceSearch

https://datamesh.com/factverse-docs/assets/js/1a0de66a.fb090ab4.js

js datamesh.com collected 2026-10-01 12:32:46 UTC 12,073 bytes, 1 lines download raw bytes

1"use strict";(self.webpackChunkfactverse_docs=self.webpackChunkfactverse_docs||[]).push([[25303],{91444:(e,n,s)=>{s.r(n),s.d(n,{assets:()=>c,contentTitle:()=>a,default:()=>h,frontMatter:()=>i,metadata:()=>r,toc:()=>o});const r=JSON.parse('{"id":"ecm","title":"Enterprise Content Management","description":"Customer guide to using Enterprise Content Management as the governed document layer for FactVerse operations, maintenance, compliance, and AI workflows.","source":"@site/.generated/en/docs/ecm.md","sourceDirName":".","slug":"/ecm","permalink":"/factverse-docs/ecm","draft":false,"unlisted":false,"tags":[],"version":"current","sidebarPosition":52,"frontMatter":{"slug":"/ecm","title":"Enterprise Content Management","description":"Customer guide to using Enterprise Content Management as the governed document layer for FactVerse operations, maintenance, compliance, and AI workflows.","sidebar_label":"Overview","sidebar_position":52},"sidebar":"docs","previous":{"title":"API Surface","permalink":"/factverse-docs/dfs/reference/api-surface"},"next":{"title":"Getting Started","permalink":"/factverse-docs/ecm/getting-started"}}');var t=s(74848),d=s(28453);const i={slug:"/ecm",title:"Enterprise Content Management",description:"Customer guide to using Enterprise Content Management as the governed document layer for FactVerse operations, maintenance, compliance, and AI workflows.",sidebar_label:"Overview",sidebar_position:"52"},a="Enterprise Content Management",c={},o=[{value:"Operating flow",id:"operating-flow",level:2},{value:"What ECM helps teams manage",id:"what-ecm-helps-teams-manage",level:2},{value:"Role paths",id:"role-paths",level:2},{value:"Common lifecycle",id:"common-lifecycle",level:2},{value:"Product boundary",id:"product-boundary",level:2},{value:"Read next",id:"read-next",level:2}];function l(e){const n={a:"a",h1:"h1",h2:"h2",header:"header",mermaid:"mermaid",p:"p",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,d.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.header,{children:(0,t.jsx)(n.h1,{id:"enterprise-content-management",children:"Enterprise Content Management"})}),"\n",(0,t.jsx)(n.p,{children:"Enterprise Content Management, or ECM, is the governed document layer for FactVerse. It helps teams organize operating manuals, inspection evidence, maintenance records, training materials, compliance packages, and site knowledge in the same environment where assets, work orders, digital twins, and AI Agent workflows are used."}),"\n",(0,t.jsx)(n.p,{children:"Use this section when documents need to become reliable operating context instead of files stored outside the workflow."}),"\n",(0,t.jsx)(n.h2,{id:"operating-flow",children:"Operating flow"}),"\n",(0,t.jsx)(n.mermaid,{value:"flowchart TD\n  A[Documents and field records] --\x3e B[ECM folders, tags, and versions]\n  B --\x3e C[Permissions, classification, policies, and audit]\n  C --\x3e D[Assets, work orders, SOPs, and compliance packs]\n  D --\x3e E[Inspector, DFS, AI Agent, and field operations]"}),"\n",(0,t.jsx)(n.h2,{id:"what-ecm-helps-teams-manage",children:"What ECM helps teams manage"}),"\n",(0,t.jsxs)(n.table,{children:[(0,t.jsx)(n.thead,{children:(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.th,{children:"Area"}),(0,t.jsx)(n.th,{children:"Typical content"}),(0,t.jsx)(n.th,{children:"Used by"})]})}),(0,t.jsxs)(n.tbody,{children:[(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Facility operations"}),(0,t.jsx)(n.td,{children:"Equipment manuals, BMS records, site drawings, inspection photos, operating procedures"}),(0,t.jsx)(n.td,{children:"Facility managers, inspectors, maintenance teams"})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Predictive maintenance"}),(0,t.jsx)(n.td,{children:"Maintenance history, failure reports, vibration or sensor evidence, replacement records"}),(0,t.jsx)(n.td,{children:"Reliability teams, data stewards, AI Agent workflows"})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Compliance and audit"}),(0,t.jsx)(n.td,{children:"Approval records, signed documents, retention evidence, exception notes, generated compliance packs"}),(0,t.jsx)(n.td,{children:"Compliance owners, auditors, project administrators"})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Field work"}),(0,t.jsx)(n.td,{children:"Mobile photos, job attachments, repair notes, handover materials"}),(0,t.jsx)(n.td,{children:"Field technicians, supervisors, remote experts"})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Digital twin context"}),(0,t.jsx)(n.td,{children:"Documents linked to assets, areas, systems, and work orders"}),(0,t.jsx)(n.td,{children:"Inspector, Designer, AI Agent, Twin Engine workflows"})]})]})]}),"\n",(0,t.jsx)(n.h2,{id:"role-paths",children:"Role paths"}),"\n",(0,t.jsxs)(n.table,{children:[(0,t.jsx)(n.thead,{children:(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.th,{children:"Role"}),(0,t.jsx)(n.th,{children:"Start with"}),(0,t.jsx)(n.th,{children:"Confirm before handoff"})]})}),(0,t.jsxs)(n.tbody,{children:[(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Operations user"}),(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/getting-started/",children:"Getting Started with ECM"})}),(0,t.jsx)(n.td,{children:"Documents are in the right folder, searchable, and linked to the right asset or work order."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Document owner"}),(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/document-workspace/",children:"Document Worksp
1ace"})}),(0,t.jsx)(n.td,{children:"Folder structure, tags, versions, and ownership are ready for daily use."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Tenant administrator"}),(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/permissions-and-governance/",children:"Permissions and Governance"})}),(0,t.jsx)(n.td,{children:"Roles, folder access, classification, policies, and audit expectations are configured."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Process owner"}),(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/workflows-and-approvals/",children:"Workflows and Approvals"})}),(0,t.jsx)(n.td,{children:"Review, approval, signature, and record retention steps match the operating process."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Integration owner"}),(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/connectors-and-imports/",children:"Connectors and Imports"})}),(0,t.jsx)(n.td,{children:"Source ownership, sync cadence, folder target, and validation steps are defined."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"AI workflow owner"}),(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/ai-and-agent/",children:"ECM for AI Agent"})}),(0,t.jsx)(n.td,{children:"Source documents, access rules, version scope, and citation expectations are clear."})]})]})]}),"\n",(0,t.jsx)(n.h2,{id:"common-lifecycle",children:"Common lifecycle"}),"\n",(0,t.jsxs)(n.table,{children:[(0,t.jsx)(n.thead,{children:(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.th,{children:"Phase"}),(0,t.jsx)(n.th,{children:"ECM area"}),(0,t.jsx)(n.th,{children:"Result"})]})}),(0,t.jsxs)(n.tbody,{children:[(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Collect"}),(0,t.jsx)(n.td,{children:"Uploads, mobile capture, connectors, imports"}),(0,t.jsx)(n.td,{children:"Documents and field records enter the tenant."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Organize"}),(0,t.jsx)(n.td,{children:"Folders, tags, metadata, asset links"}),(0,t.jsx)(n.td,{children:"Content can be found by team, asset, site, or workflow."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Govern"}),(0,t.jsx)(n.td,{children:"Roles, folder access, classification, policies"}),(0,t.jsx)(n.td,{children:"Access follows project and compliance rules."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Use"}),(0,t.jsx)(n.td,{children:"Preview, download, search, comments, workspaces"}),(0,t.jsx)(n.td,{children:"Teams can use approved content in daily operations."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Approve"}),(0,t.jsx)(n.td,{children:"Workflow, signatures, approval status"}),(0,t.jsx)(n.td,{children:"Changes move through review before release or record declaration."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Retain"}),(0,t.jsx)(n.td,{children:"Audit logs, compliance packs, retention actions"}),(0,t.jsx)(n.td,{children:"Evidence remains traceable for handover and audit."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:"Reuse"}),(0,t.jsx)(n.td,{children:"AI Agent, SOPs, predictive maintenance, Inspector"}),(0,t.jsx)(n.td,{children:"Documents become governed context for operations and intelligence."})]})]})]}),"\n",(0,t.jsx)(n.h2,{id:"product-boundary",children:"Product boundary"}),"\n",(0,t.jsx)(n.p,{children:"ECM manages operating documents and evidence inside FactVerse. Source systems such as EAM, CMMS, SharePoint, file servers, data historians, and external compliance systems can remain the source of record when a project defines them that way. ECM records how documents are used, linked, reviewed, and governed inside FactVerse workflows."}),"\n",(0,t.jsx)(n.p,{children:"AI-assisted search, comparison, translation, and compliance review should be treated as workflow assistance. The customer process, assigned owners, approvals, and audit record decide what becomes official."}),"\n",(0,t.jsx)(n.h2,{id:"read-next",children:"Read next"}),"\n",(0,t.jsxs)(n.table,{children:[(0,t.jsx)(n.thead,{children:(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.th,{children:"Page"}),(0,t.jsx)(n.th,{children:"Use"})]})}),(0,t.jsxs)(n.tbody,{children:[(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/getting-started/",children:"Getting Started with ECM"})}),(0,t.jsx)(n.td,{children:"Create a folder, upload a document, tag it, link it to an asset, and verify access."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/document-workspace/",children:"Document Worksp
1ace"})}),(0,t.jsx)(n.td,{children:"Understand folders, versions, tags, search, workspaces, and document relationships."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/permissions-and-governance/",children:"Permissions and Governance"})}),(0,t.jsx)(n.td,{children:"Plan roles, folder access, classification, policies, and audit."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/workflows-and-approvals/",children:"Workflows and Approvals"})}),(0,t.jsx)(n.td,{children:"Build document review, approval, signature, and record handover flows."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/connectors-and-imports/",children:"Connectors and Imports"})}),(0,t.jsx)(n.td,{children:"Bring external documents into FactVerse with owner and sync controls."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/ai-and-agent/",children:"ECM for AI Agent"})}),(0,t.jsx)(n.td,{children:"Prepare governed document context for AI Agent workflows."})]}),(0,t.jsxs)(n.tr,{children:[(0,t.jsx)(n.td,{children:(0,t.jsx)(n.a,{href:"/factverse-docs/ecm/recipes/",children:"ECM Recipes"})}),(0,t.jsx)(n.td,{children:"Follow task-oriented guides for operations, maintenance, compliance, and field records."})]})]})]})]})}function h(e={}){const{wrapper:n}={...(0,d.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(l,{...e})}):l(e)}},28453:(e,n,s)=>{s.d(n,{R:()=>i,x:()=>a});var r=s(96540);const t={},d=r.createContext(t);function i(e){const n=r.useContext(d);return r.useMemo(function(){return"function"==typeof e?e(n):{...n,...e}},[n,e])}function a(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:i(e.components),r.createElement(d.Provider,{value:n},e.children)}}}]);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.