DRAFT_BAA_12-21-15.docx

COMBATING TERRORISM TECHNICAL SUPPORT OFFICE/

Technical Support Working Group

(CTTSO/TSWG)

BROAD AGENCY ANNOUNCEMENT (BAA)

16-Q-XXXX

Due Date for Receipt of Phase 1 Quad Charts:

No Later Than March 18, 2016 All submissions are due by 1500; 3:00 p.m.

Eastern Time (ET) on the above date

AAC – Advanced Analytic Capabilities CBRNE – Chemical, Biological, Radiological, Nuclear, and Explosives IDD/EC – Improvised Device Defeat/Explosives Countermeasures IFS - Investigative and Forensic Science IW/ET – Irregular Warfare and Evolving Threats PP – Personnel Protection PS – Physical Security SCOS – Surveillance, Collection, and Operations Support TOS – Tactical Operations Support TTD – Training Technology Development

The Broad Agency Announcement Information Delivery System (BIDS) is the system in which all submissions and communications will flow. Communications outside of BIDS may result in expulsion from the competition.

TSWG BAA 04-Q-XXXX BAA PACKAGE

7/20/04

16-Q-XXXX BAA Package December 21, 2015

TABLE OF CONTENTS

1. INTRODUCTION.

This is a Combating Terrorism Technical Support Office (CTTSO) Broad Agency Announcement (BAA) issued under the provisions of paragraph 6.102(d)(2)(i) of the Federal Acquisition Regulation (FAR) to provide for the competitive selection of research proposals. Contracts based on responses to this BAA are considered to be the result of full and open competition and in full compliance with the provisions of Public Law (PL) 98-369 Section 2701, “The Competition in Contracting Act.” Awards for submissions under this BAA are planned for Fiscal Year (FY) 2017. Funds may not be available for all requirements under this BAA. No contract awards will be made until appropriated funds are available from which payment for contract purposes can be made.

1.1. Approach.

A three-phased proposal selection process will be used for this BAA to minimize cost and effort for prospective offerors:

· Phase 1 will consist of the solicitation, receipt, and evaluation of a one-page Quad Chart.

· Phase 2 will consist of the solicitation, receipt, and evaluation of a White Paper and applies to only those submissions that have been accepted in Phase 1.

· Phase 3 will consist of the solicitation, receipt, and evaluation of a Full Proposal and applies to only those submissions that have been accepted in Phase 2. Based on the priority of critical requirements and the availability of funding, Phase 1 submissions can be selected for Phase 3 without a Phase 2 submission.

Clarifications to White Papers and Full Proposals may be requested.

1.2. HBCU, MI, and Small Business Set Aside.

The Government encourages nonprofit organizations, educational institutions, small businesses, small disadvantaged business (SDB) concerns, Historically Black Colleges and Universities (HBCU), Minority Institutions (MI), women-owned businesses, and Historically Underutilized Business zone enterprises as well as large businesses and Government laboratories to submit research proposals for consideration and/or to join others in submitting proposals; however, no portion of the BAA will be set aside for these special entities because of the impracticality of reserving discrete or severable areas of research and development (R&D) in any specific requirement area. A goal of 2.5 percent of total dollars awarded will be considered for HBCU and/or MI, and a goal of 2.5 percent of total dollars awarded will be considered for small businesses for a total goal of 5 percent. The final determination will be made based on the individual technical merits of the proposal and budget constraints within the mission priorities. To ensure full consideration in these programs, registration in the BAA Information Delivery System (BIDS), described later in this document, requires the appropriate business type selection as well as accurate up-to-date information.

1.3. Limitation of Funds.

The Government intends to incrementally fund Cost Reimbursable contracts awarded from this BAA as provided by FAR 52.232-22, “Limitation of Funds.” Most contracts awarded are anticipated to be 6 to 24 months in duration. To facilitate incremental funding, submissions shall include the cost and schedule by a task-phased structure with clear exit criteria, and shall be inclusive of all work to complete the effort including any options. It is anticipated that the entire effort will be negotiated with the initial contract award.

[Note: Based upon the availability of funding, the Government may have to partially fund Fixed Price contracts in accordance with DFAR 252.232-7007, “Limitation of Government’s Obligation”. In such cases, milestone payments will need to be a part of the full proposal. Applicability of this issue will be stated in the email asking for a Phase III proposal.]

1.4. Technical Evaluation Support.

It is the intent of this office to use contractor support personnel in the review, evaluation, and administration of all submissions for this BAA. All contractor support personnel will have access to proprietary data and shall certify that they: (1) will not disclose any information pertaining to this solicitation including any submission, the identity of any submitters, or any other information relative to this BAA; and (2) have no financial interest in any submissions evaluated, reviewed, and administered. Submissions and information received in response to this BAA constitutes permission to disclose that proposal data to certified evaluators under these conditions.

1.5. BAA Package Download.

This BAA Package can be downloaded electronically in its entirety from https://bids.cttso.gov/ under BAA Information. Registration is not required to download the BAA package; however, a BIDS registration is required to upload a response to the BAA.

1.6. BAA Contractual and Technical Questions.

All contractual and technical questions regarding this BAA, including the published requirements and instructions, must be directed to the Contracting Officer at BIDSHelp@cttso.gov. No other office personnel will acknowledge, forward, or respond to any inquiries received in any manner concerning the BAA. Contractual questions and answers will be posted periodically under BAA Questions on the BIDS website. All questions must be received at least 72 hours prior to close of the submission.

1.7. BIDS Website Help Requests.

For technical help using BIDS, submit questions to the BIDS administrators at BIDSHelp@cttso.gov or by using the Request Help link located on the BIDS Homepage. Include a valid email address, your BIDS User Name, and a detailed description of the question or concern in the comments block. The BIDS Website provides other valuable resources under Online Help and Useful Links, such as Prerequirements for Working with the Government.

Reference documents including the BIDS Submitter Quickcard and Quad Chart Sample are available for download under Reference Materials. Information regarding compliance requirements for using humans and animals in testing is also available from BIDS.

1.8. BIDS Frequently Asked Questions (FAQs).

FAQs are a list of questions and associated responses for general and specific topics. Offerors are encouraged to periodically review BAA Questions located at https://bids.cttso.gov.

NOTE: Persons submitting proposals are advised that only the Contracting Officer can obligate the Government to any agreement involving expenditure of Government funds.

2. GENERAL INFORMATION.

This section includes information applicable to all awards under this BAA.

2.1. Eligibility.

To be eligible for contract award, a responsible offeror must meet certain minimum standards pertaining to financial solvency and resources, ability to comply with the performance schedule, prior record of satisfactory performance, integrity, organization, experience, operational controls, technical skills, facilities, and equipment. See FAR 9.104.

· All offerors must be registered in the System for Award Management (SAM) database at https://www.sam.gov/portal/public/SAM/.

These and other helpful links are also provided on the BIDS Homepage.

2.2. Procurement Integrity, Standards of Conduct, Ethical Considerations.

Certain post-employment restrictions on former federal officers and employees exist including special Government employees (Section 207 of Title 18, United States Code (U.S.C.)). If a prospective offeror believes that a conflict of interest exists, the offeror should make this known to the Contracting Officer for resolution before time and effort are expended in preparing a proposal.

2.3. Reserved.

2.4. Restrictive Markings on Proposals.

All proposals should clearly indicate content disclosure limitations. Submissions can be marked as “Proprietary” or words to that effect; however, markings such as “Company Confidential” or other phrases that could be confused with national security classifications shall not be used. All paragraphs that contain proprietary information must be clearly marked. The Contracting Officer may challenge proprietary markings if they are not substantiated.

2.5. Submission Handling/Rights in Technical Data and Computer Software/Patent Rights.

2.5.1. Procurement Integrity.

The Government shall comply with FAR 3.104 in its treatment of information submitted in response to this BAA solicitation and marked with the individual’s or company’s legend.

2.5.2. Submission Information and FOIA.

Records or data bearing a restrictive legend can be included in the proposal. However, the offeror is cautioned that portions of the proposal are subject to release under the terms of the Freedom of Information Act (FOIA), 5 U.S.C. 552, as amended. In accordance with FOIA regulations, the offeror will be afforded the opportunity to comment on, or object to, the release of proposal information.

2.5.3. Rights in Technical Data and Computer Software.

Rights in technical data and computer software and software documentation provided in the proposal are treated in accordance with the Department of Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7016, “Rights in Bid and Proposal Information.” Rights in technical data, and computer software and computer software documentation in the resultant contract shall be in accordance with DFARS 252.227-7013 (regarding technical data) and DFARS Section 252.227-7014 (regarding computer software and software documentation). Both clauses (DFARS sections 252.227-7013 and 252.227–7014) will be included in any noncommercial contract exceeding the simplified acquisition threshold. Table 1 contains these and related clauses that may be included in the contract.

Table 1. Contract Clauses

2.5.4. Patents.

Patents in existence and patent applications pending at the time of the proposal, that relate to the proposed effort, shall be identified in the White Paper and Full Proposal in accordance with the clauses above.

2.6. Product and Deliverable Requirements.

All proposal phases shall include the costs for products and data deliverable requirements. Minimum data (report) requirements include Monthly Status Reports (MSRs) and a Final Technical Report even if the research is to be continued under a follow-on contract or contract option. MSRs document program, technical, and financial status. The Final Technical Report summarizes the project and associated tasks at the conclusion of each contract. Include MSRs, the Final Technical Report, and any products and deliverables specific to the performance of the proposed effort (e.g., system specification). The Government will provide the offeror with a full listing of data deliverables (i.e., Contract Data Requirements List) in the request for Phase 3 Full Proposal. Additional products and deliverables could include prototype hardware, software, or systems; test plans; test and technical reports; technical data; specifications; requirements documents; computer programs or software; user manuals; drawings; or other products and data. The number, types, and preparation instructions for products and deliverables will be specified in the contract.

2.7. Distribution/Release Limitations.

The offeror should be aware that all resulting contracts or other awards will contain release limitations for all data resulting from the effort in accordance with DFARS 252.204-7000. This includes products, data, information, and services to be performed. The contractor shall protect all data and information from disclosure, and shall not release any data or information by any method of dissemination without prior Government approval.

2.8. Subcontracting.

Pursuant to Section 8(d) of the Small Business Act (15 U.S.C. 637(d)), it is the policy of the Government to enable small business and small disadvantaged business concerns to be considered fairly as subcontractors to contractors performing work or rendering services as prime contractors or subcontractors under Government contracts, and to assure that prime contractors and subcontractors carry out this policy.

2.9. Animal or Human Testing Compliance.

The contractor shall comply with all laws and regulations governing the use of animals or human subjects in research projects.

2.9.1. Animal Testing.

Any contract resulting from this BAA that potentially involves the testing of animals shall include the following language:

Any contractor performing research on warm blooded vertebrate animals shall comply with the Laboratory Animal Welfare Act of 1966, as amended, 7 U.S.C. §§ 2131 - 2159, and the regulations promulgated thereunder by the Secretary of Agriculture in 9 C.F.R. Parts 1 through 4, pertaining to the care, handling, and treatment of vertebrate animals held or used for research, teaching, or other activities supported by Federal contract awards. In addition, the contractor shall comply with the provisions of Department of Defense Directive (DoDD) 3216.1, as implemented by SECNAVINST 3900.38C, and DFARS 252.235-7002, “Animal Welfare,” which is incorporated into this contract.

2.9.2. Human Subjects Testing.

Any contract resulting from this BAA that potentially involves the use of Human Subjects in the research or study shall include the following language:

The contractor shall comply with all regulations promulgated by the Office of the Secretary of Defense in 32 C.F.R. Part 219, pertaining to the protection of human subjects. In addition, the contractor shall comply with the provisions of DoDI 3216.02. If human subjects are to be used at any time during the project, the contractor shall have a Federal assurance that is acceptable to CTTSO before involving human subjects. Additionally, the protocol shall be approved by a Federally-assured Institutional Review Board (IRB) office named in the institution’s assurance. The contractor shall prepare these documents and shall ensure that they are on file with CTTSO prior to the start of research involving human subjects. Collaborators with the contractor, to include IRBs, shall also comply with regulations to protect human subjects for both classified and unclassified research. The contractor shall report all changes in the protocol or consent form to the CTTSO Contracting Officer’s Representative as they occur. Release of initial and follow-up funding will be contingent upon initial and continuing reviews, and to other IRB and component requirements.

3. PROPOSAL PREPARATION.

This section provides information and instructions for the preparation and submission of all phases under this BAA. All submissions must meet these requirements including format, content, and structure, and must include all specified information to avoid disqualification, submission rejection, or delays in evaluation.

3.1. BAA Information Delivery System (BIDS).

BIDS at https://bids.cttso.gov/ is used: (1) to provide public access to the BAA package; (2) to collect all unclassified submissions; and (3) to collect placeholder records for all classified submissions. BIDS also provides submission progress tracking, evaluation comment collection, and results notification back to the submitter.

3.1.1. Submitter Registration.

A BIDS submitter registration is required to respond to this BAA. Existing BIDS accounts are acceptable for a new BAA if the company contact information is the same or is corrected. Registrations should reflect the offeror’s contracting or business authority. The User Name, created by the offeror, must be unique and is used for BIDS login and submission tracking. Registration acceptance for submitters is automatic, but takes several seconds to be recognized by BIDS. A success email will be sent to indicate that the User Name and account are accepted. BIDS is email dependent and uses the Registration email as the single point of contact (POC) for all notifications associated with the BAA. This email address should be monitored frequently during the BAA process for the notices. Submitters should periodically check status in their account, not receiving a notification email does not constitute grounds to appeal an evaluation decision. Spam blockers and other email security software may cause a notification email to be rejected; check your account. Email addresses included in the submissions or any other data field in BIDS will not be used for contact and notification purposes.

3.1.2. User Accounts and Password Resets.

Registration account information such as the POC, email, and password can be updated after login. The “Forgot Password?” link on the BIDS Homepage allows registered users with a valid email address to automatically reset a password. The system will verify the account User Name and email to send a new password to that email.

3.1.3. Registration and Account Help.

BIDS Help requests can be emailed to BIDS administrators at BIDSHelp@cttso.gov or submitted via the Request Help link located on the BIDS Homepage.

3.1.4. Document Identifier.

The offeror shall include the document identifier in the header of each submission. Document identifiers must match the BIDS submission record and should be constructed before upload to BIDS.

3.1.4.1. Constructing Document Identifiers.

Document identifiers, auto-generated in part by BIDS, are based on Subgroup or Mission Area, the requirement number, the user name, and a Submitter Internal Tracking (SIT) number. The underlined portion of the sample shown in Table 2 depicts the segment automatically formed by BIDS.

Table 2. Sample Document Identifier and Components Definition

CB-1112-ABCCORP-10703JT-QC

3.1.4.2. Creating Submitter Internal Tracking (SIT) Numbers.

SIT numbers are unique identifiers created by submitters and entered in the submission record during the upload process. SIT numbers can be any alphanumeric combination (no special characters or spaces) chosen by the submitter plus a suffix indicating the document type. BIDS enforces unique SIT numbers and will not allow the submission record to be saved if the SIT number has already been used. Table 3 provides sample SIT numbering formats for each document type.

Table 3. Sample SIT Numbers for an Accepted Submission

Offerors uploading more than one submission to the same requirement shall create unique identifiers by adding a numbered sequence to the document type suffix. Table 4 offers sample SIT number formats for multiple submissions to the same requirement.

Table 4. Sample SIT Numbers for Multiple Submissions to the Same Requirement

* NOTE: If the submitter does not require an internal tracking number, use the document type designation.

3.2. BIDS Security and Access Control.

All data uploaded to BIDS is secure from public view and download. All submissions will be considered proprietary/source selection sensitive and protected accordingly. The documents can only be reviewed by the registrant and authorized Government and contractor representatives with no conflict of interest.

3.3. Submission Changes.

Changes to uploaded submissions are permitted up to the closing date and time. If a modification is required, update the original file in the source application and save. Convert to an acceptable format if applicable. In BIDS, open the submission record, click Edit Proposal, and update the record information. Click on the trash can icon to delete the old file. Use Browse to select the revised document. Click Submit Proposal to save the changes. Documents cannot be edited online through the BIDS Web interface. File names must contain no spaces or special characters. Ensure the file size does not exceed the prescribed limits. To completely remove a submission from consideration, select Delete Proposal. Changes after the requirement due date and time are not permitted.

3.4. Special Handling Procedures for Classified Information.

If a submission contains classified information, the offeror must first create a placeholder record in BIDS with an unclassified cover page attachment. Identify in the comments section of the submission record that the submission cannot be uploaded due to classification. The BIDS Document Identifier must be clearly identified on the mailed document(s). Classified responses (up to SECRET) must be appropriately and clearly marked (including all paragraphs and pages containing the subject data), packaged, and shipped in accordance with classified material handling procedures and security regulations pertaining to the level of classification for that document.

To obtain mailing instructions for classified submissions, email: BAASecurity@cttso.gov.

Classified submissions must be received by the applicable due date and time. Classification in no way eliminates the offeror’s requirement to comply with all BAA instructions.

3.5. Phase 1 Quad Chart Submissions.

Offerors shall prepare and upload a one-page (8 ½ by 11 inches) Quad Chart in response to Phase 1 of this BAA. Use font sizes of 10 point or greater. If more than one page is submitted, only the first page will be evaluated. Quad Charts do not require a Cover Page.

3.5.1. Phase 1 Due Date and Time.

All unclassified Quad Charts must be received electronically through BIDS no later than 1500 (3:00 p.m.) Eastern Time (ET) on the date specified on the cover of this document. Likewise, classified submissions must be received by the same due date and time. Offerors must create a placeholder record in BIDS with an unclassified cover page attachment. Refer to the “Special Handling Procedures for Classified Information” in this document for instructions on classified submissions. BIDS does not allow proposals to be uploaded or classified placeholders to be created after the closing date and time. Any proposal, regardless of classification, submitted by any other means, or that is late, will not be considered by the Government. Avoid the last minute rush; submit early.

3.5.2. Electronic File Format.

The Quad Chart shall be submitted in Microsoft Office (Word or PowerPoint), or Adobe Acrobat (PDF – portable document format). ZIP files and other application formats are not acceptable. The document must be print-capable, without password, and no larger than 1024 KB. File names must contain the appropriate file name extension (.doc/.docx, .ppt/.pptx, or .pdf). File names cannot contain spaces or special characters. Apple/Macintosh users must ensure the entire file name and path are free of spaces and special characters. Submissions that cannot be opened, viewed, or printed will not be considered.

3.5.3. Quad Chart Content.

A Quad chart conveys the essence of the proposed solution for a single requirement. When preparing a submission, the offeror shall ensure that the specific criteria of the requirement are addressed, the solution is clear, and can be accomplished with the proposed technology, cost, and schedule. The Quad Chart includes a document header and four quadrants. The Quad Chart format and sample are provided at the BIDS website under Reference Materials.

3.5.3.1. Header Information.

Header information shall include the BAA Announcement number, the Document Identifier, and the Proposal Title. The date and company name should be included along with the appropriate document markings.

3.5.3.2. Top Left Quadrant, Graphical Depiction.

The top left quadrant is a graphical depiction, photograph, or artist’s concept of the proposed solution or prototype. Include labels or brief descriptive text as needed for clarification. Ideally, this will convey the prototype concept, use, capability, and any relevant size or weight relationships based on the published requirement.

3.5.3.3. Top Right Quadrant, Operational and Performance Capabilities.

The top right quadrant contains the operational and performance capabilities summary. Describe any basic, new, or enhanced capabilities the system will provide to meet the published requirement. In bullet form, list key aspects of performance, capability, operational use, relevant software or hardware specifications, and planned interface and/or compatibility. The offeror is only required to submit past performance information in response to a request for Full Proposal.

3.5.3.4. Bottom Left Quadrant, Technical Approach.

The bottom left quadrant contains the proposed technical approach. Specifically, describe the technology involved, how it will be used to solve the problem, actions done to date, and any related ongoing efforts. Briefly describe the tasks to be performed for each phase. A bullet list is acceptable.

3.5.3.5. Bottom Right Quadrant, Cost and Schedule.

The bottom right quadrant contains the Rough Order of Magnitude (ROM) and Schedule, Products and Deliverables, and Corporate Contact Information. ROM and Schedule shall be proposed by phase and include the cost, period of performance (POP), and exit criteria for each phase. A total cost and POP that combines all phases shall also be included. Products and Deliverables shall include, by phase, a list of all prototype hardware and software along with the required data as described in “Product and Deliverable Requirements” in section 2 of this document. Corporate Contact Information shall include the submitter’s company name, POC, phone number, and email address. Include any significant teaming partner (contact information) relevant to the evaluation. (Note that the contact information in the BIDS registration is used for all notices and contact purposes.)

3.5.4. Phase 1 Notification to Offeror.

The Government will notify the offeror when a submission has been accepted or rejected. Notification of acceptance with a request to submit the next phase document will be emailed to the offeror’s contracting authority as entered in the BIDS registration and will indicate the next submission type, clarification requests, and due date and time. Likewise, rejection notifications will be emailed to the address provided in the BIDS registration. Debriefings for Quad Charts will not be conducted due to the nature of BAAs. In general, submissions are not considered for further review when they do not meet the basic requirement, are too costly, or do not fit the mission. All Quad Charts are evaluated in accordance with Section 4, Proposal Evaluation, of this BAA.

3.5.5. Phase 1 Status and Inquiries.

Phase 1 is complete when all submissions have been accepted or rejected in accordance with this BAA. Inquiries by phone concerning the status of Quad Charts will not be accepted. After login to the BIDS website, submitters are able to check the status of their submission(s) under Check My Current Proposals.

3.6. Phase 2 White Paper Submissions.

Offerors shall prepare and upload a White Paper with no more than twelve (12) pages plus a cover page in response to Phase 2 of this BAA. All submission pages shall be 8 ½ by 11 inches, double-spaced with fonts no smaller than 10 point; all margins shall be one inch. Each page of the submission shall contain the document identifier in the document header. If the White Paper contains more than 12 pages including tables, charts, and figures, only the first 12 pages will be evaluated. All White Paper submissions must include a cover page. The cover page template is provided at the BIDS website under Reference Materials. Cover pages are excluded from the White Paper page count.

3.6.1. Phase 2 Due Date and Time.

All unclassified White Papers must be received electronically through BIDS no later than the due date and time specified in the Phase I Quad Chart acceptance email. Likewise, classified submissions must be received by the same due date and time. Offerors must create a placeholder record in BIDS with an unclassified cover page attachment. Refer to the “Special Handling Procedures for Classified Information” in this document for instructions on classified submissions. BIDS does not allow proposals to be uploaded or classified placeholders to be created after the due date and time. Any proposal, regardless of classification, submitted by any other means, or that is late, will not be considered by the Government.

3.6.2. Electronic File Format.

The White Paper shall be submitted in Microsoft Office (Word or PowerPoint), or Adobe Acrobat (PDF – portable document format) format. ZIP files and other application formats are not acceptable. The document must be print-capable, without password, and no larger than 2048 KB. File names must contain the appropriate file name extension (.doc/.docx, .ppt/.pptx, or .pdf). File names cannot contain spaces or special characters. Apple/Macintosh users must ensure the entire file name and path are free of spaces and special characters. Submissions that cannot be opened, viewed, or printed will not be considered.

3.6.3. Phase 2 Document Upload.

To upload a next phase document use the link back to BIDS provided in the acceptance email, or login to BIDS under Proposals Due to open the accepted record. Select Create Next Submission and follow the instructions.

3.6.4. White Paper Content.

White Papers shall provide a description of the technical approach, the specific tasks and deliverables by phase, schedule and cost estimate by phase, intellectual property and government rights, transition planning for production, and a capability statement. The offeror shall incorporate all clarification data requests from the acceptance email into the submission. Indicate clarification entries by footnote and reference the requested item(s) in the footer area. The following White Paper sections and details are required.

3.6.4.1. Cover Page.

A cover page template is provided at the BIDS website under Reference Materials. The cover page includes necessary contractual information including the offeror’s contracting POC (name, telephone number, email address, facsimile number, mailing address) and business information (Data Universal Numbering System (DUNS) number, CAGE code, business type). Include the proposed contract type, total cost, and the duration of all phases/tasks. Cover pages are excluded from the page count.

3.6.4.2. Technical Approach.

Describe the proposed solution relative to the requirement. Focus content on operational capabilities required to address the problem, the underlying theory that supports the operational capability, and suggested concept of operations. Identify end users that could be interested in the proposed solution and describe how the solution will be a benefit. Include drawings, diagrams, charts, and tables needed to explain the effort. Describe if, and where, the proposed technology/solution has been, or is being used. Identify sponsoring agency and funding resources; or if none, so state.

3.6.4.3. Tasks and Deliverables.

Identify the proposed tasks by phase in the order of occurrence. A phase must have clear exit criteria to serve as a “go” or “no-go” decision point to proceed to the next phase. Identify work that will be performed by other organizations or agencies. Identify anticipated technical risks along with planned mitigation efforts. Indicate any Government furnished material (GFM), equipment (GFE), or information (GFI) that will be required with the task and need date; or if none, so state. For each phase include the exit criteria and all products and deliverables as defined in “Product and Deliverable Requirements” in section 2 of this document. If a phase is proposed as an option, so state.

3.6.4.4. Schedule.

Develop a master project schedule preferably in Gantt chart format. The schedule shall indicate the planned start and stop point for each phase with top level subordinate tasks, estimated delivery dates, and completion dates. Indicate the total project POP in months using January 2nd as a notional start date through the completion date.

3.6.4.5. Cost.

Provide the proposed, task-phased budgetary estimate inclusive of any proposed options. At a minimum, this estimate shall detail estimated labor hours and costs, anticipated material costs, product and deliverable costs (see section 2 General Information, “Product and Deliverable Requirements” in this document) and other costs (e.g., subcontracts, indirect rates, fee rate) for each phase/task. Costs allocated to other organizations (e.g., Government testing) shall be clearly shown; or if none, so state. Changes in cost greater than 10 percent from those proposed in the prior submission shall be explained.

3.6.4.6. Intellectual Property, Technical Data, and Software.

Disclose/discuss all intellectual property, technical data, and/or software rights that are intended to be used in connection with this submission. See section 2 General Information, “Submission Handling/Rights in Technical Data and Computer Software/Patent Rights” in this document. For additional information on this topic, see the DOD Intellectual Property Guide, available for download on the Technology Transition Web page at www.cttso.gov and DFARS 252.227-7013 and DFARS 252.227-7014.

3.6.4.6.1. Patents and Patent Applications.

Identify any existing, applied for, or pending patents that will be used in the conduct of this effort. Provide patent number with date of issue and title or patent application number with filing date and title. Any patent or patent application that resulted from prior government funding should be identified. If no patents or patent applications are relevant, so state. See section 2 General Information, “Submission Handling/Rights in Technical Data and Computer Software/Patent Rights” in this document.

3.6.4.6.2. Rights in Technical Data and Software.

Identify any technical data and/or computer software that will be delivered with less than unlimited rights as prescribed in DFARS 252.227-7013 and DFARS 252.227-7014. If unlimited rights in technical data are proposed, so state. See section 2 General Information, “Submission Handling/Rights in Technical Data and Computer Software/Patent Rights” in this document.

3.6.4.7. Transition from Prototype to Production.

Describe the overall strategy to transition the results of this development effort to production once the funded effort is concluded. Briefly describe the overall strategy for transition, potential partners, transition issues to include any obvious regulatory, liability, interoperability, or financing issues. Discuss the interaction with representative users and the concept for test and evaluation by those users and follow on support of a product resulting from this effort.

3.6.4.8. Organizational Capability Statement.

Describe the offeror’s capability and/or experience in doing this type of work. Identify technical team members or principal investigators and associated expertise. If applicable, include a description of co-participants’ capabilities and/or experience. State whether an agreement has been reached (or not) with the co-participants. The offeror is only required to submit past performance information in response to a request for Full Proposal.

3.6.5. Phase 2 Notifications to Offeror.

The Government will notify the offeror when a submission has been accepted or rejected. Notification of acceptance with a request to submit the next phase document will be emailed to the offeror’s contracting authority as entered in the BIDS registration and will indicate the next submission type, clarification requests, and due date and time. Likewise, rejection notifications will be emailed to the address provided in the BIDS registration. Debriefings for White Papers will not be conducted due to the nature of BAAs. In general, submissions are not considered for further review when they do not meet the basic requirement, are too costly, do not fit the mission, or funding is not expected. All White Papers are evaluated in accordance with Section 4, Proposal Evaluation, of this BAA.

3.6.6. Phase 2 Status and Inquiries.

Phase 2 is complete when all submissions have been accepted or rejected in accordance with this BAA. Inquiries by phone concerning the status of White Papers will not be accepted. After login to the BIDS website, submitters are able to check the status of their submission(s) under Check My Current Proposals.

3.7. Phase 3 Full Proposal Submissions.

Offerors shall prepare and upload a Full Proposal, consisting of a Technical Proposal and a Cost Proposal, plus a cover page, in response to Phase 3 of this BAA. All pages shall be 8 ½ by 11 inches, double-spaced with fonts no smaller than 10 point; all margins shall be one inch. Each page of the submission shall contain the document identifier in the document header. The Technical Proposal must be no more than 50 pages including tables, charts, and figures. If the document contains more than 50 pages, only the first 50 pages will be evaluated. All paragraphs containing proprietary information must be clearly marked. The Cost Proposal has no page limit; however, unnecessarily elaborate or information beyond those sufficient to present a complete and effective response is not desired.

Disclaimer - To minimize the cost and effort for submitters, Phase 3, Full Proposals, will only be requested for qualifying solutions that have a high probability of award; however, the Government reserves the right to cancel requirements, or any request for proposals for this solicitation, at any time prior to award and shall not be liable for any cost of proposal preparation or submission.

3.7.1. Phase 3 Due Date and Time.

All unclassified Full Proposals must be received electronically through BIDS no later than the due date and time specified in the acceptance email. Likewise, classified submissions must be received by the due date and time. Offerors must create a placeholder record in BIDS with an unclassified cover page attachment. Refer to the “Special Handling Procedures for Classified Information” in this document for instructions on classified submissions. BIDS does not allow proposals to be uploaded or classified placeholders to be created after the due date and time. Any proposal, regardless of classification, submitted by any other means, or that is late, will not be considered by the Government.

3.7.2. Electronic File Format.

The Full Proposal shall be submitted in Microsoft Office (Word or PowerPoint), or Adobe Acrobat (PDF – portable document format). The cost proposal may be submitted in Microsoft Office (Excel) format. ZIP files and other application formats are not acceptable. The document must be print-capable, without password, and no larger than 2048 KB. File names must contain the appropriate file name extension (.doc/.docx, .ppt/.pptx, .xls/.xlsx, or .pdf). File names cannot contain spaces or special characters. Apple/Macintosh users must ensure the entire file name and path are free of spaces and special characters. Submissions that cannot be opened, viewed, or printed will not be considered.

3.7.3. Phase 3 Document Upload.

To upload a next phase document, locate and open the accepted record in BIDS and select Create Next Submission.

3.7.4. Full Proposal Components.

Full Proposals shall consist of two major sections described in this document, and can be uploaded to BIDS in two separate files each limited to 2048 KB each. The first section is the Technical Proposal and shall include all information related to the proposal as specified in this BAA including figures, charts, and tables plus the cover page. The second section is the Cost Proposal to include all cost data as well as an explanation of changes in cost greater than 10 percent from those proposed in the prior submission. Additionally, the offeror will include a cover page as follows:

A cover page template is provided at the BIDS website under Reference Materials. The cover page includes necessary contractual information including the offeror’s contracting POC (name, telephone number, email address, facsimile number, mailing address) and business information (DUNS number, CAGE code, business type). Include the proposed contract type, total cost, and the duration of all phases/tasks.

3.7.5. Technical Proposal Content.

The Technical Proposal shall provide a technically detailed solution of the problem addressed in the requirement and fully expand the technology proposed in the prior submissions. The following sections and associated data are required. The offeror shall incorporate all clarification data requests in the Phase 2 acceptance email. Indicate clarification entries by footnote and reference the requested item(s) in the footer area.

3.7.5.1. Reserved.

3.7.5.2. Abstract.

The abstract is a one page (or less) synopsis of the proposal that includes the title and the basic approach to satisfy the requirement. Describe the overall scope of work to be performed for the entire POP inclusive of options. The abstract shall stand alone and be suitable for release under the Freedom of Information Act, 5 U.S.C. 552, as amended.

3.7.5.3. Executive Summary.

An executive summary is a concise description of the technology and solution being proposed. Include key information that demonstrates how the proposed solution meets the published requirement. The executive summary should not introduce any new information not covered in the subsequent content.

3.7.5.4. Technical Approach.

Describe the technical approach for the proposed solution to meet the requirement. Include technical details of the solution and fully expand the technology proposed in the prior phase submission. Include the methodology, underlying theory, system components, and operational scenario for the intended users. Include drawings, diagrams, charts, and tables needed to explain the effort. Describe relevant prior application of the proposed technology and/or solution, how it is being used, and by whom. Identify sponsoring agency and funding resources; or if none, so state. If subcontractors are proposed, include a detailed description of the effort that they will be performing in support of or in addition to the prime.

3.7.5.5. Project Plan.

The project plan shall be organized by phase and describe the work to be performed along with all associated requirements to successfully complete the proposed effort. Include a summary of the individual phases to follow.

3.7.5.5.1. Phases.

Phases shall be defined by the subset of tasks to be performed, phase objectives to be accomplished, and the required POP to completion. Phases shall be listed in order of occurrence. Identify phases that are optional. Each phase must contain clear exit criteria that is measurable evidence of completion and serves as a “go” or “no-go” decision point. Each phase shall include a total cost.

3.7.5.5.2. Tasks within a Phase.

For each task, provide a detailed description of the work to be performed. Identify any work that will be performed by other organizations or agencies; or if none, so state.