Attachment_06_-_Section_L-Instructions_to_Offerors.docx

FA4600-19-R-A001

Attachment 06 -- Section L - Instructions, conditions, and notices to offerors

TECHNOLOGY APPLICATION DEVELOPMENT AND SUSTAINMENT (TADS)

SOLICITATION SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

FA4600-19-R-A001

Attachment 06 24 June 2019

L1 GENERAL INSTRUCTIONS

L1.1 General The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. Offerors shall submit only one proposal, as the Government will review only one proposal per offeror.

L1.2 Point of Contact The contracting officer is the sole point of contact for this acquisition. All questions regarding any aspect of this solicitation must be addressed only to the contracting officer. Prospective offerors are cautioned against contacting other Government personnel about this solicitation prior to contract award. Prospective offerors are also cautioned to advise potential subcontractors or teaming contractors of this instruction. If such contact occurs and is found to be prejudicial to competing offerors, the offeror (including subcontractors or teaming contractors) making such contact may be excluded from award consideration. Information and/or any changes pertaining to the solicitation will be communicated via the Federal Business Opportunities (FedBizOpps) website.

The contracting officer for this acquisition is:

L1.3 Communications After submission of the initial proposal packages, the Contracting Officer shall control all exchanges of source selection information between the Government and offerors.

L1.3.1 Email may be used to transmit source selection information only if the email can be sent encrypted. The subject line of the email must include “Source Selection Information – See FAR 2.101 and 3.104.”

L1.3.1.1 In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted email, you will need to contact the Buyer/Contracting Officer prior to that first submittal in order to exchange certificates used for encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information).

L1.3.1.2 When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted.

L1.3.2 At the discretion of the Contracting Officer, transmittal of source selection information may be accomplished via direct mailing, the ARL Secure Access File Exchange <https://safe.arl.army.mil>, the AMRDEC Safe Access File Exchange <https://safe.amrdec.army.mil>, or other methods as directed by the contracting officer that appropriately protects source selection information.

L1.4 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 FAR 15.505. Offerors excluded from the competitive range may request a preaward debriefing or they may choose to wait until after the source selection decision to request a postaward 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 in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

L1.5 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 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.

L1.6 Electronic Reference Documents All solicitation documents are available on the Federal Business Opportunities (FedBizOpps) website at http://www.FBO.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information is posted to the website for this solicitation.

L1.7 Proposal Preparation Costs The Government will not be obligated to pay any costs incurred by an offeror in the preparation and submission of a proposal in response to this competitive Request for Proposals (RFP).

L1.8 Availability of Funds Notice to Offeror(s)/Supplier(s): Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an offeror for any costs.

L1.9 Use of Contractor Support

L1.9.1 The Government will use Quantech Services, Inc for cost analysis support during source selection and during the term of any resulting contract. Responsibility for source selection will reside exclusively with the Government.

L1.9.2 The Government will use Stellar Innovations & Solutions to support the EZSource Electronice Source Selection Tool.

L1.9.3 Proprietary information submitted in response to this solicitation will be protected from unauthorized disclosure as required by Subsection 27 of the Office of Procurement Policy Act as amended (the Procurement Integrity Act)(41 U.S.C. 423) as implemented in the FAR. The aforementioned contractors have signed Nondisclosure Agreements and Conflict of Interest Statemenst to protect proprietary information. By submitting a proposal in response to this solicitation, the offeror consents to the Government disclosing proprietary information to the aforementioned contractors for the purposes indicated.

L2 VOLUME ORGANIZATION

L2.1 General Proposals shall be submitted to the Government as set forth below:

· Volume 1 Table of Contents

· Proposal Cross Reference Matrix

· Glossary None

L2.2 Cost Information All cost or pricing data shall be addressed ONLY in the Volume 2: Cost/Price and Volume 3: Contract Documentation. Work hour estimates and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale to support a technical/management position, or unless otherwise specified.

L2.3 Page Limitations To aid in the Government’s evaluation, all proposals shall follow the same general format.

L2.3.1 Page limitations shall be treated as maximums and are specified for each volume in the table above. All pages submitted by an offeror in excess of the limitations contained in the RFP instructions will not be evaluated.

L2.3.2 The table of contents, title pages, glossary, blank pages, and the cross reference matrix do not count toward page limitations. Page limitations include charts and graphic material. The offeror shall number all pages and the numbering methodology must clearly demonstrate compliance with the page limitations shown above. Partial pages count as a full page for page limitation purposes.

L2.3.3 Page limits on revised proposals, if required, shall be provided as part of the request for revised proposals notification. Page limitations may be placed on Evaluation Notices (ENs), if issued. The specified limits for EN responses will be identified in the letters accompanying the ENs to the offerors or on the EN form itself.

L2.4 Format

L2.4.1 Page margins shall be a minimum of one (1) inch on top, bottom, and each side. Page size shall be 8.5 x 11 inches, not including foldouts. Minimum text size shall be 10-point Times New Roman standard font. Typesetting, font compression, or other techniques to reduce character size or spacing are not permitted and are considered a deliberate attempt to circumvent the page limitations. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to EN responses.

L2.4.2 Tables, charts, graphs and figures shall be used where practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be legible, uncomplicated, and shall not exceed 11 by 17 inches in size. Any page that exceeds the standard 8.5 x 11 inches size shall count as two (2) pages. Offerors may use JPEG, JPG, or PNG images for charts or screen shots. Figure call-outs (identification and titles) may be single-spaced. Embedded text shall be no smaller than 8 point Times New Roman, Arial, or Arial Narrow.

L2.4.3 Each page containing proprietary information shall be so marked.

L2.4.4 Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

L2.5 Classified Information All proposal documents shall be unclassified.

L2.6 Cross-Referencing To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

L2.7 Glossary of Abbreviations and Acronyms Each volume 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 volumes.

L2.8 Electronic Format

L2.8.1 This section is intended to provide information to the offeror on the electronic format and application software to be used for submitting soft-copy proposals. Use of the software and procedures described in this section reduces the amount of time and effort needed by the Government to receive and install proposals onto the electronic evaluation system and will help to ensure that proposals are suitable for reading electronically. The information regarding electronic productions listed below shall not be construed as Government endorsement for such products. Efforts by the Government to clarify and open electronic proposal submission in accordance with FAR 15.207(c) will not be considered discussions.

L2.8.2 Submission of the initial proposal packages via electronic mail will not be accepted. Initial proposal packages shall be either mailed or hand-delivered. Offerors are cautioned that Offutt Air Force Base has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be anticipated when hand-delivering proposal packages. Offerors are responsible for allowing for sufficient time to obtain a visitor pass and deliver proposals to the specified office PRIOR to the time specified for receipt of proposals.

L2.8.3 The sealed package used to submit the proposal package must show the time and date specified for receipt. Each volume shall be marked with the RFP number and the offeror’s name. Proposals shall be in the English language and all monies shall be proposed in United States dollars.

L2.8.4 All proposal documents shall be contained on a single disk (e.g. CD-R, CD+R, DVD-R, or DVD-R) in a format compatible with the Windows 10 operating system. No files, documents, spreadsheet, or cells shall be password protected.

L2.8.4.1 Microsoft Office documents shall be compatible with Microsoft Office 2016. Offerors shall remove macros and close any linked information used in developing spreadsheets prior to submittal. Excel spreadsheets shall include working formulas of calculations within the spreadsheet. Excel spreadsheets shall remain unaltered and unincorporated into any other format.

L2.8.4.2 PDF documents shall be compatible with Adobe Acrobat X (10.0) or later. Do not submit any documents in PDF format that are created as "images." When creating PDF files always create to enable textual search and copy functions.

L2.8.4.3 Electronic submissions may contain hyperlinks or cross-references when reference is made to other sections, tables, or figures within a given proposal volume. Offerors shall make the existence of hyperlinks or cross-references obvious by using a different font color, underlining, or other methods to highlight hyperlinks. Offerors shall not use hyperlinks or cross-references to link items between different proposal volumes, separate documents, or separate folders. This restriction is necessary because the Government will be placing electronic versions of the documents on its evaluation server, causing the previously created hyperlinks between volumes to malfunction.

L2.8.4.4 Do not submit documents using file compression software (such as .zip format).

L2.9 Paper Copies Paper copies of proposal documents are neither required nor requested.

L3 VOLUME 1: TECHNICAL

L3.1 General In Volume 1, address your technical solution for meeting or exceeding the Government’s threshold performance or capability requirements of each technical subfactor.

L3.1.1 Volume 1 should be concise, specific, and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory.

L3.1.2 By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation, but provide convincing rationale to address how the offeror intends to meet these requirements.

L3.2 Technical Risk Within each subfactor, address Technical Risk associated with those aspects of your proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, and/or the likelihood of unsuccessful contract performance.

L3.2.1 Classify each risk in accordance with M2.3, Technical Risk Rating. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance.

L3.2.2 Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: PWS or specification requirements), whether or not those requirements are identified as subfactors.

L3.2.3 For each identified risk, propose a realistic "work around" or risk mitigators that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

L3.3 Factor 1: Technical The following information shall be provided in the written technical proposal and will be evaluated to assess the proposed technical approach and associated technical risk in accordance with Section M, Evaluation Basis for Award. The written technical proposal shall address each of the following subfactors to describe the offeror’s proposed approach to performing the requirements set forth in the Performance Work Statement (PWS) or Statement of Objectives (SOO).

L3.3.1 Subfactor 1: Cyber Security Approach

L3.3.1.1 The offeror shall provide their approach to addressing all aspects of AFMAN 17-1303/DoD 8570.01 compliance while minimizing operational impacts. Their approach shall include:

i. How the offeror will ensure identified personnel are certified prior to, and maintain certification during, the life of the contract.

ii. How the offeror will provide continuing education.

iii. How the offeror will document training and certification compliance.

L3.3.1.2 The offeror shall provide their approach to patch management that addresses time-sensitive security issues while minimizing disruption to operations and maintaining system accreditation. Their approach shall explain how the offeror will handle continuous integration, blackout periods, test and evaluation periods, denied connectivity, mandatory directives, lack of vendor guidance, additional mitigation requirements.

L3.3.1.3 The offeror shall provide their approach to security testing in a DevOps environment that addresses automated testing, continuous integration, and continuous deployment processes while minimizing operational impacts. Their approach shall include:

i. How security testing is automated and incorporated into testing and evaluation.

ii. How security testing is incorporated into continuous integration and continuous deployments processes.

iii. How the offeror reports, mitigates, resolves, or writes Plan of Action and Milestone (POA&M) reports against findings.

L3.3.1.4 The offeror shall provide their process to identifying, testing, auditing, and reporting vulnerabilities in information systems/information system components that addresses the need for evaluating the impact of third-party software components. Their approach shall include:

i. How the offeror vets and verifies third-party software components using industry standards and best practices such as OWASP Application Security Verification Standards (ASVS) or other such frameworks.

ii. How the offeror supports automated testing.

iii. How the offeror supports auditing, reporting and addressing findings.

L3.3.1.5 The offeror shall provide their approach for a Secure Software Development Lifecycle that addresses all aspects of software development in a DevOps environment. Their approach shall include:

i. How automated software configuration and deployment tools are utilized to integrate and deploy software changes to target environments as part of a continuous process.

ii. How secure coding practices are incorporated into the development lifecycle.

iii. How Static and Dynamic Application Security Testing (SAST/DAST) is incorporated into the development lifecycle.

iv. How languages not supported by COTS SAST/DAST tools will be scanned for potential security findings.

v. How publically available and third-party software components are used.

vi. How integrity is maintained across the development lifecycle in the development pipeline.

vii. How security-relevant software, source code, features, and configurations used for IA or IA-enabled purposes are identified, implemented, and documented.

viii. How deficiencies discovered in the development lifecycle are resolved prior to implementing development or sustainment activities.

L3.3.1.6 The offeror shall explain their proactive approach to cybersecurity and demonstrate how their approach applies institutional knowledge and subject matter expertise.

L3.3.2 Subfactor 2: Management Approach

L3.3.2.1 The offeror shall provide a human resource management strategy that will support the execution of the program. The strategy shall address the offeror’s:

i. Integrated process to recruit, hire, and retain qualified personnel for all positions.

ii. Approach to ensure continuation of services during personnel disruptions. (e.g. sickness, leave, voluntary or involuntary termination, or employee turnover)

iii. Approach for maintaining currency of any required certifications, specialized training, security clearance tracking, and other information necessary in order to satisfy government requirements over the life of the contract.

L3.3.2.2 The offeror shall provide an agile software development process plan. The plan must explain:

i. How the offeror will meet evolving requirements while leveraging agile best practices in software development including human-centered design and automated test.

ii. How the offeror will ensure robust communication between the government and contractor.

iii. Which tools the offeror will use to track and report productivity.

iv. How status will be provided to the government.

v. How the offeror will integrate into the enterprise.

vi. How the offeror will manage and coordinate multi-site development.

L3.3.2.3 The offeror shall explain how Modular Open Systems Architecture (MOSA) principles will be applied to design/development processes. The explanation shall include:

i. How application will achieve benefits of portability, technology insertion, reusability, and scalability.

ii. How the system’s architecture exhibits modular design characteristics.

iii. How architectural description language is used to define system modules and interfaces.

iv. Hardware and software module decoupling.

v. How key interfaces are designated, use open standards, and migrate to open interfaces.

vi. Which standards will be used in the design and development processes.

vii. How software choices are made during design.

viii. How MOSA principles could be applied to legacy software.

L3.3.2.4 The offeror shall demonstrate how their organization has adopted a culture of innovation and how that culture will be applied to enhance the Air Force weather enterprise. Provide evidence that demonstrates the offeror’s experience applying this innovation culture to organizations.

L3.3.2.5 The offeror shall provide their approach to data management that describes the structured approach and proposed plan for data management throughout TADS. Their approach includes:

i. How the offeror will maintain current and accurate documentation that is sufficient for operational personnel to quickly troubleshoot, operate and sustain the Air Force weather enterprise.

ii. How the offeror will ensure all documents have correct markings to include data rights, distribution statements, security classification, and export restrictions.

iii. How the offeror will provide enduring and unimpeded government access to all documents produced for TADS.

L3.3.2.6 All offerors shall provide their Small Business Participation approach.

The Small Business Participation approach is separate from the Small Business Subcontracting Plan required by FAR 52.219-9; offerors shall not utilize the Small Business Subcontracting Plan in to replace the Small Business Participation approach. The offeror’s approach shall describe:

i. The complexity and variety of the work small businesses are to perform.

ii. The extent of participation of such firms in terms of the total TADS acquisition value over the life of the contract.

iii. Explain how the proposal demonstrates a realistic approach to meet or exceed TADS small business subcontracting goal.

iv. The offeror’s experience applying the proposed approach while successfully meeting small business subcontracting goals.

L3.3.2.7 The offeror shall describe its systems engineering and integration approach to include:

i. How the offeror will perform analysis and planning processes to pursue and evaluate new technology or expand capabilities.

ii. How the offeror’s processes for requirements analysis, requirements traceability, and operational analysis address evolving and dynamic requirements.

iii. How the offeror will perform software engineering processes and how the offeror will apply those processes in an agile environment.

iv. How the offeror will perform logistics support analysis.

v. How the offeror will perform configuration management processes with multiple contractors conducting development using similar baselines, and rapid and frequent deliveries in multiple security enclaves.

vi. How the offeror will manage the technical baseline and keep it current.

vii. How the offeror plans to integrate subsystems including those created or modified off-site.

viii. How the offeror measures the success of systems engineering processes.

L3.3.3 Subfactor 3: Transition & Sustainment

L3.3.3.1 The offeror shall provide a Transition Plan, which shall be incorporated into Task Order 01. The proposed Transition Plan shall:

i. Identify how the offeror shall ensure continuity of operations and no system degradation of performance on contract full performance date.

ii. Specify transition schedules and milestones to ensure no disruption of service.

iii. Describe the method for processing and assigning tasks during the transition period.

iv. Indicate staffing approach and allocation to tasks.

v. Describe how the offeror will obtain personnel with required skill sets, IT and cybersecurity certifications, and personnel security clearances from award to start of full performance.

L3.3.3.2 The offeror shall describe their process to meet the subsystem operational availability and operational dependability requirements in the Task Order 01 PWS and Services Summary (solicitation Attachment 9b), and Services Requirements Summary (solicitation Attachment 9c) to include:

i. How the offeror will meet on-call response objectives.

ii. How the offeror will manage licenses.

iii. How the offeror will manage vendor support agreements.

iv. How the offeror will integrate software maintenance, hardware maintenance, and systems administration services to correct deficiencies.

L3.3.3.3 The offeror shall describe their approach to:

i. Perform hardware maintenance in accordance with Task Order 01 PWS para 2.4.1 and Services Summary. (solicitation Attachment 9b)

ii. Manage hardware replacements to ensure subsystems meet the operational availability and operational dependability requirements in the Task Order 01 Services Requirements Summary. (solicitation Attachment 9c)

L3.3.3.4 The offeror shall describe its sustainment systems analysis processes including:

i. How the offeror will perform root cause analysis and fault isolation.

ii. How the offeror will perform trend analysis to identify systemic issues.

iii. How the offeror will identify deficiencies and recommend corrective actions.

L3.3.3.5 The offeror shall describe its sustainment configuration management processes including:

i. How the offeror will capture and coordinate corrective changes to the production baseline.

ii. How the offeror will correct the baseline for corrective changes when other contractors have updated the baselines of interest.

L3.3.3.6 The offeror shall describe its systems administration processes including:

i. How the offeror will install/maintain operating systems and applications to meet the subsystem operational availability and operational dependability requirements in the the Task Order 01 PWS and Services Summary (solicitation Attachment 9b) and Services Requiremts Summary (solicitation Attachment 9c).

ii. How the offeror will manage accounts and coordinate with the Government.

iii. How the offeror will respond to and meet mandatory directive due dates.

L3.3.3.7 The offeror shall describe its processes to implement corrective software changes including:

i. How the offeror will work with appropriate stakeholders to identify corrective changes to software baselines.

ii. How the offeror will identify performance issues and collaborate with appropriate stakeholders for recommended corrective actions.

iii. How the offeror will meet the subsystem operational availability and operational dependability requirements in the Task Order 01 PWS and Services Summary (solicitation Attachment 9b) and Services Requiremts Summary (solicitation Attachment 9c).

L3.3.4 Subfactor 4: CAF Development & Integration

L3.3.4.1 The offeror shall provide a process for error and deficiency tracking and correction. The process shall include the following:

i. Identification of any meteorological or software errors or deficiencies found either previously existing or in the course of development.

ii. An assessment of the impact of any errors or deficiencies.

iii. Error/deficiency tracking so that all documentation concerning errors and deficiencies can be readily accessed, viewed, and prioritized by Government.

iv. An outline of discreet steps to resolve the errors/deficiencies to include level of effort.

L3.3.4.2 The offeror shall provide a process for providing continuous improvement and development of new or enhanced capabilities and data sources across multiple security enclaves. The process shall include:

i. A process for evaluating any new methodology.

ii. Metrics to quantitatively and qualitatively assess any new capability or enhancement.

iii. New and expanding definitions of clouds.

iv. An accommodation process for multiple mission sets within the current environment of operational software packages.

L3.3.4.3 The offeror shall provide a process that ensures that all scientific enhancements are referenced, documented, and provided to the government. The process shall include:

i. How scientific journals, reviewed papers, and communication with Subject Matter Experts (SMEs) will be documented.

ii. Methods for peer review and timeliness of documentation delivery.

L3.3.4.4 The offeror shall provide a process for release documentation and training deliverables. The process shall include:

i. What documentation will be produced.

ii. How the documentation approach will ensure sufficient quality.

iii. How the documentation approach considers Government operators and sustainment personnel who may not be familiar with the delivered software.

L3.3.4.5 The offeror shall provide an outline for the utilization of a sandbox testbed environment. The outline shall include:

i. How developed software components will be maintained within the sandbox environment to ensure support for operational baselines.

ii. A methodology for determining which past baselines will be maintained for potential use in case studies.

iii. An outline for what types of archival datasets to be saved as a common benchmark for case studies and comparisons between baselines.

L3.3.4.6 The offeror shall provide a plan to obtain proper scientific expertise. The plan shall include:

i. How to recruit and retain expertise in the areas of cloud analysis, Numerical Weather Modeling, data assimilation, and satellite remote sensing.

ii. Explanation for how the offeror will utilize the expertise.

L3.3.4.7 The offeror shall provide an Agile Epic formatted case study on their choice of an enhancement of a current capability or newly prototyped capability for CAF that could be completed during the base period of performance. The case study shall be delivered as “Volume 1 Appendix: Task Order 02 – Agile Epic”.

L4 VOLUME 2: COST/PRICE

L4.1 Introduction

L4.1.1 This section is to assist you in submitting data other than certified cost or pricing data in accordance with FAR 15.403-3. The Government requires this data to evaluate the reasonableness, realism and balance of the offeror’s proposed costs/prices. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally reference FAR 15.404-1(g), unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. The burden of proof for credibility of proposed costs/prices rests with the offeror.

L4.1.2 The Contracting Officer determined there is a high probability of adequate price competition in this acquisition. Therefore, a Certificate of Current Cost or Pricing Data per FAR 15.403-4 will not be required. In the event that adequate competition does not emerge in response to the solicitation, and no other exception to certified cost or pricing data requirements applies, the Contracting Officer may require certified cost or pricing data in accordance with FAR 15.4.

L4.1.3 Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price position.

L4.2 General Instructions The offeror shall provide data other than certified cost or pricing data and supporting rationale to demonstrate the reasonableness, realism and balance of its proposed costs/prices. The offeror shall provide sufficient detail to demonstrate proposed costs/prices are sufficient for the work required, reflect a clear understanding of the requirements and are consistent with the unique methods of performance and materials described in its proposal. The offeror shall base its proposal on its Contractor Fiscal Year (CFY). The offeror shall provide an accounting calendar covering all periods of performance and delivery dates included in its proposal, including showing the start and end of its CFYs.

L4.2.1 Estimating Techniques and Methods When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the work breakdown structure (WBS). The offeror shall identify all ground rules and assumptions used in developing the cost documentation. These assumptions shall include, at a minimum, any conditions, constraints or expectations upon which the offeror’s cost/price proposal is based

L4.2.2 Rounding The offeror shall round all dollar amounts to the nearest dollar, except for labor rates; the offeror shall round all labor rates to the nearest penny. The offeror shall round Overhead Rates, Fringe Rates, General and Administrative (G&A) Rates, Cost of Money Rates and any other factors it uses to the third digit after the decimal when the factor is expressed as a percentage.

L4.2.3 Subcontractor/Interdivisional Transfer (IDT) Cost Proposals

L4.2.3.1 Major subcontractors, IDTs, teaming partners and joint venture partners shall submit separate Cost/Price volumes. For each Order in the solicitation, on an Order-by-Order basis, a major subcontractor, IDT, teaming partner or joint venture partner is one whose share exceeds either 10 percent (10%) of the total price (at target) of that order or $2,000,000, whichever is greater. For any subcontractor, IDT, teaming partner or joint venture partner required to submit a separate Cost Price volume, the team member shall submit a single proposal that addresses all of the required elements for each of the orders on which it qualifies as a major subcontractor, IDT, teaming partner or joint venture partner. The major subcontractor, IDT, teaming partner or joint venture partner may omit Cost/Price volume elements that do not apply to their workshare. For any subcontractor, IDT, teaming partner or joint venture partner required to submit a separate Cost Price volume, the team member’s BOE information shall be integrated into the offeror’s BOEs.

L4.2.3.2 If a subcontractor, IDT, teaming partner or joint venture partner considers any portion of its cost information proprietary, it may submit that portion of the documentation under separate cover directly to the contracting officer or under seal in the offeror’s proposal. The offeror’s proposal, however, shall uniquely identify all subcontractor, IDT and other subcontractor labor hours and total burdened costs. The offeror shall ensure the Government receives all required subcontractor data by the proposal submission deadline. The offeror is responsible for the consistency of the cost data between its submission and the subcontractor, IDT, teaming partner or joint venture partner submissions.

L4.2.3.3 In accordance with FAR 15.404-3(b), for all proposed subcontracts, IDTs (including transfers of commercial items between divisions, subsidiaries, or affiliates of a contractor or a subcontractor), teaming partners and joint venture partners, the offeror shall conduct appropriate cost or price analyses and provide the results as part of its proposal. These analyses must describe the evaluation rationale that led to the offeror’s conclusion that the subcontract cost or price is fair and reasonable. The offeror shall identify and explain any price adjustments made to the proposed prices of the subcontractors, IDT, teaming partner or joint venture partner submissions, other subcontractors and vendors that the offeror has included in its proposal. These price adjustments shall include discounting or expected decreases to be achieved in negotiations.

L4.2.3.4 If the offeror’s normal accounting practice applies (and invoices for) indirect burdens against subcontract and vendor costs, then the offeror shall include all applicable indirect burdens on all subcontract and vendor costs included in its proposal. If the offeror chooses not to apply indirect burdens against subcontract and vendor costs or to deviate from the offeror’s standard practice, then the offeror shall propose a Section H clause to identify this special term and condition.

L4.3 Conditions, Constraints, Assumptions & Government-Established Amounts In preparing its proposal, the offeror shall consider the following information.

L4.3.1 Task Order 01 Transition & Sustainment This section shall be used to price the Transition and Sustainment as described by solicitation Attachment 9a, Attachment 9b, Attachment 9c, Attachment 9d, Attachment 9e, and the offeror’s response to Factor 1.

L4.3.1.1 Conditions, Constraints & Assumptions:

1. The proposal for Task Order 01 Transition and Sustainment is awardable.

2. The 1-year base period consists of a 3-month transition plus 9 months of full performance. Data CLIN 0008 (not separately priced) spans the entire base year.

3. Start date for transition is anticipated to be 1 April 2020.

4. The TADS contractor will have to work with the incumbent SEMS III contractor to successfully transition into full performance.

5. The SEMS III contractor will be responsible for enterprise maintenance during the entire 3-month transition period.

6. Government-directed software licenses, spare parts and support agreements (to include extended warranties) will be accounted for on the cost reimbursable (no fee) CLINs X006.

7. For pricing purposes, assume the tasks and systems described by the Task Order 01 PWS (solicitation Attachment 9b) and Services Requirements Summary (solicitation Attachment 9c) have to be supported for the entire life of TADS.

8. The Government’s estimated labor workload for Task Order 01 is provided as solicitation Attachment 9f.

9. Per FAR 52.217-8, all CLIN prices for the six-month extension period shall be proposed as 50% of the price for Option Year 4.

L4.3.1.2 Government-Established Amounts

1. Cost Reimbursable CLINs X006 have Government-populated direct costs of:

Base Year Option Year 1 Option Year 2 Option Year 3 Option Year 4 Six-Month Extension Total Direct Costs

These amounts include Government-directed software licenses, support agreements, spare parts, and extended warranties.

If the offeror’s normal accounting practice applies (and invoices for) burdens against miscellaneous direct costs, then the offeror shall propose the Government-populated amount plus the addition of all applicable burdens such as G&A, material handling, and Facilities Capital Cost of Money.

If the offeror chooses not to burden cost reimbursable CLINs or to deviate from the offeror’s standard practice, then the offeror shall propose a Section H clause to identify this special term and condition.

2. Cost-Plus Fixed Fee CLINs X003 have Government-populated Direct Productive Labor Hours of:

Base Year Option Year 1 Option Year 2 Option Year 3 Option Year 4 Six-Month Extension

Solicitation Attachment 9a includes clause H-6 “Level of Effort (Cost-Plus-Fixed-Fee, Term)” which defines Direct Productive Labor Hour.

These Direct Productive Labor Hours are stated in the extended CLIN descriptions of Task Order 01, Section B.

L4.3.2 Task Order 02 CAF Development & Integration This section shall be used to price the CAF Development & Integration as described by solicitation Attachment 10a, Attachment 10b, Attachment 10c, Attachment 10d, and the offeror’s response to Factor 1.

L4.3.2.1 Conditions, Constraints & Assumptions:

1. The proposal for Task Order 02 CAF Development and Integration is awardable.

2. Start date is anticipated to be 1 July 2020.

3. The sandbox/OSE testbed environment (L3.3.4.5) will be provided as a Government-furnished environment using Amazon Web Services GovCloud. The following tools will be provided at no cost to the offeror:

· JIRA

· Trello

· Packer

· ANSIBLE

· Cloudformation

· Terraform

· Vormetric

· OpenSCAP

· CloudTrail

· Twistlock

· ClamAV

· AWS WAF

· Splunk

· Amazon Cloudwatch

· DISA HBSS, ACAS, & CSSP

· NeuVector

· Xacta 360

· Confluence

· Contrast Security

· ThreadFix

· Se

· Sonarqube

· Jenkins

· Artifactory

· Maven

· Git

4. The contractor will be provided updated software source code and data upon task order start.

L4.3.2.2 Travel

Cost Reimbursable CLINs X006 have Government-populated direct costs of:

Base Year Option Year 1 Option Year 2 Option Year 3 Total Direct Costs

If the offeror’s normal accounting practice applies (and invoices for) burdens against travel costs, then the offeror shall propose the Government-populated amount plus the addition of all applicable burdens such as G&A, material handling, and Facilities Capital Cost of Money.

If the offeror chooses not to burden cost reimbursable travel CLINs or to deviate from the offeror’s standard practice, then the offeror shall propose a Section H clause to identify this special term and condition.

L4.3.2.3 Miscellaneous Direct Costs Although the Government has no known requirements for miscellaneous direct costs, offerors are invited to propose miscellaneous direct costs needed to support their technical approach.

L4.3.3 Model FFP CLINs 0001 and 1001 Pricing

L4.3.3.1 This section is for building the Total Evaluated Price (TEP) and to establish IDIQ Section G terms and conditions.

L4.3.3.2 The offeror shall propose the profit rate that will be applied against all future FFP efforts on the TADS contract.

L4.3.4 Model CPFF CLINs 0002 and 1002 Pricing

L4.3.4.1 This section is for building the TEP and to establish IDIQ Section G terms and conditions.

L4.3.4.2 The offeror shall propose the fixed fee rate that will be applied against all CPFF line items for experimental, developmental, or research efforts. In accordance with FAR 15.404-4(c)(4)(i) and statutory limitations imposed by 10 U.S.C. 2306(d), the fixed fee rate shall not exceed 15 percent.

L4.3.5 Model CPFF CLINs 0003 and 1003 Pricing

L4.3.5.1 This section is for building the TEP and to establish IDIQ Section G terms and conditions.

L4.3.5.2 The offeror shall propose the fixed fee rate that will be applied against all CPFF line items for maintenance or sustainment efforts. In accordance with FAR 15.404-4(c)(4)(i) and statutory limitations imposed by 10 U.S.C. 2306(d), the fixed fee rate shall not exceed 10 percent.

L4.3.6 Model CPIF CLINs 0004 and 1004 Pricing

L4.3.6.1 This section is for building the TEP and to establish IDIQ Section G terms and conditions.

L4.3.6.2 The offeror shall propose the rates for target fee, maximum fee, minimum fee, overrun share, and underrun share that will be applied against all CPIF line items for experimental, developmental, or research efforts.

L4.3.7 Model CPIF CLINs 0005 and 1005 Pricing

L4.3.7.1 This section is for building the TEP and to establish IDIQ Section G terms and conditions.

L4.3.7.2 The offeror shall propose the rates for target fee, maximum fee, minimum fee, overrun share ratio, and underrun share ratio that will be applied against all CPIF line items for maintenance or sustainment efforts.

L4.3.8 Model High-Dollar Materials CLINs 0007 and 1007 Pricing

L4.3.8.1 This section is for building the TEP and to establish IDIQ Section G terms and conditions.

L4.3.8.2 The offeror shall propose the rates for target profit and ceiling that will be applied against all orders with FPIF line items.

L4.4 Volume Content The offeror shall provide comprehensive narrative support for its cost proposal. The offeror shall provide a consolidated Cost/Price volume that includes all required data, formats, BOM elements, BOE elements, etc.

L4.4.1 Volume Organization The offeror shall organize the Cost/Price volume according to the following general outline:

L4.4.2 Section 1 – General Information The offeror shall prepare an introduction to the Cost/Price volume. The offeror shall also provide summary descriptions of its estimating, purchasing and accounting systems. If applicable, the offeror shall identify changes to approved/disclosed estimating, purchasing or accounting systems or its Cost Accounting System (CAS) Disclosure Statement.

L4.4.2.1 Estimating System Summary The offeror shall provide a summary description of their standard estimating system or methods. The summary description shall cover separately each major cost element (e.g., Direct Labor, Indirect Costs, Other Direct Costs, Overhead, G&A). The offeror shall also identify any deviations from their standard estimating procedures in preparing this proposal volume. The offeror shall indicate if the Government has approved the estimating system and if so, provide evidence of such approval.

L4.4.2.2 Purchasing System Summary The offeror shall provide a summary description of their purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). The offeror shall also identify any deviations from their standard procedures in preparing this proposal. The offeror shall indicate if the Government has approved the accounting system and if so, provide evidence of such approval.

L4.4.2.3 Accounting System Summary The offeror shall provide a summary description of their accounting system and identify any deviations from their standard accounting procedures. The offeror shall also identify any deviations from their standard procedures in preparing this proposal. The offeror shall indicate if the Government has approved the your accounting system and if so, provide evidence of such approval.

L4.4.2.4 Earned Value Management System (EVMS) Summary In accordance with DFARS 252.234-7001, Notice of Earned Value Management System (Deviation 2015-O0017)(Sep 2015), the offeror shall provide documentation that the Cognizant Federal Agency has determined that the EVMS complies with the EVMS guidelines in the American National Standards Institute/Electronic Industries Alliance Standard 748, Earned Value Management Systems (ANSI/EIA-748). If the offeror does not have formal verification documentation, the offeror shall provide their plan to obtain verification.

L4.4.3 Section 2 – Cost/Price Proposal

L4.4.3.1 Cost Proposal Summary The offeror shall provide a summary of the cost proposal, including a summary of all priced CLINs.

L4.4.3.2 Ground Rules and Assumptions The offeror shall explain all the ground rules and assumptions used to develop the proposed costs and prices. Describe any assumptions with regard to Government actions (e.g., providing resources whether it be equipment or people) that enabled the proposed price/cost to be lower and identify the amount by which it is lower. Ground rules and assumptions addressed elsewhere do not need to be addressed again in this volume unless there are unique aspects related to costs/prices that are not addressed in other sections.

L4.4.3.3 Explanation of Estimating Methods Used Explain the methodology used to estimate each cost element. As a minimum, provide the following information for each cost element. If a portion of the required information is not applicable for a particular cost element, so state.

L4.4.3.3.1 Direct/Indirect Rates The offeror shall use and submit Forward Pricing Rate Agreements (FPRAs), Collective Bargaining Agreements (CBAs), and Area Wage Determinations (AWDs) if applicable. The Offeror shall identify whether the labor rates proposed are FPRAs, CBAs, AWDs, DCMA/DCAA recommended rates, or offeror-proposed rates. The offeror shall provide information necessary to substantiate the rates proposed such as a complete copy of the signed FPRA, complete copy of the CBA, complete copy of the AWD, or other documentation as applicable.

L4.4.3.3.2 Escalation Rates The offeror shall identify the…