Introduction
Thanks for the opportunity to bid on this project. I am a business professional with approximately 13 years of experience providing consulting services to large organizations. I am an advance Excel, VBA, MS Access user with years of experience with data analytics, data mining, data normalization.
Over the years I have build a number of database for various clients.
Scope of the project
I understand that you need a resource to create a MS Access database to track hard drives being received and issued to users. The database are to include forms and reports accessible to the user.
Do you have an idea how the database will be deployed i.e. are we talking about t client – server architecture or just a single installation being used by users.
Also, do you require dynamic reporting driven by a dashboard or static reports with pre-determined query parameters defined.
Introduction
Thanks for the opportunity to bid on this project. I am a business professional with approximately 13 years of experience providing consulting services to large organizations. I am an advance Excel, VBA, MS Access user with years of experience with data analytics, data mining, data normalization.
Over the years I have build a number of database for various clients. However for this project, I believe that’s a secondary deliverable with the emphasis on the written procedures displayed below.
Scope of the project
I understand that you need a prototype MS Access database developed with limited functionality. The focus in on creating detailed supporting documentation related to developing:
• detailed implementation plan (how the system will be implemented, eg, abrupt cutover, phased in, etc., who is responsible)
• user training plan (categories of users to be trained, who will train the users, how they will be trained, how many training sessions, how many at each session)
• system backup plan for bringing the system back into operation after a major fault/catastrophe (plans for backing up data normally, cater for power failures, factory burning down, hard disk failures, server failures)
• anticipated maintenance plan that states at what intervals the system will be checked for problems after full implementation of the system
• the procedures for adding new users to the system such as the user’s logon username, password and user access permission (how they get their username and password, who authorises it, who issues it)
Please let me know should you have any questions.