Draft_Section_L-IAFNOS.docx

L-1 PROPOSAL PREPARATION INSTRUCTIONS

A. GENERAL INFORMATION

1. This acquisition is being conducted as a 100% Women-Owned Small Business set-aside under the North American Industry Classification System (NAICS) 517110.

2. Points of Contact. The CO and/or Contract Specialist (CS) are the only points of contact (POC) for questions or concerns regarding this acquisition. Address any questions or concerns to the CO or CS specified in Blocks 10a through 10c of the SF 33. Written requests for clarification (questions) may be sent to the CO and CS to the e-mail address located in Block 10c of the SF 33 until the date/time specified in provision Air Force Federal Acquisition Regulation Supplement (AFFARS) 5352.215-9001. Changes to the CO POC will be made by amendment to the solicitation. Late requests may not be considered.

3. Debriefings. The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with (IAW) FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable.

4. Discrepancies. If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO and CS in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

5. Electronic Reference Documents. All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at https://www.fbo.gov/. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

6. Communications. The CO will control exchanges of source selection information between Government and offerors. The Government may use email to transmit such information to offerors and will include “Source Selection Information – See FAR 2.101 & FAR 3.104” in the Subject line. Otherwise, the Government will transmit source selection information via, United States Postal Service or commercial carrier.

7. Questions: All questions related to this solicitation must be submitted to Julie.Chase@us.af.mil and Cathy.Summers@us.af.mil no later than 3:00 PM CT on 20 Mar 15.

8. Reading Library. A Reading Library containing a list of Exhibits has been established at Tinker Air Force Base (AFB). The single POC for access is Ms. Julie Chase who can be reached at (405) 734-9711 or julie.chase@us.af.mil. Instructions for the library are included in the request for proposal (RFP) as Attachment 8. Reservations shall be made in advance not later than 3:00 PM CT on 20 Feb 15. The Library will be open from 2 Mar – 6 Mar 15 from 8:00 AM CT to 12:00 PM CT and 1:00 PM CT to 4:00 PM CT. The Library will be open again 23Mar – 27 Mar from 8:00 AM CT to 12:00 PM CT and 1:00 PM CT to 4:00 PM CT; reservations for this timeframe must be submitted no later than 16 Mar 15 to the above POC.

B. GENERAL INSTRUCTIONS

1. To assure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, technical requirements, and Contract Security Classification Specification, in addition to those identified as evaluation factors or subfactors.

2. This section of the RFP provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include all data and information requested by the RFP and must be submitted IAW these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements Lists (CDRL), and RFP. Non-conformance with the instructions provided in the RFP may result in an unfavorable proposal evaluation. Alternate proposals will not be accepted.

3. Offeror’s 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. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the offeror's proposal.

4. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

5. The proposal acceptance period is specified in Section A of the solicitation.

6. IAW FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. After contract award, the Government will destroy extra copies of such unsuccessful proposals.

C. ORGANIZATION.

1. Number of Copies/Page Limitations. The offeror shall prepare the proposal as set forth in the Proposal and Binder Organization Tables (Tables 1 and 2 below). The titles and content of each part, all of which shall be within the required page limits, are defined in Table 1, and the number of copies is described in Table 2. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal.. Proposal change pages are customarily subject to the same page limitations stated in Table 1 below; however, deviated page limitations may be required on responses to Evaluation Notices (ENs). Each page shall be counted except cover pages, table of contents, and glossary. The Cover page shall include Offeror DUNS, Cage Code, POC’s name, phone number, email, and physical address.

2. The response shall consist of four (4) separate parts: Part I – Technical Proposal, Part II – Present/Past Performance Information (PPI), Part III – Price, and Part IV – Contract Documentation. The content of each proposal binder is described in detail as follows:

TABLE 1 – PROPOSAL ORGANIZATION (within binders)

PART TITLE PAGE NUMBERS

EZ Source)

G for additional instruction)

TABLE 2 - BINDER ORGANIZATION

COPY PARTS TO INCLUDE

*Original and Copy 1 binders contain the complete proposal package. Reproduction of the entire RFP is unnecessary (and unwanted).

*Original shall include a recordable, virus-free data compact disk (CD) which contains all parts (Parts I, II, III, and IV). CD must be secured inside CD/DVD binder storage pages (3-hole type) and secured into binder rings at the front of the Original” binder.

3. 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 may be single-spaced but shall have at least double spacing between paragraphs and factors or sub-factors. Except for the reproduced sections of the solicitation document, Attachment 2 (Pricing Table), and items specified in paragraph (b) below, the text size shall be no less than 12 point, Times New Roman, Arial or Courier font type. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one-inch margins on all sides. Pages shall be numbered sequentially by part. These limitations shall apply to both electronic and hard copy proposals.

b. Legible tables, charts, graphs and figures may 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 part, and shall 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 eight-point. These limitations shall apply to both electronic and hard copy proposals.

4. Cross Referencing. The offeror shall provide a cross-reference matrix, which does not count against the page count, at the beginning of Part 1-technical volume indicating the PWS paragraph number and the corresponding proposal paragraph. To the greatest extent possible, each part shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other parts of the proposal. Cross referencing within a proposal part is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation which is not found in its designated part will be assumed to have been omitted from the proposal.

5. Indexing. Tab indexing shall be used to identify parts.

6. Glossary of Abbreviations and Acronyms. Each part shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective parts.

7. Binding and Labeling. The proposal shall be bound in three-ring, loose leaf binders permitting the binders to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each binder, clearly marked with the title, copy number, solicitation identification, and the offeror’s name. The same identifying data shall be placed on the spine of each binder.

8. Electronic Documents. The content and page size of electronic documents must be identical to the hard copies. Label the CD with the RFP number, title, and offeror’s name. Within the CD, use a separate electronic file for each part with associated exhibit, annexes, and attachments to permit rapid search and location. Files shall not be compressed. Submit electronic proposal documents in a format readable by Microsoft (MS) Office Word 2010, MS Office Excel 2010, and MS Office Power Point 2010, as applicable. In the event of discrepancy(s) between the hard copies and electronic copies of a proposal, the hard copies will be used for evaluation.

D. PART 1 – TECHNICAL PROPOSAL.

1. The Technical Part should be specific and complete. Legibility, clarity, and coherence are very important. Offeror responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide the actual methodology the offeror will use to accomplish/satisfy these subfactors. All the requirements specified in the solicitation are mandatory. By submitting its proposal, the offeror represents that its firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for the offeror to tell the Government so in its proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

2. Identify submitted material by corresponding factor, subfactor, and paragraph/element herein. If an offeror is subcontracting/teaming with another vendor, the prime shall clearly identify work to be performed by each specific sub-contractor within the appropriate Factors/Subfactors in the prime’s proposal. The proposals shall provide a clear distinction of functions to be performed by the prime and subcontractor to include the following: the nature of work, criticality of the work, and the percentage of overall effort performed by each subcontractor in each area of service provided based upon the cost of contract performance incurred for personnel (See FAR52.219-14 (b)(1) -- Limitations on Subcontracting, Services).

3. Format and Specific Content. Offeror shall address its proposed approach to meet the minimum performance or capability requirements of each Technical Proposal subfactor as follows:

Subfactor 1: Staffing/Retention. The offeror shall present an acceptable staffing and retention approach that explains how it will meet PWS Sections 3 and 4 and Appendices 3 and 4.

Subfactor 2: Transition Plan. The offeror shall present a plan to ensure continuity of services between the incumbent contractor and the new contractor IAW PWS sections 3 and 4..

Subfactor 3: AFIN Mission Assurance Center (AMAC) Support. The offeror shall provide an acceptable AMAC Support action plan and/or approach that demonstrate how it will meet the PWS sub-paragraphs 3.6 requirements by addressing the following scenario:

Scenario 1: The AMAC is notified of a complete base isolation via a phone call from the affected base communication focal point (CFP). Prior to the phone call, there were no indicators identifying an impending problem. Later, an I-NOSC infrastructure technician identified the outage was due to high CPU utilization on the External Router.

Subfactor 4: Network Operations and Core Services. The offeror shall provide an acceptable network operations and core services action plan and/or approach that demonstrates how it will meet the PWS sub-paragraphs 3.2 and 3.3 requirements by addressing the following scenarios:

Scenario 2: You unilaterally implement a web proxy change request for a fellow NOS technician, Bob, and validate that traffic is processing successfully and passing through a valid firewall rule within a proxy service group. A week later, Bob submits a new incident ticket stating that he applied a security patch that changed the protocol and now his connection isn't working. No other configuration changes were made to the system.

Scenario 3: A Maintenance Task Order has been released authorizing Microsoft patch KB2902892.

Scenario 4: Tom, Dick, Harry, and Renee are trying to access the same file, a sensitive but unclassified summary of a particular organization’s logistics and resupply plans while it’s in garrison. Tom has nothing to do with the organization or its resupply effort. Dick has credentials to not only access but also to manipulate and save changes to the data—but not to send it anywhere. After he manipulates the data, he attempts to put it on a USB stick. Harry has credentials to not only access, manipulate, and save changes to the data, but also to send it to the trucking company. Harry decides he wants to work on a particular file at home and attempts to attach and send it to his Hotmail account. When that fails, he decides to cut and paste all of the contents of the file into an email and tries again. Renee has credentials to not only access, manipulate, and save changes to the data, but also to send it to the trucking company. Renee finishes her work, and attempts to email the file to the trucking company. When that fails, she sends the file via FTP. The data owner has determined that this data cannot be transmitted to any Internet-enabled destination, except that of a public trucking company that is assisting in a particular portion of a resupply effort, but then only by FTP.

Scenario 5: On Monday, technicians are managing AFIN infrastructure devices from authorized workstations on the X.X.20.0/24 network. On Tuesday, the infrastructure work center is converted to virtual desktops and the physical workstations are removed. The work center’s IP space for the virtual desktops is now on the X.X.40.0/24 network. After the change, the infrastructure technicians notice that they can no longer login and manage AFIN devices.

Scenario 6: A Virtual Environment Technician is physically separated from a virtual environment that they manage. The managed virtual environment has a local technician that can perform touch maintenance but is unskilled in managing virtual environments.

The virtual environment is configured with iSCSI connections using pairs of active/passive network interface cards for resiliency.

The Virtual Environment Technician has the following tools available to them:

a. Ping

b. Virtual Center vSphere VMWare Web Client(v5.5)

c. Site plan that includes DNS machine names for physical and virtual machines, assigned IP addresses, multiple ESX host virtual environment topology, iSCSI storage connections, Ethernet switch ports and vLAN connections

The Virtual Environment Technician receives an incident ticket stating that host XYZ-003v is unresponsive. From the host name, the technician knows that XYZ-003v is a virtual machine (VM) located in the virtual environment. The local technician is not reachable.

Scenario 7: After performing routine inspection of a remote virtual environment, your fellow virtualization technician notices that a single virtual machine host at site X has alerts stating that connectivity to that site's storage array have been lost and asks that you troubleshoot the issue.

The following tools, accesses and information are available to the technician:

a. VMWare vSphere Web Client

b. VMWare virtual client command line tool

c. PuTTy

d. Storage array web client

e. Windows Command Prompt

f. Web browser

g. RPC access to the remote site's physical Backup Server

h. Remote location's site work book that includes DNS machine names for physical and virtual machines, assigned IP addresses including devices, multiple ESX host virtual environment topology, redundant path Fibre Channel storage connections, Ethernet switch ports and vLAN connections

Subfactor 5: Operations Support and Enterprise Governance. This subfactor is met when the offeror demonstrates an acceptable operations support and enterprise governance approach that meets the PWS sub-paragraph 3.5 requirements based on the following scenarios:

Scenario 8: Geographically separated ESU technicians are making authorized configuration changes inconsistent with each other. These changes are causing storage issues in the exchange environments

Scenario 9: A technician was assigned a ticket that was to be completed before Monday at 1100AM. It is now 2PM on Monday and the ticket has not been worked.

Scenario 10: The AF Cyber Security and Control System (CSCS) provides 24/7 network operations and management functions to manage, monitor, detect, prevent, and defend the AF networks (NIPR and SIPR) from cybercriminal activities. 690 COG collaborates with numerous AF organizations to modernize the AFIN and can, at any time, simultaneously manage operational employment of five to ten major projects for the AFIN. The projects can range from firewall modernization of all bases to data center consolidation.

E. PART II – PRESENT/PAST PERFORMANCE INFORMATION.

1. General. Each offeror shall submit Present/Past Performance Information (PPI) no later than 1:00 PM CT 30 Mar 15 IAW the format contained in Attachment 6. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of present/past performance. Past performance of either party in a joint venture counts for the past performance of the entity.

2. New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers, employees, and key personnel who have relevant experience and/or data of efforts that will perform major or critical aspects of the requirement. Discuss the roles and responsibilities of personnel involved in the prior contracts cited.

3. Reference Data. The Government reserves the right to contact and use information provided by the references and any other sources. The Government may also obtain and consider information about other contracts not mentioned in the offeror’s proposal, but which the Government believes to be similar to the proposed effort. It is the offeror’s responsibility to ensure all reference data is current and correct so that the Government can properly evaluate PPI.

4. Recency/Relevancy. Offeror shall submit PPI on no more than twelve recent contracts that the offeror considers most relevant in demonstrating its ability to perform the proposed effort. The total includes any subcontractors or teaming partners; however, no more than six of the twelve recent contracts shall be submitted on the teaming partners and/or significant subcontractors that the offeror considers most relevant in demonstrating their ability to perform the proposed effort. Do not duplicate a contract reference for prime and subcontractor but rather explain the role each played within the contract reference itself. For a description of the characteristics or aspects the Government will consider in determining how contracts are considered recent and relevant, see Section M, B.4.a 1 and 2.

5. Quality. CPARs information and present/past performance questionnaires (PPQ) will be used in evaluation of recent and relevant present/past performance. Offeror may provide any additional information to explain corrective actions taken in the past, if any, for substandard performance and any current performance problems such as cost overruns, extended performance periods, numerous warranty calls, etc.

6. Present/Past (PP) Performance Questionnaire (PPQ).

a. The offeror shall send out the PPQ (Attachment 4) to each of the offeror’s critical subcontractors’, teaming contractors’ and/or joint venture partners’ (i.e., each entity’s). The responsibility to send out and track the receipt and submission of the PPQs rests solely with the offeror. For each PPQ, complete and sign a letter containing substantially the same information as in the Sample PPQ Cover Letter (Attachment 5). Cover letters should be printed on company letterhead. The offeror shall exert its best effort to ensure that a current POC, per relevant contract, submit a completed PPQ directly to the Government not later than the due date for the past performance proposal volume. Each of the offeror’s POCs shall e-mail the completed PPQ directly to Ms. Julie Chase, and Ms. Cathy Summers at: julie.chase@us.af.mil and cathy.summers@us.af.mil. Mailing the PPQs is an acceptable alternative method of transmission. The mailing address is:

38 CONS/LGCC

ATTN: Ms. Julie Chase 4004 Hilltop Rd.

Tinker AFB, OK 73145-2713

If mailing, the outside envelope must be marked as follows:

NOTE: TO BE OPENED BY ADDRESSEE ONLY

SOURCE SELECTION INFORMATION - SEE FAR 3.104 FOR OFFICIAL USE ONLY

b. Once the PPQs are completed by the POC, the information contained therein shall be considered source selection sensitive and shall not be released to the offeror. Questionnaires shall be sent to directly to the Government from at least one of the following:

Program/Project Manager or equivalent, CO/Contract Administrator (CA) or equivalent, or CO Representative (COR).

7. Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent present/past efforts and this source selection. As a result, it is sometimes difficult to determine what present/past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of the company. As part of this explanation, show how these changes impact the relevance of any efforts the offeror identifies for present/past performance evaluation/performance confidence assessment. Since the Government intends to consider PPI provided by other sources as well as that provided by the offeror(s), the "roadmap" should be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources.

9. Consent Letters. The offeror shall submit a consent letter, executed by any potential subcontractors, teaming partners, and/or joint venture partners. The consent letter authorizes release of adverse PPI to the offeror so the offeror can, in turn, respond to such information. A sample letter follows:

F. PART III – PRICE PROPOSAL.

1. Price Reasonableness, Completeness, Balance, and Affordability. This section is to assist the offeror in submitting information other than cost or pricing data that is required to evaluate the reasonableness, completeness, balance, and affordability of the offeror’s proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of offeror’s proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness, completeness, balance, and affordability. The burden of proof for credibility of proposed prices rests with the offeror at the time of proposal or during subsequent discussions (if any are held).

2. Price Information. The price proposal shall not include information beyond that required by this instruction unless the offeror considers it essential to document or support offeror’s price position. All information relating to the proposed price, including all required supporting documentation must be included in this part or assumptions of the proposal. Under no circumstances shall this information and documentation be included in the Technical Proposal or Present/Past Performance Information parts.

3. Adequate Price Competition. The Government has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the CO will review this determination and if, in the CO’s opinion, adequate price competition exists, no additional cost information will be requested and certification under FAR 15.406-2 will not be required. However, if at any time during this competition the SSEB determines that adequate price competition no longer exists; offerors may be required to submit information to the extent necessary to determine the reasonableness of the price.

4. Rounding. All dollar amounts (unit and extended prices and other price factors) provided shall be rounded to the nearest penny (two decimal places only). This includes base period and out-year (option) prices. Rounding errors caused by Government formulas will be corrected during evaluation to round to the nearest penny.

5. Downward Pricing Initiatives Process(es). Describe your process(es) for identifying, assessing, evaluating, and implementing price efficiency initiatives to achieve continuous downward pricing reductions. Provide evidence these processes are incorporated in the price for the initial period of performance resulting in downward out-year prices in then-year dollars, based on an annualized value for the effort. Include any pertinent diagrams, charts or tables.

6. Professional Compensation Plan. As part of its price proposal, offeror shall provide its total compensation plan setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract IAW FAR 52.222-46 -- Evaluation of Compensation for Professional Employees (Feb 1993).

7. Organization. Part III shall consist of the following:

a. Table of Contents: includes Table of Contents and summary descriptions of estimating, purchasing, accounting systems and invoicing processes and practices.

b. Pricing Notes/Methodology: pricing information and supporting data, to include estimating methodology.

c. Pricing Assumptions/Exceptions. Repeat any assumptions/exceptions affecting pricing only in this area. Do not cross reference to/from Part IV, Contracting Documentation. Annotate “none,” if no assumptions/exceptions apply.

d. PRICING TABLE (included in Section J, as Attachment 2 to the solicitation). The offeror shall comply with the following requirements and instructions:

(1) Price all Contract Line Item Numbers (CLIN). Limit unit prices to two decimal places. The abbreviations Not Separately Priced (NSP) and No Charge (N/C) are not acceptable entries. If the offeror is providing a CLIN to the Government at no additional charge, “$0.00” must be entered for that item. The dollar value of CLINs X013 is a not to exceed (NTE) amount established by the Government and shall not be altered by the offeror. Option to Extend Services, CLINs 5002-5012 will be automatically populated with established formulas on the Pricing Table.

(2) Electronic Media Submission of Pricing Table. The CLINs in the Pricing Table of this solicitation are an electronic file, presented as Excel spreadsheet/workbook format. Submit both a hard copy and an electronic copy using the exact file provided by the Government without changing the format of the files.

(3) Description of Files.

(i) Summary Sheet: Contains cells for the entry of unit prices for CLIN 0001 and CLINS X002 -X010 and calculates extended prices for the Base Period through Option Period 4 and the Option to Extend Services (500X).

(ii) Option to Extend Services, CLINs 5002-5010, will be automatically populated IAW clause 52.217-8. While it is not the Government’s intent to utilize these option CLINs, they are included to facilitate the extension of services if it is deemed necessary at the end of period of Option 4 performance.

G. PART IV - CONTRACT DOCUMENT SECTION

1. Contract Documentation. The purpose of this part is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the SF 33 and SF 30 for any subsequent amendments issued. The offeror shall complete and submit “ONLY” the contract document sections as follows:

Section A - Solicitation/Contract Form. Complete Blocks 12 through 18 (including original signature and date) of the SF 33. Signature by the offeror on the SF 33 constitutes an offer, of which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes. Instead, secure the original signed SF 33 in a document protector bound in the “original proposal” binder and one copy in the “Copy 1” binder. Offeror shall include a statement within this part that the proposal is valid through the proposal acceptance period specified in Section A.

Section B - Supplies or Services and Costs/Prices. Do not include. This section will be populated by the Government at contract award from data provided on Attachment 2, Pricing Table.

Sections C, E, and F. Do not include. These sections are not modifiable by the offeror and are redundant to include with the proposal submission.

Section G - Contract Administrative Data. Offeror shall provide a “remit-to” address if different from the mailing address in Block 9 on the SF 33. The Remit-to address will be included in Section G of any resultant contract at the time of award. Do not include Section G if “remit-to” address does not apply. DD Form 254 Instructions. To be considered for award, offerors must comply with all security requirements specified in the DD Form 254, Contract Security Classification Specification included in this solicitation, complete Blocks 6.a., b. and c. thereof, and return the completed DD Form 254, Contract Security Classification Specification, along with evidence that: 1) offeror has an Active TOP SECRET Facility Clearance; and 2 each position identified in offeror’s proposal has a final TOP SECRET or SECRET personal security clearance. To fulfill the requirements of this effort, some positions must be eligible for access to Sensitive Compartmented Information IAW Intelligence Community Directive (ICD)704 and Intelligence Community Policy Guidance (ICPG) 704.2. A qualified offeror must have an Active TOP SECRET Facility Clearance at the time it submits its proposal. Failure to do so shall result in the Government determining a proposal unacceptable.

Section I - Contract Clauses. Submit pages for only clauses which require offeror fill-ins: 52.2095. Ensure the submissions are from the RFP itself, which includes the RFP and page numbers. Other pages in this section shall not be included with the submission.

Section J – List of Attachments. Complete and submit Attachment 2, Pricing Table (Schedule B); Attachment 7, DD 254; and Exhibits 1-22, CDRLS, which are to be returned with Block 18 completed. If the CDRLS are not separately priced, use NSP to complete the block.

Section K –

a. System for Award Management (SAM) (Representations, Certifications, and other Statements of Offerors). Completed SAM representations, certifications, acknowledgments and statements shall be included with submission. Ensure SAM is current, complete, and accurate at the time of proposal submission. SAM representations and certifications must include those specified within Section K of this RFP. SAM can be accessed at https://www.sam.gov/portal/public/SAM/#1. Offeror shall be eligible for award under the specified NAICS code, 517110, and the specified set-aside at the time of submittal of their proposal and remain eligible when verified again prior to award of the contract.

b. Joint Venture Agreements. Joint Ventures are allowable if offeror(s) meets the criteria established in FAR 19.1403(c). Additionally, if the JV does not possess its own TS facility clearance, it is permissible for the managing member of the JV to utilize its TS Facility Clearance to meet the requirement. Offeror must state in its proposal that all classified work or data will be performed in the designated JV partner’s TS facility.

Sections L. Do not include. This section is not modifiable by the offeror and is redundant to include with the proposal submission with exception of DFARS provision 252.237-7024, Notice of Continuation of Essential Contractor Services. Offeror shall include, in Part IV, documentation required by DFARS provision 252.237-7024(b). There is no page limitation for this document and it is not included in the overall page limitation. Additionally, the submitted document will be incorporated into the contract by reference IAW DFARS 252.237-7023.

Section M. Do not include. This section is not modifiable by the offeror and is redundant to include with the proposal submission.

2. Offerors shall list any assumptions that affect the offered price, such as Government Furnished Property/Government Furnished Equipment (GFP/GFE), and base support. Should the offeror have no assumptions, then the proposal shall so state “no assumptions made for the RFP proposal submission.” Moreover, failure to include assumptions in this area will be deemed as acceptance of all terms and conditions of the solicitation (as amended) and resulting award document.

3. OTHER INFORMATION REQUIRED. Offerors shall also provide a separate sheet at the end of this part with the following information:

a. Authorized Offeror Personnel. Provide the name, title, e-mail address, voice and fax telephone numbers, street and mailing address (if a PO Box is used) of the primary and alternate company/division POC 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.

b. Company/Division Address, Identifying Codes, and Applicable Designations. Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation.

c. SAM. Offerors are required to maintain an active registration in the SAM database at https://www.sam.gov/portal/public/SAM/ (see FAR 52.204-7).

d.. DD Form 254 Instructions. To be considered for award, offerors must comply with all security requirements specified in the DD Form 254, Contract Security Classification Specification included in this solicitation, complete Blocks 6.a., b. and c. thereof, and return the completed DD Form 254, Contract Security Classification Specification, along with evidence that: 1) offeror has an Active TOP SECRET Facility Clearance; and 2 each position identified in offeror’s proposal has a final TOP SECRET or SECRET personal security clearance. To fulfill the requirements of this effort, some positions must be eligible for access to Sensitive Compartmented Information IAW Intelligence Community Directive (ICD)704 and Intelligence Community Policy Guidance (ICPG) 704.2. A qualified offeror must have an Active TOP SECRET Facility Clearance at the time it submits its proposal. Failure to do so shall result in the Government determining a proposal unacceptable.