University of Wisconsin-Madison

Check the "Contract Updates for the Week"

Click here for piggybacking data form

PROJECT MGT SOFTWARE FOR THE SCHOOL OF MEDICINE &  PUBLIC HEALTH FACILITIES MGT

SMPH Facilities acquired a Project Management Program that has the applications to properly, effectively, and efficiently manage the wide-array of projects that are managed by SMPH Facilities (i.e. Capital Projects, Project Admininstration Center (PAC) Projects, and UW Physical Plant Projects) throughout various locations assigned to SMPH Facilities (i.e. Health Sciences Learning Center (HSLC), Medical Sciences Center (MSC), Service Memorial Institute-Bardeen (SMI/Bardeen), Wisconsin Psychiatric Institute & Clinics (WisPic), Health Emotions Research Institute (HERI), the upcoming Interdisciplinary Research Complex (IRC), Wisconsin Alumni Research Facility (WARF), and many other locations throughout the city of Madison as well as the state of Wisconsin.

The program will track the status of each of the projects mentioned above, and also function as a management tool to accurately track budgets and costs associated with these projects, which can tie in to various existing database programs.

08-5056

PROJECT MGT SOFTWARE FOR THE SCHOOL OF MEDICINE &  PUBLIC HEALTH FACILITIES MGT

Non-UW-Madison users contact: Vendor Representative

October 1, 2008 through September 30, 2009, with automatic renewal extensions to September 30, 2013, unless amended, cancelled or rebid.

208-68
209-69
958-77

“D” FOB DESTINATION, FREIGHT PREPAID AND ALLOWED
“V” F.O.B.  SERVICE/MAINTENANCE

SEE BELOW

SPECIFICATIONS

1. Software must have a file management system for organizing all project information.
2. Software must have a contact relationship management system.
3. Software must have reusable precedents or templates for automating recurring processes.
4. Software must have built-in reporting capability.
5. Software must be useable on a local area network.
6. Software license must allow a minimum of 6 concurrent users.
7. Software must be able to import/convert existing SQL Server database data.
8. Software should be accessible over the Internet with appropriate security.
9. Software should allow for custom fields.
10. Software must have data backup and recovery.
11. The system's backup process should be capable of selective restores.
12. Contractor must provide training and customization services for the software system to meet our office requirements with installation.
13. Users should be able to drill down into detailed budget and cost information.
14. There should be reports for both summarized (by project, by time period, by location, etc.; total costs, costs by provider)

1.         License Grant and Use 
            The Software license(s) identified in Contractor's response to the University's solicitation document is (are) purchased on a non-exclusive, non-transferable, perpetual license basis (unless otherwise stated in the Contractor's response) and shall continue in perpetuity until cancelled by the University or unless terminated in accordance with the provisions of this Contract.  The license(s) granted to the University is (are) for the use of the Software product(s) to conduct University business in the ordinary course at any location at the University of Wisconsin-Madison.

2.         Software Ownership and Title
            Contractor shall maintain all title, copyright, and other proprietary rights in the Software. University does not acquire any rights, express or implied, in the Software, other than those specified in this Contract.
            Contractor represents and warrants that it is the sole owner of the licensed Software or, if not,  the owner has received all proper authorizations from the owner to license the Software, and has the full right and power to grant the rights contained in this Contract.

3.         Software Documentation
            Contractor shall provide, at no additional charge, documentation which describes in detail the Software capabilities, its operation, installation procedures, error messages with identification of probable causes, Software modification procedures and techniques, and program interfaces. Documentation will be furnished for each individual piece of Software ordered by the University. Updated, revised, or replacement documentation published by Contractor shall be provided free of charge pursuant to the requirements specified in this section. Contractor agrees that the University may make such additional copies of documentation supplied pursuant to this section as are needed for use by University employees. Contractor agrees to make every reasonable effort to furnish documentation which will conform to industry standards for such documentation and programs used at the University's installation site.

4.         Software Maintenance
            a)      Maintenance Overview: Maintenance is not linked to usage or License rights.  Maintenance is an option, to be acquired at the sole option of University.  Cancellation of Maintenance by University will not in any way affect other parts of this Contract and the grant of License herein.  Maintenance shall include options to renew and if elected by University, shall commence upon expiration of the Software Warranty and may be renewed on an annual basis. 
            b)      Maintenance Assurance: Contractor agrees to make available maintenance services for the Software.  Such services shall be available at the prices contained in Contractor's response to the University's solicitation document, but shall in no event exceed these prices increase more than the Consumer Price Index or 5%, whichever is lower, for each year after the date of acceptance of the Software.
            c)      Maintenance Release Services. Contractor will provide error corrections and maintenance releases to the Software that have been developed by Contractor at no additional cost to the University. Such releases shall be licensed to The University pursuant to the terms and conditions of this Contract. Each maintenance release will consist of a set of programs and files made available to the University and accompanied by a level of documentation adequate to inform the University of the problems resolved including any significant differences resulting from the release that are known by Contractor. Contractor agrees that each maintenance release of Software will be compatible with the then-current unaltered release of Software applicable to the computer system

5.         Specified Operating System
            The University reserves the right to exchange copies of the licensed Software designed to operate in one operating system for copies designed to operate in another operating system in which Contractor has stated the licensed Software is designed to operate.  Should the University exercise this right, it will pay any costs of shipping and handling involved in the exchange as well as any positive cost difference between the two licenses.

Revision History