Combating terrorism technical support office/ Technical Support Working Group
Product and Deliverable Requirements
Download 341.58 Kb.
|
- Navigate this page:
- 2.7. Distribution/Release Limitations.
- 2.9. Animal or Human Testing Compliance.
- 2.9.2. Human Subjects Testing.
- 3. PROPOSAL PREPARATION.
- 3.1. BAA Information Delivery System (BIDS).
- 3.1.1. Submitter Registration.
- 3.1.2. User Accounts and Password Resets.
- 3.1.3. Registration and Account Help.
- 1.3.1.4.1. Constructing Document Identifiers.
- 2.3.1.4.2. Creating Submitter Internal Tracking (SIT) Numbers.
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. 1.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.
2.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.
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.
Download 341.58 Kb. Share with your friends:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||