My question is coming from a broad experience in using third party documentation management system for the oil and gas industry. These database were very helpful in managing documentations, including versions, document numbering, comments, transmittals in and out. In my current industry the mindsed is the "folder" type and I can't live with that. I would like to transfer those database features of my previous job to my new company using a tool that we already have, that is Sharepoint. What I would like to create, starting from the most complex library, is the engineering documentation library and in the specific the features I would like to have are the following
1. Starting from a master document register with "N" documents (that in the beginning are all in the status "not started"), create the same "N" placeholder documents in the sharepoint library, all with the status "not started". In this way i can make statistics on the overall picture. Is there a smart way to do this? I was thinking to create one subfolder per document in the root folder and leave it empty. Does it make sense?
2. Add metadata to the documents ( I saw that it can be done using "document sets") such as planned submission date etc
3. Each document filename consists of a document number ( according to the numbering procedure) , Revision, Reason for issue, and title. This should be done via "document sets"? The version history in sharepoint collide with the revision of documents inside the document code?
4. Comments are managed via comments inside each app? In word it's easy, what about pdf or other formats? Is it possible also to generate comment sheets?
5. Is it possible to share the documents outside the organization?
6. Statistics : I suppose that I can set up something in Power BI, ( late documents etc).
Thanks for the support