EIS_RFP_Section_L_Amendment_07.docx

Enterprise Infrastructure Solutions (EIS) Request for Proposals

Section L Instructions, Conditions, and Notices to Offerors or Respondents

Issued by:

General Services Administration Office of Integrated Technology Services 1800 F St NW Washington, DC 20405

October 2015

Table of Contents

General Services Administration Network Services 2020 Enterprise Infrastructure Solutions

EIS RFP #QTA0015THA3003 Amendment 07 Enterprise Infrastructure Solutions EIS RFP #QTA0015THA3003 Amendment 07 iv Enterprise Infrastructure Solutions Appendix A Appendix B Appendix C Appendix D Appendix E Appendix F Appendix G Appendix H Appendix I Appendix J Appendix K Appendix L 52.252-1 Solicitation Provisions Incorporated by Reference (FEB 1998) This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. The Contracting Officer (CO) will make the full text available upon request. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. The full text of a solicitation provision may be accessed electronically at these addresses:

FEDERAL ACQUISITION REGULATION

http://acquisition.gov/far/index.html

GENERAL SERVICE ADMINISTRATION ACQUISITION MANUAL

http://www.acquisition.gov/gsam/gsam.html

52.211-3 Availability of Specifications Not Listed in the GSA Index of Federal Specifications, Standards and Commercial Item Descriptions (JUN 1988) The specifications not listed in the GSA Index of Federal Specifications, Standards and Commercial Item Descriptions cited in this solicitation may be obtained from:

Mr. Timothy Horan FAS EIS Contracting Officer 1800 F St NW Washington DC 20405-0001

Telephone (703) 306-6426 Timothy.Horan@gsa.gov The request should identify the solicitation number and the specification requested by date, title, and number, as cited in the solicitation.

52.215-20 Requirements for Certified Cost or Pricing Data and Data Other Than Certified Cost or Pricing Data (Alternate IV) (OCT 2010)

1. Submission of cost or pricing data is not required.

1. Provide data described below:

The offeror shall provide access to records necessary and sufficient to permit an adequate evaluation of the proposed price in accordance with FAR Part 15.403-3. If, after receipt of offers, the CO concludes that there is insufficient information available to determine price reasonableness on any price submitted in response to this Request for Proposal (RFP), then additional data other than cost data shall be made available by the offeror upon request; and if none of the exceptions applies then cost or pricing data shall be supplied.

52.216-1 Type of Contract (APR 1984) The government contemplates award of one or more Indefinite Delivery Indefinite Quantity (IDIQ), fixed-price, and time-and-materials with economic price adjustment contracts resulting from this solicitation.

52.216-29 Time-and-Materials/Labor-Hour Proposal Requirements-Non-Commercial Item Acquisition with Adequate Price Competition (FEB 2007)

1. The government contemplates award of a Time-and-Materials or Labor-Hour type of contract resulting from this solicitation.

2. The offeror must specify fixed hourly rates in its offer that include wages, overhead, general and administrative expenses, and profit. The offeror must specify whether the fixed hourly rate for each labor category applies to labor performed by—

1. The offeror;

1. Subcontractors; and/or

1. Divisions, subsidiaries, or affiliates of the offeror under a common control.

3. The offeror must establish fixed hourly rates using—

1. Separate rates for each category of labor to be performed by each subcontractor and for each category of labor to be performed by the offeror, and for each category of labor to be transferred between divisions, subsidiaries, or affiliates of the offeror under a common control;

1. Blended rates for each category of labor to be performed by the offeror, including labor transferred between divisions, subsidiaries, or affiliates of the offeror under a common control, and all subcontractors; or

1. Any combination of separate and blended rates for each category of labor to be performed by the offeror, affiliates of the offeror under a common control, and subcontractors.

52.233-2 Service of Protest (SEP 2006)

1. Protests, as defined in Section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the General Accounting Office (GAO), shall be served on the CO by obtaining written and dated acknowledgment of receipt from the CO at the address listed in Block 7 on Standard Form 33.

2. The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO.

Notice of Supply Chain Risk

1. Definitions. “Supply chain risk,” as used in this provision, means the risk that an adversary may sabotage, maliciously introduce unwanted function, or otherwise subvert the design, integrity, manufacturing, production, distribution, installation, operation, or maintenance of a national security system (as that term is defined at 44 U.S.C. 3542(b)) so as to surveil, deny, disrupt, or otherwise degrade the function, use, or operation of such system.

2. In order to manage supply chain risk, the government may consider information, public and non-public, including all-source intelligence, relating to an offeror and its supply chain.

Exceptions Any exceptions taken to the requirements, clauses, provisions or terms and conditions of the RFP must be submitted in writing to the government prior to the submission of offers. The offeror shall identify each requirement, clause, provision or term and condition for which exceptions and/or deviations are requested. Each exception and/or deviation identified must be fully explained including sufficient justification as to technical problems, cost savings, and/or benefits to the government so that the government can thoroughly evaluate the offeror’s input and determine if it is in the best interest of the government to amend the RFP. If the offeror’s explanation is not acceptable to the government, the exception and/or deviation will not be allowed and the RFP shall not be amended.

NO EXCEPTIONS AND/OR DEVIATIONS SHALL BE ACCEPTED AFTER THE CLOSING DATE OF THE RFP. ANY PROPOSAL CONTAINING EXCEPTIONS AND/OR DEVIATIONS MAY BE DETERMINED UNACCEPTABLE AND REMOVED FROM FURTHER CONSIDERATION.

Assumptions and Conditions All assumptions and/or conditions must be listed and discussed. The area of the RFP affected by the assumption and/or condition must also be identified. The resolution for each must be thoroughly detailed and documented.

The government reserves the right to reject any proposal that includes any assumption or condition that is a deviation from the government’s requirements.

Point of Contact Information

Mr. Timothy Horan FAS EIS Contracting Officer 1800 F St NW Washington DC 20405-0001

Telephone (703) 306-6426 Timothy.Horan@gsa.gov

A. Michelle White FAS EIS Contract Specialist 1800 F St NW Washington DC 20405-0001

Telephone (703) 306-6264 Audrea.White@gsa.gov 552.239-70 Information Technology Security Plan and Security Authorization (Jun 2011) All offers/bids submitted in response to this solicitation must address the approach for completing the security plan and certification and security authorization requirements as required by the clause at 552.239-71, Security Requirements for Unclassified Information Technology Resources.

Small Business Teaming Arrangement Small business prime contractors are encouraged to enter into a Small Business Teaming Arrangement with one or more other small business concerns and submit an offer as a small business. EIS is a consolidated requirement, and for small business teams competing for consolidated requirements SBA provides relaxed affiliation rules that enable small business team members to maintain their small business status. A joint venture or teaming arrangement of two or more business concerns may submit an offer as a small business without regard to affiliation as long as each concern is small under the size standard corresponding to the NAICS code 517110. The Small Business Teaming Arrangement must comply with the applicable limitations on subcontracting provisions and the non-manufacturer rule, if applicable, on all orders issued against the Multiple Award Contract.

Small Business Teaming Arrangement is defined as:

1. Two or more small business concerns that have formed a joint venture to act as a potential prime contractor.

2. A potential small business prime contractor agrees with one or more other small business concerns to have them act as its subcontractor(s) under a specified Government contract. A Small Business Teaming Arrangement between a prime and its small business subcontractor(s) must exist through a written agreement between the parties that is specifically referred to as a ‘‘Small Business Teaming Arrangement’’ or ‘‘Small Business Teaming Agreement’’ and which sets forth the different responsibilities, roles, and percentages (or other allocations) of work as it relates to the acquisition.

1. A Small Business Teaming Arrangement can include two business concerns in a mentor-protégé relationship so long as both the mentor and the protégé are small or the protégé is small and the concerns have received an exception to affiliation.

1. The agreement must be provided to the CO as part of the proposal with the Business Volume.

Modifications to Proposals All proposal revisions/updates shall meet the following criteria:

1. Submit changes in the same electronic format as required for the initial proposal submission described in Section L.27.3. Electronic revision submissions shall conform to the organization and format requirements for the original submission. For electronic revision submissions, the offeror shall resubmit only the volume that includes the change except for price table changes. All changes must be marked and the offeror is required to identify what has changed by using track changes in Microsoft Word 2007 or newer.

2. Submit any changed electronic copies of the price tables with a complete update, not just the price(s) that may be changed.

Reserved Data to Support Proposal Analysis In accordance with FAR 15.404-2, the CO may request field pricing assistance when the pricing information is inadequate to determine a fair and reasonable price.

Delivery of Proposals Proposals shall be delivered through the AcquServe Portal as specified in Section L.27.3.

Proposal Due Date Proposals are due no later than February 22, 2016, 4:00 PM (Eastern Time Zone).

Solicitation Questions The EIS CO is the sole point of contact for all questions under this solicitation. The offeror shall submit questions electronically via the AcquServe Portal. Questions are due by December 7, 2015, 4:00 PM (Eastern Time Zone). The offeror is cautioned not to include its company name with any of the questions. This information will not be redacted from the government’s responses.

Potential offerors are responsible for gaining access to the AcquServe Portal in advance of proposal submission. Questions not submitted via AcquServe Portal will not be answered.

Disposition of Unclassified Drawings and Specifications Any drawings, specifications, and other material furnished by the government in connection with this solicitation need not be returned to the government, except as noted.

Minimum Acceptance Period Offerors allowing less than 365 days in the “offer” portion of SF 33 for acceptance by the government may be rejected as unacceptable.

Proposal Preparation Costs This RFP does not commit the government to pay any cost for the preparation and submission of a proposal(s) in response to this RFP.

Abbreviation and Acronym Definitions List The offeror may provide an abbreviation and acronym definitions list as part of the proposal response. The list will be excluded from the page count.

Reserved Disposition of Proposals One copy of each proposal will be retained by GSA in accordance with FAR 4.805. No destruction certificate will be issued.

Authorized Official and Submission of Proposal A Standard Form (SF) 33, Solicitation, Offer, and Award, completed and signed by the offeror, constitutes the offeror’s acceptance of the terms and conditions of this solicitation. An official authorized to bind the organization shall sign Block 17 of SF33 (page 1 of this solicitation) and complete provision K.2.1 as required.

Offers signed by an agent are to be accompanied by evidence of their authority. For additional information, see Section I, Clause 52.204-8.

If any amendments to the solicitation are issued, the offeror must acknowledge each amendment number and date in Block 14 of the SF33 and as part of the Business Volume.

The Offeror’s Legal Name and Address in Block 15A on the SF33 must match the information for the offeror in the System for Award Management (SAM) system at http:www.sam.gov.

Each offeror shall furnish the information required by the solicitation. The proposal shall be submitted in accordance with Section L.27.3.

Offerors are expected to read the entire solicitation. Failure to do so shall be at the offeror’s own risk.

Each response to this solicitation shall consist of six volumes: Technical, Management, Past Performance, Business, Subcontracting, and Price. Each volume shall include the following components:

1. Submission Matrix. The offeror shall complete the submission matrix in its entirety for each volume via AcquServe. A copy of the matrix is in Section J.19.

1. Cover Page. Each volume’s cover page shall include the offeror’s name, solicitation number, volume name, date, and revision number if appropriate.

1. Table of Contents. Each volume shall include a table of contents.

1. Information Requested in the Volume Instructions. The RFP provides these instructions for the Technical Volume in Section L.29, for the Management Volume in Section L.30, for the Past Performance Volume in Section L.31, for the Business Volume in Section L.32, Subcontracting in Section L.33 and for the Price Volume in Section L.34.

Offeror Performance Information The offeror is advised that the government will use the Past Performance Information Retrieval System (PPIRS) database as one source of information in assessing past performance under this solicitation. PPIRS can be accessed at: http://www.ppirs.gov/default.htm. The offeror may view its own data. In order to access the information in PPIRS, the offeror must register in the System for Award Management (SAM) system and must have created a Marketing Partner Identification Number (MPIN) in the SAM profile. The offeror shall go to the SAM web site at: http://www.sam.gov/ to register for the first time or update its information profile to indicate a past performance Point of Contact.

General Proposal Instructions The purpose of this section is to specify the general requirements for the contents of proposals. The proposal shall be submitted in electronic media through the AcquServe Portal. The specific requirements for the general proposal contents are presented in the following sections. The offeror shall submit a proposal that addresses the mandatory services identified in Section C. In addition, the offeror may propose one or more of the optional services identified in Section C. The offeror shall indicate which optional services it is offering through the “Optional Services” indicator tool described in the AcquServe Portal User Instructions.

The offeror shall not include classified material in its submission.

The proposal shall be submitted and uploaded in separate volumes as shown in Table L.27.1.

Contents of Proposals Table

Each proposal volume shall be limited to the maximum number of pages shown in Table L.27.2. Page counts shown for the Technical and Management volumes apply to both mandatory and optional services. Page counts do not apply to the Submission Matrix, cover page, table of contents, assumptions and conditions, abbreviation and acronym definitions list, Financial Status Report (Sample), Subcontracting Plan, or the price tables that must be submitted with the offeror’s proposal.

Contents of Proposal Volumes Table

1) Network Architecture & Technical Response

2) Risk Management Framework Plan

3) MTIPS Risk Management Framework Plan (if applicable)

4) Submission Matrix

250 (Including Optional Services)

Unlimited

1) Management Response

2) Program Management Plan

3) SCRM Plan

4) Draft BSS Verification Test Plan

5) EIS Verification Test Plan

6) Climate Risk Management Plan

7) Financial Status Report (Sample)

8) BSS Risk Management Framework Plan

9) NS/EP Functional Requirements Implementation Plan

10) Submission Matrix

Unlimited

Unlimited

1) Past Performance References Submission Matrix

Unlimited

1) Entire Business Volume Response Submission Matrix

Unlimited

1) Subcontracting Plan

2) Subcontracting History

3) Submission Matrix

Unlimited Unlimited

1) Price Response

2) Price Tables

3) Submission Matrix

3) Error Checker Explanation

Unlimited Unlimited Unlimited

The requirements for each of these volumes are set forth in this section; detailed instructions are provided in Sections L.28 – L.35. Failure to follow the instructions may result in the offeror’s proposal being removed from consideration.

The following format requirements apply for each proposal volume:

1. Microsoft Word 2007 or newer, standard letter size 8.5 x 11 inches, font type Arial with a size standard of 12 and one (1) inch margins. The maximum number of pages for each volume is based on the assumed use of standard 8.5 x 11 inch sheets. No embedding of files within the proposal files is permitted. Information provided via external links will not be considered. No other file formats, such as pdf, shall be accepted.

2. The following are the only pages that shall not be included in computing the maximum number of pages:

1. Cover Page, provided no proposal information appears Table of Contents List of Tables List of Figures Pages intentionally left blank Price tables Following Documents:

Financial Status Report (Sample) as required in Section L.30.1 The Subcontracting Plan as required in Section L.33.1.

Assumptions and Conditions as described in L.9.

Abbreviation and Acronym Definitions List per Section L.22.

3. Each page shall conform to the following:

1. Page Margin – Each page shall have the following margins:

i. Top and Bottom: 1.0 inch

ii. Left and Right: 1.0 inch

iii. Header and Footer: 0.5 inch

1. Font – The font used in the offeror’s proposal shall be 12 point Arial with no reduction. However, figures and charts may be reduced as long as text on the figures or charts is at least 66 percent of full size (i.e., 12 point).

1. Spacing – All volumes shall have line spacing of one-and-a-half.

Submission Requirements (Electronic) The offeror shall submit all proposal components electronically via the AcquServe Portal. Instructions on how to access the system are identified in the AcquServe Access Guide located in Section J.16.1. Once the offeror has access to the system, detailed proposal instructions will be available for download within AcquServe.

The file names for each volume shall identify the offeror’s name, volume name, date, sequence number (for multiple files), and revision number (if appropriate).

Any proposal submitted after the due date and time specified in block 9 of the SF33 is late and shall not be considered. The government will strictly observe FAR 52.215-1(c)(3)(ii) and (iii) for determining timeliness of proposal submissions. The AcquServe Portal is the “initial point of entry to the Government infrastructure” as envisioned by FAR 52.215-1(c)(3)(ii).

Multimedia Files No multimedia files (e.g., QuickTime or Windows Media Player) will be accepted.

Detailed Proposal Instructions This section provides detailed instructions for preparing proposals to offer mandatory services and, if offered, optional services. Mandatory and optional services are identified in Section C.

The proposal shall contain six volumes: 1) Technical, 2) Management, 3) Past Performance, 4) Business, 5) Subcontracting, and 6) Price. The instructions for preparing these volumes are provided in Sections L.29 through L.35.

Each volume shall be separate and complete in itself. The offeror shall present information in each volume in sufficient detail to enable an evaluator with a general professional expertise in the area of interest to thoroughly understand the response to this solicitation. The detail shall be sufficient that no reference to other volumes of the proposal or to non-proposal material is required to understand the offeror’s response. This includes links to external data. The proposal shall clearly demonstrate the offeror’s ability to perform the services in accordance with the government’s requirements.

Technical Volume The offeror shall prepare its Technical Volume to address all mandatory service requirements specified in this RFP and the requirements of any optional services that are offered.

If optional services are offered, all of the technical requirements pertaining to those optional services are mandatory unless otherwise stated.

The Technical Volume of the proposal shall conform to the following:

1. Network Architecture.

2. Technical Response to requirements for:

1. All mandatory EIS Services as listed in Section C.1.2

1. Any optional EIS Services as listed in Section C.1.8.1

1. Traffic identification and routing policy as identifed in Section C.1.8.8 sub-paragraph 3

3. Technical Volume documents to be addressed separately:

1. Risk Management Framework Plan as identified in Section C.1.8.7 System Security Requirements

1. If MTIPS (Section C.2.8.4) is offered, MTIPS Risk Management Framework Plan as identified in Section C.2.8.4.5

1. Technical Evaluation Matrices within the Submission Matrix (Section J.19) Network Architecture The offeror shall provide a description of its proposed network architecture that clearly articulates how the architecture will support all offered services to address the following:

Technical Response EIS Services For each of the EIS services that the offeror proposes, the offeror shall describe and explain how it will provide the proposed services and features, including how they will be provided architecturally and technically (referencing the network architecture description provided in Section L.29.1), and shall identify their solutions for the following areas (as defined in Section M.2.1) for each proposed service:

For each proposed service, the offeror shall specifically address the following items as applicable:

· Service and Functional Description: The offeror shall identify the proposed solution and define any proprietary technology.

· Standards: The offeror shall state that it will comply with all listed standards.

· Connectivity: The offeror shall state that it will comply with all listed connectivity instances with accompanying description as necessary.

· Technical Capabilities: The offeror shall clearly articulate how it proposes to meet or exceed each of the listed technical capabilities as specified for that service.

· Features: The offeror shall clearly articulate how it proposes to meet or exceed each of the listed technical capabilities as specified for that service.

· Interfaces: The offeror shall state that the proposed service is compatible with listed interfaces for that service.

· Performance Metrics: The offeror shall state that it will meet each of the listed Key Performance Indicators (KPIs) and if applicable identify where it will exceed the stated KPIs.

All mandatory services must be addressed. For optional services, the offeror must address all requirements listed as mandatory within each optional service.

Information Security The offeror shall address in the Risk Management Framework Plan how it will ensure the delivery of system security for the EIS services as specified in Section C.1.8.7. If MTIPS is proposed, the offeror shall identify how it will address system security (as specified in Section C.2.8.4.5) in its MTIPS Risk Management Framework Plan.

External Traffic Routing Requirement The offeror is not required to have established infrastructure supporting the National Policy requirements described in Section C.1.8.8 in order to respond to the EIS RFP. However, the offeror shall provide a detailed technical description of how it will accomplish the design, implementation, and operation of its aggregation service that addresses, at a minimum, the following items sufficiently to establish and demonstrate the technical viability of the offeror's aggregation service:

1. Methodology for identifying the offeror's participating agency traffic for each affected service.

2. Anticipated technical approach, for each affected service, to redirect all participating agency Internet, Extranet, and inter-agency traffic to DHS EINSTEIN Enclaves, receive processed traffic from GFP within the DHS EINSTEIN Enclave, and deliver traffic to its final destination. Descriptions shall include transport types and speeds, diversity, number of hops and delays per hop.

3. Technical approach to notify DHS if any non-participating agency traffic (IPv4, IPv6, etc.) will be redirected through DHS EINSTEIN Enclaves.

4. Control mechanisms the offeror will use to ensure that the identification and redirection of participating agency traffic cannot be inadvertently or maliciously by-passed.

5. Sensing and control mechanisms the offeror will use to ensure the redirection of traffic is failsafe (no disruption of participating agency services) should failures occur with DHS GFP.

6. Location of the offeror's existing or planned ANSI/TIA-942 and ICD 705 certified facilities that can serve as DHS EINSTEIN Enclaves capable of hosting DHS GFP at or near appropriate traffic-access locations.

7. Availability of TS/SCI-cleared personnel for "smart-hands" service of DHS-supplied equipment.

8. Instrumentation to measure transport SLA KPIs (as if traffic passes through loopbacks in EINSTEIN Enclaves with no impact within DHS GFP being counted against the offeror’s performance).

Technical Evaluation Matrices The offeror shall populate and identify the exact sections in the offeror’s proposal that address each of the proposed services by completing Vol 1, Vol 1a and Vol 1b in the EIS Submission Matrix workbook (see Section J.19).

Management Volume The offeror shall prepare its Management Volume response to address the management approach, techniques, and tools that the offeror will use to meet all requirements specified in Section G: Contract Administration Data, Section E: Inspection and Acceptance, and Section J.2 Contractor Data Interaction Plan.

The Management Volume of the proposal shall conform to the following.

Management Volume Response to include:

1. Management Response to requirements for Section G: Contract Administration Data

2. Management Response to requirements for Section E: Inspection and Acceptance

3. Management Response to requirements for Section J.2 Contractor Data Interaction Plan Management Volume Documents to be addressed separately:

· Program Management Plan (PMP)

· SCRM Plan

· Draft BSS Verification Test Plan (BSS Test Plan)

· EIS Services Verification Test Plan (EIS Test Plan)

· Climate Risk Management Plan

· Financial Status Report (Sample)

· BSS Risk Management Framework Plan

· NS/EP Functional Requirements Implementation Plan Management Response The offeror’s response shall:

1. Address the following requirements as specified in Section G: Contract Administration Data:

1. Describe the offeror’s approach and capability to provide user-friendly, compliant and efficient support systems, including: Ordering, Billing, Business Support Systems, Customer Support Office and Technical Support, Trouble Ticket Management, Inventory Management, Service Level Management, and Training.

1. Describe the offeror’s capability to provide customers with web-based access to support systems.

2. Describe the offeror’s capability to comply with the requirements in Section E: Inspection and Acceptance.

3. Describe the offeror’s capability to comply with Section J.2 Contractor Data Interaction Plan.

Management Volume Documents Program Management Plan (Section G.9.4) The offeror shall submit with its proposal a Program Management Plan (PMP) that details its program management method and implementation plan at a level sufficient to give the government an understanding of the program management approach. The PMP shall address, at a minimum, but is not limited to the following:

1. Summary of contract management requirements, including government dependencies and assumptions regarding government services, facilities, and personnel.

2. Summary description of service solution, including methodology to comply with Service Ordering, Billing, Inventory Management, and Service Management requirements.

3. Draft program management schedule.

4. Draft transition management approach; the offeror shall describe its approach to the project management of transition, including the offeror’s project management process, procedures, and tools to meet the transition requirements of Section C.3. The transition section shall address the following areas as well as additional areas proposed by the offeror:

1. Transition Project Management. The offeror shall address the billing, service ordering, trouble reporting, and customer service processes that are unique for transitioning onto EIS as well as transitioning off EIS, including specifically discussing how the offeror will expedite transition when it is also the incumbent service provider. The offeror shall describe how it will coordinate with other incumbent providers to ensure a smooth, successful, and timely transition. The offeror shall identify and assess the major transition risks and propose a response to each.

1. Agency Solicitations. The offeror shall describe its approach to assisting agencies with selecting new or enhanced services to replace services on expiring contracts. The offeror shall identify in the Transition Management Approachincentives, if any, it will offer agencies to expedite transition.

1. Customer Support During Transition. The offeror shall describe and provide an outline for any transition handbooks or guides it will make available to customers and indicate the target date for publication.

1. Interconnection Plan. The offeror shall describe the interconnection arrangements between the incumbent contractor’s network and the EIS networks during the transition, including the interconnection arrangements with local exchange carriers, the IXCs, and government private networks. The offeror shall describe any interconnections with other service providers, including other operating units within the offeror’s company, such as wholesale services known or expected to be required to transition services, and shall describe the potential impact to customers’ operations.

1. Transition Contingency Plan. The offeror shall describe how service will be restored if unforeseen difficulties are encountered at any stage of the transition.

5. Resource plan: providing a management approach to:

1. Financial Resources: budgeting, tracking, and controlling costs

1. Human Resources: identifying and retaining qualified personnel and making effective use of their skills

1. Equipment: managing hardware and software assets

6. Quality Control Program: Management approach to formulating and enforcing work and quality standards, ensuring compliance with contractual Service Level Agreements (SLAs), reviewing work in progress, and providing customer support services.

7. Key Personnel and Organizational Structure: Management structure, organizations, and roles and responsibilities of each component that performs work under the contract, and key personnel and corporate structure, as defined in Section H.10 Key Personnel and Corporate Structure.

8. Risk Management: Process for identifying program risks, including risks identified in the contract and actions to mitigate them.

9. Information Systems: Description of the BSS employed to implement the requirements of the contract consistent with security plans to prevent unauthorized access to the government’s data, or access by an agency to data belonging to any other agency. Describe how the offeror shall ensure those systems are available to meet the requirements of Business Support Systems (see Section G.5).

SCRM Plan The offeror shall include a SCRM Plan (see Section G.6.3) with its proposal that addresses counterfeit and illegally modified products. The SCRM plan shall describe the offeror’s approach to SCRM and demonstrate how the offeror’s approach will reduce and mitigate supply chain risks.

The offeror shall provide a SCRM plan to manage supply chain risk throughout each of the five (5) supply chain phases specified in its proposal:

1) Design and engineering

2) Manufacturing and assembly

3) Distribution and warehousing

4) Operations and support

5) Disposal and return.

In addition to the components and processes for which the offeror is directly responsible, and as feasible, the offeror shall identify “specified supporting infrastructure beyond the system boundary” and where appropriate, include such infrastructure in its SCRM Plan.

The SCRM Plan shall address at a minimum, but not be limited to, the following:

1. How the offeror ensures that requirements for genuine Information Technology Tools (ITT) are imposed upon its direct suppliers, whether the direct supplier is a systems integrator, reseller or OEM. The requirements for assurance and supporting evidence include:

1. The offeror performs reasonable steps to ensure its SCRM Plan is performed for ITT in its delivered and installed configuration.

1. Equipment resellers from whom the offeror purchases ITT have valid licenses for OEM equipment and software.

1. The ITT OEM exercises strict quality control to ensure that counterfeit or illegally modified hardware or software components are not incorporated into the OEM product.

1. The offeror ensures traceability of assurance and evidence of genuineness of ITT back to the licensed product and component OEMs.

2. The offeror’s use of system security engineering processes in specifying and designing a system that is protected against external threats and against hardware and software vulnerabilities.

3. The offeror’s strategy for implementing SCRM security requirements throughout the life of the contract. The SCRM plan shall address the security controls (at least SA-12) described in NIST Special Publication 800-53 Revision 4 or the latest publication. Implementation of the controls shall be tailored in scope to the effort and the specific information.

4. The criticality analysis (CA) process used by the offeror to determine Mission Critical Functions and the protection techniques (countermeasures and sub-countermeasures) used to achieve system protection and mission effectiveness. The CA shall describe the offeror’s supply chain for all critical hardware and software components (and material included in products), key suppliers, and include proof of company ownership and location (on-shore or off-shore) for key suppliers and component manufacturers.

5. How the offeror will ensure that products and components are not repaired and shipped as new products and components provided to the government.

6. How the offeror will ensure that supply channels are monitored for counterfeit products throughout the product life cycle to include maintenance and repair.

7. How the offeror’s physical and logical delivery mechanisms will protect against unauthorized access, exposure of system components, information misuse, unauthorized modification, or redirection.

8. How the offeror’s operational processes (during maintenance, upgrade, patching, element replacement, or other sustainment activities) and disposal processes will limit opportunities for knowledge exposure, data release, or system compromise.

9. Which of the following identifies the relationship between the offeror and the manufacturer: 1) OEM, 2) authorized reseller, 3) authorized partner/distributor, or 4) unknown/unidentified source.

10. The offeror’s expressed warranty that the software shall be free from all computer viruses, worms, time-outs, time bombs, back doors, disabling devices and other harmful or malicious code intended to or which may damage, disrupt, inconvenience or permit access to the software user's or another's software, hardware, networks, data or information. The government will only accept standard commerical warranties for Commerical-Off-the-Shelf (COTS) components if they are consistent with clause 52.246.17. In the case of standard commerical warranties that exceed one year, the government shall receive the additional term(s) of the commerical warranty.

11. How the offeror will ensure independent verification and validation of assurances, and provide supporting evidence as required.

The offeror shall incorporate the substance of this provision in subcontracts at all tiers where a subcontractor provides personnel, components, or processes identified as 1) a critical component, or 2) part of the offeror’s supporting infrastructure. All subcontractors providing critical components or services shall be identified and required to provide all necessary information to complete the SCRM Plan in association with the offeror. Suppliers of COTS components are considered subcontractors for the contract.

The offeror shall comply with NIST SP 800-161 Supply Chain Risk Management (SCRM) Practices. The offeror shall update its SCRM Plan to include any future changes to the NIST SCRM Guidelines and all such modifications to the Plan shall be made at no cost to the government. The offeror shall update its SCRM Plan to include any future changes to the NIST SCRM Guidelines and all such modifications shall be implemented at no cost to the government.

Draft BSS Verification Test Plan (Section E.2.1) The offeror shall provide a draft BSS Verification Test Plan (BSS Test Plan) in accordance with the test methodology for BSS defined in Section E.2.1. The offeror’s plan shall meet the following inspection and acceptance requirements:

1. The BSS testing shall verify that all BSS functional, regression, load, and security requirements have been successfully met. Note: regression testing applies only to system changes and not initial BSS development.

1 The BSS testing shall be performed for all management and operation functions supporting the Ordering, Billing, Inventory Management, Disputes, SLA Management and Trouble Ticketing processes that are described in Sections G.3 – G.8 and Section J.2.

2 Security testing shall be based on functional requirements described in Section G.5.6 BSS Security Requirements. Acceptance of the security requirements shall be based on evaluation for completeness.

3 The testing shall include the test cases defined in Section E.2.1.3 Test Cases.

4 The BSS testing shall include use cases for quality, utility and customer access features.

EIS Services Verification Test Plan (Section E.2.2) The offeror shall provide an EIS Services Verification Test Plan (EIS Test Plan) that describes their approach in accordance with the test methodology defined in Section E.2.2 (test scenarios, test cases, test data sets, and acceptance criteria) for each of the proposed EIS services.

Climate Risk Management Plan (Section G.12) In accordance with the requirements described in Section G.12, the offeror shall provide a Climate Risk Management Plan that demonstrates offeror’s compliance with the climate change adaptation conditions described in Executive Orders and other applicable laws, regulations, and directives.

Financial Status Report (Sample) (Section G.9.5) The offeror shall provide the format of its Financial Status Report (Sample) including the information required in Section G.9.5.

BSS Risk Management Framework Plan (G.5.6) The offeror shall identify how the Business Support Systems (BSS) Risk Management Framework Plan will address system security in accordance with Section G.5.6.

NS/EP Functional Requirements Implementation Plan (Sections G.11.1-G.11.3) The offeror shall show how the NS/EP Functional Requirements Implementation Plan will address the specifications identified in Sections G.11.1 – G.11.3.

Past Performance Volume The Past Performance Volume shall conform to the following.

Past Performance Response The offeror must submit three (3) past performance references on government or commercial projects reasonably similar in size and scope to the four mandatory services identified in Section C.1.2. Past performance for optional services will not be accepted.

Past performance must be the offeror’s direct history and past performance as a prime contractor for projects similar in size and scope to the four mandatory services. Past performance will also be accepted for contractors who have formed a “small business teaming arrangement” as defined in L.13 where all business are small under NAICS code 517110 or for other “prime” contractors who have formed a “contractor team arrangement” as defined in FAR 9.601 (1) where two or more companies form a partnership or joint venture to act as a potential prime contractor. The signed agreements must be provided to the CO as part of the proposal included in the Business Volume.

PLEASE NOTE: GSA WILL NOT accept experience of subcontractors or experience of “contractor team arrangements” as defined in FAR 9.601 (2) where a prime contractor agrees with one or more other companies to have them act as its subcontractor(s). Exception: Subcontractor past performance under a “small business teaming arrangement” where all business are small under NAICS code 517110 will be accepted.

The references must be for government or commercial work completed within the past three (3) years from the RFP release date. Work completed in the past three (3) years on an ongoing contract is acceptable, provided the offeror has performed for a minimum of one (1) year. Each reference is limited to two (2) pages in length.

For each reference, provide the following:

1. Customer/Agency name

1. Contract title

1. Contract or task order number

1. Total contract/project value

1. The percent of total contract/project work complete to date by the offeror

1. Contract/project start date and end date

1. Customer’s/CO’s name, address, email address and telephone number

1. Customer’s / Program Manager’s name, address, email address and telephone number

1. A description of the work performed by the offeror

1. Provide information on problems encountered on the identified contracts and the offeror’s corrective actions.

Business Volume The Business Volume shall conform to the following.

Standard Form 33 This form shall be signed by the offeror in accordance with the requirements in Section L.25.

Representations and Certifications The offeror shall submit Representations and Certifications in accordance with Section K.2.

Also, in accordance with K.2, the following information shall be provided for all prime contractors and subcontractors performing at least 10% of the contract revenue:

· Commercial and Government Entity (CAGE) number

· Dun and Bradstreet Data Universal Numbering System (DUNS) number

· Taxpayer Identification Number (TIN)

· Legal “doing business as” (DBA) name'

Small Business Teaming Arrangement / Contractor Teaming Arrangement Agreements (if applicable) The offeror shall submit the signed contractor teaming arrangement agreement as defined in FAR 9.601(1) or small business teaming or joint venture agreement as defined in Section L.12.

Proposal Amendment Acknowledgement The offeror shall acknowledge any proposal amendment in writing as part of the Business Volume and on block 14 of the SF33. Offerors shall acknowledge receipt of Amendment 05 and greater with an affirmative statement in its Business Volume.

Subcontracting Volume A small business concern is not required to submit an Individual Subcontracting Plan. For other than small business concerns, the offeror shall provide an Individual Subcontracting Plan.

The Subcontracting Volume shall conform to the following.

Subcontracting Plan and Subcontracting Participation If the offeror is a large business, it shall submit an individual subcontracting plan, specific to the EIS procurement in accordance with FAR 52.219-9, with consideration made to the GSA Subcontracting Target Goals as described in Table L.33.1.3. The RFP contains some non-commercial services, terms and conditions and therefore a commercial plan will not be accepted. An individual subcontracting plan shall be provided to the government at the time of proposal submission and is subject to negotiation by the CO. At award, the plan is included in the contract. Through the plan, the offeror shall:

1. Demonstrate compliance with requirements of FAR Subpart 52.219-9 and FAR Subpart 19.704.

2. Demonstrate commitment and capability to meet subcontracting target goals for participation of small business, veteran-owned small business, service-disabled veteran-owned small business, HUBZone small business, small disadvantaged business, and women-owned small business concerns as described in Table L.33.1.3.

3. Subcontracting goals are to be calculated based on total subcontracting dollars as required by FAR.

The General Services Administration Manual (GSAM), Appendix 519A-Small Business Subcontracting Plan Outline (Model) provides a model Subcontracting Plan as a template for…