Logistics Reduction: RFID Enabled Autonomous Logistics Management (REALM)

Metadata Updated: February 28, 2019

The Advanced Exploration Systems (AES) Logistics Reduction (LR) project Radio-frequency identification (RFID) Enabled Autonomous Logistics Management (REALM) task focuses on the subset of autonomous logistics management functions pertaining to automated localization and inventory of all physical assets pertaining to, or within, a vehicle utilizing RFID technologies.[HTML_REMOVED]REALM technology can provide detailed data to enable autonomous operations such as automated crew procedure generation and robotic interaction with logistics and deep space habitats; this is especially of value where communication delays with Earth drive the need for self-reliance.[HTML_REMOVED] The REALM project will conduct a series of ISS technology demonstrations.[HTML_REMOVED] The first demonstration, REALM-1, started in February 2017.The problem of locating all mission items within and around a vehicle are complicated by many factors, including the desire to rely only on passive tags, restrictions on RF transmit power,[HTML_REMOVED]layered storage of logistics, the challenging RF scattering[HTML_REMOVED]environment of vehicles, and metallic storage enclosures. To address this complex problem, associated RFID technologies are partitioned into three classes:Dense Zone technologiesSparse Zone technologiesComplex Event ProcessingDense Zone technologies pertain to enclosures with conductive, or shielded, boundaries and an integrated RFID reader to interrogate the items contained therein. Sparse zone technologies address all areas exclusive of the dense zones, including the open areas of a habitat module in addition to crevices, for example, behind a rack. These technologies include fixed-zone readers, steered-beam antenna readers, and mobile readers such as robotic elements, crew-held readers, or crew-worn readers. With both dense and sparse zones, guaranteed real-time, on-demand reads are not possible, so [HTML_REMOVED]smart[HTML_REMOVED] applications, e.g., Complex Event Processing (CEP), are required to infer item locations based on context from the sparse and dense zone technologies.Mission details might drive a different combination of these three technologies. Therefore, in addition to maturing these individual technology areas, the LR REALM team will learn which combinations of technologies are best suited for specific missions. For example, dense zone technologies can be made highly accurate but entail greater mass compared to sparse[HTML_REMOVED]zone technologies. Sparse zone technologies typically cover greater volume per reader, but are more apt to miss tags because they cover a larger area. They still require readers, cables, and antennas to accomplish their function. The operational intelligence provided by CEP can likely be traded for the size, weight, and power associated with dense and sparse zone technologies, but the extent, and specific implementation, remain as knowledge gaps to be addressed by this effort.The REALM task is divided into three sub-technology projects: REALM-1, 2, and 3.REALM-1REALM-1 infrastructure will be developed and evaluated on ISS, with RFID hatch readers and antennas deployed in ISS Node 1, U.S. Laboratory, and Node 2. A ground- based CEP center will receive data from the ISS hatch readers and will provide operational intelligence that infers item locations. This effort is in collaboration with the ISS program payloads office and the ISS vehicle office, both of which provide cost sharing for development.[HTML_REMOVED] In FY15, manufacturing of the hatch readers, known as EMBER (EMBEdded RFID Reader), began, along with resident software development. In parallel, the CEP center was established, and the CEP team, including a university partner, began tailoring prior CEP work to NASA[HTML_REMOVED]s REALM goals. The REALM Test Bed was utilized for testing CEP concepts of operation prior to the processing of ISS REALM-1 data in succeeding years. In FY16, the hatch readers, antennas, and RF cables were developed. REALM-1[HTML_REMOVED]was launched[HTML_REMOVED]December 2016. Testing, evaluation, and advancement of the CEP will continue using the REALM Test Bed in advance of REALM-1 data downlinked from ISS. FY17 and FY18[HTML_REMOVED]are[HTML_REMOVED]devoted to the 12-month ISS technology demonstration of REALM-1.[HTML_REMOVED] Multiple cycles of visiting vehicles, and the subsequent loading, off-loading, and translation of cargo through ISS will provide for thorough REALM-1 assessment.[HTML_REMOVED] During this time, the CEP software will reside in a ground system and utilize the ISS REAM-1 data with crew activity data, inventory surveys, and imagery to improve the CEP location algorithms and evaluate the effectiveness of the hatch reader locations and ability to assess tagged item locations in non-REALM instrumented nodes.[HTML_REMOVED] The REALM-1 system is tentatively scheduled to end its experimental phase and transition to ISS sustaining support in FY19.REALM-2REALM-2 is an AES LR RFID interrogator payload on the Space Technology Mission Directorate (STMD)[HTML_REMOVED]Next Generation Free-Flyer (NGFF) that will take RFID [HTML_REMOVED]snapshots[HTML_REMOVED] during cargo movement[HTML_REMOVED]and refine item localization. In FY15, REALM-2 and Astrobee initiated discussions and identified a preliminary payload architecture and preliminary interfaces.[HTML_REMOVED]In FY16, the REALM-2 activity initiated formal interface development with the Astrobee project.[HTML_REMOVED][HTML_REMOVED]The REALM-2 task also initiated development of flight software that will reside in the mobile reader.[HTML_REMOVED] In FY17, REALM-2 will mature[HTML_REMOVED]portions of the flight hardware design and software.[HTML_REMOVED][HTML_REMOVED]The REALM-2 flight hardware will be fabricated and[HTML_REMOVED]then ground tested in an integrated flight-like Astrobee configuration in FY18.[HTML_REMOVED] It is anticipated that REALM-2 will be delivered in mid-FY19 to support Astrobee[HTML_REMOVED]s ISS flight experiment.REALM-3REALM-3 will provide a smart cargo transfer bag or rack drawer that can provide immediate feedback to the crew regarding items required for work or experiments. In FY15, REALM-3 was a small task and used the RFID MCTB prototypes to test various configurations.[HTML_REMOVED] These tests supported REALM-1/CEP development and supported inquiries from potential future collaborators. In FY16 and FY17, REALM-3 was limited in scope.[HTML_REMOVED] The REALM team determined concepts of operation and benefits of the RFID-enabled CTB in coordination with stakeholders. In FY18, REALM-3 will be developed and recommend an ISS flight demonstration[HTML_REMOVED]activity in late FY19.[HTML_REMOVED] The project will seek cost sharing from ISS for the ISS flight demonstration.

Access & Use Information

Public: This dataset is intended for public access and use. License: U.S. Government Work

Downloads & Resources


Metadata Created Date August 1, 2018
Metadata Updated Date February 28, 2019

Metadata Source

Harvested from NASA Data.json

Additional Metadata

Resource Type Dataset
Metadata Created Date August 1, 2018
Metadata Updated Date February 28, 2019
Publisher Space Technology Mission Directorate
Unique Identifier TECHPORT_93175
Maintainer Email
Public Access Level public
Bureau Code 026:00
Metadata Context https://project-open-data.cio.gov/v1.1/schema/catalog.jsonld
Metadata Catalog ID https://data.nasa.gov/data.json
Schema Version https://project-open-data.cio.gov/v1.1/schema
Catalog Describedby https://project-open-data.cio.gov/v1.1/schema/catalog.json
Harvest Object Id 7928fe41-57d9-4b24-b8bb-e38f7ccc03ca
Harvest Source Id 39e4ad2a-47ca-4507-8258-852babd0fd99
Harvest Source Title NASA Data.json
Data First Published 2020-09-01
Homepage URL https://techport.nasa.gov/view/93175
License http://www.usa.gov/publicdomain/label/1.0/
Data Last Modified 2018-07-19
Program Code 026:027
Source Datajson Identifier True
Source Hash a6bdf8af3ffeef45e1e5597f525bcdec68ada70b
Source Schema Version 1.1

Didn't find what you're looking for? Suggest a dataset here.