Contract Mgmt Application

I require a web-based application that will be used to manage our customer's contracts. The requirements are spelled out in the deliverables section. Overall, the application is a fairly straigthforward application to enter contracts into a database, attached scanned images of contract to contract record, enter key contract milestones into database for each contract, enter contacts for each contract, have the application email notifications when certain milestone based alerts come due, etc. The application should be built on the LAMP technology platform. ## Deliverables 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) Detailed functional requirements include the following: Overview The contract management module will provide functionality that will enable Source Loop to better administer our customer’s telecom contracts. Functionality The following functionality will be provided by the Contract Management Module: · _Contract image repository:_ store scanned images of contracts ; allow for browsing, printing and downloading of contract documents · _Contract Calendar:_ interface that allows for the entry of key contract milestone dates (to be entered and stored by contract) as well as functionality to trigger events (such as sending an email notification, etc.) when dates are encountered. · _Contract Contacts:_ interface that allows user to load in key contact info related to specific contracts. · _Contract Diary/Notes/log:_ allows user to log/enter notes related to specific contract to record interactions with vendors that occurred on certain dates User Interfaces/Usability Guide The key user interfaces envisioned for this module are the following: · Contract entry form. Allows user to enter all pertinent data for inclusion in summary contract record. Also should allow user to upload digital documents related to contract which would include copies of contracts, amendments, pricing schedules, etc. · Contract Calendar/Diary: an interface similar to MS-Outlook Calendar is envisioned for this portion of the module. The view will allow one to view each contract and its associated key milestone dates (as indicated by bold values for dates that have entries. Upon clicking of the bold date object a form should appear that displays the following: o Contract ID o Provider o Service Type o Description of Milestone Event o Notification type (email, application (user will get prompt when using the application)) o Notification date o Notification list (email addresses to use to notify of events) o Notification Message: allows for a custom message to be put into the email to notify users. Interface should allow user to view milestone events for all contracts or events for a specific contract by selecting from a drop down list. Application should use system date as a trigger to issue contract notifications. Upon trigger dates being realized, the application will send an email with the custom message to the addresses in the notification list. · Contract Contacts form. Allows user to enter contact information indexed by contract ID. User should be able to filter the Contacts view by selecting a specific contract ID or “All Contracts?? from a pick list. This interface should look like the MS Outlook Contacts form. Database Requirements Database schema will be provided upon acceptance of proposal. User Interaction The following describes how the user will use this module: 1. Users will first load in summary contract information into application along with supporting digital content. The creation of these summary contract records will serve as the objects that will be selected when entering milestone data. The contract ID assigned during contract entry stage will be used when entering contract rates into rate database. <!-- --> 1. Users will then review contract and determine the significant contract milestone events which they will add to the Contract Calendar section of module. <!-- --> 1. As users do their work related to contracts they can enter information indexed by each contract into the Contract Diary forms. User/Data Security: The database needs to have strong security to prevent the viewing of contract data for parties outside of those that are registered with the application. Initially, there are 2 types of users envisioned on this application: 1. Client user: Source Loop customer that will use the system 2. Admin: Source Loop employee that will make changes to the user profiles. Only the admin user will have the ability to add/delete/modify user profiles. Administration: There needs to be an interface where an admin can perform the following: 1. Add, delete, modify user id/passwords Development Technology Requirements: The following are the desired components to be used for this development: OS: should be OS-independent but definitely run on Linux Database: MySQL Web Server: Should run on Apache Web coding: PHP ## Platform Linux, Apache, MySQL, PHP