15-Q-3359_BAA.docx

COMBATING TERRORISM TECHNICAL SUPPORT OFFICE/

Technical Support Working Group

(CTTSO/TSWG)

BROAD AGENCY ANNOUNCEMENT (BAA)

15-Q-3359

Due Date for Receipt of Phase 1 White Papers:

No Later Than 2 April 2015 All submissions are due by 3:00 p.m.

Eastern Time (ET) on the above date

Bidders Conference: Attendance is Required

PP – Personnel Protection SCOS – Surveillance, Collection, and Operation 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

15-Q-3359 BAA Package January 9, 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) 2016. 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.Objective.

The CTTSO Personnel Protection Subgroup has interest in technical development efforts. The efforts include: detection and identification of both fixed wing and vertical take-off and landing small unmanned aerial vehicles in dense urban environments; countermeasures for both fixed wing and vertical take-off and landing small unmanned aerial vehicles that can be safely deployed in dense urban environments without risk of collateral damage or injury upon engagement; a means to detect and locate explosive devices planted on motor vehicles while driving through areas heavily congested with pedestrians and cyclists; and the development of a personnel signature management system that eliminates or reduces any or all of the following: radar, electronic, thermal infrared, visual, and acoustic signatures of a dismounted soldier.

The Surveillance Collections and Operations Subgroup is interested in development efforts. The efforts include: biometrics and the development of new or improved technologies or emerging technological capabilities that biometrically enroll and/or verify the identity of individuals, at high-speed and with high-confidence in operational conditions; secure or special communications pertaining to secure and mobile communications that are not commercially available; emerging technological capabilities, or methods pertaining to accessing Telematics/Infotainment information.

The Tactical Ops Subgroup (TOS) is interested in development effort in the communications field, specifically looking for new technologies that are tailored for tactical operations, exploit underutilized parts of Electro Magnetic Spectrum in innovative ways, have a low/zero Radio Frequency (RF) signature, while still providing effective bandwidth for C2 and ISR.

The Training Technology Development Subgroup is interested in Unconventional Warfare Interpersonal Communications, Negotiations, and Psychology Course. The course will enhance Unites States military personnel interpersonal communications and negotiations skill sets when interacting with tactical leaders of resistance movements.

Specific details on required performance characteristics and potential mission application for each effort is classified and will be provided at a classified Bidder’s Conference hosted by CTTSO on February 19, 2015. See section 3.1. “Bidders Conference” for details.

1.2. Approach.

A two 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 White Paper in response to the specific requirement(s).

• Phase 2 will consist of the solicitation, receipt, and evaluation of a Full Proposal and applies to only those submissions that have been accepted in Phase 1. Clarifications to White Papers and Full Proposals may be requested.

The Government is soliciting a two-phased proposal selection process to minimize cost and effort for prospective offerors in full compliance with requirements described in this document. Phase 1 will consist of the solicitation, receipt and evaluation of a 12 (twelve) page White Paper. All White Paper submittals are due no later than 3:00 pm Eastern time on 2 April 2015. The Government will review each White Paper’s merit to proceed to Phase 2. Phase 2 will consist of the solicitation, receipt and evaluation of a Full Proposal. The due date for Full Proposals will be given to submitters whose White Paper is accepted in Phase 1. The Government will review each proposal’s merit for contract award based on criteria described in this document. The Government expects to award one contract for each technology development in support of these efforts. However, the Government reserves the right to select for award all, some, or none of the proposals received.

1.3. 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.4. 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 the Limitation of Government’s Obligation clause (Department of Defense Federal Acquisition Regulation Supplement (DFARS 252.232-7007)). In such cases, milestone payments will need to be a part of the full proposal. Applicability of this issue will be stated in the e-mail asking for a Phase III proposal]

1.5. 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.6. BAA Package Download.

This BAA Package can be downloaded electronically in its entirety from https://www.bids.tswg.gov/ under its’ News entry. Registration is not required to download the BAA package. However, registration is required to create a BIDS placeholder record for each submission. It is anticipated that white papers and proposals will be classified. For classified submissions, a BIDS submittal number is required for tracking purposes as described in Section 3 of this document.

1.7. BAA Contractual and Technical Questions.

All contractual and technical questions regarding this BAA, including the published requirements and instructions, shall be directed to the BIDS Help Desk at BIDSHelp@cttso.gov. Do not contact any other CTTSO personnel concerning this BAA! Contractual questions and answers will be posted periodically under BAA Questions on the BIDS Web site. All questions must be received at least 72 hours prior to close of the submission period. For technical help using the BIDS website, submit questions to the BIDS administrators at bidshelp@cttso.gov or by using the Help Request link located on the BIDS Homepage. Include a valid e-mail address, your BIDS User Name, and a detailed description of the question or concern in the comments block. The BIDS Web site provides other valuable resources under Online Help, and Doing Business with the Government. Reference documents including the BIDS Submitter Quickcard are available for download. 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://www.bids.tswg.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/

· In addition, the efforts will involve the use of and access to classified data and results, and shall require classified facilities. Offeror’s must have a SECRET facility clearance and processing and storage capability. All work relating to these efforts will be performed in a secure facility. Individuals working on these efforts must hold a final SECRET clearance. 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. 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.4. Submission Handling/Rights in Technical Data and Computer Software/Patent Rights.

2.4.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.4.2. Submission Information and FOIA.

Records or data bearing a restrictive legend may 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.4.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 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 DFARS sections 252.227-7013 and 252.227–7014 will be included in any noncommercial contract exceeding the simplified acquisition threshold awarded under this BAA. Table 1 contains these and related clauses that may be included in the contract.

Table 1. Contract Clauses

2.4.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.5. 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 2 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.6. 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.7. 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.8. 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.8.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.8.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 and DFARS 252.235-7004. 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.

CTTSO will hold a one-day Bidders Conference on February 19, 2015 from 8:00 AM until 12:00 PM Eastern Time, at the Booz Allen Hamilton conference facility in McLean, Virginia. ONLY THOSE COMPANIES THAT ATTEND THE BIDDERS CONFERENCE WILL BE ELIGIBLE TO SUBMIT A WHITE PAPER IN RESPONSE TO THIS BAA. All interested attendees must register on line at http://events.SignUp4.net/CTTSOABPI2015 . Please limit attendance to no more than two (2) people per organization. The registration web site includes the address and directions to the conference from local airports as well as names and contact information for area hotels. Registration must be completed no later than 5:00 PM, February 10, 2015. Information conveyed at this meeting will include classified data at the SECRET level. Therefore, all attendees are required to submit a visit authorization request no later than 1:00 PM Eastern Time on February 10, 2015. Only US citizens with a SECRET clearance will be permitted to attend. Attendees will only be admitted into the meeting if their VAR's have been received. Please submit clearance information on-line at http://events.SignUp4.net/CTTSOABPI2015 .

Facility information and directions, local hotel information and instructions on passing clearance information can be found on the conference registration page. http://events.SignUp4.net/CTTSOABPI2015 .

No one will be admitted into the meeting before confirmation of their clearance on file.

Questions regarding security requirements may be sent to BAASecurity@cttso.gov.

General questions regarding the Bidders Conference may be sent to BIDSHelp@cttso.gov.

3.1. BAA Information Delivery System (BIDS).

BIDS at https://www.bids.tswg.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 e-mail will be sent to indicate that the User Name and account are accepted. BIDS is e-mail dependent and uses the Registration e-mail as the single point of contact (POC) for all notifications associated with the BAA. This e-mail address should be monitored frequently during the BAA process for the notices. Submitters should periodically check status in their account, not receiving a notification e-mail does not constitute grounds to appeal an evaluation decision. Spam blockers and other e-mail security software may cause a notification e-mail to be rejected, check your account. E-mail 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, e-mail, and password can be updated after login. The Forgot Password? link on the BIDS Homepage allows registered users with a valid e-mail address to automatically reset a password. The system will verify the account User Name and e-mail to send a new password to that e-mail.

3.1.3. Registration and Account Help.

BIDS Help requests can be e-mailed to BIDS administrators at bidshelp@cttso.gov or submitted via the Help Request link located on the BIDS Homepage.

3.1.4. Format and Submittal.

All responses must be submitted according to proper classified mailing procedures for Secret material as described in the National Industrial Security Program Operating Manual (NISPOM), DoD 5200-1R and DoD M5205.7 to the following address (if required):

Outer Envelope:

CTTSO

Attn: Document Control 4800 Mark Center Drive, Suite 13E13 Alexandria, VA 22350-2600

Inner Envelope:

CTTSO

Attn: Contracting Officer 4800 Mark Center Drive, Suite 13E13 Alexandria, VA 22350-2600 To deliver by cleared company courier, contact BAASecurity@cttso.gov.

All submittals must consist of five hardcopies in ringed binders and accompanied by one copy of the entire document on a single CD in accordance with file formats described in section 3.3.1 and 3.4.1 of this document. White papers or proposals submitted in sections under separate covers based on classification will not be accepted. The entire white paper or proposal shall be submitted as a classified document to the above address

3.1.4.1. BIDS Placeholder Record.

The submitter shall create a BIDS record for each submission mailed in accordance with the paragraph above. The record is created by logging into BIDS, selecting this BAA number, clicking on Respond to BAA, and creating a submission record for the appropriate requirement by following the screen prompts. The submission record must include an unclassified attachment letter or cover page. Classified data shall not be entered in BIDS.

3.1.4.2. Document Identifier.

The submitter shall insert a “Document Identifier” into the header (top margin area) of each submittal. The identifier shall be unique to any other submittal from the offeror in BIDS and MUST be formatted with the prefix, the User Name (entered when you register in BIDS) and the submitter internal tracking number entered at the time the BIDS placeholder record is created. The constructed document identifier is frequently used by the evaluation team to identify each submittal and to connect printed documents with evaluation records.

Example Document Identifier = PP-XX-USERID-Submitter Internal Tracking Number

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 will be 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 Submission, and update the record information. Use Browse to select the revised document. Select the checkbox to remove the old attachment. Click Submit for Processing 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 Submission. Changes after the requirement due date and time are not permitted.

3.4. Special Handling Procedures for Classified Information.

Since all submittals shall be classified, the offeror must first create a BIDS submission record and obtain a Document Identifier through BIDS for tracking purposes. The BIDS tracking number must be clearly identified on the mailed submittal. Classified responses must be appropriately marked, sealed and delivered to CTTSO in accordance with regulations and instructions pertaining to the level of classification and means of delivery per the NISPOM.

3.5. Phase 1 White Paper Submissions.

White Paper submissions must include five (5) hardcopies in ringed binders and accompanied by one copy of the white paper on a single CD in accordance with file formats described in Section 3 of this document. White papers submitted in sections under separate covers based on classification will not be accepted. The entire white paper shall be submitted as a classified document.

Offerors shall prepare a white paper with no more than twelve (12) pages plus a cover page in response to the first phase of this BAA. All submission pages shall be single sided, 81/2 by 11 inches, double spaced with fonts no smaller than 10 point: all margins shall be one inch left/right/top/bottom. Each page of the submission shall contain the document identifier in the document header. If the white paper contains more than twelve (12) pages including tables, charts, and figures only the first twelve (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 Downloads, Reference Documents, and Document Format. Cover pages are excluded from the white paper count. Submissions must be appropriately marked for classification, sealed, and mailed in accordance with classified material handling procedures in the NISPOM. White Papers received after the closing date and time will not be considered by the Government.

3.5.1. Phase 1 Due Date and Time.

All white papers must be received no later than 3:00PM Eastern time on 2 April 2015. Refer to section 3.4. “Special Handling Procedures for Classified Information” and 3.1.4 “Format and Submittal“ of this document for instructions on classified submissions. BIDS does not allow white paper cover letter notifications to be uploaded or classified placeholders to be created after the due date and time. Any white paper, regardless of classification, submitted by any means other than specified in this BAA, or that is late will not be considered by the Government.

3.5.2. Electronic File Format.

The white paper shall be prepared in color or black and white in Microsoft Word, Microsoft Excel or Adobe Acrobat PDF electronic file format. ZIP format or other application formats are not acceptable. The document must open without password and be print capable. Filenames cannot contain spaces or special characters. Submissions that cannot be opened, viewed or printed from the CD copy, will not be considered.

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 to the intellectual property, transition planning for production, and a capability statement. The offeror shall incorporate all clarification data requests from the acceptance e-mail 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 Web site. The cover page includes necessary contractual information including the offeror’s contracting POC (name, telephone number, e-mail 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 period of performance (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, including patents, copyrighted material, 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 1 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 e-mailed 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 e-mailed 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 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 White Papers will not be accepted. After login to the BIDS Web site, submitters are able to check the status of their submission(s) under Past Proposals.

3.7. Phase 2 Full Proposal Submissions.

Proposal submissions must include five (5) hardcopies in ringed binders and accompanied by one (1) copy of the entire proposal on a single CD in accordance with file formats described in section 3. Proposals submitted in sections under separate covers based on classification will not be accepted. The entire proposal shall be submitted as a classified document to the address in section 3.1.4.

Offeror’s shall prepare and submit a full proposal with a separate detailed cost proposal in response to Phase 2 of this BAA. All pages shall be single sided, 8½ by 11 inches, double-spaced with fonts no smaller than 10 point; all margins shall be one inch left/right/top/bottom. Each page of the submission shall contain the document identifier in the document header. The technical portion shall be no more than fifty (50) pages including tables, charts, and figures. If the document contains more than fifty (50) pages, only the first fifty (50) pages will be evaluated. All paragraphs containing proprietary information must be clearly marked. The cover page and the detailed cost proposal are excluded from the full proposal page count.

Disclaimer - To minimize the cost and effort for submitters, Phase 2 full proposals, will only be requested for qualifying solutions that have a high probability of award; however, the Government reserves the right to cancel any request for proposal for this solicitation prior to award.

3.7.1. Phase 2 Due Date and Time.

All full proposals must be received no later than the due date and time specified in the White Paper acceptance e-mail. Refer to section 3.4. “Special Handling Procedures for Classified Information” and 3.1.4 “Format and Submittal“of this document for instructions on classified submissions. BIDS does not allow proposal cover letter notifications to be uploaded or classified placeholders to be created after the due date and time. Any proposal, regardless of classification, submitted by any means other than specified in this BAA, 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 open without password and print-capable. Filenames must contain the appropriate filename extension (.doc, .ppt, .xls, or .pdf). Filenames cannot contain spaces or special characters. Apple/Macintosh users must ensure the entire filename 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 2 Document Upload.

To upload a next phase cover letter proposal submission notification, locate and open the accepted record in BIDS and select Create Next Submission. DO NOT UPLOAD THE CLASSIFIED PROPOSAL. Upload only the cover letter to indicate the classified document is being mailed in accordance to the NISPOM. This is the same process used for Phase 1 submissions

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 2 MB 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 White Paper. Additionally, the offeror will include a cover page as follows:

A cover page template is provided at the BIDS Web site. The cover page includes necessary contractual information including the offeror’s contracting POC (name, telephone number, e-mail 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 e-mail. Indicate clarification entries by footnote and reference the requested item(s) in the footer area.

3.7.5.1. 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.2. 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.3. 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 and identify any government contracts or related subcontracts for such technology, prior applications and/or solutions (include contracting agency(ies), contract number(s) and dates of contract performance). 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.4. 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.4.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.4.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. Indicate if an agreement is in place for the resources.

3.7.5.4.3. Products and Deliverables.

Identify all deliverables - products as well as documentation and reports - for each Task/Phase. Refer to section 2.6 of this document “Product and Deliverable Requirements” for the minimum report requirements, and additional products and deliverables in performance of the effort proposed.

3.7.5.5. Master Schedule.

Develop a master project schedule that includes phase start and stop dates as well as major milestones, critical tasks, and report and product delivery dates. Assume a start date of 02 January. Indicate any optional phases.

3.7.5.6. Government Furnished Equipment.

Reasonably identify all Government furnished equipment (GFE), materials, facilities, or information with the need date and suggested source at the time of proposal submission. GFE includes, but is not limited to: Government e-mail accounts, SIPRNET access, Common Access Cards (CACs), and/or space at a CTTSO facility (either permanent residence, temporary residence, or testing). Upon identifying GFE, if an offeror’s proposal is selected for contract award, the proposed GFE will be identified in the resulting contract. Failure to adequately identify necessary GFE may result in contract termination due to the offeror’s inability to perform under this competitive source selection. If Government equipment, materials, facilities, or information are not required, so state.

3.7.5.7. Project Risks and Mitigation.

Identify anticipated technical and management risks along with planned mitigation efforts. Indicate the risk assessment as high, medium, or low.

3.7.5.8. Organizational Capability Statement.

Include a brief description of the offeror’s organization. Describe the offeror’s capability and/or experience in doing the type of work being proposed. If applicable, include a description of co-participants’ capabilities and/or experience. State whether an agreement has been reached with the co-participants. Provide at least three references, to include points of contact, for like or similar work.

3.7.5.9. Organizational Resources.

Identify key technical personnel and principal investigator(s) including alternates and co-participants, if applicable.