Docstoc

11

Document Sample
11 Powered By Docstoc
					                              The University Of Connecticut

                               REQUEST FOR PROPOSALS

                                      NO. WH031604

             Facilities Computer Information Management System (CIMS)

                              Software and Implementation


                                       Date Issued:

                                     March 17, 2004


                           Date and Time of Proposal Opening:

                                      April 16, 2004
                                        2:00 PM




Issued By:   William Hill
             Associate Director/Purchasing
             Purchasing Department
             3 North Hillside Road
             Storrs, Connecticut 06269-6076
             Phone: (860) 486-0991
             Fax:     (860) 486-5051




                                              1
                 TABLE OF CONTENTS FOR RFP No. WH031604


SECTION 1      OVERVIEW

SECTION 2      GENERAL TERMS & CONDITIONS

SECTION 3      SCOPE OF WORK/SPECIFICATIONS

SECTION 4      EVALUATION CRITERIA

FORM OF PROPOSAL

NOTIFICATION TO BIDDERS

BIDDERS QUALIFICATIONS CHART

ATTACHMENT A

INSTRUCTIONS TO BIDDERS

AWARD AND CONTRACT

EXHIBIT A

EXHIBIT B




                                      2
SECTION 1       OVERVIEW

1.1   Introduction

      The University of Connecticut located in Storrs Connecticut along with the University of
      Connecticut Health Center, located in Farmington Connecticut, is interested in receiving
      proposals from qualified and experienced vendors to provide software and implementation for
      a proposed Facilities CIMS. In soliciting proposals, it is the University's intent to establish one
      source for providing software and implementation services for the Storrs and Health Center
      campuses – as well as all other regional campus locations. The University shall reserve the
      right to place purchase orders in any manner deemed by the University to be in its own best
      interest. The University also reserves the right, as the need arises, to negotiate with vendors
      to establish contracts in addition to those awarded pursuant to this RFP.

1.2   Overview
      UConn Storrs and the UConn Health Center reevaluated their facility management tools by
      going through a Business Process review and Information Needs Analysis. An investigation
      of all critical information that flows in an organization and to and from their customers was
      performed to identify (a) how they perform work, (b) what business processes work to meet
      their mission(s), (c) which processes need to be modified and (d) to identify a fully Web Based
      – Computerized Information Management Software System (CIMS) that would support their
      business process state-wide.

      The Information Need Analysis study has determined the needs of the Facilities Management
      Organization (FMO) management team, assessing the capabilities of the current systems to
      meet those needs and, where appropriate, make recommendations to enhance or replace
      those systems. This assessment also involved analyzing the needs of the supported
      departments and schools at the University as they relate to the proposed information systems
      within the facilities organization. Needs are to be addressed within the FMO management
      team as related to the Computerized Information Management System (CIMS). Information
      requirements such as security, scalability and reliability of a multi-site system will be
      addressed in the selection process to support the following integrated functionality.

         Multi-site Web-based application --
         Option for ASP (outsourced application serves provider model)
         Single Integrated System
         Pure Web GUI Interface based upon active server page technology and a GIS query
          tool
         Space Management
         Move Management
         Asset Management
         Maintenance Management
         Stock room / Inventory Management
         Environmental Management
         Grant Management
         Utility Management
         Construction and Project Management
         Communication module (email, pager, telephonic, iPAC, 802.11)
         Interface with the current financial package (FRS)
         Interface with the current HR package (Genesis) and the planned HR package,
          Peoplesoft
         Web-based Customized Reporting

      The scope of the Information Needs Analysis was to establish how the UConn, Storrs and the

                                                   3
      Health Center can best collect, analyze, and report data to support the mission requirements
      of the organization and space ownership, work management effort, pertaining to the
      operations/maintenance of the facilities and planning/design/project management/construction
      groups.

      Implementation of this product will be the responsibility of the vendor. The University may
      contract with another vendor to collect and validate data. This Vendor shall identify required
      skills necessary to complete the project and schedule all of the required tasks to accomplish
      this effort in a timely manner. These additional skills could include Space and Maintenance
      Consultants, legal, administrative, financial and IT skills -- all working with the University
      Implementation team.

      It is the University‟s intent to implement the selected application at the University‟s, Storrs
      campus and the Health Center simultaneously. Then upon completion of acceptance testing,
      the web-based product will be implemented to the branch campuses over the following year.

1.3   Demographics

      The University of Connecticut has a total enrollment, at all campuses, of approximately 23,500
      students. The Storrs campus has an enrollment of approximately 16,700 undergraduates and
      graduate students including a resident population of approximately 8,700 students. There are
      approximately 5,900 full and part-time faculty and staff. The Storrs campus is responsible for
      approximately 500 buildings and 11.5 million square feet. The Health Center is responsible for
      approximately 40 buildings and more than 2 million square feet.

      University of Connecticut campuses includes:

           Main Campus at Storrs, Mansfield
           Mansfield Depot Campus, Mansfield
           University of Connecticut Health Center, Farmington
           Avery Point (Groton/New London Campus), Groton
           Greater Hartford Campus, West Hartford
           Law School Campus in Hartford, Hartford
           Stamford Campus, Stamford
           Torrington Campus, Torrington
           Waterbury Higher Education Center, Waterbury

1.4   Method of Award

      Each proposal will be evaluated by a committee using points earned matrix. Awards shall be
      made to the most responsive and responsible Respondents offering the best value and most
      economical proposals based on the total matrix scores, and if requested by the University, site
      visits, product demonstrations and/or business opportunities as determined by the University.
      All Respondents, in submitting proposals, concur with this method of award and will not, under
      any circumstances not in any manner, dispute any award made using this method.

1.5   Not Used

1.6   Definitions

             “Purchaser”, “Buyer”, “UConn”,
             “University of Connecticut”, or
             “University”                                  The University of Connecticut and the University
                                                           of Connecticut Health Center
                                                  4
             “Bidder”, “Contractor”, “Vendor”               Person, firm or corporation
             “Seller” Or “Respondent”                       submitting proposal to this RFP

             “Coordinator”                                  William Hill or
                                                            Other University authorized
                                                            Purchasing Department personnel


1.7   Estimated Timetable

      The following schedule will apply to this RFP.

             Release of RFP                                 March 17, 2004
             Pre-proposal Conference                        (None Planned)
             Closing Date for Inquiries                     April 9, 2004
             Submission of RFP Due                          April 16, 2004
             Oral Presentations (if necessary)              (Mutually agreed date and time)
             Anticipated Award Date                         June 30, 2004 or sooner

1.8   NOT USED


1.9   General Instructions and Timetable

      A.     Inquiries: Direct all inquiries relative to the conditions and specifications listed herein
      to:

             William Hill
             Associate Director of Purchasing & Stores
             University of Connecticut
             Purchasing Department
             3 North Hillside Road Unit 6076
             Storrs, CT 06269-6076
             Phone: (860) 486-0991
             Fax: (860) 486-5051
             E-mail: William.Hill@UConn.edu

      B.     Requests for Clarification

             Requests for Clarification by Bidders: Any Bidder may request that the University
             clarify any information contained in this Request for Proposal for Facilities CIMS
             Software and Implementation. All such requests must be made in writing to:

             William Hill
             Associate Director of Purchasing & Stores
             University of Connecticut
             Purchasing Department
             3 North Hillside Road Unit 6076
             Storrs, CT 06269-6076
             Phone: (860) 486-0991
             Fax: (860) 486-5051
             E-mail: William.Hill@UConn.edu
                                                  5
     The University's response to any request for clarification, together with a copy of the
     request for clarification, will be provided contemporaneously by the University to each
     party receiving this RFP. Responses to all written requests will also be posted on the
     University Purchasing Department website:
     http://www.purchasing.UConn.edu/currentbid/currentbid.html .

     Under no circumstances, may any Bidder or its representative contact any employee
     or representative of the University regarding the RFP prior to the closing date, other
     than as provided in this section. Strict adherence to this important procedural
     safeguard is required and appreciated.

     Any violation of this condition may result in Bidder being considered non-compliant and
     ineligible for award.

C.   Requests for Clarification by the University: The University may request that any
     Bidder clarify or supplement any information contained in any proposal. Bidders are
     required to provide a written response within five (5) business days, or sooner, of
     receipt of any request for clarification by the University.

D.   Submission Format/Receipt of Proposal

     An original and Ten (10) copies of the proposal must be submitted in a sealed
     envelope to:

            University of Connecticut
            Purchasing Department
            Attention: William Hill
            3 North Hillside Road Unit 6076
            Storrs, CT 06269-6076
            Reference RFP No. WH031604
            “Facilities CIMS Software and Implementation”

            On or before 2:00 p.m. on April 16, 2004

     At the specified time stated in above, all proposals received as stipulated, shall be
     publicly opened and dated. However, due to the complexity of the bid, only the names
     of the Respondents will be read, as no immediate decision will be made. All
     information will be confidential until after review and action by the Evaluation
     Committee. All interested parties are; however, welcome to attend the bid opening.

     Failure to respond to all points may be grounds for rejection. Likewise, failure to
     supply any information required to accompany the proposals may cause a rejection of
     the proposal as non-compliant. The University reserves the right to request additional
     information and/or presentations, if clarification is needed.

     All proposals must be submitted in a sealed envelope and labeled as noted
     above. No responsibility will be attached to any person for the premature
     opening of any proposal that is not properly identified.

     E-mail or electronic attachments are not acceptable means of submitting a proposal
     and will be rejected as non-conforming. If you intend to use an express delivery
     service, it is recommended that you stress the need to deliver your package to the
     building and office designated above. Packages delivered by express mail to other
                                          6
     locations might not be re-delivered to the appropriate address in time to be
     considered.

     Proposals that do not substantially conform to the contents of the bid request,
     consequently altering the basis for proposal comparison, may be disregarded
     and considered as unresponsive.

E.   Communications between the University and the Bidder:

     Informal Communications:

     From the date of receipt of this RFP by each Bidder, until a binding contractual
     agreement exists with the selected Firm and all other Bidders have been notified or
     when the University rejects all proposals, informal communications regarding this
     procurement shall cease. Informal communications shall include but not be limited
     to: Requests from the Vendors to any department(s) at the University, for information,
     comments, speculation, etc; and requests from any department at the University, or
     any employee of the University for information, comments, speculation, etc.

     Formal Communications:

     From the date of receipt of this Request for Proposal by each Bidder until a binding
     contractual agreement exists with the selected Firm and all other Bidders have been
     notified or when the University rejects all proposals, all communications between the
     University and the Bidders will be formal, or as provided for in this Request for
     Proposal. Formal communications shall include but not be limited to:

            A. Pre-Proposal Conference
            B. Oral Presentations, if required
            C. Pre-Award Negotiations

F. Freedom of Information Act

     Respondents are advised that all materials submitted to the University of Connecticut
     for consideration in response to this solicitation will be considered the property of the
     University of Connecticut and will not as a matter of course be treated as confidential
     information. The University of Connecticut reserves the right to distribute or not to
     distribute materials and information submitted by Respondents as it sees fit and/or as
     required by applicable law.

     If a Respondent wishes to supply any information, which it believes is exempt from
     disclosure under the Act, that Respondent should summarize such information in a
     separate envelope. Each page submitted should be clearly marked "Confidential," but
     otherwise be presented in the same manner as the Proposal. However, any such
     information is provided entirely at the Respondent's own risk and the University
     assumes no liability for any loss or damage which may result from the University's
     disclosure at any time of any information provided by the Respondent in connection
     with its proposal.




                                          7
SECTION 2 - GENERAL TERMS & CONDITIONS

2.1   Each firm, by submitting a proposal, represents that the firm has:

      A.     Read and completely understood the RFP documents and attachments thereto.

      B.     Is familiar with the conditions under which services would be provided, including availability
             and cost of materials, equipment and personnel.

2.2   Receipt of Proposals

      A.     The University will receive proposals at the Purchasing Department, 3 North Hillside Road,
             Storrs, CT 06269-6076, until 2:00 P.M., on April 16, 2004. Proposals will be opened and the
             names only of the Respondents will be read publicly. All information will be confidential until
             after review and action by the Evaluation Committee.

      B.     Any proposal received after the time and date specified for receipt of proposals shall not be
             considered and shall be returned unopened via regular mail.

      C.     Each Respondent shall be solely responsible for the delivery of his or her proposal to the
             University at the place and before the time as specified above.

      D.     Unless otherwise noted in this document, all materials submitted in response to this RFP shall
             become the property of the University of Connecticut upon delivery and are to be appended to
             any formal documentation, which would further define or expand the contractual relationship
             between the University and the Respondent.

      E.     The University reserves the right to reject any or all proposals submitted for consideration in
             whole or in part; and to waive technical defects, irregularities or omissions, if, in its judgment,
             the best interest of the University would be served thereby. Non-acceptance of a proposal
             shall mean that another proposal was deemed more advantageous to the University, or that
             all proposals were rejected. Firms whose proposals are not accepted shall be notified, upon
             request, after a binding contractual agreement between the University and the selected
             Respondent exists, or after the University has rejected all proposals.

      F.     A Respondent shall promptly notify the University of any ambiguity, inconsistency, or error,
             which they may discover upon examination of the proposal documents.

2.3   Preparation of Proposals

      A. Proposals shall include an exact copy of the "Form of Proposal" included within these documents.
         All applicable blank spaces shall be filled in, typewritten or in ink, and amounts shall be written in
         both words and figures. If there is a discrepancy between the words and the figures, the amount
         shown in words shall be deemed correct.

      B. Respondents shall provide a written, itemized list of any exceptions to this RFP in the space
         provided on the “Form of Proposal”.

      C. Proposals shall indicate the full name of the Respondent submitting the proposal and shall bear
         the signature of the principal duly authorized to execute contracts on behalf of the Respondent.
                                                          8
         The name of each person signing the proposal shall be typed or printed below the signature.

      D. All erasures or corrections shall be initialed by the person(s) signing the proposal.

      E. The terms and provisions of this RFP and any contract resulting from this RFP shall be construed
         in accordance with the laws of the State of Connecticut. All deliveries hereunder shall comply in
         every respect with all applicable laws of the Federal Government and/or State of Connecticut.

      F. Any interpretation, correction, or change to this RFP shall be made by a written addendum to this
         contract. Interpretations, corrections or changes to the RFP made in any other manner shall not
         be binding and Respondents shall not rely upon such interpretations, corrections or changes. Any
         changes or corrections shall be issued by the University Purchasing Department. Questions
         regarding this RFP shall be submitted in writing and directed to:

             William Hill
             Associate Director/Purchasing
             3 North Hillside Road
             Storrs, CT 06269-6076

             Questions will be accepted via Facsimile to 860-486-5051

      G. Additional Charges - All additional charges, including but not limited to training, insurance or other
         costs must be included in the proposal prices. Charges not specified in the proposal will not be
         honored unless agreed to in writing by the University Purchasing Department.

      H. Addenda - All addenda shall be mailed or delivered to all who are known to have received the
         RFP. No addenda shall be issued later than seven (7) days prior to the date for receipt of
         proposals except an addendum, if necessary, postponing the date for receipt of proposals or
         withdrawing the RFP.

2.4   Format of Proposals

      A. Proposals must include a point-by-point response to this RFP, where required. Each such
         response must be cross-referenced to the correspondingly numbered item in this RFP and
         described in as much detail as possible. Likewise, any samples and/or examples, which are
         provided to support responses, shall be labeled to correspond with the specific requirement in this
         RFP. This MANDATORY REQUIREMENT will facilitate a more expedient evaluation of the
         proposals.

      B. Failure to respond to all points may be grounds for rejection. Likewise, failure to supply
         any information requested to accompany proposals may cause rejection of the proposal as
         noncompliant. The University reserves the right to request additional information if clarification
         is needed.

2.5   Submittal of Proposals

      A. An original and Ten (10) copies of each proposal shall be submitted in a sealed parcel addressed
         to the University at the address given above. The sealed parcel shall further be identified with the
         name and address of the Respondent and the designation "SEALED PROPOSAL RFP NO.
         WH031604 / Facilities CIMS Software and Implementation”


                                                          9
         The complete response to this RFP shall include:

          Software name and release number
          Work plan and approach
          Completed questions in sections 4, 5, 6, 7, 10 and 11 and matrices in sections 8, 9 and
           Exhibit A
          Deliverables
          Team Members – Resumes‟
          Assistance required from UConn
          Engagement Terms & Conditions
          Timing and Fees
          Key Clients
          A completed "Form of Proposal" included herein,
          A comprehensive point-by-point response to all items listed herein, where applicable,
          A completed "Notification to Bidders" forms,
          A completed "Bidders Qualifications" form
          References
          Portfolio of samples produced by Respondent

      B. No oral, telephonic or telegraphic proposals will be accepted. If a proposal is sent by mail,
         allowance should be made for the time required for such transmission. The officer whose duty it
         is to open proposals shall decide when the specified time has arrived and no proposal received
         thereafter will be considered.

      C. No responsibility will be attached to any person for the premature opening of any proposal that is
         not properly identified.

2.6   Modifications or Withdrawal of Proposals Will Be Executed As Follows:

      A. A proposal shall not be modified, withdrawn or canceled by the Respondent for a sixty (60) day
         period following the time and date assigned for the receipt of proposals as specified in paragraph
         2.2.A above and the Respondent so agrees in submitting a proposal.

      B. Prior to the time and date assigned for receipt, proposals submitted early shall be modified or
         withdrawn only by written notice to the University. The University prior to the designated date and
         time for receipt of proposals as provided in paragraph 2.2.A shall receive such notice.

      C. Withdrawn proposals may be resubmitted up to the time designated for receipt of proposals
         provided they are then fully in conformance with these terms and conditions.

2.7   Formation of Agreement

      A. The response to this RFP will be considered an offer to contract. At its option, the University may
         take either one of the following actions in order to form an agreement between the University and
         the selected Respondent:

            Accept a proposal as written by issuing a written "Notice of Award" to the selected
             Respondent which refers to this RFP and accepts the proposal as submitted; or

            Enter into negotiations with one or more Respondents in an effort to reach a mutually
             satisfactory agreement that will be executed by both parties and will be based on this RFP,
             the proposal submitted by the selected Respondent and the negotiations concerning these.
                                                        10
       B. Because the University may use either alternative described in above, each Respondent should
          include in his or her written proposal all requirements, terms or conditions it may have, and should
          not assume an opportunity will exist to add such matters after the proposal has been submitted.

       C. The University reserves the right to award a contract not based solely on the firm with the lowest
          cost, but based on an offer which, in the sole opinion of the University best fulfills or exceeds the
          requirements of this RFP and is deemed to be in the best interest of the University.

       D. The contract, when duly executed, shall represent the entire agreement between the parties.

       E. The University expressly reserves the right to negotiate prior to an award, any contract that may
          result from this RFP.

2.8    Presentations
       Potential firms may be asked to discuss their written responses to this document at a presentation at
       the Storrs campus on date(s) mutually agreed upon between the firm and the University. If a firm is
       requested to make a presentation, the firm will make the necessary arrangements and bear any costs
       associated with the demonstration. Presentations will be by scheduled appointment only by the
       Purchasing Department.

2.8    Qualifications of Firm

       A. Preference will be given to those Vendors with a demonstrated and substantial history of
          experience in successfully providing the highest quality software and implementation services to
          institutions or corporations whose requirements were similar in size and scope to those of the
          University.

       B. Prospective firms must be prepared to provide any evidence of experience, performance ability
          and/or financial surety the University deems necessary to fully establish the performance
          capabilities represented in their proposal.

       C. The University will reject the proposal of any firm and void any award resulting from this RFP to
          any firm who makes any material misrepresentation in their proposal.

2.10   Assignment
       Any contract resulting from this RFP may not be assigned or transferred without the prior written
       consent of both parties.

2.11   Nonappropriation of Funds
       Notwithstanding any other provision of this RFP or any ensuing contract, if funds anticipated for the
       continued fulfillment of the contract are at any time not forthcoming or insufficient, either through the
       failure of the Connecticut Legislature to provide funds or alteration of the program under which funds
       were provided, then the University shall have the right to terminate the contract without penalty by
       giving not less than thirty (30) days advance written notice documenting the lack of funding. Unless
       otherwise agreed to, the contract shall become null and void on the last day of the fiscal year for
       which appropriations were received; except that if an appropriation to cover the costs of this contract
       becomes available within sixty (60) days subsequent to termination under this clause, the University
       agrees to re-establish a contract with the firm whose contract was terminated under the same
       provisions, terms and conditions of the original contract.


                                                           11
2.12   Indemnification
       The Respondent agrees to jointly and severally indemnify and hold the University, its successors and
       assigns harmless from and against all liability, loss, damage or expense, including reasonable
       attorney's fees, which the State may incur or sustain by reason of the failure of the Respondent to
       fully perform and comply with the terms and conditions of any contract resulting from this RFP.

       State of Connecticut agencies (University of Connecticut) may not enter into indemnification or “hold
       harmless” agreements. In the event of a loss by the vendor or any third party shall have recourse
       through the State of Connecticut Claims Commission, as provided under Chapter 53 of the General
       Statutes of the State of Connecticut, in which all claims against the State of Connecticut and the
       University of Connecticut will be filed with the Connecticut Claims Commissioner.

2.13   Contract Termination for Cause

       A.     The University may terminate any resulting contract for cause by providing a Notice to Cure to
              the Respondent citing the instances of noncompliance with the contract.

                   The Respondent shall have ten (10) days to reply to the Notice to Cure, indicate why
                    the contract should not be terminated, and recommend remedies to be taken.

                   If the Respondent and the University reach an agreed upon solution, the Respondent
                    shall then have thirty (30) days after such agreement is reached to cure the
                    noncompliance cited in the Notice to Cure.

                   If a mutually agreed upon solution cannot be reached within ten (10) days after receipt
                    of Notice to Cure by Respondent, the University reserves the right to terminate the
                    agreement.

                   If the mutually agreed upon solution is not implemented within thirty (30) days from the
                    date of agreement, the University reserves the right to terminate the contract.

       B.     The University shall be obligated only for those services rendered and accepted prior to the
              date of Notice of Termination.

2.14   Ethical Considerations:

       The proposing vendor must certify that no elected or appointed official or employee or student of the
       University has benefited, or will benefit financially or materially from the proposed services. The
       University may terminate any contract resulting from this RFP, if it is determined that gratuities of any
       kind were either offered to, or received by, any University officer or employee contrary to this policy.
       The authorized signatory of a submitted proposal automatically attests this to be true.

       The laws of the State of Connecticut provide it is a felony to offer, promise or give anything of value
       or benefit to a State employee with intent to influence that employee‟s acts, opinion, judgment or
       exercise of discretion with respect to that employee‟s duty. Evidence of violation of this statute will be
       turned over to the proper prosecuting attorney.


2.15   Responsibility of Those Performing the Work

       A.      The firm shall be responsible for the acts and omissions of all the firm's employees and all
               subcontractors, their agents and employees and all other persons performing any of the work
               under a contract with the vendor.
                                                           12
       B.      The firm shall at all times enforce strict discipline and good order among the firm's employees
               and shall not employ any unfit person or anyone not skilled in the task assigned.

2.16   Payment Terms
       Payment Terms shall be 2 %-15 days/Net 45 days after receipt of invoice unless otherwise
       negotiated.

2.17   References
       All proposals shall include the minimum of three (3) references, on the form furnished for that
       purpose, for contracts similar in size and scope to those of the University. As a minimum, the
       company or individuals name, telephone number, description of the contract, the contract sum and
       name of the contact person assigned to the contract shall be provided.

2.18   Promotion
       Unless specifically authorized in writing by the Vice Chancellor for Business Administration on a case
       by case basis, the firm shall have no right to use, and shall not use, the name of the University of
       Connecticut, its officials or employees, or the seal of the University: (A) in any advertising, publicity,
       promotion, nor (B) to express or to imply any endorsement of contractor's products or services: nor
       (C) to use the name of the state, its officials or employees or the University seal in any manner
       (whether or not similar to uses prohibited by subparagraphs (A) or (B) above), except only to
       manufacture and deliver in accordance with this agreement such items as are hereby contracted by
       the University.

2.19   Contract Provisions by Reference
       It is mutually agreed by and between the University and the Respondent that acceptance of the
       Respondent's offer by the issuance of a purchase order shall create a contract between the parties
       thereto containing all specifications, terms and conditions in this RFP except as amended in the
       purchase order.

2.20   Price Adjustment
       Prices quoted shall remain firm during the initial term of the agreement. Thereafter, prices may be
       subject to revision, at yearly intervals. Price changes will be accepted subject to the following
       conditions only:

           The proposal should include suggested procedures for dialog and agreement regarding the
            review of requested price increases in other similar mutual circumstances. After the initial period,
            the prices quoted in response to this Request for Proposal may be adjusted up or down in an
            amount not to exceed the Consumer Price Index (CPI), appropriate for the commodity, as
            published by the United States Department of Labor.

           Price changes shall be submitted in writing thirty (30) calendar days prior to the date the increase
            rate is allowed to become effective, acceptance of which shall be subject to the University‟s
            receipt and approval of the written documentation requesting the changes. No retroactive
            increases will be allowed. Price escalation is permitted only once per term.

           Price changes approved by the University shall then remain firm for the term of each successive
            extension.

           The prices quoted for each yearly period shall be firm except that the University shall receive any
            reduction in prices that may occur during the contract period. The reduced prices shall apply on
                                                           13
          all shipments made on or after the date the reduced prices become effective.

2.21   Term and Extension of Contract
       By mutual agreement between the parties, this contract shall be implemented for two (2) years from
       acceptance of software and may be extended for three (3) additional one (1) year periods for either
       ASP or service agreement. Said option will be exercised only upon the satisfactory performance of
       the Respondent as determined by the University and upon the mutual consent of both parties to any
       contract resulting from this proposal. Such intent to renew shall be conveyed to the Respondent in
       writing thirty (30) days prior to the effective date.

2.22   Taxes
       The University of Connecticut is exempt from Federal Excise taxes, and from State and local sales
       and use taxes. Tax exemption certificates can be furnished to the awarded vendor(s) upon request.

2.23   Federal, State and Local Taxes, Licenses and Permits
       The successful Respondent(s) will comply with all laws and regulations on taxes, licenses and
       permits.

2.24   Waiver of Rights
       No delay or failure to enforce any provision of this agreement shall constitute a waiver or limitations of
       the University's rights under any resulting contract.

2.25   Prior Course of Dealings
       The parties hereby agree that no trade usage, prior course of dealing or course of performance under
       other contracts shall be a part of this agreement or shall be used in the interpretation or construction
       of this agreement.

2.26   Choice of Law and Venue
       The terms and provisions of this RFP and any ensuing contract shall be governed by and construed
       in accordance with the laws of the State of Connecticut.

2.27   Violence in the Workplace - Executive Order No. Sixteen
       This solicitation (or any contract resulting from this solicitation) is subject to the provisions of
       Executive Order No. Sixteen of Governor John G. Rowland promulgated August 4, 1999 and, as
       such, the contract may be canceled, terminated or suspended by the University for violation of, or
       noncompliance with, said Executive Order No. Sixteen, which governs violence in the workplace. The
       parties to this contract, as part of the consideration hereof, agree that said Executive Order No.
       Sixteen is incorporated herein by reference and made a part hereof. The parties agree to abide by
       such Executive Order.

SECTION 3     SCOPE OF WORK AND SPECIFICATIONS

  1.0 As an aid in the development of this RFP, the University has provided a CIMS Implementation
      Scope of Work Matrix (‘Exhibit B’) of existing systems, both at Storrs and the Health Center. This
      should be used as a guide in determining costs for interfaces, legacy issues and timeframes for
      implementation.

  2.0 Response Requirements

  2.1 The purpose of this RFP is to gather enough information to determine the degree to which your
       system(s) meet the functional and technical needs of the University. Your responses to these
       questions must be complete, as they will become part of any contractual agreements. We
       appreciate the investment of time and resources the vendors are making by participating in
       this process.
                                                          14
2.2 The review of your product and services will be based on your responses to this RFP, demonstration
     sessions and potential site visits to a client site. Once the response to the RFP is received, an
     Evaluation Committee may invite selected vendors to provide the University with a structured
     demonstration lasting one full day. The anticipation of this evaluation committee is to have these
     demonstration sessions commence during late April 2004. The schedule for site visits is anticipated
     to begin in mid May and continue into June 2004. If a remote hosting or ASP model is quoted, the
     site visit may include a visit to the remote hosting facility as well as a live client site.

2.3 The University reserves the right to amend this RFP without altering the timing requirements. Any
     changes or addenda to these documents will be communicated in writing to all vendors as quickly as
     possible. If there are modifications, which will change the timing requirements, these will be
     communicated to all vendors as quickly as possible.

2.4 The University reserves the right to negotiate the final terms and conditions of the proposal and
     resulting agreement.

2.5 The vendor must respond to each item in the purchase specification, stating acceptance or taking
     exception to the item. If a specification cannot be met, the vendor is required to provide alternatives
     or explanations, noted as exceptions to these specifications. If certain functionality is to be
     incorporated into future releases of the software product, give expected date of release to the general
     client base. If the functionality is currently in alpha or beta testing, state client testing functionality
     and start date of testing.

2.6 The vendor providing this hardware/software should list any special requirements in regards to power
     and infrastructure features of the buildings that will house the hardware, if not an ASP model, and
     include any special installation requirements in the purchase price of the CIMS.

    State the electrical power requirements with respect to power line conditioning and protection from
    spikes, surges, sags, loss of power, and other power line interference.

2.7 The vendor must meet the Standard Bid Terms and Conditions, the University Information Security
     Policy, and other regulatory (State and Federal) guidelines where applicable.

2.8 The vendor shall provide the University with one original and Ten (10) complete RFP packages,
     including itemized quotation, terms and conditions, maintenance agreements, equipment
     description/technical product data specifications, and acceptance test procedure. All proposals
     become the property of the University.

2.9 Any questions or concerns regarding the System requirements should be addressed to William Hill,
     Purchasing Department.

3.0 System Costs

3.1 Overview
    In the proposal, the vendor shall supply a list of the major components, the individual major
    component's costs, licensing costs, and the total cost, including any installation costs of the system.
    Itemize any options requested on a separate list. Also, the vendor shall provide a list with costs of any
    items/hardware/disposables that are required in order to use the product in a typical University
    setting. The proposal shall contain a detailed comparison of costs associated with Application
    Service Provider (ASP) hosting compared to the University hosting the system internally.
    Provide detailed costs of both hosting options or state if ASP is not available.

3.2 Proposed Hardware Configuration and Costs
    Describe the required hardware configuration for your system, including vendor specific model
                                                         15
    numbers and maintenance costs. Disk space requirements should include the application software,
    production data, and full copies of the database files on line. Off site communication links should also
    be included. Peripherals must be vendor specific --NO THIRD PARTY REPLACEMENTS. All
    hardware specifications must be configured to allow for three years growth.

3.3 Proposed Application Costs
    Identify the costs for the application we have identified. Please indicate if there is any financial
    advantage in purchasing other related/integrated applications planned for the future that would be
    beneficial to be purchased up front. Provide alternative pricing for a leasing model, ASP model
    or Remote Hosting Option.

3.4 Implementation Costs
    Describe each method available for implementation. Define the costs associated with each of the
    implementation options presented. Please include estimated Travel expenses as well as any out of
    pocket expenses, implementation/installation costs and any other costs that will be charged to the
    University. All costs associated with the project should be quoted as a not to exceed amount.

3.5 Ongoing Maintenance and Support Costs
    Describe the options and components of on-going maintenance and the costs associated with them
    for any system equipment and software. All hardware purchased from the vendor should state
    warranty period as well as ongoing support once the warranty period expires. Describe the types of
    support available and their associated costs for any equipment and/or software. Include all peripheral
    costs such as transportation or dedicated lines.

3.6 Other Costs
    The vendor shall provide to the University, at no additional cost, any service diagnostic upgrades for
    the equipment purchased, for the life of the equipment. Define any other costs not addressed in the
    above categories, which are relevant to this proposal.

3.7 Financing
    Describe any alternate methods of financing available to the University. Example –leasing
    agreement, etc.

3.8 Payment Terms
    The Vendor shall propose payment terms as part of their response to this RFP.

4.0 Vendor Information
    Please provide the appropriate response as required for both ASP and UConn internal hosting
    options.

4.1 Vendor Overview
     Please provide the following:
     4.1.1 The name and location of your company.
     4.1.2 A brief general description of your business.
     4.1.3 How many years has your company been in business?
     4.1.4 Please provide a copy of your most recent annual report.
     4.1.5 Please provide a copy of your company‟s organizational chart.
     4.1.6 If your response indicates a joint effort between your company and others, describe the
            relationship between the firms and other vendors involved. Who is the primary contact
            person?
     4.1.7 Is your company a subsidiary of another corporation? If so, what is the name of the parent
            company?
     4.1.8 Do you publish newsletters or other publications? How frequently?
     4.1.9 Do you hold educational seminars for users? How often? Where? Cost?
     4.1.10 Do you have national and/or regional user group meetings? What month(s) of the year?
            Where? Cost?
                                                       16
    4.1.11 Is there a formal user advisory council?
    4.1.12 Please list, and then give a general description of the hardware and software products you
           offer in the facilities management industry.
    4.1.13 Please explain your strategy for developing new products and product enhancement,
           including information on the current status of your product, upcoming planned enhancements
           and release dates for future releases. Will there be a charge for these enhancements?
    4.1.14 Please explain your philosophy concerning open systems approach.
    4.1.15 What percentage of your budget is devoted to R and D for application software?
    4.1.16 How many personnel does your company employ? Please describe the breakdown by
           functional areas in your company.

                    Sales;
                    Hardware/Technical Support;
                    Software Support;
                    Software Development;
                    Other;

    4.1.17 Each vendor must submit audited financial statements for the most recent fiscal year. If the
           vendor is a subsidiary of another entity, the same information must be submitted for the
           parent company.
    4.1.18 Please provide a copy of your company policy on travel. Is travel an additional cost to the
           project?
    4.1.19 How has web-based technology been incorporated into your system? Discuss your current
           and future plans regarding the usage of Internet and/or Intranet.
    4.1.20 What industry standards do you support?

4.2 Client Base
     4.2.1 Provide specific reference information for a minimum of three organizations that would be
            potential site visit locations that are using a configuration similar to the one being proposed.
            Please include the following information:

                    Organization Name;
                    Address
                    Phone number
                    Date of Installation
                    Date of Go-Live
                    Applications Installed
                    Number of Interfaces/Integrations with other systems

    4.2.2   Provide a list of the customers of your proposed systems. This list should include the
            institution's name, address, phone number, and contact person.
    4.2.3   Provide the following information with regards to the total number of contracts signed with in
            the last 24 months:

                    # of contracts signed with in last 24 months
                    # of unique clients
                    Distribution of clients by
                             Purchase date
                             by quarter
                             # of these clients live
                    Distributions of clients expected to be live by quarter
                    # of clients on proposed software/hardware

4.3 Contractual Information
    4.3.1 What system response time will you commit to with the proposed configuration?
    4.3.2 Will the vendor agree to a post system performance bond?
                                                        17
    4.3.3    What impact do software modifications have on warranties or guarantees?
    4.3.4    Please provide a copy of your standard contract and maintenance agreement.
    4.3.5    Vendor will comply with University policies and procedures as well as all laws, ordinances,
             rules, regulations, standards, and orders of governmental, regulatory and accrediting bodies

5.0 Support and Services

5.1 On-going Support:
    5.1.1 What geographic area(s) will support our account for on-going support?
    5.1.2 When users discover errors with applications, what is the process and turnaround time for
           corrections of errors?
    5.1.3 How do you advise users of:

                    Outstanding problems with applications?
                    Fixes, modifications, and improvements?
                    Upgrades to application software?

    5.1.4    Describe your formal trouble-shooting procedures. How quickly does your staff respond to
             calls? Describe policies for call-backs and issue resolution.
    5.1.5    Describe support staff: number of staff, experience levels, rate of expansion.
    5.1.6    Describe the support your company provides on a continuing basis.
    5.1.7    Describe the method you use for charging for support services.
    5.1.8    Do you provide a web-based mechanism for reporting error?
    5.1.9    Describe your escalation process.
    5.1.10   Describe your policy on providing Source Code to your clients?
    5.1.11   Who is responsible for Hardware Maintenance during warranty period? After the warranty
             period expires?
    5.1.12   What services are covered under the maintenance agreement?
    5.1.13   How frequently is the system updated?
    5.1.14   Is there a charge for updates?
    5.1.15   Is software support available via modem/remote network access?
    5.1.16   Is there person-to-person telephone support available? For how many employees? Which
             ones?
    5.1.17   What are the hours of coverage?
    5.1.18   What is the procedure for suggesting changes/enhancements to the system?
    5.1.19   At what rate do maintenance/support fees increase?

5.2 Service Response Time
     5.2.1 The vendor shall provide telephone support for emergency service requests 24-hrs/day, 365
           days/yr.
     5.2.2 Telephone response to service problems should be provided within 30 minutes.
     5.2.3 The response time shall be the same whether under service contract or if maintenance is
           handled on a time & materials basis, following the warranty period.
     5.2.4 If we make changes to your software, what type, if any invalidates our software support
           agreement?

5.3 Documentation of Maintenance and Repair
     5.3.1 The vendor shall provide the IT and/or any other relevant department with individual written
           reports for each maintenance event whether it is scheduled maintenance or repair. The
           reports must adequately detail the work performed, provide accurate hours for labor and
           travel, and give list prices for any parts used or subassemblies that were replaced.
     5.3.2 All software changes need to be documented according to relevant regulatory agency
           guidelines.
     5.3.3 During the warranty period and under future service arrangements loaner equipment will be
           provided at no additional cost if equipment cannot be repaired within a 24-hour period.

                                                       18
5.4 Hours of Coverage
     5.4.1 Software/Operating System: Support shall be for 24 hours by 7 days for 365 days a year.
           Please describe how that support will be provided.
     5.4.2 During and After the Warranty Period for Equipment/Hardware: The Principle Period of
           Maintenance (PPM) on the items purchased will be provided from 7:00am - 7:00pm EST,
           Monday - Saturday, excluding national legal holidays. During this time, normal labor and
           travel rates will apply. Premium rates will apply if service is requested outside the specified
           times. Describe equipment/hardware support during and after the warranty period.

5.5 Service Options Following Warranty Period
           The vendor should list the available service options and costs following the warranty period
           and also list preventive maintenance, labor rates, and travel rates for normal and after-hours
           service on a time & materials basis. If there are multiple maintenance plans available please
           state all options and costs associated with the options.

5.6 NOT USED

5.7 System Enhancements / Upgrades
     5.7.1 Describe how enhancements and upgrades to your system are identified. Describe any
           differences between the processes. How are the upgrades released to the general client
           base?
     5.7.2 What criteria are used to select the functionality that will be added to upgraded versions?
     5.7.3 Are the two previous releases of your systems supported? How long are older releases
           supported? How often is the software upgraded, please distinguish between major and minor
           upgrades.
     5.7.4 Provide a brief statement indicating what your upgrade policies are for the software. Define
           Maintenance Upgrade, Version Upgrade, Enhancement, or any other term related to changes
           to the software.
     5.7.5 What will the cost (if any) be for upgrades?
     5.7.6 Is there an existing active user group for your products? If so, please list the nearest local
           user group contact and telephone number. What is your company's role in the user group?

5.8 Implementation Process
     5.8.1 Implementation Plan:
     5.8.1.1 Provide a sample plan for the application implementation, including appropriate timelines.
     5.8.1.2 Describe your implementation process including how testing is executed and tracked.
     5.8.1.3 Describe any interfaces that will be required.
     5.8.1.4 Describe data conversion requirements and the overall approach you would recommend for
             the installation of the proposed systems.
     5.8.2 Training :
     5.8.2.1 Describe your approach to user training, including the use of training aids and training
             courses.
     5.8.2.2 Describe your approach to training for new releases of the system you are proposing. What
             documentation is provided?
     5.8.2.3 The successful bidder shall provide formal and informal on-site training for the personnel in
             the operation of the System. The vendor shall cover all training expenses including tuition,
             travel, and per diem, if training is performed off-site.
     5.8.2.4 Do you provide training for department „super user‟, database specialists, system analysts
             and other Information Technology personnel?
     5.8.2.5 What is the estimated training period for end users of various types, including facilities staff,
             financial staff, professional and clerical users of the product?
     5.8.2.6 Do you provide web-based training? Computer-based training?
     5.8.2.7 Is all training documentation available electronically via the Internet?
     5.8.2.8 How many University staff members, including ancillary departments, do you envision will be
                                                        19
             needed at our site to accomplish the installation plan? Please describe the skill set required
             for the implementation team.
    5.8.2.9 How many staff members do you recommend be dedicated to the software after
             implementation has been completed? Please include any technical requirements and %FTE
             needed.
    5.8.2.10 How many IT staff members do you recommend be dedicated to the operation, both software
             and hardware, after implementation has been completed? Please include any technical
             requirements and % FTE needed.
    5.8.2.11 What geographic area(s) will support our account during the implementation?
    5.8.2.12 What documentation is available to technical staff and end users? How many copies are
             made available? At what cost?

5.9 Acceptance and Warranty
     5.9.1 Acceptance testing will be performed by the relevant department staff and Information
           Technology personnel and will include the verification of all equipment technical
           specifications, software, and safety features.
     5.9.2 Functional Acceptance will be achieved with consistent usage of the system 45 days post first
           use of the system. During this period the system shall operate according to the printed
           documentation, without errors, and uninterrupted. If there is a deviation, i.e. software bug, the
           45 days will begin from the date of the fix being applied to the live environment. A payment
           milestone will be associated with achieving functional acceptance.
     5.9.3 A minimum 12-month warranty period is to begin when the system is fully operational and
           accepted for use and performs as described in the technical specifications. During the
           warranty period, the University has the right to return the system, without penalty, for full
           refund, if it is found to be unacceptable due to deficiencies in meeting the technical and
           performance specifications on the bid and in the system‟s product literature.
     5.9.4 During the warranty period the vendor shall furnish all labor, travel, and parts necessary to
           maintain all equipment specified under the purchase agreement in proper operating condition.
           Vendor shall provide services 24 hours per day, 7 days per week, 365 days per year as
           necessary for urgently needed repairs. Please describe your normal response procedures and
           time frames for equipment repairs.

5.10 Documentation
    5.10.1 Provide four complete sets of operator manuals and service manuals.
    5.10.2 Provide a listing of all documentation relevant to the proposed system.
    5.10.3 Do you provide your documentation on CD-Rom? On-line?
    5.10.4 Do you provide new documentation as you upgrade your applications?
    5.10.5 Do you provide the following documents to your clients:

                   Systems operations manuals
                   Technical/operations manuals
                   User manuals for each application
                   Installation manuals
                   Training manuals

6.0 System Processing/Environment Requirements
6.1 NOT USED

6.2 Current University Hardware/Environment: Available upon request.

6.3 Hardware Needs
     System/Host Characteristics
    6.3.1   Describe the architecture for the host based systems associated with your system (hardware
            requirements, operating system, database engine, network interface requirements, etc.)
    6.3.2   Describe your ability to utilize the existing network (FDDI/Ethernet). If necessary, provide
                                                       20
             details regarding any additional networking peripherals (except the cable) necessary to meet
             University needs.
    6.3.3    Describe your integration approach regarding our existing systems where necessary (i.e.,
             communications to various nodes in the existing VAX cluster, IBM mainframe, Windows NT
             Servers, communications mechanisms for interfaces, etc.).
    6.3.4    Do you provide offsite Disaster Recovery? Is so, please provide description of services, cost
             to provide and equipment required, if any, in „FORM OF PROPOSAL‟ section under other
             services.

    Client Server Characteristics
    6.3.5    Describe the architecture for the servers associated with your system (hardware
             requirements, operating system, database engine, network interface requirements, etc.)
    6.3.6    Describe the client architecture required by your system (minimum hardware requirements,
             operating system, network operating system, network protocol stacks, database engine
             connectivity mechanisms, network interface requirements, etc.)
    6.3.7    What system networks does your system support?
    6.3.8    What are the minimum requirements for desktop PC‟s? If multiple platforms are supported for
             various levels of user access, please describe requirements at these various levels that would
             be supported without system/network modifications?

6.4 Hardware Specifications and Communications
     In order to evaluate hardware costs and system performance objectively, we want the vendor to
     assume our current systems are all at capacity and any system we purchase will require additional or
     new hardware. If you are quoting a traditional option as well as a remote hosted or ASP option, make
     sure you answer these questions for both options.

    6.4.1    The CIMS shall be accessible (for viewing, work order entry, document access, etc.) from any
             “Standard Network Desktop” PC. Describe the server and workstation costs to provide this
             capability. If additional software/hardware is required please include the specific additions and
             the costs associated with these items.
    6.4.2    Describe in detail the processing hardware required by your system. Provide all significant
             technical data (i.e. memory, speed, capabilities, throughput, languages, noise level, site
             preparation, space requirements, electric/cooling requirements, etc.)
    6.4.3    Describe the expansion possibilities of the system.
    6.4.4    Describe the workstations, peripheral hardware, and printers required; include the ability to
             use PC‟s as workstations, the minimum specifications, and the recommended specifications
             for optimum performance.
    6.4.5    For ASP/Remote Hosting, describe the type of connection required.
    6.4.6    Hand Held Units: Does your system accommodate PDA‟s ? Please describe hardware
             requirements and specifications. Please identify any components of your system that cannot
             operate on this hardware, including print capabilities. If you are partnered with another vendor
             for this technology, please state the company, contact name and phone number and type of
             applications.
    6.4.7    Describe the types of printers your system will support.
    6.4.8    Does your system support the use of Laser Printers?
    6.4.9    Are there any special requirements for Bar code printers, label printers, etc?
    6.4.10   What is the maximum number of workstations, printers, hand held devices, ports and/or other
             devices, which can be accommodated, in your proposed configuration? What is the optimal
             number?
    6.4.11   Describe the network topology and protocols supported by your system.
    6.4.12   Describe the LAN/WAN cabling options available, including type, maximum lengths, etc.
    6.4.13   Does your system support the client-server architecture? If so, please describe how your
             system operates as a client-server (i.e., what processing is done on the client, and what
             processing is done on the server?)
    6.4.14   The system must be available by remote access to users, who are stationed at off-site
                                                        21
          locations, describe your proposed systems ability to meet this requirement.

7.0 Software Technical Requirements

   The software application shall meet or exceed the requirements listed below. If the application cannot
   provide the noted functionality, please note its limitations in the „FORM OF PROPOSAL‟ section.

   1.     FACILITY FOCUSED: The system must be oriented toward facilities management, rather than
          manufacturing.
   2.     SYSTEM FLEXIBILITY OVERVIEW: The system shall be flexible, allowing System
          Administrators or other approved users to create or modify fields, hierarchies, associations,
          processes and access to the application. The ability to tailor the solution to meet the
          University‟s needs is Paramount. Please submit a document describing your general
          approach to provide a flexible solution by answering, at a minimum, the following questions:
               Are source code changes or development effort required to customize the solution?
               How will customizations impact support or the ability to upgrade?
               Provide an overview how “user-definable fields” are used throughout the product.
               Provide an overview on what import/export functions are provided with the product.
               Provide an overview of how workflow/processes (i.e. document movement, approvals,
                    communications, etc) are supported.
   3.     WEB BASED: The proposed solution must be a fully integrated system, with a single web-
          based front end. Solution shall not incorporate any middle-ware (i.e. Citrix, or any other
          terminal server emulators) to meet the requirements found within this RFP. (e.g. All
          functionality, other than initial GIS and drawing setup shall be performed through an internet
          browser (Internet Explorer or Netscape Navigator) interface, (i.e., viewers, forms, queries,
          reporting and system administration). Also identify what program language is being used.
   4.     GUI/GIS INTERFACE: Product will have a Web-based Graphical User Interface (GUI). The
          GUI must sensibly complement the modules(s) and achieve a balance between richness of
          capabilities and intuitive presentation. The University prefers that GIS and CAD be used as
          the graphical query tool and currently is an ESRI and AutoDesk shop.
                         Proposed solution shall also share a common user interface between modules.
                         Product should share common table structure between modules and be tightly
                          integrated.
                         Product should support an API allowing interfaces to existing systems.
   5.     NAVIGATION: System shall be navigable similar to internet browser.
   6.     MODULAR GROWTH: Proposed solution shall be modular and support growth-over-time
          deployment.
   7.     INTEGRATION: .All modules must be integrated, so that data is entered only once, and is
          immediately accessible by any other module, without requiring any batch or reboot process to
          be executed.
   8.     QUERY CAPABILITY: A general ad-hoc web based query interface should be available for
          non-technical users. Users should be able to report on any item in the data dictionary, per
          selection criteria defined by the user: specific values, ranges, and/or conditions, etc. Ideally,
          Queries should be performed either graphically through the drawings or through the forms.
   9.     TOOL BARS: Among the points to be evaluated are the presentation and use of tool bars,
          levels of screen nesting needed to complete transactions, and the on-line help available.
   10.    ALERTS / TRIGGERS: The system must be able to automatically trigger alerts for upcoming
          action needed to be taken
                         For example, for work that needs to be started a number of user-designated
                          days into the future, critical maintenance conditions and database systems
                          conditions are desired.
                         Alerts can take the form of windows presented to the operators of the system
                          and hard copy reports.
                         Equipment warranties, existing maintenance contracts, approvals, customer
                          response, etc.
                                                     22
                      The system must also support E-mail, cell phone, iPAC, pager and minimally
                       802.11 wireless supported alerts.
11.    BAR CODES: The system must support bar coding as part of its base product functionality
       including bar coding of the forms; both bar code printing and scanning must be supported.
12.    IMPORT/EXPORT CAPABILITY: The system should have a utility that enables the export
       and import of data items selected by the user, without having to write a program to do so.
       Imported data should be able to be updated onto the database by the importing utility
       program. The import import/export capability must be able to work with standard desktop
       products, such as Microsoft Office Products (word, excel, project, etc).
13.    STANDARD RELATIONAL DATABASE: Product should be built around the MS SQL Server
       or Oracle database.
14.    APPLICATION SECURITY: Security should be able to be assigned and changed at the user
       group, user, screen, row, and column levels. Audit trails for key file maintenance functions
       should be part of base product functionality with full reporting functions.
15.    FIREWALLS: Please describe how the system handles firewalls.
16.    ADDING OPEN-ENDED TEXT: There should be the capability for entering descriptive
       information to the degree considered necessary by the user. Furthermore, this information
       must be printable as addenda to whatever basic document is being printed; for example, work
       orders and purchase orders.
17.    CAD / GIS SUPPORT: The system must operate smoothly on the Customer Administrative
       desktop Workstations (AutoCAD and ESRI –GIS modules) linking to the application database.
       Both AutoCAD and ESRI applications are current licensed products with the University.
18.    HARDWARE – Please describe the minimum desk-top and lap-top hardware requirements for
       proposed ASP hosting solution.
19.    SOURCE CODE: The vendor shall declare their willingness in writing as part of this RFP to
       provide application source code for the product. -- by purchase or escrow.
20.    CANNED REPORT: The vendor must furnish source code for all standard (“canned”) reports
       included with the proposed solution. The vendor shall declare their willingness to provide
       standard report source code. Reports shall be based in the latest version of Crystal Reports.
       A copy of Crystal Report shall be included as part of the product cost.
21.    DOCUMENTATION: - The proposed solution must include complete system documentation
       and training manuals. Vendors shall describe the documentation provided with the proposed
       solution.
22.    ON LINE HELP: The product must have on-line-help and must be usable during training and
       product acceptance. This includes any agreed to “added functionality.” Final payment will be
       held until such times as this component is functional.
23.    INTERFACES: - The proposed solution must provide, as a minimum, interfaces to the
       following software applications: Please provide estimated budget figures for these interfaces
       based on past interface services for existing clients.
                      Facility Condition Assessment (FCA) applications from ISES Corporation
                      Asset Management System (FFX) module of FRS financial software
                      University FRS financial software:
                      Peoplesoft financial software (future interface)
24.    If vendor can not provide a single solution for all requested applications, the vendor must
       provide the interfaces to a single web front end to provide a single data entry, query, view and
       reporting functionality.

7.1 General Requirements
7.1.1 Describe the language and/or database management system (DBMS) in which your system is
      written. Please tell us why you chose this language and any costs/benefits associated with it.
      Please specify those applications that are a DBMS, if it does not apply to all applications.
7.1.2 Describe in detail the processing software required by your system. Provide all significant
      data including version, vendor, memory requirements, etc. This information should address all
      system and application software including:
       Workstation
                                                  23
          Operating System
          Server Operating System
          Network Communication Software
          Application Software
          Development Software
          Relational Database Management System
          Interface Engines
          Gateways
          Routers
          Bridges
7.1.3    Describe the available and/or planned fault tolerant options that your system can provide,
         especially for the shadowing of production data.
7.1.4    Not Used.
7.1.5    Describe the components of your system (e.g., development tools, database structures) that
         will facilitate the University in developing other applications that can integrate with the
         proposed system.
7.1.6    NOT USED
7.1.7    Describe the system‟s processing schedule.
7.1.8    Provide a complete description of all back up and recovery procedures associated with the
         system.
7.1.9    Can routine incremental and archival backups occur with the users on-line?
7.1.10   Identify the effects on availability when updates to the operating system are released.
7.1.11   Identify the application upgrade methodology.
7.1.12   Can the upgrade/update process occur automatically through the network systems
         management software?
7.1.13   Provide information on the database and file structures used by the proposed systems.
7.1.14   Describe the relational database system, utilized by your system.
7.1.15   Can new data elements be added, as they are required without rebuilding the data schema
         and database? Can this occur without reducing the performance of the system?
7.1.16   When a database update is required, identify the period of unavailability during the database
         rebuild process.
7.1.17   Identify a cost and floor space requirement for a mirrored database and storage system.
         Provide a network impact statement for this estimate.
7.1.18   Describe in detail the normal synchronization method used in the mirror (e.g. real-time,
         scheduled, on demand, etc.) for the database system.
7.1.19   Are the mirrored storage or database systems fully operational during synchronization?
7.1.20   Please describe in detail the fail-over strategy used in the estimate when a database/storage
         system or mirror fails.

7.2 Ease of Use
7.2.1 Does the system employ a graphical user interface?
7.2.2 Does the system utilize Windows-based and/or icon driven technology?
7.2.3 Does the system offer point and click technology in addition to keyboard input?
7.2.4 Is on-line help available at all times? Describe.
7.2.5 Is it possible to scroll both forward and backward?
7.2.6 Can the system import and export data, both for use in other applications as well as for use in
       the decision support system?
7.2.7 Describe the process for getting printed output of data. Can you obtain all data from all
       modules, or specific data?
7.2.8 Does the system provide a “dashboard” for key executives and non-executives to get
       information published to them and also see other key data and applications from within and
       outside of the organization?

7.3 Integration Requirements
7.3.1 Describe your systems ability to integrate using an interface engine solution.
                                                   24
7.3.2   Please describe your point-to-point interface solution for both ancillary systems and devices.
7.3.3   Describe the hardware platforms with which you have interfaced your applications.
7.3.4   Describe any additional hardware required for interfaces to foreign systems.
7.3.5   General Interface Requirements:

       All interfaces must accommodate the TCP/IP protocol, length encoded
       Message length should be 6 bytes ASCII inclusive
       Must be four character length within messages
       All interfaces ARE NOT required to be real time

7.4 For each of the following interfaces please list the systems you have already successfully
integrated into your proposed system. In order to meet this qualification state whether the
interface is operational in a live environment or in the process of implementation. For all other
systems state which systems you are under contract to integrate.

System                               Vendor                                 Yes/No
COGNOS Finance
FRS (Financial Records System)       SCT
HRS (Human Resource System)          SCT
Peoplesoft                           Peoplesoft

Please note: the University has not implemented a system like the one you are proposing and some
of the interfaces above may or may not be feasible. In your experiences, make recommendations on
the feasibility and the appropriate interfaces required.

7.5 NOT USED

7.6 Scope and Flexibility of the Database
7.6.1 Does the database have unlimited volume capacity?
7.6.2 What type of file architecture does the system database have?
7.6.3 Can users move from high-level, summarized information to specific record and transaction
     level detail? Describe.
7.6.4 Does an end-user need to understand the database file structure in order to navigate through
     it? Explain.
7.6.5 Can special databases be added easily? How?
7.6.6 Can data elements be added at any time without reorganizing the files? Explain
7.6.7 Do users have on-line, real-time access to the database?
7.6.8 How many users can access the database simultaneously?

7.7 Technical Environment
7.7.1 Can the system operate on multiple platforms? If so, which ones?
7.7.2 What is the suggested operating environment?
7.7.3 Is the system MS Windows-compatible?
7.7.4 What network(s) does the system support?
7.7.5 What language is the system written in?
7.7.6 Does the system employ cooperative processing?
7.7.7 Does the system operate in a client/server environment? Describe.
7.7.8 What are the hardware requirements for the system?

8.0 General System Functionality

SOFTWARE FUNCTIONALITY REQUIREMENTS

The University has completed a self evaluation of what features and functionality are expected in
the major modules of the CIMS system and are included in this RFP (See EXHIBIT „A‟). The
                                                   25
University rated these features and functionalities on a scale of 1-4 with 4 being the highest and
considered to be mandatory. The required elements that the University identified as „4‟ are key
functions that the software company will be required to deliver. To complete this section, please
indicate in the MATCH CODE column, your product‟s ability to meet these requirements.

MATCH CODE
     The Match Codes must be supplied by the responding Vendor to (a) identify how well their
     product fits the requirements -- AS OF THE DATE OF THE RESPONSE.

       If the Vendor uses a Match Code of 4, the component can be delivered within 180 days of
       installation. If the Vendor is selected, all Match Code 4‟s will be listed as a contractual
       requirement for an agreed to percentage of the software‟s value for final payment.

       The Match Code values to be used are:

      5    The product as delivered meets the requirement with no modifications or user effort required.
      4    The product does not meet the requirement as delivered but is scheduled to be modified to
           include the feature within 6 months of the installation of the software.
      3    The product as delivered if configured by the Customer, by updating a table or other high level
           setting, meets the requirement.
      2    The product as delivered does not meet the requirement. The requirement could be met
           practically through modifications to the logic of the product made by the Customer utilizing a
           high level language or toolkit provided by the vendor for this purpose. The toolkit would then be
           responsible for generating all necessary replacement source code, including database
           descriptions, help files, etc.
      1    The product as does not meet the requirement. The requirement can only be met by the
           vendor or Customer making changes directly to the base source code of the product. If this
           value is selected, please include an estimate of the effort and cost involved to make this
           change or addition. (Add Alternate – time and cost)
      0    The requirement is not met by the system as delivered and it is not practical for the vendor or
           the Customer to make any sort of modification to the system to incorporate the change.

       The Vendor should make extensive use of the column for Comments and Explanations to
       describe how the product fulfills the requirement or why the requirement is not necessary in
       this particular product and for what reasons. Some of the requirements are actually requests
       for information about how the product deals with a particular issue. Any attached, additional
       information must be clearly referenced in the “Comments” column.

       If compliance to an item requires a modification at extra cost, indicate the approximate degree
       of effort and estimated cost of the modification as part of your response.

       IF the Vendor has a feature, to which this RFP does not allude and which the Vendor
       feels may be useful to the University, please include a description of the feature at the
       bottom of that section in the spreadsheet.

The basic modules that are expected to be provided in the integrated set of administrative web-based
software systems are:
        ASP Hosted using either SQL Server or an Oracle database
        All modules work through a Browser
        Web-based integrated application with front end user portal
        GIS /CAD Graphical Query Engine.
               o Integrated CAD throughout the total application
        Space Management
        Move Management
        Asset Management
        Grant Management
        Maintenance Management (CMMS),
                                                      26
           Stock room / Inventory
           Environmental and Regulatory Management
           Utility Management
           Project and Construction Management (CM/PM/Document Management)
                 o Integrated with work order system
           Proposed Interfaces to identified existing University software system in this RFP.
           Communication module (email, pager, telephonic, iPAC, 802.11)
           Interface with the current financial package (FRS)
           Interface with the Comprehensive Rate financial Information System (CRIS)
           Interface with the current HR package (Genesis) and the planned HR package, Peoplesoft
           Web-based Customized Reporting

This software package will be specifically integrated to address the administrative and management
needs of a large multi-site State University system.

In this section of the RFP, the University has described general functional requirements of the
Facilities CIMS. For each question, the vendor should respond by making a checkmark in the
appropriate column. If additional information is required please make additional comments on a
separate sheet identifying the specification: If a requirement is left blank, we will assume the
requirement cannot be met.

A     The function is available and active for more than 2 years
B     The function is available and active
C     The function is in development (include date functionality will be available to the
      general client base)
D     The function requires customized development (include the estimated cost)
E     The function is not available

8.1 Timeliness of Information

Functional Description                                                    A        B        C   D   E
Please respond to each question with summary answers whenever
applicable.
System is on-line, real-time
Revised data immediately updates all applications
System is completely integrated
Response time for system is one (1) second or less
Information can never be lost due to on-line backup system

8.2 Security System

Functional Description                                                    A        B        C   D   E
Please respond to each question with summary answers whenever
applicable.
System permits definition of security by user defined classes /
levels/ job description such as supervisor, clerk, etc.
New users can be added or their security level modified on-line,
real-time by authorized persons
Does your security system limit access to the entire computer, the
application modules, etc.
System provides automatic locking of records to prevent two
people from modifying the same data at the same time
Describe the mechanism used for monitoring locked records or
files.


                                                         27
Describe the mechanism for controlling simultaneous updates to

                                                 -only queries?

record is read) or optimistically (when update occurs)?
Describe the mechanism in place for maintaining system security.
What level of staff (i.e. Information Technology professional or
business application “owner”) is required to maintain security?
At what level is security supported? · Log-on · Access to specific
application modules · Database viewing (read only)
Is a password required to log-on to the system?
Database update (read-write) · Specified functions within
application modules · Master file access · Record access ·
Protected field access · Record locking by specific field value
How many user ID passwords can the system support?
How are passwords defined?
Does the system force periodic password changes? Can users
override this?
Can users and/or managers change a password at any time?
Can the system allow global assignment of passwords by the
institution (a file of revised user IDs and passwords can be applied
as a whole?)
Does the system keep track of failed log-in attempts?
Does the system provide notification to an operator if the number
of failed attempts exceeds a certain number?
Is it possible to maintain an audit trail regarding what information
has been downloaded, and which user IDs have requested and
received the downloads?

8.3 Audit Trails

Functional Description                                                 A   B   C   D   E
Please respond to each question with summary answers whenever
applicable.
System provides audit trails that document who, date and time the


                                                            .
Audit trails are maintained on-line for a user-defined number of
days – specify number of days audit trails are maintained on your
system.
System supports alarm/notification feature to provide immediate
notification of predefined events.
System prevents deletion or unauthorized modification of audit
trails.
System logs and reports all violations of system security
procedures.
Audit t

application

attempts at unauthorized access including user identification code
and password with date, time and location

authorities, including creating, disabling and deleting user
identification codes




                                                         28
         any debugging tools which may modify data, the

enable and disable logging of activities
At user's request, system prints management reports of security
access by application and by department
System maintains information on security violations by day of
violation
System allows sign on ID to tag on-line transaction audit records
for reporting capabilities
Audit trail generation does not impact storage or response times
System supports separate files or transactions to allow training
without corrupting the operational database
System log records all production changes in organization's
environment
Application-level changes (e.g. destination tables, routing tables)
can be easily moved into production with no need to disable
production environment. Such changes can be readily backed out
Third-party audit packages can access system files. List them
System provides audit reports of file changes, journal entries,
exceptions, validation changes, error reports, etc




8.4 Help Functions

Functional Description                                                  A   B   C   D   E
Please respond to each question with summary answers whenever
applicable.
Help provides information about valid entries for the field currently
being accessed
There is help for every data entry field without leaving the field
Every data element with a list of valid entries has the following:

                                rtial, long or short description

off list and have system automatically put value into field
User may define narrative for all help during system installation




8.5 User Friendly Features

Functional Description                                                  A   B   C   D   E
Please respond to each question with summary answers whenever
applicable.
System is menu driven, user friendly
“Windows”, split screens, GUI Front ends
                     Data can be retained on-line based on user




                                                           29
requirements as necessary both initially in set up and on-going as

                                          -line?

8.6 Authentication Requirements

Functional Description                                                 A   B   C   D   E
Please respond to each question with summary answers whenever
applicable.
System provides for the use of both a user identification code and
password to verify authorization to access the system.
System permits the use of passwords containing combinations of
alphabetic, numeric, and special characters.

minimum password length that will be enforced by the system
which is 8-
                                                 -user or per

time limit for expiration of a user's access privileges.


the password at will
System prohibits the re-use of passwords
System provides for comparing user-suggested passwords with
dictionary entries to prohibit weak passwords prior to accepting the
password change
System automatically prompts users to enter a new password upon
password expiration.
System provides messages to user upon denial of access due to
an invalid user identification code or password.
System supports automatic disabling of user identification code
after a predetermined system administrator defined, number of
consecutive invalid access attempts.
System informs user of the last time the system was accessed with
that user identification code.
System supports the encryption of the password file or the
password information
Security administration functions are separate from system
operation, management and maintenance functions.
System prevents system support and maintenance personnel from
accessing data.
System supports a hierarchy of security administration
System is designed to permit highest-level security administrators
to delegate specific security administration functions to
departmental security administrators.
System provides for multiple security administrators to be assigned
the highest level of authority.
System permits security administrator to disable a user
identification code without deleting it from the system.
System supports the disabling of a user identification code
immediately.
System provides system administrator's functions for monitoring
devices, sign-ons by function/sub-function.
System provides security features associated with dial-up
diagnosis (of system trouble) capability.
Vendor support personnel (without the knowledge of the
organization) cannot access system.


                                                           30
System provides password management function to allow
password change to be announced a number of days before it
becomes mandatory and to allow coupling of text screens to the
password change process for security certification.
System provides reports of current inventory of users, ids, and
access authorities based on a complete pattern matching
functionality
System provides tools for batch and on-line management of IDs
System provides for security control of all batch jobs, started tasks,
and data access by each end user, application and subtask on any
platform.
System provides uniform security controls and password
management functionality on multiple platforms including
Mainframe, Unix and Windows in any networked combination.
System accommodates single sign on ID and password across all
platforms.
System supports transaction authentication.
System provides security pass-through. Describe
System provides for dynamic reconfiguration based on
administrator requirements (e.g. immediately or deferred).
System supports the copying of user access profiles from one to
another. Describe other timesaving security set up features
System functions do not prevent sign-off from occurring
System provides reporting tools to the security administrator.
System can accommodate the user ID and password being passed
to it by an external security brokering agent (e.g. a CUI single
logon product) and consequently, for bypassing logon specific to
your system.


8.7 Authorization Requirements

Functional Description                                                   A   B   C   D   E
Please respond to each question with summary answers whenever
applicable.
System allows access to specific data elements; files, functions,
menus, and commands based on user's job functions.
System supports defining groups of users to be granted access to
specific data elements, files, functions, menus and commands or
collections of these.
System permits the security administrator to grant specific users
the authority to permit other users to access specific data items,
menus, or functions.
System supports the encryption of sensitive data and key
management tools to support the encryption methods.
System provides multi-level security down to options within menus.
System provides multi-level security features for dial-up access.
Access to databases can be restricted at level of schema;
subschema, area, record, set, element, or menu based on user
class.
System allows user to restrict printing and display of confidential
data elements if flagged in data dictionary.
System allows multilevel, read-only access to the system by
authorized personnel only.
System restricts additions to, changes to, and/or deletion of
records by security level.


                                                         31
System supports data security at all levels (e.g. dataset, volume,
task, transaction, etc.).
System supports various levels of security for programmer and
operator terminals and logs their activity through audit reports.
Systems can determine who is accessing a record at any point in
time through on-line inquiry.
System prevents access to functions without logging in through the
security system.
System restricts update and inquiry at the field level for every field
in the database. If this is not possible, describe where such
capability is present and where it is absent.
System prevents user from seeing menu items, screen formats,
report forms if user's security profile prevents them from accessing
the data elements associated with these system components.
System provides multiple levels of security, including but not limited
to the following: By User: -System Manager -Technical
(programmer) -Operator -Department Manager -Supervisor -End-
user - departmental personnel By Function: -Update, delete, and
inquire -Update and inquire -Inquire only -Print By Location: -

8.8 Integrity Requirements

Functional Description                                                   A   B   C   D   E
Please respond to each question with summary answers whenever
applicable.
System provides control over stored data to ensure data is
complete and internally consistent.
System allows authorized organization personnel to easily modify
and implement screen layouts without programming.
System provides screen and report prompts that will indicate
missing or critical information.
System provides data management features that eliminate the
redundant maintenance of duplicate data.
System provides provisions for recovering data if signed off.
System supports anti-virus software at both the network server and
workstation levels, including both a scanner to detect existing
viruses and an activity trapdoor to look for hitherto unreported
viruses.
Internet access is protected through the use of firewalls, crypto-
graphy, authentication devises and electronic signature systems.
System provides data management system features that allow for
integration and sharing of data among all applications.
Describe the file access methods used by the system. If there is
more than one, indicate the number and type of programs that use
each method.
How is overall system integrity and reliability achieved?

8.9 Disaster Prevention/Recovery Requirements
Functional Description                                                   A   B   C   D   E
Please respond to each question with summary answers whenever
applicable.
System provides a backup process that can be performed in a
dynamic mode so that the system can be operational 24 hours/day
File backup procedures are provided. Indicate recommendations
and time requirements.
System provides a data archiving process based on system
administrator criteria (e.g. time, data type).

                                                         32
System supports disaster recovery procedures. Describe and
estimate recovery time.
In the event of hardware/software failure, system can recover to
the point of failure. Describe.
System provides sufficient back-up and recovery feature to assure
minimal data loss after system failures.

9.0 Specific Functionality

Functional Description                                                A   B      C       D       E
Please respond to each question with summary answers whenever
applicable.
System supports inquiries to database to select and export data to
other systems. Describe limitations and security.
System provides a system-to-system link for the uploading and
downloading of data (e.g. existing systems, popular PC file forms).
System provides interface to allow archival of data.
System security maintained when integrating and communicating
with systems outside the vendor's system.
Encryption is used to protect sensitive data sent over networks.
Secure dial-in access, unique user Ids and passwords, limited
access times and limited connection duration are incorporated for
remote access. Token cards and dial back modems are supported.
System supports a multiple facility organization
System supports multiple printers
System supports printing to fax machines
System supports Internet Access


If your system utilizes any specialized equipment or 3rd party
products (i.e. construction databases, special hand held devices,
etc.), and if this recommendation will include the use of any of
these products, have you certified compliance for those products?
Does the system offer both financial and clinical decision support?
Can multiple users directly access the system simultaneously? To
what level of detail (i.e., summary level, transaction level)? Can
multiple users access the exact same record at the exact same
time?
Can the system handle the unique requirements of a multi-entity
organization from not only a reporting view but a file structure?
What file types can the system directly upload? The intent is to
avoid the needing to pay a fee while attempting to avoid manual
data entry?



10.0 Reporting
10.1     Does the system have the ability to generate standard and custom reports? If custom reports
        are defined by the University that varies from canned reports, is there an additional cost to do
        this?
10.2    Can reports be generated regularly (monthly, for example) as well as on an ad hoc basis.
10.3    Is the report writer menu-driven? Please describe the average training requirements for a
        user to be able to write reports. Please also define the amount of support provided to assist in
        the initial report writing phases.
10.4    Does the system supply a data dictionary?
10.5    What formatting features are available?
10.6    Do selection criteria print at the beginning of a report? How? In code or "plain English"?
                                                       33
10.7    Is page numbering possible? Optional?
10.8    Can system report be generated by selecting specific records?
10.9    Is it possible to sort on computed fields?
10.10   Does the report writer support unlimited summarization levels.
10.11   For such reports, is it possible to print a summary page at the end showing only the
        summation lines?
10.12   Is it possible to "collapse" criteria to control the number?
10.13   Is it possible to store extended search criteria in tables
10.14   Can users view reports on-line prior to printing? Can the user print form this screen view?
10.15   Is it possible to print to a file for downloading a report?
10.16   Is it possible to produce simple flat files for downloading? With delimiters?
10.17   Does the report writer allow users to qualify and catalogue a set of records?
10.18   Is it possible to include user-defined fields in any report?
10.19   NOT USED
10.20   Is there any limit to the number of data elements that can be added?
10.21   Does the report writer allow for complex conditions with multiple parenthetical clauses, AND's
        and OR's?
10.22   Is it possible to prevent certain sensitive fields from being printed on reports?
10.23   Is it possible to have a management report run in the background and still perform different
        functions on the same workstation?
10.24   Does the system enable users to determine how long it will take to run an on-line report?
        Give examples of how long a batch report takes to run for a system.
10.25   Does the report writer allow multiple time periods to be included in each report?
10.26   Can monthly reports include last year monthly and year-to-date figures?
10.27   NOT USED
10.28   Can the system generate graphical reports with charts, or does the user need to export data
        and create them in another program? Describe the process.
10.29   Can reports be batched, or must they be run one at a time?
10.30   Can reports prompt for run-time parameters?
10.31   What reports are pre-formatted (included with the system?) Please provide a list.
10.32   Is the report writer an in-house product, or third-party? If third party, which one? Describe.
10.33   How are reports catalogued? How does the user become familiar with which reports are
        already available?
10.34   Your system will no doubt generate numerous reports covering many important areas of
        concern. Describe how your system turns this wealth of data into manageable information --
        especially for non-technical users.

11.0 Multi Entity Considerations
11.1    Do you have experience with multi-entity IDN‟s and if so, which organizations.
11.2    How is your system capable of handling multi-facility organizations including branch
        campuses?
11.3    NOT USED.
11.4    For reporting purposes, will they automatically sort by campus location within the
        organization?
11.5    Will the individual entities have to share the same database, and if so, how is security
        maintained across the different organizations?
11.6    Does the system allow enough flexibility to look both within and across the multiple
        organizations for adequate comparisons and reporting considerations?
11.7    Can the costing be done differently at each organization (i.e.; one organization may treat one
        type of cost as overhead where another might treat the same cost as an indirect) and still
        allow for comparison.
11.8    From a corporate view is there an easy way to handle looking across all organizations but
        then drill down to the finest level of detail, without having to re-run reports or start over?
11.9    How is your system capable of handling multi-entity organizations which require complete
        separation of data?

                                                  34
12.0 Business Opportunities
Please describe any business opportunities available to the University such as:

„Development Partner‟ or:
„Beta Test Site‟

for this software package. Please explain clearly the business or financial benefits to the
University for either of these opportunities.




                                                   35
SECTION 4 EVALUATION CRITERIA

    RFP Evaluation Criteria: The award of an Agreement will be based upon a comprehensive review,
    analysis and negotiation of the proposal which best meets the needs of the University. The contract
    award will be based on a points-earned matrix derived from a technical and financial evaluation and
    potential site visit, product demonstration and/or business opportunity, if requested by the University.

    The award shall be made to the most responsive Bidder offering the best value and with the highest
    total matrix scores and if requested by the University, most satisfactory site visit, product
    demonstration and/or business opportunity, as determined by the University. All vendors submitting
    proposals concur with this method of award and will not, under any circumstances or in any manner,
    dispute any award made using this method.

    All proposals will be evaluated by a committee, which will use the specific evaluation criteria listed
    below. The importance given to each element is represented proportionately by the respective
    weight assignments. Proposals will be evaluated as to the Firm‟s response to the following criteria:

        Evaluation criteria

        1. Section 5.0 – Support and Services                                                  10 points

        2. Section 6.0 – System Processing/Environment Requirements                            10 points

        3. Section 7.0 – Software Technical Requirements                                       10 points

        4. Section 8.0 – General System Functionality                                          10 points

        5. Section 9.0 – Specific Functionality                                                10 points

        6. Section 10.0 – Reporting                                                            10 points

        7. Institution Experience :                                                             5 points
           Demonstrated experience assisting with the implementation of a Facilities
           CIMS three or more institutions or firms whose requirements were similar in
           size and scope to those of the University.

        8. CIMS Workflow Processes:                                                            10 points
           Experience assisting with the implementation of workflow
           processes for the Facilities CIMS

        9. References:                                                                         10 points

        10. Pricing :                                                                          15 points

                                                            Total maximum points available:    100 Points

           Site Visit results (if applicable)
           Product Demos & Presentation
           Business Opportunities

    Please Note: The forms listed below must be completed, signed, dated and returned with your
    proposal. Failure to do so may result in your proposal being rejected for noncompliance:

       NOTIFICATION TO BIDDERS FORM
       BIDDERS QUALIFICATION FORM
       REQUEST FOR PROPOSAL


                                                          36
FORM OF PROPOSAL FOR RFP # WH031604 UNIVERSITY OF CONNECTICUT

TO: University of Connecticut
Purchasing Department
3 North Hillside Road Unit 6076
Storrs, CT 06269-6076

The undersigned Respondent, in response to your request for proposal for the above contract, having
examined the proposal documents and being familiar with the conditions surrounding the proposed
contract, including the availability of labor and supplies, hereby propose to provide services in
accordance with these documents and submit for your consideration the following unit costs

Respondent hereby acknowledges receipt of the following addenda that are a part of the proposal
documents:

       NO.    1   , Dated

       NO.    2   , Dated

       NO.    3   , Dated

Respondent understands that the university reserves the right to reject any and all proposals, waive
irregularities or technicalities in any proposal, and accept any proposal in whole or in part which it
deems to be in its own best interest.

Respondent agrees that this proposal shall be good and may not be withdrawn for a period of sixty
(60) calendar days after the public opening and reading of the proposals.

Respondent hereby certifies: a) that this proposal is genuine and is not made in the interest of or on
behalf of any undisclosed person, firm or corporation; b) the Respondent has not directly or indirectly
induced or solicited any other Respondent to put in a false or sham proposal; c) that the Respondent
has not solicited or induced any person, firm or corporation to refrain from bidding; and d) that the
Respondent has not sought by collusion to obtain any advantage over any other Respondent or over
the university.

Date submitted:                      2004

Firm name:

Address:

City and State:                                                     Zip Code:

By:                                                                 Title:
       Signature of Owner or Authorized Officer

Telephone #                                                         Facsimile #




                                                   37
     FORM OF PROPOSAL                FOR RFP #WH031604

     Fees:

1.      Total software license package cost (attach breakdown by module and seat fees if any):

                                                                          ($               )
                            Written figures

2.      Maintenance Fees Per Year (attach maintenance fee schedule for additional seats, if any)

                                                                          ($               )
                           Written figures
     State annual escalation rate, if any, for five year period.          (                )

3.      ASP Hosting (if applicable):

                                                                          ($               )
                           Written figures
     State annual escalation rate, if any for five year period.           (                )

4.      Applicable Hardware cost, if any (attach hardware specification data):

                                                                          ($               )
                            Written figures

5.      Estimate Customization cost based on 1500 hours:

                                                                          ($               )
                            Written figures

6.      Provide hourly rate for customization beyond 1500 hours                            Unit:
        Hour

                                                                          ($       )$      /Hour
                            Written figures

7.      Provide hourly rate for interface development                              Unit:   Hour

                                                                          ($       )$      /Hour
                            Written figures


8.      Other:

                                                                          ($               )
                            Written figures


9.      If applicable, indicate any anticipated expenses, to be billed at cost:

         _________________________________________________________________________
         _________________________________________________________________________
                                                                                                   38
STATE EXCEPTIONS TO THE SPECIFICATIONS:


     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________

     ______________________________________________________________________



                                                                         39
FORM OF PROPOSAL WH031604

List any other services available from your company. Please provide a description of services,
standard hourly rate and discounted rate that would be extended to the University for this
contract.

Item No.      Item Description - Unit price in words                      Unit price in figures

Describe service:



              Standard Hourly Rate:

                                                                          $
                      Written figures


              Discounted Hourly Rate:

                                                                          $
                      Written figures


Describe service:



              Standard Hourly Rate:

                                                                          $
                      Written figures


              Discounted Hourly Rate:

                                                                          $
                      Written figures


Describe service:



              Standard Hourly Rate:

                                                                          $
                      Written figures

              Discounted Hourly Rate:

                                                                          $
                      Written figures

                                                                                                  40
FORM OF PROPOSAL FOR RFP #WH031604

Please provide suggested implementation schedule.

In the space below, list references:

       No.     Name                                 Name of contact person
               Address                              Telephone number
               Email address

       1.      _______________________________

               _______________________________

               _______________________________


       2.      _______________________________

               _______________________________

               _______________________________


       3.      _______________________________

               _______________________________

               _______________________________


       Enclosures:

       References Included:
        Yes  No

       Resumes Included:
        Yes  No

       Portfolio Included:
        Yes  No




                                                                             41
                                     NOTIFICATION TO BIDDERS

The contract to be awarded is subject to contract compliance requirements mandated by Section 4a-60
(formerly 4-14a) of the Connecticut General Statutes; and, when the awarding agency is the state, Section
46a-71(d) of the Connecticut General Statutes. There are Contract Compliance Regulations codified at
Section 46a-68j-1 et.seq. of the Regulations of Connecticut State Agencies which establish a procedure
for the awarding of all contracts covered by Sections 4a-60 and 46a-71(d) of the Connecticut General
Statutes. According to Section 46a-68j-30(9) of the Contract Compliance Regulations, every agency
awarding a contract subject to the contract compliance requirements has an obligation to “aggressively
solicit the participation of legitimate minority business enterprises as bidders, contractors, subcontractors,
and suppliers of materials.” “Minority business enterprise “ is defined in Section 4a-60 of the Connecticut
General Statutes as a business wherein fifty-one percent or more of the capitol stock, or assets belong to
a person or persons: “(1) Who are active in the daily affairs of the enterprise; (2) who have the power to
direct the management and policies of the enterprise; and (3) who are members of a minority, as such
term is defined in sub-section (a) of Section 32-9n.” “Minority groups are defined in Section 32-9n of the
Connecticut General Statutes as “(1) Black Americans; (2)Hispanic Americans; (3) Women; (4) Asian
Pacific Americans and Pacific Islanders; or (5) American Indians or (6) Disabled Persons”. The above
definitions apply to the contract compliance requirements by virtue of Section 46a-68j-21(11) of the
Contract Compliance Regulations.

The awarding agency will consider the following factors when reviewing the bidder‟s qualifications under
the contract compliance requirements:

        (a) The bidder‟s success in implementing an affirmative action plan;
        (b) The bidder‟s success in developing an apprenticeship program complying with sections
            46a-68-1 to 46a-68-17 of the Connecticut General Statutes, inclusive;
        (c) The bidder‟s promise to develop and implement a successful affirmative action plan;
        (d) The bidder‟s submission of EEO-1 data indicating that the composition of its work force is at
            or near parity when compared to the racial and sexual composition of the work force in the
            relevant labor market area; and
        (e) The bidder‟s promise to set aside a portion of the contract for legitimate minority business
            enterprises. See Section 46a-68j-30(10)(E) of the Contract Compliance Regulations.

*INSTRUCTION: Bidder must sign acknowledgment below, and return acknowledgment to the awarding
agency with bid proposal.


The undersigned acknowledges receiving and reading a copy of “Notification to Bidders” form.


Signature: ___________________________________________

Date: _________________________________

On Behalf of: _____________________________________________________

RFP NUMBER-________________________________


OPENING DATE-______________________________




                                                                                                           42
                                          BIDDERS QUALIFICATIONS CHART
                                 COMPLETION REQUIRED FOR CONSIDERATION OF AWARD

The University requires the completion of this BIDDERS QUALIFICATION CHART under the contract compliance requirements mandated by Section
C.G.S. 4a-60 and Section 46a of the Connecticut General Statues and will consider your answers in making an award.

          1.     Have you implemented an Affirmative Action Plan?
                  YES___________________ NO________________

                 1a.   If yes, date implemented______________________

          2.     If answer to #1 is no, do you intend to develop an Affirmative Action Plan?
                   YES___________________ NO________________

                 2a.   If yes, date you plan to implement_______________

          3.     Have you implemented an apprenticeship program complying with Section 46a-68f of the Connecticut General Statutes?
                   YES___________________ NO________________

          4.     If the answer to #3 is no, do you intend to develop an apprenticeship program?
                   YES__________________ NO________________

          5.     Please provide the following equal employment opportunity data (EEO-1)


                                                           MALE                                                              FEMALE
JOB                    Overall   White        Black        Hispanic     Asian       American     White        Black          Hispanic   Asian        American
CATEGORIES             Totals    (Not of      (Not of                   or          Indian       (Not         (Not                      or Pacific   Indian
                       (Sum of   Hispanic     Hispanic                  Pacific     or           of           of                        Islander     or Alaskan
                       col. B    Origin)      Origin)                   Islander    Alaskan      Hispanic     Hispanic                               Native
                       thru K)                                                      Native       Origin)      Origin)

                       A         B            C            D            E           F            G            H              I          J            K
1.   Officials &
Managers
2.Professionals
3. Technicians
4.Sales Workers
5.Office/Clerical
6.Craft Workers
(Skilled)
7.Operatives
(Semi-skilled)
8. Laborers (un-
skilled)
9.Service
Worker
10. TOTAL


          6.     Do you intend to set aside a portion of this contract for legitimate minority business enterprises (MBE)?

                 YES___________________ NO________________


COMPANY:                   Name____________________________________ TYPE OF CO. _______________________________


NAME 0F OWNER:             _________________________________________FEIN: ______________________________________


INFORMATION:               Address: _____________________________________________________________________________

                            ____________________________________________________________________________________


                           Signature______________________Date______________Tel#________________
(Revised 3/9/99)




                                                                                                                                                         43
                                                                   ATTACHMENT A

A.Provisions of this Contract Required by Connecticut General Statutes 4a-60

(a) Every contract to which the State or any political subdivision of the State other than a municipality is a party shall contain the following provisions: (1)
The Contractor agrees and warrants that in the performance of the contract such Contractor will not discriminate or permit discrimination against any
persons or group of persons on the grounds of race, color, religious creed, age, marital status, national origin, ancestry, sex, mental retardation or
physical disability, including but not limited to blindness, unless it is shown by such Contractor that such disability prevent performance of the work
involved, in any manner prohibited by the laws of the United States or of the State of Connecticut. The Contractor further agrees to take affirmative
action to insure that applicants with job-related qualifications are employed and that the employees are treated when employed without regard to their
race, color, religious creed, age, marital status, national origin, ancestry, sex, mental retardation or physical disability, including but not limited to
blindness, unless it is shown by such Contractor that such disability prevents performance of the work involved;(2) the Contractor to state that is an
“affirmative action-equal opportunity employer” in accordance with regulations adopted by the Commission; (3) the Contractor agrees to provide each
labor union or representative of workers with which such Contractor has a collective bargaining agreement or other contract or understanding and each
vendor with which such Contractor has a contract or understanding, a notice to be provided by the Commission advising the labor union or worker‟s
representative of the Contractor‟s commitments under this section, and to post copies of the notice in conspicuous places available to
employees and applicants for employment; (4) the Contractor agrees to comply with each provision of this section and sections (46a-68e) and (46a-68f)
and with each regulation or relevant order issued by said Commission pursuant to sections (46a-56),(46a-68e) and (46a-68f); (5) the contractor agrees
to provide the Commission on Human Rights and Opportunities with such information requested by the Commission , and permit access to pertinent
books, records and accounts, concerning the employment practices and procedures of the Contractor as related to the provisions of this section and
section (46a-56). If the contract is a public works contract, the Contractor agrees and warrants that they will make good faith efforts to employ minority
business enterprises as subcontractors and suppliers of materials on such public works project.
(b) For purposes of this section, “Minority Business Enterprise” means any small Contractor or supplier of materials fifty-one percent or more of the
capitol stock, if any, or assets of which is owned by a person or persons: (1) who are active in the daily affairs of the enterprise, (2) Who have the power
to direct the management and policies of the enterprise and (3) who are member of a minority, as such term is defined in subsection (a) of section (32-
9n); and “good faith efforts” shall include, but shall not be limited to, those reasonable initial efforts necessary to comply with statutory or regulatory
requirements and additional or substituted efforts when it is determined that such initial efforts will not be sufficient to comply with such requirements.
(c) Determination of a Contractor‟s good faith efforts shall include but not be limited to the following factors: The Contractor‟s employment and
subcontracting policies, patterns and practices; affirmative advertising, recruitment and training; technical assistance activities and other such
reasonable activities efforts as the Commission may prescribe that are designed to ensure the participation of minority business enterprises in public
works projects.
(d) The Contractor shall develop and maintain adequate documentation, in a manner prescribed by the Commission, of its good faith efforts.
(e) The Contractor shall include the provisions of subsection (a) of this section in every subcontract or purchase order entered into in order to fulfill any
obligation of a contract with the State and such provisions shall be binding on the subcontractor, vendor or manufacturer unless exempted by
regulations or orders of the Commission. The contractor shall take such action with respect to any subcontract or purchase order as the Commission
may direct as a means of enforcing such provisions including sanctions for noncompliance in accordance with section (46a-56); provided, if such
Contractor becomes involved in, or is threatened with litigation with a subcontractor or vendor as a result of such direction by the Commission, the
Contractor may request the State of Connecticut to enter into any such litigation or negotiation prior thereto to protect the interests of the State and the
State may so enter.

B.Provisions of this Contract Required by Connecticut General Statutes 4a-60a

(a) The Contractor agrees to the following provisions: (1) The Contractor agrees and warrants that in the performance of the contract such Contractor
will not discriminate or permit discrimination against any person or group of persons on the grounds of sexual orientation, in any manner prohibited by
the laws of the United States or the State of Connecticut, and that employees are treated when employed without regard to their sexual orientation; (2) )
the Contractor agrees to provide each labor union or representative of workers with which such Contractor has a collective bargaining agreement or
other contract or understanding and each vendor with which such Contractor has a contract or understanding, a notice to be provided by the
Commission advising the labor union or worker‟s representative of the Contractor‟s commitments under this section, and to post copies of the notice in
conspicuous places available to employees and applicants for employment; (3) the Contractor agrees to comply with each provision of this section and
sections (46a-68e) and (46a-68f) and with each regulation or relevant order issued by said Commission pursuant to sections (46a-56),(46a-68e) and
(46a-68f) of the General Statutes
(b) The Contractor agrees to provide the Commission on Human Rights and Opportunities with such information requested by the Commission , and
permit access to pertinent books, records and accounts, concerning the employment practices and procedures of the Contractor as related to the
provisions of this section and section (46a-56). If the contract is a public works contract, the Contractor agrees and warrants that they will make good
faith efforts to employ minority business enterprises as subcontractors and suppliers of materials on such public works project.
(c) The Contractor shall include the provisions of subsection (a) of this section in every subcontract or purchase order entered into in order to fulfill any
obligation of a contract with the State and such provisions shall be binding on the subcontractor, vendor or manufacturer unless exempted by
regulations or orders of the Commission. The contractor shall take such action with respect to any subcontract or purchase order as the Commission
may direct as a means of enforcing such provisions including sanctions for noncompliance in accordance with section (46a-56); provided, if such
Contractor becomes involved in, or is threatened with litigation with a subcontractor or vendor as a result of such direction by the Commission, the
Contractor may request the State of Connecticut to enter into any such litigation or negotiation prior thereto to protect the interests of the State and the
State may so enter.




                                                                                                                                                             44
Pur.17 (Rev.3/9/99)

INSTRUCTIONS TO BIDDERS

1.   All bids must be submitted on and in accordance with this form. If more space is required to furnish a description of the commodities and/or
     services offered or delivery terms, the bidder may attach a letter hereto which will be made part of the bid.

2.   Bids and amendments thereto, or withdrawal of bids submitted, if received by the University after the date and time specified for the bid opening,
     will not be considered.

3.   Prices should be stated in units of quantity specified, with packing and delivery to destination included.

4.   The time of proposed delivery must be stated in definite terms. If time of delivery for different commodities varies, the bidder shall so state.

5.   Samples, when requested, must be furnished free of expense and if not destroyed, will, upon request, be returned at the bidder‟s risk and
     expense.

6.   Bids must show unit price, amount and grand total or bid may be rejected.

7.   Unless qualified by the provision “NO SUBSTITUTE” the use of the name of a manufacturer, brand, make or catalog designation in specifying an
     item does not restrict bidders to the manufacturer, brand, make or catalog designation identification. This is used simply to indicate the character,
     quality and/or performance equivalence of the commodity desired, but the commodity on which proposals are submitted must be of the same
     character, quality and/or performance equivalence that it will serve the purpose for which it is to be used equally as well as that specified. In
     submitting a proposal on a commodity other than as specified, bidder shall furnish complete data and identification with respect to the alternate
     commodity he proposes to furnish. Consideration will be given to proposals submitted on alternate commodities to the extent that such action is
     deemed to serve best the interests of the State. If the bidder does not indicate that the commodity he proposes to furnish is other than specified, it
     will be construed to mean that the bidder proposes to furnish the exact commodity described.

8.   In the event that you are unable to submit a proposal against this bid, we will appreciate your advising this office to that effect. Failure to submit
     proposals against three consecutive bids will result in you name being removed from the mailing list, unless a specific request is made in writing
     for the retention of your name on said list.

9.   The contractor agrees and warrants that in the performance of this contract he will not discriminate or permit discrimination against any person or
     group of persons on the grounds of race, color, religion, national origin, sex, age, physical disability, including but not limited to blindness, or
     learning disability, unless it is shown by such contractor that such disability prevents performance of the work involved in any manner prohibited by
     the laws of the United States or of the State of Connecticut, and further agrees to provide the Commission on Human Rights and Opportunities
     with such information requested by the Commission concerning the employment practices and procedures of the contractor as related to the
     provisions of this contract.

10. This contract is subject to the provisions of Executive Order No. Three of Governor Thomas J. Meskill promulgated June 16, 1971 and, as such,
    this contract may be canceled, terminated or suspended by the State Labor Commissioner for violation of or noncompliance with said Executive
    Order No. Three, or any state of federal law concerning nondiscrimination, notwithstanding that the State Labor Commissioner is not a party to this
    contract. The parties to this contract, as part of the consideration hereof, agree that Executive Order No. Three is incorporated herein by reference
    and made a part hereof. The parties agree to abide by said Executive Order and agree that the State Labor Commissioner Shall have continuing
    jurisdiction in respect to contract performance in regard to nondiscrimination, until the contract is completed or terminated prior to completion. The
    contractor agrees, as part consideration hereof, that this contract is subject to the Guidelines and Rules issued by the state labor commissioner to
    implement Executive Order No. Three, and that he will not discriminate in his employment practices or policies, will file all reports as required, and
    will fully cooperate with the State of Connecticut and the state labor commissioner.

11. This contract is subject to the provisions of Executive Order No. Seventeen of Governor Thomas J. Meskill promulgated February 15, 1973, and,
    as such, this contract may be canceled, terminated or suspended by the contracting agency of the State Labor Commissioner for violation of or
    noncompliance with said Executive Order No. Seventeen , notwithstanding that the State Labor Commissioner may not be a party to this contract.
    The parties to this contract, as part of the consideration hereof, agree that Executive Order No. Seventeen is incorporated herein by reference and
    made a part hereof. The parties agree to abide by said Executive Order and agree that the contracting agency and the State Labor Commissioner
    shall have a joint and several continuing jurisdiction in respect to contract performance in regard to listing all employment openings with the
    Connecticut State Employment Service.

12. The University of Connecticut is an equal opportunity employer.




                                                                                                                                                        45
                                            AWARD AND CONTRACT

1.   The University reserves the right to award by item, groups of items or total bid; to reject any and all bids in
     whole or in part, and to waive any informality or technical defects if, in its judgment, the best interests of
     the University will be served.

2.   Cash discounts may be offered by bidder for prompt payment of bills, but such discount will not be taken
     into consideration in determining the low bidder but will be taken into consideration in awarding tie bids.
     The discount period will be computed from the date delivery is accepted at destination or from date correct
     invoice is received by the consignee, whichever is the later date.

3.   ACCEPTANCE OF A BID BY THE UNIVERSITY IS NOT AN ORDER TO SHIP.

4.   Each bid is received with the understanding that the acceptance in writing by the University of the offer to
     furnish any or all of the commodities and/or services described therein, shall constitute a contract between
     the bidder and the University, which shall bind the bidder on his part to furnish and deliver the articles
     quoted on at the prices stated and in accordance with the conditions of said accepted bid; and the
     University on its part to order from such contractor, except for causes beyond reasonable control; and to
     pay for , at the agreed prices, all articles specified and delivered.

5.   In event of default by the contractor, the University reserves the right to procure the commodities and/or
     services from other sources, and hold the contractor liable for any excess cost occasioned thereby. If,
     however, public necessity requires use of material or supplies not conforming to the specifications, they
     may be accepted and payment therefore shall be made at a proper reduction in price.

6.   The contractor guarantees to save the University, its agents or employees, harmless from liability of any
     nature or kind, for use of any copyrighted or uncopyrighted composition, secret process, patented or
     unpatented invention, articles or appliances furnished or used in the performance of the contract, of which
     the contractor is not the patentee, assignee or licensee.

7.   It is understood and agreed that the contractor shall not be held liable for any failure or delays in the
     fulfillment of his contract arising from strikes, fires, or acts of God, or any other cause or causes beyond
     his reasonable control.

8.   In the event there is a need for material bonding, performance bonding and/or insurance, the bidder will
     provide the bonding and/or insurance when requested and do this within fifteen (15) days after receipt of
     our notification of apparent low bidder, otherwise, the University.




                                                                                                                 46
                                                       Exhibit ‘A’

       5    The product as delivered meets the requirement with no modifications or user effort required.

       4    The product does not meet the requirement as delivered but is scheduled to be modified to
            include the feature within 6 months of the installation of the software.
       3    The product as delivered if configured by the Customer, by updating a table or other high level
            setting, meets the requirement.
       2    The product as delivered does not meet the requirement. The requirement could be met
            practically through modifications to the logic of the product made by the Customer utilizing a
            high level language or toolkit provided by the vendor for this purpose. The toolkit would then be
            responsible for generating all necessary replacement source code, including database
            descriptions, help files, etc.
       1    The product as does not meet the requirement. The requirement can only be met by the
            vendor or Customer making changes directly to the base source code of the product. If this
            value is selected, please include an estimate of the effort and cost involved to make this
            change or addition. (Add Alternate – time and cost)
       0    The requirement is not met by the system as delivered and it is not practical for the vendor or
            the Customer to make any sort of modification to the system to incorporate the change.



                                                                                    Product
                                                                                    provides
                                                     REQUIREMENT        MATCH       feature
SYSTEM SETUP                                         CODE               CODE        y/n         COMMENTS
GENERAL PRODUCT INFORMATION
Product shall be developed utilizing fully                   4
integrated technology from a single vendor.
Critical products include the database, client and
web server.
The system must be such that moving from
function to function is seamless or undetectable
by user                                                      4
Access and use by the customer must be very
easy and understandable                                      4
The installation of applications requires an
enormous amount of time to input into the
system. Please identify tools and import/export
tools that are included with the product.                    4
Based on the deployment methodology various
security considerations need to be address
please address them for inside the firewall and or
outside the firewall (ASP) installations                     4
The vendor success record is important,
please identify the 5 largest applications that
you have up and running and identify any
access speed issues.
 1. (client/ contact person/ phone number)                   4
 2. (client/ contact person/ phone number)                   4
 3. (client/ contact person/ phone number)                   4
 4. (client/ contact person/ phone number)                   4
 5. (client/ contact person/ phone number)                   4
This product is a Web - enabled solution.
Please identify what program language is
being used
  1. Web based without middleware                            4
  2. Client Server -web emulator (i.e. Citrix)               1
                                                                                                                47
Identify the main modules of your product
relating to Space Management (CAFM),
Maintenance Management (CMMS),
Construction and Project Management
(CM/PM), GIS,                                        4
The product allows every web page to incorporate     3
graphics.
The product allows special formatting capabilities   2
for alerts and special messages appearing on
web pages or forms.
Security Manager
Describe your security system (application and       4
database)
Log In                                               4
User Group                                           4
User Roles                                           4
Mail                                                 3
System                                               3
Forms                                                2
Viewer(s) setup                                      2
drawing audits                                       2
Reporting                                            4
Import/ Export (please list/ describe)               4
INTERFACES
  1. This product interfaces with ISES FCA           3
  2. This product interfaces with UCONN FRS
financial software                                   4
  3. This product interfaces with Peoplesoft
software                                             4
The product provides the facilities to conduct       2
electronic commerce (E-commerce) with
departmental and campus customers.
Search results can be displayed in tables that       3
include links to detailed records.
Reports can be generated by the customer,            2
including cost summary reports and work order
status reports.
The product provides configurable email links to     2
departmental functions and employees.
The product can alert designated Facilities          2
Management personnel when actual costs are
nearing estimated or budgeted costs.

Business Process flow
The product has the ability to change the look,
feel, field headings, calculations, add/hide data
fields and modify the application to fit the way
UCONN works.                                         3
The product can be tailored to particular business
requirements and move information through the
organization for approvals and work flow             3
Business Object Editor                               3
Business Object Builder                              3
CAD and GIS tools


                                                         48
Identify and discuss the CAD tools provided to
implement drawings and link databases                 4
Identify and discuss the GIS tools provided to
implement graphic presentations and link
databases.                                            4
TRAINING
Super User                                            4
End User                                              4
Administration and User Manuals                       4
Training Manuals                                      4
Provide Web Based Training                            3
Provide custom report writing training
Provide On-site training                              4
LICENSING OF APPLICATION
Per concurrent user                                   3
Site license / unlimited users                        4
State license / unlimited users                       4
ASP                                                   4
MAINTENANCE Fees
Describe maintenance fees and what they cover         4
Describe ASP / yearly fee                             4
REPORTS
Describe the system's overall design and
approach to creating reports                          4
Identify which reporting applications your system
works with                                            4
Reports shall be exported to a wide range of file
formats, Please list your formats (i.e., XML, word,
excel, adobe, etc.)                                   4
All reports shall have a "screen view - print
preview" and print setup mode to make report
adjustments.                                          4
Reports shall be routed to any networked printer      4
Reports shall be linked to a user defined pick list
within the browser and shall generate the viewed
report from the database                              3
PLEASE LIST ALL SYSTEM FEATURES THAT
ARE UNIQUE TO YOUR PRODUCT AND NOT
LISTED



MOBILE
Meter reading
Work Orders
Time sheets
Users should be able to query work orders real-       3
time using wireless hand held devices
Users should be able to enter time on work            3
orders, real-time on hand held devices.
Users should be able to issue material related to     3
work orders on handheld real-time.
Hardware requirements


                                                          49
Provide the hardware requirements for your
application if client's decision is to purchase the
software.                                                   4
System should have fully integrated, role based             4
security with access defined within each screen,
form and report.
Product should have the ability to support multiple         4
locations/departments from the same database
with users from each isolated from the data of
others.
System should have user configurable menus                  4

Each record in the system should have an
attachment feature allowing easy storage and
retrieval of notes and any related file of any type.        4

                                                                             Product
                                                                             provides
                                                       REQUIREMENT   MATCH   feature
SPACE MANAGEMENT (CAFM)                                   CODE       CODE    y/n        VENDOR COMMENTS
CAFM Modules
Property / Lease Management                                 3
Space Management                                            4
Organizational Management                                   4
Move Management                                             4
Asset Management                                            4
Room Scheduling                                             2
Research / Grant Management                                 4
Environmental Management                                    4
Utility Management                                          4
Document Management                                         4
GIS / CAD                                                   4
Drawing setup/ database
CAD / Database Interface
The system shall provide a bi-directional interface
with AutoCAD (identify what release)                        4
Describe how the CAD drawings are incorporated
into the database
CAD Setup tools (Please list/ describe: i.e.,
layering, conversion tools, etc.)                           4
What CAD applications (automated tools) does
the product support?
The product should have a automated room
numbering function
 What native drawing files types does the
application support                                         4
The product‟s AutoCAD interface should have the
option of creating DWF versions of the drawings
with the room ID‟s being HTML links.                        3
Graphical assignment of a space to multi-
organizations
Advanced query system to query database for
display within the CAD drawings (minimum:
room, organization, personnel, equipment, work
orders, work order histories, non-serialized
assets, and boundaries.)
Assign, identify, move, drawing objects in a
drawing and/or to a second drawing keeping the
object attribute and relational database
information intact.
                                                                                                          50
The product should have the ability to produced
graphical reports in AutoCAD, upon request, by
seamlessly connecting to the Space Inventory
Database. Reporting should include colorizing,
annotating as well as hatching the drawing
without the requester using AutoCAD.                   3
The product should allow for real-time reports in
AutoCAD of all room data stored in the space
database without data re-entry.                        3
How do you modify / delete rooms and please
explain the process of tracking the history of
these changes                                          4
How does the application do Area calculations
(please identify how areas are calculated)             4
How does the application identify room numbers         4
How does the application do room counts
Does it Store additional data / attributes / related
data with each space                                   4
Does it have User defined fields                       4
WinSABA - stack /block - please explain
planning functions                                     3
How do you assign ownership to a space                 4
Can you Pre-assign groups based on
requirements                                           4
Relationships                                          3
Drawing audits                                         4
Describe location hierarchy (how many levels)          3
Describe organizational hierarchy (how many
levels)                                                3
GIS setup tools
Identify GIS application - integration with your
product                                                4
Graphic queries                                        4
Scenarios                                              3
Printable                                              4
PROPERTY / LEASE MANAGEMENT
User definable fields to reflect multi-site, multi-
location organizational structure                      4
The ability to catalog and sort properties by
region                                                 4
The ability to create parent-child relationships       4
The ability to define standards (n-tier)               3
   * Representative types (agent, contractor, etc)     3
   * Building classifications (Office, Lab,
classroom, residential, etc.)                          4
  *Building representative (person representing
building)                                              3
   * Services provided (phone, IT, Trash,
Custodial, etc)                                        3
   * Land Use (zoning, etc.)                           3
Link detailed cost and payment details that can
be associated to lease records                         3
Define charge backs and cost centers for each
land record                                            4
Space Standards, room records, square footage,
(usable gross, core, common and percentages of
rentable space), capital assts, personnel, etc.        4
Lease Management, calculate monthly/annual
lease costs, status codes, time lines                  4


                                                           51
Contracts, Federal EIN, credit limit, credit period,
cost centers                                           3
Subleases                                              3
Taxes                                                  3
Parking                                                3
Service Agreements                                     3
Ticklers                                               4
Rental Management                                      3
Graphical and database queries                         4
Service Agreements, Contracts linked to Work
Order system                                           4
History                                                4
Audit trails                                           4
SPACE MANAGEMENT
Describe the space hierarchy (levels)                  4
Describe how and where Square footage is used
in the application                                     4
Describe how Space types and requirements are
setup
Describe how the multi-employees are tracked to
one location
Describe how multi-locations are set up for one
employee
Describe how space utilization is tracked /
managed
  Charge backs based on utilization
Describe how non-serialized equipment is tracked
Describe stacking/blocking and relationship
functionality
SPACE INVENTORY
Square Footage]
  roll up information by location /organization (n-
tier)                                                  4
Create space scenarios / modify / save / update
to database                                            4
Space Type, Personnel space requirements               4
Space Use                                              4
Ownership of space                                     4
Organization / using space                             4
Utilization, Occupancy status                          4
Charge back                                            4
Research Grant allocation                              4
Asset Depreciation                                     3
Graphical and database Queries                         4
MOVE MANAGEMENT
Describe Move process on a single floor, multi-
floors within the same buildings, between
buildings, between sites (graphically and by
forms) including all related assets by personnel
(i.e., computer, phone, chair, files, etc.)            4
Describe Reservations for moves, budgets,
schedules,                                             4
Provide user-defined move "classes" (ie.
Construction, renovation, departmental, etc.)          3
WO creation for moves within Maintenance
Module                                                 4
Tracking personnel and assets                          4
Updates to HR, IT, Department, Phone, etc.             4
Win Saba                                               3

                                                           52
Space Utilization                                      4
Ownership                                              4
Status                                                 4
Generate / Trace Move W.O.                             3
Space type                                             4
Graphical display of move dates (to/from)              3
Multiple scenario's                                    3
Project Overview                                       3
RESEARCH FUNDING
  Dollar Density /SF                                   4
  Budgets                                              4
  F&A funding                                          4
  Ownership                                            4
  Utility Sharing                                      4
SPACE SCHEDULING
Space setup                                            4
AV Setup                                               3
Catering                                               3
Schedule                                               3
Rentals                                                3
GIS FRONT END
Graphic queries /Reports                               4
Scenarios                                              4
Color/Hatch                                            4
Print /cut-paste drawing                               3
Setup tools (Please list/ describe)                    4
Redlining functionality                                4
Site and Building drawings                             4
Viewer - Browser
Graphic queries /Reports (GIS and CAD)                 4
Describe how drawing relationships are set up
(i.e. Floors of a building, buildings to a campus,
campus's to a county/state)                            4
The product should provide a web-based function
allowing users to update space usage. This
facility should be real time and not require the
involvement of clerical personnel.                     3
The product should support the production of
annotated floor plans with legible plots without
annotation overlapping other annotation or walls.
When annotation does not fit within small rooms,
it should be dynamically written into a chart on the
drawing.                                               3
Create Scenarios and save them                         4
Identify Color/Hatch schema queries
(environmental, personnel, equipment, usage,
organization, etc.)
Stack diagrams (dynamic queries)                       3
Print /cut-paste drawing to reports                    3
CAD Setup tools (Please list/ describe)                3
Redlining functionality                                3
Site and Building drawings                             3
Describe how drawing information is viewed in a
browser                                                4
Describe how drawings are queried in the
browser                                                4
Please describe to what level this application is
integrated with the proposed CMMS                      4
ASSET VIEW

                                                           53
By Location                                          4
By Organization                                      4
By Asset type                                        3
Capitalized equipment should be inventoried in
the application and tied to specific building
locations.                                           3
ORGANIZATION VIEW
ownership (n-tier)                                   4
location (n-tier)                                    4
use                                                  4
utilization                                          4
Hierarchical organization model                      4
  graphical views (reports)                          4
  Organization charts                                4
Phone directories                                    4
Design online questionnaire or checklist             4
Employee information                                 4

VIEWERS
CAD / GIS                                            4
Web Presentation                                     4
Graphical Queries                                    4
Red line                                             4
Print /scale)                                        4
BAR CODING
Update with scanner (survey)                         4
add/ delete/                                         4
WO History                                           4
CAPITAL INVENTORY


REPORTING
e-mail                                               3
facsimile                                            3
print routing                                        4
Dynamic billboard                                    4
Dynamic calendaring                                  4
Canned Reports -- Identify the number of
"canned report" within product out of the box        4
Custom reports on the fly                            4
Viewable reports on the web                          4
E-mail reports                                       4
export reports                                       4
Identify report engine and ability for UCONN to do
custom reports                                       4
FINANCIAL DETAILS
Asset Depreciation Policies                          4
Set Residual values                                  4
Depreciation start date                              4
Monthly straight-line depreciation                   4
Asset Acquisition handling                           4
Disposal methodology                                 4
forecast depreciation                                4
Expected life                                        4
Life cycle costing                                   4
Purchase cost                                        4
Billing related to rental properties and utilities   4
Interface into UCONN FRS system                      4

                                                         54
AUDIT TRAIL
exception Report                                          4
PLEASE LIST ALL SYSTEM FEATURES THAT
ARE UNIQUE TO YOUR PRODUCT AND NOT
LISTED


                                                                           Product
                                                                           provides
                                                     REQUIREMENT   MATCH   feature
MAINTENANCE MANAGEMENT (CMMS)                           CODE       CODE    y/n        Comments
CMMS Modules
Customer Request                                          4
Call Center                                               4
Contract management                                       4
Security / log in, user groups, individual, etc.          4
Work Order's                                              4
PM's                                                      4
Time Cards                                                4
Projects                                                  4
Serialized and non-serialized Equipment                   4
Warehousing/ Inventory                                    4
Integration into Financial package(s)                     4
Graphical Query                                           4
Reports                                                   4
CUSTOMER REQUEST
Web Based work request submittal                          4
Problem location different than requestor                 4
Help Desk                                                 4
Shop/ staff directory                                     4
Vender/Contractor/Consultant directory                    4
Direct work request/order entry                           4
Duplicate validation                                      3
Customer notification                                     3
WO authorization approval/rejection by e-mail             3
WO tracking through web                                   4
Graphical queries based on maps and floor plans           3
The product provides facilities to allow customers        3
to perform work requests via an on-line form
utilizing standard web browsers.
Audit trail                                               3
WORK ORDERS
System Setup (employee, shop, WO
type/problem codes, etc.)                                 4
Auto populate associated fields based on
customer, location, equipment, problem code,
shop, etc.                                                4
Standing, Rounds Work Orders                              4
Monitoring status of WO                                   4
Classify equipment conditions                             3
Classify cause of problem and final resolution            4
Maintain work order history                               4
Multiple phases per Work Order (multiple crafts)          4
Account information                                       4
Review project/ Work Order costs                          4
Provide the ability to break down projects into
multiple work orders and multiple phases)                 4



                                                                                                 55
Provide the ability to copy existing projects and/or
work orders to create new ones and then make
modifications.                                         4
Describe the scheduling process for work orders
for internal and external staffing.                    4
Describe the scheduling process for backlog,
emergency work, contractors, consultants,
vendors, etc.                                          4
Warranty trigger                                       3
Work order entry can be configured to generate         2
quality assurance questionnaires, customized
messages, surveys, etc., every "x" number of
work orders, and automatically report the results.
Work orders can be routed for review and               3
approval.
Describe how the supervisors process all work          4
requests and assignments for their staff and track
the daily work loads
Predefined jobs can be selected from a                 3
customizable pick list,
Resulting in fields such as assigned shop, job         4
type, and account number being subsequently
incorporated into the work order.
Work orders can be electronically routed to shops      4
and others.
A field identifying the work order data entry          3
operator is included.
Space, equipment, and asset descriptions and           3
work procedures can be included on work orders.
Scheduled maintenance work orders should be            3
generated automatically.
Conditions associated with work on equipment or        3
facility will validate and identify Hazardous
material locations, hazardous conditions such as
high voltage, confined space etc and flag if the
selected shop person is not certified to perform
the work effort.
Users can compare estimated vs. actual
expenses for both labor and materials on each
work order                                             3
Material costs shall be automatically tabulated
based on materials assigned                            4
System shall support charge backs to multiple
cost centers by percentage and/or dollar value         4
System shall provide means of attaching CAD
drawings or graphics to work order                     3
Describe the proposed solution's reporting
capabilities in regard to maintenance
management.                                            4
PREVENTATIVE MAINTENANCE
Describe application's approach to PM tasks.           4
PM Task List / by equipment                            4
assignment of PM task list to unlimited number of
assets                                                 4
assignment of PM's by equipment type or by
building                                               4
Assignment of PM's to multiple shops from one
Work Order                                             4
PM's can be assigned by meter, timed, fixed,
seasonal, yearly,                                      4
Track labor, materials, tools, expendables             4
                                                           56
  materials                                            4
  tools                                                3
PM Task List / by building                             4
PM Templates (reusable PM's - multiple equip.)         4
PM Scheduling (metered, fixed, timed, seasonal,
calendar, etc.)                                        4
Assignment to vendor, contractor or internal
staffing                                               4
Describe back door process for batch loading of
PM task lists into system                              4
Describe the process to set up PM time lines and
how product creates PM Work Orders                     4
The product should maintain a database of              3
information on assets and equipment, including
such items as type and location of asset,
manufacturer's specifications, serial number, etc.
Any asset can be designated as related to any          3
another asset with an unlimited number of such
relationships.
Assets and PMs can be associated in Route, by          4
reporting labor and closing the route costs will be
distributed to all items in the route and the entire
route closed in a single operation.
PM routes will record work history and costs for       4
each location/equipment in the route.
PM routes will allow for exceptions for incomplete     4
PM‟s.
The product can maintain the preventive                3
maintenance (PM) histories of assets and
equipment
Priorities can be assigned to assets and               3
equipment, and PM priorities can reflect asset
and equipment priorities.
The product can schedule PM orders by fixed or         3
sliding calendar intervals, usage, or on demand.
PM work orders can be automatically generated          3
by fixed date, last completion, meter reading,
conditions such as high or low limits, or alarms.
Preventive maintenance activities can be               3
scheduled on specified dates, days of the week,
days of the month, 1st Monday or work day of the
month, other user defined schedules, and may be
restricted to specified seasons.
Preventive maintenance orders are part of a            3
hierarchical arrangement whereby the scheduling
of certain PM orders prevents the scheduling of
other PM orders so that, for example, quarterly or
semi-annual PM orders should not be scheduled
at the same time as an annual PM order.
Sets of PM tasks can be defined for groups of          3
similar equipment.
Existing PM plans can be copied to create new          3
PM plans.
PM tasks and schedules can be assigned to              3
Equipment or to Building Locations
The product can record labor, material, and tools      3
required to perform each PM order.
Preventive maintenance procedure descriptions          3
can be any size of text and schematics; other
drawings can also be printed with the work order.


                                                           57
Any number of PM orders can reference                 3
predefined sets of PM procedures.
The product can project manpower requirements,        3
including type and number of personnel, for a
specified future time period, such as a week,
month, or year, based on information in property
management plans.
Preventive maintenance orders can be assigned         3
to specific employees or groups of employees.
The product can generate reports of overdue PM        3
orders.
The product can generate reports detailing            3
adherence of actual PM and materials used.
The product can aid in performing failure analysis    2
by providing reports such as failure frequency by
building, by component, by equipment type, by
manufacturer, by maintenance regimen, etc.
The product can track interrelated parts and          3
pieces and track work on all interrelated parts
and pieces.
The product can track history of all Customer         3
assets, equipment and materials.
The product can track financial data of all           3
Customer assets, equipment and materials.
The product can provide references to spare           3
parts associated with each item.
The product can show work history.                    3
The product can show relationships.                   3
The product can track service contracts and           3
warranties.
The product can track failure analysis.               3
The product can allow for definable tasks per         3
item and item groups.
EMPLOYEE
HR import / export                                    4
Employee information, pay rates                       4
certifications, work order triggers                   4
Training triggers                                     4
EQUIPMENT INVENTORY (serialized and
non-serialized)
Describe how the application manages serialized
 equipment                                            4
Describe how the application manages non-
serialized equipment - FF&E (assigned to
organization, cost center, locations)                 3
Equipment attributes, serial number, tag-bar
code. manufacture information, warranties,
specifications, etc) -- Duplicate tags not allowed)   4
Warranties / ticklers                                 3
Acquisition / history information                     4
Equipment hierarchies (parent-child/ from
systems, to assemblies, to individual parts)
Describe how user views this information              4
Define acceptable operating limits for condition      3
Equipment location hierarchies (n-tier) and
histories                                             4
Graphical Queries                                     4
Associated information                                4
External file links (CAD, images, graphs,
documents, spreadsheets, etc.)                        4

                                                          58
The product can store information on assets and      3
equipment such as buildings, rooms,
indoor/outdoor spaces and facilities,
infrastructure, tools, supplies, vehicles, trees,
manholes, and utility poles, ground area and
other items of value to the Customer.
Asset and equipment work order histories,            3
including accumulated costs can be recorded,
and these records are directly available from
asset record display windows.
Asset and equipment records can be linked to         3
detailed stored
Specifications and schematics.
Asset records can contain detailed lockout tag-      3
out procedures.
Asset records can contain or reference confined      3
space permits and instructions.
Asset and equipment records can include user-        3
definable fields
Indicating the presence and nature of hazardous
materials.
Failure codes and descriptions can be assigned       3
to asset records.
Asset and equipment records can contain a            3
history of condition
Asset and equipment records can contain cost         3
center account numbers to which costs can be
charged by default.
Asset and equipment records can contain or           3
reference information on warranties.
Work order data entry or queries should alert the    3
user to the existence of warranties on the assets
referenced by the work order.
The product alerts selected users to impending       3
expiration of warranties with user definable lead-
time.
WAREHOUSING / MATERIALS MANAGEMENT
Reorder process                                      4
max/min                                              4
just in time                                         4
reorder points (ROP)                                 4
Economic order Quantities (EOO)                      4
commodity codes                                      4
Multiple warehouses                                  4
Part / Bin levels                                    4
Parts catalog with photos                            4
Kits                                                 4
Vendors/ suppliers                                   4
Physical inventory updates                           4
Bar coding                                           4
Purchase requisitions (forms)                        4
Purchase Orders (credit cards/cash/voucher)          4
Request for quotes                                   4
Interface with financial packages (GAAP)             4
Receiving                                            4
  Incremental quantity delivery                      4
  Updates PO's                                       4
  Updates average-unit price                         4
Work Order input                                     4
  issues items to WO or department                   4
                                                         59
  Print Pick tickets for issue requests                4
The product can suggest order quantity based on        2
a user-defined maximum on-hand quantity.
The product can create a request for quotation         2
that can be edited while retaining sequential item
numbering and proper formatting.
The product can display both part cost as well as
selling price
The product can maintain separate on-hand              2
quantity, reorder point, and transaction history for
multiple stocking locations.
The product allows universal updates to markups,       2
commodity codes, etc.
Item records can contain or reference a note           2
field, which is not part of an item's description.
The product provides user-definable categories         2
that allow users to classify stock items as
"seasonal," "discontinued," "hazardous," etc.
The product can record commodity codes in a            2
user-definable format.
The product can record stock numbers of at least       2
eight (10) digits in a user-definable format.
Markup percentage can be defined by item or            2
class of item rather than universally.
Any transaction affecting on-hand quantity             2
increments or decrements updates on-hand
quantities immediately.
Items may be flagged as "No Reorder" to prevent        2
their appearance on reorder reports, but can be
issued to use up existing stock.
Part types such as „Benchstock‟ and „Direct‟ can       2
be used to allow flexibility in ordering and issuing
stock.
A user definable part index can be established to      2
allow users to place parts in simple easier to
understand categories for the purposes of user
query.
The product does not allow deleting items with         2
on-hand or on-order quantities.
Item records contain a separate field for              2
manufacturer part number.
Item records can include or can reference item         2
images.
The product can store Material Safety Data             2
Sheets for hazardous stock items.
The product can store date established, last           2
receipt date and last issued date.
The product can store quantity on-order and            2
expected due date (based on date entered by
purchaser on purchase order).
The extended description can be of any length.         2
Issues
The product provides a way to document the             2
physical issue of non- stock items received for a
work order, including a record of the stock items
received for a work order, including a record of
the date picked up and person accepting goods
from stores.
Items to be issued can be selected from a list of      2
query results.


                                                           60
The product can issue non-inventoried items             2
such as screws, nuts and bolts by dollar value
only.
The product alerts the user before creating a           2
back-order at the point of issue or does not allow
back-orders at issue.
The product allows no negative on-hand                  2
quantities.
The product offers a method to transfer costs of        2
items originally issued for truck stock to work
orders for which the items are ultimately used.
Issuing or returning an item, whether stock or          2
special order automatically charges or credits a
work order.
Issued items can be charged to either a work            2
order or a cost center.
When a user revises an incorrect issue                  2
transaction, the product implements the revision
by creating both a corrected charge transaction
and a credit transaction to negate the incorrect
issue, so that the user need not create these
transactions manually.
Receipts
Non-stock items can be received and issued              2
directly on a work order without passing through
inventory. A mark-up should still be charged for
these items.
The product can print a receiving worksheet             2
containing the items ordered as well as quantities
of items previously received, if any.
The product can record the receipt of items             2
procured by blanket purchase order.
A return transaction can be created that negates        2
a receipt transaction. This process would correct
changes to on-hand quantities and purchase
histories resulting from the original receipt
transaction, and annotate the purchase order to
reflect that received items have been returned.
The product can prohibit receipt in units other         2
than as ordered.
Physical Inventory
The user can establish variance thresholds              3
between physical and stored counts that can be
used to perform recounts of items outside the
variance threshold. The threshold can be either a
percentage of the count or it can be an absolute
dollar amount.
Items not found in an physical count are flagged        2
for recount if the stored quantity is not zero or are
freed from the inventory process if the stored
quantity is zero.
In support of a physical inventory the product can      3
generate a report that indicates:
     those items that have been flagged for                      
recount, 
     those that have been freed from the                         
inventory process, 
     those that have had their stored counts                     
adjusted, 
     those inventoried items which do not exist in               
the database, 
                                                                           61
    those stored items that do not appear in the                
physical inventory.
The authorized user can edit on-hand quantities.       2
The product can report net variances between           2
stored and physical count at any stage of the
recount and count adjustment process.
The product maintains a transaction history for all    2
adjustments made during the inventory process.
Product has the ability to Lock inventory by item,     2
row, commodity code or other attributes
The product can adjust recorded quantities             2
between count cycles due to variances between
actual and recorded quantities and can record
such adjustments as transactions.
TOOL CRIB MODULE
Tool Information                                       4
  Serialized                                           4
  Non - serialized                                     4
  Consumable (oil, solder, caulk, etc)                 3
Tool Boxes                                             3
  content                                              3
Check out/ in                                          4
Vendor/ purchase information                           4
Repair /rebuilt                                        3
  History of tools                                     3
Work Order assignment                                  3
Billable rates for use on Work Orders                  3
Audit trail of tool use                                3
KEY MODULE
electronic signature                                   3
Smart cards                                            3
Security status                                        3
The product can maintain a database of                 3
information on keys and locks, including such
items as lock location, on-hand and total key
quantities, key type (master, sub-master, etc.),
and date of last re keying.
The product can store multiple key levels              3
(master, sub-master, etc.) for the same door.
The product can track individual name, campus          3
address, telephone number, and/or other contact
information for keys issued and returned.
The product places no limits on the number of          3
keys that can be issued to a key holder.
The product has the ability to store information on    3
issue, return, lost, payment, and refund
transactions as well as transaction dates, with
whom transactions take place, and notes about
transactions.
The product can generate various reports,              3
including reports of key schedules, key
transactions, and key holders (such as a list of all
those having access to given areas).
The product can generate charge records that           3
may be used to bill departments for lost keys or
other key fees.
The product provide keys security hierarchy on         3
multi level (master, sub-master, departmental,
day key, entry level, entrances)


                                                                          62
The product supports query by multi level             3
(master, sub-master, departmental, day key,
entry level, entrances)(key number, key type,
building, location, room).
The product provides key catalog of pin settings      3
per lock.
The product provides on-line ability of request for   3
keys, authorization of request, and automatic
email notification to employee and authorizing
personnel of approval, issuance, and receipt of
keys.
The product prints receipts for key issues and        3
returns in real time.
WARRANTIES
Purchase date, end dates,                             4
Vendor information                                    4
Service Contracts: Extended warranties (Start,
stop)                                                 4
Date Ticklers                                         4
Emergency contact information                         4
PROJECTS
Multiple work orders, multiple shops                  4
Budgets, multiple cost centers                        4
CONTRACTOR/VENDOR/CONSULTANT
List of contractors, vendors, consultants and the
contract information                                  4
Contact Information                                   4
Equipment/ building/grounds assignments, etc          4
PURCHASE ORDERING
The product will integrate with UCONN                 3
Purchasing and Stores systems for materials on
order and issued for each work order.
Describe the PO process and how it updates
finance, the work order, the warehouse, etc.          4
UTILITIES MANAGEMENT
Meter setup: production, consumption, virtual,
etc.                                                  4
Meter Information                                     4
Meter Routes / schedules                              4
Historical Weather data / analysis                    4
Utility types (gas, water, steam, waste, etc.)        4
Invoicing: facility, department, space, other, etc.   4
Billings                                              4
  Tenant moves                                        4
  account re-allocation                               4
  Financial system integration/interface              4
REPORTING
Crystal Report Engine                                 4
Custom reports on the fly                             4
Viewable on the web                                   4
Canned Reports (how many)                             4
Graphical reports (charts and graphs)                 4
Graphical reports CAD - color/hatch                   4
Identify other special reports that your product
can provide                                           3
The product provides required reports for             3
budget/consumption analyses.



                                                          63
The product has the ability to group work orders,    3
i.e., perpetually open service contracts, specific
closing and perpetually open standing work
orders, Renovation & Job Order type projects
embracing one or more work orders and
reflection of original and work definitions and
change orders.
The product can generate Work Orders for             4
Locations, Equipment or both.
The product has the ability to generate and track    3
change orders to original work orders.
The product has the ability to store and view        2
documents associated with work orders (CAD,
Word, Excel, drawings, notes, etc.).
The product has the ability to store (and reuse on   3
other similar work orders) write-ups of work to be
performed.
The product has the ability to store worker          3
comments upon completion of work.
Work orders should include a variable length text    1
description of at least 500 characters.
Work order fields other than work order number       4
can be edited following entry.
The product can record information about work        3
requestors such as name, phone number,
department, and email address.
The product can record information about rental      3
equipment including charge out rates.
The product can record information about project     3
estimates as well as work order estimates.
The product can generate reports on actual           3
versus estimated costs.
The product integrates employee information with     3
the work order, including name, identification
number, salary, charges out rates, etc.
The product has the ability to estimate work at      3
detail shop level (electric, plumbing, carpentry,
and other FMD shops).
The product has the ability to store and view        3
detail write-ups of work to be done at shop level.
The product can create and manage projects           3
consisting of an unlimited number of sub-
projects, work orders, or activities.
The product allows detailed descriptions of          3
projects.
The product provides a database of common jobs       2
together with their typical labor, material, and
equipment requirements.
The product can reference an account number          3
within the general/subsidiary ledger module to
which costs should be charged.
The product can post charges to work orders          3
daily or more frequently.
Charges can only be posted to work orders that       3
have not been closed.
Unlimited items can be posted to work orders.        3
Labor, material, and equipment rental costs may      3
be posted to work orders interactively.
Miscellaneous user defined costs can be charged      3
to work orders.
Queries and Reports
                                                         64
The product can report items not issued within a      2
range of dates.
The product can report at least a year's monthly      2
issue summary reports.
The product can report items with a quantity of       2
zero.
The product can report orders not fully received      2
by due date.
The product can list requisitions not yet converted   2
to purchase orders.
The product can report the status of items            2
ordered against work orders, including current
status of an order, the purchase order number,
quantity ordered, quantity received to date, due
date, etc
The product can report stock items issued             2
against work orders.
The product can query purchase orders using           2
vendor name or partial vendor name.
The product can query purchase orders for non-        2
stock items using the item description or
wildcards.
The product can query purchase orders for non-        2
stock items using cost center number.
The product can query purchase orders for non-        2
stock or stock items using building code.
The product can query purchase orders for stock       2
items using stock number.
The product can print a daily report of all issue     2
activity for a specified date.
The product can print a daily report of all receipt   2
activity for a specified date.
The product can query, report, and sort items by      2
such criteria as stock number, commodity code,
short description, bin location and primary
vendor.
Query results are displayed with links to more        2
detailed information.
A complete audit trail is maintained for each         2
transaction by stock number or work order.
The product can report complete inventory             2
valuation using the Average Cost valuation
accounting method.
The product can query any item by manufacturer        2
part number.
The product can query and report summary
purchase history by craft and/or requestor.
The product can report the last five vendors from     2
which an item has been purchased.
Utilities Management
The product provides entry and inventory of utility   3
bill information.
Unique identifier for each meter. To include          3
master meters, sub meters, and tracking-only
meters.
Variable rate charges, updateable in real-time for    3
future billing
Ability to import current meter readings from text    3
file or from bar code reader as well as manual
data entry.

                                                          65
Ability to enter an invoice from an outside vendor     3
and calculate charges for billing.
Ability to assign percentages of a master meter to     3
a sub meter and have system calculate “left over”
amount to bill.
Ability to track in-house utility production as well   3
as outside utilities purchased.
The product allows multiple rate schedules from        3
various vendors.
The product provides projections based on what         3
if scenarios coupled with consumption for various
historical periods.
An alarm situation can be defined and reported.        3
The product provides for meter/sub-meter               3
reading storage and history.
The product provides billing of utilities              3
consumption with export of formatted
transactions to Customer Financial System.
The product provides cost breakdown with               3
reports.

Miscellaneous
Requisitions and purchase orders can be created        3
and/or updated by importing data exported from
the Customer's purchasing system.
The product can print a reorder list, and              2
automatically generate requisitions by vendor of
items at or below reorder point and sort by
commodity code, vendor, or stock number.
The product provides for navigation to part history
while reviewing recommended order quantity.
Preferred venders can be associated with each          2
part along with history of purchases.
The product makes a distinction between                2
requisitions and purchase orders.
One requisition can have several purchase order        2
numbers assigned to it.
Requisition and purchase order numbers can be          2
assigned by user and the purchase order number
can be different from the requisition number.
(They need to be assigned by import of data from
Customer Procurement System referenced in
later section.)
The product can create Purchase                        2
Orders/Requisitions for both materials and
services.
The product includes a workbench or similar            2
vehicle to allow the user to easily convert
requisitions to Purchase Orders, apply line items
from requisitions to Purchase Orders and other
similar functions.
The product includes a complete PO change              2
capability to track changes to Purchase Orders.
The product includes an invoice approval facility      2
to allow users to approve both service and
inventory based invoices.
The product includes a 3-way matching function         2
that allows the users to match receipts, PO lines
and invoices as a means to validate invoices.
The product includes an approval hierarchy for         2
requisitions.
                                                           66
Key Control
Description
Tool Crib Management
Description
The product can maintain a database of tools and      2
equipment available for checkout, including
information such as on-hand and total quantities,
charge-out rates, warranty information, and serial
numbers of serialized equipment.
The product can maintain an inventory of              2
consumable tools and generate re-order lists as
needed.
The product can record the checkout and check         2
in of tools and equipment.
Checkouts can be designated as permanent or           2
temporary.
The product can create charge records for billing     2
purposes.
Default charges can be manually overridden.           2
Asset records can include quantity information to     2
handle the occurrence of multiple identical non-
serialized items in the tool inventory.
Asset records can include or reference such           2
information as PM histories, maintenance costs,
and revenue totals for individual serialized tools.
The product can record information about              2
customers such as name, shop and other contact
details.
The product can interface with card reader and        2
bar code input devices to scan employee ID
cards and record tool and equipment issues,
returns, and inventory.
The product can print real time receipts upon         2
check in of tools and equipment.
The product can generate commonly needed              2
reports, such as past due lists, lists of tools
checked out by employee or shop, and lists of
permanent issues by shop.
The product can display on-hand quantities of         2
tools and equipment.
The product provides documentation and                2
inventory of tools to be checked out.
The product provides reports and approval             2
processes.
The product integrates Human Resources                2
component for termination reporting.
Work request forms can be tailored to the type of     2
service requested (e.g., by prompting for account
information only if service is billable).
The product can be configured such that               3
completion of certain fields of the work request
form is mandatory.
The product generates email notifications of          3
receipt and status of work requests to customers.
Work order request number is assigned and             3
reported to the customer upon submission of a
work request.
Incoming work requests are time stamped.              3
Work requests entered via the web should              3
automatically update the product's database
tables.
                                                          67
Work requests entered through web should be
grouped with other requests available for review
and scheduling.
The product provides graphical access to work           3
orders via floor plans.
Authorized customers can view cost details such         2
as labor, material, rental, and outside services
and can determine whether work is billed on
actual costs or a flat fee.
PLEASE LIST ALL SYSTEM FEATURES THAT
ARE UNIQUE TO YOUR PRODUCT AND NOT
LISTED ABOVE



                                                                         Product
                                                                         provides
                                                   REQUIREMENT   MATCH   feature
PROJECT MANAGEMENT PACKAGES                        CODE          CODE    y/n        COMMENTS
PORTFOLIO
Asset
Organization
Location
People
EXECUTIVE VIEW
Configurable dashboard view
Program Summary
Project Summary
PROJECT ADMINISTRATION
Meetings
Requests for Information (RFI)
Submittals
Change Orders
contact Records
Transmittals
DOCUMENT MANAGEMENT
Documents (general)
Drawings (redlining)
Letters
Manuals
Memorandums
Photographs
Publications
DESIGN MANAGEMENT
Deliverables
Design Review Checklists
Design Review Comments
Item Specifications
Performance Specifications
Permits.
CHANGE & CONFIGURATION MGMT.
Design Change Notice
Issue Management
                                                                                               68
Potential change Order
Request for Change
COST MANAGEMENT
Project Cost Plan
Project Budgets
Actual vs. budget
Funding / multiple funding sources
Track encumbered and committed funds
Work orders against the project
Timesheets
Trend
FIELD MANAGMEENT
Accident Reports
Daily Details
Field Work Directives
Inspections and Tests
Notices to Comply
Punch lists
Safety Notices

RISK MANAGEMENT
Risk Item
Risk Mitigation Plan

SCHEDULE MANAGEMENT
Schedule Management
SUPPLY CHAIN MANAGEMENT
Agreement
Application for Payment
Bid
Closeout Report
Change Order
Expediting
Invoice
Lien Release
Payment Request
Procurement Request
Purchase Order
Receiving
Request for Quote
Service Agreement
Shipping Notice
Substantial Completion Notice
Work Authorization
Work Order
WORKFLOW
Graphical Interface
Designed and edited through browser
Complete Access to all fields and data elements.
PERSONALIZATION
                                                   69
Ability to add and / or edit fields and data
elements
Ability to place all additions in any location on any
form
Ability to add new forms and incorporate into
application
REPORTING
Canned Reports
Custom reports on the fly
Viewable on the web
Project Management                                      Priority*
Track Billable and Non-Billable Time for
Professional Hourly Services for Specific
Projects
The product allows staff to input their time (hours)            3
worked on construction and renovation projects,
both locally and from remote sites.
The product allows users to enter time charged to               3
specific accounts. This edit function is only
allowed for active accounts.
The product provides the ability to assign a type               3
of time from a user managed set of billable and
non-billable time types. Time may be
distinguished as billable or non-billable.
Allows management to review, edit, or delete all                3
time transactions provided by staff. Once
reviewed, staff may not update time information.
The product allows the user to define a variety of
project types to include different, user defined
fields, milestones and budget codes.
The product allows the user to define different
types of contracts to support the capital projects,
such as architectural/engineering, construction,
furniture/fixtures, telecommunications, etc.
The product tracks major revisions to project that
might affect the schedule, funding or budget.
The product provides for comparisons between
different versions in terms of funding, budgets,
milestones and costs incurred.
The product allows the user to define milestones,
the weighting of the milestones and percent
complete of each of the milestones in the overall
capital project.
The product allows project management to input                  3
data both locally and from remote locations
(project no., date worked, hours, time category,
and rate).
The product provides for a user-defined set of                  3
rates for billing.
The product maintains project histories.                        3
The product tracks sources of funds for projects                3
The product allows users to change requests                     3
The product supports different revisions to project
and changes between revisions.


                                                                    70
All costs related to projects are accumulated from
feeds from the financial system.
The user is able to drill down to view source of
costs and financial information, including PO‟s,
invoices, work orders, for each of the budget
codes of the project.
Capital projects are fully integrated with the work
order system to incorporate work performed by
in-house crews.
The product allows the user to attach all project
information such as drawings, engineering
analysis, notes from telephone conversations, etc
to the capital project.
Administrative and Financial Management
Billing Systems General
The product has the ability to bill accounts from       3
any billing/cost tracking module/system, i.e.,
billing of variously available cost info with feed of
formatted transactions to general ledger.
Account numbers used/to be used in billings are         3
audited against general ledger account numbers.
Each billing process operated should create its         3
own distinct batch general ledger transactions.
The product has the ability to display labor,           3
material costs at various levels (shop, account
number, project).
The product integrates with other financial             3
management systems.
Personnel
The product integrates with TIME KEEPING and            3
LABOR REDISTRIBUTION modules.
The product recognizes the work assignment              3
centers‟ functionality around which FMD
processes are organized.
The product provides query by name, SS#, Work           3
Assignment center (shop), vacant positions,
position #, etc.
The product provides various reports such as            3
Vacant Positions, Filled Positions, Complete
Roster, FMD Excel Employee Incentive Reports,
etc. and list all standard reports.
Display Customer HRS data stored.                       3
Time Keeping
The product will integrate with PERSONNEL and           3
LABOR REDISTRIBUTION modules.
The product will provide the capability for the user    3
to define multiple leave types and maintain
balances for them.
The product maintains leave balances in total and       3
per fiscal years.
The product produces time sheets per pay period         3
for authentication by employee and supervisors
with totals per account per day in a multiple week
format including summaries for each week and in
total. Leave balances will also be shown.

                                                            71
The product captures work and leave time, with       3
overtime, shift indication, regular when working
for compensatory time off, and other
characteristics involved with FMD methods of
operation.
The product will require work and leave time to be   3
on valid work order numbers, open for the shop
for which the employee works.
The product prevents leave from being recorded       3
where unearned.
The product allows time worked to be                 3
reported/viewed in work management, web, and
all other system components.
The product provides the reports required for        3
FMD operations.
The product tracks work overtime, shift              3
differential, and other FMD specific time
characteristics.
The product tracks vacation by current, last and     3
prior fiscal year. It will track holiday, total
disability leave, and other in total only.
The product provides for a record of standard        3
time per craft shop employee per pay period that
can be used to enter actual time worked by that
employee‟s timekeeper.
The product provides for a record of standard        3
time per administrative employee per pay period
that can be used to enter actual time worked by
for that employee.
The product provides for a record of standard        3
time per administrative employee per biweekly
period, which can be used to enter worked by a
single “button push” per that employee.
Labor Redistribution
The product integrates with TIME KEEPING, and        3
PERSONNEL.
The product will provide pro rata distribution of    3
appropriate percentage of administrative
overhead costs recovery to appropriate FMD
service center accounts.
The product creates, per payroll period, a feed of   3
ledger transactions to charge job order/service
order work for the period to the appropriate FMD
work order account and credit that same amount
back to the appropriate FMD service center
accounts.
Recharges can be broken into multiple amounts        3
per employee based on actual pay rate and
standard rate per shop.
Material Management
The product integrates with UCONN Purchasing.        4
The product‟s purchasing module will meet the        3
FMD needs of a work order shop-based
organization.
The product allows on-line viewing counts, on-       3
hands, and locations from Customer
Purchasing/Stores.

                                                         72
The product provides web-based training as           3
required.
Integration to Construction & Project
Management System
All associated information about assets will be      3
integrated with facilities maintenance.
Employee History
The product tracks employee educational history.     3
The product tracks employee craft/job training       3
and credentials history.
The product tracks employee employment history       3
including non-Customer employment.
The product produces New Hire/Promotion              3
Recommendation Report(s) ranking individuals
by educational, years of experience, and pay rate.

PLEASE LIST ALL SYSTEM FEATURES THAT
ARE UNIQUE TO YOUR PRODUCT AND NOT
LISTED ABOVE




                                                         73
                                               EXHIBIT B



                                                               REQUIRED VENDOR
MODULE                           PRESENT System/Source                Process                 Vendor
                                   Storrs      UCHC            Storrs        UCHC          Storrs UCHC
General
     Security                                                   req'd          req'd        x      x
     Training                                                   req'd          req'd        x      x
     Business Process Review
     (BPR)                           All            All         req'd          req'd        x      x
     Estimated cost

Space Management                  Aperture       Drawbase
                                                              convert to
     Drawing conversion            Aperture      AutoCAD        ACAD          import        x      x
     Data gathering/database
     creation                      Aperture
       Site/Campus                 Aperture      TBD/excel     import         import        x      x
       Building Table              Aperture        excel       import         import        x      x

       Occupant Data               Aperture        excel       import      import/survey    x      x
       FICM Table                  Aperture        excel       import         import        x      x
       Floor Table                 Aperture        excel       import         import        x      x
       Room numbers                Aperture        excel       import         import        x      x
                                                   to be
        Room Attributes            Aperture       created      import         survey        x
        PI Information             Aperture        excel       import         import        x      x
     Interfaces required
        Department Information      FRS            FRS        interface      interface      x      x
        Employee Information     FRS/Genesys       FRS        interface      interface      x      x
        PI Information                             FRS        interface      interface      x      x
     Estimated cost

Project Management                CAPSAT         UltiMaint
     Normalize Legacy data                                      req'd          req'd        x      x
                                                              convert /      convert /
     Data conversion              CAPSTAT        Foxpro 2.6    import         import        x      x
     Interfaces required
        Accounting                  FRS            FRS        interface      interface      x      x
        Microsoft Project                        MS Project                  interface             x
     Estimated cost

                                 FX MODULE
Asset Management                   OF FRS           FFX                         BPR                x
                                                              determine     determine
     Database work                                             linkages      linkages       x      x
                                 FX MODULE
     Interfaces required           OF FRS           FFX       interface      interface      x      x
     Estimated cost

Move Management
                                                                to be
     Determine Process                                         created         BPR          x      x
     Estimated cost

                                                                                                         74
Maintenance                       CAPSTAT     UltiMaint
     Normalize Legacy data                                    req'd        req'd       x   x
                                                           convert/      convert /
      Data conversion             CAPSTAT     Foxpro 2.6     import       import       x   x
                                                           convert/      convert /
      Stores                      CAPSTAT     Foxpro 2.6     import       import       x   x
                                                           convert/
      Shops                       CAPSTAT     Foxpro 2.6     import         x          x   x
                                                           separate
      PM set-ups                  No Data     Foxpro 2.6      RFP      to be created   x   x
                                                           separate
      Tag equipment (barcode)     No Data                     RFP
                                  n/a - see                   to be
      Contracts                     PO's       FRS??        created    to be created   x   x
      Interfaces required                       FRS             x            x         x   x

        POs                         FRS        FRS??       interface     interface     x   x
        Vendors                     FRS        FRS??       interface     interface     x   x
      Estimated cost

Report Writer                      Excel      Foxpro 2.6   replace       replace       x   x
     Estimated cost

Communications                     802.11      802.11       req'd          req'd       x   x

Environmental                      None         None
     Data gathering/data base                               to be
     creation                      None         None       created     to be created   x   x
     Estimated cost

Utilities
       Data gathering/data base                             to be
       creation                    None         None       created     to be created   x   x
       Estimated cost

Grant Management                    n/a          FRS
     Normalize Legacy data          n/a                      n/a        NOT req'd
     PI Information
        Location                    n/a         excel        n/a           import          x
        Expeditures                 n/a         FRS          n/a         interface         x
        Effort Information          n/a         excel        n/a           import          x
     Interfaces required            n/a         FRS          n/a         interface         x
     Estimated cost




                                                                                               75

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:54
posted:8/7/2011
language:English
pages:75