DRAFT CP1 Addendum to 52.212-1.pdf

DRAFT GSP ADDENDUM 52.212-1, INSTRUCTIONS TO OFFERORS

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

SOLICITATION HT0015-22-R-0030

1. PROPOSAL INSTRUCTIONS

The following instructions are for the preparation and submission of proposals. The purpose of this section is to establish requirements for the format and content of proposals, so proposals contain all information essential for a thorough evaluation. Proposals that do not comply with the detailed instructions for the format and content of the proposal may render the Offeror ineligible for award.

The Government will evaluate proposals in accordance with the instructions and evaluation criteria set forth in the PROPOSAL INSTRUCTIONS and BASIS OF AWARD sections of this solicitation. The Government will not reimburse Offerors for any cost incurred for the preparation and submission of a proposal in response to this solicitation.

Offerors are instructed to read the entire solicitation document, including all attachments, prior to submitting questions and/or preparing a proposal. The electronic solicitation documents, as posted on http://www.sam.gov, will be the “official” documents for this solicitation. Omission of any information or items from the proposal submission requirements may result in rejection of the offer.

Multiple IDIQ contracts will result from this solicitation. Therefore, an Offeror (as identified in Block 17A of the SF1449) may only submit a single proposal for this solicitation. An Offeror found submitting more than one proposal will have ALL of its proposals disqualified and removed from further award consideration.

Cross-teaming or entities participating in more than one proposal (e.g., whether as an Offeror, proposed subcontractor, Joint Venture member) is prohibited under this solicitation. Offerors are solely responsible for ensuring that none of the entities proposed as a subcontractor or teaming partner under their proposals are also proposed or identified as a prime contractor, subcontractor, or partner in any other offeror’s proposal. If the Government identifies instances of prohibited cross-teaming, Offerors’ proposals will be rejected and not further evaluated.

1.1. Proposal Due Date and Submission Instructions

Offerors shall submit all volumes of their proposal electronically via the Procurement Integrated Enterprise Environment (PIEE) Solicitation Module at https://piee.eb.mil.

Offerors are advised that an active Proposal Manager role in the PIEE Solicitation Module is required to submit an offer in response to a solicitation posted in the PIEE Solicitation Module.

Point of Contact for Vendor Registration/Technical System issues – Email: disa.global.servicedesk.mbx.eb-ticket-requests@mail.mil Phone: 866-618-5988 / 801-605-7095 mailto:disa.global.servicedesk.mbx.eb-ticket-requests@mail.mil

To be considered for evaluation, the proposal shall be received (i.e., completely uploaded and time-stamped in the PIEE module) no later than the date and time (local time San Antonio, Texas) specified in Block 8, SF 1449. Offerors are cautioned to log into PIEE Solicitation Module within sufficient time to ensure the electronic proposal package is completely uploaded and time-stamped in the system by the due date and time specified for receipt of proposals. The PIEE Solicitation Module is the ONLY electronic commerce method authorized for the submission of proposals in response to this solicitation. Submissions received outside of the PIEE Solicitation Module will NOT be considered. Proposals received after the due date and time specified herein will be considered late.

1.2. Solicitation Questions Due Date

Offerors shall address all questions, clarifications, or concerns regarding this solicitation in writing to the Contracting Officer, Chris Rieper, christopher.d.rieper.civ@health.mil referencing solicitation number HT0015-22-R-0030.

Questions shall be submitted no later than XX October 2022 (local time San Antonio, Texas) using the GSP Questions Matrix Template at Attachment RFP3.

In the event of you believe you’ve identified a possible discrepancy in the solicitation (e.g., errors, omissions, or otherwise unclear or unsound), Offerors shall immediately notify the Contracting Officer in writing with supporting rationale.

Offerors are cautioned that no email shall be submitted exceeding 20MB due to limitations experienced by the Government email system with regard to reliably delivering/receiving emails larger than 20MB.

1.3. Proposal Content and Organization

It is the sole responsibility of the Offeror to ensure that the electronic files submitted are virus free and can be opened and read by the Government. All files shall be submitted compatible with Microsoft Office 2016 or Adobe Acrobat, as indicated. Proposal submissions shall not be locked, password protected, encrypted, or otherwise contain barriers to opening. Offeror’s proposals shall not contain classified data.

Each proposal shall consist of five Volumes, as follows:

Volume I - Administrative Volume II - Support Qualifications Volume III - Scope Area Qualifications Volume IV - Geographic Breadth Qualifications Volume V - Performance Validation mailto:christopher.d.rieper.civ@health.mil

Each Volume of the Offeror’s proposal shall include a cover file which includes a table of contents for that Volume, as well as a glossary of all abbreviations and acronyms used. The cover file shall clearly label the Offeror’s name, cage code, and Volume number. The cover file shall be prepared using a standard, 12-point Arial Font, double spaced, with 1” margins, and 8.5” x 11” page size. The file shall be converted to Adobe Portable Document Format (PDF) before submission.

Each cover file shall conform to the following file naming convention:

OFFEROR NAME COVER_FILE_VOL_>

“OFFEROR NAME” shall be replaced with name of Offeror submitting the proposal in response to this solicitation and shall be no longer than 25 characters.

“>” shall be replaced with the corresponding Volume number for which the cover file is being submitted.

All files for Volume I shall be converted and combined into a single PDF file prior to submission and shall conform to the following file naming convention:

OFFEROR NAME VOL_1

to this solicitation and shall be no longer than 25 characters.

1.4. GSP Technical Qualification Worksheet (Attachment RFP1)

For Volumes II-V, the Offeror will identify reference projects on the GSP Technical Qualification Worksheet (Attachment RFP1) in accordance with this section.

The Offeror shall submit the GSP Technical Qualification Worksheet (Attachment RFP1) in the electronic format provided in this solicitation (i.e., Microsoft Excel). No other format will be considered. The Offeror shall not alter rows, columns, font, or formulas in the file. The Offeror shall not copy and paste information from one cell into another. The GSP Technical Qualification Worksheet (Attachment RFP1) shall be submitted once and is not part of any particular Volume.

The GSP Technical Qualification Worksheet shall conform to the following file naming convention:

OFFEROR NAME GSP_QUAL_WKSHT

to this solicitation and shall be no longer than 25 characters.

The Offeror shall follow the instructions listed below when filling out the GSP Technical Qualification Worksheet:

• Enter the Offeror name in Row 1, Column B.

• For each qualification identified by the Offeror, the Offeror shall include the evidence file name, as described in 1.5 below, in the corresponding cell for which it is being submitted.

If no qualification is identified or no evidence is being submitted, the Offeror shall write “NOT APPLICABLE” in the corresponding cell. No cells should be blank.

• For each instance of evidence submitted, Offeror shall only include references to the location of the specific information which supports the identified qualification, such as page number and paragraph in the corresponding cell. If a reference is not used, Offeror shall include “NOT APPLICABLE” in the corresponding cell.

• Although there are no page count limitations, the Offeror shall align and narrow evidence to that which supports the identified qualification. It is essential the Offeror identifies specific page(s) and paragraph(s) (e.g., columns E, G, or I of the GSP Technical Qualification Worksheet (Attachment RFP1) within the evidence which substantiates the Offeror’s qualification. In the event that information in the GSP Technical Qualification Worksheet and the Offeror’s evidence conflict, the evidence submitted by the Offeror will be relied upon.

1.5. Evidence Naming and Restrictions

Each qualification identified shall be supported by evidence in the proposal. Evidence for each Reference Project shall be combined into one PDF and shall be submitted conforming to the following file naming conventions:

• For Support Qualifications in Volume II:

OFFEROR NAME SUPPORT_AREA_>_REF_<

• For Combined Scope Areas 1, 2, and 5 Qualifications in Volume III:

OFFEROR NAME COMBINED_SCOPE_AREAS

• For each Scope Areas 3, 4, 6, and 7 Qualifications in Volume III:

OFFEROR NAME SCOPE_AREA_>_REF_<

• For Geographic Breadth Qualifications in Volume IV:

OFFEROR NAME GEO_AREA_>_REF_<

• For Combined Scope Areas 1, 2, and 5 Performance Validation in Volume V:

OFFEROR NAME PV_COMBINED_SCOPE_AREAS

• For each Scope Areas 3, 4, 6, and 7 Performance Validation in Volume V:

OFFEROR NAME PV_SCOPE_AREA_>_REF_<

to this solicitation and shall be no longer than 25 characters. Abbreviated names may be used.

“>” shall be replaced with the corresponding Scope or Geographic Area for which evidence is being submitted.

“<” shall be replaced with the corresponding numbered reference (i.e., 1, 2, or 3) for the criteria starting with number 1 up to number 3.

Example:

Alpha Corp SUPPORT_AREA_1_REF_1.pdf

Bravo Co. COMBINED_SCOPE_AREAS.pdf

Charlie Inc PV_SCOPE_AREA_3_REF_2.pdf

Automatic file extensions are acceptable inclusions in the file name.

• Although there are no page count limitations, the Offeror shall align and narrow evidence to that which supports the identified qualification.

• Each qualification identified shall have its own evidence file. If the evidence is identical, duplicate files shall be submitted with each applicable qualification using the unique file name corresponding to the naming conventions above.

• All evidence shall be submitted in a searchable PDF file.

1.6. Definitions

The following definitions are established to provide clarity to aspects of proposals submitted in response to the GSP solicitation.

• DoD IT Services. Services implementing or supporting computers, electronic storage, networking or other physical devices, infrastructure or processes to create, process, store, secure or exchange all forms of electronic data in support of DoD missions.

• Evidence. Information sufficient to support the reasonable belief that a particular act has occurred and directly links to the entity for which a qualification is being identified. For Support Area, Scope Area, and Geographic Breadth Qualifications, the following are considered evidence: referenced project or contract award or execution document, including its Statement of Work (SOW)/PWS that cross references with Contract Line Item Numbers

(CLINs). For Performance Validation a Contractor Performance Assessment Report (CPAR) or Past Performance Questionnaire is considered evidence.

A MA IDIQ contract or MA IDIQ PWS is not an acceptable form of evidence.

• Offeror. The official legal offering entity identified in Block 17A on the Standard Form (SF)

1449, Solicitation/Contract/Order for Commercial Products and Commercial Services.

• Joint Venture. A cooperative business agreement or partnership between two or more parties that is usually limited to a single enterprise and that involves the sharing of resources, control, profits, and losses.

• Multiple Award (MA) Contract. For purposes of providing evidence under this solicitation, MA Contract means: (1) A Multiple Award Schedule (MAS) contract issued by General Services Administration (GSA) or agencies granted MAS contract authority by GSA as described in FAR part 38; (2) A multiple-award task-order or delivery-order contract issued in accordance with FAR subpart 16.5, including Governmentwide acquisition contracts; or

(3) Any other indefinite-delivery, indefinite-quantity contract entered into with two or more sources pursuant to the same solicitation. Examples include, but are not limited to, the following: GSA MAS, GSA Blanket Purchase Agreement (BPA), GSA MA contract, Government-Wide Acquisition Contracts (GWACs), National Institutes of Health’s CIO SP3, and Army Computer Hardware Enterprise Software and Solutions (CHESS).

• Prime. A contractor that has or has had privity of contract with public or private sector for all contractual obligations under a mutually binding legal agreement.

• Qualifying Offeror. Per FAR 2-101(b), an Offeror that (i) is determined to be a responsible source; (ii) submits a technically acceptable proposal that conforms to the requirements of the solicitation; and (iii) the contracting officer has no reason to believe would be likely to offer other than fair and reasonable pricing under future Task Order(s).

• Recent. For the purpose of this solicitation, the term “Recent” when referring to a “recent” project or “recent” prior contract to be identified and submitted by Offerors means a project or contract with any contract performance having occurred within the three (3) years prior to the closing date of this solicitation.

• Subcontractor. Any supplier, distributor, vendor, or firm that furnished supplies or services to or for a prime contractor or another subcontractor. Subcontractor means an individual or business firm contracting to perform part or all of another's contract.

• Referenced Project or Prior Contract. Unless otherwise specified, any of the following: (1) a single contract or subcontract; (2) a single Task Order awarded under a Multiple Award contract (as defined above); (3) a single Task Order awarded under a Single-Award

Indefinite Delivery Task Order contract (FAR 16.5); (4) a single Task Order placed under a Federal Supply Schedule contract (FAR 8.405-2); or (5) a single Task Order placed under a Blanket Purchase Agreement (BPA) (FAR 8.405-3).

Unless otherwise specified, a Joint Venture member’s performance on one of the above as part of a Joint Venture is also considered a referenced project.

A referenced project may be one in either the public or private sectors with the exception of Support Area 3 in Volume II.

1.7. Volume I – Administrative

1.7.1. Representations and Certifications

Offerors shall have completed all representations and certifications for each proposed team member (see 1.7.2 and 1.7.3) in the Online Representations and Certifications at the System for Award Management (SAM) https://www.sam.gov/portal/public/SAM.

1.7.2. Joint Ventures, if applicable

Offerors submitting as a Joint Venture may submit a proposal under this solicitation subject to the following conditions:

• The Joint Venture is registered in SAM.gov and has a corresponding Unique Entity

Identification (UEI).

• The Joint Venture meets the definition of a Joint Venture for size determination purposes (13 C.F.R. 125.8).

• The Offeror shall submit a complete copy of the Joint Venture agreement that established the relationship, and the agreement shall meet the requirements of FAR 52.207-6, 13 C.F.R.125.8 and/or 13 C.F.R. 125.9, as applicable. Failure to submit a copy of the Joint Venture agreement with the proposal meeting these requirements will result in the proposal being rejected. DHA is not obligated to acquire this information for an Offeror.

A Joint Venture shall complete its annual representations and certifications electronically within SAM.gov.

1.7.3. Proposed Subcontractors, if applicable

An Offeror may establish agreements with one or more other companies to have them act as its subcontractor(s). Offerors submitting a proposal that includes proposed subcontractor(s) may submit a proposal under this solicitation subject to the following conditions.

• The Prime contractor and all proposed subcontractors shall be registered in SAM.gov and have a corresponding UEI.

• Each proposed subcontractor shall also have completed the Online Representations and Certifications at the System for Award Management (SAM) https://www.sam.gov/portal/public/SAM.

• The Prime contractor shall submit a Subcontractor Letter of Commitment for all proposed subcontractors. The Government has the right to accept those letters of commitment at face value. The information identified below is required for all Subcontractor Letter(s) of Commitment to be deemed conforming, and no other information contained therein will be considered:

o Offeror’s legal name and UEI (SAM).

o Proposed subcontractor’s legal name and UEI (SAM).

o Name, phone number, and email address of the proposed subcontractor’s representative able to validate the letter’s content.

o Signature of representative with the authority to bind the proposed subcontractor.

o A statement of commitment by the proposed subcontractor to support the Offeror in performance of GSP Task Orders.

o A statement by the proposed subcontractor authorizing use of its qualifications in support of the Offeror’s GSP proposal, as applicable, including the specific Referenced Project(s).

o A statement of understanding that on the resulting GSP MA IDIQ, a small business concern contracting for services will not pay more than 50 percent of the amount paid by the Government for contract performance to subcontractors that are not similarly situated entities, as defined in FAR clause 52.219-14 Limitations on Subcontracting. Any work that a similarly situated entity further subcontracts will count towards the Prime contractor’s 50 percent subcontract amount that cannot be exceeded. When a contract includes both services and supplies, the 50 percent limitation will apply only to the service portion of the contract.

Identification of proposed subcontractors does not result in Government consent of them for any particular Task Order; rather it addresses this solicitation requirement for the solicitation only.

Consenting to specific subcontractors may be required on individual Task Orders when required IAW FAR Subpart 44.2, Consent to Subcontracts.

1.7.4. Organizational Conflicts of Interest Mitigation Plan

The Offeror shall submit for itself and from any and all subcontractors or members of the Joint Venture, the following:

o Offeror or subcontractor legal name and UEI.

o Name, phone number, email address, and signature of Offeror or subcontractor representative able to certify on its behalf.

o A completed OCI mitigation plan along with the OCI Mitigation Plan Checklist

(Attachment GSP3).

1.7.5. Past Performance Consent Letters

Past Performance information concerning subcontractors and teaming partners cannot be disclosed to a private party without the subcontractor’s or teaming partner’s consent. Offerors shall have each of their subcontractors and teaming partners complete a teaming partner consent for each subcontractor or teaming partner which the Offeror is using to identify qualifications in the GSP Technical Qualification Worksheet (Attachment RFP1) and submit it as part of its proposal in Volume I. Consent letters shall include the following information:

o Offeror’s legal name and UEI (SAM).

o Proposed subcontractor’s legal name and UEI (SAM).

o Name, phone number, and email address of the proposed subcontractor’s representative able to validate the letter’s content.

o Signature of representative with the authority to bind the proposed subcontractor.

o A statement by the proposed subcontractor indicating permission to discuss its past and present performance information, which is being used as part of the Offeror’s proposal, with the Offeror during the source selection process.

1.7.6. Responsibility Determination

The determination that an Offeror, including all parties of a Joint Venture, is a “responsible source” will be made by the Contracting Officer in accordance with FAR 9.104.

The Government will use all information submitted in the Offeror’s proposal as well as any other information the Government obtains from its information system(s) and other legitimate sources of information to arrive at this determination.

1.7.7. Fair and Reasonable Pricing Determination

The determination that “the contracting officer has no reason to believe the Offeror would likely offer other than fair and reasonable pricing” will be made based on the Government’s review of information submitted in the Offeror’s proposal as well as any other information the Government obtains from its information system(s) or other legitimate sources of information which would indicate the contrary or give cause for concern, including the following which shall be submitted as part of the Offeror’s proposal:

• A timely submitted and signed certification stating that the Offeror follows generally accepted accounting practices and has not knowingly submitted cost or pricing data which were incomplete, inaccurate, or not current to the Government over the past three years.

• Any (if applicable) Forward Pricing Rate Agreement (FPRA), Forward Pricing Rate Recommendation (FPRR), and any Defense Contract Audit Agency (DCAA) audits regarding the Offeror’s accounting system, including, but not limited to an audit documenting that the Offeror has a DCAA approved accounting system.

• The Offeror’s representations and certifications

1.7.1. Volume II – Support Qualifications

The Offeror will be evaluated on its Support Qualifications based on the criteria identified on the GSP Technical Qualification Worksheet (Attachment RFP1) and corresponding evidence submitted. The Offeror shall ensure the evidence corresponding to criteria identified are accurate, complete, and comply with the instructions herein.

1.7.1.1. Support Area 1: Performance as a Prime Contractor Managing Multiple Subcontractors

To substantiate qualifications for acceptable Performance as a Prime contractor managing multiple subcontractors, evidence submitted shall include:

• Up to three (3) recent, referenced projects.

The evidence shall include either one (1) referenced project as a Prime contractor with two (2) or more subcontractors simultaneously, or up to three (3) referenced projects as a Prime contractor each with one (1) or more subcontractors performing simultaneously.

If only one referenced project is submitted it shall come from the small business prime or a small business Joint Venture member. If two reference projects are submitted, they shall both come from the small business prime or a small business Joint Venture member. If three reference projects are submitted, at least two shall come from the small business prime or a small business Joint Venture member.

1.7.1.2. Support Area 2: Supplier Performance Risk System

To substantiate qualifications for Supplier Performance Risk System (SPRS) of PIEE, evidence submitted shall include:

• Assessment for the Prime or joint venture, or an assessment for each individual member of the joint venture demonstrating compliance with DFARS clause 252.204-7012, which implements NIST SP 800-171.

• The certification(s) shall be a screen shot from the SPRS indicating the assessment has been submitted.

1.7.1.3. Support Area 3: Competitively Awarded Order(s) under a Multiple Award Contract for DoD IT Services

To substantiate qualifications for IT Support provided to DoD under a Multiple Award Contract, evidence submitted shall include:

• Up to two (2) recent, referenced projects.

• Referenced project(s) shall be for competitively awarded orders against Multiple Award Contract(s), and be for any DoD IT Services.

• At least one referenced project shall come from the small business prime or a small business Joint Venture member.

• The referenced projects shall collectively have an obligated or funded value exceeding $30 million total or $10 million in any one year.

1.7.1.4. Support Area 4: Facility Clearance

To substantiate qualifications for Facility Clearance, evidence submitted shall include:

• A certification for the Prime or Joint Venture, or a certification for each individual member of the Joint Venture.

• The certification(s) shall indicate a Secret or higher facility clearance level and state the following:

o [Offeror name] certifies it currently possesses an active DoD facility clearance at the [level] and is in good standing with the Defense Counterintelligence and Security Agency (DCSA).

• Contact information of company Facility Security Officer (FSO) to include:

o Name.

o Title.

o Phone number.

o Email address.

o Physical address.

• Contact information of Government Industrial Security Representative (ISR) to include:

o Name.

o Title.

o Phone number.

o Email address.

o Physical address.

1.7.2. Volume III – Scope Area Qualifications

The Offeror will be evaluated on its Scope Area Qualifications based on the criteria identified on the GSP Technical Qualification Worksheet (Attachment RFP1) and corresponding evidence submitted. The Offeror shall ensure the evidence corresponding to criteria identified are accurate, complete, and comply with the instructions herein.

Referenced projects may be used to substantiate qualifications in more than one Scope Area, however they shall be submitted separately for each Scope Area being identified by the Offeror.

The Government will not evaluate or apply evidence submitted for one Scope Area for another Scope Area.

NOTE: Scope Areas 8 and 9 are not included in the list of required scope areas, and therefore do not need to be addressed by Offerors in Volume III. Qualifications related to Scope Areas 8 and 9 will not be considered in evaluating technical acceptability.

1.7.2.1. Combined Scope Areas 1, 2, and 5

Offerors shall submit at least one (1), but no more than two (2), recent referenced project(s) to substantiate qualifications related to combined Scope Areas 1, 2, and 5 Qualifications. At least one referenced project shall come from the small business prime or a small business Joint Venture member. Evidence submitted shall collectively address all the following qualifications listed under each of the three scope areas below:

• Scope Area 1: IT Service Desk o Manage tickets (e.g., incidents, cases, and requests, in an integrated enterprise level help desk).

o Answers IT support calls and responds to questions.

o Contains Local site knowledge bases.

o Trains help desk staff.

o Management of service catalog entries.

o Direct calls that do not belong to the site back to the correct site, queue, or enterprise help desk or both.

o Manage the IT Help Desk queue and complete work orders.

o Support local assets, new technology acquisition, and life cycle management, including inventory management and disposal IAW customer requirements, or supporting agency guidance for desktops, laptops, tablets, printers and other IT hardware.

• Scope Area 2: Database, Application, and Web Development o Maintain Databases to meet the Service Levels Agreements (SLA) or Operational Level Agreements (OLA) and other performance standards, to maximize efficiency, and minimize outages.

o Create and maintain website or applications using platforms including each of the following: SharePoint, ASP, .NET, and JAVA platforms, and while doing so, follow process definition, certification, validation and verification, architecture and reengineering, scripting, security and configuration management.

o Apply, implement, document and gain approval for application Security Technical Implementation Guidelines (STIGs).

o Support the entire Software Development Life Cycle (SDLC), e.g., process definition, requirements, management, project planning, quality assurance, metrics, testing, certification, validation and verification, architecture and reengineering, security and configuration management.

o Have working knowledge of the software development methodologies, including the use of any of the following: Agile, sprints, or stories.

• Scope Area 5: Information Assurance o Information Assurance compliance, documentation, authorization, certification, validation, verification, assessment, testing, evaluation IAW the DoD Risk Management Framework (RMF) guidelines, and HIPAA laws in order to obtain an Authorization to Operate (ATO).

o Apply DISA Security Technical Implementation Guideline (STIG) and Security Requirements Guides (SRGs) against the site assets and document STIG / Security Requirements Guide SRG compliance.

o Update and document customer enclave artifacts in Enterprise Mission Assurance Support Service (eMASS).

o Conduct Cybersecurity threat monitoring, risk identification, incident mitigation, and administration.

1.7.2.2. Scope Area 3: Identity Management and Desktop Support

Offerors shall submit at least one (1), but no more than three (3), recent referenced projects to substantiate qualifications related to combined Scope Area 3 Qualifications. At least one referenced project shall come from the small business prime or a small business Joint Venture member. Evidence submitted shall collectively address all the following qualifications:

o Active Directory (AD) management, including hosting services, sustainment, and management of the costumer associated AD Organizational Units (OU), user accounts, and systems.

o Manage, monitor, patch, upgrade, and ensure Information Assurance Vulnerability Assessment (IAVA) compliance of hardware site AD domain controllers as well as other AD associated resources and hardware using, including each of the following:

Microsoft Endpoint Configuration Manager (MECM), Splunk, and Tanium.

1.7.2.3. Scope Area 4: Data Center Operations

substantiate qualifications related to combined Scope Area 4 Qualifications. At least one o On-site Data Center/server room storage, back-up and data restoration, recovery, capacity planning, utilization monitoring, performance monitoring, disruptions, changes, service-level compliance, operational improvement, service reports, annual planning, annual evaluations, life cycle management, and physical security control.

o Monitoring the data center environment, e.g., HVAC system, fires suppression, uninterrupted power supply, generator, security access control.

1.7.2.4. Scope Area 6: Network Operations

substantiate qualifications related to combined Scope Area 6 Qualifications. At least one o Install, relocate, configure, update, test, or manage network devices (e.g., routers, switches).

o Create, maintain and manage Virtual Local Area Networks (VLANs) o Assist with the establishment and implementation of network policies, procedures and standards to include network security.

o Collect and report network performance measurement information, (e.g., LAN, circuit bandwidth).

o Develop, plan, and maintain network topology documentation.

1.7.2.5. Scope Area 7: Telecommunications

substantiate qualifications related to combined Scope Area 7 Qualifications. At least one o Operate and maintain site telecommunications systems (e.g., PBX, voicemail, VOIP, automated call distribution (ACD)), including any of the following activities:

additions, moves, and changes.

o Support installs, moves, changes, or operation of telecommunication devices, including any of the following: video teleconference systems, telephones, handsets, headsets, and analog lines.

1.7.3. Volume IV – Geographic Breadth Qualifications

The Offeror will be evaluated on its Geographic Breadth Qualifications based on the criteria identified on the GSP Technical Qualification Worksheet (Attachment RFP1) and corresponding evidence submitted. The Offeror shall ensure the evidence corresponding to criteria identified are accurate, complete, and comply with the instructions herein.

To substantiate Geographic Breadth Qualifications, evidence submitted may include up to two

(2) recent referenced projects per Geographic Area. A single referenced project may be used to substantiate qualifications in more than one Geographic Area, however that referenced project shall be submitted separately for each of the various Geographic Areas being identified by the Offeror.

Evidence submitted for each Geographic Area shall collectively address all the following Geographic Area qualifications.

1.7.3.1. Geographic Area 1: OCONUS, plus SOFA and/or DOCPER System

Offerors shall submit at least one (1), but no more than two (2), recent referenced projects to substantiate qualifications related to performing relevant services Outside the Continental United States (OCONUS). At least one referenced project shall come from the small business prime or a small business Joint Venture member. Evidence submitted shall collectively address all the following qualifications:

o Services performed relate to at least one (1) of the GSP Scope Areas, as described in the GSP PWS.

o Services were performed in one (1) or more of the following countries: Germany, Spain, Italy, United Kingdom, Turkey, Japan (including Okinawa Islands), or Korea.

o Services performed included experience staffing personnel in a country where SOFA status was granted and/or personnel processed through the DOCPER system.

1.7.3.2. Geographic Area 2: Northwest

Offerors shall submit at least one (1), but no more than two (2), recent referenced projects to substantiate qualifications related to performing relevant services in the Northwest Geographic Area. At least one referenced project shall come from the small business prime or a small business Joint Venture member. Evidence submitted shall collectively address all the following qualifications:

o Services were performed in at least two (2) of the following states: Washington, Oregon, Idaho, Montana, Wyoming, Utah, Colorado, Kansas, Nebraska, South Dakota, or North Dakota.

1.7.3.3. Geographic Area 3: National Capital Region

substantiate qualifications related to performing relevant services in the National Capital Region Geographic Area. At least one referenced project shall come from the small business prime, small business Join At least one referenced project shall come from the small business prime or a small business Joint Venture member. Evidence submitted shall collectively address all the following qualifications:

o Services were performed in at least two (2) of the following areas:

the District of Columbia, Montgomery, Prince Georges, Anne Arundel, Frederick, or Charles counties in Maryland, and/or Arlington, Fairfax, Loudon, Prince William, or King George counties in

Virginia.

1.7.3.4. Geographic Area 4: Southwest

substantiate qualifications related to performing relevant services in the Southwest Geographic Area. At least one referenced project shall come from the small business prime or a small o Services were performed in at least two (2) of the following states: California, Nevada, Arizona, New Mexico, Texas, or Oklahoma.

1.7.3.5. Geographic Area 5: Northeast

substantiate qualifications related to performing relevant services in the Northeast Geographic Area. At least one referenced project shall come from the small business prime or a small o Services were performed in at least two (2) of the following states: Minnesota, Wisconsin, Iowa, Illinois, Missouri, Indiana, Michigan, Ohio, Kentucky, West Virginia, Virginia, Pennsylvania, Maryland, Delaware, New Jersey, Rhode Island, Connecticut, Massachusetts, New York, Vermont, New Hampshire, or Maine.

1.7.3.6. Geographic Area 6: Southeast

substantiate qualifications related to performing relevant services in the Southeast Geographic Area. At least one referenced project shall come from the small business prime or a small o Services were performed in at least two (2) of the following states: Arkansas, Louisiana, Mississippi, Tennessee, Alabama, Georgia, South Carolina, North Carolina, or Florida.

1.7.4. Volume V – Performance Validation

The Offeror will be evaluated on its Performance Validation based on the criteria identified on the GSP Technical Qualification Worksheet (Attachment RFP1) and corresponding evidence submitted. Each qualification identified shall have its own evidence file. If the evidence is identical, duplicate files shall be submitted with each applicable qualification.

For Volume V, the Offeror shall submit the most recent completed CPARS report for each referenced project identified by the Offeror in its proposal’s Volume III, Scope Areas Qualifications. If no completed CPARS report exists for a referenced project, the Offeror shall instead submit a completed Past Performance Questionnaire, using the template provided at Attachment RFP2. A Past Performance Questionnaire (Attachment RFP2) is considered completed when all areas of the Past Performance Questionnaire (Attachment RFP2) are filled in, the questionnaire is signed, and converted to a PDF document by the customer point of contact completing the questionnaire. Only one CPARS or Past Performance Questionnaire (Attachment RFP2) will be accepted for each referenced project for each Scope Area.

Referenced projects submitted in Volume V for Performance Validation shall be the same Referenced projects as submitted in Volume III for Scope Area Qualifications and correspond to the same scope area being identified in both volumes. The Offeror shall ensure the evidence corresponding to criteria identified are accurate, complete, and comply with the instructions herein.

The CPARS or Past Performance Questionnaire (Attachment RFP2) shall indicate Satisfactory or higher performance level in the following categories: Quality, Schedule, and Management. The Government will only consider final Past Performance ratings that are Satisfactory or above to be technically acceptable.

In the event that neither a completed CPARS nor Past Performance Questionnaire is submitted for a particular referenced project, the proposal will be considered not qualified. The Government is under no obligation to locate or retrieve any past performance not specifically provided with the proposal. It is, therefore, the Offeror’s sole responsibility to request and/or ensure completed CPARS and/or Past Performance Questionnaire are received.

1.8. Likelihood of Offering Other than Fair & Reasonable Pricing for Future Task Orders

Also as part of Volume I, the Offeror shall submit the following information:

• A timely submitted and signed certification stating that the Offeror follows generally accepted accounting practices and has not knowingly submitted cost or pricing data which were incomplete, inaccurate, or not current to the Government over the past three years.

• Any (if applicable) FPRA, FPRR, and any DCAA audits regarding the Offeror’s accounting system, including, but not limited to an audit documenting that the Offeror has a DCAA approved accounting system.

The Government will additionally assess information on an Offeror (including proposed team members) to determine if any information provides a reason to believe, or significant cause for concern, that the Offeror would likely offer other than fair and reasonable pricing when competing for future Task Orders under this solicitation. This assessment will be made based on the Government’s review of the information to be provided directly above and other information submitted by the Offeror in its proposal, including representations and certifications. The Government reserves the right to also review any other relevant information it may separately obtain from its information system(s) or other legitimate sources of information if deemed necessary.