Section_L_-_DRAFT_to_Industry_20190308.pdf

FA8730-19-R-xxxx, Attachment #, Page 1

ATTACHMENT xx

INSTRUCTIONS, CONDITIONS, AND NOTICES TO

OFFERORS

INSTRUCTIONS FOR PROPOSAL PREPARATION (IFPP)

SECTION L

FOR

FORCE PROTECTION SITE SECURITY SYSTEM SOLUTIONS

(FPS4)

xx MARCH 2019

FA8730-19-R-xxxx, Attachment #, Page 2

REVISION HISTORY

Revision Number

Date Description Sections

Affected

1 8 Feb 19 Initial Publication

2 8 Mar 19 Second Draft

FA8730-19-R-xxxx, Attachment #, 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 Bidder’s Library

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

4.0 VOLUME II - TECHNICAL

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 Test/Verification Approach

4.4.3 Interim Contractor Support Approach

4.4.4 Attachments to the Sample Problem

FA8730-19-R-xxxx, Attachment #, 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 B - Supplies or Services and Costs/Prices

5.1.3 Section F - Deliveries or Performance

5.1.4 Section G - Contract Administrative Data

5.1.5 Section H - Special Contract Requirements

5.1.6 Section I - Contract Clauses

5.1.7 Section J - List of Attachments

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

5.2 Other Information Required

5.2.1 Authorized Offeror 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 Drawings Attachment L-3 Sample Problem Labor Categories and Qualification

FA8730-19-R-xxxx, Attachment #, Page 5

1.0 PROGRAM STRUCTURE AND OBJECTIVES

The Force Protection Site Security System Solutions (FPS4) contract is a five (5) year ordering period Indefinite Delivery/Indefinite Quantity (IDIQ) contract (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), Fixed Price Award Fee (FPAF), Cost Plus Award Fee, and Time & Material (T&M) contract types and the following initial order Contract Line Item Number (CLIN) structure:

CLIN “0001” of the FPS4 Request for Proposal (RFP) is a Firm-Fixed-Price Post Award Conference CLIN in the amount of $x intended to meet the minimum ordering requirement of any resulting IDIQ contract.

Each IDIQ awardee will receive an order against CLIN 0001 in the amount of $x.

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), Automated Entry Control Systems (AECS) and surveillance systems; 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 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 (i.e., 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 or proposed. 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) acquired under this contract will consist of either (1) already proven COTS equipment from the Air Force Security Forces Center (AFSFC) Approved Equipment List (AEL), (hereafter referred to as the “Approved Equipment List” [AEL]); or (2) non-AEL COTS equipment proposed by the offerors (or otherwise specifically required by the Government as part of a Delivery Order (DO) solicitation). If non-AEL COTS equipment falls into the categories established in the AEL, and is proposed as part of an FPS4 Indefinite Delivery/Indefinite Quantity (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 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 delivery order solicitation) may demand.

FA8730-19-R-xxxx, Attachment #, 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 and support 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 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 consideration in developing your proposal, 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 CONUS Fixed Site Projects $513M

OCONUS/CONUS Sustainment and Operational Readiness Support Activities, Equipment Buys & FMS Projects

$142M

C-sUAS Projects, Delay/Denial Projects, 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 Statement of Work (SOW), Model Contract, including all Exhibits and Attachments thereto, and all attachments to this IFPP including 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.

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.

FA8730-19-R-xxxx, Attachment #, Page 7

e. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one complete copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

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.

Offerors 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 found on the FedBizOpps site at http://www.fedbizopps.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

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

Torch Technologies, Inc. 4090 South Memorial Parkway Huntsville, AL 35802 http://www.fedbizopps.gov/

FA8730-19-R-xxxx, Attachment #, Page 8

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.

TABLE 2. Proposal Organization

Volume

Atch)

IFPP

Paragraph

No.

Volume Title Hard Copies (Including one original)

Electronic Copies

Page Limit

I 3.0 Executive Summary 5 1 None

II 4.0 Technical 5 1 20

4.4.1 Design/Install Approach 5 1

4.4.2 Verification Approach 5 1

4.4.3 Interim Contractor Support

Approach

5 1

4.4.4 Sample Problem Attachments 1-3 5 1 None

III 5.0 Contract Documentation 2 1 None

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

FA8730-19-R-xxxx, Attachment #, Page 9

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 both electronic and hard copy proposals.

b. 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. Foldout pages shall fold entirely within the volume, and each

8.5 x 11 surface of a foldout shall be counted as a separate page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. 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 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 IV in electronic format, using a separate read-only 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

FA8730-19-R-xxxx, Attachment #, Page 10

(MS) Word 2016, MS Excel 2016, MS-Project 2016, MS-Power Point 2016, and Adobe Acrobat DC as applicable.

2.2.7 Distribution

The "original" proposal shall be identified. 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”:

Andrew J. Sibley, Contracting Officer

AFLCMC/HBUK

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

3.0 VOLUME I - EXECUTIVE SUMMARY

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

4.0 VOLUME II - TECHNICAL

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 Volume requirements. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.2 Format and Specific Content

Your proposed technical approach for accomplishing/satisfying all technical requirements and objectives shall be presented in the Technical Volume. In this volume, your proposed approach shall map to the Technical Factor identified in Section M.

4.3 Table of Contents

The offeror shall provide a table of contents of the Technical Quote 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 (20 page limit)

4.4.1 Design/Install Approach

Provide a narrative description of the proposed system security conceptual design, installation, and integration solution to the Sample Problem in sufficient detail to explain 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

FA8730-19-R-xxxx, Attachment #, Page 11 incorporates Sample Problem assumptions, and how it proposes to satisfy Sample Problem requirements.

The intent is to measure the Contractor’s ability to answer the Sample Problem and only the Sample Problem. Limit the contents of this response to 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 the verification plan that depicts the offeror’s approach to verify proper implementation of sample problem requirements. The plan shall include a description of proposed verification methods that will verify the sample problem project requirements, to include non-technical project requirements, including, but not limited to quality control approach, schedule management approach, and sub-contractor/OEM management approach.

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 (No Page Limit)

Attachment 1 - Site Design & Install Drawings

Provide Site Design & Installation drawings for the proposed conceptual design solution to the Sample Problem. Include sufficient detail to reflect locations where the equipment will be installed, integrated with GFE, infrastructure (a network topology, spreadsheet, and switch configuration IAW CDRL A023 instructions), coverage areas and other information and details to provide a conceptual overview of the proposed design.

Attachment 2 – List of Equipment (LOE)

Provide a LOE to be used for the Sample Problem. Include the quantity of each piece of equipment.

The list of Intrusion Detection System (IDS) equipment (such as cameras, sensors, annunciators, etc.)

proposed to be used to support the IDS aspects of the sample problem project must be selected from the Approved Equipment List (Attachment L-1, Table 3-1). The contractor may select ancillary equipment that is not on the AEL (such as displays, fiber optic converters, etc.) needed to support the Sample Problem project requirements that do not relate to the IDS equipment categories. Separate the Sample Problem list into those equipment items selected from the Approved Equipment List and other equipment proposed to support meeting Sample Problem requirements. Also, tie each piece of equipment in the LOE to the appropriate Contract Work Breakdown Structure (CWBS) element. Finally, network equipment is not on the AEL. All network equipment selected by the offeror shall be pre-certified, Joint Interoperability Testing Center (JITC) approved (reference DoDI 8100.04). The contractor shall ensure that all network equipment (switches, modules, SFPs, etc.) is selected from the DISA Approved Products List (APL) and is approved for its proposed use.

Attachment 3 – Integrated Master Schedule (IMS)

Provide an Integrated Master Schedule (IMS) (in Microsoft Project 2016 format) for the Sample Problem installation work. The IMS shall be defined to the level of detail to which the offeror plans to manage execution of the Sample Problem installation work to successfully meet the requirements of the sample problem. The IMS shall depict the critical path, each task’s duration, and its relationships with

FA8730-19-R-xxxx, Attachment #, Page 12 other tasks. Furthermore, the IMS shall be resource-loaded by labor category at the lowest level of detail needed to manage execution of the installation work. Distinguish between prime contractor, sub-contractor and OEM labor categories. Tie the lowest levels of detail in the IMS to the appropriate corresponding CWBS elements.

Attachment 4 - Risk Matrix

Provide a risk matrix for the sample problem identifying those significant Sample Problem risks or aspects of the Sample Problem installation 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 Estimates (BOE)

The BOEs shall provide the basis, rationale, estimating methodology and historical database used to derive proposed labor hour estimates. In selecting labor categories, the offeror shall use the Government-provided categories (see Attachment L-7) to the greatest extent possible. If necessary, describe any additional labor category required to accomplish the sample problem, to include duties, level of responsibility and minimum qualifications (i.e., years of experience, education requirements, etc.). The offeror must provide clear traceability from the BOEs to their IMS. Cost per labor hour and total labor costs will not be included in the BOE submission. To support the proposed labor hours, provide a BOE for each WBS element proposed. The BOE shall include a comparison of the proposed hours to historical experiences on similar/analogous projects and rationale for the proposed labor-skill mix.

The offeror shall provide a Contractor WBS (CWBS) based on the Proposal WBS (PWBS) provided in Attachment X 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 complete flexibility based on the proposed implementation approach. However, the offeror must provide visibility by extending the CWBS to the same level at which the BOEs are created.

The PWBS dictionary that corresponds to the WBS will be provided with the PWBS template. The offeror must adhere to these definitions. Also, when the offeror extends the CWBS below levels identified in Attachment X, the offeror must provide WBS definitions at these lower levels.

Attachment 6 – Small Business Participation (1-page limit)

Provide an explanation for how you will identify and commit to small business (as identified FAR 52.219-8) participation in performance of your proposed sample problem solution. Small Businesses will be allowed to submit their own participation to meet the requirements of this section.

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. The offeror’s proposal shall include one (1) signed copy of the Standard Form (SF) 33, Solicitation Offer and Award, and Sections A through K. 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.

FA8730-19-R-xxxx, Attachment #, Page 13

5.1.1 Section A - Solicitation/Contract Form

Completion of blocks 12 through 16 and signature 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 or Services and Costs/Prices

Completed pricing information in Section B of the model contract for Order 0001, “FPS4 Post Award Conference."

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

The offeror shall take note of all Special Contract Requirements identified in Part I Section H of the Model Contract that an offeror must demonstrate its ability to meet in order to be eligible for award.

5.1.6 Section I – Contract Clauses

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

They 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 all appropriate information 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.

Attachment 3 - FPS4 Labor Categories & Qualifications

A description of FPS4 Labor Categories & Qualifications are provided by the Government (RFP, Section L, Attachment L-3). Modifications to the Government provided labor categories and qualifications

FA8730-19-R-xxxx, Attachment #, Page 14 are not allowed. However, offerors may propose any additional labor category required to accomplish the sample problem, to include duties, level of responsibility and minimum qualifications (i.e., years of experience, education requirements, etc.).

Attachment 4 – Section L – Instructions for Proposal Preparation

Attachment 5 – 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.

5.2 Other Information Required

5.2.1 Authorized Offeror 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 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, DCAA, and Government Paying Office. 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; CAGE code; DUNS code; size of business (large or small (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 successful offeror will be required to provide

FA8730-19-R-xxxx, Attachment #, Page 15 reports on subcontractor participation in accordance with FAR clause 52.219-25 in Section I of the contract. Failure to submit such a plan will render the offeror ineligible for award.

The current Department of Defense small business subcontracting goals apply to the FPS4 acquisition:

TABLE 6-1. Current DoD Small Business Subcontracting Goals

Small Business 33% HUBZone Small Business 3.0% Service-Disabled Veteran-Owned Small Business 3.0% Small Disadvantaged Business* 5.0% Women-Owned Small Business 5.0%

*Small Disadvantaged Business awards include 8(a) awards

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 organizational conflicts of interest (OCI) 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 potential OCI, the Offeror will 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-xxxx, Attachment #, Page 16

ATTACHMENT L-1

SAMPLE PROBLEM INSTRUCTIONS

*This page has been intentionally left blank*

FA8730-19-R-xxxx, Attachment #, Page 17

ATTACHMENT L-2

SAMPLE PROBLEMS DRAWINGS

*This page has been intentionally left blank*

FA8730-19-R-xxxx, Attachment #, Page 18

ATTACHMENT L-3

SAMPLE PROBLEM LABOR CATEGORIES & QUALIFICATIONS

a. System Engineer. Possesses five to ten years of experience in the design and development of physical and electronic security systems. Possesses a Bachelor’s degree in Electrical, Electronics, Computer or Systems Engineering or a related field. Comprehensive knowledge and familiarity with physical and electronic security system implementation, including Air Force and Department of Defense standards, is required.

b. Senior Engineer. Possesses a minimum of ten years technical experience relating to the assigned project area. Possesses a Bachelor’s degree applicable to the design, development and installation of physical or electronic security systems. Possesses an advanced degree(s) or has conducted studies in engineering or IT. An additional four years of experience may be substituted for the advanced degree requirement. Individual must be particularly knowledgeable and competent in at least one function/technological area and familiar in all aspects of a particular project. Functional and technological areas include, but are not necessarily limited to, systems engineering management, system test and evaluation, project engineering support, software development, civil engineering, electrical engineering, mechanical engineering, reliability and maintainability, parts control program, electromagnetic compatibility, radio frequency management, system safety, and human factors.

Comprehensive knowledge and familiarity with physical and electronic security system implementation, including Air Force and Department of Defense standards, is required.

c. Engineer. Possesses a minimum of one to three years of technical experience relating to the assigned project area. Possesses a Bachelor’s degree applicable to the design, development and installation of physical or electronic security systems. Individual must be particularly knowledgeable and technically competent in at least one of the functional/technological areas described for the Senior Engineer above. Possesses detailed knowledge and familiarity with physical and electronic security system implementation.

d. Senior Technician. Possesses specific OEM certifications for the type of equipment to be utilized. Possesses a minimum of ten years of technical experience in a specific function/technological area related to physical or electronic security systems. Possesses an Associate’s degree or equivalent in that functional/technological area. An additional two years of experience may be substituted for the degree requirement. Working knowledge of physical and electronic security systems and equipment, as well as their installation, test and operation is required.

e. Technician. Possesses a minimum of three years of technical experience in installation, testing, operation and maintenance of electronic systems. Possesses a high school diploma or equivalent GED.

f. Network Engineer. Evaluates current network systems and makes recommendations for resources required to maintain and/or expand service levels. Provides highly skilled technical expertise in network planning, engineering, and architecture. Develops technical standards and interface applications, identifies and evaluates new products, and provides resolution for network problems. Plans large-scale systems projects through vendor comparison and cost studies. Manages the purchase, installation, and support of network communications, including LAN/WAN systems.

Provides system configuration of Network, and/or communication systems, including Local Area Network (LAN) and Wide Area Network (WAN) systems. Prepares technical implementation plans that provide integrated solutions including actions, milestones, timelines and critical paths required for complete solutions. Per DoD 8570.01-Manual, all personnel involved in network design shall have

FA8730-19-R-xxxx, Attachment #, Page 19

Information Assurance Technician Level III certification. In addition, network design personnel shall have specific OEM certifications for the type of equipment to be utilized (such as CCNP or equivalent).

g. Network Technician. Engages in the operation and support of network facilities, including all communications equipment in large scale or multi-shift operations. Supervises complex operations that involve two or more additional functions such as, but not limited to, network installation, network configuration, network operations, systems security, systems software support, and production support activities. Monitors and responds to hardware, software, and network problems. Provides the routine testing and analysis of all elements of the network facilities (including power, software, communications machinery, lines, modems, and terminals). Monitors and controls the performance and status of the network resources. Per DoD 8570.01-Manual, installation/maintenance personnel having administrative credentials for the system shall have Information Assurance Technician Level II certification. These personnel shall have OEM certifications for administration of the equipment to be utilized (such as CCNA or equivalent). Installation/maintenance personnel shall have OEM certification for FPS4 systems that are being installed or maintained.

h. Logistics Manager. Possesses ten years of experience in logistics management that includes at least five years of experience supporting Department of Defense systems, preferably Air Force. Possesses a Bachelor’s degree applicable to logistics management. An additional four years of experience may be substituted for the degree requirement. Must be knowledgeable and technically competent in all facets of product support to include, but not limited to, technical manual development, training, supply chain management and maintenance concepts.

i. Logistics Specialist. Possesses six years of logistics experience that includes assignments in one or more of the following areas: technical manual development, training material development, or supply management. Possesses a Bachelor’s degree applicable to logistics management. An additional four years of experience may be substituted for the degree requirement. Be competent in technical manual development or training material development covering both operational and maintenance documents.

j. Administrative or Clerical. Possesses a minimum of one year of experience as a secretary, technical typist, or in performing clerical duties related to the preparation of technical documents. Possesses a high school diploma or equivalent GED certificate.

k. Systems Field Engineer (FE). Possesses specific OEM certifications for the type of equipment to be utilized. Possesses a minimum of five years of technical experience relating to physical or electronic security system projects. Possesses a Bachelor’s degree in an engineering discipline or computer science. An additional four years of experience may be substituted for the degree requirement. The FE shall support the maintenance, inspection, adjustments, reconfiguration, and introduction of new or advanced security technology including testing. The FE shall perform all related IT support required to host upgraded security systems.

The tasks to be performed/supervised by the FE may consist of, but are not limited to, the following:

• Works to ensure that all site work progresses as scheduled and contract specifications are met

• Installs and maintain all security systems and associated IT networks, systems and support equipment

• Works closely with the site’s Force Protection and Security Forces personnel on all security system issues

• Provides technical expertise and maintain all security systems at designated sites.

• Performs security site surveys as required by Force Protection staff

FA8730-19-R-xxxx, Attachment #, Page 20

• Writes detailed trip reports to include sensor recommendations and sensor placement derived from site surveys

• Assists the System Administrator located at his/her assigned site(s).

• Provides initial and/or refresher training on equipment for personnel assigned to administer and/or operate the system. The FE shall train personnel on operational, field-level, or depot maintenance, as well as higher headquarters procedures. The FE shall help local Force Protection Commanders develop security system subject matter experts within their command

• Makes recommendations to the Security Forces Commander on the placement of new or upgraded equipment.

l. Project Manager. Possesses a minimum of seven years of experience in managing projects, including at least five years of experience with technical projects. Possesses a bachelor’s degree in management, business or a technical field related to engineering, construction or IT. Tasks to be performed may include the following.

• Oversees all elements of a project

• Leads and motivate a team and coordinate its efforts to ensure that a project progresses according to plan

• Communicates with stakeholders to solicit input, define requirements and provide updates from conceptual design through project completion

• Manages and mitigates risk

• Plans, builds, analyzes and manages schedules, budgets and technical requirements

m. Quality Assurance Inspector. Possesses a minimum of four years of experience in a technical field related to what this person is inspecting. Possesses a bachelor’s degree in construction, engineering or IT, depending upon what this person is required to inspect. An additional four years of relevant experience may be substituted for the degree requirement, provided that the person has a high school diploma or GED. Tasks to be performed may include the following.

• Coordinates with stakeholders and engineers to build a Quality Assurance plan

• Inspects work, either in-progress or after completion, to ensure that completed work complies with applicable federal, state and local standards and regulations

• Records inspection results; prepares and submits inspection reports as required

• Notifies project managers if work is performed unsatisfactorily, or if a work environment is deemed to be unsafe

n. Information Assurance (IA) Specialist. Possesses a minimum of six years of experience in analyzing and applying IA requirements to computer systems. Possesses a bachelor’s degree in IA, IT or computer science. An additional four years of relevant experience may be substituted for the degree requirement, provided that the person has a high school diploma or GED. Also possesses a DoD 8570.01-compliant IA Technician (IAT) Level II certification. Tasks to be performed may include the following:

• Reviews DoD Security Technical Information Guides (STIGs) and identifies which ones apply to FPS4 projects

• Examines FPS4 systems for potential IA vulnerabilities; works with Government agencies to correct vulnerabilities

• Ensures that FPS4 systems comply with IA requirements as determined by the Defense

Information Systems Agency (DISA) or other applicable DoD entities

• Prepares and submits IA documentation that illustrates a system’s IA configuration

• Configures FPS4 equipment to match established IA baselines

• Coordinates with other team members to prepare and submits interface control documents

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS