THIS TASK ORDER IS A COST-PLUS-FIXED-FEE, FULLY FUNDED TASK ORDER UNDER CONTRACT NNK17LA01C. THE PURPOSE OF THIS TASK ORDER IS TO AUTHORIZE WORK ON SPECIAL STUDY LSP-18-012 MULTIPLATFORM TRANSIENT RECORDER STUDY OBJECTIVE: THE OBJECTIVE IS TO STUDY IS TO PROVIDE A FEASIBILITY STUDY REPORT AND PROTOTYPE HARDWARE OF AN EXPLOSION PROOF TRANSIENT RECORDER DESIGNED TO DETECT ELECTRIC/MAGNETIC FIELDS AND UMBILICAL CURRENTS DURING ALL PRE-LAUNCH PHASES INCLUDING VEHICLE ROLL-OUT/ERECTION BACKGROUND: SINCE ALL MISSIONS CAN BE EXPOSED TO LIGHTNING AND MANY AT REMOTE LOCATIONS HAVE MINIMAL LIGHTNING PROTECTION SYSTEMS, LIGHTNING MONITORING AND LIGHTNING EFFECTS MONITORING ARE COMMONLY REQUESTED BY OUR SPACECRAFT AND VEHICLES. THE CURRENT PORTABLE LIGHTNING INSTRUMENTATION SYSTEM CAN ONLY BE USED BEFORE ROLL-OUT. WHEN THE HIGH-SPEED TRANSIENT RECORDER IS INTEGRATED INTO THE PROPOSED SUPPORTING INFRASTRUCTURE DESCRIBED IN THIS STUDY, THE NEW LIGHTNING INSTRUMENTATION SYSTEM WOULD ALLOW OPERATORS TO ACCURATELY DETECT AND QUANTIFY ALL CONDUCTED AND RADIATED LIGHTNING-RELATED TRANSIENTS THAT MAY HAVE DELETERIOUS EFFECTS ON THE VEHICLE AND PAYLOAD. TASKS: EXPLORE THE POWER CONDITIONING/FILTERING, PURGING, ENVIRONMENTAL/ELECTROMAGNETIC SHIELDING, COMMUNICATION, AND RAPID DATA REPORTING FEATURES THAT WOULD BE REQUIRED TO SUPPORT THE INSTALLATION OF AN INTEGRATED, MULTI-CHANNEL HIGH-SPEED TRANSIENT RECORDER TO MONITOR THE VEHICLE/PAYLOAD DURING ALL PHASES OF LAUNCH OPERATIONS. THE STUDY WILL ALSO ADDRESS INSTALLATION FEASIBILITY OF THIS RUGGEDIZED TRANSIENT RECORDER AT BOTH THE ATLAS AND DELTA LAUNCH PADS IN ADDITION TO THE SPACEX TRANSPORTER ERECTOR. THE STUDY WILL: 1. CHASSIS: A. WITH THE POWER, THERMAL MANAGEMENT, AND COMMUNICATION INFRASTRUCTURE (IF THE STAND-ALONE OPTION IS PURSUED), OR B. THE HARDWARE REQUIRED TO PERFORM THE INTEGRATION INSIDE AN EXISTING JUNCTION BOX TO FULFILL THE REQUIREMENTS LISTED ABOVE. 2. TEST REPORT -THE PROTOTYPE DEVELOPMENT STUDY WOULD INCLUDE THERMAL TESTING TO VERIFY OUTDOOR AND CLASS 1 DIV II OPERATIONS. 3. FINAL REPORT DESCRIBING HARDWARE CHOICES AND INTERFACES. THE PROTOTYPES INCLUDE ALL THE REQUIRED INFRASTRUCTURE BUT THE DATA ACQUISITION PCB.
THIS TASK ORDER IS A COST-PLUS-FIXED-FEE, FULLY FUNDED TASK ORDER UNDER CONTRACT NNK17LA01C. THE PURPOSE OF THIS TASK ORDER IS TO AUTHORIZE WORK ON SPECIAL STUDY LSP-18-012 MULTIPLATFORM TRANSIENT RECORDER STUDY OBJECTIVE: THE OBJECTIVE IS TO STUDY IS TO PROVIDE A FEASIBILITY STUDY REPORT AND PROTOTYPE HARDWARE OF AN EXPLOSION PROOF TRANSIENT RECORDER DESIGNED TO DETECT ELECTRIC/MAGNETIC FIELDS AND UMBILICAL CURRENTS DURING ALL PRE-LAUNCH PHASES INCLUDING VEHICLE ROLL-OUT/ERECTION BACKGROUND: SINCE ALL MISSIONS CAN BE EXPOSED TO LIGHTNING AND MANY AT REMOTE LOCATIONS HAVE MINIMAL LIGHTNING PROTECTION SYSTEMS, LIGHTNING MONITORING AND LIGHTNING EFFECTS MONITORING ARE COMMONLY REQUESTED BY OUR SPACECRAFT AND VEHICLES. THE CURRENT PORTABLE LIGHTNING INSTRUMENTATION SYSTEM CAN ONLY BE USED BEFORE ROLL-OUT. WHEN THE HIGH-SPEED TRANSIENT RECORDER IS INTEGRATED INTO THE PROPOSED SUPPORTING INFRASTRUCTURE DESCRIBED IN THIS STUDY, THE NEW LIGHTNING INSTRUMENTATION SYSTEM WOULD ALLOW OPERATORS TO ACCURATELY DETECT AND QUANTIFY ALL CONDUCTED AND RADIATED LIGHTNING-RELATED TRANSIENTS THAT MAY HAVE DELETERIOUS EFFECTS ON THE VEHICLE AND PAYLOAD. TASKS: EXPLORE THE POWER CONDITIONING/FILTERING, PURGING, ENVIRONMENTAL/ELECTROMAGNETIC SHIELDING, COMMUNICATION, AND RAPID DATA REPORTING FEATURES THAT WOULD BE REQUIRED TO SUPPORT THE INSTALLATION OF AN INTEGRATED, MULTI-CHANNEL HIGH-SPEED TRANSIENT RECORDER TO MONITOR THE VEHICLE/PAYLOAD DURING ALL PHASES OF LAUNCH OPERATIONS. THE STUDY WILL ALSO ADDRESS INSTALLATION FEASIBILITY OF THIS RUGGEDIZED TRANSIENT RECORDER AT BOTH THE ATLAS AND DELTA LAUNCH PADS IN ADDITION TO THE SPACEX TRANSPORTER ERECTOR. THE STUDY WILL: 1. CHASSIS: A. WITH THE POWER, THERMAL MANAGEMENT, AND COMMUNICATION INFRASTRUCTURE (IF THE STAND-ALONE OPTION IS PURSUED), OR B. THE HARDWARE REQUIRED TO PERFORM THE INTEGRATION INSIDE AN EXISTING JUNCTION BOX TO FULFILL THE REQUIREMENTS LISTED ABOVE. 2. TEST REPORT -THE PROTOTYPE DEVELOPMENT STUDY WOULD INCLUDE THERMAL TESTING TO VERIFY OUTDOOR AND CLASS 1 DIV II OPERATIONS. 3. FINAL REPORT DESCRIBING HARDWARE CHOICES AND INTERFACES. THE PROTOTYPES INCLUDE ALL THE REQUIRED INFRASTRUCTURE BUT THE DATA ACQUISITION PCB.
What this contract page answers
This is the canonical contract page for 80KSC018F0314. It summarizes the award identity, mission scope, obligated amount, customer, recipient, source evidence, and the exact program page that owns broader context.
Mission
SpaceX Program
Amount
$79,247
Recipient
Recipient not published
Source coverage
Additional source records pending
Contract evidence mix
Contract pages combine the normalized record with linked actions, notices, spending points, bidder records, and public source evidence when those records are available.
Actions
1
Notices
0
Spending points
1
Exact source records
0
Source and freshness notes
This page uses T-Minus Zero contract normalization plus linked public-source evidence. Award identifiers, source URLs, agency/customer fields, and amounts are shown only when available in the normalized source data.
Source label
USASpending award record
Freshness
Sep 12, 2026
Data policy
Published source fields only
Contract interpretation
Use this page to identify what the award is, who it is tied to, how much has been obligated, and which evidence rows support the contract record. Use the program link below for broader mission context and related program records.
Award date
2018-10-01
Agency/customer
AI SOLUTIONS INC
Source match confidence
Not matched
Contract relationship map
Use the links below to open related records: the program link adds mission context, the contract family link adds related opportunities, and the public source link opens the original award or contract record.
Use these internal paths to move from this exact contract row into the mission hub, program contract index, source evidence, and broader program pages that own surrounding context.
Search-first answers for this contract entity and its source identifiers.
What sources feed the contract data on this site?
Contract entities combine USAspending award references with SAM.gov-normalized procurement records (including PIID-linked actions, notices, and spending rows when available).
Why is there a canonical /contracts URL when program pages already exist?
Program pages keep mission context, while /contracts URLs consolidate duplicate contract entities into one indexable canonical URL so search engines attribute ranking signals to a single record.
Which identifiers should I search to find a specific government contract?
Use any of these identifiers: USAspending Award ID, PIID, contract key, solicitation ID, notice ID, recipient/awardee name, or agency/customer name.
How often do contract pages update?
Contract pages revalidate on a 10-minute cadence, while upstream source data refresh timing depends on ingest jobs and source-side publication timing.
What is the difference between SAM.gov and USAspending in these records?
USAspending primarily provides award and obligation visibility, while SAM.gov captures procurement lifecycle context such as solicitation notices and related action thread signals.
Why can the contract amount differ from another source?
Amounts can differ across snapshots because some sources report base award value while others include modification deltas, cumulative obligations, or later adjustments.
Can one contract appear in more than one program section?
Yes. A contract may appear in multiple program contexts; canonical entities are designed to consolidate those overlaps into a single URL for indexing and discovery.
What is a PIID on a contract detail page?
PIID stands for Procurement Instrument Identifier. It is the contracting identifier used to track related awards, actions, and notices across a procurement thread.
Where should I verify the official source record for this contract?
Use the Source record link on the contract detail page. The page also links back to the program-native detail page and, when available, the Artemis story page for thread context.
Why are actions, notices, or spending rows sometimes missing?
Missing rows usually mean no matched records were returned yet for that identifier set in the current source snapshot, not that the contract entity itself is invalid.
What exact terms should I search to verify this specific contract?
Use these identifiers in search: 80KSC018F0314 | 80KSC018F0314. Add terms like "USAspending", "SAM.gov", or the awardee name for faster exact matching.
