RFP_26F-0326_Specifications.docx

Request for Proposal 26F-0326

Telecommunication Systems

Scope of Work Specifications

SPECIFICATIONS

Purpose of specifications: Specifications are designed to enable offeror to satisfy a requirement for a product, material, process, or service. A specification may be expressed as a standard, part of a standard, or independent of a standard. No specification is intended to limit competition by eliminating items capable of satisfactorily meeting the requirements of the procurement. If offeror believes a specification is unnecessarily restrictive, offeror must notify Mohave prior to specified proposal due date and time.

Partial proposals: Mohave may consider partial proposals for award of a contract.

Use of brand names: Brand names, trade names, model numbers, and/or catalog numbers may be used to describe the standard of quality, performance, and other characteristics needed to meet member requirements. Use of the name of a manufacturer, brand, make, or catalog number is not intended to limit or restrict competition, nor does it restrict offeror from the submission of brand equivalent offers. However, Mohave reserves the right to decide whether alternatives are equivalent to the materials and/or equipment described in the solicitation. Mohave shall be the sole judge of equivalent quality, and Mohave’s decision shall be final.

Compliance with specifications: Offerors shall offer products, materials, processes, or services they believe meet the specifications. The fact that a manufacturer, supplier, or offeror chooses not to produce or provide product, material, process, or services to meet the specifications shall not be considered sufficient cause to adjudge the specifications as restrictive.

Additional references and definitions used for specifications (acronyms used in the solicitation are noted in bold font below):

· ANSI (ANSI): www.ansi.org

· Arizona Registrar of Contractors: https://roc.az.gov/

· CSA Group: www.csagroup.org

· Distributed Computer Telephony (DCT): DCT is a computer telephony term for technology used in the industry. This is open technology, which does not have a website for reference.

· Energy Star: www.energystar.gov

· ETL Certification by Intertek (ETL): www.intertek.com/marks/etl/faq

· Federal Communications Commission (FCC): www.fcc.gov

· International Electrotechnical Commission (IEC): www.iec.ch

· IEEE (IEEE): www.ieee.org

· Integrated Services Digital Network (ISDN): ISDN is digital communications that allows for the transmission of voice, data, video and graphics at very high speeds, over standard communications. ISDN does not have a website for reference.

· ISO (ISO): www.iso.org

· ITU (ITU): www.itu.int

· National Electronic Code (NEC): https://www.nfpa.org

· North American Numbering Plan Administrator (NANPA): www.nanpa.com

· Occupational Safety and Health Administration (OSHA): www.osha.gov

· Signal Computing System Architecture (SCSA): SCSA is open architecture developed by leading telecommunications companies. This open architecture does not have a website for reference.

· Safety Data Sheet (SDS): https://www.osha.gov/hazcom

· Simple Network Management Protocol (SNMP): www.net-snmp.org

· Telecommunications Industry Association (TIA): https://tiaonline.org/

· UL Solutions (UL): www.ul.com

SPECIFICATION INSTRUCTIONS

Exceptions/Deviations from specifications: Offerors will respond to each numbered specification by checking the appropriate “Comply” or “Exception/Deviation*” box. “No Bid” items shall be marked as such in the appropriate “Exception/Deviation*” box. Your exceptions/deviations must be clearly explained. Reference the specification that you are taking exceptions/deviations to detail any proposed substitute language, and clearly explain how the exceptions/deviations meet or exceed specifications. Unacceptable exceptions/deviations shall remove your proposal from consideration for award. Mohave shall be the sole judge on the acceptance of exceptions and Mohave’s decision shall be final. Details for exceptions/deviations shall be listed by specification number on the Scope of Work and Specifications Acceptance Form.

Specifications

1.1 General Specifications

1.1.01 Contract vendor shall provide telecommunication systems to include, but not be limited to: installation of new systems, replacement of legacy systems, upgrade of legacy systems, expansion of legacy systems, and maintenance of legacy systems.

1.1.02 Contract vendor shall install telecommunication systems in compliance with manufacturer’s instructions, local, state, and federal codes, and industry standards.

1.1.03 Contract vendor may provide services specific to the scope of work and specifications, that may include, but not be limited to: consulting, design, providing products only, onsite and remote customer service and technical support, warranty service or support, and training. Any pricing for these services shall be included in the electronic pricing workbook. Services provided at “No-charge” should be provided in Value-added Services offered.

1.1.04 Contract vendor shall have a current and maintain through the life of an awarded contract, Arizona contractor’s C-67 or CR-67 Low Voltage Communication Systems license from the Arizona Registrar of Contractors. Provide copy(ies) of Arizona Registrar of Contractors license(s) in Vendor Submissions (See Primary Vendor Information – Qualifications and Experience).

1.1.05 Contract vendor that is in the license application process shall provide evidence of application. An awarded contract will be contingent on a successful award of C-67 or CR-67 Low Voltage Communication Systems license. Provide a copy of the Arizona Registrar of Contractors application receipt with pending number in Vendor Submissions (See Primary Vendor Information – Qualifications and Experience).

1.1.06 Telecommunication systems shall comply with all current applicable provisions and standards of the following: ANSI; CSA Group; DCT; ETL; FCC; IEC; IEEE; ISDN; ISO; ITU; NEC; OSHA; SCSA; SNMP; TIA; UL; and local, state, and federal building codes. Where compliance with two or more standards creates a conflict for minimum quantities or quality levels, refer the uncertainties to member for a written decision before proceeding.

1.1.07 Contract vendor shall cooperate with architect, engineer, general contractor, subcontractor, or other vendor working on the same project, as necessary and as directed by member, to assure that the scope of work for a project is accomplished.

Specifications

1.2 Telecommunication System Equipment Specifications

1.2.01 Contract vendor shall offer telecommunication systems from manufacturers regularly engaged in telecommunication systems and be of the latest designs and technology.

1.2.02 Contract vendor shall only provide telecommunication equipment supplied by a primary manufacturer or compatible secondary equipment designated and accepted by the primary manufacturer for use in a manufacturer’s designed telecommunication system.

1.2.03 All electronics shall be designed for continuous use without degradation of function or performance. When practical, one manufacturer shall be used to ensure compatibility.

1.2.04 Contract vendor may offer refurbished, remanufactured, or used equipment. The type of equipment shall be clearly identified on the quote. Contract vendor shall only offer refurbished, remanufactured, or used equipment for service/repairs of legacy systems when new replacement equipment is no longer manufactured or available. Member has the right to refuse any refurbished, remanufactured, or used equipment.

1.3 Telecommunication System Installation Specifications

1.3.01 During installation, all connections and pieces of equipment shall be fully tested by a technician trained by the manufacturer. Contract vendor shall only install local area network cable that has been tested and verified by ETL and has been listed in compliance with current applicable TIA and ISO/IEC.

1.3.02 Contract vendor shall ensure all work areas are identified by signage, warning tape, or other warning devices, as required by law and standard practice. Signage shall be the property of contract vendor and remain in place until work is finished. Contract vendor shall remove all signage when work is completed.

1.3.03 Member acceptance of installed or upgraded system shall be in writing only after a satisfactory test of the entire network or installation in the presence of member. Project scope of work shall define the terms for acceptance and title to the completed work. If any part of the cabling requires member to assume control prior to project completion, this requirement will also be clearly defined and agreed upon. Both parties shall agree on the definition of what constitutes final acceptance before final payment.

1.3.04 Contract vendor shall provide training of the telecommunication system to include, but not be limited to: overall system operation, individual unit operation, description, and operation of installed equipment, any user level testing or troubleshooting.

1.3.05 Contract vendor shall, upon request, submit complete documentation for the telecommunication system to member (including architect, engineer, or general contractor) for approval prior to work. The documentation shall include model numbers, type, rating, size, style, manufacturer’s name and manufacturer’s catalog data sheets, and cabling drawings.

1.3.06 All materials used by contract vendor at a worksite shall have a SDS as required by law. The SDS shall be filed in a centrally located area accessible by the both the workers and member.

Specifications

1.4 Design and Infrastructure Specifications

1.4.01 Contract vendor may develop a needs analysis report at the request of member that includes an assessment of current hardware and identifies what can be incorporated into the new system design.

1.4.02 Needs analysis report shall list all structural changes to the worksite that are necessary for implementation of new system.

1.4.03 Needs analysis report shall identify potential disruptions and inconveniences that could be encountered during installation and testing of new equipment.

1.4.04 Needs analysis report shall recommend training requirements necessary for operation, installation, and maintenance of the new system.

1.4.05 Needs analysis report shall list the minimum requirements for LAN/VLAN/WAN technology, hardware, software, and services.

1.5 Infrastructure for Departmental and Workgroup LANs Specifications

1.5.01 Site infrastructure cabling is requested. Member shall not be bound to use cabling services offered under an awarded contract and may use an alternative when such use is in members best interest.

1.5.02 Site infrastructure cabling shall last a minimum of fifteen (15) years of use and be built using current applicable ANSI/TIA structured cabling standards.

1.5.03 Cable runs shall be designed to use industry appropriate pathways that meet current applicable local, state, or federal building codes that provide protection of cables, and provide easy installation or replacement of cables.

1.5.04 Contract vendor shall deliver cabling materials to the worksite in new, dry, unopened, and marked containers showing product and contract vendor’s name. Damaged or unlabeled materials shall not be accepted. Contract vendor shall deliver materials in sufficient quantity to allow for continuity of work.

1.5.05 Only horizontal cable types recommended by current applicable ANSI/TIA standards shall be installed.

1.5.06 Cabling infrastructure shall be grounded as described in the current applicable ANSI/TIA standard.

1.5.07 Copper-based cabling systems shall be protected from electromagnetic interference (EMI) by being shielded or installed a sufficient distance from power lines and other sources of EMI.

1.5.08 Equipment shall be protected from power fluctuations (e.g., spikes, surges, brownouts, blackouts) by surge suppressors and/or uninterruptible power supplies.

1.6 Infrastructure for Organizational Network Specifications

1.6.01 The interconnection of two or more workgroup LAN/VLAN/WAN networks to form a backbone network shall be available in multiple configurations and use a variety of technologies, as described in the current applicable ANSI/TIA standard.

1.6.02 Transmission technique employed should include, but not be limited to: switched Ethernet, SD-WAN, various wireless technologies, MPLS, dark fiber, and DWDM, or TCP/IP technology. The backbone should be able to operate at current applicable speeds.

1.6.03 Backbone network shall connect various LANs to each other using routers, cloud managed networking, and current wireless standards.

1.6.04 Backbone shall use cloud-based network management and integrated security models.

Specifications

1.7 Ethernet Switch and Switch Module Specifications

1.7.01 Contract vendor shall offer passive, active, and multi-gigabit speed switches or concentrators shall be available.

1.7.02 Workgroup switches shall have the ability to connect multiple network devices, and shall support multiple network technologies and multiple type of transmission mediums.

1.7.03 Smart or intelligent switches shall provide for management functions and be able to connect multiple technologies and media types.

1.7.04 Enterprise switches shall support all cabling and networking needs of the system.

1.7.05 Contract vendor may offer modules that plug into the back plane of switches or modules that provide bridging, routing, and management functions.

1.7.06 Switches shall be desktop models or rack mountable.

1.8 Router Specifications

1.8.01 Routers shall be scalable and modular; shall be OSI layer 3 capable; shall allow for multiple LAN/WAN protocols; and shall provide encryption, VPN, and firewall capabilities.

1.8.02 Routers shall support the current applicable IEEE 802.11 Wi-Fi protocols. Routers shall be wireless or wired.

1.8.03 Access routers and router hubs that function as full-featured routers are requested. Devices should provide WAN and LAN interfaces and support multiple protocols.

1.8.04 Contract vendor may offer specialized routers that include, but are not limited to: core routers, edge routers, or virtual routers.

1.9 Network Gateway Specifications

1.9.01 If protocol translation is required between proprietary or legacy protocol stacks (e.g., SNA, DNA, AppleTalk) and modern standards such as TCP/IP, it is requested the contract vendor provide and configure all necessary network gateway devices.

1.9.02 Network gateways shall provide the following services to include, but not be limited to: VoIP, Internet of Things (IoT), cloud storage, application access, cellular access, or wireless access.

1.9.03 Network gateways shall provide for the following functionality to include, but not be limited to: security scalability, multiprotocol capability, visibility, and analytical capability.

1.10 Network Management System (NMS) Specifications

1.10.01 The NMS shall have a graphical user interface; allow for LAN/VLAN/WAN topology discovery; allow for in-band and out-band transmission of network related data; allow for monitor and control to port level; and allow cloud-based network management.

1.10.02 The NMS shall be available in either a Unix, Windows, or Linux based operating system.

1.10.03 The NMS shall allow for network traffic monitoring, provide network statistics, allow for multiple topologies (e.g., 10/100T, GbE), shall have alarms that can be preset by member to monitor various system outages or problems, and include network based cyber security applications that interact with the network switch hardware.

Specifications

1.11 Dynamic Host Configuration Protocol Server (DHCP) Specifications

1.11.01 DHCP shall support automated IP address assignment and management for networked devices; provide a graphical or web-based administrative interface; support operations across multiple IP subnets and VLANs; and integrate with DNS services to support dynamic DNS updates including forward and reverse record updates.

1.11.02 Converged and hyper-converged infrastructure for virtualized environments, along with server and storage support services, are requested.

1.11.03 The DHCP shall be available in either a Unix, Windows, or Linux based operating system.

1.12 Remote Access Server (RAS) Specifications

1.12.01 The RAS shall be of current applicable internet-based, remote access, and VPN technology.

1.12.02 The RAS shall allow for LAN/WAN modularity and scalability.

1.12.03 The RAS shall allow for multiple topologies and have adequate security and encryption protection.

1.13 Cellular Access Control Specifications

1.13.01 Cellular access control products offered may include, but not be limited to: cellular access switches and cellular access multiplexers.

1.13.02 Cellular access switches and cellular access multiplexers shall comply with all industry open standards; shall be OSI layer 2 and 3 capable; shall be interoperable for all specified LAN/WAN protocols; and shall have a standards compliant network management system implementation plan (SNMP).

1.14 Network Firewall Specifications

1.14.01 Firewalls shall work at the Internet, intranet, department, and workgroup level, depending on member’s requirements. Firewall software shall include intrusion prevention, malware protection, and security information and event management centralized logging.

1.14.02 Firewalls shall be equipped with, but not be limited to the following features: address translator, packet filters, circuit gateways, application-level gateway, stateful traffic inspections and event logging. Software solutions may include optional end-to-end cyber security solutions.

1.15 Power Monitoring and Uninterruptible Power Supply (UPS) Specifications

1.15.01 Power monitoring products shall monitor for voltage levels, current, load, power quality indicators, and transient events.

1.15.02 Power monitoring products shall provide local or centralized monitoring through graphical or web-based interfaces. Monitoring products shall support the following: data logging, data reporting, network management system (NMS) or central monitoring platform integration.

1.15.03 Power monitoring products shall measure the power feed for true current; AC/DC voltage levels; EMF; harmonics; impulses demand vs. energy; and cycle-by-cycle disturbances.

1.15.04 UPS products shall be rack mountable and installed in the equipment rack of the equipment being protected.

Specifications

1.15 Power Monitoring and Uninterruptible Power Supply (UPS) Specifications (Cont’d)

1.15.05 Any UPS unit supporting a server shall have at least 100% greater rating than the supported loads and have a minimum of eight (8) minutes of run-time at full speed. In addition, it shall warn the NMS that power has been lost when it is in the battery power operational mode.

1.16 Network Monitor, Analyzer, and Tester Specifications

1.16.01 Network monitors shall monitor, analyze, and test OSI layers 1-7.

1.16.02 Network monitors shall inventory and store data for all connected LAN/VLAN/WANs; provide real-time frame monitoring; monitor peak, average, and current network utilization, errors counts, station and user activity, and traffic and protocol distributions.

1.16.03 Network analyzers shall analyze and store data for all connected LAN/VLAN/WANs; provide real-time frame monitoring; and analyze peak, average, and current network utilization, error counts, station and user activity, and traffic and protocol distributions.

1.16.04 Network testers shall test and store data for all connected LAN/VLAN/WANs; provide real-time frame monitoring; and test peak, average, and current network utilization, error counts; station and user activity, and traffic and protocol distributions.

1.17 Telephone and Network Integration - General Communication Specifications

1.17.01 Automated services and state-of-the-art telephony are requested.

1.17.02 Telephone system shall include speech recognition that permits a caller to reach a destination by speaking their name or by using their touch-tone phones to enter an extension, name, department or “0” to get a live operator.

1.17.03 Telephone system shall include a voice attendant system that provides a twenty-four (24) hour voice messaging communication to individuals and departments.

1.17.04 Telephone systems shall support routing of incoming calls to designated destinations, such as extensions, operators, voicemail, external numbers, or other configured endpoints.

1.17.05 Telephone system shall include software that works in conjunction with a networked computing device to provide a phone line directory with first party call control functions including dial, transfer, and conference.

1.17.06 Telephone system shall include a call center program that allows a caller to select options while waiting, including listening to music or a special message, leaving a message, or to request information.

1.17.07 Telephone system shall support secure remote user access, allowing authorized users to authenticate and place or receive call using external devices (e.g., cellular, landlines) with similar functionality of an internal extension.

1.17.08 Telephone system with the ability to record telephone voice messages digitally and store the messages as easily accessed files is preferred.

1.17.09 Telephone system that can provide out calling to member or member’s customers to announce events is requested.

1.17.010 Telephone system with password protected voice mailboxes is requested.

Specifications

1.17 Telephone and Network Integration - General Communication Specifications (Cont’d)

1.17.011 Fully digital/IP, hybrid systems (end-to-end), or cloud-based systems are required. Configurations shall be modular in design with universal ports. All hardware shall be NANPA compliant. Configurations may be expanded to the full capacity by the addition of circuit card modules, voice terminals, station wiring, and cabinets. None of the original equipment shall become obsolete through expansion.

1.17.012 Telephone unit station shall contain all of the necessary printed circuit cards, power supplies and other components necessary for line and intercom switching and feature operation. System shall be of modular design for ease of expansion and replacement of defective components.

1.17.013 Telephone unit station instruments/voice terminals shall be multi-button, digital type, with modular connectors, and a built-in speaker for tone signals and intercom voice announcements. The instrument shall have the appropriate number of programmable buttons as required for normal operations. The instrument shall provide audible and visual signals to indicate ringing, call, and feature status. Wireless end-point devices or Wi-Fi based phones may be offered. All instruments shall be hearing aid and amplified handset compatible.

1.17.014 Headset and connector may be offered for connection with a telephone unit station instrument. The connector shall contain a volume control and an on-off switch to enable switching between headset and handset operation.

1.17.015 The attendant telephone console (physical or soft) shall have access to all lines in the system with the ability to transfer any call to any and all voice terminals in the system.

1.17.016 Contract vendor may offer direct station selection/busy lamp field (DDS/BLF) console with its associated features for installation adjacent to the attendant telephone console serving as a main call answering point. Note, this can be offered as a function of the software console. Attendant telephone console shall include the required circuit card(s), installation, wiring, and programming. The DSS/BLF shall have the appropriate number of buttons and associated lights for the maximum number of voice terminals specified by the end user.

1.17.017 Programming should be able to be completed via software on a computer, on the network, or via a browser.

1.17.018 Contract vendor may offer peripheral equipment which may include, but not be limited to: music source (digital) recorded announcement machines (4-channel, digital); paging amplifier (100 W); speaker (indoor/outdoor); voice mail; terminal; and battery backup (4-hour at the wired level which does not require venting).

1.18 Hosted Voice over Internet Protocol (VoIP) Systems/Platform Telephone System Specifications

1.18.01 Contract vendor may offer hosted VoIP systems and platforms.

1.18.02 Hosted VoIP systems and platforms shall provide the same functionality as an onsite VoIP system.

1.18.03 Hosted VoIP systems and platforms shall manage all sites and endpoints with web controls.

1.18.04 Hosted VoIP systems and platforms shall provide flexible system with configuration options.

Specifications

1.18 Hosted Voice over Internet Protocol (VoIP) Systems/Platform Telephone System Specifications (Cont’d)

1.18.05 Hosted VoIP systems and platforms shall provide standard system options and features.

1.18.06 Contract vendor hosted VoIP systems and platforms shall offer support services to monitor voice infrastructures. Services shall include after hour emergency contact information.

1.19 Telephone and Network Integration – VoIP Telephone Systems Specifications

1.19.01 VoIP systems shall allow voice-data to flow over a general purpose packet-switched network.

1.19.02 VoIP systems shall allow for the integration of various services to include, but not be limited to: video conversations; message and data file exchange in parallel with a conversation; audio and video conferencing; managing address books; and passing information between users.

1.19.03 VoIP systems shall allow members to make and receive calls, regardless of their location on the LAN/VLAN/WAN.

1.19.04 VoIP systems shall support quality-of-service (QoS) and call traffic prioritization to help maintain acceptable voice quality over shared networks.

1.19.05 VoIP systems shall include an UPS to maintain VoIP services during a power outage.

1.19.06 VoIP systems shall provide for emergency call services.

1.19.07 VoIP systems shall meet industry standards for allocating and assigning telephone numbers according to current applicable ITU E.164 standards.

1.19.08 VoIP systems offered shall meet either current applicable Session Initiation Protocol (SIP) or ITU H.323 standards.

1.20 Telephone and Network Integration – VoIP Installation, Management, and Administration Specifications

1.20.01 Contract vendor shall provide for the installation of equipment, configuration of software, testing of the equipment, and establish a management capability for the administrators of the LAN.

1.20.02 Network equipment configuration shall allow for replacement of components or modular equipment without loss of system configuration and with minimal service disruption.

1.20.03 Network management system shall be menu-driven and shall have a graphical user interface. The network management system hardware platform shall be fully configured, including all necessary interface hardware, software, and cabling.

1.20.04 Network management system shall support SNMP and have an integrated database with the ability to provide hooks to outside software packages.

1.20.05 Network management system shall provide multi-layered management of supported network devices with automatic recognition of all manageable elements. Network management system shall provide graphic reports, reporting network topology, traffic, and statistics.

1.20.06 Network management system shall be able to perform diagnostic tests at all nodes in the LAN. Network management system shall have the ability to gather and store information about the operation of the network and publish reports about the system as requested, including information about major and minor alarms.

Specifications

1.20 Telephone and Network Integration – VoIP Installation, Management, and Administration Specifications (Cont’d)

1.20.07 Contract vendor shall offer a network management system that has the ability to distinguish context-sensitive and time-sensitive alarms (either major or minor) and shall have screens to display these alarm classifications. Users shall be able to set alarm thresholds.

1.20.08 Network management system software updates and revisions shall be made available to member without additional charge during the warranty period.

1.20.09 Contract vendor shall ensure firestops are used for each cable interface between floors and fire-rated spaces per current applicable code, statute, or standard. Drawings shall show firestops and materials used. Drawings shall be provided to member.

1.20.010 Contract vendor shall supervise the installation of any cabling for systems provided under an awarded contract.

1.20.011 Contract vendor shall provide physical support and cable management means for all copper runs and termination points, especially between floors, between and on cable trays, and within equipment racks. Proper bend radius to wire diameter shall be maintained. Cable run outside shall be suitable for runs buried in conduits and aerial runs. Cable performance shall not be degraded, and the cable shall not be damaged in any way by long-term immersion in ground water. Aerial cable outer jacket shall be suitable for long-term exposure to sunlight and weather, with a life cycle greater than twenty (20) years. Outer jackets on all cables shall be fungus inert and crush resistant.

1.20.012 Spliced fiber optic cable shall be spliced in accordance with current industry standards. Contract vendor shall test all splices to verify the fiber optic cable meets current industry standards.

1.20.013 Contract vendor shall test fiber optic network to verify network meets current industry standards. If any segment of cable is found to have unsatisfactory test results, that specific cable link shall be replaced with a new link, and retested.

1.20.014 Copper cabling used for network shall pass all tests for Category 6A. Cable used shall be standard color-coded and UL listed. Cable shall be secured in a neat and organized manner in accordance with current industry standards.

1.21 Warranty Specifications

1.21.01 Minimum length of warranty required under this contract shall be one (1) year for equipment and components, and fifteen (15) years for all cabling (copper and fiber optic).

1.21.02 Warranties shall begin on the date of the final written acceptance by member. Where a manufacturer’s warranty begins upon the date of purchase, contract vendor agrees to extend the warranty period to the date of final acceptance by member.

1.22 Legacy Equipment Specifications

1.22.01 Contract vendor shall provide equipment and current manufacturer technology to support member legacy systems.

1.22.02 Legacy equipment shall include, but not be limited to: channel banks; digital access carrier systems (DACS); analog, digital, and optical repeaters; bridge (intelligent repeater); bridge routers (brouters); non-VoIP telephone systems; channel service units (CSU) or data service units (DSU).

Specifications

1.22 Legacy Equipment Specifications (Cont’d)

1.22.03 Channel banks and DACS shall be equipped with data cards, including, but not limited to: subrata data multiplexer cards, inverse multiplexer cards, DS0 and DS1 cards, and switched 56 cards.

1.22.04 Repeaters provided shall include, but not be limited to: local; remote using copper or fiber; multi-port; buffered (non-discriminating bridges); or hub.

1.22.05 Bridges shall be multi-port or switching to provide local bridges for back-to-back type connections or remote bridges for LANs separated by a large distance.

1.22.06 Brouters that use proprietary technologies and do not operate with other brouters, bridges, and routers are not acceptable.

1.22.07 Non-VoIP telephone systems shall allow voice-data to flow over a general-purpose circuit-switched network.

1.22.08 Non-VoIP telephone system switches shall support a wide number of interfaces including, but not limited to: X.25 dedicated links (for Electronic Data Interchange [EDI]); EIA RS-232 links; ISDN BRI; contact for connecting analog devices; and auxiliary for analog trunk connections networks.

CSU/DSUs shall be 56k/T1/DS3/frame relay capable; support multiple LAN/WAN protocols; support integration of synch data and digital voice channels; and provide in-band and out-band data management.

Indicate if the following features are standard or an option for the systems that you are providing by indicating “Standard”, “Option”, or by using “S” or “O” in the S/O column. If the feature is not being bid, enter “No Bid” in the No Bid column.

1.23 Telephone System Standard and Optional Feature Specifications

1.23.01 Abbreviated Dialing (Station or System Level): This feature shall allow users to store frequently called telephone numbers or dial access codes in system memory and access these phone numbers or access codes using an abbreviated procedure.

1.23.02 Account Codes: This feature shall allow the caller to input billing information (e.g., client account number) when placing/receiving a call.

1.23.03 Alerting: This feature shall provide unique patterns of voice terminal alerting for all voice terminal users to distinguish between various types of incoming calls. The pattern should indicate various types of calls including, but not limited to: terminal-to-terminal call, an attendant or incoming trunk call, or a priority call. Users of terminals serving both voice and data should be provided with the ability to transfer or cut off alerting patterns at their voice terminals.

1.23.04 Alternate Console Position: This feature shall provide for the capability of an alternate attendant console position, as well as the regular attendant console position(s). This position shall provide all regular attendant console functions. A lockout capability shall be affected from the main console to prevent unauthorized access.

1.23.05 Attendant Manual Splitting: This feature shall allow the attendant to consult privately with one party on a call without a second party hearing.

1.23.06 Attendant Call Waiting: This feature shall provide for calls completed by the attendant (to a busy series voice terminal line) to be held waiting while a tone indication of the waiting call is directed toward the busy voice terminal.

1.23.07 Attendant System Control of Trunk Group Access: This feature shall allow for the restriction of terminal lines and incoming tie trunks from accessing selected trunk facilities. Calls to restricted facilities shall be routed to the attendant position.

1.23.08 Attendant System Control of Voice Terminals: This feature shall provide for the restriction of selected lines or groups of lines.

1.23.09 Attendant Direct Trunk Group Selection: This feature shall provide for an attendant to be able to directly access an idle-outgoing trunk by depressing a button associated with the desired trunk group.

1.23.010 Attendant Display: This feature shall provide for an alphanumeric display to allow the attendant to visually identify: calling number, class of service, trunk identification, or other important information.

1.23.011 Authorization Code: This feature shall allow a terminal user or attendant to dial a code, which overrides the facility’s restriction level associated with the terminal.

1.23.012 Automated Attendant: This feature shall automate the transfer of incoming calls to the particular voice terminal or voice message box that corresponds to the caller’s inputs.

Indicate if the following features are standard or an option for the systems that you are providing by indicating “Standard”, “Option”, or by using “S” or “O” in the S/O column. If the feature is not being bid, enter “No Bid” in the No Bid column.

1.23 Telephone System Standard and Optional Feature Specifications (Cont’d)

1.23.013 Automatic Call Distribution: This feature shall provide for a large volume of incoming calls to be answered by a group of telephones allocated for this purpose. Incoming calls are served on a first-in, first-out basis and are distributed among the available telephones (agent positions) so that the agent position that has been idle the longest is presented with the first call. A reporting package shall be included that provides, at a minimum, agent, and agent group and trunk activity reports.

1.23.014 Automatic Callback: This feature shall provide for voice terminal users, calling a busy station, to be automatically connected to that line when the station becomes idle.

1.23.015 Automatic Route Selection/Least Cost Routing: This feature shall provide routing of long distance calls over the most preferred route based on time of day and day of week. An access code and the public network telephone number shall be utilized to select the least expensive route. At least 10-digit screening/routing capability is required. All digit translation required to conflate the call shall be performed automatically.

1.23.016 Auxiliary Equipment Access: This feature shall provide (through an extension or trunk) for the auxiliary equipment access between the system and dictation, voice, analog interfaces, or paging equipment.

1.23.017 Call Forwarding-Internal: This feature shall allow calls (internal or external) destined for the attendant or a voice terminal to be routed to another voice terminal or to the attendant. This feature shall be activated or canceled by the user or the attendant.

1.23.018 Call Park: This feature shall allow a voice terminal user to have the ability to place a call on hold without tying up the activating line.

1.23.019 Call Pickup: This feature shall allow a voice terminal user to have the ability to answer any call directed to another terminal line within the user’s pickup group.

1.23.020 Call Waiting: This feature shall allow any call attenuating to terminate on a user’s voice terminal, when the user is busy on another call, to be held waiting while a tone indication of the waiting call is directed toward the busy terminal. The called terminal user may then be connected to the waiting call at the user’s convenience.

1.23.021 Caller Identification: This is an ISDN service feature. Caller ID provides out-of-band channel delivery of data about an incoming caller.

1.23.022 Class of Service: For each station on the system, the proposed system shall have the ability to provide variable classes of service, alterable from an on-premises administration terminal. Service class shall define the specific calling privileges of the associated station.

1.23.023 Computer Telephone Integration: This feature allows interconnection of computers and telephone systems wherein the computer directs the system to switch calls to various internal resources and also might forward stored data to various internal resources. It is preferred to be compliant with Telephony Application Programming Interface and/or Telephony Server Application Programming Interface.

Indicate if the following features are standard or an option for the systems that you are providing by indicating “Standard”, “Option”, or by using “S” or “O” in the S/O column. If the feature is not being bid, enter “No Bid” in the No Bid column.

1.23 Telephone System Standard and Optional Feature Specifications (Cont’d)

1.23.024 Conference, Three-Party: This feature shall allow a voice terminal user to have the ability to connect a third party to an existing 2-party call.

1.23.025 Console Alarm Display: This feature shall allow systems to provide audible and visual alarms at the attendant console, which signal major and minor system failures.

1.23.026 Data Protection: This feature shall protect data calls from intrusion by the various bridge-on features, which may otherwise disturb data transmission, and include VoIP encryption.

1.23.027 Dial Access to Attendant: This feature shall allow the attendant to be dial accessed by voice terminal users. Unique access codes can be assigned to individual attendant positions to allow dial access to a specific attendant position.

1.23.028 Direct Department Calling: This feature shall provide a distribution service for selected high incoming call volume departments.

1.23.029 Direct Inward Dialing: An incoming call from the exchange network shall be directed to the dialed voice terminal without attendant intervention.

1.23.030 Direct Outward Dialing: A voice terminal user shall be able to access the public exchange network without attendant assistance.

1.23.031 Dual-tone Multi-frequency (DTMF) Service: This feature shall provide DTMF signaling for terminal and attendant console users.

1.23.032 Hold: This feature shall allow terminal users to maintain a current call in a held state. Access to the held call shall be provided.

1.23.033 Hunting: This feature shall allow an incoming call to a voice terminal to be routed to an idle voice terminal in a prearranged group when the called terminal is busy. Circular and linear hunt groups shall be possible.

1.23.034 Intercept Treatment: This feature shall allow calls that cannot be automatically completed, to be routed to either an attendant or a recorded announcement.

1.23.035 Intercom: This feature shall allow voice terminal users to be connected to a conning intercom path with other voice terminals. An alerting signal shall be provided to audibly identify intercom calls.

1.23.036 Last Number Redial: This feature shall allow voice and data terminal users to automatically redial the last number called by depressing a single terminal button.

1.23.037 Line/Feature Status Indication: A status lap shall be provided with an indication of the call status for each call appearance on all digital voice and data terminals.

1.23.038 Line Lockout: Intercept tone shall be provided to a voice terminal user who remains off-hook for 10 seconds without dialing.

1.23.039 Loudspeaker Paging Access: This feature shall allow the attendant and voice terminal users access to voice paging equipment.

1.23.040 Moves, Adds, and Change Administration by Member: This feature shall allow moves, adds, deletes, and changes to extension numbers, service classes, and station and trouncing arrangements to be accomplished by member via an on-premises phone/terminal.

Indicate if the following features are standard or an option for the systems that you are providing by indicating “Standard”, “Option”, or by using “S” or “O” in the S/O column. If the feature is not being bid, enter “No Bid” in the No Bid column.

1.23 Telephone System Standard and Optional Feature Specifications (Cont’d)

1.23.041 Message Waiting: This feature shall allow two modes of usage, manual and automatic. In the manual mode of operation, a voice terminal user shall have the ability to activate a status lamp at another designated voice terminal to indicate there is a message for the designated terminal user. System shall also have the ability to automatically light a message-waiting lamp at a user terminal in conjunction with various message services provided.

1.23.042 Music-on-Hold Access: This feature shall allow music to be provided to the held party during any holds interval.

1.23.043 Night Answer from Console: This feature shall automatically reroute incoming calls to an attendant position, in this case an executive station set after hours.

1.23.044 Off-premises Terminal: This feature shall provide access to the system by voice terminals located off-premises from the system location. Off-premises terminals shall be connected to the system via a line or trunk circuit, depending upon the application required.

1.23.045 Override: This feature shall allow a warning tone to be applied to a busy connection followed by bridge-on of the calling party, when activated by a calling terminal user on a call to a busy terminal line.

1.23.046 Privacy: This feature shall prevent another user from entering into an established call.

1.23.047 Queuing: This feature shall allow for calls to an all-busy trunk group to be placed in a queue while awaiting an idle trunk.

1.23.048 Private Network Access: This feature shall provide connection to a tandem tie trunk network, a common control switching arrangement, and an enhanced private switched communications service network or an electronic tandem network. Private network access calls shall have the ability to tandem through the local or distant system or on-premises system without attendant assistance if this option is provided.

1.23.049 Recall Signaling: This feature shall provide a unique audible signal, which indicates that the system has recognized a recall and is ready to receive a request for activation of a voice terminal feature.

1.23.050 Remote Access: This feature shall provide users outside of the system access to the system via the public network for the purpose of using system services.

1.23.051 Remote Maintenance System Access: This feature shall enable a remote central facility to access the system via the serving network for administration, maintenance, and automated alarm reporting.

1.23.052 Serial Calls: This feature shall provide the ability for the attendant to extend a call to two or more voice terminals or trunks in succession without requiring the calling party to redial the attendant.

1.23.053 Station Message Detail Recording/Call Recording: This feature shall provide a means to permanently record the completion time, call duration, dialed number, and the trunk group used for outgoing and/or incoming calls. Any authorization code shall also be recorded. Records shall be available for extensions and the attendant(s) position(s).

Indicate if the following features are standard or an option for the systems that you are providing by indicating “Standard”, “Option”, or by using “S” or “O” in the S/O column. If the feature is not being bid, enter “No Bid” in the No Bid column.

1.23 Telephone System Standard and Optional Feature Specifications (Cont’d)

1.23.054 Terminal Busy Indication: This feature shall provide a visual indication of the switch hook status of a particular voice and data terminal.

1.23.055 Time Reminders: This feature shall alert the attendant after 30 seconds when a call on the console is waiting to be connected.

1.23.056 Toll Restriction: This feature shall restrict voice terminals from completing toll calls or calls to the toll operator without attendant assistance.

1.23.057 Transfer: This feature shall permit certain voice terminal users to transfer a 1-party call to another party. Voice terminal users shall be able to transfer a 1- or 2-party call to a third party.

1.23.058 Trunk Group Busy/Warning Indicators: This feature shall alert the attendant (with visual warning indication) when a preset number of trunks in a group is busy, or a visual busy indication when the entire trunk group is busy.

1.23.059 Trunk-to-Trunk Connections: This feature shall allow an incoming trunk call to be extended to an outgoing trunk, or allow an outgoing trunk call to be extended to another outgoing trunk.

1.23.060 Uniform Call Distribution: This feature shall allow incoming listed directory number trunk calls to be terminated, without attendant assistance, directly to a prearranged group of voice terminals.

1.23.061 Visually Impaired Attendant Services: This feature shall enable a visually impaired person to operate the attendant position by augmenting the normal visual signals with special devices and audible signals.

1.23.062 Voice Mail System: Voice mail system shall be fully integrated with the telephone system.

Telecommunication Systems Specifications

*Exceptions/deviations must be listed on the Scope of Work and Specifications Acceptance Form. List the specification number for each exception/deviation.

RFP 26F-0326

Scope of Work and Specifications Acceptance Form

Signature on the Offer and Acceptance Form certifies complete acceptance of the Scope of Work and Specifications in this solicitation, except as noted below (additional pages may be attached, if necessary).

Check one of the following responses to the Scope of Work and Specifications:

We take no exceptions/deviations to the Scope of Work and Specifications.

(Note: If nothing is listed below, it is understood that no exceptions/deviations are taken.)

We take the following exceptions/deviations to the Scope of Work and Specifications. All exceptions/deviations shall be clearly explained. Reference the corresponding Scope of Work or Specifications that you are taking exceptions/deviations to. Provide details on your exceptions/deviations below:

(Note: All requested exceptions/deviations must be clearly explained. Reference the specific language that you are taking exceptions/deviations to detail any proposed substitute language, and clearly explain how the exceptions/deviations meet or exceed Scope of Work and Specifications. Unacceptable exceptions/deviations may remove your proposal from consideration for award. Mohave shall be the sole judge on the acceptance of exceptions/deviations and Mohave’s decision shall be final.)

image1.png