refreshed_PWS.pdf

Performance Work Statement For

Washington, DC 20024‐2141

1/14/2015

1. INTRODUCTION

This Task Order supports the Department of Housing and Urban Development Office of Inspector General (HUDOIG Office of Management and Technology), Infrastructure Services Division (ISD). The work described in this Performance Work Statement (PWS) includes the contract scope and objectives, to design, build, deploy, and maintain the HUDOIG Wide Area Network (WAN) and to provide WAN services (Network services).

The Department of Housing and Urban Development, Office of Inspector General (HUDOIG) was created with the signing of the Inspector General Act of 1978 (Public law 95‐452). The Inspector General (IG) has the authority to inquire into all of the programs and administrative activities of the Department. The HUDOIG serves its customers by being a proactive force in identifying and mitigating problems while remaining committed to its statutory mission of identifying and preventing waste, fraud, and abuse and promoting the effectivenessand efficiency in the Department’s programs, activities, and functions. The HUDOIG receives and processes complaints of inappropriate behavior or violations of law; conducts audits and investigations of HUD activities; and develops, analyzes, and reviews legislative and policy proposals.

HUDOIG is an independent and objective oversight agency, reporting to the Secretary and the Congress for the purpose of bringing about positive change in the integrity, efficiency, and effectiveness of HUD business operations.

The success of the HUDOIG mission requires a cost‐efficient, reliable, and fast telecommunications infrastructure.

2. SCOPE

The scope of this RFPI is to identify a vendor (Offeror) that can design, deploy and maintain a secure, fast and reliable WAN telecommunications infrastructure for HUDOIG at the best value. Included in the scope are the high level requirements to design, deploy and maintain a secure end‐to‐end telecommunications infrastructure that meets compliance frameworks: FISMA, US‐CERT, NIST, OMB directives and Government directives that establish security requirements for protecting Government data and privacy.

The WAN is a component of the HUDOIG Distributed Computing Environment (DCE). The other components of the DCE are the two datacenters (Central Server Facility and Disaster Recovery Facility) and the HUDOIG offices. Maintenance and support of the datacenters and HUDOIG offices are not in the scope of this PWS.

The Offeror Provider Edge (PE) routers, switches, and software are within the scope of this PWS.

The Customer Edge (CE) routers are not within the scope of this PWS.

3. OBJECTIVES

HUDOIG requires an Offeror that can meet the following business objectives:

3‐1. Offer realistic and transparent prices.

3‐2. Efficient management of the Offeror’s telecommunications resources, components and circuits.

3‐3. Proactive monitoring, addressing and communication of any network issues.

3‐4. Expeditious execution of HUDOIG’s change requests.

3‐5. Provide timely service and product cost information when requested.

3‐6. Proactive and prompt communication of planned and unplanned network maintenance activities.

3‐7. Provide a scalable solution that will enable HUDOIG to add business services such as video streaming and VOIP (for example).

3‐8. Implement dedicated replication circuit between HUDOIG datacenters.

3‐9. Be proactive in regularly identifying solutions that would lower costs without a reduction in service, performance or availability.

3‐10.Assist HUDOIG in meeting new and existing Federal mandates and regulations.

4. HUDOIG LOCATIONS

The HUDOIG WAN encompasses various locations within the continental US and Puerto Rico and two datacenters. Network services for HUDOIG are currently implemented at/between two primary datacenters, the Central Server Facility (CSF) located in Washington, D.C., and the Disaster Recovery Facility (DRF), located in Denver CO. The two datacenters provide failover capabilities to the organization.

• CSF address – 1845 4th Street, NE Washington DC 20002‐1503

• DRF address – 335 Inverness Drive South, Englewood, CO 80112‐5882

The Offeror will terminate WAN circuits between each of the sites listed in Appendix A, and the CSF and DRF. HUDOIG requests pricing for Ethernet handoff at all locations. Where Ethernet handoff is not available, HUDOIG requests that the most cost effective access be proposed that meets the stipulated service delivery requirements in this PWS. Additionally, HUDOIG requests that all sites have an alternate, cost effective handoff proposed.

5. TECHNICAL REQUIREMENTS

All information and requirements contained within this document are requirements that the Offeror shall provide as part of their service.

The Offeror shall deploy a synchronous dedicated link between the two datacenters for replication and failover purposes. The Offeror shall be able to satisfy the requirements described herein; all services are required to operate and perform as defined in the attached Service Level Requirements.

5.1 WAN REQUIRMENTS

The Offeror shall meet the following requirements:

5.1‐1. The Offeror shall be responsible for the provisioning, installation, and coordination of all circuits.

5.1‐2. The Offeror shall deploy the WAN that connects all HUDOIG Offices to the CSF and DRF.

5.1‐2. The Offeror shall provide network bandwidth and system capacity for the WAN based on infrastructure and application requirements.

5.1‐3. The Offeror shall develop, maintain, and deliver network specifications, configuration, and topology diagrams.

5.1‐4. The Offeror shall deliver network engineering plans and schedules to support new and enhanced network applications, architectures, and standards.

5.1‐5. The Offeror shall conduct pre‐installation site surveys, as applicable, stage new and upgraded equipment to smoothly install and transition components into the network.

5.1‐6. The Offeror shall deploy Ethernet access type (preferred).

5.1‐7. The Offeror shall ensure a minimum bandwidth of 10 Mbps for Field Office locations.

5.1‐8. The Offeror shall ensure a minimum bandwidth 50 Mbps for Region Office locations.

5.1‐9. The Offeror shall ensure a minimum bandwidth of 200 Mbps for HUDOIG Headquarters.

5.1‐10. The Offeror shall ensure a minimum bandwidth of 1 Gbps for the synchronous dedicated link between the two datacenters.

5.1‐11. The Offeror shall ensure a minimum bandwidth of 100 MBps Ethernet for

Disaster Recovery Facility‐335 Inverness Dr South, Engelwood

5.1.1 WAN TRANSITION

The Offeror shall provision and install circuits as identified with the following requirements:

5.1.1‐1. The Offeror shall ensure continuity of operations during the transition period.

5.1.1‐2. The Offeror shall complete the transition from the current contractor to the Offeror with minimal disruption to the users.

5.1.1‐3. The Offeror shall provision HUDOIG datacenter’s circuits first; no later than 60 work days after receipt of order. contract award.

5.1.1‐4. All other new circuit deliveries shall be provisioned in accordance with a schedule negotiated between the Offeror and HUDOIG. New circuits shall be operational no later than sixty (60) work days from the date the circuit is approved.

5.1.1‐5. The Offeror shall ensure circuits are tested and fully functional. Test results shall be provided to HUDOIG. HUDOIG expects the Offeror to include circuit test planning in their proposal.

5.1.1‐6. The Offeror shall terminate circuits at the location Demarcation Point.

5.1.1‐7. All pertinent circuit information shall be provided to HUDOIG on the install date.

5.1.2 MOVES ADDS AND CHANGES

It is the intent of HUDOIG to maintain a stable WAN environment. Business requirements will require changes on as as‐needed basis. As required the following requirements include:

5.1.2‐1. The Offeror shall cancel, and relocate circuits, as authorized by HUDOIG, on an as needed basis.

5.1.2‐2. The Offeror shall provide quotes to be delivered to HUDOIG within 5 days of request.

5.1.2‐3. The Offeror shall provide operational circuits no longer than 60 business days after the authorization date. The authorization date will be the date of the contract modification.

5.1.2‐4. The Offeror shall decommission circuits no later than 30 business days after the authorization date.

5.1.2‐5. The Offeror shall ensure all new circuits are operational within 60 business days of authorization date.

5.1.2‐6. The Offeror shall ensure circuits are tested and fully functional. Test results shall be provided to HUDOIG.

5.1.2‐7. The Offeror shall provide a report of pertinent circuit information to HUDOIG on the install date.

5.1.3 ACCESS MEDIA TYPES

HUDOIG is primarily interested in Ethernet access at all sites where it is available. In the case that Ethernet hand off is not available.

5.1.3‐1. The Offeror shall identify the hand‐off that is available at each of the sites. If access is available in multiple forms, please indicate any price differences related to the different hand‐ offs.

5.1.3‐2. The Offeror shall describe in detail each proposed access service for each site, including availability and bandwidth scalability for each proposed access service.

5.1.4 DIVERSITY REQUIREMENTS

HUDOIG seeks Point‐of‐Presence (POP) level diversity for circuits. POP level diversity is HUDOIG’s preferred diversity strategy. HUDOIG will entertain solutions that are based around card level diversity in a single POP.

5.1.4‐1. Circuit diversity is a requirement for each datacenter and HUDOIG Headquarters. 7th Street address (refer to Appendix A).

5.1.4‐2. HUDOIG is interested in understanding the diversity options that are available for Regional and Field office sites. HUDOIG may choose not to purchase diversity for any or all of the Regional and Field office sites.

5.1.4‐3. The Offeror shall provide a description of the diversity options available for each site as well as a cost comparison for the different options.

5.1.5 ROUTING PROTOCAL SUPPORT

The Offeror shall provide HUDOIG with the list of routing protocols and technologies the Offeror supports.

5.1.5‐1. The Offeror shall provide HUDOIG with the limitations of the proposed protocols. For example: Describe table‐size limits for BGP / MBGP or identify any PRIVATE ASNs. The Offeror shall indicate whether or not these are hard limitations or soft limitations.

5.1.5‐2 If the service offering is a Layer 3 based MPLS VPN, then HUDOIG expects to run BGP with the service provider.

5.1.5‐3. The Offeror shall detail the maximum number of paths per prefix.

5.1.6 TRAFFIC ENGINEERING SUPPORT

Depending on the solution proposed by the Offeror, HUDOIG may need to influence traffic flows across diverse circuits in order to protect circuit capacity for a variety of reasons. HUDOIG is interested in understanding the mechanisms available for Traffic Engineering.

5.1.6‐1. The Offeror shall describe any mechanisms that exist for HUDOIG to influence the data paths over diverse circuits based upon the available routing protocols. For example: BGP Attributes: AS PATH, Communities, Local Preference, and Multiple Exit Discriminators.

5.1.6‐2. The Offeror shall describe any mechanisms that exist for HUDOIG to influence the data paths over diverse circuits based upon VPLS/MPLS label switching.

5.1.6‐3. If the network being proposed is a Layer 2 MPLS VPN (VPLS), the Offeror shall indicate whether or not customers may run their own Layer 3 MPLS VPN over the proposed network.

The Offeror shall highlight any limitations that are imposed upon this scenario.

5.1.7 QUALITY OF SERVICE

HUDOIG’s QoS strategy involves a potential of six forwarding classes with classification based upon DiffServ code points (DSCP). HUDOIG is interested in understanding the Offeror’s QoS options available on the provider network.

5.1.7‐1. The Offeror shall describe QoS implementation options available. In addition, the Offeror shall detail the number of forwarding classes available as well as the bandwidth allocations available to HUDOIG for each forwarding class.

5.1.7‐2. The Offeror shall advise whether or not the customer may choose custom sizes for the different forwarding classes.

5.1.7‐3. The Offeror shall provide the specifics of the DiffServ code point mappings per forwarding class.

5.1.7‐4. The Offeror shall advise policy for accepting and preserving any class marking set by

HUDOIG.

5.1.8 VOIP

HUDOIG intends to implement VOIP/Video on the WAN; the Offeror shall describe how this requirement will be supported. VOIP traffic shall be prioritized across the entire carrier backbone network with minimal delay and jitter. Jitter within the VOIP queue must be < 10ms.

The VOIP network shall be a separate subnet at each of the HUDOIG sites. The Offeror shall describe routing mechanisms available to prioritize and distribute this traffic over the WAN.

5.1.9 IP MULTICAST

HUDOIG may run Multicast natively across point to point circuits and over GRE tunnels with MBGP across the network. HUDOIG prefers to run IP multicast natively and eliminate the GRE tunnel and MBGP requirements if possible.

5.1.9‐1. The Offeror shall provide the ability to support IP multicast natively.

5.1.9‐2. The Offeror shall document requirements or limitations that exist including but not limited to the following: MBGP, Rendezvous Points, MSDP, and Multicast address space reservations.

5.1.10 DATACENTER REPLICATION

HUDOIG intends to implement a separate circuit for replication between the data centers in Colorado and the District of Columbia. This circuit shall be capable of extending the same VLAN’s between the two datacenters.

5.1.10‐1. This replication circuit shall also be used for user traffic in the event of one of the primary data center WAN circuit fails.

5.1.10‐2. The Offeror shall propose what technologies will be used to support these requirements.

6. SECURITY

The Offeror shall provide system security in compliance with the Federal Information Security Management Act (FISMA), security‐related OMB Circulars and Memorandums (e.g., OMB Circular A‐ 130), security‐related compliance standards and requirements for federal agencies issued by the National Institute of Standards and Technology (NIST), and any future statutes, regulations, requirements, or guidelines for securing federal systems.

6.1 PERSONNEL SECURITY REQUIREMENTS

The Offeror must have the necessary procedures in place to ensure that all personnel working on the project are properly screened and cleared to work on the project. The personnel security requirements are detailed below.

6.1‐1. The Offeror shall ensure that all their personnel working on the project with access to

OIG data circuits are U.S. citizens and have a full background investigation with a public trust security clearance prior to either directly or remotely accessing HUDOIG computer system(s).

HUDOIG has final determination on acceptability. Favorable adjudication is required prior to any access to HUDOIG systems.

6.1‐2. The Offeror shall be responsible for all expenses associated with the clearance/security process and procedures for its personnel.

6.1‐3. The Offeror shall ensure that personnel and third‐party resources it uses for non‐data related maintenance and dispatch/repairs are escorted and monitored when working in secure areas. The Offeror shall be responsible for any actions of personnel performing activities on their behalf.

6.1‐4. The Offeror shall ensure that all Offeror’s personnel working on the project take and pass the Basic Systems Security Awareness course approved by HUDOIG , and available on‐line before commencing their HUDOIG duties and annually thereafter.

6.1‐5. The Offeror shall have and implement a documented formal sanctions process for personnel failing to comply with established security policies and procedures.

6.1‐6. The Offeror shall ensure that terminated employees have no access to government computing systems immediately prior to their termination in accordance with the MAC Delete procedures.

6.1‐7. The Offeror shall ensure the return of all government information system‐related property (e.g., documentation, software, equipment, keys, identification cards, building passes) when an employee is terminated. These shall be surrendered to HUDOIG immediately upon termination.

6.1‐8. The Offeror shall train personnel in their incident response roles and responsibilities with respect to the DCE, and provide refresher training no less than every twelve (12) months.

6.2‐1.

6.2 SYSTEMS AND INFORMATION SECURITY

At all points throughout the DCE, security must be in place to protect access to systems and the data contained on the systems. The systems and data security requirements are presented below.

6.3‐1. The Offeror on an ongoing and continuing basis shall review information system security alerts/advisories (e.g., CERTS, SANS, NIST) as published and take appropriate actions in response.

6.3‐2. The Offeror shall report, in real‐time, all DCE network incidents and attacks to HUDOIG Incident Response Team.

6.3‐3.

6.3‐4. The Offeror shall support the test and installation of newly released relevant security patches, service packs, and hot fixes in accordance with industry best practices.

6.3‐5. The Offeror shall address immediately flaws discovered during security assessments, continuous monitoring, or incident response activities.

6.3‐6.

6.3‐7. The Offeror shall maintain, review, and provide to HUDOIG DCE network audit logs as required.

6.3‐8. The Offeror shall archive and index network audit logs for management purposes. The audit logs must be available and provided upon HUDOIG management request.

6.3‐9. The Offeror shall ensure that the network protects audit information and audit tools from unauthorized access, modification, and deletion.

6.3‐10. The Offeror shall track and document network security incidents on an ongoing basis, and shall within one hour of discovery report incident information to HUDOIG Incident Response Team.

6.3‐11.

7. WAN ADMINISTRATION

Continuous monitoring 24x7 is crucial for ensuring that the HUDOIG WAN is always available to HUDOIG employees, and that the network is operating at the desired performance and availability levels. The network administration requirements are presented in accordance with Federal mandates and requirements are listed below.

7‐1. The Offeror shall provide real/near real time network monitoring and network performance tools for monitoring the status and performance of the network.

7‐2. The Offeror shall use these network monitoring and network performance tools to optimize performance of the network.

7‐3. The Offeror shall provide circuit error/discard monitoring with applicable reporting to

HUDOIG.

7‐4. The Offeror shall ensure all exceptions to normal operating conditions are communicated to

HUDOIG.

7‐5. The Offeror shall provide training to the designated HUDOIG POC in the use of the oversight and monitoring tools.

7‐6. The Offeror shall meet the SLAs specified in Appendix B.

7‐7. The Offeror shall provide 24x7 technical support of the WAN infrastructure.

7‐8. The Offeror shall provide the HUDOIG with reports and statistics resulting from real/near real time network monitoring.

7‐9. The Offeror shall ensure circuits are tested and fully functional. Test results shall be provided to HUDOIG. HUDOIG expects the Offeror to include circuit test planning in their proposal.

8. SUPPORT

In the design of its WAN, the Offeror must include elements that safeguard against outages. The Offeror must also have plans and facilities in place to ensure continued operations of HUDOIG Identified critical functions in the event of a disaster or major damage to the CSF. The outage prevention and disaster recovery requirements are presented below.

8‐1. The Offeror shall provide a Service Escalation Plan.

8‐2. The Offeror shall provide 24x7x365 support and access to Tier 2 support with a service escalation path to Tier 3 support engineers.

8‐3. In the event of errors on a circuit, non‐intrusive testing shall be performed first to try and isolate the cause of errors.

8‐4. Intrusive testing shall only be performed during pre‐scheduled downtime coordinated with

HUDOIG. Intrusive testing will be completed according to this schedule and on‐demand when approved by HUDOIG.

9. PROJECT MANAGEMENT

HUDOIG intends to reduce risk and uncertainty through industry standard project management activities.

The Offeror shall propose the project management activities to create repeatability, reliable performance and standardization. As such HUDOIG expects the Offeror to plan, organize, and control all activities, tasks, and resources that impact of otherwise effect the service delivery, or the identified Service Level Requirements.

9‐1. The Offeror shall propose the Project Manager to manage the transition activities..

9‐2. The Offeror shall propose an Account Manager as HUDOIG’s main point of contact.

9‐3. The Offeror shall demonstrate in their offering, problem or service ticket escalation methodology to ensure circuit, or service delivery problems are aggressively resolved with minimal customer intervention required.

9‐4. The escalation process shall allow for HUDOIG input to Offeror’s upper management if lower tier management of service tickets is not acceptable to the HUDOIG.

9‐5. The Offeror shall develop, and submit to HUDOIG for approval, a Project Management Plan that includes but is not limited to the rationale for the proposed organization, the work to be performed, the schedule for performance, the method by which communications with HUDOIG will be accomplished, the method for problem resolution, and the resources allocated to each task.

9‐6. The Offeror shall develop, and submit to HUDOIG for approval, a Risk Management Plan that includes but is not limited to: specifying the context, identifying and prioritizing the risks, specifying the identified risk management strategies, and describing how the risk management program will be monitored. In addition it should describe the process by which risks will be recorded and managed.

10. DELIVERABLES AND REPORTING

The Offeror shall develop, deliver to HUDOIG for acceptance and regularly update a prescribed set of deliverables.

10‐1. Within 5 business days of contract award, the Offeror shall deliver a Transition Plan.

10‐2. Within 60 days of contract award after receipt of order, the Offeror shall deliver initial WAN circuits that meet or exceed the Service Level Requirements.

10‐3. Within 30 business days of contract award, the Offeror shall deliver a Service Escalation

Plan.

10‐4. Within 30 business days of contract award, the Offeror shall deliver a Project

Management Plan.

10‐5. Within 30 business days of contract award, the Offeror shall deliver a Risk Management

Plan.

10‐6. Within 30 days of contract award, the Offeror shall deliver network topology diagrams.

10‐7. The Offeror shall deliver within five business days of each month a Monthly Service

Level Requirements Compliance Report for the previous month.

11. CONTRACT TYPE

The anticipated contract type of this contract is Firm Fixed Price.

12. PERIOD OF PERFORMANCE

Date of Award thru one year thereafter, with 4 optional periods. The Government may exercise the option periods up to 1 day prior to the expiration of the preceding contract period.

13. EVALUATION CRITERIA

Proposals will be evaluated using the following criteria, which are of descending importance:

Technical Approach Past Performance Price

The basis for award for this task order will be a best value determination considering technical capability and price. Technical capability (including the technical approach and experience/past performance, combined) is significantly more important than price.

As part of the proposal submission, offerors shall submit a Proposal Matrix using the table below or similar format, which maps what page of the proposal addresses each Performance Work Statement requirement identified under Technical Approach, and which page of the proposal fully addresses each Evaluation Factor.

The offeror shall use the appropriate column to fill in the requirement as stipulated in the RFP to which the page/section number applies.

Proposal Page(s)/Section

Number(s) RFP Requirement

Statement of Work

Section L or Instructions to Offerors

Section M or Evaluation

Factors Comments

TECHNICAL APPROACH (Shall not exceed 50 pages)

The offeror shall submit a technical approach that demonstrates logical and feasible methods for meeting the requirements described in the Performance Work Statement 1 through 12 ( the offeror must address all tasks in the PWS) and meeting the performance objectives outlined within the solicitation.

The offeror shall submit a project schedule that demonstrates a clear understanding of the required operations and HUD requirements with realistic timeframes for performing all tasks.

If the offeror is proposing subcontractors, the offeror shall clearly identify what aspects of the work will be performed by the prime and what aspects of the work will be performed by each subcontractor in its technical approach.

The Government will evaluate the following regarding the proposed Technical Approach:

How well the proposal demonstrates logical and feasible methods for meeting the requirements described in Performance Work Statement Sections 1 through 12 and meeting the performance objectives outlined within the solicitation;

o How well the project schedule demonstrates:

a clear understanding of the required operations and HUD‐OIG requirements;

and realistic timeframes for performing the PWS/SOW tasks and associated deliverables identified in the Instructions to Offerors.

If the proposal includes subcontractors, how well the proposed approach delineates the technical responsibilities between the prime and the subcontractor(s).

Technical Approach Proposals will be rated as follows:

Excellent (High Confidence) – The overall assessment of the offeror’s technical approach reveals a sufficient quantity of highly relevant and high quality technical performance. There is no doubt the offeror will successfully perform the effort required under the contract. The confidence of successful performance is evaluated as high.

Good (Significant Confidence) – The overall assessment of the offeror’s technical approach, in terms of relevancy, quality, and sufficiency reveals a technical approach in which there is little doubt the offeror will successfully perform the effort required under the contract. The confidence of successful performance is evaluated as significant.

Fair (Some confidence) – The overall assessment of the offeror’s technical approach in terms of relevancy, quality, and sufficiency reveals a past technical approach in which there is some doubt the offeror will successfully perform the effort required under the contract. The confidence of successful performance is evaluated as some.

Neutral – The overall assessment of the offeror’s technical approach, in terms of relevancy, quality, and sufficiency reveals the offeror has no relevant technical approach which may be effectively evaluated. The performance risk of the offeror is neutral. The contractor is rated neither good nor bad.

(Note that, to obtain this rating, the offeror must specifically address the factor and state that the submitted technical approach must be determined to not be relevant. Failure to address the factor in its entirety does not warrant this rating.)

Unacceptable (Low confidence) – The overall assessment of the offeror’s technical approach, in terms of relevancy, quality, and sufficiency reveals a technical approach in which there is substantial doubt the offeror will successfully perform the effort required under the contract. This rating may also be due to the offeror failing to address the factor as required and no additional information is available.

The confidence of successful performance is evaluated as low.

PAST PERFORMANCE (Shall not exceed 30 pages)

The offeror shall submit the following information/documents:

A completed chart providing the information required by the Past Performance Information chart in Attachment 1. The chart shall reflect all relevant past performance performed in the three year period immediately preceding submission of the proposal and all work currently being performed. If the offeror has more than 5 relevant past performance references, then the offeror shall provide the most recent 5 references. As an attachment to the chart, the offeror shall provide a narrative describing the past performance references that reflect the most relevance to the services being obtained under the contract to be awarded. The narrative shall clearly establish the relevancy of the past performance to the current requirements. (Narratives shall not exceed 1 page per reference.)

If the offeror is proposing to subcontract (or use joint ventures/ partners, or other entities other than the prime contractor to perform) more than 20% of the contract value, the offeror shall submit a separate chart and narrative described for past performance above, for the proposed subcontractor(s).

The contractor shall provide the survey contained in Attachment 2 to each past performance reference in sufficient time for the reference to complete and submit the survey directly to the HUD Contracting Officer prior to the date and time for submission of proposals. Offerors are not required to submit surveys for references where past performance is available in the Past Performance Information Retrieval System.

In evaluating Past Performance, HUD‐OIG will address four components – recency, relevancy, quality, and sufficiency. This factor’s primary emphasis is to assess the past performance of the proposed prime contractor (or in the case of joint ventures or some other teaming arrangement, the primary member of the team). However, if significant subcontracting/use of other teaming arrangements is anticipated, the past performance history of the proposed subcontractors/other team members must also be evaluated.

All references will be first assessed for recency and HUD will consider only references performed within the three years immediately prior to submission of the proposal;

Of those determined to be recent, HUD will assess the degree of similarity in scope, value and magnitude the past performance efforts submitted have to the solicitation requirements to determine relevancy;

HUD will then assess relevant past performance efforts for quality;

HUD’s overall assessment will be based upon sufficiency of high quality past performance and risk of nonperformance.The final rating under this factor will encompass the totality of the information provided, including completeness, relevancy, and the depth, breadth, and quality of only relevant past performance for the proposed prime contractor and proposed subcontractor/team members. The final rating will range from Excellent (High Confidence) to

Unacceptable (Low Confidence). Offerors that have addressed the factor and have no relevant past performance history by the prime and any subcontractors/team members will be rated as Neutral (Unknown Confidence). Offerors that fail to address the factor will be determined to have not complied with the solicitation requirements and will receive the lowest possible rating.

HUD is not restricted to evaluating the information provided by the offeror or the surveys provided by references and may utilize information obtained from any source. HUD will obtain additional information from the Government’s Past Performance Information Retrieval System (PPIRS), if available.

Past performance Proposals will be rated as follows:

Excellent (High Confidence) – The overall assessment of the offeror’s recent past performance reveals a sufficient quantity of highly relevant and high quality past performance. There is no doubt the offeror will successfully perform the effort required under the contract. The confidence of successful performance is evaluated as high.

Good (Significant Confidence) – The overall assessment of the offeror’s recent past performance, in terms of relevancy, quality, and sufficiency reveals a past performance record in which there is little doubt the offeror will successfully perform the effort required under the contract. The confidence of successful performance is evaluated as significant.

Fair (Some confidence) – The overall assessment of the offeror’s recent past performance, in terms of relevancy, quality, and sufficiency reveals a past performance record in which there is some doubt the offeror will successfully perform the effort required under the contract. The confidence of successful performance is evaluated as some.

Neutral – The overall assessment of the offeror’s past performance, in terms of relevancy, quality, and sufficiency reveals the offeror has no relevant past performance record which may be effectively evaluated. The performance risk of the offeror is neutral. The contractor is rated neither good nor bad. The performance risk of the offeror is neutral.

(Note that, to obtain this rating, the offeror must specifically address the factor and either state it has no relevant past performance or the submitted past performance must be determined to not be relevant. Failure to address the factor in its entirety does not warrant this rating.)

Unacceptable (Low confidence) – The overall assessment of the offeror’s past performance, in terms of recency, relevancy, quality, and sufficiency reveals a past performance record in which there is substantial doubt the offeror will successfully perform the effort required under the contract. This rating may also be due to the offeror failing to address the factor as required and no additional information is available. The confidence of successful performance is evaluated as low.

PRICE (Shall not exceed 20 pages)

Offerors shall submit prices that are consistent with the requirements set forth in the Performance Work

Statement of this solicitation. If the offeror proposes annual cost of living increases, the offeror must support the proposed increases with historical and relevant market index information.

Price will be evaluated separately from Technical and other non‐cost/price factors, and will be evaluated as follows:

Reasonableness. The reasonableness of the prices proposed will be evaluated as follows:

On the basis of adequate price competition, by comparing the proposed prices among offers;

Comparing proposed prices to the Independent Government Cost Estimate to ensure that prices are reasonable for the results to be achieved;

Determining if the proposed labor mix is based upon reasonable assumptions and is consistent with the requirements set forth in the Performance Work Statement/Statement of Work and the proposed technical approach.

Ensuring line item prices are not unbalanced.

The total evaluated price will include all option periods, including the value of the 6‐month extension if the Option to Extend Services clause at FAR 52‐217‐8 is included in the solicitation.

The Government will evaluate the reasonableness of proposed price for the option periods by assessing the acceptability of the offeror’s methodology used in developing the price estimates. For the cost to be reasonable in its nature and amount, it should not exceed that which would be incurred by a prudent person in the conduct of a competitive business. Reasonableness takes into account the context of a given source selection, including current market conditions and other factors that affect the ability of an offeror to perform the contract requirements.

APPENDIX A HUDOIG OFFICE LOCATIONS

Region Street City State Zip As is Circuit

Region 1/2 ‐ New T3 ‐ 12 York 26 Federal Plaza New York NY 10278‐0068 Mbps Region 1/2 – Boston T3 ‐ 12 Field Office 10 Causeway Street Boston MA 02222‐1092 Mbps Region 1/2 Field T3 ‐ 12 Office 1085 Raymond Blvd Newark NJ 07102‐5206 Mbps Region 1/2 Field T1 ‐ 1.5 Office 20 Church Street Hartford CT 06103‐3904 Mbps Region 1/2 Field T1 ‐ 1.5 Office 465 Main Street Buffalo NY 14203‐1780 Mbps Region 11/2 Field T1 ‐ 1.5 Office 275 Chestnut Street Manchester NH 03101 Mbps Region 1/2 Field T1 ‐ 1.5 Office 52 Corporate Circle Albany NY 122035121 Mbps

Region 3 – T3 ‐ 12 Philadelphia 100 Penn Square East Philadelphia PA 19107‐3380 Mbps

T1 ‐ 1.5 Region 3 Field Office 10 South Howard Street Baltimore MD 21201‐2505 Mbps

T1 ‐ 1.5 Region 3 Field Office 1000 Liberty Avenue Pittsburgh PA 15222‐4004 Mbps

T1 ‐ 1.5 Region 3 Field Office 600 E. Broad Street Richmond VA 23219 Mbps

T3 ‐ 12 Region 4 – Atlanta 75 Spring Street, SW Atlanta GA 30303‐3388 Mbps

T1 ‐ 1.5 Region 4 Field Office 710 Locust St Knoxville TN 37902‐2526 Mbps

T1 ‐ 1.5 Region 4 Field Office 350 Carlos Chardon Ave San Juan PR 00918 Mbps

T1 ‐ 1.5 Region 4 Field Office 909 S E 1st Avenue Miami FL 33131‐3028 Mbps

T1 ‐ 1.5 Region 4 Field Office 1500 Pinecroft Road Greensboro NC 27407‐3707 Mbps

Region 4 Field Office 400 N. Tampa Street Tampa FL 33602 T1 ‐ 1.5

Mbps

T1 ‐ 1.5 Region 4 Field Office 200 Jefferson Ave Memphis TN 38103 Mbps

T3 ‐ 12 Region 5 ‐ Chicago 77 West Jackson Blvd Chicago IL 60604‐3507 Mbps

T1 ‐ 1.5 Region 5 Field Office 477 Michigan Avenue Detroit MI 48226‐2592 Mbps

T1 ‐ 1.5 Region 5 Field Office 200 North High Street Columbus OH 43215‐2499 Mbps

T1 ‐ 1.5 Region 5 Field Office 1350 Euclid Avenue Cleveland OH 44115‐1815 Mbps

920 Second Avenue, T1 ‐ 1.5 Region 5 Field Office South Minn‐St Paul MN 55402 Mbps

T1 ‐ 1.5 Region 5 Field Office 151 N. Delaware Street Indianapolis IN 46204‐2526 Mbps

T3 ‐ 12 Region 6 ‐ Fort Worth 819 Taylor Street Fort Worth TX 76102‐6195 Mbps

T1 ‐ 1.5 Region 6 Field Office 500 Poydras Street New Orleans LA 70130‐3099 Mbps

T1 ‐ 1.5 Region 6 Field Office 1301 Fannin Street Houston TX 77002 Mbps

Oklahoma T1 ‐ 1.5 Region 6 Field Office 301 Northwest 6th St City OK 73102 Mbps

T1 ‐ 1.5 Region 6 Field Office 615 E. Houston San Antonio TX 78205‐2001 Mbps

T1 ‐ 1.5 Region 6 Field Office 5757 Corporate Blvd. Baton Rouge LA 70808 Mbps

Room 7th Floor, Suite T1 ‐ 1.5 Region 6 Field Office 7301; 500 Gold Ave. SW Albuquerque NM 87102‐3118 Mbps

T3 ‐ 12 Region 6 Field Office 801 Cherry Street Fort Worth TX 76102 Mbps

T1 ‐ 1.5 Region 6 Field Office 425 W Capitol Ave Little Rock AR 72201‐3425 Mbps

(4) T1 ‐ 6 Region 7 ‐ Kansas City 400 State Avenue Kansas City KS 66101‐2406 Mbps

T1 ‐ 1.5 Region 7 Field Office 1222 Spruce Street St Louis MO 63103‐2836 Mbps

T3 ‐ 12 Region 8 – Denver 1670 Broadway Denver CO 80202 Mbps

(2) T1 ‐ 3 Region 8 Field Office 909 1st Ave Seattle WA 98104‐1000 Mbps

T1 ‐ 1.5 Region 8 Field Office 125 South State Street Salt Lake City UT 84138 Mbps

T1 ‐ 1.5 Region 8 Field Office 2900 4th Avenue North Billings MT 59101 Mbps

Region 9 ‐ Los T3 ‐ 12 Angeles 611 West 6th Street Los Angeles CA 90017 Mbps

T1 ‐ 1.5 Region 9 Field Office 600 Harrison Street San Francisco CA 94107 Mbps

T1 ‐ 1.5 Region 9 Field Office 1 North Central Avenue Phoenix AZ 85004‐4415 Mbps

T1 ‐ 1.5 Region 9 Field Office 302 E Carson Ave. Las Vegas NV 89101 Mbps

T1 ‐ 1.5 Region 9 Field Office 650 Capitol Mall Sacramento CA 95814 Mbps

T1 ‐ 1.5 Region 9 Field Office 7832 Smokerise Court Las Vegas NV 89132 Mbps

T3 ‐ 45 HQ 451 7th Street SW Washington DC 20410 Mbps

550 12th Street SW ‐ T3 ‐ 12 HQ Potomac Center Washington DC 20024 Mbps

1250 Maryland Ave SW T3 ‐ 45 HQ 3rd floor Suite 300 Washington DC 20024 Mbps

Central Server Facility 1845 4th Street, NE Washington DC 20002‐1503 T3‐45Mbps

Disaster Recovery Facility 335 Inverness Dr. South Englewood CO 80112‐5882 T3‐45Mbps

APPENDIX B SERVICE LEVEL REQUIREMENTS

This appendix defines the Service Level Requirements for the Offeror to provide levels of service that meet HUDOIG expectations.

Since technology and services change through each year, this document will be updated on a regular basis to reflect those changes. This Service Level Agreement defines the service environment, service descriptions with roles and responsibilities, and service level requirements (SLRs) for the provisioning of HUDOIG Network services.

HUDOIG has established several goals for network performance and network administrative services.

The overall goal is to provide high‐quality support services to customers using the physical network in a cost‐effective manner.

A summary of the network services goals follows:

Network Performance SLR

Definition Network availability is defined as the time during which the network is fully operational and functioning as specified, connectivity between the user and the application system(s) and server(s) is established, and normal business operations can be carried out with no data loss or downtime.

Pre‐scheduled downtime requirements

All pre‐schedule system downtime must be communicated and coordinated with HUDOIG.

All pre‐scheduled system downtime, unless otherwise agreed upon in advance by Delivery Services will occur one weekend a month.

Work must conform to Configuration Management standards.

Service Type Service Measure Performance Target SLR Availability Routine 24x7x365 99.9% Grade of Service (Packet Loss)

Routine <.01% 99/9%

Latency (Aggregate) Routine 70 ms 99.9% Latency (per circuit) Routine 20 ms 99.9% Utilization (Aggregate) Routine <70% 99.9% Utilization (per circuit) Routine <50% 99.9%

HQ Circuit Routine 200 Mbps 99.9%

Regional Office Circuit Routine 50 Mbps 99.9% Field Office Circuits Routine 10 Mbps 99.9% Datacenter Synchronous Dedicated Link

Routine 1 Gbps 99.9%

Jitter (VOIP) Routine <10 ms 99.9%

Network Administration Service SLR

Definition Service requirements identified to provide high‐quality support services to HUDOIG.

Service Type ServiceMeasure Performance Target SLR Network Monitoring Routine 24x7x365 99.9% Technical Support – Time to Answer

Routine < 5 minutes 99.9%

Support Tier Escalation Routine < 2 hours 99.9% Support Tier Escalation Priority < 30 minutes 99.9% New Circuit Routine 60 business days after approval 99.9%

Disconnect Circuit Routine 30 business days after approval

99.9%

Change Request Routine 3 business days after approval

99.9%

Change Request Priority <1 hour 99.9% Service Outage Priority <2 hours plus priority

Time to Restore 99.9%

Time to Restore (without dispatch)

Routine 4 hours 99.9%

Time to Restore (without dispatch)

Priority 1 hour 99.9%

Time to Restore (with dispatch)

Routine 8 hours 99.9%

Time to Restore (with dispatch)

Priority 4 hours 99.9%

Contract Clauses

52.212-1 Instructions to Offerors - Commercial Items. (APR 2014)

(a) North American Industry Classification System (NAICS) code and small business size standard. The NAICS code and small business size standard for this acquisition appear in Block 10 of the solicitation cover sheet (SF 1449). However, the small business size standard for a concern which submits an offer in its own name, but which proposes to furnish an item which it did not itself manufacture, is 500 employees.

(b) Submission of offers. Submit signed and dated offers to the office specified in this solicitation at or before the exact time specified in this solicitation. Offers may be submitted on the SF 1449, letterhead stationery, or as otherwise specified in the solicitation. As a minimum, offers must show-

(1) The solicitation number;

(2) The time specified in the solicitation for receipt of offers;

(3) The name, address, and telephone number of the offeror;

(4) 52.204-10, Reporting Executive Compensation and First-Tier Subcontract Awards (FEB 2012) (Pub. L. 109-282) (31 U.S.C. 6101 note).

(5) Terms of any express warranty;

(6) Price and any discount terms;

(7) "Remit to" address, if different than mailing address;

(8) A completed copy of the representations and certifications at FAR 52.212-3 (see FAR 52.212-3(b) for those representations and certifications that the offeror shall complete electronically);

(9) Acknowledgment of Solicitation Amendments;

(10) Past performance information, when included as an evaluation factor, to include recent and relevant contracts for the same or similar items and other references (including contract numbers, points of contact with telephone numbers and other relevant information); and

(11) If the offer is not submitted on the SF 1449, include a statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation.

Offers that fail to furnish required representations or information, or reject the terms and conditions of the solicitation may be excluded from consideration.

(c) Period for acceptance of offers. The offeror agrees to hold the prices in its offer firm for 30 calendar days from the date specified for receipt of offers, unless another time period is specified in an addendum to the solicitation.

(d) Product samples. When required by the solicitation, product samples shall be submitted at or prior to the time specified for receipt of offers. Unless otherwise specified in this solicitation, these samples shall be submitted at no expense to the Government, and returned at the sender's request and expense, unless they are destroyed during preaward testing.

(e) Multiple offers. Offerors are encouraged to submit multiple offers presenting alternative terms and conditions or commercial items for satisfying the requirements of this solicitation. Each offer submitted will be evaluated separately.

(f) Late submissions, modifications, revisions, and withdrawals of offers. (1) Offerors are responsible for submitting offers, and any modifications, revisions, or withdrawals, so as to reach the Government office designated in the solicitation by the time specified in the solicitation. If no time is specified in the solicitation, the time for receipt is 4:30 p.m., local time, for the designated Government office on the date that offers or revisions are due.

(2)(i) Any offer, modification, revision, or withdrawal of an offer received at the Government office designated in the solicitation after the exact time specified for receipt of offers is "late" and will not be considered unless it is received before award is made, the Contracting Officer determines that accepting the late offer would not unduly delay the acquisition; and-

(A) If it was transmitted through an electronic commerce method authorized by the solicitation, it was received at the initial point of entry to the Government infrastructure not later than 5:00 p.m. one working day prior to the date specified for receipt of offers; or

(B) There is acceptable evidence to establish that it was received at the Government installation designated for receipt of offers and was under the Government's control prior to the time set for receipt of offers; or

(C) If this solicitation is a request for proposals, it was the only proposal received.

(ii) However, a late modification of an otherwise successful offer, that makes its terms more favorable to the Government, will be considered at any time it is received and may be accepted.

(3) Acceptable evidence to establish the time of receipt at the Government installation includes the time/date stamp of that installation on the offer wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel.

(4) If an emergency or unanticipated event interrupts normal Government processes so that offers cannot be received at the Government office designated for receipt of offers by the exact time specified in the solicitation, and urgent Government requirements preclude amendment of the solicitation or other notice of an extension of the closing date, the time specified for receipt of offers will be deemed to be extended to the same time of day specified in the solicitation on the first work day on which normal Government processes resume.

(5) Offers may be withdrawn by written notice received at any time before the exact time set for receipt of offers. Oral offers in response to oral solicitations may be withdrawn orally. If the solicitation authorizes facsimile offers, offers may be withdrawn via facsimile received at any time before the exact time set for receipt of offers, subject to the conditions specified in the solicitation concerning facsimile offers. An offer may be withdrawn in person by an offeror or its authorized representative if, before the exact time set for receipt of offers, the identity of the person requesting withdrawal is established and the person signs a receipt for the offer.

(g) Contract award (not applicable to Invitation for Bids). The Government intends to evaluate offers and award a contract without discussions with offerors. Therefore, the offeror's initial offer should contain the offeror's best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions if later determined by the Contracting Officer to be necessary. The Government may reject any or all offers if such action is in the public interest; accept other than the lowest offer; and waive informalities and minor irregularities in offers received.

(h) Multiple awards. The Government may accept any item or group of items of an offer, unless the offeror qualifies the offer by specific limitations. Unless otherwise provided in the Schedule, offers may not be submitted for quantities less than those specified. The Government reserves the right to make an award on any item for a quantity less than the quantity offered, at the unit prices offered, unless the offeror specifies otherwise in the offer.

(i) Availability of requirements documents cited in the solicitation. (1)(i) The GSA Index of Federal Specifications, Standards and Commercial Item Descriptions, FPMR Part 101-29, and copies of specifications, standards, and commercial item descriptions cited in this solicitation may be obtained for a fee by submitting a request to- GSA Federal Supply Service Specifications Section, Suite 8100, 470 East L'Enfant Plaza, SW, Washington, DC 20407, Telephone (202) 619-8925, Facsimile (202) 619-8978.

(ii) If the General Services Administration, Department of Agriculture, or Department of Veterans Affairs issued this solicitation, a single copy…