其他系统与定制化套件
文档管理系统
文档问题很少自己冒出来。图纸发错版本，作业照着某人去年打印的复印件执行，关键时刻却拿不出该用的那一版。文件都没丢；问题在于没人说得清哪份是现行版。
文档管理系统把文档当作受控对象来管理，而不只是文件。每份文档都有当前版本、明确可见人员范围，以及改了什么、何时改的、由谁批准的完整记录。分发不再是一件靠记得发送正确副本的事。
实用的检验很简单：当有人要一份文件的现行版本、问两个版本之间改了什么、或问某次变更是谁在何时批准的，答案应当几秒内从系统里出来——而不是翻文件柜或问人。
一份没人找得到的文档并不算丢失。它只是在需要时拿不出来而已。
它是什么
文档是受控对象。每份文档有身份、状态、现行版本与责任人——不只是硬盘上的一个文件名。有意义的版本控制。修订彼此关联，两个版本之间改了什么一目了然，而非靠比对文件日期去猜。按角色与目录设权限。谁可读、谁可编辑、谁可发布一次设定，而非每次共享副本时重新决定。评审与审批属于文档本身。文档在评审中流转，决定及其条件随文档存档。分发始终指向现行版本。授予的是文档的访问权，而非一份发出时才正确的副本。可证明的留存。每类文档保存多久、到期后如何处置，按政策设定，而非取决于存储空间。
当下的阻碍是什么
版本有好几个，没人知道哪个是现行的。文件名不是版本控制系统。
草稿、修订版、终版、终版修订版同时存在。没人能不看一眼就说清哪份在生效。版本靠日期与姓名缩写区分。它只能告诉你何时被动过，不能说明改了什么。已作废的副本仍在流通。而且还会被使用——因为手头正好有这一份。
访问权限由发送者临场决定。权限成了一种信任行为，而不是一条规则。
A document is shared with whoever needs it, by whatever means. 于是，持有副本的人员清单无人维护。
Confidential material sits in the same folder as everything else. Protected by whoever remembers not to forward it.
When someone leaves, nobody knows what they had. Which is discovered when it matters.
变更在事后不可见。记录止步于发布那一刻。
变更到达时不说明改了什么、为什么改。读者只能自己找不同。审批散落在邮件串里。被质询时拿不出决定。文档与所属流程之间没有任何关联。评审无法判断文件集是否齐全。
留存期限取决于磁盘空间。这不是策略。
文档一直留到空间不够。然后或随意删除，或干脆什么都不删。处置了什么、何时处置的，没有任何记录。而这恰恰是审计要问的。
一份受控文档的生命周期
每份文档走同样的路径，无论内容是什么——关于文档的问题因此总有同样的答案。
文件依据明确的审批发布，任何历史日期生效的是哪一版都能拿得出来。被替代的版本按留存策略保留而非删除，因为“当时执行的是哪份文件”这个问题被问到的频率超出想象——通常是在出了问题之后。
您将获得
应用场景
不同场景之间的差异，在于重要文档的数量、变更频率，以及受控的严格程度。
场景 | 文档管控通常聚焦 |
工程与设计 | 图纸、模型与规格书，含版本、审批及整套交付文件 |
质量与合规 | 程序文件、作业指导书与记录，含留存与评审周期 |
运营与维护 | 手册、许可与技术文档，与所适用设备一并保存 |
商务与项目工作 | 合同、规格与交付物，含版本与分发跟踪 |
受监管环境 | 受控文档含审批历史、留存及现行有效性的证据 |
核心能力
按功能分组展示。
Capability | What it means |
Document record | Identity, owner, status, current version and location for each document |
Versioning | Revisions related to one another, with what changed between them visible |
Status and lifecycle | Draft, in review, published, superseded, retired — with what is allowed at each stage |
Review and approval | Routing, approvers, conditions, decision and date stored with the document |
Permissions | Read, edit, publish and distribute rights by role, folder and document class |
Distribution | Access granted to people rather than copies circulated, so what they see is the current version |
Comparison | See what differs between two revisions without opening both side by side |
Classification and metadata | Class, tags and custom fields used to find and filter documents |
Full-text search | Search across content, with filters for class, status, owner and date |
Workflow | Review, approval and release steps configured per document class |
Retention and disposal | Retention by class, disposal decisions, and the record of what was disposed of and when |
Audit trail | Who viewed, changed, approved, published or disposed of each document, and when |
Templates and conversion | Start from a template, or bring existing documents in and assign their class |
External sharing | Controlled sharing with an expiry, rather than permanent copies in mailboxes |
Integration | Connect to the systems where documents are referenced, so links do not go stale |
部署方式选择 | Run on your own servers or in the cloud, usually decided by where the documents may be stored |
Roles and audit | Role-based access with the audit trail retained and exportable |
工作原理
Define the classes. What kinds of document exist, who owns each class, what state it must pass through and how long it is kept.
Bring them in. Existing documents are classified and versioned, so what already exists stops being an uncontrolled set of files.
Write and review. 作业依据草案执行；评审与批准随文档一并记录。
Publish. The approved revision becomes the current version, and access follows the document rather than a copy.
Use the current one. Readers see the version in force, and what changed is visible when they need to know.
Retire and dispose. Superseded versions are retained per policy, and disposal is decided and recorded.
边界与它不决定的事
它负责存储与管控，不负责撰写。The engineering, the drafting and the authorship happen elsewhere. What this application governs is the version, the permission and the record.
Approval is not advice. 应用负责流转与记录决策；谁有权批准什么由组织设定，并始终是组织层面的决定。
It does not claim to prevent every mistake. It makes the current version unambiguous and the history complete, which is what most document errors actually come down to.
Where it runs. On your own servers or in the cloud, decided by where documents may be stored and who may reach them.
What is local. 留存期限、存档义务与访问权限因辖区和行业而异，由现场自身政策设定。