DOW-UAP-D114, AAWSAP Contract Modification P00003, May 2010

53
⬇ Download HD (2.5 MB)
SHARE Reddit X Facebook HN Email
Agency
DoD
Category
military
Type
PDF
Event Date
5/18/2010
Size
2.5 MB
Original Filename
DOW-UAP-D114_AAWSAP-Contract-Modification-P00003-May-18- 2010.pdf
Location
Washington, D.C.
Status
REDACTED

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 May 2010 contract modification is an administrative change to contract HHM402-08-C-0072. The modification states that its purpose is to change the Contracting Officer’s Representative (COR) designation for the AAWSAP contract and identifies the newly designated COR while specifying that guidance from the COR must comply with the contract’s governing terms. In effect, the file is best understood as an internal contract-administration update reflecting oversight realignment rather than a substantive change to AAWSAP’s research deliverables or program direction.

The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.

Text of the document

Machine-extracted from the PDF war.gov published (its text layer or OCR), so expect errors, especially in names, numbers and handwriting; the PDF is the authoritative copy. Lines that did not extract as readable text are left out. Showing about 607 words from pages 1, 2 of 3.

PAGE 1

CONTRACT DIRIBUTION LIST VIRGINIA CONTRACTING ACTIVITY Building 6000, Bolling AFB Delivery Order /Task Order: REQ: Admin Mod ro: ~DRESS: COPIES l. Contractor Bigelow Aerospace Advanced "Duplicate Original V Contractor Co " 2. Payment Office NSA FINANCE AND ACCOUNTING OFFICE v (for Invoice status) 5. DI FE Representative 7. Contract File D.O. File (Ori • al COPIES: TOTAL NO. 7 DISTRIBUTION COMPLETED:

PAGE 2

6. ISSUED BY COOE HHQ402 7. ADMINISTERED BY U1 other than Item 6! CODE 2050 Virginia Contracting Activity Virginia Contracting Activity 8. NAME ANO ADDRESS OF CONTRACTOR (No .. street, coumy, State and ZIP Code) (XI 9A. AMENDMENT OF SOLICIATION NO. BIGELOW AEROSPACE ADVANCED SPACE STUDIES, DUNS: 827037768 10A. MODIFICATION OF CONTRACT/ORDER NO. 108. DATED (SEE ITEM 13) 11 . THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS The above numbered solicitation is amended as set for1h In Item 14. The hour and date specified for receip1 of Offers is extended, is 001 extended. Offers must acknowledge receipt of this amendment prior to tho hour and date specified In the sollchatlon or as emended. by one of the fellowing methods: (a)By completing Items 8 and 15, and returning copies of the amendment; (bl By acknowledging receipt of this amendment on each copy of the offer submitted; or le) By separate letter or telegram which Includes a reference to tho solicitation and omendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment your dosiro to change an offer already submi11cd, such change may be made by telegram or letter, provided each telegram or lotter makes roferenco to the solicita1ion and this arnondment. and is rocolvod prior to the oponing hour and date specified. 12. ACCOUNTING ANO APPROPIATION DATA (If required) Modification Amount: $0.QQ See Schedule Modification Obligated Amount: $0.00 13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14. CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 1OA. X 8. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFI ED TO REFLECT THE ADMINISTRATIVE CHANGES (Ruch as changBS in paying office. appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.1031b). C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF: D. OTHER (Specify type of modification and authority! E. IMPORTANT: Contractor 0 is not, Dis required to sign this document and return copies to the issuing office. 14. DESCRIPTION OF AMENOMENT/MOOIFICATION (Organized by UCF section headings, Including sollcttatlon/conlracl subject matter where feasible.) The purpose of this modification is to Change the COR designation on Contract HHM402-08-C-0072 in accordance with the terms below: a) The following individual is named as the Contracting Officer™s Representative: b) For guidance from the COR to be valid, it must be: 1.Consistent with the Statement of Work for this Contract. 2.Not constitute a new assignment of work or change the expressed terms, conditions, or specifications incorporated in this Contract. 3.Not constitute a basis for extension to the period of performance or delivery schedule. 4.Not constitute a basis for increase in any CUN quantities or in the total contract value. c) All other terms and conditions remain the same. Exceot as Dfovided herein all terms and conditions of the document referenced in ltom 9A or 1OA as heretoforo ch&flQ&d remains unchanged and in full force and effect (Signature of person authorized to sign! Previous odhion unusable Proscribed by GSA FAR [48 CFR) 53.243

Where this file fits in the PURSUE archive

This file is one of DoD's 282 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #230 of 282 by Anomalousness Index. Across the entire 478-file archive it ranks #405 of 478.

That places it in the lower-scoring band of the archive (405 of 478 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.

Anomalousness Index: 53/100

This is a reference document, not an encounter report, so the index has no encounter to measure here. The value above is the rubric's default for a document that describes no event, shown so every file in the archive can be ranked the same way. Not a probability of extraterrestrial origin - that number is not honestly computable from the released files and this tracker refuses to publish it.

🤖 AI-ASSISTED SCORING · methodology

The six rubric components break down for this file as follows. Each component has a weighted contribution to the final score; the per-component explanation below describes what this file's particular value on that component means in the rubric's framework.

sensor quality (eyewitness only) 30 × 0.25 = 7.5

This file is a reference document, not an observation, so no sensor, camera, or witness captured anything. The rubric's sensor axis has no not-applicable option, so a document with no instrument record sits on its lowest tier by default.

witness credibility (military personnel) 80 × 0.2 = 16.0

There is no witness: this is a document released by the Department of War, not a first-hand account. The rubric assigns this axis from the originating body, so the value reflects the source of the record, not anyone's testimony.

corroboration (single witness instrument) 60 × 0.2 = 12.0

Nothing is being corroborated, because the file does not report an event. Like every file in the archive it takes the rubric's single-source default.

kinematic anomaly (no kinematic data) 30 × 0.15 = 4.5

The file describes no object and no motion, so the kinematic axis takes the archive-wide 'no kinematic data' default.

mundane explanation available (weak mundane candidate) 70 × 0.1 = 7.0

Every file in the archive scores this tier. For a document that describes no event it carries no information about the record at all.

official disposition (unresolved no review) 60 × 0.1 = 6.0

The rubric's default for the file's release status (files released with redactions are catalogued as unresolved, unredacted ones as open). For a document that reports no event this describes how the file was released, not anything that happened.

Bottom line on the score: the 53/100 is the rubric's default for a document that reports no encounter, so it is not a finding about any event and should not be compared with the scores of sighting reports. For the full per-axis weights and the rubric JSON, see /methodology.

Related files in DoD

Other PURSUE files in the same category, ranked by Anomalousness Index.

DoD · VIDEO SCORE 68

DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023

DoD · VIDEO SCORE 68

DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…

DoD · VIDEO SCORE 68

DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020

DoD · VIDEO SCORE 68

DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020

DoD · VIDEO SCORE 68

DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015

DoD · VIDEO SCORE 68

DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020

BROWSE ALL 478 FILES →

Verification

SHA-256:

6998e57cacab3b6e53950843c67ac165c9f0cfd49972edf4dafd822eed804eb0

This hash is the SHA-256 of the file body war.gov served on the verification date above. War.gov has re-processed some file bodies since first release (re-compression + OCR, no content removed - see /changes); we re-verify and record the change rather than silently serve a stale hash. How to check this yourself →

Source: https://www.war.gov/medialink/ufo/sept-18/release-06/assets/DOW-UAP-D114_AAWSAP-Contract-Modification-P00003-May-18- 2010.pdf

📡 Subscribe via RSS 🔔 Watch on GitHub