Document management system: Difference between revisions
Mindmatrix (talk | contribs) |
|||
Line 1: | Line 1: | ||
{{Short description|Organised collection of documents}} |
|||
{{Refimprove|date=October 2008}} |
|||
{{redirect|Digital archiving|the long-term archiving of digital media|Digital preservation}} |
|||
{{redirect|EDMS|an airport with ICAO acronym "EDMS"|Straubing Wallmühle Airport}} |
|||
{{Use dmy dates|date=February 2020}} |
|||
A '''document management system''' ('''DMS''') is usually a computerized system used to store, share, track and manage files or documents. Some systems include history tracking where a log of the various versions created and modified by different users is recorded. The term has some overlap with the concepts of [[content management system]]s. It is often viewed as a component of [[enterprise content management]] (ECM) systems and related to [[digital asset management]], [[document imaging]], [[workflow]] systems and [[records management]] systems. |
|||
==History== |
|||
A '''document management system''' (DMS) is a [[computer system]] (or set of computer programs) used to track and store [[electronic document]]s and/or [[digital image|image]]s of paper documents. The term has some overlap with the concepts of [[Content management system|Content Management Systems]] and is often viewed as a component of [[Enterprise content management|Enterprise Content Management Systems]] (ECM) and related to [[Digital asset management|Digital Asset Management]], [[Document imaging]], [[Workflow]] systems and [[Records Management]] systems. [[Contract Management]] and Contract Lifecycle Management (CLM) can be viewed as either components or implementations of ECM. |
|||
While many [[electronic document management system]]s store documents in their native file format ([[Microsoft Word]] or [[Microsoft Excel|Excel]], [[PDF]]), some web-based document management systems are beginning to store content in the form of [[HTML]]. These HTML-based document management systems can act as publishing systems or policy management systems.<ref>[http://www.policystat.com/health-systems-or-networks/ Policy Management System] {{webarchive |url=https://web.archive.org/web/20111029013250/http://www.policystat.com/health-systems-or-networks/ |date=29 October 2011 }}</ref> Content is captured either by using browser based editors or the importing and conversion of not HTML content. Storing documents as HTML enables a simpler full-text workflow as most search engines deal with HTML natively. DMS without an HTML storage format is required to extract the text from the proprietary format making the full text search workflow slightly more complicated. |
|||
Search capabilities including [[Full-text search#Boolean queries|boolean queries]], [[cluster analysis]], and [[stemming]]<ref>[http://www.policystat.com/blog/2011/11/08/making-medical-office-policies-easier-to-find-with-stemming/ Stemming: Making searching easier] {{webarchive|url=https://web.archive.org/web/20120111094547/http://www.policystat.com/blog/2011/11/08/making-medical-office-policies-easier-to-find-with-stemming/ |date=11 January 2012 }}</ref> have become critical components of DMS as users have grown used to internet searching and spend less time organizing their content. |
|||
==Components== |
|||
Document management systems commonly provide storage, versioning, metadata, security, as well as indexing and retrieval capabilities. Here is a description of these components: |
|||
{| class="wikitable" document management system (section): |
|||
==Overview== |
|||
In the broadest sense, document management systems can range from a shoebox <ref> [http://www.bbc.co.uk/dna/h2g2/A23296773 BBC -h2g2 guide] Shoebox Storage </ref> all the way to an [[Enterprise Content Management]] system. There are several common issues that are involved in managing documents, whether the system is an informal, ad-hoc, paper-based method for one person or if it is a formal, structured, computer enhanced system for many people across multiple offices. Most methods for managing documents address the following areas: |
|||
{| class="wikitable" |
|||
|- |
|- |
||
! Topic !! Description |
|||
! Location |
|||
| Where will documents be stored? Where will people need to go to access documents? Physical journeys to filing cabinets and file rooms are analogous to the onscreen navigation required to use a document management system. |
|||
|- |
|- |
||
| '''[[Metadata]]''' || [[Metadata]] is typically stored for each document. [[Metadata]] may, for example, include the date the document will be stored and the identity of the user storing it. The DMS may also extract metadata from the document automatically or prompt the user to add metadata. Some systems also use [[optical character recognition]] on scanned images, or perform text extraction on electronic documents. The resulting extracted text can be used to assist users in locating documents by identifying probable keywords or providing for full text search capability, or can be used on its own. Extracted text can also be stored as a component of metadata, stored with the document, or separately from the document as a source for searching document collections.<ref name="ParsonsEffective04">{{cite book |url=https://books.google.com/books?id=R_oRDAAAQBAJ&pg=PA234 |title=Effective Knowledge Management for Law Firms |last=Parsons |first=M. |publisher=Oxford University Press |page=234 |year=2004 |isbn=9780195169683 |access-date=19 May 2018}}</ref> |
|||
! Filing |
|||
| How will documents be filed? What methods will be used to organize or index the documents to assist in later retrieval? Document management systems will typically use a [[database]] to store filing information. |
|||
|- |
|- |
||
| '''Integration''' || Many document management systems attempt to provide document management functionality directly to other applications, so that users may retrieve existing documents directly from the document management system repository, make changes, and save the changed document back to the repository as a new version, all without leaving the application. Such integration is commonly available for a variety of software tools such as [[Workflow management system|workflow management]] and [[content management system]]s, typically through an [[application programming interface]] (API) using open standards such as [[ODMA]], [[Lightweight Directory Access Protocol|LDAP]], [[WebDAV]], and [[SOAP]] or [[Representational state transfer|RESTful]] web services.<ref name="ShivakumarEnter16">{{cite book |url=https://books.google.com/books?id=wFK9DQAAQBAJ&pg=PA93 |title=Enterprise Content and Search Management for Building Digital Platforms |last=Shivakumar |first=S.K. |publisher=John Wiley & Sons |page=93 |year=2016 |isbn=9781119206828 |access-date=19 May 2018}}</ref><ref name="FletcherWorkflow03">{{cite book |url=https://books.google.com/books?id=Z0VuXKlaLNcC&pg=PA16 |title=Workflow Management with SAP WebFlow: A Practical Manual |last1=Fletcher |first1=A.N. |last2=Brahm |first2=M. |last3=Pargmann |first3=H. |publisher=Springer Science & Business Media |pages=15–16 |year=2003 |isbn=9783540404033 |access-date=19 May 2018}}</ref> |
|||
! Retrieval |
|||
| How will documents be found? Typically, retrieval encompasses both browsing through documents and searching for specific information. |
|||
|- |
|- |
||
| '''Capture''' || Capture primarily involves accepting and processing images of paper documents from [[Image scanner|scanner]]s or [[multifunction printer]]s. [[Optical character recognition]] (OCR) software is often used, whether integrated into the hardware or as stand-alone software, in order to convert digital images into machine readable text. [[Optical mark recognition]] (OMR) software is sometimes used to extract values of check-boxes or bubbles. Capture may also involve accepting electronic documents and other computer-based files.<ref name="WebberITGov16">{{cite book |url=https://books.google.com/books?id=4OzyDAAAQBAJ&pg=SA41-PA4 |title=It Governance: Policies and Procedures |last1=Webber |first1=M. |last2=Webber |first2=L. |publisher=Wolters Kluwer |pages=41–4 |year=2016 |isbn=9781454871323 |access-date=19 May 2018}}</ref> |
|||
!Security |
|||
| How will documents be kept secure? How will unauthorized personnel be prevented from reading, modifying or destroying documents? |
|||
|- |
|- |
||
| '''Data validation''' || Data validation rules can check for document failures, missing signatures, misspelled names, and other issues, recommending real-time correction options before importing data into the DMS. Additional processing in the form of harmonization and data format changes may also be applied as part of data validation.<ref name="TrinchieriEval03">{{cite book |title=Evaluation of Integrated Document Management System (IDMS) Options for the Arizona Department of Transportation (ADOT) |last=Trinchieri |first=D. |publisher=Arizona Department of Transportation |page=158 |year=2003 |quote="The data validation rules should be embedded in the form itself, rather than accomplished in a post-processing environment. This provides the use an interactive real-time experience. Often data validation requires a database look-up. The rules should allow this database query, providing the user real-time choices based on query results."}}</ref><ref name="MorleyUnder14">{{cite book |url=https://books.google.com/books?id=bDAeCgAAQBAJ&pg=PA558 |title=Understanding Computers: Today and Tomorrow, Comprehensive |last1=Morley |first1=D. |last2=Parker |first2=C.S. |publisher=Cengage Learning |pages=558–559 |year=2014 |isbn=9781285767277 |access-date=19 May 2018}}</ref> |
|||
!Disaster Recovery |
|||
| How can documents be recovered in case of destruction from fires, floods or natural disasters? |
|||
|- |
|- |
||
| '''Indexing''' || Indexing tracks electronic documents. Indexing may be as simple as keeping track of unique document identifiers; but often it takes a more complex form, providing classification through the documents' metadata or even through word indexes extracted from the documents' contents. Indexing exists mainly to support information query and retrieval. One area of critical importance for rapid retrieval is the creation of an index [[topology]] or scheme.<ref name="MeurantInto12-1">{{cite book |url=https://books.google.com/books?id=lzGGHLDERYIC&pg=PA120 |title=Introduction to Electronic Document Management Systems |last=Meurant |first=G. |publisher=Academic Press |page=120 |year=2012 |isbn=9780323140621 |access-date=19 May 2018}}</ref> |
|||
![[Retention period]] |
|||
| How long should documents be kept, i.e. retained? As organizations grow and regulations increase, informal guidelines for keeping various types of documents give way to more formal [[Records Management]] practices. |
|||
|- |
|- |
||
| '''Storage''' || Store electronic documents. Storage of the documents often includes management of those same documents; where they are stored, for how long, migration of the documents from one storage media to another ([[hierarchical storage management]]) and eventual document destruction. |
|||
![[Archiving]] |
|||
| How can documents be preserved for future readability? |
|||
|- |
|- |
||
| '''Retrieval''' || Retrieve the electronic documents from the storage. Although the notion of retrieving a particular document is simple, retrieval in the electronic context can be quite complex and powerful. Simple retrieval of individual documents can be supported by allowing the user to specify the unique document identifier, and having the system use the basic index (or a non-indexed query on its data store) to retrieve the document.<ref name="MeurantInto12-1" /> More flexible retrieval allows the user to specify partial search terms involving the document identifier and/or parts of the expected metadata. This would typically return a list of documents which match the user's search terms. Some systems provide the capability to specify a [[Boolean expression]] containing multiple keywords or example phrases expected to exist within the documents' contents. The retrieval for this kind of query may be supported by previously built indexes,<ref name="MeurantInto12-1" /> or may perform more time-consuming searches through the documents' contents to return a list of the potentially relevant documents. ''See also [[Document retrieval]].'' |
|||
!Distribution |
|||
| How can documents be available to the people that need them? |
|||
|- |
|- |
||
| '''Distribution''' || A document ready for distribution has to be in a format that cannot be easily altered. An original master copy of the document is usually never used for distribution; rather, an electronic link to the document itself is more common. If a document is to be distributed electronically in a regulatory environment, then additional criteria must be met, including assurances of traceability and versioning, even across other systems.<ref name="SommervilleImp06">{{cite book |url=https://books.google.com/books?id=QkUqBgAAQBAJ&pg=PA130 |title=Implementing IT in Construction |last1=Sommerville |first1=J. |last2=Craig |first2=N. |publisher=Routledge |page=130 |year=2006 |isbn=9781134198986 |access-date=19 May 2018}}</ref> This approach applies to both of the systems by which the document is to be inter-exchanged, if the integrity of the document is imperative. |
|||
![[Workflow]] |
|||
| If documents need to pass from one person to another, what are the rules for how their work should flow? |
|||
|- |
|- |
||
| '''Security''' || Document security is vital in many document management applications. Compliance requirements for certain documents can be quite complex depending on the type of documents. For instance, in the [[United States of America|United States]], standards such as [[ISO 9001]] and [[ISO 13485]], as well as U.S. [[Food and Drug Administration]] regulations, dictate how the document control process should be addressed.<ref name="SkipperHowTo15">{{cite book |url=https://books.google.com/books?id=HLIDCwAAQBAJ&pg=PT10 |title=How to Establish a Document Control System for Compliance with ISO 9001:2015, ISO 13485:2016, and FDA Requirements |last=Skipper |first=S.L. |publisher=ASQ Quality Press |pages=156 |year=2015 |isbn=9780873899178 |access-date=19 May 2018}}</ref> Document management systems may have a rights management module that allows an administrator to give access to documents based on type to only certain people or groups of people. Document marking at the time of printing or PDF-creation is an essential element to preclude alteration or unintended use. |
|||
!Creation |
|||
| How are documents created? This question becomes important when multiple people need to collaborate, and the logistics of version control and authoring arise. |
|||
|- |
|- |
||
| '''[[Workflow]]''' || Workflow is a complex process, and some document management systems have either a built-in workflow module<ref name="AusterberryDigital12-1">{{cite book |url=https://books.google.com/books?id=c5ncAwAAQBAJ&pg=PT35 |title=Digital Asset Management |last=Austerberry |first=D. |publisher=CRC Press |pages=27–28 |year=2012 |isbn=9781136033629 |access-date=19 May 2018}}</ref> or can integrate with workflow management tools.<ref name="FletcherWorkflow03" /> There are different types of workflow. Usage depends on the environment to which the electronic document management system (EDMS) is applied. Manual workflow requires a user to view the document and decide whom to send it to. Rules-based workflow allows an administrator to create a rule that dictates the flow of the document through an organization: for instance, an invoice passes through an approval process and then is routed to the accounts-payable department. Dynamic rules allow for branches to be created in a workflow process. A simple example would be to enter an invoice amount and if the amount is lower than a certain set amount, it follows different routes through the organization. Advanced workflow mechanisms can manipulate content or signal external processes while these rules are in effect. |
|||
!Authentication |
|||
|- |
|||
|Is there a way to vouch for the authenticity of a document ? |
|||
| '''Collaboration''' || Collaboration should be inherent in an EDMS. In its basic form, collaborative EDMS should allow documents to be retrieved and worked on by an authorized user. Access should be blocked to other users while work is being performed on the document. Other advanced forms of collaboration act in real time, allowing multiple users to view and modify (or markup) documents at the same time. The resulting document is comprehensive, including all users additions. Collaboration within document management systems means that the various markups by each individual user during the collaboration session are recorded, allowing document history to be monitored.<ref name="AusterberryDigital12-2">{{cite book |url=https://books.google.com/books?id=c5ncAwAAQBAJ&pg=PT38 |title=Digital Asset Management |last=Austerberry |first=D. |publisher=CRC Press |page=30 |year=2012 |isbn=9781136033629 |access-date=19 May 2018}}</ref> |
|||
|- |
|||
| '''[[Version control|Versioning]]''' || Versioning is a process by which documents are checked in or out of the document management system, allowing users to retrieve previous versions and to continue work from a selected point. Versioning is useful for documents that change over time and require updating, but it may be necessary to go back to or reference a previous copy.<ref name="AusterberryDigital12-2" /> |
|||
|- |
|||
| '''Searching''' || Searching finds documents and folders using template attributes or full text search. Documents can be searched using various attributes and document content. |
|||
|- |
|||
| '''Federated search''' || This refers to the capability to extend search capabilities to draw results from multiple sources, or from multiple DMSes within an enterprise.<ref name="WhiteEnterprise12">{{cite book |url=https://books.google.com/books?id=4M46PRgJmJYC&pg=PA73 |title=Enterprise Search |last=White |first=M. |publisher=O'Reilly Media, Inc |pages=73–74 |year=2012 |isbn=9781449330408 |access-date=19 May 2018}}</ref> |
|||
|- |
|||
| '''[[Publishing]]''' || Publishing a document involves the procedures of [[proofreading]], [[Peer review|peer]] or public reviewing, authorizing, printing and approving etc. Those steps ensure [[prudence]] and logical thinking. Any careless handling may result in the inaccuracy of the document and therefore mislead or upset its users and readers. In law regulated industries, some of the procedures have to be completed as evidenced by their corresponding signatures and the date(s) on which the document was signed. Refer to the [[International Organization for Standardization|ISO]] divisions of ICS 01.140.40 and 35.240.30 for further information.<ref name=pub>{{cite web |
|||
|last = International Organization for Standardization |
|||
|title = 01.140.40: Publishing |
|||
|url = http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=40& |
|||
|access-date = 14 July 2008 |
|||
|url-status = live |
|||
|archive-url = https://web.archive.org/web/20110606045311/http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=40& |
|||
|archive-date = 6 June 2011 |
|||
}}</ref><ref name=itpub>{{cite web |
|||
|last = International Organization for Standardization |
|||
|title = 35.240.30: IT applications in information, documentation and publishing |
|||
|url = http://www.iso.org/iso/catalogue_ics_browse?ICS1=35&ICS2=240&ICS3=30& |
|||
|access-date = 14 July 2008 |
|||
|url-status = live |
|||
|archive-url = https://web.archive.org/web/20110606045331/http://www.iso.org/iso/catalogue_ics_browse?ICS1=35&ICS2=240&ICS3=30& |
|||
|archive-date = 6 June 2011 |
|||
}}</ref> |
|||
The published document should be in a format that is not easily altered without a specific knowledge or tools, and yet it is read-only or portable.<ref name=sdmv>{{cite web|last=OnSphere Corporation|title=SOP Document Management in a Validated Environments|url=http://www.avidoffice.com/docushare/dsweb/Get/Document-9101/Standard%20Operation%20Procedure%20(SOP)%20Document%20Management%20in%20Validated%20Environments.pdf|access-date=25 April 2011|archive-url=https://web.archive.org/web/20110904190514/http://www.avidoffice.com/docushare/dsweb/Get/Document-9101/Standard%20Operation%20Procedure%20%28SOP%29%20Document%20Management%20in%20Validated%20Environments.pdf|archive-date=4 September 2011|url-status=dead}}</ref> |
|||
|- |
|||
| '''Hard copy reproduction''' || Document/image reproduction is often necessary within a document management system, and its supported output devices and reproduction capabilities should be considered.<ref name="MeurantInto12-2">{{cite book |url=https://books.google.com/books?id=lzGGHLDERYIC&pg=PA16 |title=Introduction to Electronic Document Management Systems |last=Meurant |first=G. |publisher=Academic Press |page=16 |year=2012 |isbn=9780323140621 |access-date=19 May 2018}}</ref> |
|||
|} |
|} |
||
== |
==Standardization== |
||
Many industry associations publish their own lists of particular document control standards that are used in their particular field. Following is a list of some of the relevant ISO documents. Divisions ICS 01.140.10 and 01.140.20.<ref name=wt>{{cite web |
|||
|last = International Organization for Standardization |
|||
|title = 01.140.10: Writing and transliteration |
|||
|url = http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=10& |
|||
|access-date = 14 July 2008 |
|||
|url-status = live |
|||
|archive-url = https://web.archive.org/web/20090707023803/http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=10& |
|||
|archive-date = 7 July 2009 |
|||
}}</ref><ref name=is>{{cite web |
|||
|last = International Organization for Standardization |
|||
|title = 01.140.20: Information sciences |
|||
|url = http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=20& |
|||
|access-date = 14 July 2008 |
|||
|url-status = live |
|||
|archive-url = https://web.archive.org/web/20081205165925/http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=20& |
|||
|archive-date = 5 December 2008 |
|||
}}</ref> The ISO has also published a series of standards regarding the [[technical documentation]], covered by the division of 01.110.<ref name=tpd>{{cite web |
|||
|last = International Organization for Standardization |
|||
|title = 01.110: Technical product documentation |
|||
|url = http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=110& |
|||
|access-date = 15 July 2008 |
|||
|url-status = live |
|||
|archive-url = https://web.archive.org/web/20110606045413/http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=110& |
|||
|archive-date = 6 June 2011 |
|||
}}</ref> |
|||
* [[ISO 2709]] Information and documentation – Format for information exchange |
|||
* [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=52142 ISO 15836] Information and documentation – The [[Dublin Core]] metadata element set |
|||
* [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=31908 ISO 15489] Information and documentation – Records management |
|||
* [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=57832 ISO 21127] Information and documentation – A reference [[Ontology (information science)|ontology]] for the interchange of cultural heritage information |
|||
* [[ISO 23950]] Information and documentation – Information retrieval (Z39.50) – Application service definition and protocol specification |
|||
* [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45935 ISO 10244] Document management – Business process baselining and analysis |
|||
* [[ISO 32000]] Document management – Portable document format |
|||
* [[ISO/IEC 27001]] Specification for an information security management system |
|||
==Document control== |
|||
Beginning in the 1980s, a number of vendors began developing systems to manage paper-based documents. These systems managed paper documents, which included not only printed and published documents, but also photos, prints, etc. |
|||
[[Regulatory economics|Government regulations]] typically require that companies working in certain industries control their documents. A [[Document Controller]] is responsible to control these documents strictly. These industries include accounting (for example: 8th [[Directive (European Union)|EU Directive]], [[Sarbanes–Oxley Act]]), food safety (for example the [[Food Safety Modernization Act]] in the US), ISO (mentioned above), medical device manufacturing ([[Food and Drug Administration|FDA]]), manufacture of blood, human cells, and tissue products (FDA), healthcare (''[[JCAHO]]''), and information technology (''[[ITIL]]'').<ref> |
|||
{{cite web |
|||
|title = Code of Federal Regulations Title 21, Part 1271 |
|||
|url = http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/CFRSearch.cfm?CFRPart=1271&showFR=1 |
|||
|publisher = Food and Drug Administration |
|||
|access-date = 31 January 2012 |
|||
|url-status = live |
|||
|archive-url = https://web.archive.org/web/20111010114628/http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/CFRSearch.cfm?CFRPart=1271&showFR=1 |
|||
|archive-date = 10 October 2011 |
|||
}} |
|||
</ref> |
|||
Some industries work under stricter document control requirements due to the type of information they retain for privacy, warranty, or other highly regulated purposes. Examples include [[protected health information]] (PHI) as required by [[HIPAA]] or construction project documents required for warranty periods. An information systems strategy plan (ISSP) can shape organisational information systems over medium to long-term periods.<ref> |
|||
{{cite book |
|||
|last1 = Wiggins |
|||
|first1 = Bob |
|||
|title = Effective Document Management: Unlocking Corporate Knowledge |
|||
|year = 2000 |
|||
|url = https://books.google.com/books?id=JnDwAAAAMAAJ |
|||
|edition = 2 |
|||
|publisher = Gower |
|||
|publication-date = 2000 |
|||
|page = 25 |
|||
|isbn = 9780566081484 |
|||
|access-date = 2016-04-09 |
|||
|quote = At the organisational level an information systems strategy plan (ISSP) is a way to determine in general terms what information systems an organisation should have in place over the medium to long term (typically around three to five years [...]). |
|||
|url-status = live |
|||
|archive-url = https://web.archive.org/web/20180113184109/https://books.google.com/books?id=JnDwAAAAMAAJ |
|||
|archive-date = 13 January 2018 |
|||
}} |
|||
</ref> |
|||
Documents stored in a document management system—such as procedures, work instructions, and policy statements—provide evidence of documents under control. Failing to comply can cause fines, the loss of business, or damage to a business's reputation. |
|||
Later, a second system was developed, to manage electronic documents, i.e., all those documents, or files, created on computers, and often stored on local user file systems. The earliest electronic document management (EDM) systems were either developed to manage proprietary file types, or a limited number of file formats. Many of these systems were later referred to as [[document imaging]] systems, because the main capabilities were capture, storage, indexing and retrieval of image file formats. These systems enabled an organization to capture faxes and forms, save copies of the documents as images, and store the image files in the repository for security and quick retrieval (retrieval was possible because the system handled the extraction of the text from the document as it was captured, and the text indexer provided text retrieval capabilities). |
|||
Document control includes:<ref>{{cite web|url=https://www.isotracker.com/blog/what-is-document-control/|title=What is Document Control?|accessdate=9 November 2023|website=isoTracker}}</ref> |
|||
EDM systems evolved to where the system was able to manage any type of file format that could be stored on the network. The applications grew to encompass electronic documents, collaboration tools, security, and auditing capabilities. |
|||
* reviewing and approving documents prior to release |
|||
* ensuring changes and revisions are clearly identified |
|||
* ensuring that relevant versions of applicable documents are available at their "points of use" |
|||
* ensuring that documents remain legible and identifiable |
|||
* ensuring that external documents (such as customer-supplied documents or supplier manuals) are identified and controlled |
|||
* preventing “unintended” use of obsolete documents |
|||
These document control requirements form part of an organisation's [[compliance cost]]s alongside related functions such as a [[data protection officer]] and [[internal audit]]. |
|||
==Components== |
|||
Document management systems commonly provide storage, versioning, metadata, security, as well as indexing and retrieval capabilities. Here is a description of these components: |
|||
==Integrated DM== |
|||
;Metadata |
|||
'''Integrated document management''' comprises the technologies, tools, and methods used to capture, manage, store, preserve, deliver and dispose of 'documents' across an enterprise. In this context 'documents' are any of a myriad of information assets including images, office documents, graphics, and drawings as well as the new electronic objects such as Web pages, email, instant messages, and video. |
|||
:[[Metadata]] is typically stored for each document. Metadata may, for example, include the date the document was stored and the identity of the user storing it. The DMS may also extract metadata from the document automatically or prompt the user to add metadata. Some systems also use [[optical character recognition]] on scanned images, or perform text extraction on electronic documents. The resulting extracted text can be used to assist users in locating documents by identifying probable keywords or providing for full text search capability, or can be used on its own. Extracted text can also be stored as a component of metadata, stored with the image, or separately as a source for searching document collections. |
|||
;Integration |
|||
:Many document management systems attempt to integrate document management directly into other applications, so that users may retrieve existing documents directly from the document management system repository, make changes, and save the changed document back to the repository as a new version, all without leaving the application. Such integration is commonly available for [[office suite]]s and [[e-mail]] or collaboration/groupware software. Integration often uses open standards such as [[ODMA]], [[Lightweight Directory Access Protocol|LDAP]], [[WebDAV]] and [[SOAP]] to allow integration with other software and compliance with internal controls.{{Fact|date=February 2007}} |
|||
;Capture |
|||
:[[digital image|Image]]s of paper documents using [[scanner]]s or [[multifunction printer]]s. [[Optical Character Recognition]] (OCR) software is often used, whether integrated into the hardware or as stand-alone software, in order to convert digital images into machine readable text. |
|||
;Indexing |
|||
:Track [[electronic document]]s. Indexing may be as simple as keeping track of unique document identifiers; but often it takes a more complex form, providing classification through the documents' metadata or even through word indexes extracted from the documents' contents. Indexing exists mainly to support retrieval. One area of critical importance for rapid retrieval is the creation of an index [[topology]]. |
|||
;Storage |
|||
:Store [[electronic document]]s. Storage of the documents often includes management of those same documents; where they are stored, for how long, migration of the documents from one storage media to another ([[Hierarchical storage management]]) and eventual document destruction. |
|||
;Retrieval |
|||
:Retrieve the electronic documents from the storage. Although the notion of retrieving a particular document is simple, retrieval in the electronic context can be quite complex and powerful. Simple retrieval of individual documents can be supported by allowing the user to specify the unique document identifier, and having the system use the basic index (or a non-indexed query on its data store) to retrieve the document. More flexible retrieval allows the user to specify partial search terms involving the document identifier and/or parts of the expected metadata. This would typically return a list of documents which match the user's search terms. Some systems provide the capability to specify a [[Boolean expression]] containing multiple keywords or example phrases expected to exist within the documents' contents. The retrieval for this kind of query may be supported by previously-built indexes, or may perform more time-consuming searches through the documents' contents to return a list of the potentially relevant documents. See also [[Document retrieval]]. |
|||
==Document management software== |
|||
;Distribution |
|||
Paper documents have long been used in storing [[information]]. However, paper can be costly and, if used excessively, wasteful. Document management software is not simply a tool but it lets a user manage access, track and edit information stored. Document management software is an [[Electronics|electronic]] cabinet that can be used to organize all paper and digital files.<ref>{{cite web |url=http://www.businessnewsdaily.com/8026-choosing-a-document-management-system.html |title=Document Management Systems - A Buyer's Guide |access-date=2017-01-10 |url-status=live |archive-url=https://web.archive.org/web/20170110162200/http://www.businessnewsdaily.com/8026-choosing-a-document-management-system.html |archive-date=10 January 2017}}</ref> The software helps the [[businesses]] to combine paper to digital files and store it into a single hub after it is scanned and [[digital formats]] get imported.<ref>Chaouni, Mamoun (5 February 2015). [http://www.business2community.com/tech-gadgets/7-powerful-advantages-using-document-management-system-01148648#QByJYdR4YItDZzq1.97 "7 Powerful Advantages of Using a Document Management System"] {{webarchive|url=https://web.archive.org/web/20170110162348/http://www.business2community.com/tech-gadgets/7-powerful-advantages-using-document-management-system-01148648 |date=10 January 2017 }}</ref> One of the most important benefits of [[digital document]] management is a “fail-safe” environment for safeguarding all [[documents]] and data.<ref>{{Cite web|title=Benefits of a Document Management System and 9 Things to Look For|url=https://www.ashconversions.com/blog/document-management/benefits-document-management-system-9-things-look/|last=ash-conversions|date=2020-02-13|website=Ash Conversions International|language=en-GB|access-date=2020-05-07}}</ref> In the heavy construction industry specifically, document management software allows team members to securely view and upload documents for projects they are assigned to from anywhere and at any time to help streamline day-to-day operations.<ref name="HCSS-document-management">{{cite web |title=Document Management Software for Construction |date=15 December 2021 |url=https://www.hcss.com/products/construction-document-software/ |website=HCSS |access-date=7 June 2022}}</ref> |
|||
:A published document for distribution has to be in a format that can not be easily altered. As a common practice in law regulated industries, an original master copy of the document is usually never used for distribution other than [[archiving]]. If a document is to be distributed electronically in a regulatory environment, then the equipment tasking the job has to be quality endorsed AND validated. Similarly quality endorsed electronic distribution carriers have to be used. This approach applies to both of the systems by which the document is to be inter-exchanged, if the integrity of the document is highly in demand. |
|||
;Security |
|||
:Document security is vital in many document management applications. Compliance requirements for certain documents can be quite complex depending on the type of documents. For instance the [[Health Insurance Portability and Accountability Act]] (HIPAA) requirements dictate that medical documents have certain security requirements. Some document management systems have a rights management module that allows an administrator to give access to documents based on type to only certain people or groups of people. |
|||
;[[Workflow]] |
|||
:Workflow is a complex problem and some document management systems have a built in workflow module. There are different types of workflow. Usage depends on the environment the Electronic Document Management System (EDMS) is applied to. Manual workflow requires a user to view the document and decide who to send it to. Rules-based workflow allows an administrator to create a rule that dictates the flow of the document through an organization: for instance, an invoice passes through an approval process and then is routed to the accounts payable department. Dynamic rules allow for branches to be created in a workflow process. A simple example would be to enter an invoice amount and if the amount is lower than a certain set amount, it follows different routes through the organization. |
|||
;Collaboration |
|||
:Collaboration should be inherent in an EDMS. Documents should be capable of being retrieved by an authorized user and worked on. Access should be blocked to other users while work is being performed on the document. |
|||
;[[Versioning]] |
|||
:Versioning is a process by which documents are checked in or out of the document management system, allowing users to retrieve previous versions and to continue work from a selected point. Versioning is useful for documents that change over time and require updating, but it may be necessary to go back to a previous copy. |
|||
;[[Publishing]] |
|||
:Publishing a document is sometime tedious and involves the procedures of [[proofreading]], [[Peer review|peer]] or public reviewing, authorizing, printing and approving etc. Those steps endure [[prudence]] and logic thinking. Any careless handling may result in the inaccuracy of the document and therefore misleading or upset its users and readers. In law regulated industries, some of the procedures have to be completed with the evidences of their corresponding signatures and the dates on which the document is signed. Refer to the [[International Organization for Standardization|ISO]] divisions of ICS 01.140.40 and 35.240.30 for further information <ref name=pub>{{cite web |
|||
| last = [[International Organization for Standardization]] |
|||
| first = |
|||
| authorlink = |
|||
| coauthors = |
|||
| title = 01.140.40: Publishing |
|||
| work = |
|||
| publisher = |
|||
| date = |
|||
| url = http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=40& |
|||
| format = |
|||
| doi = |
|||
| accessdate = 14 July |
|||
| accessyear = 2008 }}</ref><sup>,</sup> <ref name=itpub>{{cite web |
|||
| last = [[International Organization for Standardization]] |
|||
| first = |
|||
| authorlink = |
|||
| coauthors = |
|||
| title = 35.240.30: IT applications in information, documentation and publishing |
|||
| work = |
|||
| publisher = |
|||
| date = |
|||
| url = http://www.iso.org/iso/catalogue_ics_browse?ICS1=35&ICS2=240&ICS3=30& |
|||
| format = |
|||
| doi = |
|||
| accessdate = 14 July |
|||
| accessyear = 2008 }}</ref>. |
|||
== Standardization == |
|||
Currently, the availability of the standards is perhaps scattered all over industries and it is not hard to adopt some of those for each business interest. The following is the list of some of the relevant [[International Organization for Standardization|ISO]] documents. Divisions ICS 01.140.10 and 01.140.20 <ref name=wt>{{cite web |
|||
| last = [[International Organization for Standardization]] |
|||
| first = |
|||
| authorlink = |
|||
| coauthors = |
|||
| title = 01.140.10: Writing and transliteration |
|||
| work = |
|||
| publisher = |
|||
| date = |
|||
| url = http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=10& |
|||
| format = |
|||
| doi = |
|||
| accessdate = 14 July |
|||
| accessyear = 2008 }}</ref><sup>,</sup> |
|||
<ref name=is>{{cite web |
|||
| last = [[International Organization for Standardization]] |
|||
| first = |
|||
| authorlink = |
|||
| coauthors = |
|||
| title = 01.140.20: Information sciences |
|||
| work = |
|||
| publisher = |
|||
| date = |
|||
| url = http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=20& |
|||
| format = |
|||
| doi = |
|||
| accessdate = 14 July |
|||
| accessyear = 2008 }}</ref>. The ISO has also published a series of standards regarding the technical documentation, covered by the division of 01.110 <ref name=tpd>{{cite web |
|||
| last = [[International Organization for Standardization]] |
|||
| first = |
|||
| authorlink = |
|||
| coauthors = |
|||
| title = 01.110: Technical product documentation |
|||
| work = |
|||
| publisher = |
|||
| date = |
|||
| url = http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=110& |
|||
| format = |
|||
| doi = |
|||
| accessdate = 15 July |
|||
| accessyear = 2008 }}</ref>. |
|||
* ISO 2709:1996 Information and documentation -- Format for information exchange |
|||
* ISO 15836:2003 Information and documentation - The Dublin Core metadata element set |
|||
* ISO 21127:2006 Information and documentation -- A reference ontology for the interchange of cultural heritage information |
|||
* ISO 23950:1998 Information and documentation -- Information retrieval (Z39.50) -- Application service definition and protocol specification. |
|||
* ISO/CD 10244 Document management -- Business process/workflow baselining and analysis associated with EDMS technologies |
|||
{{Expand|section|date=October 2008}} |
|||
==See also== |
==See also== |
||
{{Div col|colwidth=22em}} |
|||
* [[Business process management]] |
|||
* [[Construction collaboration technology]] |
|||
*[[Data proliferation]] |
|||
* [[Customer communications management]] |
|||
*[[Information repository]] |
|||
* [[Data proliferation]] |
|||
*[[Enterprise Content Management]] |
|||
*[[Document |
* [[Document automation]] |
||
* [[Documentation]] |
|||
* [[Database management system]] |
|||
* [[ |
* [[Enterprise content management]] |
||
* [[ |
* [[Information repository]] |
||
*[[Records Management]] |
|||
*[[Workflow]] |
|||
* [[Publishing]] |
|||
* [[Library science]] |
|||
* [[Information science]] |
* [[Information science]] |
||
* [[Knowledge base]] |
|||
* [[Knowledge management]] |
|||
==Document management systems== |
|||
* [[Library science]] |
|||
<!-- Do not add a link to your company's website or product here - it will be deleted. Only links to articles in Wikipedia should be listed --> |
|||
* [[Product data management]] |
|||
{{col-begin}} |
|||
* [[Revision control]] |
|||
{{col-2}} |
|||
* [[Snippet management]] |
|||
*[[ViciDocs - www.vicidocs.com]] |
|||
*[[ |
* [[Taxonomy (general)]] |
||
* [[Technical data management system]] |
|||
*[[Cognidox]] |
|||
* [[Technical documentation]] |
|||
*[[ColumbiaSoft]] |
|||
{{Div col end}} |
|||
*[[IBM |Content Manager]] |
|||
*[[Computhink]]'s [[ViewWise]] |
|||
*[[DocPoint]] |
|||
*[[Documentum]] |
|||
*[[Filehold]] |
|||
*[[FileNet]] |
|||
*[[Hummingbird Ltd.|Hummingbird DM]] |
|||
*[[Hyland Software]]'s OnBase |
|||
*ImageNow by [[Perceptive Software]] |
|||
*[[IBM |ImagePlus]] |
|||
*[[Infonic]] Document Manager UK |
|||
*[[Intact]] |
|||
*[[Interwoven]]'s Worksite |
|||
*[[Invu]] |
|||
*[[ISIS Papyrus]] |
|||
*[[KnowledgeTree]] |
|||
*[[Laserfiche]] |
|||
{{col-break}} |
|||
*[[Livelink]] |
|||
*[[Main//Pyrus DMS]] |
|||
*[[Nuxeo]] |
|||
*[[O3spaces|O³Spaces]] |
|||
*[[Objective Corporation|Objective]] |
|||
*[[OpenKM]] |
|||
*Oracle's [[Stellent]] |
|||
*[[Questys Solutions]] |
|||
*[[Redmap]] |
|||
*[[Report2Web]] |
|||
*[[Saperion]] |
|||
*[[SharePoint]] |
|||
*[[Teamwork (software)|Teamwork]] |
|||
*[[TRIM Context]] |
|||
*[[Version One Ltd]] |
|||
*[[Xerox Docushare]] |
|||
{{col-end}} |
|||
==References== |
==References== |
||
{{}} |
{{reflist}} |
||
==External links== |
==External links== |
||
<!--========================({{No More Links}})============================ |
|||
<!-- Do not add a link to your company's website here - it will be deleted. Only websites about document managing in general that do not advertise a particular product or company should be listed --> |
|||
| PLEASE BE CAUTIOUS IN ADDING MORE LINKS TO THIS ARTICLE. WIKIPEDIA | |
|||
* {{cite paper |url=http://www.cabinetng.com/media/Paperless%20Office_Troy%20State.pdf |title=The Paperless Office: Accepting Digitized data |format=PDF |publisher=Troy State University |author=Miles L. Mathieu, Ernest A. Capozzoli |date=2002}} |
|||
| IS NOT A COLLECTION OF LINKS NOR SHOULD IT BE USED FOR ADVERTISING. | |
|||
* {{cite paper |url=http://www.document-strategy.com/excerpts.html|title=Excerpts from ''Designing a Document Strategy''|format=HTML |publisher=Craine Communications Group|author=Kevin Craine}} |
|||
| | |
|||
* [http://code.google.com/p/kognite/wiki/DocumentManagementSoftware A list of personal document management software] |
|||
| Excessive or inappropriate links WILL BE DELETED. | |
|||
{{WebManTools}} |
|||
| See [[Wikipedia:External links]] & [[Wikipedia:Spam]] for details. | |
|||
[[Category:Content management systems]] |
|||
| | |
|||
[[Category:Information technology management]] |
|||
| If there are already plentiful links, please propose additions or | |
|||
[[Category:Document Management System]] |
|||
| replacements on this article's discussion page, or submit your link | |
|||
| to the relevant category at the Open Directory Project (dmoz.org) | |
|||
| and link back to that category using the {{dmoz}} template. | |
|||
=======================({{No More Links}})=============================--> |
|||
{{Commons category|Document management systems}} |
|||
<!-- Do not add a link to your company's website here - it will be deleted. Only websites about document managing in general that do not advertise a particular product or company should be listed --> |
|||
{{Authority control}} |
|||
[[Category:Document management systems| ]] |
|||
[[af:Dokumentbestuurstelsel]] |
|||
[[Category:Records management technology]] |
|||
[[cs:Správa dokumentů]] |
|||
[[de:Dokumentenmanagement]] |
|||
[[es:Software de gestión documental]] |
|||
[[fa:سامانه مدیریت اسناد]] |
|||
[[fr:Gestion électronique des documents]] |
|||
[[it:Document Management System]] |
|||
[[lt:Dokumentų valdymo sistema]] |
|||
[[nl:Documentmanagementsysteem]] |
|||
[[ja:文書管理システム]] |
|||
[[pl:System zarządzania dokumentami]] |
|||
[[pt:Gerenciamento eletrônico de documentos]] |
|||
[[ru:Система управления документами]] |
Latest revision as of 14:26, 12 December 2024
A document management system (DMS) is usually a computerized system used to store, share, track and manage files or documents. Some systems include history tracking where a log of the various versions created and modified by different users is recorded. The term has some overlap with the concepts of content management systems. It is often viewed as a component of enterprise content management (ECM) systems and related to digital asset management, document imaging, workflow systems and records management systems.
History
[edit]While many electronic document management systems store documents in their native file format (Microsoft Word or Excel, PDF), some web-based document management systems are beginning to store content in the form of HTML. These HTML-based document management systems can act as publishing systems or policy management systems.[1] Content is captured either by using browser based editors or the importing and conversion of not HTML content. Storing documents as HTML enables a simpler full-text workflow as most search engines deal with HTML natively. DMS without an HTML storage format is required to extract the text from the proprietary format making the full text search workflow slightly more complicated.
Search capabilities including boolean queries, cluster analysis, and stemming[2] have become critical components of DMS as users have grown used to internet searching and spend less time organizing their content.
Components
[edit]Document management systems commonly provide storage, versioning, metadata, security, as well as indexing and retrieval capabilities. Here is a description of these components:
Topic | Description |
---|---|
Metadata | Metadata is typically stored for each document. Metadata may, for example, include the date the document will be stored and the identity of the user storing it. The DMS may also extract metadata from the document automatically or prompt the user to add metadata. Some systems also use optical character recognition on scanned images, or perform text extraction on electronic documents. The resulting extracted text can be used to assist users in locating documents by identifying probable keywords or providing for full text search capability, or can be used on its own. Extracted text can also be stored as a component of metadata, stored with the document, or separately from the document as a source for searching document collections.[3] |
Integration | Many document management systems attempt to provide document management functionality directly to other applications, so that users may retrieve existing documents directly from the document management system repository, make changes, and save the changed document back to the repository as a new version, all without leaving the application. Such integration is commonly available for a variety of software tools such as workflow management and content management systems, typically through an application programming interface (API) using open standards such as ODMA, LDAP, WebDAV, and SOAP or RESTful web services.[4][5] |
Capture | Capture primarily involves accepting and processing images of paper documents from scanners or multifunction printers. Optical character recognition (OCR) software is often used, whether integrated into the hardware or as stand-alone software, in order to convert digital images into machine readable text. Optical mark recognition (OMR) software is sometimes used to extract values of check-boxes or bubbles. Capture may also involve accepting electronic documents and other computer-based files.[6] |
Data validation | Data validation rules can check for document failures, missing signatures, misspelled names, and other issues, recommending real-time correction options before importing data into the DMS. Additional processing in the form of harmonization and data format changes may also be applied as part of data validation.[7][8] |
Indexing | Indexing tracks electronic documents. Indexing may be as simple as keeping track of unique document identifiers; but often it takes a more complex form, providing classification through the documents' metadata or even through word indexes extracted from the documents' contents. Indexing exists mainly to support information query and retrieval. One area of critical importance for rapid retrieval is the creation of an index topology or scheme.[9] |
Storage | Store electronic documents. Storage of the documents often includes management of those same documents; where they are stored, for how long, migration of the documents from one storage media to another (hierarchical storage management) and eventual document destruction. |
Retrieval | Retrieve the electronic documents from the storage. Although the notion of retrieving a particular document is simple, retrieval in the electronic context can be quite complex and powerful. Simple retrieval of individual documents can be supported by allowing the user to specify the unique document identifier, and having the system use the basic index (or a non-indexed query on its data store) to retrieve the document.[9] More flexible retrieval allows the user to specify partial search terms involving the document identifier and/or parts of the expected metadata. This would typically return a list of documents which match the user's search terms. Some systems provide the capability to specify a Boolean expression containing multiple keywords or example phrases expected to exist within the documents' contents. The retrieval for this kind of query may be supported by previously built indexes,[9] or may perform more time-consuming searches through the documents' contents to return a list of the potentially relevant documents. See also Document retrieval. |
Distribution | A document ready for distribution has to be in a format that cannot be easily altered. An original master copy of the document is usually never used for distribution; rather, an electronic link to the document itself is more common. If a document is to be distributed electronically in a regulatory environment, then additional criteria must be met, including assurances of traceability and versioning, even across other systems.[10] This approach applies to both of the systems by which the document is to be inter-exchanged, if the integrity of the document is imperative. |
Security | Document security is vital in many document management applications. Compliance requirements for certain documents can be quite complex depending on the type of documents. For instance, in the United States, standards such as ISO 9001 and ISO 13485, as well as U.S. Food and Drug Administration regulations, dictate how the document control process should be addressed.[11] Document management systems may have a rights management module that allows an administrator to give access to documents based on type to only certain people or groups of people. Document marking at the time of printing or PDF-creation is an essential element to preclude alteration or unintended use. |
Workflow | Workflow is a complex process, and some document management systems have either a built-in workflow module[12] or can integrate with workflow management tools.[5] There are different types of workflow. Usage depends on the environment to which the electronic document management system (EDMS) is applied. Manual workflow requires a user to view the document and decide whom to send it to. Rules-based workflow allows an administrator to create a rule that dictates the flow of the document through an organization: for instance, an invoice passes through an approval process and then is routed to the accounts-payable department. Dynamic rules allow for branches to be created in a workflow process. A simple example would be to enter an invoice amount and if the amount is lower than a certain set amount, it follows different routes through the organization. Advanced workflow mechanisms can manipulate content or signal external processes while these rules are in effect. |
Collaboration | Collaboration should be inherent in an EDMS. In its basic form, collaborative EDMS should allow documents to be retrieved and worked on by an authorized user. Access should be blocked to other users while work is being performed on the document. Other advanced forms of collaboration act in real time, allowing multiple users to view and modify (or markup) documents at the same time. The resulting document is comprehensive, including all users additions. Collaboration within document management systems means that the various markups by each individual user during the collaboration session are recorded, allowing document history to be monitored.[13] |
Versioning | Versioning is a process by which documents are checked in or out of the document management system, allowing users to retrieve previous versions and to continue work from a selected point. Versioning is useful for documents that change over time and require updating, but it may be necessary to go back to or reference a previous copy.[13] |
Searching | Searching finds documents and folders using template attributes or full text search. Documents can be searched using various attributes and document content. |
Federated search | This refers to the capability to extend search capabilities to draw results from multiple sources, or from multiple DMSes within an enterprise.[14] |
Publishing | Publishing a document involves the procedures of proofreading, peer or public reviewing, authorizing, printing and approving etc. Those steps ensure prudence and logical thinking. Any careless handling may result in the inaccuracy of the document and therefore mislead or upset its users and readers. In law regulated industries, some of the procedures have to be completed as evidenced by their corresponding signatures and the date(s) on which the document was signed. Refer to the ISO divisions of ICS 01.140.40 and 35.240.30 for further information.[15][16]
The published document should be in a format that is not easily altered without a specific knowledge or tools, and yet it is read-only or portable.[17] |
Hard copy reproduction | Document/image reproduction is often necessary within a document management system, and its supported output devices and reproduction capabilities should be considered.[18] |
Standardization
[edit]Many industry associations publish their own lists of particular document control standards that are used in their particular field. Following is a list of some of the relevant ISO documents. Divisions ICS 01.140.10 and 01.140.20.[19][20] The ISO has also published a series of standards regarding the technical documentation, covered by the division of 01.110.[21]
- ISO 2709 Information and documentation – Format for information exchange
- ISO 15836 Information and documentation – The Dublin Core metadata element set
- ISO 15489 Information and documentation – Records management
- ISO 21127 Information and documentation – A reference ontology for the interchange of cultural heritage information
- ISO 23950 Information and documentation – Information retrieval (Z39.50) – Application service definition and protocol specification
- ISO 10244 Document management – Business process baselining and analysis
- ISO 32000 Document management – Portable document format
- ISO/IEC 27001 Specification for an information security management system
Document control
[edit]Government regulations typically require that companies working in certain industries control their documents. A Document Controller is responsible to control these documents strictly. These industries include accounting (for example: 8th EU Directive, Sarbanes–Oxley Act), food safety (for example the Food Safety Modernization Act in the US), ISO (mentioned above), medical device manufacturing (FDA), manufacture of blood, human cells, and tissue products (FDA), healthcare (JCAHO), and information technology (ITIL).[22] Some industries work under stricter document control requirements due to the type of information they retain for privacy, warranty, or other highly regulated purposes. Examples include protected health information (PHI) as required by HIPAA or construction project documents required for warranty periods. An information systems strategy plan (ISSP) can shape organisational information systems over medium to long-term periods.[23]
Documents stored in a document management system—such as procedures, work instructions, and policy statements—provide evidence of documents under control. Failing to comply can cause fines, the loss of business, or damage to a business's reputation.
Document control includes:[24]
- reviewing and approving documents prior to release
- ensuring changes and revisions are clearly identified
- ensuring that relevant versions of applicable documents are available at their "points of use"
- ensuring that documents remain legible and identifiable
- ensuring that external documents (such as customer-supplied documents or supplier manuals) are identified and controlled
- preventing “unintended” use of obsolete documents
These document control requirements form part of an organisation's compliance costs alongside related functions such as a data protection officer and internal audit.
Integrated DM
[edit]Integrated document management comprises the technologies, tools, and methods used to capture, manage, store, preserve, deliver and dispose of 'documents' across an enterprise. In this context 'documents' are any of a myriad of information assets including images, office documents, graphics, and drawings as well as the new electronic objects such as Web pages, email, instant messages, and video.
Document management software
[edit]Paper documents have long been used in storing information. However, paper can be costly and, if used excessively, wasteful. Document management software is not simply a tool but it lets a user manage access, track and edit information stored. Document management software is an electronic cabinet that can be used to organize all paper and digital files.[25] The software helps the businesses to combine paper to digital files and store it into a single hub after it is scanned and digital formats get imported.[26] One of the most important benefits of digital document management is a “fail-safe” environment for safeguarding all documents and data.[27] In the heavy construction industry specifically, document management software allows team members to securely view and upload documents for projects they are assigned to from anywhere and at any time to help streamline day-to-day operations.[28]
See also
[edit]- Construction collaboration technology
- Customer communications management
- Data proliferation
- Document automation
- Documentation
- Enterprise content management
- Information repository
- Information science
- Knowledge base
- Knowledge management
- Library science
- Product data management
- Revision control
- Snippet management
- Taxonomy (general)
- Technical data management system
- Technical documentation
References
[edit]- ^ Policy Management System Archived 29 October 2011 at the Wayback Machine
- ^ Stemming: Making searching easier Archived 11 January 2012 at the Wayback Machine
- ^ Parsons, M. (2004). Effective Knowledge Management for Law Firms. Oxford University Press. p. 234. ISBN 9780195169683. Retrieved 19 May 2018.
- ^ Shivakumar, S.K. (2016). Enterprise Content and Search Management for Building Digital Platforms. John Wiley & Sons. p. 93. ISBN 9781119206828. Retrieved 19 May 2018.
- ^ a b Fletcher, A.N.; Brahm, M.; Pargmann, H. (2003). Workflow Management with SAP WebFlow: A Practical Manual. Springer Science & Business Media. pp. 15–16. ISBN 9783540404033. Retrieved 19 May 2018.
- ^ Webber, M.; Webber, L. (2016). It Governance: Policies and Procedures. Wolters Kluwer. pp. 41–4. ISBN 9781454871323. Retrieved 19 May 2018.
- ^ Trinchieri, D. (2003). Evaluation of Integrated Document Management System (IDMS) Options for the Arizona Department of Transportation (ADOT). Arizona Department of Transportation. p. 158.
The data validation rules should be embedded in the form itself, rather than accomplished in a post-processing environment. This provides the use an interactive real-time experience. Often data validation requires a database look-up. The rules should allow this database query, providing the user real-time choices based on query results.
- ^ Morley, D.; Parker, C.S. (2014). Understanding Computers: Today and Tomorrow, Comprehensive. Cengage Learning. pp. 558–559. ISBN 9781285767277. Retrieved 19 May 2018.
- ^ a b c Meurant, G. (2012). Introduction to Electronic Document Management Systems. Academic Press. p. 120. ISBN 9780323140621. Retrieved 19 May 2018.
- ^ Sommerville, J.; Craig, N. (2006). Implementing IT in Construction. Routledge. p. 130. ISBN 9781134198986. Retrieved 19 May 2018.
- ^ Skipper, S.L. (2015). How to Establish a Document Control System for Compliance with ISO 9001:2015, ISO 13485:2016, and FDA Requirements. ASQ Quality Press. p. 156. ISBN 9780873899178. Retrieved 19 May 2018.
- ^ Austerberry, D. (2012). Digital Asset Management. CRC Press. pp. 27–28. ISBN 9781136033629. Retrieved 19 May 2018.
- ^ a b Austerberry, D. (2012). Digital Asset Management. CRC Press. p. 30. ISBN 9781136033629. Retrieved 19 May 2018.
- ^ White, M. (2012). Enterprise Search. O'Reilly Media, Inc. pp. 73–74. ISBN 9781449330408. Retrieved 19 May 2018.
- ^ International Organization for Standardization. "01.140.40: Publishing". Archived from the original on 6 June 2011. Retrieved 14 July 2008.
- ^ International Organization for Standardization. "35.240.30: IT applications in information, documentation and publishing". Archived from the original on 6 June 2011. Retrieved 14 July 2008.
- ^ OnSphere Corporation. "SOP Document Management in a Validated Environments" (PDF). Archived from the original (PDF) on 4 September 2011. Retrieved 25 April 2011.
- ^ Meurant, G. (2012). Introduction to Electronic Document Management Systems. Academic Press. p. 16. ISBN 9780323140621. Retrieved 19 May 2018.
- ^ International Organization for Standardization. "01.140.10: Writing and transliteration". Archived from the original on 7 July 2009. Retrieved 14 July 2008.
- ^ International Organization for Standardization. "01.140.20: Information sciences". Archived from the original on 5 December 2008. Retrieved 14 July 2008.
- ^ International Organization for Standardization. "01.110: Technical product documentation". Archived from the original on 6 June 2011. Retrieved 15 July 2008.
- ^ "Code of Federal Regulations Title 21, Part 1271". Food and Drug Administration. Archived from the original on 10 October 2011. Retrieved 31 January 2012.
- ^
Wiggins, Bob (2000). Effective Document Management: Unlocking Corporate Knowledge (2 ed.). Gower. p. 25. ISBN 9780566081484. Archived from the original on 13 January 2018. Retrieved 9 April 2016.
At the organisational level an information systems strategy plan (ISSP) is a way to determine in general terms what information systems an organisation should have in place over the medium to long term (typically around three to five years [...]).
- ^ "What is Document Control?". isoTracker. Retrieved 9 November 2023.
- ^ "Document Management Systems - A Buyer's Guide". Archived from the original on 10 January 2017. Retrieved 10 January 2017.
- ^ Chaouni, Mamoun (5 February 2015). "7 Powerful Advantages of Using a Document Management System" Archived 10 January 2017 at the Wayback Machine
- ^ ash-conversions (13 February 2020). "Benefits of a Document Management System and 9 Things to Look For". Ash Conversions International. Retrieved 7 May 2020.
- ^ "Document Management Software for Construction". HCSS. 15 December 2021. Retrieved 7 June 2022.