3Com by decree

VIEWS: 34 PAGES: 27

									     County of Mecosta

Request for Telephone System Update




              Page 1
Table Of Contents

1    General Information and Instructions.................................................................................... 3
    1.1    Purpose of Project ....................................................................................................... 3
    1.2    Goals and Objectives................................................................................................... 3
    1.3    Current Telephony Environment .................................................................................. 4
    1.4    Current Data Environment ........................................................................................... 5
    1.5    RFP Coordinator.......................................................................................................... 6
    1.6    RFP Schedule ............................................................................................................. 6
    1.7    Proposal Submission ................................................................................................... 6
    1.8    Vendor Site Tours........................................................................................................ 7
    1.9    Proposal Questions ..................................................................................................... 8
    1.10 RFP Evaluation Factors ............................................................................................... 8
2    Requirements ....................................................................................................................... 8
    2.1    System Capacities ....................................................................................................... 8
    2.2    System Architecture .................................................................................................... 8
    2.3    Remote Sites and Survivability ...................................................................................10
    2.4    Redundancy and Reliability ........................................................................................11
    2.5    Scalability ...................................................................................................................11
    2.6    Interoperability ............................................................................................................12
    2.7    Collaboration ..............................................................................................................12
    2.8    Data Network ..............................................................................................................13
    2.9    IP Phones ...................................................................................................................13
    2.10 System Features ........................................................................................................16
    2.11 Calling Features .........................................................................................................17
    2.12 System Administration ................................................................................................23
    2.13 Reporting ....................................................................................................................23
    2.14 System Management ..................................................................................................24
    2.15 Implementation ...........................................................................................................25
    2.16 Maintenance ...............................................................................................................25
    2.17 Training ......................................................................................................................25
3    Vendor Overview .................................................................................................................25
4    Pricing .................................................................................................................................26
5    BIDDER INFORMATION .....................................................................................................27




                                                             Page 2
1 General Information and Instructions
This RFP is organized into the following sections:

      Section 1 – General Information and Instructions
      Section 2 – Requirements
      Section 3 - Pricing

All vendors responding to this RFP must respond to section 2 and section 3 using the
information provided in section 1.

1.1         Purpose of Project
This Request for Proposal (RFP) is being used to obtain proposals for changes to the current
telephony systems in use at Mecosta County in Big Rapids, Michigan, including the Mecosta
County Services Building. These locations are currently served by two separate Nortel PBX
systems connected by a T1.

The purpose of this project is to eliminate the T1 between the County Building and the Service
Building and utilize the Alvarian Wireless currently in place and to find the best solution that is
reliable, secure, and scalable to accomplish this task. The solution must support, among other
things, centralized administration, inter-site dialing and directory, advanced PBX features, inter-
site voice and fax mail with unified messaging, inbound call center functionality, in-house
conferencing, and site survivability.

1.2         Goals and Objectives
The goal of this project is to eliminate the leased T1 currently connecting the two telephone
systems and use the Alvarian Breeze wireless system currently in place. Any replacement of
our existing telephony systems should be with a state of the art communications solution with
these objectives:

      Comprehensive solution from industry leading manufacturer and vendors
      Reliable and scalable platform with minimum number of servers
      Cost effective total solution including product, installation, and maintenance
      Centralized administration and management of hardware and software
      Easy to use phones, applications, and features with superior voice quality
      Transparent features and dialing between phones regardless of location
      Centralized auto attendants and voice messaging to all users
      Choice of regular voice mail or unified messaging for all users
      Standards-based integration with other telephony applications
      Interoperability with existing PBX




                                          Page 3
1.3          Current Telephony Environment
County Building – Nortel PBX with T1 interface (used to connect to the Service Building
telephone system), and PRI

Service Building – Nortel PBX with T1 interface (used to connect to the County Building
telephone system),

Guest mail boxes = ~50 (all at County Bldg.)
Headsets = ~4 (2 each bldg.)
There is one analog line connected to the Services Building phone system. This is programmed
for 911 calls.
There are no analog lines connected at the County Building.

Phones:
Style                  County Building            Services Building   Picture



M7100
                       90                         22
Basic




M7208
                       31                         8
8 Button




M7310
                       5                          1
22 Button




M7324
                       4                          0
24 Button



Analog/Fax             20                         6


Total                  150                        36




                                         Page 4
1.4         Current Data Environment
Cisco Catalyst WS-C3550-48-SMI Switch = 3 (County Bldg.)
Cisco Catalyst WS-C3550-24-SMI Switch = 1 (County Bldg.)
Cisco Catalyst WS-C3560-48-TS-S V02 = 1 (County Bldg.)
Cisco Catalyst WS-C3550-12G Switch = 1 (County Bldg.)

Nortel Baystack 450-24T w/400-4TX MDA (Services Bldg.)
Centre Com 3716TR (Services Bldg.)

Cisco 1841 Router = 2 (1 each bldg.)

Alvarian Breeze Wireless 3.1 – 54mg




                                       Page 5
1.5          RFP Coordinator
Upon release of this RFP, all communications concerning the proposal must be directed in
writing to the RFP Coordinator listed below.

      Name:           Janet Langell
      Address:        County of Mecosta, 400 Elm Street, Big Rapids, MI 49307
      Phone:          (231)592-0188
      Email:          jlangell@co.mecosta.mi.us

1.6          RFP Schedule
The schedule for this project is as follows:

      RFP Issued:                                  February 16, 2010
      Vendor Questions Due:                        March 2, 2010
      Response to Vendor Questions:                March 9, 2010
      Proposals Due:                               March 16, 2010
      Finalist presentations:                      March 23, 2010
      Reference Checks:                            March 30, 2010
      Selection of vendor and equipment:           April 6, 2010
      Implementation schedule due:                 April 13, 2010
      Cut-over:                                    April 20, 2010

The County of Mecosta reserves the right to adjust this schedule as necessary.

1.7          Proposal Submission
All proposals must be received in their entirety no later than 10:00 a.m. March 16, 2010.
Vendors must submit three (3) complete copies of their proposal to:

               Mecosta County Board of Commissioners
               Attn: Telephone Upgrade
               400 Elm St.
               Big Rapids, MI

Proposal responses must be in the same structure as this RFP prefaced with an executive
overview, requirements compliance information from section 2, and pricing information from
section 3.

Submission of a proposal and acceptance of the same proposal under this RFP shall constitute
a binding agreement between both parties.

The County reserves the right to consider proposals based on their relative merit, risk, and
value to the County of Mecosta. Lowest price is not the sole consideration, but must be
combined with vendor reliability, customer service, technical support, policy, and proposal
quality. Any and/or all proposals may be rejected on this basis.



                                           Page 6
The County reserves the right to reject a bid on any basis.

This RFP does not commit the County of Mecosta to award a contract, to pay any costs incurred
in the preparation of a response to this request, or to procure or contract for services or
equipment.

The County of Mecosta may accept any item or groups of items, unless the vendor qualifies
their offer to specific limits.

The County of Mecosta may accept any item or groups of items at the stated per unit price,
unless the vendor qualifies their offer to specific limits. If the quantity purchased has an effect
on the price per unit, indicate the price break points in relation to the number of units requested
in the specification pages.

Product pricing shall be in effect for ninety (90) days after the acceptance date.

The vendor's proposal will provide the name and telephone number for an individual within the
vendor's organization with the ability to authorize proposal changes and/or negotiate
specifications and/or price throughout the duration of this agreement.

By submitting a bid, each vendor represents that:

        a.      The vendor has read and understands the RFP.
        b.      The proposal has been made in accord with the RFP.
        c.      The vendor has contacted the RFP Coordinator to arrange a site visit and
                discuss the project.
        d.      Any costs associated with preparing proposals in response to this RFP are the
                sole responsibility of the respondent.

The terms of this bid specification shall be construed in accordance with the laws of the State of
Michigan. Any and all litigation or actions commenced in connection of this bid shall be
instituted in the appropriate courts in the State of Michigan.

The successful bidder shall not assign, transfer, convey or otherwise dispose of the Award of
Bid or his right to execute it or his right, title, or interest to it or any part thereof or assign any of
the monies due or to become due under the Award of Bid, without prior written consent of the
County of Mecosta.


1.8          Vendor Site Tours
There will not be a formal proposal conference conducted for vendors wanting a site survey of
the main office facilities. A site visit is not required for the proposal but the County of Mecosta
will be available to allow proposing vendors an opportunity to obtain first-hand exposure to the
implementation environment. To schedule a site tour, contact the RFP Coordinator.




                                             Page 7
1.9           Proposal Questions
RFP questions must be forwarded to the RFP Coordinator. The preferred method of questions
is via email. All official questions and answers will be in writing and made available to all
vendors.

1.10          RFP Evaluation Factors
The County of Mecosta will evaluate the proposals to determine the most advantageous
proposal. We will use the following factors to evaluate the proposals listed in order from most to
least important:

        Ability of the proposed system(s) to meet the stated requirements
        Proposed vendor experience and qualifications related to delivering, installing and
         maintaining the proposed system
        Total cost of ownership for the proposed system
        References of comparable installations noting quality of past performances
        Documented training plans for users and Information Technology staff
        System warranty, technical support and annual maintenance offerings
        RFP response document completeness




2 Requirements
Vendors must provide brief, clear, and concise responses to the following requirements with
illustrations where appropriate.

2.1          System Capacities
The following table describes the number of IP phone sets that are required at each location.

                                                            22 Button          24 Button
                      BasicPhone       8 Button Phone
       Location                                               Phone              Phone
                      Equivalent         Equivalent
                                                            Equivalent         Equivalent
 Services Building
  County Building




2.2          System Architecture
2.2.1       Identify the manufacturer, make and models of the proposed solution, including a
            brief overview of the proposed solution.




                                         Page 8
2.2.2     Provide a network diagram that shows the system elements of the proposed solution
          including all locations.

<Insert your network diagram here>


2.2.3     Does the proposed solution support end-to-end SIP signaling. Describe how SIP
          provides end-to-end signaling in your communications architecture?



2.2.4     Does the proposed solution utilize Session Initiation           Protocol   (SIP)   for
          communications to all handsets and media gateways?



2.2.5     Does the proposed solution support the ability to integrate additional SIP-based
          applications and SIP devices with the base system? Describe how the proposed
          solution provides the ability to add and integrate SIP-based applications and devices
          to the base system.



2.2.6     Does the proposed solution support a Windows and/or Linux operating system with
          additional security built in? Describe the operating system supported by the
          proposed solution.



2.2.7     A minimum server footprint is required. How many servers are required to implement
          the minimum capacity requirements?



2.2.8     Does the proposed solution support a centralized system with the ability to distribute
          and centrally administer and manage call processing and voice mail/auto attendant
          services across the corporate WAN?



2.2.9     Does the proposed solution provide scalable and modular connectivity to the PSTN
          or legacy PBX in a single 1U chassis? Describe the equipment and interfaces that
          are used to connect to the Public Switched Telephone Network (PSTN).



2.2.10    Does the proposed system support connectivity of analog phones, fax machines,
          modems, and other analog devices? How are analog phones and devices such as
          fax machines connected to the system?




                                        Page 9
2.2.11    Does the proposed solution support Power Failure Transfer Station (PFTS) for a
          minimum of one line at each location?



2.2.12    Describe how the proposed solution can be implemented in a manner supporting a
          planned migration from legacy phones to IP phones, with all users sharing the same
          voice mail system.



2.2.13    Can the same servers used to implement the solution be used to host other business
          or communications applications?



2.3      Remote Sites and Survivability
2.3.1    Does the proposed solution support the deployment at selected remote locations of full
         call processing feature functionality with redundancy to the central system?



2.3.2    Does the proposed solution optionally support the deployment of full voice mail and
         auto attendant feature functionality at selected remote locations?



2.3.3    Does the proposed solution provide the same call processing and voice mail feature
         set and administration interfaces at all locations that are part of a distributed call
         processing and voice mail system?



2.3.4    Does the proposed solution provide the ability to administer all locations from a central
         position, with updates automatically propagated to remote call processing systems?



2.3.5    Does the proposed solution provide the ability to administer all locations from the local
         call processing system, with updates automatically propagated to the central call
         processing system?



2.3.6    Does the proposed solution provide PSTN survivability for any location, so that when
         connectivity to the central or local call processing system is disrupted in any way, the
         users at the location can place outgoing calls to the PSTN/PBX and receive incoming
         calls from the PSTN/PBX?




                                         Page 10
2.4     Redundancy and Reliability
2.4.1   Does the proposed solution provide redundancy ensuring no single point of failure for
        the entire system, including servers, software, and interfaces to external networks?



2.4.2   Are failovers to redundant servers or gateways automatic and not require any action
        by users?



2.4.3   Are established calls dropped during server failover if network connectivity is not lost



2.4.4   When unavailable equipment becomes available, is the system automatically restored
        to its original state in a redundant configuration?



2.4.5   Does the proposed solution provide redundancy of the call processing and voice
        mail/auto attendant systems?



2.4.6   Does the proposed solution support redundancy of call processing and voice mail/auto
        attendant systems across two geographically disparate locations across the corporate
        WAN?



2.5     Scalability
2.5.1   Can the number of devices and mailboxes be increased as we need them over the
        next 5 years? In what increments?



2.5.2   Is the proposed solution able to add call processing systems to remote locations
        without the need to add additional capacity at the central call processing system
        across the corporate WAN as we need them over the next 5 years?



2.5.3   Is the proposed solution able to scale PSTN gateway capacity?




                                        Page 11
2.5.4   Is the proposed solution able to scale messaging mailbox and auto attendant
        capacity?



2.5.5   Is the proposed solution able to scale simply by adding resources such as CPU,
        memory, and disk?



2.5.6   Is the proposed solution able to dynamically allocate CPU resources to an operational
        system without restarting it?



2.6     Interoperability
2.6.1   Is the proposed solution architected on open standards with the ability to support other
        vendors’ SIP-based devices?



2.6.2   Does the proposed solution employ standards-based protocols for the telephones to
        learn their voice VLAN?



2.6.3   Does the proposed solution utilize 802.3af Power over Ethernet specification to power
        the IP Phones?



2.7     Collaboration
2.7.1   Does the proposed solution support LDAP connectivity to Microsoft Active Directory for
        one way synchronization of IP PBX user information, including name, IP PBX
        extension number, address, and email?



2.7.2   Does the proposed solution support LDAP connectivity to OpenLDAP directory for one
        way synchronization of IP PBX user information, including name, IP PBX extension
        number, address, and email?



2.7.3   Does the proposed solution support email integration with Novel GroupWise, Microsoft
        Exchange 2003 and Exchange 2007 for the purpose of auto-delivering voice and fax
        messages as attachments in email messages?




                                       Page 12
2.7.4   Does the proposed solution support email integration with Novel GroupWise, Microsoft
        Exchange 2003 and Exchange 2007 for the purpose of synchronizing voice and fax
        messages as attachments in email messages between the email server and the user’s
        inbox using a standards based poll driven interface?



2.7.5   Does the proposed solution support the ability for users to view presence and chat with
        their contacts with no additional software or hardware?



2.7.6   Does the proposed solution support the ability for users to connect up to 6 parties on
        an audio conference using a soft phone without the need for an external conferencing
        server?



2.8     Data Network
2.8.1   Does the proposed solution adhere to internationally recognized standards for the
        implementation of VoIP quality of service throughout the network?



2.8.2   Does the proposed solution not require a specific vendor’s data networking equipment
        for deployment of the voice solution?



2.8.3   Does the proposed solution provide the ability for us to monitor Quality of Service of
        VoIP calls?



2.9     IP Phones
2.9.1   Describe your phone set models, including the number of system appearances,
        buttons, display, and features of each phone.



2.9.2   Describe the SIP-based soft phones available with your solution.



2.9.3   Describe the SIP-based software attendant console supported by the proposed
        solution.




                                       Page 13
2.9.4       Describe the options for powering IP phone sets.



2.9.5       Describe the options for connecting the IP phone sets to the LAN.



2.9.6       Can IP phone sets share existing Ethernet ports with data devices or do they require
            separate Ethernet ports?



2.9.7       Do any of your IP phone sets support gigabit to the desktop?



2.9.8       Do IP phones require manual intervention to upgrade phone software?



2.9.9       Complete the following Phone Features table, answering “Y” for compliance of the
            feature in the standard General Available (GA) product, “P” for partial compliance
            (and complete the notes column), or “N” for no compliance (and optionally complete
            the notes column).

               If a feature is available but optional, list the price in the Notes column.

               If the feature is optional, but included in the system price as bid, type Included in the
               Notes column

               You may attach additional pages as needed to elaborate on your responses.
               However, you must cross-reference all attachments to the appropriate item(s) on the
               questionnaire.

                                                               Comply?
Feature name                                                                 Notes
                                                              (Y, N, or P)

Automatic Profile Updates

Automatic Phone Software Updates

Button mapping

Country Specific Tones

Desk Use

DHCP capable phones

DTMF Dialing

DTMF Monotone

Dynamic Codec Selection

Echo Cancellation, Acoustic




                                              Page 14
                                                                       Comply?
Feature name                                                                         Notes
                                                                      (Y, N, or P)

Echo Cancellation, Handset

Integrated Ethernet Support 10/100 (2 ports)

Integrated Ethernet Support 10/100/1000 (2 ports)

Faceplate localization

Fixed Button Labeling

Flexible date/time display

Hands free Installation of phones

Headset Support

Locked Down Phones (MAC support)

Multi-lingual display

One-button send all calls

One-button speed dial

One-button voice mail

Power, External

Power over Ethernet (IEEE 802.3af)

Full Duplex Speaker Phone

Static IP Configuration

VLAN Support

G.722.2 (wideband)

G.711 (u-Law)

G.729A/B

Voice activity detection

Voice Prioritization

Volume control

Wall Use

4 non-programmable line/feature         keys with hard label/status
indicators

18 programmable line/feature keys with hard label/status indicators


8 programmable line/feature keys with hard label/status indicators


3 context sensitive soft feature keys


4 context sensitive soft feature keys




                                                      Page 15
                                                                       Comply?
Feature name                                                                         Notes
                                                                      (Y, N, or P)

Cursor/navigator interface for display control

Attendant Console with 4 programmable buttons with status LEDs
(conference, transfer, serial transfer, park, hold), and ability to
monitor BLF and speed dial up to 100 extensions on a single
console, with ability to daisy chain up to 3 consoles




2.10 System Features
2.10.1     Does the proposed solution provide the ability to route long distance calls over the
           appropriate, usually least costly, trunk group via public or private networks, IP or
           traditional?



2.10.2     Does the proposed solution support the ability to route calls based on ANI/DNIS/CLID
           incoming call information?



2.10.3     Does the proposed solution support the ability to route calls to alternate route points in
           cases of congestion or failure of a device interfacing with the PSTN?



2.10.4     Does the proposed solution provide the ability to set bandwidth usage for call
           admission controls on a per-region and per-site basis?



2.10.5     Describe the ability of the proposed solution to support many different music on hold
           sources, and how these sources can be assigned on a per-user basis.



2.10.6     Briefly describe the 911/E911 capabilities of your solution.



2.10.7     Is operator intervention required or are specific phones required when dialing
           emergency calls?



2.10.8     How are media gateways assigned to handle emergency calls when the call processor
           is unavailable?




                                                     Page 16
2.11 Calling Features
2.11.1      Describe the systems Call Accounting Features



2.11.2      Complete the following Calling Features table, answering “Y” for compliance of the
            feature in the standard General Available (GA) product, “P” for partial compliance (and
            complete the notes column), or “N” for no compliance (and optionally complete the
            notes column).

            If a feature is available but optional, list the price in the Notes column.

            If the feature is optional, but included in the system price as bid, type “Included” in the
            Notes column

            You may attach additional pages as needed to elaborate on your responses. However,
            you must cross-reference all attachments to the appropriate item(s) on the
            questionnaire.

                                                                      Comply?
Feature name                                                                        Notes
                                                                     (Y, N, or P)

Anonymous All

Anonymous Next

Anonymous Call Reject

Automatic Call Distribution

Bridged Line Appearance

Bridged Line Appearance, MWI

Bridged Line Appearance, Shared Hold

Busy Lamp Field. Specify max for each phone model
Multiple System Appearance (multiple appearances of same
extension), Specify max for each phone model
Call Admission Control on a regional and per-site basis for either
number of calls or bandwidth
Call Conference, Three Way Calling

Call Conference, Six Way Calling

Call Conference, Drop

Call Coverage

Call Drop

Call Duration Display

Call Forward All

Call Forward Busy

Call Forward No Answer




                                                       Page 17
                                                          Comply?
Feature name                                                            Notes
                                                         (Y, N, or P)

Call Forward Out of Coverage

Call Forward Programmable

Call Forward Reminder

Call Forward Remote
Call History (Missed, Answered, Placed Logs)
Call Logs Display Sort

Call Hold

Call Hold Reminder

Call Park/Retrieve

Call Park, Fallback

Call Park, Button Mapping

Call Pickup, Directed

Call Pickup, Group

Call Restrictions, Blocking Inbound

Call Restrictions, Blocking Outbound

Call Restrictions, Call Screening

Call Restrictions, Toll Screening

Call Restrictions, Black List

Call Restrictions, White List

Call Restrictions, Forward to Trunk

Call Restrictions, Transfer to Trunk

Call Return

Call Transfer, Attended

Call Transfer, Unattended

Call Transfer, Fallback on Transfer Failure

Call Transfer, Restrictions

Call Waiting

Called ID, Called Party

Caller ID, Calling Party Number

Caller ID, Calling Party Name

Caller ID, Privacy

Camp On Busy (Automatic Call Back)

Customer Accounting and Billing Codes




                                               Page 18
                                                                        Comply?
Feature name                                                                          Notes
                                                                       (Y, N, or P)

Class of Service Override

Delayed or No Ringing

Distinctive Ringing, Ring Patterns (Different Types of Calls)

Distinctive Ringing, Selective Ringing (Ident-A-Call)

Do not disturb

Feature Codes (from IP phones)

Feature Access Codes (from analog phones)

Forced Account Codes

Forward to Mail

Directory, Local User

Directory, Global User

Hands Free Support

Hotline (hot ring down circuits)
Hunt Group with ability login/logout to one or more hunt groups that
the phone belongs to, Number of hunt groups and members per
hunt group
Hunt Groups, Linear

Hunt Groups, Circular

Hunt Groups, Calling Group

Hunt Groups, MWI

Hunt Groups, View Hunt Group Status

Hunt Groups, Malicious Call Trace

Hunt Groups, Call Coverage

Last Number Redial

Malicious Call Trace

Message Waiting Indication (MWI), Audio


Messaging Waiting Indicator (MWI), Visual

Missed Call Indicator

Mobility, Single Region Hot Desking

Mobility, Multi Site Hot Desking
Music on hold. Specify number of MoH sources that can be
configured.
Mute

Paging, Analog External Paging System




                                                        Page 19
                                                             Comply?
Feature name                                                               Notes
                                                            (Y, N, or P)

Paging, SIP External Paging System

Paging, Phone to Phone (Send Beep with Calling Number)

Paging, Group (Zone)

Phone Lock/Unlock

Power Fail Transfer Station Support

Privacy, Calling Number Suppression
Privacy, Block Silent Monitor/Barge-in
Serial Calling (Transfer with Callback)
Silent Monitor/ Barge- In
Speed Dial, Personal
Speed Dial, System
Transfer to voicemail, Direct
Voice Mail access
Warmline (warm ring down circuits)
Unified Messaging
Message Folders
Message Deposit
Message Deposit Treatment Options
Message Retrieval
Message Review
Message Review Options
Message Auto Playback
Message Review Playback Controls
Message Reply
Message Forward
Message Append
Message Annotation
Message Save
Message Delete
Message Delete Retrieval
Message Record Options
Message Send
Message Send Treatment Options
Message Delivery to non-subscribers
Message Schedule Delivery
Message Delivery Report
Message Broadcast
Message Notification




                                                  Page 20
                                                Comply?
Feature name                                                  Notes
                                               (Y, N, or P)

Message Notification Options
Message Auto Delivery
Message Priority
Default System Greeting
Personal Normal Greeting
Personal Busy Greeting
Personal Extended Absence Greeting
Personal Scheduled Greetings
Personal Distribution Lists
Administrator Distribution Lists
System Distribution Lists
Directory Search
Directory Search Dial By Name
Online Help
Setup Assistant Tutorial
Personal Address Book
Shortcut Keys
Personal Auto Attendant
Prompt Bypass
Mailbox Full Alert
Virtual Calling Card
Privacy
Family Mailbox
Zero Out
Call Back
Call Monitor
Message Waiting Indicator
Music On Hold
Force Password Change
User Password Change
User Provisioning through TUI
User Provisioning through web
Find Me Follow Me
Find Me Follow Me Call Intercept
Fax Message Deposit
Fax Message Retrieval
Fax Delivery to Fax Machine
Fax Auto Delivery to Fax Machine
Fax Auto Delivery to E-Mail




                                     Page 21
                                                                        Comply?
Feature name                                                                          Notes
                                                                       (Y, N, or P)

Never Busy Fax
Email Integration
Email Auto Delivery
Voice Mail POP3/IMAP4 Client Integration
Email Synchronization
IP Messaging Web Interface Updates
Voice Mail Security Enhancements
Administration of all parameters through XTerminal interface
Administration of mailbox and class of service through web interface
Multiple Language Support
Telephone User Interface (3Com)
Telephone User Interface (Basic)
Text To Speech
Auto Attendants
Information Mailboxes
Announcement Mailboxes
Bulletin Board
System Bulletin/Broadcast Mailboxes
Forms (Q&A) Mailboxes
Survey Mailboxes
Mailbox On The Fly
Multiple Administrators
Multiple Permission Levels
Mailbox Administration
Class of Service Administration
Batch Import
Import Mailbox/COS
Export Mailbox/COS
Company/Division administration
Send User Groups
Pager Templates
Time Zones
Mailbox Un-login
System Backup
System Restoration
System Status
System Alarms
Reports
Call Detail Records




                                                      Page 22
2.12        System Administration
2.12.1   Does the proposed solution support a web browser based interface for system
         administration from any position on the corporate network?



2.12.2   Describe the process for administrators to remotely access the system. Identify if any
         special software or plug-in is required.



2.12.3   Does your solution provide central administration and management of all users and
         equipment across all locations?



2.12.4   Is your system compliant with government standards on time zones?



2.12.5   Does the proposed solution support automated daylight savings time?



2.12.6   Could there be several security levels established in order to access the administration
         applications?



2.12.7   Describe the US 508/ADA compliance of your system.



2.12.8   Does the proposed solution support the ability to upload Music on Hold and other
         audio source files using the web browser interface?



2.13        Reporting
2.13.1   Provide a brief overview of your system’s data reporting and real-time monitoring
         capabilities.



2.13.2   Can your system aggregate performance data from multiple PBX systems, sites,
         servers, and/or components?




                                        Page 23
2.13.3   Describe the historical reports that can be generated from the call detail record system
         of your solution.



2.13.4   Describe the licensing requirements for your historical (call detail record) reporting
         system.



2.13.5   Describe the server requirements for your historical (call detail record) reporting
         system.



2.13.6   Does your system provide the user with the ability to create custom real-time and
         historical reports?



2.13.7   Provide examples of the standards reports available with the proposed solution for the
         telephony and voice mail sub-systems.



2.14        System Management
2.14.1   Briefly describe the network management capabilities of the proposed solution.



2.14.2   Describe the server and database requirements of your management solution.



2.14.3   Can the system be programmed to perform system backups automatically?



2.14.4   Does the management system support the graceful shutdown of services?



2.14.5   Describe how we can monitor the status of equipment in your proposed solution. Does
         the equipment send SNMP alerts?




                                        Page 24
2.14.6   Can QoS monitoring be done through SNMP for monitoring with your network
         management solution?



2.15        Implementation
2.15.1   Fully describe the implementation process.



2.15.2   Define a schedule for product delivery.



2.15.3   The County of Mecosta will require an inventory list (shipping list) of all accepted
         products from this proposal which will include the expected date of delivery for each
         item. The County of Mecosta will expect an itemized invoice for all products, which
         shall match the inventory list.



2.16        Maintenance
2.16.1   Fully describe the maintenance plans available for the proposed solution.



2.17        Training
2.17.1 Provide a description of the System Administration and Maintenance training courses.




3 Vendor Overview
3.1.1    Describe your company’s experience with implementing SIP-based communications
         solutions.



3.1.2    Provide a brief history of the proposed solution and state its experience in our market.



3.1.3    List references here:




                                         Page 25
4 Pricing
Please remember that the County of Mecosta is tax exempt.

All quotes must be itemized and include per unit and total extended cost to the County of
Mecosta as indicated on the Specification Page(s).


Quote #1: Upgrading equipment needed to replace the T1 with the Alvarian Breeze wireless
system.

Quote #2: Upgrading the entire phone system.


Please note that proposals submitted without a stand alone Quote #1 will not be considered.




                                        Page 26
5 BIDDER INFORMATION

This Proposal is submitted in the name of:_________________________________________

The undersigned hereby designates below his business to which all notices, directions or other
communications may be served or mailed:

Street_______________________________________________________________________
City_________________________________________________________________________
State_____________________________________________                Zip Code_____________


The undersigned hereby declares that he or she has the legal status checked below:
       (     )    INDIVIDUAL
       (     )    INDIVIDUAL DOING BUSINESS UNDER AN ASSUMED NAME
       (     )    CO-PARTNERSHIP
       (     )    The Assumed Name of the Co-Partnership is registered in the County of
                  _________________________________, Michigan
       (     )    CORPORATION INCORPORATED UNDER THE LAWS OF THE STATE OF
                  _________________________________. The Corporation is:
                  (    )   LICENSED TO DO BUSINESS IN MICHIGAN
                  (    )   NOT NOW LICENSED TO DO BUSINESS IN MICHIGAN


The name, titles and addresses of all persons who are Officers or Partners in the organization
are as follows:
       NAME AND TITLE                                             ADDRESS
___________________________________                 ___________________________________
___________________________________                 ___________________________________
___________________________________                 ___________________________________
___________________________________                 ___________________________________
SIGNED AND SEALED THIS _____ day of _________________________________________
________________________________                    ___________________________________
BY (Signature)                                      PRINTED NAME OF SIGNER
                                                    ___________________________________
                                                    TITLE
                                                    ___________________________________
                                                    TELEPHONE NUMBER


                                        Page 27

								
To top