EQUAL OPPORTUNITY by fionan

VIEWS: 31 PAGES: 29

									                          SALEM STATE COLLEGE
                               INVITATION TO BID
                             THIS IS NOT AN ORDER


1. The College is an agency of the            7. Salem State College reserves
   Commonwealth of Massachusetts                 the right to waive informalities
   and is exempt from any State tax              and to reject any and all bids; or
   or Federal excise tax.                        to accept the bid deemed best
                                                 for the Commonwealth.
2. Unless otherwise stated, the unit
   price shall be the net price.              8. Any objections to the above
   Separate unit and total prices                conditions must be clearly
   must be shown if applicable.                  indicated in the proposals.

3. Unless otherwise stated, all               9. For    additional   information
   quoted prices shall be FOB                    contact Chuck Walla, MIS
   college address inside delivery.              Director, at 978-542-6961

4. Bid must be received on or before          10. Bids must be submitted to:
   May 28, 2004, at 03:00 pm, in
   the    Purchasing    Department,                Salem State College
   Salem     State    College,  352                Evelyn Wilson, C.P.M., Director
   Lafayette Street, Salem, MA                     of Purchasing & Materials
   01970-5353, at which time there                 Management
   will be a public opening.                       Administration Bldg., 2nd Floor
5. No FAX copies will be accepted.                 352 Lafayette Street
                                                   Salem, MA 01970-5353
6. Submit 1 original and six copies
   of bid.                                    11. Reference:     Bid # 2004-13



SPECIFICATIONS                   UNIT PRICE                            TOTAL PRICE

                SEE ATTACHED SPECIFICATIONS



          EQUAL OPPORTUNITY

The Contractor agrees not to discriminate against any employee or applicant for
employment because of race, sex, color, religious creed, national origin, and/or
ancestry. The contractor agrees to post in conspicuous places notices to be provided by
the Massachusetts Commission Against Discrimination with respect to the Fair
Employment Practice laws of the Commonwealth, which are herein made part of this
contract reference.
   VENDOR IDENTIFICATION

COMPANY NAME: _______________________
Dba: __________________________________________________________
Company's Federal ID Number:
_______________________________________________
Order Address:________________________
Remit To
Address:_______________________________________________________
CITY____________________STATE_____ ZIP____________
TELEPHONE NO _______________ Toll Free or
"800":____________________________________________
Fax
Number:____________________________________________________________
____
E-Mail Address:
_____________________________________________________________
NAME _______________________________ TITLE ____________________

AUTHORIZED SIGNATURE __________________________________________




                                      2
Request For Proposal
            E-Commerce Services
              Cashiering Services
                  Billing Services
         Student Services Via IVR




         Published On: April 23, 2004
     Prepared By: Salem State College


            3
                          Table of Contents

1. PURPOSE AND GENERAL INFORMATION: .................................... 5

2. BACKGROUND: ............................................................................ 8

3. COMPUTING ENVIRONMENT: ...................................................... 8

4. APPLICATION REQUIREMENTS: ................................................ 10

5. HARDWARE/SOFTWARE FEATURES:.......................................... 22

6. TRAINING: ................................................................................ 23

7. CUSTOMIZATIONS: ................................................................... 23

8. MAINTENANCE: ......................................................................... 23

9. INSTALLATION AND CONFIGURATION: ..................................... 24

10.    INTERFACES: .......................................................................... 24

11.    COSTS: ................................................................................... 25

12.    VENDOR REFERENCES: ........................................................... 26

13.    OTHER REQUIREMENTS: ......................................................... 26

14.    EVALUATION CRITERIA: ......................................................... 27

15.    EVALUATION OF PROPOSALS: ................................................ 28

16.    WARRANTIES, MAINTENANCE AND SUPPORT: ....................... 29

17.    STANDARD TERMS AND CONDITIONS: ................................... 29




                                                        4
1.    Purpose and General Information:

1.1   The purpose of this document is to provide interested vendors with
      information to enable them to prepare and submit proposals for a
      student related services consisting of the following: The processing of
      e-commerce transactions via both the web and in person, over the
      counter; and student class registration, and grade reporting via touch-
      tone telephone. These services, where appropriate need to be
      compatible with both the Student Administration, as well as the
      Enterprise Portal applications supplied by PeopleSoft.

      The timetable for selection and installation:


       Request for Proposal issued to Vendors                     April 29

       Pre bid Conference                                         May 14

       Proposal Due Date, Opening                                 May 28

       Vendor Demonstration(s) (if needed)                        June 4

       Complete the Review of Proposals and Make Award            June 18

       Negotiate Contract, Place Order                            June 25

       System Equipment Installation                              July 1

1.2   The primary contacts for this contract would be the following:

      a.    The Purchasing Department is responsible for the administration
            of the Request for Proposals and will ultimately award the
            contract. Contact person is Evelyn Wilson, Director. She may be
            reached at (978) 542-6152.

      b.    Information Technology/MIS is responsible for the administrative
            data processing requirements. Contact person is Chuck Walla.
            He may be reached at (978) 542-6961.

      c.    The Department of Financial Services is responsible for the
            ongoing maintenance of the e-commerce processing services.
            The contact person is Joseph Donovan, Executive Director. He


                                             5
            may be reached at (978) 542-6561. That department is one of
            the primary users of the equipment and services to be obtained
            as a result of this Request for Proposal.

      d.    The Office of Student Records & Registrar is responsible for the
            ongoing maintenance of the student related services. The
            contact person Ali Guvendiren, Registrar. He may be reached at
            (978) 542-6081. This department is one of the primary users of
            the equipment and services to be obtained as a result of this
            Request for Proposal.

1.3   No public disclosure or press release pertaining to this RFP, review
      process, or award shall be made.

1.4   Negotiations may be undertaken with those contractors whose
      proposals as to price and other factors show them to be qualified,
      responsible and capable of performing the work. The contract entered
      into will be that most advantageous to the College, price and other
      factors considered.

1.5   The selection of a vendor and the accompanying award of a contract
      are to be based on evaluation criteria established in this Request for
      Proposal.

1.6   The College, at its discretion, may select not to award a contract to
      any vendor as a result of this RFP. The College reserves, at its
      discretion, the right to reject any and/or all proposals received in
      response to this RFP if determined that such action is taken in the best
      interest of the College.

1.7   All vendors who provide a proposal in response to this RFP are
      responsible for incurring all costs associated with preparing that
      proposal, answering all questions, providing the College with requested
      information, and making a vendor presentation to the College. The
      College is under no obligation to incur or reimburse any vendor for
      proposal costs.

1.8   Proposals must include a current financial statement and a statement
      indicating whether or not their company has been profitable for the
      three prior fiscal years (and parent company if applicable).

1.9   Proposal must be organized in the order presented in this RFP.
      Proposals not organized in this prescribed manner may be considered
      informal and rejected.

                                            6
1.10 The following general instructions are suggested to bring clarity and
     order to the proposal preparation and subsequent evaluation process:

      a. Proposals should be prepared simply and economically, providing a
         straight forward, concise description of the contractor’s ability to
         meet the requirements of the RFP. Fancy binding, colored displays,
         promotional material, etc. are not desired. Emphasis should be on
         completeness and clarity of content.

      b. Supporting documentation such as technical manuals or product
         details may be included in the Appendices and referenced in the
         appropriate section of the RFP.

1.11 All proposals and attachments become the property of the College.
     Please indicate any or all portions, which are proprietary and are to be
     kept confidential.

1.12 The selected contractor will be required to assume responsibility for all
     services offered in his proposal. Further, the College will consider the
     selected contractor to be the sole point of contact with regard to
     contractual matters, including payment of any and all charges resulting
     from the contractor.

1.13 Payment for any contractor entered into as a result of this RFP will be
     made monthly upon receipt of contractor’s billing statement.
     Contractors may submit invoices for partial payment, based on percent
     of work completed. Request for payment must be substantiated by
     written documentation and reference a purchase order.

1.14 By submission of a proposal, the offeror certifies, and in the case of a
     joint proposal each party thereto certifies as to its own organization,
     that in connection with this proposal the prices in the proposal have
     been arrived at independently, without consultation, communication,
     or agreement, for the purpose of restricting competition, as to any
     matter relating to such prices with any other offeror or with any
     competitor.

1.15 The contents of the successful proposal may become contractual
     obligations, if a contract ensues. Failure of the successful proposer to
     accept these obligations may result in the cancellation of the award.

1.16 The proposal shall remain valid for a minimum of ninety (90) days. If
     additional time is needed, the College reserves the right to request an

                                            7
     extension.

1.17 Questions that arise prior to the pre bid conference of the RFP should
     be submitted in writing to the issuing office and will be answered at
     that time along with additional questions.

1.18 In the event that it becomes necessary to revise any part of this RFP,
     addenda will be provided to all vendors who received the basic RFP.

1.19 To be considered, proposal must arrive at the Department of
     Purchasing on or before 3:00 P.M., May 28, 2004. Contractors mailing
     proposals should allow normal mail delivery time to ensure timely
     receipt of their proposals. No allowance will be made for late delivery
     for any cause whatsoever.

1.20 To be considered, contractors must submit a complete response to
     this RFP. Each proposal must be submitted in one (1) original and six
     (6) copies to the Office of Purchasing. ORIGINAL MUST BE CLEARLY
     MARKED ORIGINAL. The Contractor will make no other distribution
     of proposals. An official authorized to bind the contractor to its
     provisions must sign proposal. For this RFP the proposal must
     remain valid for at least ninety (90) days after response date.


2.   Background:
     Salem State College has an enrollment of approximately 10,000
     students in the fall and spring semesters with approximately 6,000
     students enrolled in the summer terms. The College is currently in
     the process of upgrading its PeopleSoft Student Administration and
     Financial applications to the current Version 8 standard offered by
     PeopleSoft. To successfully accomplish this upgrade, the solutions for
     replacing its existing credit card and touch-tone services are being
     assessed.


3.   Computing Environment:
     Salem State College currently operates a PeopleSoft Student
     Administration and Financial Services systems on an Oracle 9i
     platform. In addition, the PeopleSoft Enterprise Portal is being
     installed. For the purposes of this RFP, the e-commerce processes
     requested must be compatible with and support financial transactions
     via this portal. This hardware configuration is intended to show our
     primary platform standards at the current time. When responding to

                                           8
      this RFP, please indicate compatible platform components where
      possible, and lower cost alternatives where available.

3.1   Hardware Environment

      Database Server (Production)
      a.   Sun Fire V880, Solaris 8, Oracle 9i
      b.   900 MHz four-way CPU, 8 Gb RAM, 6-73 Gb internal disks
      Database Server (Development)
      a.   Sun Fire V880, Solaris 8, Oracle 9i
      b.   900 MHz four-way CPU, 8 Gb RAM, 6-73 Gb internal disks
      Application Server (Production)
      a.   Sun Fire V480, Solaris 8
      b.   900 MHz four-way CPU, 8 Gb RAM
      Portal Database Server (Production)
      a.   Dell PowerEdge 6650, Windows 2003
      b.   3.0 GHz four-way CPU, 4 Gb RAM, 2-36 Gb, 3-73 Gb disks
      Portal Database Server (Development)
      a.   Dell PowerEdge 2650, Windows 2003
      b.   3.0 GHz four-way CPU, 4 Gb RAM, 2-36 Gb, 3-146 Gb disks
      Portal Web/Application Server (Production)
      a.   Dell PowerEdge 6650, Windows 2003
      b.   2.8 GHz dual CPU, 2 Gb RAM, 2-36 Gb, 1-73 Gb disks
      Portal Web/Application Server (Development)
      a.   Dell PowerEdge 2650, Windows 2003
      b.   3.0 GHz four-way CPU, 4 Gb RAM, 2-36 Gb, 3-146 Gb disks
      File Server (Production)
      a.   Dell PowerEdge 2650, Windows 2000, SP3
      b.   3.0 GHz CPU, 256 Mb RAM, 1-146 Gb disk
      File Server (Development)
      a.   Dell PowerEdge 2650, Windows 2000, SP3
      c.   3.0 GHz CPU, 256 Mb RAM, 1-146 Gb disk
      PBX (Telephone)
      a.   Lucent G3
      b.   Trunking, Digital T1

3.2   Application Environment

                                          9
        The three groups of services to be encompassed by this RFP are the
        campus credit card processing services, the student billing services
        and the student services offered via a touch-tone registration system.
        A brief description of each of the current systems follows:

        Credit Card Processing

        The current over-the-counter credit card transactions are supported by
        a 7-station counter system that submits the transactions for payment
        via a system called Retriever.

        Touch-Tone Student Registration and Grade Reporting

        Students can currently register for classes or retrieve their grades,
        using the Encore IVR system from EPOS Corporation. This system
        support 16 lines, and a real-time connection, via the WebAuth software
        product, to NDC Atlanta.

        Data Consolidation

        Transaction information regarding the transactions sent via either
        method above is consolidated and reported to the College via a web-
        based service supplied by Merchant Bank Services.


4.      Application Requirements:

4.1. Application Requirements – Student Services Via IVR
        Salem State College would like to upgrade its current IVR system that
        allows students access to several services via touch-tone telephone.
        Vendors should include their full range of student services in their
        response.

4.1.1       Vocabulary management
           The voice response unit should allow the College to create, record,
            and maintain the vocabulary without vendor assistance, other than
            initial training. Explain in detail how this is to be accomplished.

           Respondent to state whether the voice response system uses
            digitized pre-recorded human speech or if some other technique is
            used to produce the “voice” of the system.

           Specify if the voice response system is able to speak all of the


                                               10
            recorded phrases across all telephone lines within the system
            without degradation to system response time.

           State what documentation is provided with the system explaining
            how to create, record, and maintain vocabularies. Specify what
            additional information is made available at additional costs on this
            subject.

           Describe the system’s ability to add or load new recordings while
            the system is in use without interfering with delivery of messages to
            touch-tone callers?

4.1.2       Application Development Requirements

           Describe your application development utilities and how new voice
            response applications can be developed by Salem State College.
            What requirements for vendor support are included in developing
            new applications?

           Describe what features the application generator has with respect
            to run-time debug facilities.

4.1.3       Physical and Technical Specifications

           State guidelines or parameters for determining the number of lines
            and the number of ports needed initially to support this application.
             Comment on any other items you consider to be important with
            respect to the number of lines and/or ports.

           State the following system specifications along with associated
            costs: State maximum number of ports in a single cabinet; State
            incremental port additions (1, 2, 4 or 8)

           Describe your proposed system’s environmental requirements.

4.1.4       Hardware/Software Features

           Describe the hardware and software architecture and detail
            specification

           Describe the hardware to be used in the voice response unit.
            Technical information or brochures may be included in the
            appendices.


                                               11
   Describe the voice response units capability for back-up in the
    event of a major failure and the approximate time necessary to
    complete the restoration.

   Will the voice response system run multiple applications
    simultaneously on multiple lines? If so, how much response time
    degradation can be expected if all lines are simultaneously in use
    with multiple applications.

   Will the voice response system allow callers to dial-ahead over
    speech prompts? Will the system stop speaking and accept the
    input from the caller?

   Specify what the voice response system software provides for
    setting time limits for such things as initial input, inter-character
    pause, and total call length. State all time limits recognized by the
    system and the action taken when a time limit is exceeded.

   Specify what statistical information the voice response system
    provides on the telephone calls handled by the system. For
    example, the total number of calls, average length of call,
    percentage of time system was in use, where this information is
    stored, and how much storage capacity is used for statistical
    information. Include a few sample reports in your appendices.

   Specify if the system currently contains the ability to exit the
    registration program, interface with a credit card authorization
    service, verify a credit card, make a transfer of funds from the
    student’s credit card account to a College account and transfer the
    control of the call back to the registration program. If so, give a
    specific example of where this is in use and who may be contacted
    for information on this feature. If not, describe the system’s
    capability or approach to collecting tuition using credit cards.

   Specify if the voice response system configuration suggested
    provides complete system redundancy in the event of a major
    failure of one unit.

   Describe the remote diagnostics available with the system that
    permits the voice response unit to communicate with the vendor
    when the system is having difficulties. Specify if this diagnostics
    system is capable of reporting trends which may be leading to a
    system or component failure as well as “hard” software/hardware

                                       12
    failures.

   Does the system provide a diagnostic port whereby vendor
    specialists can correct problems remotely, download software
    changes and verify proper system operation?

   Describe what programming the College will be responsible for on
    the voice response system.

   Describe any translator programming that must be done by the
    College to allow the voice response system to communicate with
    the mainframe. Include the purpose of the program, the language,
    and where the program would reside.

   Describe how the voice response system will handle a student that
    accesses the system using a rotary dial telephone.

   Describe the methods available with your system for activating call
    transfer.

   Describe the security capabilities available with your system.

   State how the system will handle “stand alone” messages that do
    not require host interface, i.e. announcements or music. Specify
    where these messages are stored, how they will be stored and what
    must take place for one of these messages to be activated.

   Describe what capabilities your system has for recording voice
    messages from callers.

   Describe your system’s ability to provide simultaneous IVR and
    Internet/Intranet/World Wide Web access and transaction
    processing. Provide client references where this is operational, in
    production, not at Beta sites.

   Does your system provide a method of queuing calls when the
    maximum number of sessions are in use?

   What database structure is used by your system?

   What access methods (touch-tone, local console, remote PC) are
    available to authorized administrators to make routine changes
    while the system is active?



                                       13
           Describe how the voice response unit will respond to a host system
            failure during an active registration session and by what methods
            can an administrator be notified of a system error?

           Describe the features of the system in terms of real time line and
            system status displays.

           Describe the audit trails maintained on the voice response system.

4.2     Application Requirements – E-Commerce

        Salem State College would like to offer the ability for students to pay
        fees with a credit card from the PeopleSoft Student Administration and
        Enterprise Portal applications. The Respondent must provide
        compatible software and hardware required to allow this ability,
        including the ability to authorize and settle credit card transactions
        using a remote payment processor (Eastern Bank uses NDC Atlanta).
        The system must also be able to update the PeopleSoft Student
        Administration System to reflect these transactions.

        Respondents must provide detailed explanations of how their payment
        system meets the following requirements;

4.2.1       Interface with PeopleSoft Student Administration/Financial
            Services

           The system must be currently certified with PeopleSoft for providing
            credit card payment functionality for the Student Administration and
            Enterprise Portal applications.

           The solution must be completely developed, and turnkey with the
            PeopleSoft Student Administration System (explain in detail how
            this connection is provided; what versions of PeopleTools are
            supported)

           The system must be able to connect to Salem State College’s host
            system, both student and financial.

           The system must be able to connect to external payment
            processors via modem, IP, or leased lines.

           The system must accept payment transactions either over-the-
            counter, via an IVR student service system, or via services offered
            through the PeopleSoft Enterprise Portal.



                                              14
           The system must respond to PeopleSoft status information relating
            to the student, such as: financial, registration and grade holds.

4.2.2       Expandability to Other Web Applications

           The solution must have the ability to be expanded for other campus
            web applications for payment functionality (explain in detail how
            this is provided).

4.2.3       Physical Requirements

           Hardware must be optional for the solution (Salem State College
            reserves the right to choose to provide the hardware for the
            solution).

           The system must include all software and hardware necessary for
            payment and logging functions.

           The system software and hardware must be capable of supporting
            multiple e-commerce stations, for card-present transactions, in
            offices throughout the campus environment.

           The vendor must support the Windows platform (NT, 2002, 2003)

           All hardware, if provided by the vendor, must be non-proprietary.

           All hardware, if provided by the vendor, must provide redundancy
            capability.

4.2.4       External Payment Processor Compatibility

           The system must connect directly to NDC Atlanta, to authorize the
            credit care transactions, the credit card clearinghouse utilized by
            Salem State College.

           The respondent should also list all clearinghouses for which it is
            certified in the event Salem State College changes banking
            institutions.

           Any transactions charges associated with this interface must be
            clearly itemized in the response to this RFP.

4.2.5       Credit Cards Accepted

           The system must be capable of accepting all major credit cards,
            including Visa, MasterCard, American Express and the Discover
            Card.

                                               15
4.2.6       Portal Transactions and Capacity

           The system must be capable of performing standard authorizations,
            individual settlements (“settle now”), and batch settlement
            transactions.

           The system must be capable of performing multiple authorization
            transactions per connection (“Piggy-backing”) with the external
            payment processor.

           The system must be capable of processing Electronic Checks, and
            Debit Card transactions.

           The system must support e-commerce payment for third-party
            applications delivered via the PeopleSoft Enterprise Portal
            application.

           Describe a credit card payment transaction, including information
            gathering, card authorization, settlement, and processing.

           The system must not use a third-party to process credit card
            payments, but should instead interface directly with the bank
            and/or credit card processor of Salem State College.

           Describe the ability to authorize payment in real-time.

           The portal system should be able to incorporate the campus’s
            existing business days, and should post payments to the
            appropriate business day. Describe how this is accomplished.

4.2.7       Card-Present Transactions and Capacity

           The system must be capable of performing standard authorizations,
            individual settlements (“settle now”), and batch settlement
            transactions.

           The system must be capable of supporting transactions in which a
            credit card is physically swiped.

           The system must be capable of performing multiple authorization
            transactions per connection (“Piggy-backing”) with the external
            payment processor.

           The system must be capable of processing Electronic Checks, and
            Debit Card transactions.



                                              16
           Describe a credit card payment transaction, including information
            gathering, card authorization, settlement, and processing.

           The system must not use a third-party to process credit card
            payments, but should instead interface directly with the bank
            and/or credit card processor of Salem State College.

           Describe the ability to authorize payment in real-time.

           The system must be capable of supporting deposits, escrows and
            application fees taken by campus departments. Describe how this is
            accomplished.

           The card-present system should be able to incorporate the
            campus’s existing business days, and should post payments to the
            appropriate business day. Describe how this is accomplished.

           Cashier’s should be able to accept payment for multiple fees, and
            multiple bank accounts, in a single customer session. This
            transaction should be reflected in a single customer receipt.
            Describe how this is accomplished.

           The cashiering system must have a customer-facing display that is
            capable of displaying pertinent student information such as account
            balance, name, student ID number, address, amount due, and
            other relevant information.

           This terminal must allow a student ot swipe their credit card without
            handing it to the cashier.

4.2.8       Bad Check Flag

           The system should be able to maintain a “bad check flag” for each
            student. Explain how this is accomplished.

4.2.9       Check Scanning – Hosted System

           The system must scan all paper checks used by cashiers.

           The vendor must provide reports that allow cahsiers to view
            scanned check images (including both the face and back of the
            original paper check).

           This information will be used for audit-control and dispute resolution
            procedures.



                                               17
        Describe how your system supports this functionality.

4.2.10 Logging and Reporting Functions

        The system must be capable of logging all transactions, including
         those to clients, hosts, and external payment processors(s).

        Logs must list individual authorizations, settlements, and host
         transactions (such as account balance updates).

        The system must be capable of generating detailed reports based
         on log files.

        Security

        The system must encrypt the transactions as they are passed from
         the Oracle Application Server to the payment server.

        The data stored on the payment server must be encrypted.

        The system must provide for the ability for secure ID’s, and client
         addresses.

        The system must provide for the ability for administrative
         passwords and PIN’s in order to access logging and reporting data.

4.2.11 ACH Transactions

        The system must be compliant with the NACHA rules for both in-
         person and mailed-in payments

        Describe how system supports this functionality.

        Describe the system’s ability to accept payments via ACH at the
         counter, through the mail, and/or over the phone.

        Describe the process of converting a paper check into an ACH file.

4.2.12 Administration

        Describe the administrative features of the system.

4.2.13 Financial Reporting

        Describe the financial reporting and transaction auditing functions of
         the solution.


                                            18
       Describe the system’s ability to track financial transactions (monies
        collected and monies disbursed) for each individual cashier, creating
        an audit trail to be used by system administrators or supervisors.

       The system must grant secured access to finance personnel for
        reporting information and financial transaction data.

       Describe the capability for the system to maintain information about
        the cashier’s drawer, as well as its ability to close and balance the
        drawer when a cashier logs off.

       The cashiering system should save the values in the currency
        worksheet when a cashier closes and balances their drawer. This
        will assist supervisors in the audit control process.

4.2.14 Customer Receipts

       Describe the system ability to generate a multiple lined receipt that
        would include but not be limited to: cashier number, date, student
        ID, payment type, account code, transaction number, dand amount
        paid.

       The receipt must have a header and footer that can be customized
        by Salem State College.

       The system must allow for the reprinting of receipts.

4.2.15 “Card Present” Hardware

       Describe the “card-present” hardware and software required to
        perform over-the-counter transactions.

       In the event of a power interruption or communication failure to
        campus information systems, the system must be capable of
        independent operation off-line from the server and/or host.

4.2.16 Hosting Versus On-Site Hardware and Software

       Describe differences associated with hosted versus on-site solutions
        proposed.

       Describe transaction pricing options available with each proposed
        optional solutions.




                                           19
4.3     Application Requirements – Electronic Billing

        The electronic billing system must provide the required software to e-
        mail notifications, present billing statements online, accept payments,
        enable third-party payments, and utilize real-time integration with the
        PeopleSoft student information system.

        Respondents must provide detailed explanations of how their billing
        system meets the following requirements;

4.3.1       Bill Loading

           Describe how bills are loaded into the system.

4.3.2       E-mail Notification

           Explain the system’s ability to use e-mail as the primary form of
            delivering alerts and notifications. Specifically, what notifications are
            available and how are they triggered.

           What e-mail services or platforms are compatible, not compatible.

4.3.3       Web Notification

           Explain the system’s ability to use the web as the primary form of
            delivering alerts and notifications. Specifically, what notifications are
            available and how are they triggered.

           What browser platforms are compatible, not compatible.

4.3.4       Authentication

           Describe how the system authenticates users during the login
            process.

4.3.5       Bill Presentation

           Describe the file formats that are available for bill presentation.

           Describe the bill delivery options available.

4.3.6       Current Account Activity

           The system must provide the user with a real-time view of the
            student account that includes all billing data posted to the student

                                                20
            account after the bill has been sent.

4.3.7       Billing History

           Describe the system’s ability to store billing data.

4.3.8       Payment Updates

           The system must provide real-time updates to the PeopleSoft
            Student Administration System upon authorization of payment.

4.3.9       Automatic Payments

           Describe how the system supports automatic payments.

4.3.10 Authorized Users

           Describe how students grant access to a third party (parent,
            guardian, or employer), including how the system ensures
            compliance with FERPA.

4.3.11 Dispute Resolution

           Describe tools included with the system that help facilitate dispute
            resolution.

4.3.12 Administrative Applications

           The system must include a web-based administrative application for
            managing student billing. This includes the ability to look up a
            student account, review reports, and scheduling of billing functions.

4.3.13 Payment Processing

           The system should utilize Salem State College’s existing banking
            relationships. All funds collected through he payment plan software
            should be settled directly to Salem State College’s accounts.

4.3.14 Credit Cards Accepted

           The system must be capable of accepting all major credit cards,
            including Visa, MasterCard, and the Discover card.

           Transactions must be routed through Salem State College’s existing
            banking/processor relationship.




                                                21
4.3.15 ACH Transactions

         The system must be capable of processing ACH/electronic check
          transactions. Describe the system’s ability to accept payments via
          ACH.

4.3.16 Integration With PeopleSoft Enterprise Portal

         Describe how the system interfaces with the PeopleSoft Enterprise
          Portal and LDAP services such as may be adopted by Salem State
          College.

         What LDAP products are compatible, not compatible?

4.3.17 Security

         The system must offer security measures such as encryption and
          client and host identification and verification.

         Describe the system’s security standards.

4.3.19 Financial Reporting

         Describe the financial reporting capabilities of the system.

4.3.20 System User Administration

         The system must allow for the ability to assign roles to different
          campus users, giving each user different roles, responsibilities, and
          rights to the system.


5.    Hardware/Software Features:

5.1   Describe the hardware and software architecture and detail
      specifications.

5.2   Describe all single-user, multi-user implementation options that can be
      expected of Vendor software.

5.3   Describe the hardware to be used. Technical information or brochures
      may be included in the appendices.

5.4   Propose a recommended size or model identification for all components
      within that configuration.

5.5   Size the database requirements based upon your experience with

                                             22
      schools of similar student populations.

5.6   Describe the security capabilities available with your system.

5.7   What database platforms are supported by your system?

5.8   What access methods are available for authorized administrators to
      make routine changes while the system is active?

5.8   By what methods can an administrator be notified of a system error?

5.9   Describe the audit trails maintained on the system.

5.10 All software and hardware to be supplied must include support for
     segregated Production, QA and Development environments.


6.    Training:

6.1   Specify the training options included with the system in terms of the
      location of training, the duration of training, and the cost of training
      with respect to each of the following areas:
         Administration of the system
         Creating and upgrading records
         Creating and updating interfaces
         Any other areas of training necessary


7.    Customizations:

         The existing IVR dialogue is heavily customized. Describe the
          process for customizing all service dialogue.

         Describe languages and proprietary nature of all coded sources.


8.    Maintenance:

8.1   Specify the initial warranty period of the system.

8.2   Specify the annual on-site maintenance contracts that are offered by
      the bidder with specific pricing included. On-site maintenance
      contracts should be shown.



                                             23
8.3   Specify your response time policies.

8.4   Specify the length of time or criteria that must be met before and
      unresolved system call will be escalated to a higher level within
      vendor’s organization for resolution.

8.5   Specify the plan and expense to keep up with Peoplesoft SA product
      updates, upgrades and fixes.

8.6   Maintenance to include support of Production, QA as well as
      Development environments.


9.    Installation and Configuration:

9.1   Specify the length of time to be expected between date of order,
      complete software and documentation delivery, arrival of Vendor
      implementation team (if appropriate), and final completed
      implementation.

9.2   Specify the length of time required to install the system (including the
      developed applications) after receipt of purchase order.

9.3   Specify detailed installation and deployment plan to include: tasks,
      user roles, vendor roles, estimated time, and other constraints or
      expectations.

9.4   Specify what physical or operational arrangements must be made by
      the College to make installation proceed as planned.

9.5   Specify the test processes that will be required to ensure a successful
      implementation.

9.6   Installation must include hardware and software required to support
      applications in Production, QA and Development environments.


10. Interfaces:

10.1 Vendors shall describe how the software will interface with the
     PeopleSoft Student Administration and Enterprise Portal systems at
     Salem State College.

10.2 Vendors shall provide optional PeopleSoft interface development and
     maintenance agreement for this PeopleSoft interface.

                                             24
11. Costs:

11.1 Respondents shall provide a pricing proposal for Salem State Colleges
     complete system as described in this response. Including all annual
     maintenance, exceptional maintenance, and ongoing support.

11.2 Indicate any options available, including training, and associated costs.

11.3 Respondents should provide a detailed description of any hardware,
     software and implementation tasks that are the responsibility of Salem
     State College

11.4 Respondent shall provide a detailed description of any exceptions to
     the requirements in this RFP.

11.5 Respondent shall provide a detailed description of costs associated
     with coding customizations to dialogue software or web-site branding
     and style sheet creation.

11.6 Costs should include redundant hardware, software, and maintenance
     support for Development and QA environments in addition to
     Production.

11.7 Respondent shall itemize all costs to clearly separate deliverable
     groups of features. (ie. Student Billing, Portal Based Credit Card, IVR,
     etc.)

11.8 Respondent shall itemize all costs to clearly identify host-based, as
     well as Salem State College hosted options.

11.9 Respondent shall clearly identify options for purchases of multiple
     package options, highlighting opportunities for price breaks.

11.10 Respondent shall clearly differentiate cost associated with production
      copy versus QA and Development copies of hardware and software
      purchases.

11.11 Respondent shall include the costs and timeframes for the initial
      training for key College personnel.

11.12 The recommended differentiation of application software, where
      proposed, would consist of the following: Portal based payments (SSC
      hosted, vendor hosted), Counter based payments and Cashiering, Web
      based billing, Hosted billing, Student services via IVR (w/incremental
      price breakdown of incremental service features beginning with Online


                                            25
      Registration and Grade Reporting)


12. Vendor References:

12.1 Specify if the proposed system is currently installed and operating with
     the same hardware and software as proposed. Indicate a complete list
     of contacts at other comparably sized educational institutions (names
     and phone numbers) for confirmation of this information.

12.2 Provide at least three (3) references that are currently running your
     software.

12.3 You may include reference materials in the appendices for this section.


13. Other Requirements:

13.1 Specify availability date of final software version; indicate any interim
     test versions that should be considered Vendor in selection.

13.2 Provide a reliable estimate for the time required to install, configure,
     verify connectivity, and tune all required software and hardware.

13.3 Describe the testing processes available to ensure the completion of
     this implementation.

13.4 State what documentation is provided with the system explaining how
     to create, and maintain records. Specify what additional information is
     made available at additional costs on this subject.

13.5 Provide technical specifications outlining PeopleSoft modifications
     provided, firewall integration requirements, Credit Card concentration
     standards supported, and e-mail integration requirements.

13.6 Describe the software’s ability to add or load new records while the
     system is in use without interfering with delivery?

13.7 Describe range of alerts, warnings and error messages that can be
     expected while entering or processing student data.

13.8 Describe software’s ability to load and maintain student ID’s created by
     Salem State College.

13.9 If hosted services are being offered, describe the process by which

                                            26
      Salem State College can conduct an IS site audit to review compliance
      to IT security or legislative requirements; whether by Salem State
      College personnel, or a subcontracted service provider.


14. Evaluation Criteria:

14.1 All proposals will be evaluated by Salem State College’s personnel
     comprised of representatives of various departments of the College.
     Proposal evaluation will be based upon the ability fo the proposed
     integrated system of software and hardware development to meet the
     requirements of Salem State College. Each proposal will be evaluated
     against design specifications outlined in the following sections of this
     RFP. Products will not be selected solely on price but on the greatest
     value with respect to productivity, functionality, performance,
     flexibility, and ability of meet the goals of Salem State College.

14.2 Specifically, proposal evaluations will be based upon the following
     criteria:

14.2.1 Technical Approach

         Response to technical and functional specifications and
          requirements for payment server hardware, software, security, and
          capacity.

         Technical and architectural approach in accessing host database
          systems (in particular, the PeopleSoft Student Administration and
          Enterprise Portal systems.)

         Non-proprietary nature of the hardware and software provided.

         Optional features such as expandability to outer campus web
          applications, operating system platforms, acceptance of other forms
          of payment, security and capacity.

         System expandability capabilities.

         Ability of Salem State College to add additional applications to the
          System.

         Ease of management of the system, and ability to generate
          statistical reports.


                                               27
14.2.2 Compatibility with PeopleSoft Systems

        Proven business partnership with PeopleSoft.

        Compatibility with the PeopleSoft Student Administration and
         Enterprise Portal applications.

        References within PeopleSoft who can speak to the business
         relationship.

14.2.3 Implementation and Maintenance Services

        Ability to provide skilled and experienced support personnel for the
         system implementation.

        Overall project plan, and turnkey nature of the system
         implementation.

        Length of time to install the System.

        Activities required of Salem State College for the system
         implementation.

        Maintenance and support services provided by the vendor.

14.2.4 Financial Considerations

        Price Proposal.

        Operational and Development Costs.

        Ongoing Costs.


15. Evaluation of Proposals:

     Proposals shall be evaluated by a selection committee comprised of
     official of Salem State College. The proposals will be evaluated on their
     material content and responsiveness to the requirements of the RFP,
     the quality of the services offered, the price quoted, the general
     reputation of the firm, the qualifications of the personnel assigned to
     work on the project, and the demonstrated understanding of the
     Respondent of conducting the work as required by the Scope of
     Services.


                                           28
16. Warranties, Maintenance and Support:

16.1 General Requirements

    The respondent shall fully describe policies regarding warranties and
    maintenance on the proposed System, including maintenance of
    hardware, software and other system components incorporated in the
    system price. As a prime contractor, the selected respondent shall be
    the party of first contact when system problems arise, and shall be
    ultimately responsible for directing the problem to the proper party
    and coordinating activities.

16.2 System Maintenance

    The respondent shall propose a comprehensive maintenance plan
    covering all proposed components of the System, both hardware and
    software.

16.3 Hardware Maintenance

    The respondent shall propose a hardware maintenance plan for
    preventative maintenance, parts replacement, and unscheduled
    maintenance visits. Indicate the companies responsible for providing
    hardware maintenance on all equipment included in the proposal,
    including response time.

16.4 Software Support

    Respondent shall propose a software support agreement for each
    software package. Describe services covered under this agreement
    and indicate any annual recurring costs of such services in the price
    proposal.


17. Standard Terms and Conditions:

    See attached




                                          29

								
To top