IPTD-640
Digitization of Personnel Files
Description
No description
Problem Statement
Our file room is massive and unwieldy. We would like to digitize Personnel data, starting with data for new Employees hired after a certain yet-to-be-determined date.
Project Justification
This will allow for better automation: for example, documents can be automatically stored in the personnel file from our various systems.
This will ultimately allow Employees to request their Personnel data at the click of a button.
This will allow for more robust security and access control in regards to who can see what portions of each Personnel file.
This will save physical space, significantly cut down on paper usage, and save time for HR Employees who will no longer have to print out physical packets of paper and pass them around in person.
During the analysis phase, we hope to also be able to standardize what data is included in the Personnel file and document it, which will eliminate confusion between groups as to what goes where in the Personnel file.
This will ultimately allow Employees to request their Personnel data at the click of a button.
This will allow for more robust security and access control in regards to who can see what portions of each Personnel file.
This will save physical space, significantly cut down on paper usage, and save time for HR Employees who will no longer have to print out physical packets of paper and pass them around in person.
During the analysis phase, we hope to also be able to standardize what data is included in the Personnel file and document it, which will eliminate confusion between groups as to what goes where in the Personnel file.
Estimated Transactions
None
Target Rollout Date
None
Target Rollout Date Reason
None
Activity
Show:
@External Share for Jira We are planning on using Highview for file storage – we are currently working with CACI to accomplish this. That should take care of all the storage, searching, indexing and so on, and they have been very forthcoming regarding their ability to build us custom API endpoints, should we need them.
In terms of the frontend, we already develop and maintain the Evergreen platform, so we are going to build an API connector there since we already have role-based access control etc. set up. This will give HR staff an easy way to upload and categorize files without having to interact with Highview/the guts of the database. CACI has advertised a pre-built front-end to us as an alternative (the name escapes me at the moment), but I believe the cost was prohibitive so we elected to build our own.
Feel free to reach out if you have any more questions. 🙂
To build this do you need a backend in something like SQLite, and then an easy-to-use frontend where you can pull data from a search bar? Also to ask a clarifying question what else are you looking for in a digitization tool. Is it just a database that is searchable or do you need more features?