Attachment_2_-_RFP_Offerors'_Library_Access_Form.xlsx
XLSX spreadsheet 14 KB Posted
- Solicitation number
- HQ0147-14-R-0002
- Issued by
-
DOD Missile Defense Agency
About this file
Attachment_2_-_RFP_Offerors'_Library_Access_Form
View the file
Other files
Show 40 more
Latest 50 of 54 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Form
LRDR RFP Offerors' Library Access Agreement/Request Form
Request access to the LRDR RFP Offerors' Library. Fill out Section 1 and email to LRDR_effort@MDA.mil
| SECTION 1 -- FOR INDUSTRY COMPLETION | ||
| Date: | ||
| Company Name | ||
| Subject | Request for Access to the LRDR RFP Offerors' Library | |
| Unclassified Access | ||
| Classified Access | ||
| Security Officer Name | Phone Number: | |
| Corporate Point of Contact | Phone Number: | |
| Physical Mailing Address |
| Facility Clearance |
| Requestor Personnel Clearance |
| POC to Receive Classified |
| Corporate CAGE Code |
| Signature/Date |
| In submitting this request, we agree to the following document handling procedures: |
Only US persons with need to know (your team) can handle the MDA BMDS CLASSIFED and CUI documents contained in the LRDR RFP Offerors' Library, per the DD 254 definitions below.
Offerors shall comply with BMDS FOUO documentation on Offerors Unclassified LAN, see DD 254 Reference Item 11.l.
No later than 5 days after contract award, all LRDR Requestor's Library documentation, no matter what the form (hardcopy, electronic, DVD, etc.), shall be destroyed. I further agree on behalf of my company to hold the Missile Defense Agency harmless from any liability or damage which my result from the failure of my company or its employees to abide by the terms and conditions of this LRDR Offerors' Library Access Agreement. THIS AGREEMENT CONCERNS A MATTER WITHIN THE JURISDICTION OF AN AGENCY OF THE UNITED STATES AND THE MAKING OF A FALSE, FICTITIOUS, OR FRAUDULENT CERTIFICATION MAY RENDER THE MAKER SUBJECT TO PROSECUTION UNDER TITLE 18, UNITED STATED CODE, SECTION 1001. OTHER SANCTIONS RELATED TO CONDUCT MAY ALSO APPLY.
DD254 BMDS Controlled Unclassified Information Supplement
1. Definitions
a. Ballistic Missile Defense System Controlled Unclassified Information (BMDS CUI). MDA/BMDS Unclassified information associating specific technologies to components, sub-systems or systems revealing sensitive configurations of a sub-system or system; identification of out-year funding or redirection of funds to specific components or projects revealing a re-prioritization of program direction; or information revealing sensitive BMDS plans, intentions, or activities relating to BMDS operations or contingencies. Examples: 1) Unclassified information that, if not protected, could lead to revealing classified Critical Program Information. 2) Information that identifies the number of components intended to be configured that would make up the operational Field of View of an interceptor thus potentially leading to concluding the Instantaneous Field of View. 3) MDA/BMDS infrastructure information revealing the location of sensitive areas, the facility protective measures, information disclosing infrastructure or security operations, harm or damage to persons, systems, utilities, or facilities, that are not otherwise eligible for classification under Executive Order 12958, as amended. BMDS CUI meets the requirement of Controlled Unclassified Information, as defined below, requiring protection during dissemination.
| b. Controlled Unclassified Information (CUI). Unclassified information which requires access and distribution limitations prior to appropriate coordination and an official determination by cognizant authority approving clearance of the information for release to one or more foreign governments or international organizations, or for official public release. It includes BMDS CUI or other information marked, or that is eligible for marking, as "For Official Use Only" (FOUO) in accordance with DoD 5400.7-R; technical information as discussed in DoD 5230.24 and 5230.25; information that is subject to export controls in accordance with the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR); sensitive information as defined in the Computer Security Act of 1987, or other qualifying information as identified in DoD 5200.1-R. | |
| h. U.S. Person. Any form of business enterprise or entity organized, chartered, or incorporated under the laws of the United States or its possessions and trust territories and any person who is a citizen or national (see National of the United States) of the United States, or permanent resident of the United States under the Immigration and Nationality Act. | |
| SECTION 2 -- FOR GOVERNMENT COMPLETION | |
| Section 2a. Contracts | Verification of Corporation CAGE Code |
| Initials (PCO or Contract Specialist) | |
| Date | |
| Section 2a. SECURITY | Verification of Corporation DD254 compliance for classified material and/or Personnel Clearance for Library Access |
| Initials (SN Security Lead/Specialist) | |
| Date Sent to Requesting Corporation |
Sheet1
| Yes |
| No |
File details come from the government source that posted it. Updated .