To develop a MS Access database for a PMO to track the status of various initiatives. The database will be built in conjunction with MS Excel since most of the users will provide inputs in Excel worksheets. I am open to suggestions if you could suggest some other form of data gathering.
The database should be able to store and report information regarding the initiatives, key dates, owners of the initiatives, or by department. We may potentially use other variables to classify/organize the data such as tracking by department.
The database will also track the impact of the initiative on existing infrastructure. This is going to be a mapping exercise. For e.g., if the marketing dept. has an initiative that is being tracked for 10/1 but that initiative impacts the revision of some of their policies, procedures after the implementation of the project, the database should import the universe of policies and procedures so that the owner of the initiative may tag the impacted procedures.
The final aspect is reporting. The primary intent is to take inputs (dynamic data) from various departments on a periodic basis, utilize existing static data within the PMO to create a functional database and generate reports to track status, escalate issues, executive reporting, etc.
Complexity: if the database can track MS Project Plan dates and action items, that would be ideal.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
4) A detailed user guide that explains the functionality of the database including key aspects as importing dynamic data from end users, generating reports, archiving old data, etc.
5) Allocate a percentage of time on a weekly basis over the duration of the project to share information with the buyer so that the buyer may understand the database design and other key information required to support and administer the database on a going forward basis.