INVITATION TO NEGOTIATE (ITN)
ITN #851
FOR
THE FLORIDA LEGISLATURE
NETWORK SERVICES
Replies to be opened by the
Florida Legislature
Office of Legislative Services
Purchasing Office
111 West Madison Street, Room 880, (850) 488-2322
Tallahassee, Florida 32399-1400
at 3:00 P.M., March 31, 2011
NAME OF RESPONDENT________________________________________________
ADDRESS__________________________________________________________
CITY_____________________________STATE____________ZIP CODE_______
SIGNATURE________________________________________________________
(Authorized Officer)
_______________________________________________________
(Printed or typed name)
F.E.I.D._____________________________________DATE________________
TELEPHONE NUMBER (________)_______________________________________
EMAIL ADDRESS:
TABLE OF CONTENTS
Section
1.
Description
General Information
2.
Current Environment
10
3.
Scope of Services
14
4.
Administrative Documents Required
43
5.
Evaluation
46
Appendix A
Appendix B
Service Address Listing
Respondent’s Recommendation and Cost
Respondent’s Cost Summary
Response to Network Option 1
Response to Network Option 2
Response to Network Option 3
Response to Network Option 4
Optional Available Services
SLA Parameters
References
Glossary
Respondent’s Mandatory Response Checklist
Non-Collusion Statement
Disclosure Information
Warranties Certification
Policy 2.151, Joint Policies and Procedures
Appendix C
Appendix D
Appendix E
Appendix F
Appendix G
Appendix H
Appendix I
Appendix J
Page Number
3
SECTION 1: GENERAL INFORMATION
1.1
Introduction
The Florida Legislature (Legislature) intends to obtain competitive sealed responses to
upgrade and improve the Legislature's Wide Area Networks and Internet services. The
successful Respondent will be required to provide service as described in the Scope of
Services, Section 3 of this ITN.
The successful Respondent must be a Primary Multi-Protocol Label Switching (MPLS)
Provider or any State of Florida Agency Contract offering for Managed MPLS Service.
1.2
Objective
The Legislature is seeking responsible Respondents to provide network services as described
in the Scope of Services, Section 3 of this ITN. The goal is to provide greater access and
reduce the Legislature's overall communication cost.
The Legislature will cooperate fully with the successful Respondent in providing any
information which is maintained by the Legislature that is necessary for the successful
Respondent to perform assigned tasks.
1.3
Mandatory Pre-Response Conference
A Mandatory Pre-Response Conference will be held at 2:00 pm, March 8, 2011, in the
Claude Pepper Building, 111 West Madison Street, Room G01, Tallahassee, Florida 323991400.
Only respondents in attendance will be eligible to submit a response for these services.
1.4
Questions/Inquiries
Questions for additional information or clarification may be submitted in writing (by mail,
hand-delivery, email to bullock.sandra@leg.state.fl.us or by FAX to 850/414-1909) and
received no later than March 11, 2011.
All questions should be addressed as follows:
QUESTIONS ITN #851
NETWORK SERVICES
Written responses to all questions will be posted on the website at
www.leg.state.fl.us/ITN851 on the date listed in the Schedule of Events, Section 1.8.
It is the responsibility of each Respondent to monitor the website at
www.leg.state.fl.us/ITN851 for new and changing information.
1.5
Submission of Responses
Sealed responses are to be submitted to the Office of Legislative Services (OLS) Purchasing
Office, Room 880, Pepper Building, 111 W. Madison St., Tallahassee, FL 32399-1400 on
or before March 31, 2011, by 3:00 P.M.
All responses must be submitted on forms furnished herein and as required by Evaluation,
Section 5 of this ITN. Responses shall be properly executed in the name of and by the
person, firm, or corporation submitting the response.
ITN #851
3
Responses must be returned in a sealed envelope indicating the date, time of response
opening, response title, and ITN number.
Responses must be submitted in two separate sealed parts: a Technical Response and a
Cost Response, due on or before March 31, 2011, by 3:00 p.m. Response packages must be
boxed or sealed and identified as follows:



Name of Vendor (Your Company’s Name and any subcontracting entity)
Type of Response: (Technical Response or Cost Response)
ITN #851, Network Services
The Technical Response must not contain any cost information.
It shall be the sole responsibility of the Respondent to see that his or her response is received
at the proper location on or before the stated time of response opening. All responses
received after that time shall be returned unopened.
Note: A person or affiliate who has been placed on the convicted vendor list following a
conviction for a public entity crime may not submit a response on a contract to provide goods
or services for a period of 36 months from the date of being placed on the convicted vendor
list.
1.6
Opening of Responses
Sealed responses will be opened by the OLS Purchasing Office of the Legislature in Room
880, Pepper Building, 111 West Madison Street, Tallahassee, FL 32399-1400 at 3:00 PM,
March 31, 2011. All responses are subject to the conditions specified herein.
The Legislature reserves the right to waive any minor irregularities or technicalities in
any responses received, to cancel any request or reject any or all responses in whole or
in part, with or without cause, to solicit new responses or to accept the response which,
in its judgment, will be in the best interest of the Legislature.
1.7
ITN Coordinator
All Respondents’ communications concerning this ITN, including but not limited to the
“QUESTIONS/INQUIRIES”, must be directed to the ITN Coordinator of the OLS
Purchasing Office listed below. Unauthorized contact regarding this ITN with other
Legislative employees may result in disqualification. Any oral communications will be
considered unofficial and non-binding to the Legislature. Respondents should reply only in
writing (mail, hand-delivered, email or fax) to the following:
Sandra Bullock
Office of Legislative Services
Purchasing Office
Room 880, Claude Pepper Building
111 West Madison Street
Tallahassee, FL 32399-1400
FAX (850) 414-1909
bullock.sandra@leg.state.fl.us
ITN #851
4
1.8
Schedule of Events
Issuance of ITN
February 25, 2011
Mandatory Pre-Response Conference
March 8, 2011, 2:00 p.m.
Last date to submit written questions
March 11, 2011
Written responses to all questions posted
On website at www.leg.state.fl.us/ITN851
(on or about)
March 17, 2011
Responses due by 3:00 p.m. for opening
(fax or email not acceptable)
March 31, 2011
Anticipated review and evaluation of Technical and
Cost responses completed
April 19, 2011
Notification to the
Respondents to begin Negotiations
April 26, 2011
Contract negotiated and executed by the
Parties (on or about)
May 3, 2011
Special Accommodation: Any person requiring a special accommodation because of
disability should call the Purchasing Office at 850/488-2322 at least five (5) work days prior
to the response opening date. If you are hearing or speech impaired, please contact the
Purchasing Office by using the Florida Relay Service which can be reached at 1-800-9558771 (TDD).
1.9
Contract Period and Final Contract Award
The contract term will begin upon completion of negotiations and execution of the contract
between the Legislature and the Service Provider. The Legislature anticipates that the initial
term of this contract will be four years from the Effective Date.
There may be up to (two) two-year renewals of the term at the discretion of the Legislature.
Renewals are not guaranteed and are contingent upon funding and performance of the
Service Provider.
The award will consist of this ITN, any addenda to this ITN, the successful Respondent’s
response to this ITN, the contract, any purchase order(s) issued as a result of this ITN, and
such other terms and conditions agreed between the parties that may be necessary to the
Legislature.
ITN #851
5
1.10
Contract Cancellation
This award may be canceled by the Legislature with 30 days advance written notice to the
Service Provider. In the event an award is terminated by such notice from the Legislature,
the Service Provider will be paid for services provided through the date of termination.
Notice will be sufficient if it is hand-delivered personally, mailed by certified mail, or sent
via courier service to the Service Provider.
1.11
Warranties
The Respondent represents that it is professionally qualified and possesses the requisite
skills, knowledge, qualifications and experience to provide the required services specified.
The following are warranty certification requirements that must be certified in writing
(Appendix I) in the Administrative Documents Required (Section 4). If the Respondent
cannot so certify to any of the following, the Respondent must submit with its Response a
written explanation of why it cannot do so within the Administrative Documents Required.
1.11.1 The Respondent or any other organization associated with the ITN is not
currently under suspension or debarment by the State or any other governmental
authority.
1.11.2 To the best knowledge of the person signing the Response, the Respondent, its
affiliates, subsidiaries, directors, officers, employees of any other organization
associated with this ITN are not currently under investigation by any governmental
authority and have not in the last ten years been convicted or found liable for any act
prohibited by law in any jurisdiction involving conspiracy or collusion with respect to
bidding on any public contract.
1.11.3 To the best knowledge of the person signing the Response, the Respondent, its
affiliates, subsidiaries, directors, officers or any other organization associated with
this ITN have no delinquent obligations to the State, including a claim by the State for
liquidated damages under any other contract.
1.11.4 To the best knowledge of the person signing the Response, the Respondent, its
affiliates, subsidiaries, directors, officers or any other organization associated with
this ITN have not within the preceding three years been convicted of or had a civil
judgment rendered against them or is presently under indictment for or otherwise
criminally or civilly charged for commission of fraud or a criminal offense in
connection with obtaining, attempting to obtain or performing a federal, state, or local
government transaction or public contract; violation of federal or state antitrust
statutes; or commission of embezzlement, theft, forgery, bribery, falsification or
destruction of records, making false statements, or receiving stolen property.
1.11.5 To the best knowledge of the person signing the Response, the Respondent, its
affiliates, subsidiaries, directors, officers or any other organization associated with
this ITN have not within a three-year period preceding this certification had one or
more federal, state, or local government public transactions terminated for cause or
default.
ITN #851
6
1.12 Availability of Funds
The performance of the Legislature under any awards from this ITN shall be subject to and
contingent upon the availability of funds lawfully appropriated by and to the Legislature and
applicable for the purpose of the services specified.
1.13 Payment Terms
All invoicing and payments will be made monthly in arrears and in accordance to Policy
2.151, Joint Policies and Procedures of the Presiding Officers (Appendix J). Payment will be
made after receipt of a correct invoice and approval by the Legislature. Travel, when
required, must be authorized in advance and is to be included in the total costs of this ITN.
1.14 Insurance
The successful Respondent shall not commence any work in connection with an award until
it has obtained all of the appropriate insurance coverages to adequately protect the
Legislature from any and all liability and property damage hazards which may result in the
performance of an award. Furthermore, all insurance shall be with qualified insurers duly
licensed to transact business in this state. The Legislature shall be exempt from, and in no
way liable for, any sums of money which may represent a deductible in any insurance policy.
The payment of such deductible shall be the sole responsibility of the successful Respondent
providing such insurance. Upon request, the successful Respondent shall furnish the
Legislature an insurance certificate which will evidence that all of the appropriate coverage’s
are fully in effect.
1.15 Indemnification
The successful Respondent shall be fully liable for the actions of its agents, employees,
partners, or subcontractors and shall fully indemnify, defend, and hold harmless the
Legislature and its officers, agents and employees from suits, actions, damages, and costs of
every name and description, including attorney’s fees, arising from or relating to personal
injury and damage to real or personal tangible property alleged to be caused in whole or in
part by the successful Respondent, its agents, employees, partners or subcontractors;
provided however, that the successful Respondent shall not indemnify for that portion of any
loss or damages proximately caused by the negligent act or omission of the Legislature.
The successful Respondent’s obligations under the preceding paragraph with respect to any
legal action are contingent upon the Legislature’s giving the successful Respondent (1)
written notice of any action or threatened action, (2) the opportunity to take over and settle or
defend any such action at the successful Respondent’s sole expense, and (3) assistance in
defending the action at the successful Respondent’s sole expense.
1.16 Limitation of Respondent’s Liability
Except as specified in the foregoing section 1.15, for all other claims against the successful
Respondent under any award from this ITN, and regardless of the basis on which the claim is
made, the successful Respondent’s liability for direct damages shall be limited to the annual
value of the Respondent’s total Response under this ITN. No party shall be liable to another
for special, indirect, punitive, or consequential damages, including lost data or records even
if the party has been advised that such damages are possible. No party shall be liable for lost
profits, lost revenue, or lost institutional operating savings. The Legislature may, in addition
to other remedies available to it at law or in equity and upon notice to the successful
Respondent, retain such monies from amounts due to the successful Respondent as may be
necessary to satisfy any claim for damages, penalties, costs and the like asserted by or against
ITN #851
7
it. The Legislature may set off any liability or other obligation of the successful Respondent
under any contract with the Legislature.
1.17 Prohibition Against Assignment
An award of this ITN is for services to be provided by the successful Respondent. The award
may not be assigned by the successful Respondent in whole or in part, unless specified
otherwise in this ITN. The successful Respondent will agree that its performance of any
other services during the term of this award or future awards shall not interfere with the
faithful and timely performance of this award.
1.18 Collusion
Response-rigging is a crime. The Florida Antitrust Act and the Sherman Antitrust Act
prohibit agreements among actual or potential competitors as to which firm will win a
contract put out for response. The antitrust laws also prohibit other forms of price-fixing,
including agreements and conspiracies among actual or potential competitors with the
purpose or effect of raising, fixing, pegging, or stabilizing prices, or allocating (dividing)
geographic markets or contracts. Any suspicion of anticompetitive conduct in connection
with this response should be reported to the State of Florida’s Office of the Attorney General,
Antitrust Section.
Please complete the enclosed Non-Collusion Statement (Appendix G) and enclose with your
ITN package.
1.19 Disclosure Information
Please complete the enclosed Disclosure Information Form (Appendix H) and enclose with
your ITN package.
1.20 Consultant Review
The Legislature reserves the right to share with any consultant of its choosing this ITN and
ITN responses received in order to secure a second opinion.
1.21 Waivers
The Legislature shall not be deemed to have waived any of its rights or remedies hereunder
unless such waiver is in writing and signed by the Legislature. No delay or omission on the
part of the Legislature in exercising any rights or remedies shall operate as a waiver of such
right or remedy or any other rights or remedies. A waiver on any one occasion shall not be
construed as a bar or waiver of any right or remedy on future occasions.
1.22 Cost of Reply Preparation
The cost of preparing the Response is the sole responsibility of the Respondent, whether or
not any award results from this ITN.
1.23 Subcontractors or Third Party Vendors
The successful Respondent will be responsible for all costs to subcontractors or third party
vendors contracted for services by the Respondent.
1.24 Resolution of Disputes
Any disputes between the successful Respondent and the Legislature as to the application,
meaning, or interpretation of any part of an award as a result of this ITN shall be resolved in
Leon County, Florida, by application of Florida law.
ITN #851
8
1.25 Confidential, Proprietary, Trade Secret
If the Respondent considers any portion of the documents, data or records submitted with this
ITN to be confidential, trade secret or otherwise not subject to disclosure pursuant to Section
11.0431, Florida Statutes, the Florida Constitution or other authority, Respondent must also
simultaneously provide the Legislature with a separate redacted copy of its documents, data
or records and briefly describe in writing the grounds for claiming exemption from the public
records law, including the specific statutory citation for such exemption. This redacted copy
shall contain the ITN number and Respondent’s name on the cover and shall be clearly titled
“Redacted Copy.” The Redacted Copy shall be provided to the Legislature at the same time
Respondent submits the document, data or records to the Legislature and must only exclude
or obliterate those exact portions that are claimed confidential, proprietary, or trade secret.
Respondent shall be responsible for defending its determination that the redacted portions of
its documents, data or records are confidential, trade secret or otherwise not subject to
disclosure. Further, Respondent shall protect, defend, and indemnify the Legislature for any
and all claims arising from or relating to Respondent’s determination that the redacted
portions of its response are confidential, proprietary, trade secret or otherwise not subject to
disclosure.
If Respondent fails to submit a Redacted Copy with its reply, the Legislature may produce
the entire documents, data or records submitted by Respondent in answer to a public records
request for these records.
1.26
Clarifications/Revisions
Before award, the Legislature reserves the right to seek clarifications and to request any
information deemed necessary for proper evaluation from all respondents deemed eligible for
award.
ITN #851
9
SECTION 2: CURRENT ENVIRONMENT
2.1
The Legislature
The Legislature maintains two separate Data Centers. The House Office of Information
Technology (House OIT) provides Information Technology (IT) services for the Florida
House of Representatives. The Office of Legislative Information Technology Services
(OLITS) provides IT services for the Florida Senate, Joint Legislative Committees, and other
Legislative Offices. OLITS also provides common shared IT services for the Florida House
of Representatives.
2.2
Network Services
OLITS-managed Wide Area Network
The Florida Senate obtains its current Multiprotocol Label Switching (MPLS) service from
Qwest. There are approximately 50 circuits statewide – 40 Senate district offices and 10 Senate
satellite district offices connecting to the OLITS-managed network in Tallahassee. There are
local servers in each of the 40 Senate district offices to provide DNS, DHCP and local file
sharing. The Senate satellite district offices use the router for DNS and DHCP.
The Senate WAN also provides for connectivity to the Voice over IP service located in
Tallahassee. All customer premise equipment (Cisco 2811s) in district offices have a PSTN
connection should the WAN connection fail. This service is managed by another vendor. The
configuration includes music on hold.
In addition to managing the Senate WAN, OLITS maintains two circuits in Tallahassee for
district office support and testing. The Commission on Ethics also has two circuits for a total of
3mb. All circuits are logically connected to OLITS located in Tallahassee, and terminate into
one 45MB circuit (DS3) in Tallahassee. The WAN is designed for redundancy at the core in
Tallahassee. In the event of a failure in the MPLS Core router all traffic will seamlessly route
through the Qwest provided Internet router.
There are three Metropolitan Area Network (MAN) connections in Tallahassee. The OLITSmanaged Data Center (100MB) circuit provides 45Mbps Internet and 55Mbps Department of
Management Services (DMS) Common Services. Two other circuits are 100Mbps layer 2
trunks used for failover between the Claude Pepper and Senate Building networks.
House OIT-managed Wide Area Network
The Florida House of Representatives Wide Area Network is made up of one hundred twenty
(120) districts and approximately ten (10) satellite offices connecting to the House OITmanaged network in Tallahassee. Each district office connection is provided through local
providers (DSL, cable, MFN). These offices are using split tunneling to allow internet traffic
out their provider and VPN connection to allow for network connection to the House OITmanaged network. Tallahassee consists of two 33mb MFN lines that are set up for failover to
each other.
2.3
Internet Access
OLITS-managed Internet
OLITS has two Internet connections, one 45MB DS3 circuit is provided by Qwest and one
45MB MAN circuit provided by CenturyLink Commercial Services. OLITS manually load
balances outgoing traffic using Border Gateway Protocol (ASN 36514) based on subnet
ITN #851
10
address. The CenturyLink circuit also provides connectivity to the State of Florida Common
Services offerings.
Internet access also provides for external customers’ access to Legislative websites in the
OLITS-managed DMZ.
House OIT-managed Internet
House OIT has two 33MB connections provided by MFN that are set up for failover to each
other.
Internet access also provides for external customers’ access to Legislative websites in the
House-managed DMZ.
2.4
Firewall Services
OLITS and House OIT maintain separate firewalls protecting and controlling access between
the Internet and the internal legislative networks.
2.5
Remote Access Services
OLITS and House OIT provide separate VPN access for approved Legislative staff and
contractors. OLITS maintains support for all Senate and Joint Committee employees for client
based and SSL based VPN. House OIT maintains support for all House employees for client
based and SSL based VPN.
ITN #851
11
Current Network Diagrams
OLITS-managed (Senate and Joint Committees)
District Offices
Commission on
Ethics
Tallahassee
. . . .
INTERNET
Qwest
Qwest MPLS router to
Districts
MPLS failover
Centurylink Commercial
Firewall
Service includes
connection to the State of
Florida Network/ Common
Services
Core Services:
Voice, Email, DNS, etc
DMZ web servers
Senate Office
Building
Internal
Legislative
Network
MAN Failover
OLITS
Tallahassee
Computer Room
Tallahassee MAN
ITN #851
12
House OIT-managed (House of Representatives)
House Districts
MFN
Cable
DSL
Internet
Split-Tunnel
IPS
ec
n
Tu
ne
l
Firewall
MFN/PublicInternet
DMZ
Internal Network
ITN #851
13
SECTION 3:
SCOPE OF SERVICES
All technical requirements defined in Section 3 must be addressed and responded to by any
Primary Multi-Protocol Label Switching (MPLS) Provider or any State of Florida Agency
Contract offering for Managed MPLS Service.
In addition, Respondents must be able to fulfill the requirements labeled [Mandatory –
Respondents must confirm compliance]. Failure to fulfill a Mandatory requirement will result
in disqualification of a Respondent’s Response.
3.1
General Description of the Requested Scope of Services.
3.1.1
Managed Multi-Protocol Label Switching (MPLS) IP VPN Services
a. 40 Senate district offices including managed CPE for minimum 16 LAN ports and
one WAN port, including management and support of the extended wiring as needed
in each office. Each office must be equipped with VoIP failover to a PSTN.
b. Approximately 10 Senate satellite offices including managed CPE for minimum 8
LAN ports and one WAN port, including management and support of the extended
wiring as needed in each office. Each office must be equipped with VoIP failover to
a PSTN.
c. 1 Tallahassee remote office (Commission on Ethics)
d. 2 Tallahassee circuits with Senate district office configurations (one of each CPE
solution, satellite and district) for development and testing
e. 120 House district offices including managed CPE for minimum 8 LAN ports and
one WAN port, including management and support of the extended wiring as needed
in each office. Each office must be equipped with VoIP failover to a PSTN.
f. Approximately 10 House satellite offices including managed CPE for minimum 4
LAN ports and one WAN port, including management and support of the extended
wiring as needed in each office. Each office must be equipped with VoIP failover to
a PSTN.
g. 2 Tallahassee circuits with House district office configurations (one of each CPE
solution, satellite and district) for development and testing
3.1.2 Respondents will provide two unfiltered Internet service connections of at least 45Mbps
– one physically located in the OLITS-managed Data Center and one in the House OITmanaged Data Center. The OLITS-managed Internet service must peer with OLITS BGP
switches to accommodate failover between Internet service providers. The House-managed
Internet service must peer with House BGP switches to accommodate failover between
Internet service providers.
In addition the Legislature requests the option to add a managed Intrusion Prevention/
Intrusion Detection System (IPS/IDS) to the House OIT-managed internet circuit.
ITN #851
14
3.2
Managed MPLS VPN Design Requirements
The Legislature is seeking responses for a secure, Managed MPLS IP VPN and highly
available Internet access service from a Primary Multi-Protocol Label Switching (MPLS)
Provider or any State of Florida Agency Contract offering for Managed MPLS Service.
The Managed MPLS VPN should enable legislative users to enjoy economical and reliable
network access regardless of location and to expand secure remote access to staff.
Implementation of network technology should help limit future cost growth for the network
services needed to support mission-critical business requirements.
The Managed MPLS VPN will provide for data, video streaming and VOIP in its initial
deployment, but will be positioned to include video conferencing and other possible services
including WAN optimization technology.
At a minimum, the Managed MPLS VPN will include the OLITS managed devices (40 Senate
District Offices, approximately 10 Senate Satellite Offices, 1 Tallahassee connection and 2 simulated
district offices). Additionally, the 120 House District Offices, approximately 10 Satellite Offices,
and the Tallahassee connections, may be included.
The managed solution will include the following.

Fully managed end-to-end service with Service Level Agreements (SLAs). The
respondent is required to manage and maintain all circuit wiring and equipment
up to and including the LAN equipment. LAN wiring, that is the wiring from
the CPE to the end user’s device, is not part of the end-to-end service.

Legislative district office connectivity: Four (4) bandwidth options are being
requested for the district offices and must be provided by Respondents. The
Legislature will evaluate all four (4) bandwidth options and reserves the right to
select a bandwidth option that provides the performance required to meet
business needs and is fiscally prudent. The Legislature will evaluate and select
one or more of the bandwidth options. For each bandwidth option the
Respondent’s bandwidth must come as close as possible to the bandwidth
options listed below.
Option 1: minimum 512Kbps
Option 2: minimum 1.5Mbps
Option 3: minimum 3Mbps
Option 4: minimum 6Mbps
ITN #851

Dedicated circuits are preferred, however, other circuit types (Frame Relay,
Digital Subscriber Line, etc.) providing the same bandwidth and quality features
will be considered.
Managed MPLS VPN technology must allow the use of Classes of Service to
facilitate rationing and prioritizing bandwidth to best serve mission-critical
applications.

Managed security and resiliency to include VoIP failover to a PSTN

Respondent-managed Customer Premise Equipment which includes for Senate
districts one WAN port for uplink and 16 LAN ports for intra-office
connectivity and Satellite offices may have one WAN and 8 LAN ports. For
House districts the CPE must include one WAN port for uplink and 8 LAN
ports for intra-office connectivity, House satellite office will require one WAN
15
port and 4 LAN ports.
The Managed MPLS VPN should serve these legislative business requirements for
more bandwidth for business-critical applications, provide the foundation for secure
data, video, and voice communications, and provide a reliable and flexible core
network.
The Legislature desires to achieve the advantages and practicality of Managed
MPLS IP VPN to provide higher reliability through the ability to re-route around
failed network nodes. The Managed MPLS VPN technology employed must allow
the use of Classes of Service that should facilitate rationing and prioritizing
bandwidth to best serve mission-critical applications.
The Managed MPLS VPN solution should allow for reliable, high-bandwidth
connections to all district and satellite offices regardless of their geographical
location. The Managed MPLS VPN network will also need to support the delivery
of mobile solutions and secure remote network access.
3.2.1
Managed MPLS VPN Core Functionality
The Legislature requires that MPLS be a core technology of the proposed network.
Respondent must describe their Managed MPLS VPN network in enough detail for the
Legislature to evaluate the characteristics of the Respondent’s network. Include the
following:
3.2.1.1 Managed and Dynamic MPLS VPN Routing [Mandatory Respondent must confirm compliance] The Legislature requires a core
network that supports the Multi-Protocol Label Switching routing protocol.
Core Network: Describe the following:

Core/backbone with a drawing including any aggregation services.

Access circuit options.

Location of Point of Presence (POP) that will serve this network.

Class of switches in the POPs.

Network strategic plan for the next three years, including roadmap of
when new product/services will be implemented.
3.2.1.2 Non Standard-Based Services: the Legislature desires that the
provisioning of services and related options will be handled by the
Respondent resulting in a standard, routed, IP only enterprise environment.
Describe and explicitly identify all non-standards-based services to be used
to provide Managed MPLS VPN services.
3.2.2
Connectivity
3.2.2.1 Statewide connectivity: [Mandatory - Respondent must confirm
compliance] The Legislature requires connectivity throughout the State of Florida to
conduct its business. The Managed MPLS VPN core network must provide for the
connectivity needs of all currently existing sites as listed in Appendix A.
ITN #851
16
3.2.2.2 Future Statewide Connectivity: The Legislature desires to ensure that the
most cost effective access solutions are used for future connectivity to the Managed
MPLS VPN network. Future needs will include new service addresses.
These sites will exist in rural as well as metro areas. Respondent should be prepared
to connect these sites in an affordable manner. Responses must include a strategy to
address these concerns.
3.2.3
High Availability and Reliability
The Legislature desires that the Managed MPLS VPN core network have High
Availability to properly support its business requirements. Define the strategy and
architecture for providing High Availability within the Respondent’s core network to
include distinguishing features and capabilities for proposed services.
3.2.4
Quality of Service (QoS)
Quality of Service: It is important that critical applications receive SLA contracted
resources across the network, despite varying network traffic loads.
3.2.4.1 QoS Functionality: [Mandatory – Respondent must confirm compliance]
The Legislature requires end-to-end IP QoS features to preferentially handle traffic as
one of the network’s fundamental design philosophies to accomplish the task of
managing resources within the core. The network must be able to prioritize traffic by
tagging packets in order to utilize multiple queues for voice, video and other mission
critical applications and to segregate such traffic from other traffic types that are more
delay-tolerant.
3.2.4.2 Non-standard QoS Services: Describe any QoS functionality that is unique
to the Respondent’s Managed MPLS VPN network that is not based on industry
standards.
3.2.5
Class of Service (CoS)
3.2.5.1 CoS Functionality: [Mandatory – Respondent must confirm compliance]
MPLS Class of Service forwarding is required to be able to classify different types of
traffic based on traffic filters, input interface, either DSCP or CoS values, MPLS
labels, or any IP traffic pattern. Confirm Respondent’s compliance with this
mandatory and define how the Respondent’s Managed MPLS VPN network classifies
different types of traffic.
3.2.5.2 Forwarding Equivalence Classes (FEC): [Mandatory – Respondent must
confirm compliance] Minimum of four (FEC) are required. Respondent should
describe the Respondent’s FEC classes.
ITN #851
17
3.2.6
Bandwidth Increases
The Legislature desires the capability of obtaining increases in bandwidth within a
short timeframe. Beyond the logical service of altering CIR values, describe the
technical features of the proposed Managed MPLS VPN that will provide for the
bandwidth of specific Service Addresses to be increased within a few days. For
example:
3.2.7

The Respondent could participate with the Legislature’s staff working to
anticipate where additional bandwidth needs will develop.

The Respondent could install high capacity Access Circuits and offer a
reduction in monthly fees for unused capacity.
Burst Capacity and Bursty Traffic
The Legislature will size circuits appropriately to provide the most cost effective
transport based on the business needs of the service address. However, occasional
bursty traffic must be accommodated. Respondent should describe its strategy for
supplying and managing burst capacity on a circuit.
3.2.8
Traffic Engineering
3.2.8.1 Fault-Tolerance: [Mandatory – Respondent must confirm compliance] The
Legislature requires fault-tolerance in the core network and for the Legislature’s web
services such as might be provided by backup tunnels. Respondent must describe its
approach to fault-tolerance.
Fault-Tolerance must also include rerouting and load balancing the Legislature’s
public web services to a secondary Internet circuit should the primary Internet circuit
fail or become overwhelmed.
3.2.8.2 Traffic Rerouting: [Mandatory - Respondent must confirm compliance.]
The Legislature requires dynamic routing protocols for all district offices and the
capability to automatically reroute traffic in the event transport troubles are detected.
Describe the procedures to initiate automatic rerouting. Include any manual
procedures. Describe rerouting actions; explain which transport facility has priority
over others and who can in practice initiate manual rerouting of the Managed MPLS
VPN.
Discuss the Legislature’s role in this area including how the Legislature is notified
when rerouting occurs.
3.2.8.3 Emergency Traffic Rerouting Notification: The Legislature desires prompt
notification when rerouting occurs in the Managed MPLS VPN core network;
especially if the rerouting directs the Legislature’s traffic to an alternate POP.
Describe the proposed tools or procedures for this.
3.2.9
ITN #851
Multimedia
The Managed MPLS VPN solution must accommodate the connectivity, transmission
and convergence of voice, video, and data application traffic.
18
3.2.9.1 Signaling Protocols: [Mandatory – Respondent must confirm compliance]
The Legislature requires that the proposed solution support signaling protocols
including but not limited to the most currently approved versions of Session Initiation
Protocol (SIP), H.323, H.264, Media Gateway Control Protocol (MGCP), and
H.248/Megaco. SIP and H.323 use RTP to transport real-time transmission of
multimedia data over network services. Real Time Protocol (RTP), Real Time
Control Protocol (RTCP), and Real Time Streaming Protocol (RTSP) transport and
manage the real-time transmission of multimedia data over network services. List the
protocols Respondent intends to support. List and describe any non-standard
protocols or extensions.
3.2.9.2 Multicast: The Legislature highly desires the capability to use IP Multicast
as a technique to provide various network-based services. Describe Respondent’s
capability.
3.2.10 Voice
3.2.10.1 CODECs: [Mandatory – Respondent must confirm compliance] In order to
support the Legislature, the network solution is required to support standard
CODECs. Standard compression/decompression (CODEC) techniques, with their
respective mean opinion scores (MOS), include but are not limited to G.711 – 4.3
MOS, G.729 – 4.0 MOS, G.723 3.8 MOS and h.264. What CODECs does
Respondent’s solution support? Responses should include descriptions of any nonstandard protocols or extensions.
3.2.10.2 Voice over IP: [Mandatory - Respondent must confirm compliance] The
Legislature requires allowing telephony and other audio signals to be transported over
the same network as regular data traffic. Describe how the proposed solution
supports a VoIP solution. Include information regarding the support of both a
network based or premise based solution and the risks and benefits of each approach.
3.2.10.3 Least-cost Routing: [Mandatory - Respondent must confirm compliance]
The Legislature requires utilization of least cost routing. Describe the approach for
implementing this feature.
3.2.10.4 QoS and DiffServ Signaling: [Mandatory – Respondent must confirm
compliance] IP by itself is simply a best-effort service, not sufficient enough to
provide the strict delay, jitter, and bandwidth guarantees required for voice over IP
(VoIP) and other real-time traffic. The Legislature requires that the proposed solution
support a standards-based QoS or DiffServ aware TE signaling mechanism when
making forwarding decisions for passing VoIP traffic through tunnels. Respondent
must describe the method for QoS or DiffServ TE signaling for VoIP traffic.
3.2.10.5 VoIP Phone Failover to PSTN: [Mandatory - Respondent must confirm
compliance] In the event of a WAN circuit failure, the Customer Premise Equipment
is required to failover to the publically switched telephone network.
3.2.11 Access Circuits
3.2.11.1 Access Circuit Services: [Mandatory - Respondent must confirm
compliance] The local access connection between the customer premise equipment
ITN #851
19
and the Respondent’s Point of Presence (POP) is required to use generally and
commercially available transport services. Preference should be given to open,
secure, scalable, industry-standards-based, packetized services, such as SONET,
Frame Relay, ATM and others, providing end-to-end QoS capable of transporting
voice, video, and data applications within a converged media stream. TDM-based
transport services, such as T1 digital carrier, ISDN, DSL, etc., are acceptable with
sufficient SLA’s.
3.2.11.2 Access Circuits: [Mandatory - Respondent must confirm compliance] The
Legislature requires that the Respondent supply the most economical physical Access
Circuits that meet the service level and bandwidth requirements of the individual
service address. Describe the strategy for providing the most economical
accessibility while meeting Service Level Agreements (SLA).
3.2.11.3 Availability: [Mandatory - Respondent must confirm compliance] The
Legislature requires the ability to choose Access Circuit Availability per the business
requirements of each service address. Using the spreadsheet located in Appendix C,
list each Access Circuit type Respondent proposes with its accompanying bandwidth,
Availability, Latency, Jitter, MTTR, and Installation.
3.2.11.4 Bandwidth: [Mandatory - Respondent must confirm compliance] The
Respondent is required to specify the various types of access services offered
including the bandwidth increments and ranges. Clearly define the various types of
access services offered including the bandwidth increments and ranges.
ITN #851
20
3.2.12 Disaster Recovery
Loss of Data Center: In the event of a loss of either the OLITS-managed or House
OIT managed Data Center, Access Circuits are desired to be provisioned in a manner
that will allow the Legislature or the Respondent to swing circuits to an alternate, as
yet undefined, location (Service Address, Data Center). Describe Respondent’s
strategy for providing connectivity to the alternate site in such an emergency. This
includes provision for the rapid establishment or upgrade of Access Circuits to one or
more alternate locations, and rapid establishment of temporary network service.
3.2.13 Internet Access
3.2.13.1 Internet Access (Internal User Access): [Mandatory - Respondent must
confirm compliance] The Legislature requires secure Internet access for all sites
connected to its Managed MPLS VPN network including Tallahassee Capitol
Complex. Respondent must describe the strategy for providing access to the Internet.
OLITS will provide for and manage the gateway to the OLITS-managed Internet.
House OIT will provide for and manage the gateway to the internet for the House
OIT-managed Network.
3.2.13.2 Alternate Internet Access: [Mandatory - Respondent must confirm
compliance] In order to provide protection against failures and emergencies, and to
ensure business continuity, the Legislature requires Internet connections be fault
tolerant and available. Respondent should identify configuration options to increase
the resiliency of the Internet access services with preferably an alternate Internet
backbone from a separate Internet Service Provider.
3.2.13.3 IPS/IDS: The Legislature desires an option for separate Managed IPS/IDS
solutions for the House OIT managed Internet circuit. Respondent must describe the
strategy for performing all management and maintenance of the IPS/IDS including:
 Signature tuning
 Signature updates
 Configuration changes
 Security event monitoring
 Performance and availability management
3.2.14 Network Security
The physical security of network components (such as buildings, power services,
continuity of operations, etc.) and the security of the information that will traverse the
network is a prime concern and must be defined as part of this Response.
3.2.14.1 Security Threats: [Mandatory - Respondent must confirm compliance] The
Respondent is required to work with the Legislature to address security threats. This
includes threat mitigation and event correlation and access to tools and reports to aid
the Legislature in monitoring and tracing security threats. This also includes
providing support for forensic investigation and incident response procedures in the
event of malicious network activity. Describe how this will be addressed.
3.2.14.2 Security Threats CPE: [Mandatory - Respondent must confirm compliance]
ITN #851
21
The Respondent is required to work with the Legislature to address security threats at
the CPE port level. This includes authentication, authorization and accounting of end
devices/users. Describe how this will be addressed.
3.3
Managed MPLS VPN Management and Monitoring
3.3. 1
Evolving and Emerging Technologies
3.3.1.1 Evolving and Emerging Technologies: The Legislature requests that the
Respondent have a method for incorporating evolving and emerging technologies. A
Technology Plan is one method of achieving this goal. Describe how evolving and
emerging technologies are addressed and the approach taken to incorporate changes
into the overall Managed MPLS VPN architecture.
3.3.2
Ongoing Technology Refresh [Mandatory - Respondent must confirm compliance]
The Legislature requires a partnership that is committed to meeting newly defined
service needs and technological advances within advantageous timeframes and within
a framework of cost effectiveness. The Legislature requires that the CPE and all
components that make up the WAN service be replaced within 3 months of the
manufacturer’s end of support date. The Legislature intends that the installed CPE be
neither state of the art nor fully mature or outdated.
3.3.2.1 Technology Refresh: [Mandatory - Respondent must confirm compliance]
Describe how technology refresh will be addressed in support of the Managed MPLS
VPN for data, VoIP, multimedia services and CPE managed by Respondent. Include
hardware upgrades or replacement, modifications to CPE IOS, modifications to
routers and switches that support the Managed MPLS VPN.
3.3.2.2 Security Technology Refresh: [Mandatory - Respondent must confirm
compliance] The Legislature requires that the Respondent manage and operate within
manufacturers’ security requirements across the entire Managed MPLS VPN for the
life of the contract. Describe management of the Managed MPLS VPN from a
security refresh standpoint.
3.3.2.3 Competitive Market Refresh: [Mandatory – Respondent must confirm
compliance] The Legislature requires that the cost, rates and terms offered to the
Legislature during the contract term remains competitive with the cost, rates and
terms offered in the market. Describe how Respondent will keep cost, rates and terms
competitive.
3.3.3
ITN #851
Operational Planning
Operational Planning: The Respondent should facilitate a forum that includes the
Legislature when planning for routine maintenance outages, CPE upgrades, changes
to Managed MPLS VPN Access Circuits, required technology refreshes and intrusive
troubleshooting and testing. Describe procedures used for each and how the
Legislature will be incorporated into the planning process. Address the planning
process for proactive and preventive maintenance programs.
22
3.3.4
Monthly Service and SLA Reviews
Monthly Service and SLA Reviews: The Legislature desires the Respondent to
participate in monthly (and to be agreed upon later bi-monthly) service and SLA
reviews with the Legislature. Describe the process and methodology to include future
changes that will impact the proposed Managed MPLS VPN network.
3.3.5
Respondent’s Help Desk and Operational Support
The Legislature is seeking technical assistance that is available around-the-clock to
support the Managed MPLS VPN. This includes support for assisting the Legislature
in resolving MPLS VPN network services issues.
The Legislature will operate level zero and one Help Desks and will require
Respondent to operate the next level Help Desks which will support the Legislature.
The Legislature will act as the liaison and will own the problem on behalf of
legislative users.
3.3.5.1 Respondents’ Help Desk: Describe the scope of help desk coverage offered
to the Legislature’s personnel and hours of operation for support of the Managed
MPLS VPN. Include the type of assistance that would be extended to the Legislature
for end-to-end network support, including connectivity and performance. Describe
personnel qualifications and expertise that are offered in support of the technologies
mentioned above, to include the various levels of Help Desk support for the
Legislature such as Tier 1, Tier 2, Tier 3, and describe the services offered for each
level of service.
3.3.5.2 Help Desk Integration: The Legislature desires Help Desk staff
knowledgeable and familiar with our network and that functions logically within the
overall Legislative Support Services team. A single call into the support service
structure must cover questions concerning performance as well as typical end-to-end
problem resolution. Requests for assistance could occur at any time day or night (24
hours a day, 7 days a week). Describe the approach for supporting this requirement.
3.3.5.3 Legislative Session Support: During legislative session, the importance of
service availability is heightened and it is critical that resolutions to problems be
handled with extreme expedience. What can the Respondent offer as a strategy for
ensuring an appropriate support structure is in place to handle these unique periods?
ITN #851
23
3.3.6
Maintenance for Respondent-Managed CPE [Mandatory – Respondent must
confirm compliance]
Maintenance for Respondent-Managed CPE: The Respondent is required to have
maintenance policies and procedures regarding CPE that will be used in the delivery
of the Managed MPLS VPN service. Describe the preventive maintenance routines,
equipment swap-outs, the remove-repair-return procedures, and how activities are
coordinated in advance with the Legislature. Identify available service levels and
terms of coverage.
3.3.7
Configuration Management [Mandatory – Respondent must confirm compliance]
3.3.7.1 Configuration Management: [Mandatory - Respondent must confirm
compliance] The Respondent is required to describe any system or application
proposed for Configuration Management of Respondent-Managed CPE
configurations. Describe how the systems and applications operate. Describe
procedures and methodology associated with configuration management.
3.3.7.2 Configuration Records: [Mandatory - Respondent must confirm
compliance]The Legislature requires that current and accurate configuration records
be kept for Managed MPLS VPN access and CPE managed by the Respondent at all
locations found in Appendix A. Respondent must describe its approach to
maintaining these records and how access will be provided to these configuration
records by the Legislature.
3.3.7.3 Archiving Configuration Information: [Mandatory - Respondent must
confirm compliance] The Legislature requires that all CPE configurations be
archived on a regular basis. Describe the process and frequency proposed. Describe
the policies affecting the retention periods and the depth of versions kept to include
restoration testing. Clearly distinguish between transport and CPE configurations.
3.3.7.4 Security Configuration Management: [Mandatory - Respondent must
confirm compliance] The Respondent is required to describe its methodology and
procedures to ensure the Managed MPLS VPN is kept current with security patches
or upgrades.
3.3.7.5 Rapid Modifications to Configurations: [Mandatory - Respondent must
confirm compliance] The Respondent is required to describe the process and
methodology for rapid modifications of configurations (rapid being within 5 minutes
of notification). Address the time intervals required for change to occur for each type
of configuration affected.
3.3.8 Monitoring
Monitoring: the Legislature desires around-the-clock monitoring of services for the
Managed MPLS VPN. This includes operating a Network Operations Center (NOC),
utilizing state-of-the-art monitoring tools, performing real-time analysis and
diagnostics of accumulated traffic information and extending to the Legislature realtime access to these tools so that the Legislature is able to manage data, voice and
multimedia Managed MPLS VPN services. Monitoring should be set up to allow
House OIT staff the ability to monitor House services and to allow OLITS staff the
ability to monitor Senate and Joint services.
ITN #851
24
3.3.8.1 Respondent’s NOC: The Respondent should provide and operate a network
operations center (NOC) that performs network monitoring for the Managed MPLS
VPN twenty-four hours a day, seven days per week. Describe the NOC that will be
used and the type of activity the Legislature can expect from this NOC. Further
identify which NOC will serve the Legislature and the Managed MPLS VPN.
Describe how the Legislature’s technical staff will communicate with Respondent’s
technical staff in the NOC, including telephone, e-mail, and other online contact.
Identify which secondary NOC, if any, will be used as a backup.
3.3.8.2 Alarm and Alert Monitoring System or Application: [Mandatory Respondent must confirm compliance] The Legislature requires that an alarm and
alert system that receives, processes and displays alarms and alerts received from
Access Circuits and hardware be used in the delivery of the Managed MPLS VPN.
Respondent must describe in detail the system that will be utilized and how it will
support the Legislature.
 Clearly identify the capabilities of the system for generating alarms and
alerts.
 Provide examples of output from such system or application screen-shots.
 Describe policies and procedures that are followed to notify OLITS once
major or catastrophic alarms/alerts are received.
 Describe the backup system if one exists.
1)
Viewing Alarms and Alerts: Describe what types of alarms and alerts
are available for viewing and how and when they are generated.
2)
Time Intervals: Identify time intervals Respondent has established
that determine when an outage has occurred.
3)
Reaction to Alarms: Describe what immediate steps are taken once an
alarm is received.
4)
Recurring Events: Describe what procedures are in place to mitigate
recurring events.
5)
Scope of Monitoring: Clearly identify, with examples, at what point
in the transport architecture monitoring ends.
3.3.8.3 Performance and Error Monitoring of Managed MPLS VPN Access Circuits
and CPE: The Legislature desires that the Respondent operate a real-time, modern
performance and error monitoring system that will be used in the delivery of the
Managed MPLS VPN.
 Describe in detail, the system provided and how it will be used to
support the Legislature and the Managed MPLS VPN.
 Provide examples of output from such system or application screenshots.
 Describe policies and procedures that are followed to notify the
Legislature once major or catastrophic performance issues are
encountered.
ITN #851
25
1) Degradation of service: Identify specific types of performance
information that is being evaluated and how degradation of service is
determined.
2) Reaction to Performance Issues: Identify the immediate steps that are
taken once there is degradation of service or errors encountered and
the procedures that are in place to address these events.
3) Time Intervals: Define how long a problem must exist before it is
reported.
4) Problem Continuum: Identify what types of performance issues and
errors are reported immediately and those that are monitored for a
period of time.
5) Scope of Monitoring: Identify, with examples, at what point in the
transport architecture monitoring ends.
3.3.8.4 Bandwidth Utilization and Exception Monitoring: the Legislature desires that
the Respondent operates a real-time, modern bandwidth utilization and exception
monitoring system that monitors bandwidth utilization and creates exception reports
to be used in the management of the Managed MPLS VPN. Describe the system in
detail and how it will be used. Describe how the Legislature will be notified when
exceptions have been encountered that impact service delivery.
1)
Traffic Usage by Technology-Type: Address specific performance
monitoring criteria as it pertains to data, VoIP, and video bandwidth
usage. Address each performance aspect individually, showing what
is measured and how it is measured.
2)
Polling Intervals: Identify polling intervals used for each technologytype.
3)
Threshold Levels: Provide threshold levels observed for each
technology-type including the latency time window adopted that
generates an exception.
4)
Time Interval: Define how long a problem must exist before it is
reported.
5)
Problem Continuum: Identify the types of exceptions that are reported
immediately and those that are monitored for a period of time.
3.3.8.5 Access to Alarm and Alert System or Application: [Mandatory –
Respondent must confirm compliance] It is required that Internet-connected
legislative information technology staff be able to access the alarm and alert system
or application with a web browser. Identify any other needed hardware or software
for access to the alarm and alert system or application. The alarm and alert system or
application should provide a graphical interface to the web browser. This system or
application must support at least ten (10) concurrent authorized legislative
information technology staff.
ITN #851
26
3.3.8.6 Identification Options within Alarm and Alert System: [Mandatory –
Respondent must confirm compliance] The Legislature requires to have the
flexibility to view alarm and alert information by identifiers recognizable by the
Legislature. Examples are Location Name; Circuit ID, and CPE name. Describe how
the system offers this flexibility.
3.3.8.7 Alarm and Alert System or Application Training: [Mandatory – Respondent
must confirm compliance] Training should be provided as to access and use of the
alarm or alert system or application. Training must be provided for at least ten (10)
legislative information technology staff. Describe the training.
3.3.8.8 Access to Performance and Error Monitoring of Managed MPLS VPN
Access Circuits and CPE: The Legislature desires that their network engineers be
able to access and view performance of the error monitoring system or application
with a web browser. Identify any other needed hardware or software for access to
performance and error monitoring system or application. The performance and error
monitoring system or application should provide a graphical interface to the web
browser. This system or application should support at least ten (10) concurrent
authorized legislative information technology staff.
3.3.8.9 Identification Options within Performance and Error Monitoring System:
The Legislature desires the flexibility to view performance and error monitoring
information by identifiers recognizable by the Legislature. Examples are Location
Name; Circuit ID and CPE name. Describe how the system offers this flexibility.
3.3.8.10 Monitoring Data Filtered: Is information contained in alarm and alert data or
performance and error monitoring filtered before it will be disseminated to the
Legislature? If yes, describe what is being filtered before it reaches the Legislature.
3.3.8.11 Extracting Information from CPE Owned and Managed by Respondent:
The Legislature desires direct secure access to CPE hardware used in the delivery of
the Managed MPLS VPN service. The Legislature would poll CPE and re-process
that information on the Legislature’s own network management system, ZenOss.
Describe the Legislature’s level of access, types of output, the frequency of polling
allowed and the method allowed to poll data (SNMP, SNMPv2, SAA, etc.).
3.3.9 Reporting
3.3.9.1 Reporting: The Legislature desires web-browser access to online reporting as
it pertains to performance of Managed MPLS VPN services. Examples of needed
reports include alarms and alerts, threshold exceptions, user access, trend analysis,
chronic Access Circuits or CPE, threat analysis, verification of traffic processing, etc.
Describe the reports available and differentiate between reports that are scheduled
and those that are available on demand. Provide example screenshots of the various
reports and describe the Legislature’s options with respect to viewing (GUI, text,
diagrams, etc).
3.3.9.2 Report on Verification of Managed MPLS VPN Traffic Processing: The
Respondent should provide the Legislature with verification that Managed MPLS
VPN traffic is being processed at QoS and CoS levels prescribed by the Legislature.
Provide screenshots of this report.
ITN #851
27
3.3.9.3 Proactive Monitoring on Managed MPLS VPN transport: Describe how the
result of the event correlation analysis of the Managed MPLS VPN transport is
utilized to prevent future service affecting events.
3.3.9.4 Proactive Monitoring on CPE Managed by the Respondent: Describe how
the result of the event correlation analysis of the Respondent managed CPE transport
is utilized to prevent future service affecting events.
3.3.9.5 Proactive Analysis: Describe how the Trouble Ticketing System is used in
support of the Managed MPLS VPN. Describe if both transport and CPE Trouble
Tickets are used in analysis.
3.3.9.6 Degradation of Service: Describe how degradation tracking of Managed
MPLS VPN Access Circuits is accomplished and examples of the types of Access
Circuits tracked. Provide thresholds that trigger opening of a trouble ticket and
provide remediation. Describe any variations of tracking as it pertains to data, VoIP
and video.
3.3.10 Trouble Ticketing
The Legislature desires that the Respondent operate a Trouble Ticketing Function that
includes an online system. The Trouble Ticketing Function must include processes
and procedures that can be used by the Legislature to open, update, close and track
Trouble Tickets for the Managed MPLS VPN and related services covered in this
ITN. Trouble ticketing should be set up to allow House OIT the ability to access
House tickets and to allow OLITS the ability to access Senate and Joint tickets.
3.3.10.1 Trouble Ticketing System [Mandatory - Respondent must confirm
compliance]: The Legislature requires that all trouble ticket activity initiated by the
Legislature is done through an online Trouble Ticketing System provided by the
Respondent. The system must be available for use by the Legislature twenty-four
hours per day, seven days per week excluding maintenance time. Respondent must
provide applicable policies and procedures used to support this system.
1) Trouble Ticket Activity Types: Identify the types of items and
activities that flow through the Trouble Ticketing System and
how open ticket confirmations are communicated back to the
Legislature.
2) Notification Back to the Legislature: Describe how the
Legislature is kept current on the progress of trouble tickets
that were opened by the Respondent and by the Legislature.
3) Affect on SLAs: Define the time relationship between opening
of a trouble ticket and the effects on supported SLAs.
4) Severity Levels: Describe how Trouble Tickets are treated
differently based upon their Severity and Priority Levels.
(Severity refers to the technical impact of a problem. Priority
refers to the degree of business necessity for resolving the
problem.)
ITN #851
28
5) Chronic Problems: Provide policies and procedures of how a
problem becomes chronic and the resolution. Clearly identify
time intervals between chronic events before a trouble ticket is
opened.
3.3.10.2 Advanced Outage Notification [Mandatory - Respondent must confirm
compliance]: The Legislature requires to be notified prior to a planned outage
affecting the Legislature’s Managed MPLS VPN network, Access Circuits, CPE, or
other associated IP-based services including Internet. The Legislature requires at least
twenty-four (24) hours prior notice for short-term, routine outages. Provide a policy
that complies with this requirement. List maintenance window types, time frames
allotted, and identify which windows are excluded from any calculations of
Availability.
3.3.10.3 Emergency Maintenance Windows: Provide the procedure as to when and
how Respondent will notify the Legislature when emergency maintenance is required.
3.3.10.4 Access to Trouble Ticketing System: It is desired that Internet-connected
Legislative support users be able to access the Trouble Ticketing System with a web
browser. Identify any other needed hardware or software for access to the Trouble
Ticketing System. The Trouble Ticketing System should provide a graphical
interface to the web browser. The Trouble Ticketing System must support at least ten
(10) concurrent authorized legislative information technology staff.
3.3.10.5 Trouble Ticketing System Training: [Mandatory - Respondent must
confirm compliance] Training must be provided for access and use of the Trouble
Ticketing System. Training must be provided for at least ten (10) legislative
information technology staff. Describe the training that will be offered.
3.3.10.6 Trouble Ticketing Tracking: Describe how the Legislature would track
Trouble Ticket status with as close to real-time reporting as possible. Clearly identify
what can be tracked, by what identifier, and how that information is communicated
back to the Legislature.
3.3.10.7 Service Restoration: Describe procedures with respect to service restoration
both for Managed MPLS VPN Access Circuits and hardware, including CPE.
Address levels of Severity and Priority if applicable.
3.3.10.8 Troubleshooting and Testing: Describe the troubleshooting and testing
procedures in place to support the integrity of the Managed MPLS VPN, including
Managed MPLS VPN access and managed CPE operating in a production
environment. When is troubleshooting initiated? Include what time of day
troubleshooting is conducted for non-emergencies.
3.3.10.9 Intrusive Testing [Mandatory - Respondent must confirm compliance.]:
The Legislature requires that the Respondent notify the Legislature prior to any
intrusive troubleshooting or testing on Access Circuits and CPE used to support the
Managed MPLS VPN when a trouble ticket does not exist for same or if the
circumstance does not require immediate intervention. Provide policy and guidelines
for intrusive testing.
ITN #851
29
3.3.10.10 Trouble Ticketing System Reports [Mandatory - Respondent must
confirm compliance]: The Trouble Ticketing System is required to be able to produce
both scheduled and ad hoc reports and provide web browser access for the
Legislature. Provide screenshots of standard reports. Describe creation of ad hoc
reports with the Trouble Ticketing System.
3.3.10.11 Customized Reports: The Legislature desires to create customized reports
either on-demand or a scheduled basis. Describe the capabilities of the Trouble
Ticketing System in this area. Below are examples of reports that the Legislature
would be interested in generating (reports to include, but not limited to):
 Number of troubles reported within time frames: Time of day, day of
week, month of year.
 Number of repeat troubles reported within a thirty-day period.
 Trouble Tickets by Service Location
 Mean-time-to-repair statistics for all Priority Levels.
 By type of trouble reported as defined by Respondents’ classifications.
 By Priority Levels.
 Troubles reported by site ID, circuit ID, originator’s name or ID.
 Number of troubles that were escalated by level of escalation.
 Number of trouble tickets opened by Priority Levels.
 Number of trouble tickets closed by Priority Levels.
 Number of trouble tickets unresolved by Priority Levels.
 Access into trouble ticketing system by user.
 Bandwidth utilization (in, out, and total)
 Latency
 Jitter
 Packet Delivery
3.3.10.12 Escalation [Mandatory - Respondent must confirm compliance]: The
Respondent is required to list and describe trouble Severity and Priority Levels and
how they apply to the WAN service. (Severity refers to the technical impact of a
problem. Priority refers to the degree of business necessity for resolving the problem.)
Provide examples for each.
Describe Respondent’s escalation policies and procedures for WAN service troubles
and what drives troubles to be escalated to the next level. Identify professional skill
levels that are required to perform each level of escalation. Describe communication
methods that will be used by the Legislature to track initial escalations and
escalations between Severity and Priority Levels.
3.4
Managed MPLS VPN Service Level Agreement (SLA)
3.4.1
SLA Purpose and Objective
This section provides requirements for the Service Level Agreement (SLA) to be
established between the Legislature and the Respondent. The paragraphs following
describe the SLA that the Respondent must submit with the Respondent’s Response.
3.4.1.1 SLA: [Mandatory - Respondent must confirm compliance.] The
Respondent is required to submit a SLA with the Respondent’s Response. The SLA
ITN #851
30
to be submitted with the Respondent’s Response is to contain the specific service
standards, provisions, and remedies proposed by the Respondent in response to this
ITN.
3.4.2 Scope
Scope Statement: The SLA should include a statement of scope that indicates that the
SLA covers all services to be delivered, including services for planning, provisioning,
testing, operating, managing, and improving the legislative Managed MPLS VPN and
related network services that are the subject of this ITN. SLAs are tracked by the
sum of occurrences within the monthly billing cycle.
3.4.3 Related Documents
Related Documents: The Respondent should list related documents that will support
the SLA, including documentation standards and separate procedures for problem
resolution, escalation, network management, service payment calculations and
payments, and change management. Procedures for emergency provisioning or
support of disaster recovery must be listed. The Respondent should provide
document numbers, version numbers, and publication dates where available, and
describe how these standards and procedures are made available to the Respondent’s
management, operational, and engineering staff.
3.4.4 Key Contact Personnel
Key Contacts: The Respondent should identify and maintain an accurate list, in the
SLA, of the Respondent’s key and backup points of contact. These are individuals
who will directly support the SLA. This should include name, title, business address,
phone, and e-mail contact information. The Respondent should provide space in the
SLA for contact information for the Legislature’s key points of contact.
The successful Respondent shall replace the liaison or any assigned key contacts at
the request of the Legislature.
3.4.5 WAN Services
The Service Standards, provisions, and Remedies listed in this section refer to the
Respondent’s proposed WAN services.
Guarantees and Exclusions:
3.4.5.1 Guarantees: The Respondent should offer, in the SLA, Service Standard
guarantees for the WAN services. The guarantees should include Availability,
Latency, Jitter, Packet Delivery, and Outage Notification.
3.4.5.2 Exclusions: With respect to calculating Availability, any exclusions for
scheduled maintenance, time lost waiting for premises access, or other reasons should
be clearly detailed in the Respondent’s Response.
WAN Service Standards Table
Respondents must respond to each Mandatory SLA measure and should document its
remedy.
ITN #851
31
SLA Measure
3.4.5.3
Availability (PEPE)
3.4.5.4
Latency
3.4.5.5
Jitter
3.4.5.6
Packet Loss
SLA Measure
3.4.5.7
Access Circuit
and/or CPE
Availability
3.4.5.8
Latency
3.4.5.9
Jitter
3.4.5.10 Packet Loss
SLA Measure
3.4.5.11 Install, Moves,
Adds, Changes
3.4.5.12 Service outage
alerting
SLA Measure
3.4.5.13 Internet Circuit
Availability
ITN #851
Service Level Agreement
Core
Mandatory Service
Standard
It is required the Respondent
offer a service standard
guarantee for availability of
the core network.
≤ 55 ms round trip → PE-PE
Router
≤ 20 ms round trip → PE-PE
Router
≤ 1% → PE-PE Router
Access Circuit & CPE
Mandatory Service
Standard
It is required that the
Respondent offer a service
standard guarantee for access
circuit and CPE availability.
≤ 55 ms round trip for ≥ T1
speeds
≤ 20 ms round trip for both
CPE-CPE router
≤ 1% for both CPE-CPE
router
Operational
Mandatory Service
Standard
512kbps to 6Mbps = 30
business days
45Mbps = 40 business days
<15 minutes
Internet Service
Mandatory Service
Standard
It is required that the
Respondent offer a service
Preferred Remedy
1 day’s charges
prorated for each
affected site
for each hour of
outage.
10% of WAN port
MRC for 10% outside
service standard
30% of WAN port
MRC for 30% outside
service standard
50% of WAN port
MRC for 50% outside
service standard
Preferred Remedy
1 day’s charges
prorated for affected
site
for each hour of
outage.
10% of WAN port
MRC for 10% outside
service standard
30% of WAN port
MRC for 30% outside
service standard
50% of WAN port
MRC for 50% outside
service standard
Preferred Remedy
10% of install fee if
service standard is not
met.
5% CPE MRC
Preferred Remedy
1 day’s charges
prorated for affected
32
3.4.5.14 Latency
3.4.5.15 Jitter
3.4.5.16 Packet Loss
standard guarantee for
Internet access circuit.
≤ 55 ms round trip for ≥ DS3
speeds
≤ 20 ms round trip for both
CPE-PE router
≤ 1% for both CPE-PE router
site for each hour of
outage.
10% of WAN port
MRC for 10% outside
service standard
30% of WAN port
MRC for 30% outside
service standard
50% of WAN port
MRC for 50% outside
service standard
Additional Guarantees and Provisions:
3.4.5.17 Additional Guarantees: It is desired that the Respondent offer
additional Service Standard guarantees, provisions, and remedies with respect
to the Respondent’s WAN services. These might include such measures as
Mean Time to Repair (MTTR) or Maximum Service Affecting Outage
Duration.
3.4.5.18 Chronic Outages and Missed Service Standards: The Respondent
should offer provisions and remedies for chronic outages and chronic missed
Service Standards.
Additional Guarantees and Provisions:
3.4.5.19 Additional Guarantees: It is desired that the Respondent offer
additional Service Standard guarantees and provisions with respect to Access
Circuits.
3.4.5.20 Chronic Outages and Missed Service Standards: The Respondent
should offer provisions and remedies for chronic outages and chronic missed
Service Standards.
3.4.6 Disaster Recovery Loss of Service Address Standard
It is desired that the Respondent support a primary plan for Loss of Service Address
that would cover a variety of needs. These include temporary use of an alternate site
and reconstruction of Access Circuits and CPE for the lost Service Address, as
needed. This would also include provisions for rapid establishment or upgrade of
Access Circuits to an alternate site, rapid establishment of temporary Private Virtual
Circuits (PVC’s) to the alternate site, and rapid label propagation in support of the
new PVC’s, for all Classes of Service. This would also include provisions for upgrade
of CPE as needed.
ITN #851
33
3.4.7 Security
Security Service Standards: It is desirable that the Respondent offer Service
Standards, provisions, and remedies applicable to Security Services. Examples
include response to Denial of Service attacks, blocking known malicious IP addresses
and URLs, providing authentication, authorization and accounting for network
infrastructure components and secure management of said infrastructure (SSH).
3.4.8 VoIP
It is desired that the Respondent offer Service Standards, provisions, and remedies
applicable to VoIP. At a minimum, the Respondent must offer a Service Standard
guarantee and remedy with respect to the service guarantee.
3.4.9 Billing
Billing Service Standards: It is desired that the Respondent offer Service Standards,
provisions, and remedies applicable to billing.
3.4.10 SLA Management
Reporting:
3.4.10.1 It is desired that the Respondent offer Service Standards, provisions, and
remedies applicable to Reporting for Support of SLA Management.
Service Review:
3.4.10.2 It is desired that the Respondent offer Service Standards, provisions, and
remedies applicable to participation in Service Review.
SLA Review:
3.4.10.3 It is desired that the Respondent offer Service Standards, provisions, and
remedies applicable to participation in SLA Review.
3.5
Billing
3.5.1
Fixed Cost and Renegotiation
3.5.1.1 Fixed Cost: The Legislature desires that all cost be fixed during the initial
contract and renewal terms unless there is a reduction in cost.
3.5.1.2 Renegotiation: The Legislature desires a renegotiation process to begin at
least sixty (60) days prior to the end of the initial term and renewal terms of the
Contract. Describe Respondent’s approach for addressing renegotiation and define
driving factors for reduction in cost.
3.5.2 Competitive Rates
3.5.2.1 Rates: [Mandatory – Respondent must confirm compliance] The
Legislature requires that the cost, rates and terms offered to the Legislature during the
renewal terms of the Contract is at least as favorable as the cost, rates and terms
ITN #851
34
offered to Respondent’s similarly situated users. Describe Respondent’s approach for
keeping the Legislature’s cost, rates and terms at least as favorable as those offered to
Respondent’s other users.
3.5.2.2 Competitive Market: [Mandatory – Respondent must confirm compliance]
The Legislature requires that the cost, rates and terms offered to the Legislature
during the renewal terms of the Contract remains competitive with the cost, rates and
terms offered in the market. Describe how Respondent will keep cost, rates and terms
competitive.
3.5.3 Invoice Presentation
3.5.3.1 Categorization: Propose a billing hierarchy that presents invoice details
categorized by the following:
 Site (Service Address)
 Circuit type
 Circuit ID
3.5.3.2 Circuit ID: The Legislature desires all invoice components (e.g. FCC
charges, one time charges, credits, recurring charges, cancellations, escalations, etc.)
be linked to a Circuit ID.
3.5.3.3 Sample of Categorization: Provide a sample invoice of no more than ten
(10) pages demonstrating understanding of the requirements previously listed.
3.5.3.4 Electronic File Format: [Mandatory - Respondent must confirm
compliance] The Legislature requires the electronic submission of a single monthly
invoice that is able to be downloaded to an office application (such as: XML, RTF,
HTML, XLS) and be searchable by every data field and service code. Confirm
Respondent’s compliance with this mandatory requirement and describe the proposed
methodology.
3.5.3.5 Itemization: The Legislature desires that invoices be presented in an
itemized format with all abbreviations described. Respondent should supply a current
glossary (and describe process for maintaining the glossary) of all abbreviations for
any and all invoice components.
3.5.3.6 Penalties: The Legislature will not be held liable for penalties of any kind,
including cancellation charges, and early termination charges. Confirm Respondent’s
acknowledgement and agreement.
3.5.3.7 Records: The Legislature desires that the Respondent will, and will require
each of its subcontractors, to maintain accurate books, records, documents and other
evidence concerning its financial status, costs, expenses, formulas for computing
prices, and provision of services (collectively, “Records”) for five (5) years after the
final payment made by the Legislature. Confirm that Respondent’s accounting
procedures and practices conform to generally accepted accounting principles
(“GAAP”) and that the costs applicable to the Legislature will be readily
ascertainable from Respondent’s Records.
ITN #851
35
3.5.4 Billing Cycle
3.5.4.1 Bill Cycle: Describe the bill date cutoff process.
3.5.4.2 New Service Billing: The Legislature’s obligation to pay shall begin only
after the Legislature accepts the service.
3.5.5 Billing for Moves, Adds, Changes and Deletions (MACD)
3.5.5.1 MACD Charges: The Legislature desires that all charges associated with
any work order activity will appear on the invoice to the legislature within a
maximum of two (2) billing cycles from acceptance date. The Legislature will not
accept any MACDs that were not authorized by the Legislature. Describe
Respondent’s process.
3.5.6 Credits
3.5.6.1 Credits for Billing Errors: The Legislature desires that credits for items billed
in error or for other reasons must be refunded in the form of a credit against the
monthly invoice. Describe Respondent’s approach.
3.5.6.2 Credits: The Legislature desires all credits must be resolved within a
maximum of three (3) billing cycles. Describe Respondent’s approach.
3.5.7 Single Point of Contact
3.5.7.1 Communications: The Legislature desires that Respondent provide the
Legislature a single point of contact for all billing issues/inquiries including a toll free
number and email address. All communications should go through the Respondent’s
single point of contact. Describe the process for this requirement.
3.5.8
Dispute Resolution Process
3.5.8.1 Dispute Resolution Process: Define the billing dispute resolution process and
benchmark timelines to resolve. Include the Legislature’s responsibilities.
3.5.8.2 Dispute Resolution: The Legislature desires that all disputes must be
resolved within a maximum of three (3) billing cycles. Describe the approach.
3.5.9 Billing Escalation
3.5.9.1 Billing Escalation: The Legislature desires that the Respondent establish and
document a billing escalation process to resolve any billing issue including
discrepancies, errors, omissions, or unrecognized charges. Describe Respondent’s
billing escalation process.
3.5.9.2 Tracking of all Billing Issues: Describe the process for tracking the status of
all billing issues, inquiries, credits, refunds, and disputes.
ITN #851
36
3.6
Service Order Provisioning to include Moves, Adds, Changes, Disconnects
(MACD)
3.6.1
Service Ordering
3.6.1.1 Service Ordering: The Legislature desires that the Respondent operate a
Service Order Function that includes an online (web browser) system. The Service
Order Function should include processes and procedures that can be used by the
Legislature to initiate requests for new service on the WAN services and related
services covered in this ITN. Provide the processes and procedures for Service
Ordering.
3.6.1.2 Service Order System: The Legislature desires that all orders for new service
in the delivery of the WAN services should be requested through an online Service
Order System (web browser) provided by the Respondent. Describe how orders for
new service are treated differently based upon their Priority Levels. Examples of
Service Orders would include, but not be limited to, Access Circuits, CPE installation
and configuration, QoS/CoS establishment, bandwidth establishment. Identify all
turn-around times tied to each type of new service request. Provide policies and
procedures utilized including alternate access methods if web is unavailable. Identify
the types of items and activities that flow through the order management system and
how confirmations are communicated back to the Legislature.
3.6.1.3 Service Order System Integration: Describe how the Respondent’s Service
Order System is integrated with Moves, Adds, Changes, and Deletions, Provisioning,
Problem Management, and Billing Systems.
3.6.1.4 Access to Order System: The Legislature desires that authorized users be
able to access the Service Order System with a web browser. Identify any other
needed hardware or software for access to the Service Order System. The Service
Order System should provide a graphical interface to the web browser. The Service
Order System should support at least ten (10) concurrent authorized legislative
information technology staff.
3.6.1.5 Service Order System Training: Training should be provided as to access and
use of the Service Order System. Training should be provided for at least ten (10)
legislative information technology staff. Describe the training that will be offered.
3.6.1.6 Service Order System Reports: The Service Order System should be able to
produce both scheduled and ad hoc reports and provide online (web browser) viewing
by the Legislature. Describe the standard reports available. The Legislature should
be able to develop and view customized reports using the Service Order System.
Examples of Service Order reports may include but not limited to Service Order
activity by site, specific time periods, order status or by type of activity or circuit.
Describe how the Service Order System can satisfy this requirement.
3.6.1.7 Provisioning of Additional WAN services: Describe processes and
procedures for engineering (preparation) of Managed MPLS VPN services, Access
Circuits, and other related services described in this ITN for the delivery of services.
Describe initial engineering, installation, configuration, testing, cutover, acceptance
testing and billing establishment. Identify when the billing cycle begins. Detail
ITN #851
37
coordination of activities with the Legislature, including, but not limited to, site
preparation (site survey) and establishment of access arrangements with other
providers.
3.6.1.8 Inventory: [Mandatory - Respondent must confirm compliance]
Respondent is required to maintain a current and accurate inventory that would
incorporate all the items to include, but not limited to: Circuit ID, IP, CPE IOS, CPE
configuration archive, service address, on-site contact information and access circuits.
The Respondent must provide inventory information to the Legislature on a regular
basis and on request. The Respondent must maintain a current copy of inventory to
include service items once the deployment of Managed MPLS VPN services begin.
Inventory information must be available for secure viewing via web browser as well
as in spreadsheet format. Provide the policies and procedures around this
requirement.
3.7
Implementation and Acceptance
The requirements specified in Section 3.7 apply specifically to the installation and
implementation of the Respondent’s services for the Legislature.
3.7.1 Design Plan
3.7.1.1 Design Plan: [Mandatory - Respondent must confirm compliance]
Respondent is required to provide a recommended design to include Access Circuits
and CPE for each of the Service Addresses listed in Appendix A. Use the
spreadsheets in Appendix B to propose the four requested bandwidth configurations .
3.7.2 Project Plan
3.7.2.1 Project Plan: [Mandatory - Respondent must confirm compliance] The
Respondent is required to submit a representative but detailed project management
plan that includes items such as: methodology, processes, procedures, WBS and
schedule, demonstrating understanding of the scope and issues involved. The
project plan is especially critical to the success of this effort. The Legislature
realizes that the sequence of cutovers, (See Section 3.1.1) (includes two OLITS lab
and two House lab) will have to be created in collaboration with the Respondent.
3.7.3 Respondent Qualifications
3.7.3.1 Prior Project Experience: Identify at least one example of a prior project in
which Respondent performed transition and installation of Managed MPLS VPN
services. The experience requirement can be satisfied with the use of a sub-contractor
that will participate in this project. Attach a project plan (not including any
proprietary customer information) that was used for this installation. State
Respondent’s level of involvement in the prior project (i.e., whether it was as a prime
or subcontractor).
3.7.3.2 Customer References: [Mandatory - Respondent must confirm compliance]
The Respondent is required to provide three references of users of like size (more
than 40 sites). The references do not need to be utilizing MPLS VPN technology, but
they do need to be utilizing a routed network. Using Appendix D, references must
describe in detail the type and duration of services, dates of service, and effectiveness
ITN #851
38
of the services provided. Each reference will be evaluated for content and relevance.
Respondent’s reference information shall not exceed five pages in total for each
reference. If the Respondent is partnering with a subcontractor, two separate
references should be provided for the subcontractor in the same form as defined in
Appendix D – References. The Legislature reserves the right to contact references as
well as develop its own references. See 5.5 References.
3.7.3.3 Organizational Chart: Provide an organizational chart for the personnel who
will be providing deliverables and/or performing the services requested during the
transition. Changes of Key Personnel during the transition are subject to the
Legislature’s approval. Such approval will not be unreasonably withheld.
3.7.3.4 Resources: Describe the resources the Legislature will need to provide for
the transition and the length of time.
3.7.3.5 Staff Experience: Submit resumes with references for each proposed key
staff member employed by either Respondent or subcontractor.
3.7.4 Staffing Plan
3.7.4.1 Staffing Response: The Respondent should present a staffing Response that
illustrates the best mix of skills and experience to achieve project objectives.
3.7.4.2 Key Personnel: Describe and provide names, resumes and responsibilities of
all Key Personnel (if any) and time commitments of proposed staff (full time/part
time and/or number of man days/months/ per person) over the course of the transition
project. At a minimum, include the project leader and the technical lead.
3.7.5 Subcontractors
3.7.5.1 Named Subcontractors: The Respondent should disclose the planned use of
any subcontractor that will perform five percent (5%) or more of the total cost of
services described in the ITN. In addition, Respondent may choose to identify any
other subcontractor that Respondent believes may add value.
3.7.5.2 Named Subcontractor Information: Respondent should provide the following
information: Name and address of each Named Subcontractor and the work the
subcontractor will be performing.
3.7.5.3 Subcontractor Approval: Adding or changing Named Subcontractors during
the contract requires prior legislative approval.
3.7.5.4 Subcontractor Performance: The Respondent will be responsible for the
performance of any subcontractors and will not be relieved by non-performance of
any sub-contractors. Respondent shall provide a summary of qualifications, years of
experience, and references for all Named Subcontractors.
3.7.5.5 The successful Respondent should replace the liaison or any assigned key
contact at the request of the Legislature.
ITN #851
39
3.7.6 Access Circuits
3.7.6.1 Access Circuit: Attach a sample project plan and schedule for the transition
of a district office and all other activities associated with the transition. The project
plan should address, at a minimum, the following areas:
 Moves, Adds, Changes, and Deletions plan
 Provisioning
 Installation
 Testing
 Cutover
 Acceptance
 Risk Management plan
 Escalation procedure
 Assumptions on times to deal with other parties (the Legislature, district
office personnel, local access providers, CPE order/delivery, etc.)
3.7.7 Timeline
3.7.7.1 All Sites: Propose a representative timeline for the transition of the Data
Center, (Sites listed in Section 3.1.1) and testing sites. It is not necessary to call out
individual sites, but the Respondent must provide justification for the proposed
timeline.
3.7.7.2 Liquidated Damages for Missed Timeline: Prior to award, the Legislature
and Respondent will negotiate a mutually agreeable final timeline, based on the
Respondent’s proposed timeline. For each Access Circuit that is not transitioned
more than ten (10) business days after the date set forth in the timeline due to delays
not caused by the Legislature, acts of God, wars, acts of public enemies, strikes, fires,
floods, or other similar cause wholly beyond the Respondent’s control, the
Respondent shall pay to the Legislature, as liquidated damages, an amount equal to
two (2) times the current MRC for such circuit.
3.7.8 Cutover
The Legislature desires a seamless cutover strategy that minimizes any negative
impact on the ongoing delivery of services, especially the applications discussed in
Section 3.2.9. The Legislature requires that the Respondent address the following:
3.7.8.1 Cutover Methodology: Describe the methodology, processes, and procedures
for the logical and physical cutover of the network.
3.7.8.2 Cutover Backout: Describe the methodology, processes and procedures if the
site conversion fails.
3.7.8.3 Cutover Change Management: Describe the change management plan for
transition.
3.7.8.4 Cutover Test Plan: Describe the test plan for cutting over each site.
ITN #851
40
3.7.9 Acceptance
The acceptance of the circuits is to ensure that bandwidth, latency, and throughput
have been provisioned successfully. The Legislature desires the following:
3.7.9.1 Acceptance Methodology of Respondent: Describe the methodology,
processes and procedures for acceptance after the transition has been completed.
3.7.9.2 Acceptance Reports: Describe and provide sample of the reports that are
provided to ensure that, after the transition, the network is operating within specified
parameters.
3.7.9.3 Acceptance Billing: The Legislature’s obligation to pay shall begin only after
the Legislature accepts the service and the Respondent issues a disconnect order for
current service.
3.7.10 Training
3.7.10.1 Initial Training: Describe the initial training that is provided for network
management, ordering, billing, and problem management. There are various methods
of accomplishing the training, i.e. offsite courses, web-based, on customer site, etc.
3.7.10.2 Professional Development Training: Describe the ongoing training that is
provided for network management, ordering, billing and problem management.
There are various methods of accomplishing the training, i.e. offsite courses, webbased, on customer site, etc.
3.8
Disentanglement
The Legislature expects full, complete, and timely cooperation in disentangling the
relationship in the event that the Contract expires or terminates for any reason. In the
event of expiration or termination, the Legislature expects that the Respondent shall,
among other things: return all legislative data and documentation to the Legislature,
including but not limited to configuration information and allow the Legislature or the
replacement provider(s) continued access to all billing, ordering, and trouble ticketing
systems, and processes that have been employed in servicing the Legislature, in
accordance with methods and procedures to be agreed upon and established in the
Contract. In the event of the expiration or termination of the relationship between the
Legislature and the Respondent, the Respondent shall:
3.8.1 Disentanglement Approach and Process: The Respondent’s Response should
describe its specific approach to the Disentanglement process. Specifically, state the
Respondent’s proposed plan for Disentanglement, including key milestones and the
Legislature/Respondent roles and responsibilities. Provide time estimates for the
Disentanglement process based upon the number of locations detailed in this ITN.
3.8.2 Cooperation and Information: Respondent is requested to agree to cooperate
with the Legislature and/or the replacement provider(s) and otherwise take all
reasonable steps to assist the Legislature in effecting a smooth disentanglement upon
the expiration or termination of the Contract, including the provision of information
necessary to enable the Legislature’s personnel, or that of a replacement provider(s),
to fully assume and continue without interruption the provision of Services.
ITN #851
41
Respondent’s Response should state its understanding of this paragraph and provide
any details, conditions or assumptions.
3.8.3 Continued Service: Agree not to: (i) interrupt the provision of Services to the
Legislature and its users or any obligations related to disentanglement, (ii) disable any
hardware used to provide Services, or (iii) perform any other action that prevents,
slows down, or reduces in any way the provision of Services to Legislative Network
sites until the Legislature agrees that a satisfactory disentanglement has occurred.
Respondent’s Response should state their acknowledgement and agreement to each of
the subparts of this paragraph and provide any details, conditions or assumptions.
ITN #851
42
SECTION 4:
Administrative Documents Required
4.1
Economy of Presentation
Each Response shall be prepared simply and economically, providing straightforward,
concise delineation of Respondent’s capabilities to satisfy the requirements of this ITN.
Fancy bindings, colored displays, and promotional materials are not required. Emphasis on
each Response must be on completeness and clarity of content. To expedite the evaluation of
Responses, it is essential that Respondents follow the format and instructions contained
herein.
4.2
Submission of Responses
Responses must be submitted in two (2) separate sealed parts: a Technical Response and a
Cost Response, See Schedule of Events, Section 1.8 of this ITN.
The Response packages must be boxed or sealed and identified as follows:
 Response of (Your Company’s Name and any subcontracting entity)
 Type of Response: (Technical or Cost)
 ITN #851, Network Services
4.3
Part 1 - Administrative Documents and Technical Response Content
All Respondents must complete this section.
4.3.1
Administrative Documents [Mandatory - Respondent must confirm compliance]
The following items must be included in the Response:
 Completed Respondents Information Coversheet (page 1) of the ITN
 Signed Addenda Document(s) to the ITN (if applicable)
 Non-Collusion Statement (Appendix G)
 Disclosure Information (Appendix H)
 Copy of Respondent’s Standard Contract
 Warranties (Appendix I)
4.3.2
Technical Response Copies
One (1) original version, seven (7) copies and two (2) CD-ROM copies of the
following Technical Response components must be packaged and identified as the
Technical Response.
4.3.3
Technical Response Content [Mandatory - Respondent must confirm compliance]
4.3.3.1 Cover Page
4.3.3.2 Table of Contents
4.3.3.3 Respondent’s Mandatory Response Checklist, ITN Appendix F
4.3.3.4 Response to ITN Section 3.0 SCOPE OF SERVICES
ITN #851
43
In order to facilitate the Legislature’s evaluation of the Responses, the Respondent
must provide a complete description of how each requirement will be met, not merely
an acknowledgement.
The Respondent’s Technical Response must provide its approach/solution to all of the
requirements in the Scope of Services Section 3.0. The Technical Response must
not contain any cost information.
The Respondent’s organization of responses to the requirements must be arranged in
the sequence in which the requirements are referenced, and formatted with responses
inserted directly after the requirement or request. Specific answers may be crossreferenced throughout Respondent’s response to avoid duplication of material.
Additional information may be submitted to accompany the Response. In submitting
additional information, please mark it as supplemental to the required response.
Response to Requirements
All technical requirements defined in Section 3 must be addressed and responded to
by Respondents. In addition, Respondents must be able to fulfill the requirements
labeled [Mandatory – Respondent must confirm compliance]. Failure to meet a
mandatory requirement will result in disqualification of a Respondent’s Response.
General Business Information: The Respondent and any Named Subcontractors must
indicate the name, address, telephone number, Email address, FAX number, and
Employer Identification Number (EIN) of the legal entity with which the contract is
to be written.
Legal Status of the Company: The Respondent must indicate the legal status of the
company (e.g., sole proprietorship, partnership, or corporation).
Financial Information: The Legislature reserves the right to request evidence of a
Respondent’s financial capability or stability if the Legislature has a question as to
such Respondent’s abilities.
4.4
Part 2 – Cost Response [Mandatory - Respondent must confirm compliance]
The first cost component is composed of the Legislature’s total locations, (see Section 3.1.1).
Current configurations are provided to the Respondent in Appendix A. The Respondent is to
submit all four (4) bandwidth cost spreadsheets (Appendix B) back to the Legislature with
costs for a recommended solution. The Legislature will evaluate all four (4) bandwidth
options and reserves the right to select one (1) or more of the bandwidth options.
The Respondent must provide in a supplemental spreadsheet within Appendix B,
explanations for any cost that includes a variable or estimated component (e.g. Access One
Time and MRC cost, CPE One Time and MRC cost) and component level cost. Component
level cost will include all service codes that make up the cost of the item including any pass
through charges such as FCC mandated charges and taxes. Respondent will provide formulas
used for computing costs including FCC mandated charges, franchise fees, and taxes that are
clearly auditable and provide methodology for performing such audit.
The component level cost will be used to verify cost submitted in the four (4) bandwidth cost
spreadsheets for the total locations (see Section 3.1.1). Respondent must submit detailed all
ITN #851
44
inclusive component level cost. Respondent must include monthly recurring charges for all
services proposed including first and subsequent mileage (from any given CE to the PE
located anywhere in the state), training, consulting/design/engineering service, custom
documentation, firewalls, quality of service (Qo S), security, licenses, service generation
charges, time and material fees, upgrade costs for router components, expedite charges, etc.
4.4.1
Cost Spreadsheets Appendix B (Four (4) Bandwidth Options must submit all 4)
4.4.1.1 [Mandatory - Respondent must confirm compliance] Cost Response
Spreadsheets: The Legislature requires that the Respondent complete and
submit the Four (4) Bandwidth Cost Response Spreadsheets in Appendix
B in electronic format. Instructions for completing the spreadsheets are
provided therein.
4.4.1.2 Cost Consistency: Where the Legislature requests cost information in
more than one place and the four (4) bandwidth cost spreadsheets, the
Legislature requires that the Respondent’s stated cost for such items or
components must be the same or consistent in all places. Failure to
provide consistency may result in a negative impact on the evaluation.
4.4.1.3 [Mandatory - Respondent must confirm compliance] End to End
Inclusive Cost: Submit cost that is all-inclusive (including travel) of costs
end to end.
All Respondents must follow the instructions in this section carefully.
Copies: An original and seven (7) hard copies, and two (2) electronic versions of the Cost
Response contents are required.
The Respondent shall submit all four (4) Bandwidth Cost Responses in the Appendix B
Cost Response format and in a separately sealed package.
Four (4) Spreadsheets have been prepared for Respondents to submit cost for the full scope
of services as provided in Appendix B.
Respondents must use the tables in Excel to submit their four (4) Bandwidth Cost Responses.
No other method of submitting cost information will be accepted, and failure to comply will
result in rejection of Respondent’s Response. See Mandatory Requirement 4.4.1.1.
ITN #851
45
SECTION 5: Evaluation
5.1
Overview
Any Response that does not meet one or more of the mandatory requirements will be
disqualified. The Legislature reserves the right at any time and for any reason to cancel this
ITN. The Legislature reserves the right to waive any immaterial defects or irregularities in
any Response and the Legislature reserves the right to reject any and/or all Responses.
5.2
Overall Evaluation of Technical Response
Incompleteness, inconsistencies or inaccuracies in the Technical Response may result in a
negative impact on the evaluation.
Respondents must convey the technical, management, key personnel and other factors
necessary to meet the requirements of this ITN in sufficient detail within their written
Response. Responses which simply affirm and restate this ITN, or which do not adequately
convey the technical approach proposed to meet this ITN’s scope of services are not desired.
Such an approach may result in a negative impact on the evaluation of the Response or a
determination that the Respondent’s Response is non-responsive.
5.3
Oral Presentations (Optional)
After the initial technical evaluation, the Respondents may be requested to make one or more
oral presentations regarding their Responses, at dates, times and locations determined by the
Legislature. The purpose of such presentations will be to allow Responsive Respondents to
explain their proposed solutions and key points of their Responses. Additionally,
Respondents may be asked questions in order to provide a better understanding of how the
Responsive Respondent’s proposed solution will meet the requirements of this ITN. It is
critical that Respondents bring staff familiar with the detailed contents and solutions
presented within Responsive Respondent’s Response in order to maximize the productivity
of the Oral Presentation sessions. Oral presentations may not be required, may not occur,
and are not substitutes for a well-written Response.
5.4
Evaluation of Cost Responses
Respondents failing to submit cost in compliance with the Mandatory Requirements set forth
in Sections 4.4.1.1 and 4.4.1.3 will be disqualified and removed from further evaluation.
The Legislature will evaluate all four (4) bandwidth options and reserves the right to select
one (1) or more of the four (4) bandwidth options.
5.5
References
References shall be provided by the Respondent as outlined in Sections 3.7.3.2, 3.7.3.5 and
3.7.5.4 and shall be submitted using Appendix D – References. References submitted using
a format other than the Appendix D will not be considered.
5.6
Notification of Negotiations
Negotiations will be with the Respondents meeting all the Mandatory requirements in this
ITN.
ITN #851
46
Notification of Negotiations will be made to the respondents on or about April 26, 2011.
Negotiations shall be made with the responsive and responsible Respondents whose
Responses are determined to be the most advantageous to the Legislature, taking into account
all evaluation and negotiation factors set forth in this ITN.
5.7
Selection of Successful Respondent and Contract Award
The Legislature reserves the right to enter into contract negotiations with the Respondents to
arrive at a final agreement incorporating this ITN, any addenda to this ITN, the successful
Respondent’s response to this ITN, the contract, any purchase order(s) issued as a result of
this ITN, and such other terms and conditions agreed between the parties that may be
necessary to the Legislature. If, however, the negotiations impasse with each of the
respondents, the Legislature reserves the right to negotiate with any respondent who
successfully responded to this ITN. The Legislature intends to award a contract to the
respondent whose response through negotiations best meets the needs of the Legislature.
ITN #851
47