Documents / Official release
This is Standard Form 1449, the solicitation and award for contract HHM402-08-C-0072, issued September 1, 2008 and awarded September 22, 2008, administered by the Virginia Contracting Activity in Washington, D.C. The contractor is Bigelow Aerospace Advanced Space Studies, LLC of Las Vegas, and the total award is $21,948,810. The firm fixed price contract covers a base year and an option year. Deliverables include monthly status reports, project management plans, research reports for Tasks 3.a.1 to 3.a.12, and a Comprehensive Integrated Threat Assessment.
From the source:Release of 2026-09-18 Incident: 9/22/08, Washington, D.C.. Released with redactions. This document is an administrative or programmatic record related to the Advanced Aerospace Weapon System Applications Program (AAWSAP), a Defense Intelligence Agency (DIA)-administered program active from 2008 to 2012. AAWSAP’s official scope of work identified 12 technical research areas relating to potential aerospace threats over a time horizon of more than 40 years. As an administrative record, the file documents how AAWSAP was scoped, organized, tasked, funded, or described at a particular point in time. This September 2008 solicitation/contract/order document serves as the original contract award instrument for AAWSAP work performed by Bigelow Aerospace Advanced Space Studies, Inc. (BAASS), incorporating the contractor’s proposal by reference and translating the earlier Statement of Objectives (DOW-UAP-D110) into priced contract line items. The file breaks the base year into specific deliverable categories, including monthly status reports, program management plans for the 12 technical areas, research reports, a comprehensive integrated threat assessment, travel, and other direct costs, and corresponding option-year line items for follow-on performance.
Read from the scan by GLM-OCR; expect the odd misread word.
Exhibit Line Item Number (iii) Subassemblies, components, and parts embedded within delivered items as specified in Attachment Number (2) The unique item identifier and the component data elements of the DoD unique item identification shall not change over the life of the item. (3) Data syntax and semantics of unique identifiers. The Contractor shall ensure that-- (i) The encoded data elements (except issuing agency code) of the unique item identifier are marked on the item using one of the following three types of data qualifiers, as determined by the Contractor: (A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology # EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard. (B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology # EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard. (C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and (ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology # Transfer Syntax for High Capacity Automatic Data Capture Media. (4) Unique item identifier. (i) The Contractor shall-- (1) Serialize within the enterprise identifier; (A) Determine whether to-- (2) Serialize within the part, lot, or batch number; or (3) Use a DoD recognized unique identification equivalent; and (B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in the version of MIL-STD-130, Identification Marking of U.S. Military Property, cited in the contract Schedule. (d) For each item that requires unique item identification under paragraph (c) of this clause, in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, either as part of, or associated with, the Material Inspection and Receiving Report, the following information: (1) Unique item identifier. (2) Unique item identifier type. (3) Issuing agency code (if concatenated unique item identifier is used). (4) Enterprise identifier (if concatenated unique item identifier is used). (5) Original part number (if there is serialization within the original part number). (6) Lot or batch number (if there is serialization within the lot or batch number). (7) Current part number (optional and only if not the same as the original part number). (8) Current part number effective date (optional and only if current part number is used). (9) Serial number (if concatenated unique item identifier is used). (10) Government's unit acquisition cost. (11) Unit of measure. (e) For embedded subassemblies, components, and parts that require DoD unique item identification under paragraph (c)(1)(iii) of this clause, the Contractor shall report as part of, or associated with, the Material Inspection and Receiving Report specified elsewhere in this contract, the following information: (1) Unique item identifier of the parent item under paragraph (c)(1) of this clause that contains the embedded subassembly, component, or part. (2) Unique item identifier of the embedded subassembly, component, or part. (3) Unique item identifier type.++ (ii) The issuing agency code-- (A) Shall not be placed on the item; and (B) Shall be derived from the data qualifier for the enterprise identifier. (4) Issuing agency code (if concatenated unique item identifier is used).++ (5) Enterprise identifier (if concatenated unique item identifier is used).++
Not linked to a story yet.
Official release, from the pursue collection. The PDF is mirrored here; the original link is above. The text was read from the page images by GLM-OCR; expect the odd misread word. 59 pages are in the text index: search them above, or from the library's search.