I think this is a classic example of the 3 whys to why paradigms. First, let’s be clear. DocBoss was built to create and append cover pages to every vendor submitted document.
So they comply with specifications.
Why have those specifications been created?
Because the EPCs need to know information about the document, and need it provided in a consistent way, all the time.
Because every document ends up in a mega data system, and it will be found only via links to various data systems (Project, PO, SDRL, Tag, Rev).
If you ask for an apple, I can simply give you an apple, or I can give you a bag labeled “apple” with an apple inside. Which one is faster?
Project data systems can deliver either option with the same speed and accuracy. DocBoss saves the time needed to get the bag, type “apple” on the bag, put the apple in the bag, pass the bag to another person who must verify that “apple” is correctly spelled and easy to read, and that the bag does indeed contain an apple (and all subsequent unwrapping and rewrapping of said apple).
In computer systems, meta-data is routinely added to documents. File size, author, file type, date created. Every program shares a common format to store the data, and program knows how to read the data. In the world of vendor documentation, there as two road blocks. There is no automated way to create the meta data (specifically tag lists), and there is no accepted (nor easy) way to add this data to the document.
In DocBoss, we create pigeon holes for every required document on a job. The vendor simply places their original document into the correct slot. We then create all of the required meta data (including the critical tag lists), add the data to the document both in human readable form (a cover page) and machine readable form (meta data). Once EPC processes change to support digital documentation, the cover pages will be retired, leaving the massive data management system responsible to deliver the right document at the right time.