Government_Responses_to_Industry_Questions-Comments_-_12_February_2019.pdf

Government Responses to Industry Questions and Comments dated 12 February 2019

FA8750-19-R-0001

RFP Section Reference Questions/Comments Government Response 1 Proposal Due Date Due to the complexity of the RFP and sample tasks, respectfully request a 30-day extension of the proposal due date on the subject solicitation.

Due to the complexity of the requirements, the Government released a DRAFT RFP five (5) months in advance of the Final RFP to allow industry the ability to review and provide feedback on any questions they might have leading up to the Final RFP.

2 FA8750-19-R-0001 Basic Performance Work Statement (PWS) & Attachment No. 8 - Cross Reference Matrix

In Section 4 of the PWS, there are 2 references to Section 4.2, each with separate requirements. This may have an impact on our response and the traceability matrix in the Cross Reference Matrix (Attachment 8). Please correct the numbering and provide an update.

There is only one reference to Section 4.2 in section 4 of the Performance Work Station (PWS) from the basic contract (FA8750-19-R-0001).

Please note, there are differences between the PWS and the Performance Work Descriptions (PWDs) of the four (4) orders (FA8750-20-F-0001, 0002, 0003, & 0004). The PWS covers the requirements for the entire GARDEM solicitation and the PWDs cover the specific requirements for each order.

3 Attachment No. 8 - Cross Reference Matrix

Attachment 8 includes a reference to section 4.18 which does not exist in the PWS. Please correct this reference.

In Attachment No. 8 – Cross Reference Matrix PWD paragraph 4.18 is specific to orders FA8750-20-F- 0003 and FA8750-20-F-0004. The respective PWDs are attached to their corresponding orders.

4 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L008

Please confirm we only need sealed packages from subcontractors with whom we have proposed hours.

Subcontractors can be on the team without providing pricing, however, we will need to name all subcontractors in the cost narrative.

Please reference Section L – Instructions, Conditions, and Notices to Offerors, RIK-L008(e) (copied below for reference) for subcontractor proposal requirements.

(e) Subcontractors' proposals must be similarly structured. All subcontracted work must be properly identified as such. If a subcontractor elects to submit an abbreviated proposal to Offeror, it is Offeror's responsibility to see that the subcontractor simultaneously submits a complete detailed proposal per Table 15-2 directly to the Contracting Officer. Offeror must ensure that subcontractor adheres to the guidance set forth herein. FAR 15.404-3 requires that an Offeror provide an analysis of subcontractors' cost proposals.

To that end, the Offeror's proposal must:

(1) Identify principal items/services to be subcontracted.

(2) Identify prospective subcontractors and the basis on which they were selected. If noncompetitive, provide selected source justification.

(3) Identify the type of contractual arrangement contemplated for the subcontract and provide a rationale for same.

(4) Identify the basis for the subcontract costs as included in Offeror's proposal (e.g., firm quote or engineering estimate, etc.).

(5) Identify the cost documentation submitted by the subcontractor.

(6) Provide a price analysis of the proposed subcontract in accordance with FAR 15.404-1(b) and a cost realism analysis in accordance with FAR 15.404-1(d). Provide an analysis concerning the reasonableness, realism and adequacy of each subcontractor's proposal. If the analysis is based on a comparison with prior prices, identify the basis on which the prior prices were determined to be reasonable.

5 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L006

Section L states, “All pages shall be numbered sequentially from the first to the last page using only Arabic numerals.” To simplify compliance with page limits, would the Government allow the use of Roman numerals for the Tables of Contents and other front matter for each volume, and Arabic page numbering starting with page “1” for the actual text of the volumes?

The use of Roman numerals for the Tables of Contents and other front matter for each volume is allowed.

Per RIK-L006(a), “The table of contents and tabs are exempt from the page limits.”

6 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L006

Would the government allow us to provide a list of acronyms/abbreviations, to be included with “front matter” (i.e., with the title page and Table of Contents) of each volume, and which would therefore be exempt from the page limit?

Yes, the Government will allow a list of acronyms/abbreviations exempt from the page limit.

7 FAR 52.222-46, Attachment No. 3 - Performance Work Statement (PWS) AFRL/RI Supplemental Requirements, & Section M - Evaluation Factors for Award

The Government reference FAR 52.222-46 clause in Attachment No 03, page 24 and in Section M, page 4. Do offerors and subcontractors need to provide a total compensation plan? If so, as the compensation plan contains salary data, should the compensation plan be submitted as an attachment to Volume II – Cost?

Total compensation plans are required per FAR 52.222-46 and clause flow down requirements. Yes, the total compensation plan should be submitted as part of Volume II – Cost.

8 Attachment No. 18 - Cost Proposal Pricing Template

Attachment 18 Tab “F-0002 0500” shows 109,400 hours for Sample R&D Task Order, FA8750-20-F-0002 for 30 months which equals 57 FTEs times 1920 for the entire 30-month period. However, Section L estimate for FTEs states “57 FTEs CONUS at 1920 hrs./yr.” Which is correct? If the estimate is per year, should the hours be for 273,600 hours (1,920 hour per FTE *57 FTEs *30 months) and would the Government provide an updated Attachment No. 18?

109,400 hours for the 30 month period of performance of order FA8750-20-F-0002 is correct. A modification to the RFP has been accomplished. RIK-L005(a)(2)(b)(iv) was changed from 57 FTEs CONUS at 1920 hours per/year to 57 FTEs CONUS at 1920 hours per the 30 month period of performance.

9 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L007 & RIK- L013

Section L states that for each task order, the contractor is required to have a certain number of key staff with SCI access at time of award, however, the statement of work does not discuss clearance requirements, or key personnel. Can you please clarify the disconnect between the statement of work and section L, in terms of key personnel requirements? Are there key personnel in each task order? Is the offeror required to have SCI cleared staff at time of award?

The key personnel clause is not identified in each task order, however the labor categories listed in Attachment No. 9 – Labor Category Qualifications identify the qualification requirements. Additionally, RIK- L013 – Facility Clearance lists the required number of SCI cleared staff required at the time of award for each task order. The performance work statement requires offerors to “Ensure appropriately cleared and qualified personnel are maintained for successful program performance” (4.6.5.1).

10 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L006

Will the government please confirm in addition to the Electronic Copies required for each Volume (I Contract Forms: 1; II Cost: 2; III Technical: 2; IV Management: 2; V Past Performance: 2; VI First Order: 2) that the government is requesting 1 C.D with the entire proposal response for a total of 12 C.Ds submitted.

Submission of a total of two (2) CDs containing all Volumes is sufficient.

11 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L006

Please confirm the font requirements for graphics and tables. Arial 10 or Times New Roman 11 font sizes are required for charts tables and diagrams. Please note, charts, tables, & diagrams may be printed on pages not to exceed 11 x 17 inches.

12 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L005

Section RIK-L005 PROGRAM EFFORT (OCT 2016) for TO1 states “the Government estimates 36 Full Time Equivalents (FTEs) CONUS each year, and 30 FTEs OCONUS for each year.” In the breakdown of the On-site engineers that follows, 16 of the 66 FTE are listed at 3600 hrs/yr. This estimate would yield total hours of 153,600 (50X1920 plus 16X3600). However, in the Cost Proposal Pricing Template Summary CLINs tab, the government estimate for labor hours is shown as 66 FTE at 1920 hrs/yr, for total hours of 126,720.

Please clarify the government’s estimate for TO1 Hours and the expectations regarding the FTE listed at 3600 hrs/yr in section L.

The Government estimate for the hours per year for task order FA8750-20-F-0001 has been updated to 153,600 hours in the Cost Proposal Pricing Template.

The amount of labor actually required by each individual offeror is a function of its technical approach, experience, background, method of management, accounting system, and other factors. For this reason, Offerors should use this information only as a benchmark in formulating an approach to performance.

Offerors are neither expected nor encouraged to attempt to make their proposal precisely fit the Government's estimate.

13 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L013

Given the sensitive nature of the request to transmit social security numbers for the government to verify availability of personnel, and the fact that named personnel are not requested, please advise if the government would accept any alternative certification of availability of estimated resource requirements in lieu of provision of social security numbers for personnel in the offeror's staffing plan.

The Government requires the offeror to identify in Section 3 of the Contract Forms volume those cleared or clearable personnel by name and Social Security Account Number that will be assigned to the program upon contract award. This information allows the Government to verify eligibility for employment and validate facility clearance.

14 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L005

Section RIK-L005 PROGRAM EFFORT (OCT 2016) outlines specific FTE counts and locations for onsite engineering support for Task Order 001 (36 FTEs across multiple CONUS and OCONUS locations), and that this is included in the total FTE count.

Is the government looking for a specific mix of locations and clearances in the representative resumes?

The resumes provided should include engineering/scientific and management personnel representative of your proposed team. The Government is not looking for a specific mix of locations and clearances in the representative resumes or resumes specific to any individual order.

15 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L005

If the FTE count and locations are different for each Task Order, how will representative resumes be scored? ie.

Will the representative resumes be evaluated for ability to meet the travel requirements, or are the travel requirements only relevant to the cost volume and estimated ODCs?

Resumes will be used within the evaluation for purposes identified in RIK-L009 and RIK-L010.

16 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L005 & Attachment No. 8 - Cross Reference Matrix

The Cross Reference Matrix (Attachment 8) calls out for Management in the Section L Column RIK-L005.

Can the Government Clarify if this is a typo. It’s possible that it is a typo with RIK-006 Proposal Preparation Instructions?

The Government will complete Amendment No. 2 to the GARDEM RFP to correct Attachment No. 8 - Cross Reference Matrix. The references to RIK-L005 and RIK-L013 from the Management (Volume IV) row will be moved to the Technical (Volume II) row.

17 FA8750-19-R-0001 Basic Performance Work Statement (PWS)

PWS Section 4.6.12

Request the Government define the term identified in this section as “out-plant positions”.

Out-plant positions are defined as any position working outside an offeror’s facilities.

18 Attachment 18 - Cost Proposal Pricing Template

Can the Government confirm that for FA8750-20-F-0002 CLIN 0500 has a 30 month Period of Performance and that the estimate of 109,440 hours is for the total period of performance duration and not per/year?

The Government confirms a 30 month Period of Performance for Order FA8750-20-F-0002 (RIK- L005(a)(2)(b)(i), RIK-L005(a)(2)(c), & top of tab F-0002 0500 in the Cost Proposal Pricing Template).

The Government also confirms the estimate of 109,440 hours is for the total period of performance of Order FA8750-20-F-0002.

19 Attachment 18 - Cost Proposal Pricing T Section RIK-L005(a)(2)(b)(iv) states that the Government estimate is 57 FTEs CONUS at 1920 hours per/year.

Should the Government estimate be 273,600 hours over a 30 month PoP for 57 FTEs?

No. A modification to the RFP has been completed. RIK-L005(a)(2)(b)(iv) was changed from 57 FTEs CONUS at 1920 hours per/year to 57 FTEs CONUS at 1920 hours per the 30 month period of performance.

20 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L007

RIK-L007 Proposal Prep. Instructions Volume I Contract Forms (a)(4) Section 4(iv)(B) “total contract percentage” with regard to the small business participation plan indicates the method of calculating the percentage of the contract to be performed by small businesses is – SB total contract dollars / total contract dollars.

What value does the Government intend to use as the “total contract dollars”? Is it equal to the $427,000,000.00 referenced in (a)(4) Section 4(iii) related to the Small Business Subcontracting Plan; OR should it be the value of the Contract as of the date of proposal submission, equaling the total value of Task Orders 001-004 as proposed in response to this solicitation (ie. Total contract percentage = SB total contract dollars/ total evaluated price TOs 001-004)?

The current interpretation is that we will be evaluated on the total value of dollars within our proposal to be subcontracted to small businesses under the awardable task orders. This will be consistent with our teaming approach and estimated level of effort for the contract requirements known at the present time. Any clarification that you could provide would be greatly appreciated as it will impact the numbers within our proposal.

The Government requires Small Business Participation plans to be expressed in terms of the total contract value, similar to the Small Business Subcontracting Plan.

21 FA8750-19-R-0001 Basic Performance Work Statement (PWS)

Does Government have unlimited data rights and full documentation packages for all software listed in PWS paragraphs 2.2.2.4.1 and 2.2.2.4.2?

The software listed in the referenced paragraphs are Government owned; however, the software listed is not managed by AFRL. They are capabilities that this program office has integrated with in the past and continues to collaborate with.

22 FA8750-19-R-0001 Basic Performance Work Statement (PWS)

Section 4.3 is "System Installation". In subsection 4.3.9: "Design, develop, and test...", is it the expectation that "design" and "development" will be carried out during System Installation?

System Installation refers to installation of the varied systems/capabilities at various customer site locations. Once installed, there may be a need to make subtle modifications to the software or databases for the specific customers' needs at which point it would be necessary to then to test, train and maintain.

Testing may include User Acceptance Testing upon installation.

23 FA8750-20-F-0002 Performance Work Description (PWD)

Sample Task Order 002 PWD Sections 4.15, 4.15.2 and 4.15.3 all refer to researching and improving the ASPERE software system. Does the ASPERE software baseline include any source code not already released in the Technical Data package?

Yes. The Government provided representative source code via DI2E and representative source code along with the build environments via hard drives. The source code and build environments are representative of the overall baselines.

24 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L007

Section RIK-L007 (Proposal Preparation Instructions) para (a) (4) iv Small Business Participation Plan requires the offeror to estimate total dollars of work for the entire contract for each small business. This amount divided by total contract dollars (large and small) provides the percentage of contract performed by SBs. However, the Cost volume does not require offerors to provide cost for the entire contact- just the four provided task orders.

Without knowledge of full contract scope, determination of full contract value and assignment of workshare with small business partners carries huge risk. Request Government reconsider calculation of percentage of contract performed by SBs to use only inputs provided in the Cost volume

The Government requires Small Business Participation plans to be expressed in terms of the total contract value, similar to the Small Business Subcontracting Plan.

25 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L007

Should offerors assume that they will be awarded the entire ceiling of the contract to create the calculations? Yes, small business percentage calculations are required to be expressed in terms of the total contract value.

26 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L007

Will offerors be beholden to this estimate during contract performance reviews? Both Small Business Subcontracting Plans and Small Business Participation Plans will be incorporated into any resultant contract. Throughout performance, large businesses will be required to submit ISRs and SSRs in eSRS that are reviewed by the Contracting Officer in accordance with the requirements of 52.219- 09 Alt. II and 252.219-7003.

27 Attachment No. 5 - Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software

Offerors are required to submit an assertion of technical data or computer software furnished to the Government with restrictions on use, release, or disclosure have to be made in Contract Forms Volume I. Will those proposals without restrictions be assessed an additional strength in their technical volume as the Contract Forms volume is not evaluated per Section M?

Per RIK-L007(a)(iii), "while Government Purpose Rights are the minimum acceptable, the Government desires Unlimited Rights." The Technical Approach Evaluation Subfactor will review the soundness of the Offeror's proposed approach to analyzing current User, System and Security requirements to rapidly deliver novel solutions through development, enhancement, testing, evaluation, integration, and operational transition into military environments; agile development and business practices in order to quickly deliver and field operational technology with and for the Air Force, Department of Defense, Intelligence Community (IC) and other federal agencies; performing Research and Development (R&D) that satisfies the various technology areas in support of Government objectives in Command and Control, Intelligence, Surveillance and Reconnaissance, data analysis, Space and C2 exercises and operations in order to improve GARDEM capabilities that are, or may be, relevant to the GARDEM user community. Data Rights Restrictions that impact the execution of the technical objective will be taken into consideration within the Technical Approach Evaluation Subfactor.

28 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L013

Section RIK-L013 (Facility Clearance) lists the four task orders TOs) and their immediate requirements upon award for personnel with SCI access. Across the four TOs a total of 79 SCI personnel are required upon TO award. The section also requires the offeror identify in Section 3 of the Contract Forms volume those cleared or clearable personnel by name and Social Security Account Number (SSAN) that will be assigned to the program upon contract award. Are offerors to assume that all TOs will be awarded to them upon contract award and therefore the Government's expectation is the offeror will identify 79 cleared or clearable personnel in Section 3 of the Contract Forms?

Correct. Offerors are required to propose against all TOs that will be awarded, therefore, it is necessary to identify, within the proposal, the required clearable personnel to staff the positions.

29 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L005 & RIK- L013

Request Government verify personnel estimate for TO 001 in paragraph RIK-L005 and L013. Para L005 estimate for TO 001 is 66 FTEs. In paragraph L013, estimate for persons requiring SCI access is 81 personnel.

Does paragraph L013 include part time personnel?

The Government anticipates the potential need for the offeror to rotate employees performing in contingency areas in accordance with their company Rest and Recuperation (R&R) policies, therefore, creating a need for additional SCI cleared personnel beyond the FTEs required for each location.

30 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L005 & RIK- L013

Are all personnel assigned to TO 001 required to have SCI access? Not all personnel on TO 001 will require SCI.

31 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L007 & RIK- L013

Employees, prior to authorizing the release of social security account number, are requesting further details on the administrative processes and the physical security system utilized by AFRL to prevent the unauthorized release of personally identifiable information (PII) to comply with the privacy act. Can the Government provide the information on AFRL administrative processes and the physical security system used to prevent the unauthorized release of PII?

The Air Force Research Lab has processes and procedures in place to securely store PII information following the Privacy Act of 1974 (5 U.S.C. 552a). Physical security includes personal management in maintaining surveillance and control over the documents while being reviewed, and storing the documents in secured approved locations when not in use.

32 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L007

Employees are requesting provisioning of PII be done outside of Volume I Contract Forms. Furthermore as prime contractor it is our desire for subcontractors to provide PII directly to government to minimize administrative overhead associated with processes and physical security system requirements for storing and processing PII. Request Government remove requirement to provide PII in Volume I, identify a government POC for this data, and have employers (Prime and subcontractor teammates) provide data directly to a Government POC vice having prime contractor coalesce, and provide in Volume I.

PII is required to be provided in Vol I.

33 Attachment No. 9 - Labor Category Qualifications

Do either or both Field Site /System Representatives or Field Site System Engineers write software code in the field that modifies/changes software baselines?

The Field Site / System Representatives or Field Site System Engineers may write code that will get rolled into the software baselines.

34 Attachment No. 9 - Labor Category Qualifications

Are offerors constrained to the list of labor categories on Attachment No. 9, or may they add LCs to their proposal?

Offerors may map labor categories to the most appropriate LCs listed in Attachment 9. For clarity in evaluations it would be best to stick to these LCs and use industry standards.

35 Attachment No. 9 - Labor Category Qualifications

Can offerors propose different levels of seniority for the labor categories on Attachment No. 9? (For example, apprentice, journeyman, master, etc.)

Please use industry standards in your proposal for management and technical personnel.

36 Attachment No. 9 - Labor Category Qualifications

If Government is expecting a single level of each labor category to be proposed, request Government identify this level.

Senior levels are identified in Attachment 9. Please use industry standards in your proposal for management and technical personnel.

37 Attachment No. 9 - Labor Category Qualifications

Section M states “The Government will evaluate Cost/Price for reasonableness, realism, and balance”, Attachment 9 provides labor categories. Most labor category descriptions do not include years of experience or education requirements. To ensure a best value cost volume comparison between offerors, can Government provide for each labor category the expected years of experience and education?

The minimum qualifications currently listed will remain as written.

38 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L009, RIK- L010, & Attachment No. 9 - Labor Category Qualifications

Proposal preparation instructions states up to 40 resumes may be included with proposal: 20 technical and 20 management. Labor category descriptions do not differentiate labor categories as either technical or management. Can Government update Attachment 9 to include labor category identification as either technical or management personnel?

Please refer to industry standards for definition of management and technical personnel.

39 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L005 & Attachment No. 18 - Cost Proposal Pricing Template

In Section L of the RFP, the government estimates the number of engineering, scientific and/or technical labor FTE’s for each Task Order, but does not list any of the other labor referenced in the Pricing Proposal Template estimates. Can the government detail all the estimated labor categories and locations for each Task Order?

The amount of labor actually required by each individual offeror is a function of its technical approach, experience, background, method of management, business systems, and other factors. For this reason, Offerors should use Government estimate information only as a benchmark in formulating an approach.

Offerors are neither expected nor encouraged to attempt to make their proposal precisely fit the Government's estimate.

40 Attachment No. 18 - Cost Proposal Pricing Template

Are offerors allowed to deviate from the Government estimates on FTE count and/or hours per FTE? The amount of labor actually required by each individual offeror is a function of its technical approach, experience, background, method of management, business systems, and other factors. For this reason, Offerors should use Government estimate information only as a benchmark in formulating an approach.

Offerors are neither expected nor encouraged to attempt to make their proposal precisely fit the Government's estimate.

41 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L005 & Attachment No. 18 - Cost Proposal Pricing Template

In Section L of the RFP, the government estimates FTE’s located in the USCENTCOM Theater of Operation to work 3600 hrs / yr. However, in the Proposal Pricing Template, all FTE’s are estimated as working 1920 FTE’s.

Can the government please correct this discrepancy?

The Government estimate for the hours per year for task order FA8750-20-F-0001 has been updated to 153,600 hours in the Cost Proposal Pricing Template, dated 07 February 2019.

The amount of labor actually required by each individual offeror is a function of its technical approach, experience, background, method of management, business systems, and other factors. For this reason, Offerors should use this information only as a benchmark in formulating an approach. Offerors are neither expected nor encouraged to attempt to make their proposal precisely fit the Government's estimate.

42 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L005

Paragraph RIK L005 (a)(1)iv states there will be 30 FTEs OCONUS each year. Paragraph RIK L005 (a)(1)v identifies only 26 OCONUS positions. For the Cost volume where should the missing four OCONUS positions be assigned?

Per FAR 2.101 Contiguous United States (CONUS) is defined as the 48 contiguous States and the District of Columbia. Therefore, the four (4) Hawaii locations are consider Outside Contiguous United States

(OCONUS).

BREAKOUT:

Djibouti - 5; Afghanistan - 10; Kuwait - 4; Iraq - 2; Korea - 4; Hawaii - 4; Japan - 1 Total = 30

43 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L009

Is the 60 day phase in period, 60 calendar or 60 work days? The 60 day phase-in period is calendar days.

44 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L009

Para 1 states "References to appropriate Performance Work Statement /Performance Work Description tasks should be explicitly indicated."

Para 2 states "Technical proposals will be prepared in the same sequence as the Performance Work Statements and Performance Work Descriptions for Real O&M Task Orders FA8750-20-F-0001, FA8750- 20-F- 0003, and FA8750-20-F-0004, and Sample R&D Task Order FA8750-20-F-0002.

(b) The Technical Volume shall address the Basic Performance Work Statement and Performance Work Descriptions for each Order (Orders FA8750-20-F-0001, FA8750-20-F-0002, FA8750-20-F-0003, and FA8750- 20-F-0004)

(1) Section 1 (Performance Work Statement)" Is it acceptable for Offerors to discuss approaches to the individual PWS tasks in Section 1 out of sequence so long as tasks are explicitly identified per Para 1? We believe this will result in a more cohesive approach to the PWS tasks and also address the Systems Engineering Approach requirements under RIK-L009, (2)(c)(1)(i-v) without unnecessary redundancy. The Offeror also believes this approach will result in a proposal that is more clear and easier for the Government to evaluate.

Approaches to the individual PWS tasks in Section 1 can be discussed out of sequence so long as references to appropriate PWS tasks are explicitly indicated by PWS paragraph number.

45 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L009

Is it acceptable for Offerors to discuss approaches to the individual TO PWD tasks in Sections 2 - 5 respectively out of sequence so long as tasks are explicitly identified per Para 1 of RIK-L009? We believe this is necessary to provide a cohesive approach to the PWD tasks for each TO and also address the Systems Engineering Approach requirements under RIK-L009, (2)(c)(1)(i-v) for each TO without unnecessary redundancy.

Approaches to the individual PWD tasks in Sections 2 - 5 can be discussed out of sequence so long as references to appropriate PWD tasks are explicitly indicated by PWD paragraph number.

46 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L009

Para 2 states "(b) The Technical Volume shall address the Basic Performance Work Statement and Performance Work Descriptions for each Order (Orders FA8750-20-F-0001, FA8750-20-F-0002, FA8750-20-F- 0003, and FA8750-20-F-0004)" Considering the page limit placed on Volume III Technical and the Government's request that no information be duplicated between Section 1 and Sections 2-5, where Offeror's approach to a TO PWD task is identical to the approach already detailed in the associated Basic PWS Task in Offeror's Section 1 response, is it acceptable to simply state "Please see Section X for Offeror's approach to this task"?

The Government finds the suggested approach acceptable within the technical volume. In accordance with RIK-L006, no cross-referencing between volumes for essential information is permitted.

47 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L009

Para (c) states "As a minimum, each section of the Technical Volume shall address the following:"

Considering the page limit placed on Volume III Technical, where Offeror's content in response to RIK-L009 requirements (2)(c)(1), (2) and (3) is identical to the content already detailed in previous sections, is it acceptable to simply state "Please see Section X for Offeror's approach to Y"? It would be desirable to only include content that differs from previous sections based on the specific requirements of each TO.

The Government finds the suggested approach acceptable within the technical volume. In accordance with RIK-L006, no cross-referencing between volumes for essential information is permitted.

48 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L006

The instructions state that "Arial 10 or Times New Roman 11 are acceptable" for type size. Does this requirement include charts, tables, and diagrams or may smaller fonts be used for those proposal elements?

Arial 10 or Times New Roman 11 font sizes are required for charts tables and diagrams. Please note, charts, tables, & diagrams may be printed on pages not to exceed 11 x 17 inches.

49 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L009 & Attachment No. 8 - Cross Reference Matrix

The Offeror assumes (based on the statement in RIK-L009(a) on what is necessary or desirable) that the PWS/PWD sections to be specifically addressed are those listed in the cross reference matrix (RFP Attachment No. 8). Is this assumption correct? Do any sections not listed in the cross reference matrix need to be addressed?

The technical volume is required to describe, in complete detail, all aspects of the proposed program.

References in the matrix are for information purposes only and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of the Section M of the solicitation.

50 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L012 & Attachment No. 18 - Cost Proposal Pricing Template

The instructions state "Please use the appropriate tab within Section J Attachment No. 18 (Cost Proposal Pricing template) for cost proposal for first order." The bidder assumes that the whole of Volume VI would be contained within the pricing spreadsheet that is submitted as part of Volume II and, therefore, Volume VI would have no separate physical presence of its own. Is this assumption correct? If incorrect, could the Government indicate what is required separately in Volume VI?

Any cost narrative with regard to the first order should be included in the First Order (Volume VI). The First Order is not being evaluated within the Total Evaluated Price.

51 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L015 & Attachment No. 8 - Cross Reference Matrix

In what volume should the completed cross reference matrix be placed? Please include the completed cross reference matrix in Contract Forms (Volume I).

52 Proposal Due Date To properly build the installers and be able to deploy the codebase, InstallAnywhere is needed. However, we do not have a license for Install Anywhere, so problem solving and fixing the build has taken time. Also, the deployment of the VMs was not plug and play due to a lack of documentation prescribing the hypervisor /environment needed to deploy. Is it possible to receive a 2 week extension to allow us to properly evaluate the applications?

The Government denies a two week extension of the current due date.

Due to the complexity of the requirements, the Government released a DRAFT RFP five (5) months in advance of the Final RFP to allow industry the ability to review and provide feedback on any questions they might have leading up to the Final RFP.

The Government made build environments available upon request 10 days prior to the Final RFP release.

Notification that the build environments may require purchase of software licenses, such as artifactory and install anywhere, that the Government would NOT be providing was included in the FBO notice. The notice also stated that the build environments are “as is” and the Government would NOT be providing technical support.

53 Proposal Due Date The questions asked above concerning issues with the labor categories as written in Attachment 9 and discrepancies on the number of FTEs on task orders will make it difficult to obtain, analyze and complete the pricing before the current due date. Additionally, other questions may significantly affect the construct and content of a complex technical response volume.

Would the Government please consider a two week extension of the current due date to ensure that accurate pricing and a cohesive and coherent technical solution can be prepared and submitted?

The Government denies a two week extension of the current due date.

Due to the complexity of the requirements, the Government released a DRAFT RFP five (5) months in advance of the Final RFP to allow industry the ability to review and provide feedback on any questions they might have leading up to the Final RFP.

54 FA8750-19-R-0001 Basic Performance Work Statement (PWS)

Paragraph 4.3.1 lists Interface Control Document (ICD) as a deliverable which has no DD Form 1423-1.

Other than CDRL A011 in the DD Form 1423-1, there is no mention of an Interface Design Document (IDD)?

Is this a deliverable synonymous with A011 Interface Design Document (IDD)?

CDRL A011 is the Configuration Status Accounting Information which describes CM processes.

Paragraph 4.3.1 refers back to A032, the SRS, which includes the ICD. Paragraph 4.2.1 references data related information and interfaces and refers back to A010, the IDD. An IDD may describe any number of interfaces. The IDD can be used to supplement the Software Design Description (SDD) (DI-IPSC-81435).

So, yes, in this case, it is synonymous with ICD cited in paragraph 4.3.1.

55 Section L - Instructions, Conditions, and Notices to Offerors, RIK-L013

Para (c) states "Have an SCI accredited and approved Automatic Data Processing System to run SCI information. Offeror must identify in its technical proposal the location and type of SCI accredited system that will be available to the program upon contract award."

In order to have an approved SCI accredited ADP/AIS system for the GARDEM contract, award must take place first. Each ADP/AIS System that is accredited can only be used for the assigned program. Is it the government’s intention that after award, the contractor will put in place an approved system for GARDEM?

Yes, it is the Government’s intention that after award, the contractor will put in place an approved system for GARDEM; providing, in the proposal, the location and type of SCI accredited system that will be available to the program upon contract award.

56 Attachment No. 18, Cost Proposal Pricing Template

The ODC plug figure in the Excel pricing template indicates that Hardware, Software, and Cloud Services are included in the plug number. Some of these items can be burdened differently.

Can the Government provide a breakout of the ODC plug figure so that appropriate burdening may be applied?

For example, what value or percentage is Hardware and Software versus Cloud Services?

The consolidated ODC plug numbers do not include any burden costs. Burden costs for ODCs should be broken out on a separate indirect cost line within the Pricing Template, showing the base and rates used in calculations. The total ODC burden bases cannot exceed the total ODC plug amount. Details on how the application of rates and bases are developed should be included in the narrative of the cost volume.

57 Section L - Instructions, Conditions, and Notices to Offerors; RIK-L006

The requirement in the table of this section is to provide one electronic copy (CD) of Vol I and two electronic copies (CDs) for all other volumes. Below the table, there's a note that says "*In addition to the paper copies Offerors shall submit one electronic copy of each volume of their entire proposal on CD in searchable PDF format."

Can the Government please clarify the request?

Does the Government want one CD with each of the six volumes loaded onto it in PDF and Excel format?

Or does the Government want all volumes on separate CDs (11 CDs total)? For example, *One CD with just Volume I *Two CDs with just Volume II on each *Two CDs with just Volume III on each *Two CDs with just Volume IV on each *Two CDs with just Volume V on each *Two CDs with just Volume VI on each Or does the Government want two CDS with the each of the six volumes loaded onto each CD?

Submission of a total of two (2) CDs containing all Volumes is sufficient.

58 Section L - Instructions, Conditions, and Notices to Offerors; RIK-L006

"…submit one electronic copy of each volume of their entire proposal on CD in searchable PDF format."

Does the Government want the Excel/pricing files to be provided in PDF as well? Or would the Government like those files to remain in Excel so formulas can be viewed and checked?

The Government prefers to Excel/pricing files to be provided in Excel, but PDF format is also acceptable.

59 Section L - Instructions, Conditions, and Notices to Offerors; RIK-L006

"All pages shall be numbered sequentially from the first to the last page using only arabic numerals."

Can lowercase Roman Numerals be used for proposal front matter (table of contents, list of figures, other reference files) to separate those items that don't count toward overall page count from the main proposal/pages that do count toward overall page count?

The use of Roman numerals for the Tables of Contents and other front matter for each volume is allowed.

Per RIK-L006(a), “The table of contents and tabs are exempt from the page limits.”

60 Section L - Instructions, Conditions, and Notices to Offerors; RIK-L006

Is Attachment No. 18, Cost Proposal Pricing Template, included in the page count for Volume II Cost? No, the Cost Proposal Pricing Template is not part of the Cost - Volume II page count. Please note, Volume II pages should be limited to the minimum number necessary. The 50-page cost proposal is a goal not a limit. The Offeror may use additional pages if necessary to comply with public law. However, the Government will not read or evaluate deliberate attempts to circumvent the intent of page limitations.

61 Section L - Instructions, Conditions, and Notices to Offerors; RIK-L006

Does the Government require the pricing template to be included in the paper copies or electronic copies only? The Government requires both paper copies and electronic copies of the Cost Proposal Pricing Template.

62 Attachment No. 16, Past Performance Questionnaire

These pages are marked "For Official Use Only". Can we remove the markings please so we can send them through email without a password? If a particular contract is FOUO, we will add back the markings and password protect the file prior to emailing.

The Past Performance Questionnaire Template itself does not contain any FOUO information. Once the template is filled out with the information regarding the offerors past performance, it becomes FOUO/SSI.

12 February 2019