AMD_0003_Atch_8_Section_L_.pdf

FA8730-19-R-0005 0003, Attachment 8, Page 1

ATTACHMENT 8

INSTRUCTIONS, CONDITIONS, AND NOTICES TO

OFFERORS

INSTRUCTIONS FOR PROPOSAL PREPARATION (IFPP)

SECTION L

FOR

FORCE PROTECTION SITE SECURITY SYSTEM SOLUTIONS

(FPS4)

30 JULY 2019

FA8730-19-R-0005 0003, Attachment 8, Page 2

REVISION HISTORY

Revision Number

Date Description Sections

Affected

FA8730-19-R-0005 0003, Attachment 8, Page 3

TABLE OF CONTENTS

Section Page

1.0 PROGRAM STRUCTURE AND OBJECTIVES

1.1 Budget/Funding Information

2.0 GENERAL INSTRUCTIONS

2.1 General Information

2.1.1 Point of Contact

2.1.2 Debriefings

2.1.3 Discrepancies

2.1.4 Restricted Access Documentation

2.1.5 Notifications to Offerors/Organizational Conflict of Interest (OCI)

2.1.6 Classified Information

2.2 Organization

2.2.1 Page Limitations

2.2.2 Page Size and Format

2.2.3 Indexing

2.2.4 Glossary of Abbreviations and Acronyms

2.2.5 Binding and Labeling

2.2.6 Electronic Offers

2.2.7 Distribution

3.0 VOLUME I - EXECUTIVE SUMMARY INSTRUCTIONS

4.0 VOLUME II – TECHNICAL INSTRUCTIONS

4.1 General

4.2 Format and Specific Content

4.3 Table of Contents

4.4 Technical Volume

4.4.1 Design/Install Approach

4.4.2 Verification Approach

4.4.3 Interim Contractor Support Approach

4.4.4 Attachments to the Sample Problem

FA8730-19-R-0005 0003, Attachment 8, Page 4

TABLE OF CONTENTS (Cont.)

Section Page

5.0 VOLUME III - CONTRACT DOCUMENTATION

5.1 Model Contract/Representations and Certifications

5.1.1 Section A - Solicitation/Contract Form

5.1.2 Section F - Deliveries or Performance

5.1.3 Section G - Contract Administrative Data

5.1.4 Section H - Special Contract Requirements

5.1.5 Section I - Contract Clauses

5.1.6 Section J - List of Attachments

5.1.7 Section K - Representations, Certifications, and other Statements of Offerors

5.2 Other Information Required

5.2.1 Authorized Contractor Personnel

5.2.2 Government Offices

5.2.3 Company/Division Address, Identifying Codes, and Applicable Designations

5.2.4 Small Business Subcontracting Plan

5.2.5 Organizational Conflict of Interest Statement and/or Mitigation Plan

LIST OF ATTACHMENTS

Attachment L-1 Sample Problem Instructions Attachment L-2 Sample Problem Drawing List Attachment L-3 Sample Problem Labor Categories & Qualifications Attachment L-4 Sample Problem Proposal/Contract Work Breakdown Structure & Dictionary… Attachment L-5 Sample Problem Contract Data Requirements List (CDRL) A023 - Cybersecurity

Assurance Architecture Drawings…………………………………………………..45 Attachment L-6 Acronym Listing…………………………………………………………………

FA8730-19-R-0005 0003, Attachment 8, Page 5

1.0 PROGRAM STRUCTURE AND OBJECTIVES

The contract vehicles for the Force Protection Site Security System Solutions (FPS4) program are multiple awards of Indefinite Delivery/Indefinite Quantity (IDIQ) contracts with five (5) year ordering periods (with performance period extending an additional three years) utilizing Firm-Fixed-Price (FFP), Fixed Price Incentive Fee (FPIF), Cost-Plus-Fixed-Fee (CPFF), Cost Plus Incentive Fee (CPIF), Cost Reimbursement (CR), and Time & Material (T&M) contract types.

A task order will be awarded to each FPS4 awardee upon execution of the IDIQ contract for a Post Award Conference in the amount of $2,500. The Post Award Conference will be accomplished under CLIN 0001, which is a firm fixed price CLIN. This task order will satisfy the minimum ordering requirement of AFFARS MP 5316.504(a)(2).

The FPS4 contract provides for acquisition of physical and electronic security systems (ESS) including but not limited to Intrusion Detection Systems (IDS), Access Control Systems (ACS), tactical security systems; delay/denial systems and Counter-small Unmanned Aerial Systems (C-sUAS). These systems provide physical and electronic capabilities to support and enhance site security and assist security forces in protecting assets and personnel at fixed and/or tactical sites around the world. The ultimate goal of the FPS4 contract is to provide security forces with the capability to “See First, Understand First, and Act First.” In short, through this contract, users will be provided with integrated systems and equipment, tailored to specific user needs, which provide physical and electronic means to assist security forces in protecting personnel, assets, and facilities worldwide. Systems capabilities include fixed and tactical area intrusion detection; access control; automated entry control; alarm reporting and display; remote alarm assessment; area surveillance; delay/denial capabilities; C-sUAS capabilities; and alerting security response forces to intrusions. Additionally, systems provide an integrated command and control capability, permitting situational awareness reporting and warning information to be rapidly and accurately passed among security and force protection communities. Finally, associated capabilities to these systems such as fencing, lighting, power, ground communications systems, and other infrastructure improvements are nearly always required as part of FPS4 Delivery Orders (DOs) and often represent a significant portion of the work on these projects.

The contract provides associated project support including but not limited to program management, systems engineering, repair of contractor-furnished equipment and Government Furnished Property (GFP), test/verification, training, sustainment (e.g., interim contractor support and/or contractor logistics support).

The contract also provides special studies and analyses, and qualification and acceptance testing of Commercial off-the-Shelf (COTS) equipment when ordered. It includes acquisition of security systems to support Department of Energy (DoE), Department of State (DoS), other Department of Defense (DoD) and Federal Government customers, and Foreign Military Sales (FMS) customers.

Certain ESS (primarily IDS) equipment acquired under FPS4 DOs will consist of either (1) already proven COTS equipment from the Air Force Security Forces Center (AFSFC) Intrusion Detection System Equipment List (IDSEL), (hereafter referred to as the “Intrusion Detection System Equipment List” [IDSEL]); or (2) non-IDSEL COTS equipment proposed by the offerors (or otherwise specifically required by the Government as part of a DO solicitation). If non-IDSEL COTS equipment falls into categories established in the IDSEL, and is part of a FPS4 IDIQ contractor’s proposal to satisfy subsequent DO requirements, then this equipment will be evaluated during the DO technical evaluations as part of the offeror’s proposed solution.

Tactical security equipment purchases will be Government Off-the-Shelf (GOTS) equipment.

However, delay/denial system upgrades/modifications (if ordered) may require use of either COTS and/or new development items as Government requirements (identified at the time of DO solicitation) may demand.

FA8730-19-R-0005 0003, Attachment 8, Page 6

C-sUAS projects on the FPS4 contract will involve integrating and installing C-sUAS Government Furnished Equipment (GFE) into the Government-provided C-sUAS Command, Control and Display Equipment (CCDE), as well as providing the necessary infrastructure to accomplish this integration and installation work.

Installation, support operations and maintenance, procurement, and major upgrade requirements may require performance of multiple installations at different locations in parallel, and/or quick reaction support to sites around the world. Funding for FPS4 requirements may include multiple Air Force (AF) appropriations (e.g., 3600, 3080, 3400) or other DoD and Federal Agency appropriations and FMS funding as applicable.

1.1 Budget/Funding Information

For Industry’s consideration in determining whether to submit a proposal for the FPS4 IDIQ contract, the projected program/budget funding across the five-year FPS4 period of performance is as follows:

TABLE 1. FPS4 Anticipated Funding

TYPE PROJECTED AMOUNT

Air Force Fixed Site and Nuclear Projects $513M

Outside of the Continental United States (OCONUS)/Continental United States (CONUS) Sustainment and Operational Readiness Support Activities, Equipment Buys & Foreign Military Sales Projects

$142M

C-sUAS & Other Agency Projects $128M

TOTAL $783M

2.0 GENERAL INSTRUCTIONS

a. This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the offeror’s proposal. An offeror is defined as a prime contractor. The offeror’s proposal must include all data and information requested and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Request for Proposal (RFP) including the Model Contract, and all Exhibits and Attachments 1-8, and all attachments to these Instructions For Proposal Preparation (IFPP), which includes supplemental instructions contained herein. Non-conformance with these IFPP instructions and/or submittal of an incomplete package may result in an offer being considered non-responsive and/or unfavorably evaluated.

b. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. The offeror shall assume that the Government has no prior knowledge of the offeror’s facilities and experience, and will base its evaluation on the information presented in the offeror’s proposal.

c. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

FA8730-19-R-0005 0003, Attachment 8, Page 7

d. The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

e. In-depth drawings required for sample problem completion have been provided with the RFP posting on FedBizOps. All drawings have been provided in Adobe Acrobat and Visio formats. A complete list of provided drawings are included in Attachment L-2 of this document. This posting does not include restricted-access documents and regulations. Instructions for obtaining this information are provided in Section 2.1.4 of this document.

2.1 General Information

2.1.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the model contract/solicitation.

2.1.2 Debriefings

Unsuccessful offerors may request and receive a debriefing in accordance with FAR 15.505.

Offeror’s desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.1.3 Discrepancies

If an offeror believes that the requirements in these instructions or the RFP contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale.

The offeror is reminded that the Government reserves the right and intends to award this effort based on the initial proposal, as received, without discussion.

2.1.4 Restricted Access Documentation

There will be restricted access reference and technical data, supporting documents, announcements and information for offerors that can be accessed via submission of completed authorization forms (titled “FPS4BidderLibraryRequestForm.pdf”) found on the FedBizOps site at https://www.fbo.gov/ under the FPS4 posting. Once the Government has verified the offeror’s submission and approved the offeror to access the documentation, the Government will distribute the documentation to the offeror via AMRDEC SAFE transmission.

2.1.5 Notification to Offerors/Organizational Conflict of Interest (OCI)

The following companies may be used to support the evaluation of the submitted proposal in a purely advisory role:

Oasis Systems, LLC

24 Hartwell Avenue Lexington, MA 02421

MAINSAIL Group, Inc. (MAINSAIL Boston)

200 Hanscom Drive, Suite 121 Bedford, MA 01730

MCR, LLC 2010 Corporate Ridge #350 McLean, VA 22102 https://www.fbo.gov/

FA8730-19-R-0005 0003, Attachment 8, Page 8

PCI Strategic Management 6811 Benjamin Franklin Dr., Suite 200 Columbia, MD 21046

Torch Technologies, Inc. 4090 South Memorial Parkway Huntsville, AL 35802

Quantech Services, Inc. 91 Hartwell Ave, 3rd Floor

Lexington, MA 02421

If your quote in any way involves any of the above companies, notify the CO immediately and please submit an OCI Mitigation Plan.

2.1.6 Classified Information

Proposals must not include classified information.

2.2 Organization

The offeror shall prepare the proposal as set forth in the Proposal Organization Table 2 below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The attachments for volumes shall be properly marked and included within the same three-ring binder with its respective volume. The contents of each proposal volume are described in the IFPP paragraphs as noted in the table below. In cases where the hard copy and the electronic copy conflict, the hard copy will take precedence.

TABLE 2. Proposal Organization

Volume

Atch)

IFPP

Paragraph

No.

Volume Title Hard Copies (Including one original)

Electr onic

Copies

Page Limit

I 3.0 Executive Summary 5 1 Unlimited for Table of Contents; 2-page limit for Executive Summary Narrative

II 4.0

4.4.1

4.4.2

4.4.3

Technical

1. Design/Install Approach

2. Verification Approach

3. Interim Contractor Support

Approach

5 1 30

4.4.4 Sample Problem Attachments 1- 6 5 1 None

4.4.4 Sample Problem Attachment 7 5 1 1

III 5.0 Contract Documentation 2 1 None

FA8730-19-R-0005 0003, Attachment 8, Page 9

2.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will be returned to the offeror as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified therein. EN responses shall include proposal page revisions as applicable. For all Volumes and Attachments thereto, each page shall be counted except the following:

a. Cover pages

b. Tables of contents

c. Tabs

d. Lists of tables and drawings

e. Glossaries

f. Sample Problem Attachments (minus Attachment 7 which has a one page limit)

g. Acronym Lists

h. Contractual Documentation

2.2.2 Page Size and Format

a. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to ENs. These limitations shall apply to the hard copy and electronic proposals.

b. Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and shall not exceed 11 by 17 inches in size when printed. Foldout pages shall fold entirely within the volume, and count as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, and not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 8 point. For sample problem drawing sheet submittals, refer to Attachment L-1 for formatting requirements. These limitations shall apply to both electronic and hard copy proposals.

2.2.3 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.2.4 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used therein. The glossary shall be used only to spell out abbreviations and acronyms, not to provide an expanded definition of terms.

Glossaries do not count against the page limitations for their respective volumes.

2.2.5 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring loose-leaf binder which shall permit the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification and the

FA8730-19-R-0005 0003, Attachment 8, Page 10 offeror’s name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.2.6 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. In the event there is a difference in content or page size between hard and electronic copies, the Government will base its evaluation on the hard copies. For electronic copies, indicate on each CD/DVD the volume number and title. Use separate files to permit rapid location of all portions, including subfolders, exhibits, annexes, and attachments, if any. The offeror shall submit volumes I through III in electronic format, using a separate read-only Compact Disk/Digital Video Disk (CD/DVD) for each volume. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Word 2016, MS Excel 2016, MS-Project 2016, MS- Power Point 2016, MS Visio 2010, and Adobe Acrobat DC as applicable. For network infrastructure content, refer to Sample Problem Specific Contract Data Requirements List (CDRL) A023, provided in Attachment L-5, for required document format.

2.2.7 Distribution

Proposals shall be addressed to the Contracting Officer and mailed to:

Address:

66 LRS Central Shipping and Receiving (CS&R) Building 1110 (25 Randolph Road) Hanscom AFB, MA 01731-1700

Mark your proposal “Care Of”:

Tanya R. Bigelow, Contracting Officer

AFLCMC/HBUK

Re: Solicitation Number FA8730-19-R-0005 Phone: 781-225-0170

3.0 VOLUME I - EXECUTIVE SUMMARY INSTRUCTIONS

In the Executive Summary volume, the offeror shall provide a master table of contents and a summary of the offeror.

4.0 VOLUME II – TECHNICAL INSTRUCTIONS

4.1 General

The Technical Volume should be specific and complete. Legibility, clarity and coherence are very important. Your responses will be evaluated against the Technical Factor in Section M, Evaluation Factors for Award. Using the instructions provided below provide as specifically as possible the actual methodology you used to accomplish/satisfy the Technical requirements. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.2 Format and Specific Content

FA8730-19-R-0005 0003, Attachment 8, Page 11

Your proposed technical approach for accomplishing/satisfying all technical requirements and objectives shall be presented in the Technical Volume. Offerors are reminded to include in your proposal all information related to each sub factor listed in Section M.

4.3 Table of Contents

The offeror shall provide a table of contents of the Technical Volume that includes a List of Tables and Drawings and attachments included in the Technical Volume. For clarity, each table, drawing, and attachment shall be referenced to its applicable Section, and Sub-section of the Technical Volume.

4.4 Technical Volume II Sample Problem

4.4.1 Design/Install Approach

Provide a narrative description of the proposed security system conceptual design, installation and integration solution to the Sample Problem. Explain, in sufficient detail, the rationale for the design including supporting infrastructure, coverage areas, integration of GFE, rationale for location of equipment, and other information which conveys a description of the proposed Sample Problem design, how it incorporates Sample Problem assumptions, and how it proposes to satisfy Sample Problem requirements.

The intent is to measure the offeror’s ability to answer the Sample Problem and only the Sample Problem.

Limit the contents of this response to the specifically identified Sample Problem assumptions and requirements. Contractor assumptions are not permitted and will not be considered. The response should not provide a design/install approach for meeting a perceived set of holistic requirements to achieve a compliant/certified Air Force security system.

4.4.2 Verification Approach

Provide a narrative verification plan that describes the offeror’s methods to ensure proper verification of the design, installation and integration of the sample problem requirements. The plan shall include a description of proposed verification methods including, but not limited to, the following:

• Integration and functionality of all installed equipment

• Compliance with the Sample Problem Instructions, AFI-31-101, ESE-SIT-001, and other applicable requirements documentation

• Quality control approach

• Schedule management approach

• Non-technical project management requirements

• Test strategies

• Original Equipment Manufacturer (OEM) and sub-contractor inclusion

4.4.3 Interim Contractor Support (ICS) Approach

Provide a description of the proposed approach to provide organizational & depot level support of the Sample Problem system for three years after system turnover. Include a discussion of how OEM and sub-contractor relationships will be established to ensure robust organizational and depot level maintenance is provided.

4.4.4 Attachments to Sample Problem

Attachment 1 - Site Design, Install, & Network Infrastructure Drawings

In accordance with Technical Volume requirements as described in Section 4.4, the offeror shall provide Site Design & Installation drawings that graphically describe the solution to the Sample Problem.

FA8730-19-R-0005 0003, Attachment 8, Page 12

Include sufficient detail in both the Technical Volume and Installation Drawings that describe the following:

• Type, location, and orientation of all IDS / Immediate Visual Assessment (IVA) equipment to be installed.

• IDS sensor coverage areas and IVA / Surveillance camera Field of View (FOV) areas.

• Type, location and compliance details for all ACS equipment to be installed.

• All system integrations with GFE.

• All system communication infrastructure and configuration (new and GFE) shall:

o Identify critical new communication network components.

o Identify all existing communication infrastructure components.

o Identify all communication paths as to locations and mediums.

o Identify any and all new and existing communication interfaces.

o Identify and describe any and all network compatibility issues between system and existing networks and recommended fix actions.

o Describe network topology IAW Sample Problem CDRL A023 (Attachment L-5) instructions.

o Include a Network Interconnections spreadsheet IAW Sample Problem CDRL A023

(Attachment L-5) instructions.

o Include additional general communication requirements as described in Attachment L-1, section 2.2.

Attachment 2 – List of Equipment (LOE)

Provide a LOE that will be used in the solution to the Sample Problem. The LOE shall include the make, model and quantity of each new piece of equipment. The offeror shall not include equipment costs on the LOE. IDS sensor, CCDE, IVA assessment and camera equipment items in this list of must be selected from the IDSEL (Attachment L-1, Table 3-1).

The LOE shall separate equipment items selected from the IDSEL and other equipment proposed in the Sample Problem solution.

Network equipment is not on the IDSEL. All network equipment selected by the offeror shall be pre-certified, Joint Interoperability Testing Center (JITC) approved (reference DoDI 8100.04). The offeror shall ensure that all network equipment (switches, routers, etc.) is selected from the Defense Information Systems Agency (DISA) Approved Products List (APL) (https://aplits.disa.mil/processAPList) and is approved for its proposed use.

Attachment 3 – Integrated Master Schedule (IMS)

Provide an Integrated Master Schedule (IMS) (in Microsoft (MS) Project 2016 format) for the Sample Problem design, install, integration, and verification work (exclude ICS). The IMS shall be defined to no more than five (5) levels of detail to which the offeror plans to manage the execution of the Sample Problem work to successfully meet the requirements of the Sample Problem. The IMS shall depict the critical path, major milestones, each task’s duration, and its relationships with other tasks (predecessors and successors). Furthermore, the IMS shall be resource-loaded using labor categories from Attachment L-3.

Tie the lowest levels of detail in the IMS to the appropriate corresponding CWBS elements.

For the purpose of this sample problem, assume no government vector checks will be required.

Refer to Section 2.2.2 for formatting. In addition to providing a MS Project file, print a Gantt Chart displaying the following columns: Indicator (notes, information), ID, CWBS, Task Name, Duration, Predecessor, Successor, Start, Finish, Resource, and Timeline. Reduce timeline scale in order to show Offeror’s project on 11 by 17 inch paper in landscape orientation when printed.

https://aplits.disa.mil/processAPList

FA8730-19-R-0005 0003, Attachment 8, Page 13

Attachment 4 - Risk Matrix

Provide a risk matrix for the sample problem identifying those significant Sample Problem risks for aspects of the Sample Problem design, installation, integration and verification (exclude ICS) work you consider to have the potential for disruption of schedule, increased cost, or performance impact. Classify each risk as low, medium, or high and identify the probability and impact of occurrence. Propose a risk mitigation strategy for each identified risk. Identify and classify any new risks introduced by such risk mitigation.

Attachment 5 - Basis of Estimate (BOE)

The offeror shall provide BOEs for work to design, install, integrate and verify (exclude ICS) the Sample Problem. Supply BOE information for all work necessary to accomplish the Sample Problem in EXCEL spreadsheet format as outlined below “Sample BOE Template”. The offeror must provide clear traceability from the BOEs to their IMS. For the Sample Problem, the offeror shall not include cost per labor hour, total labor costs, and travel costs in the BOE submissions.

In selecting labor categories, the offeror shall use the Government-provided categories (see Attachment L-3) to the greatest extent possible. If necessary, in Attachment L-3, describe any additional labor category required to accomplish the sample problem, to include duties, level of responsibility and minimum qualifications (e.g., years of experience, education requirements).

Sample BOE Template

Proposed Work Labor

Category(s) (See Sample Problem –

PWBS)

See Attachment

L-3

1.1 PL-1

Restricted Area

1.1.1 Perimeter Detection

BOE

(hrs.)

Basis, rationale, estimating methodology used to derive

BOE

Rationale for Proposed labor-skill mix

Tractability to IMS

Contractor Name:

Attachment 6 - Contractor Work Breakdown Structure (CWBS)

The offeror shall provide a Contractor WBS (CWBS) based on the Proposal WBS (PWBS) provided in Attachment L-4 of Section L. The offeror will adhere to the PWBS structure when developing a proposed CWBS. However, if any deviations are required they will be fully explained and supporting rationale will be provided. Beyond this summary PWBS, offerors have flexibility to make changes based on their proposed approach. However, the offeror must provide visibility by extending the CWBS to the same level at which the BOEs are created.

FA8730-19-R-0005 0003, Attachment 8, Page 14

The PWBS dictionary that corresponds to the PWBS template is provided (See Attachment L-4).

The offeror must adhere to these definitions. Also, when the offeror extends the CWBS below levels identified in Attachment L-4, the offeror must amend the WBS dictionary to provide definitions.

Attachment 7 – Small Business Participation Description

The Small Business Participation Description is a separate requirement from the Small Business Subcontracting Plan that is required by FAR Subpart 19.7 and the clause FAR 52.219-9. The Small Business Participation Description is required from all offerors (including large business offerors and small business prime offerors).

Provide an explanation for how you will provide the maximum opportunity to small businesses IAW FAR 52.219-8, to include service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns in performance of your proposed sample problem solution. Small business offerors will be allowed to submit their own participation to meet the requirements of this section. The Offeror need not identify specific small businesses for their Attachment 7 response for this Sample Problem.

The North American Industrial Classification System (NAICS) code for this action is 561621 – Security Systems Services (except locksmiths) with a size standard of $20.5M annual receipts (Reference 13 Code of Federal Regulations (CFR) 121.201).

5.0 VOLUME III - CONTRACT DOCUMENTATION

5.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file, along with make a formal contractual offer to the Government. The original shall be clearly marked and should be provided without any punched holes. Fill in all blanks in the Model Contract and in Sections A through K with either specific information or with “N/A” as applicable.

5.1.1 Section A - Solicitation/Contract Form

Complete blocks 12 through 16 and sign and date for blocks 17 and 18 of the SF 33. Signature by the offeror on the SF 33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

5.1.2 Section B – Supplies and Services

Pricing information will be contained in the individual DOs. The blanks in Section B do not need to be completed.

5.1.3 Section F - Deliveries or Performance

Pricing information will be contained in the individual DOs. Period of performance will be contained in the individual orders.

5.1.4 Section G - Contract Administrative Data

Contract administrative data will be identified on the individual DOs.

5.1.5 Section H – Special Contract Requirements

Reserved.

FA8730-19-R-0005 0003, Attachment 8, Page 15

5.16 Section I – Contract Clauses

All clauses from the FPS4 IDIQ contract automatically carry over to the subsequent DOs issued.

They shall have the same applicability and effect despite not being listed again on the DOs issued. The offeror shall complete all DO requirements in accordance with all sections of the FPS4 contract.

5.1.7 Section J – List of Attachments

Exhibit A - Contract Data Requirements Lists (CDRL)

An exhibit list of CDRLs for each of the efforts is provided by the Government (RFP, Section J).

Modifications to these exhibits are not allowed.

Attachment 1 - Statement of Work (SOW)

A Statement of Work is provided by the Government (RFP, Section J). Modifications to this document are not allowed.

Attachment 2 – DD Form 254 – Contract Security Classification Specification

The offeror shall fill in blocks 6a, 6b, and 6c in the DD Form 254, Contract Security Classification Specification. The offeror’s proposed DD Form 254, when accepted by the Government, will be placed on contract at award. DO’s requiring the handling of classified information will require an additional DD254 to be submitted. Unclassified DO’s may not require an additional DD254.

Attachment 3 - FPS4 Labor Categories & Qualifications

A description of FPS4 Labor Categories & Qualifications are provided by the Government in Section J of this solicitation. Modifications to the Government provided labor categories and qualifications are not allowed.

Attachment 4 - Work Breakdown Structure (WBS)

Attachment 5 – Small Business Subcontracting Plan (to be proposed)

Attachment 6 – OCONUS Location Specific Terms and Conditions

Attachment 7 – Performance Work Statement (PWS)

Attachment 8 – Section L – Instructions for Proposal Preparation

Attachment 9 – Section M – Evaluation Factors for Award

5.1.8 Section K - Representations, Certifications, and other Statements of Offerors

FAR 52.204-7, CENTRAL CONTRACTOR REGISTRATION, is incorporated by reference in Part II, Section I. The offeror shall follow the instructions cited in this Section K, FAR 52.204-08 and complete all representations, certifications, acknowledgments and statements in the System for Award Management (SAM) as part of responding to this RFP. If a representation, certification, acknowledgement or statement cited in this Section K cannot be found in SAM, then the offeror shall submit that Section K representation, certification, acknowledgement or statement. Failure to adhere to these instructions shall render an offeror as being ineligible for award.

FA8730-19-R-0005 0003, Attachment 8, Page 16

5.2 Other Information Required

5.2.1 Authorized Contractor Personnel

Provide the name, title and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government. In addition, please provide the name, title, and telephone number of the Chief Executive Officer (CEO), Division President, Vice President, and/or other responsible parties who may be contacted for successful or unsuccessful award notification.

5.2.2 Government Offices

Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, and Defense Contract Audit Agency (DCAA). Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

5.2.3 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; Commercial and Government Entity Code (CAGE code); Data Universal Numbering System (DUNS) code; size of business (large or small (North American Industrial Classification System (NAICS) Code 561621); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

5.2.4 Small Business Subcontracting Plan

The offeror is required to submit a Subcontracting Plan IAW FAR 19.702, (Statutory Requirements), and FAR 19.704, (Subcontracting Plan Requirements), for the FPS4 effort. If applicable, submit a copy of your approved Master Plan along with an Individual Plan that includes the goals for this acquisition. The Subcontracting plan must be specific to the FPS4 Program unless the proposed Subcontracting Plan is part of a DoD Comprehensive Subcontracting Plan Test program. If the offeror is other than a small business, the offeror’s Small Business Subcontracting Plan shall be submitted in accordance with FAR 52.219-9. The Small Business Subcontracting Plan will be evaluated to determine the extent to which the offeror complies with FAR 52.219-9. The approved Small Business Subcontracting plan will be incorporated into the contract as an exhibit.

The current Department of Defense small business subcontracting goals apply to the FPS4 acquisition found at http://business.defense.gov/About/Goals-and-Performance/. Use the Subcontracting Goals for FY18 if the FY19 Subcontracting Goals have not yet been posted in your explanation.

The North American Industrial Classification System (NAICS) code for this action is 561621 – Security Systems Services (except locksmiths) with a size standard of $20.5M annual receipts (Reference

13 CFR 121.201).

If an offeror is a Small Business under this NAICS code, then they are not required to submit a Small Business Subcontracting Plan.

5.2.5 Organizational Conflict of Interest Statement and/or Mitigation Plan

All offerors must examine their contractual obligations with the Government and those of their proposed major subcontractors for potential OCIs as defined by FAR Part 9.502(c) and provide a statement identifying any potential OCI or stating that no potential conflicts exist. In the case of a potential OCI, the http://business.defense.gov/About/Goals-and-Performance/

FA8730-19-R-0005 0003, Attachment 8, Page 17 offeror shall also submit an Organizational Conflict of Interest Mitigation Plan detailing organizational and procedural steps to be taken to mitigate any OCI risk.

FA8730-19-R-0005, Attachment 8, Page 18

ATTACHMENT L-1

SAMPLE PROBLEM INSTRUCTIONS

1.0 INSTRUCTIONS

This section contains instructions for preparing responses for the FPS4 Sample Problem. The Sample Problem requires an Intrusion Detection System / Immediate Visual Assessment / Automated Entry Control System (IDS/IVA/ACS) design for the following areas of a hypothetical Air Force Installation:

1. Protection of a Protection Level 1 (PL-1) Restricted Area Boundary (RAB) and Interior Buildings within that boundary. Area 1 on included map.

2. Protection of a PL-2 Hangar (being upgraded from a PL-3 facility). Area 2 on included map.

3. Installation of a Command Control and Display Equipment (CCDE) at the Base Defense Operations

Center (BDOC) located in building 500. Area 3 on included map.

1.1 Sample Problem Response Content and Format

The offeror shall submit the responses to the sample problem IAW Section L paragraph 2.0 (General Instructions), paragraph 3.0 (Volume 1 – Executive Summary), and paragraph 4.0 (Volume II – Technical).

2.0 SAMPLE PROBLEM NOTES, REQUIREMENTS, ASSUMPTIONS AND LAYOUTS

The offeror shall incorporate the assumptions in the paragraphs below into their proposal.

2.1 General Notes, Assumptions & Requirements

1. The Sample Problem utilizes a fictitious Air Force Base (AFB) located within the northern CONUS tier.

2. For the Sample Problem, the average annual snowfall amount is 30 inches with an average seasonal storm precipitation of 5 inches.

3. Layouts of the individual areas of concern are located within each subsection with further, expandable detail PDF files available via FedBizOps (listed in Attachment L-2).

4. The Sample Problem project begins 1 October 2020.

5. All electrical work shall be installed IAW National Fire Protection Association (NFPA)

70, 780 (refer to Section 2.1.4 “Restricted Access Documentation” on page 7 for instructions to obtain documentation).

6. All IDS/ACS work performed within the secured rooms at the Sensitive Compartmented Information Facilities (SCIFS) shall adhere to IAW ICS 705-1 Section G (refer to Section

2.1.4 “Restricted Access Documentation” on page 7 for instructions to obtain documentation).

7. Unless otherwise specified, all existing GFE Squadron communications cabinets and racks are to be considered full and new equipment cannot be added to the existing cabinets.

8. All existing communications conduit not explicitly identified as having available space are to be considered full.

9. All CCDE, Video Servers, Assessment Cameras & Subsystems, Interior & Exterior IDS Sensors and Wide Area Detection Sensors shall be selected from Table 6, Intrusion Detection System Equipment List (IDSEL).

FA8730-19-R-0005, Attachment 8, Page 19

10. All submitted drawings and drawing formats for the Sample Problem shall be prepared

IAW:

a. ASME Y14.1 Engineering Drawing Practices and Related Documentation Practices section 4, 5 and 6 (refer to Section 2.1.4 “Restricted Access Documentation” on page 7 for instructions to obtain documentation).

b. ASME Y14.2 Line Conventions and Lettering, (refer to Section 2.1.4 “Restricted Access Documentation” on page 7 for instructions to obtain documentation).

c. Be created no larger than D size in native format and be provided in PDF format (with up to 50% reduction (B-Size) for incorporation into an 8 ½ x 11 hard copy package).

11. For the purpose of the Sample Problem solution, it is assumed that there is no existing Uninterruptable Power Supply (UPS) at any location.

2.2 General Communications Network Requirements

The Sample Problem communications network shall provide the connectivity from the various system components to the CCDE IAW AFI 31-101 sections 6.3.6.10 and 6.3.11, ESE-SIT-001 sections 2.5 and 3, and CDRL A023 criteria (refer to Section 2.1.4 “Restricted Access Documentation” on page 7 for instructions to obtain documentation).

A significant portion of the Sample Problem communications network is already detailed, and the offeror shall add to or modify these documents as required to complete the Sample Problem. (Reference FedBizOps for complete communications infrastructure and topology details [complete list of drawings available in Attachment L-2]).

Any and all changes to the supplied network configuration files and diagrams/drawings are to be articulated in the Technical Volume - Design/Install Approach explaining the rationale for the offeror's proposed design.

For the purpose of the Sample Problem, all “Alarm Panels” depicted in the Government supplied network diagram documentation shall be considered non-compliant for use.

The Sample Problem communications network solution shall:

a. Update the network configuration file with intended network design changes and additions (current configuration is supplied on FedBizOps via the Drawing Package. See documents titled “Network Configs.docx” and “Network Configs.pdf”).

b. Depict IP addresses, subnet masks and default gateways of all host devices (e.g. computers, servers, cameras, alarm panels).

c. Describe static routes (if used in host devices), in detail, in the Technical Volume.

d. Depict data encryption in the drawings with protocols, encryption algorithm and bit length, hash and bit length, and key exchange and bit length.

e. Describe encryption methods utilized in the Technical Volume.

f. Describe the application layer, in detail, in the Technical Volume with function, settings, and traffic flows for each component and the intended interaction with other components (Camera, VMS, IDS, etc.).

FA8730-19-R-0005, Attachment 8, Page 20

g. Describe and depict logically separate data traffic at the appropriate layer based on data type and asset protection level. Remote device management shall be restricted to a dedicated management Virtual Local Area Network (VLAN) accessible only via a specified interface on the core switch. Physical/console access shall be protected via username and password combinations that differ from manufacturer default and meet minimum security requirements.

Unused ports shall be disabled and set to a non-routed VLAN.

h. Describe the characteristics of fiber optic cables such as diameter, indoor/outdoor, single-mode/multi-mode. If cable is spliced, describe method of splicing (fusion/mechanical), length between splices. Schematic of patch panels annotated in the Rack Diagram.

i. Describe schematics of network devices’ interfaces showing modules, port numbers and connections in the Technical Volume.

j. List the ports that the connected devices utilize in the Network Interconnections file in accordance with CDRL A023

k. Show network devices and modules on a diagram that is linked back to equipment list.

l. Identify ports that are shutdown.

m. Depict all network devices that utilize Power over Ethernet (PoE) with labels on network diagrams.

n. Specify all VLANs configured on individual network devices.

o. Describe all intended layer 2 protocols and specific methods of implementation in the Technical Volume. If Spanning Tree Protocol is used, specify type and details of implementation in the Technical Volume.

p. Describe EtherChannel bundling if used and specify interfaces that are bundled in the Technical Volume.

q. Describe unicast and/or multicast protocalls and specify method and details of implementation in the Technical Volume.

r. Describe name and number assigned to native VLANs in the Technical Volume.

s. Describe name and number assigned to Parking VLAN in the Technical Volume.

t. Describe the specification of ports (per device) that are shut down and assigned to Parking VLAN in the Technical Volume.

u. Describe the functionality of all network devices and interfaces (physical and logical) labeled with IP addresses in the Technical Volume.

v. Describe how and where layer 3 routing protocols are utilized in the offeror’s proposal in the Technical Volume.

w. Detail the diagrams for all networking components including the annunciator.

x. Be designed to optimize network performance utilizing industry best practices.

3.0 SAMPLE PROBLEM

FA8730-19-R-0005, Attachment 8, Page 21

The following subsections break down the Sample Problem into three areas within the notional Air Force base. These subsections contain tables with area specific information and overall area layouts. For more infrastructure details and information refer to documents listed in Attachment L-2 and provided via the FPS4 posting on FedBizOps.

3.1 Area 1 Restricted Area (RA) Requirements

3.1.1 Area 1 Detection Requirements

Design an IDS system for the Protection Level 1 (PL-1) Restricted Area Boundary and buildings 914, 916, 918, 920 and 922 within that boundary. Reference Area 1 on included map in drawing titled “100) Area1-Overall.pdf” and “100) Area1-Overall.vsd” (reference drawing listing in Attachment L-2 and FedBizOps posting containing all required drawings).

Detection alarm and display notification shall report to building 904, room 103 in the Area 1 Entry Control Facility (ECF) and the BDOC in room 100 of building 500.

The Intrusion Detection System (IDS) shall conform to the following instructions, guide and equipment list:

• AFI 31-101, Section 6.2.6, 6.3 and 7.7.1

• ESE-SIT-0001

• FPS4 IDS Intrusion Detection System Equipment List (IDSEL), Table 6 (page 31) below, for approved equipment.

3.1.2 Area 1 Delay / Denial Requirements and Assumptions

For the Sample Problem, the existing RA fence does not meet type A1 chain link fence standards as required by AFI 31-101 section 6.5.2.2.1, AFM 32-1084 section 8.7.1.5.1.1 and ESE-SIT-0001 sections

2.5.1.1.2 and 2.6 (if appropriate).

There is sufficient clear zone at all points around the RA perimeter.

Sample Problem makes the assumption that sufficient project funds exist to replace existing RA fence line and ACS equipment in its entirety.

The offeror is required to describe how they plan to maintain the RA security during construction.

3.1.3 Area 1 Immediate Visual Assessment (IVA) Requirements

Design an IVA system for the PL-1 area in Area 1.

The RA IVA capability shall be installed in support of the perimeter detection system. The offeror shall provide 100% IVA IAW AFI 31-101, section 6.3.15 and ESE-SIT-0001, section 8. Camera poles on the RA perimeter shall be the cantilever type.

IVA video shall be displayed in room 103 in building 904, the Entry Control Facility (ECF) and BDOC in room 100 of building 500.

3.1.4 Area 1 Surveillance Requirements

FA8730-19-R-0005, Attachment 8, Page 22

The offeror shall design a surveillance system to provide visual capability around the Area 1 Entry Control Facility (building 904). This surveillance video shall be monitored in room 103 of the ECF and the BDOC. Any Pan-Tilt-Zoom (PTZ) cameras shall be controllable from the BDOC.

3.1.5 Area 1 Access Control Requirements

3.1.5.1 Area 1 RA Perimeter Access Control

Design an Automated Control System (ACS) for personnel at the Entry Control Facility (building

904) that complies with AFI 31-101, section 7.7 for a PL-1 site. The system shall also allow the Entry Control Facility Entry Controller (EC) to manually open and secure the personnel portals. The ECF personnel portals shall be Architectural Barriers Act (ABA) Article 404.3 compliant.

The motorized vehicle gates located next to the ECF will only be operated by the EC without ACS.

No work is necessary for this gate for the Sample Problem.

3.1.5.2 Area 1 RA Storage Buildings Access Control Requirements

The storage buildings in Area 1 are considered to contain the PL-1 assets. Design an IDS sensor Arm/Disarm system (not ACS) for the PL-1 area 1 buildings 914, 916, 918, 920 and 922 storage buildings.

Storage building sensor systems shall be armed/disarmed utilizing an alpha-numeric keypad located at each facility to allow authorized personnel to gain entry without the assistance of the Entry Controller or the BDOC. The ECF Entry Controller and BDOC shall have remote capability to arm/disarm each facility independently.

3.1.6 Area 1 Sensitive Compartmented Information Facility (SCIF) Area Requirements

Building 910 in Area 1 is a newly constructed SCIF facility.

Design a communication network interface (only network interface to this building, no IDS/IVA) to this SCIF facility. The secure area within this building comprises of rooms 200 & 201 only.

3.1.7 Area 1 CCDE Requirements

The Area 1 RA perimeter building sensor systems shall be annunciated in building 904 room 103 of the ECF and the BDOC. The offeror shall label the annunciation in this area IDS exterior detection sensors as “Sector X – Area 1” and clearly define the location on the graphics page of…