Document Lifecycle Management (DLM) is the process of handing a document, from the time it is conceived as an idea, to the point of its physical or electronic generation, maintaining its replicas as saperate versions throughout the process as it goes under various iterations; and finally when the document is declared dead.
The entire process revolves around placing and moving these document on storage devices as it is generated, replicated, electronically distributed, protected, archived, and ultimately retired.
DLM couples the process of storing, indexing, archiving, managing searching and retrieval services. To do this, DLM is composed of an interconnected set of processes, storage components, and data and storage management applications.
Note: Going forward we would refer DLM as DMS.
DMS is not only about storage; it is about implementation of an intelligent workflow and business process management. It is as much about automating the searching and indexing, categorizing, and managing of the documents as it is about the storing and archiving of them.
Importantly, DMS is about creating policies that can fit the information flow into the business environment as part of an overall architecture. Owing to its nature, DMS is most effectively implemented using an application-specific solution approach that includes generalized management components such as policy engines, schedulers, and application-specific components like document layout, encryption policies, updation criteria, retrieval modes, document life tenure, etc.
Why do enterprises need DMS?
Today’s enterprises face the daunting challenges of managing phenomenally increasing quantities of information (read: documents) so that its value to the business is fully realized, while minimizing the cost of maintaining and managing the IT infrastructure. It has become painfully clear that critical enterprise data must be continuously available. Automated processes to manage these documents through its life cycle are becoming essential.
The lifecycle of document is divided in the following listed steps
1. Planning
2. Analysis
3. Document Design
4. Instance Design
5. Instance Distribution
6. Management
The entire process revolves around placing and moving these document on storage devices as it is generated, replicated, electronically distributed, protected, archived, and ultimately retired.
DLM couples the process of storing, indexing, archiving, managing searching and retrieval services. To do this, DLM is composed of an interconnected set of processes, storage components, and data and storage management applications.
Note: Going forward we would refer DLM as DMS.
DMS is not only about storage; it is about implementation of an intelligent workflow and business process management. It is as much about automating the searching and indexing, categorizing, and managing of the documents as it is about the storing and archiving of them.
Importantly, DMS is about creating policies that can fit the information flow into the business environment as part of an overall architecture. Owing to its nature, DMS is most effectively implemented using an application-specific solution approach that includes generalized management components such as policy engines, schedulers, and application-specific components like document layout, encryption policies, updation criteria, retrieval modes, document life tenure, etc.
Why do enterprises need DMS?
Today’s enterprises face the daunting challenges of managing phenomenally increasing quantities of information (read: documents) so that its value to the business is fully realized, while minimizing the cost of maintaining and managing the IT infrastructure. It has become painfully clear that critical enterprise data must be continuously available. Automated processes to manage these documents through its life cycle are becoming essential.
The lifecycle of document is divided in the following listed steps
1. Planning
2. Analysis
3. Document Design
4. Instance Design
5. Instance Distribution
6. Management
No comments:
Post a Comment