SOW.pdf
PDF 281 KB Posted
- Solicitation number
- 80NSSC804653Q
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFQ Open Market.pdf | ||
| RFQ Open Market.pdf | ||
| SOW.pdf | ||
| BusinessCanvasModelTemplateM.pdf |
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
STATEMENT OF WORK
Commercial Prototyping of a Local Positioning Device/Node
1. Objective The National Aeronautics and Space Administration (NASA) is requesting proposals from contractors interested in and capable of supporting its requirements for the development of a prototype for a Local Positioning Device/Node System. The Contractor shall develop a system that consists of five (5) standalone units (nodes), in which each node is capable of wirelessly communicating with its peer nodes simultaneously. The purpose of the Local Positioning Device/Node is to operate autonomously to aid safe navigation of Unmanned Air Vehicles and Unmanned Air Systems (UAV/UAS). NASA shall be responsible for any testing on UAV/UAS after contract delivery. The intent of this prototyping activity is to bring the patented technology to a higher technology readiness level and to gain a better understanding of the nuances of the technology for future licensing and/or further research at NASA.
Patent References:
U.S. Patent 10,736,062 - System and Method to Synchronize Clocks Across a Distributed Network of Nodes U.S. Patent 10,025,344 - Self-Stabilizing Distributed Symmetric-Fault Tolerant Synchronization Protocol
Additional References:
Video: NASA' Clock Synchronization Techniques for Distributed Systems - YouTube NASA Technical Memo (TM): An Autonomous Distributed Fault-Tolerant Local Positioning System - NASA Technical Reports Server (NTRS)
2. Requirements and Specifications The Local Positioning Device/Node System shall consist of five units (nodes) capable of communicating wirelessly with each other and other similar nodes simultaneously as described in U.S. Patent No. 10,025,344 - Self-Stabilizing Distributed Symmetric-Fault Tolerant Synchronization Protocol. The Node System shall be capable of executing the protocol specified in U.S. Patent 10,736,062 - System and Method to Synchronize Clocks Across a Distributed Network of Nodes. and meet the following specifications:
2.1 A node consists of one transmitter and a set of receivers capable of communicating with all other peer nodes simultaneously, i.e., non-interfering, bidirectional wireless communication with a range of up to 2km (about 1.25 miles).
Note: The set of receivers depends upon how communication is implemented, thus, a set may consist of one or more (up to a maximum of the nodes in the network) receivers.
2.2 Each node shall be capable of processing multiple incoming simultaneous communication messages (from its receivers), executing the protocol, and broadcasting messages per protocol.
https://pdfpiw.uspto.gov/.piw?PageNum=0&docid=10736062&IDKey=361CAC1FD35F%0D%0A&HomeUrl=http%3A%2F%2Fpatft.uspto.gov%2Fnetacgi%2Fnph-Parser%3FSect1%3DPTO1%2526Sect2%3DHITOFF%2526d%3DPALL%2526p%3D1%2526u%3D%25252Fnetahtml%25252FPTO%25252Fsrchnum.htm%2526r%3D1%2526f%3DG%2526l%3D50%2526s1%3D10%2C736%2C062.PN.%2526OS%3DPN%2F10%2C736%2C062%2526RS%3DPN%2F10%2C736%2C062 https://pdfpiw.uspto.gov/.piw?Docid=10025344&homeurl=http%3A%2F%2Fpatft.uspto.gov%2Fnetacgi%2Fnph-Parser%3FSect1%3DPTO2%2526Sect2%3DHITOFF%2526u%3D%25252Fnetahtml%25252FPTO%25252Fsearch-adv.htm%2526r%3D2%2526p%3D1%2526f%3DG%2526l%3D50%2526d%3DPTXT%2526S1%3D10,025,344%2526OS%3D10,025,344%2526RS%3D10,025,344&PageNum=&Rtype=&SectionNum=&idkey=NONE&Input=View+first+page https://pdfpiw.uspto.gov/.piw?Docid=10025344&homeurl=http%3A%2F%2Fpatft.uspto.gov%2Fnetacgi%2Fnph-Parser%3FSect1%3DPTO2%2526Sect2%3DHITOFF%2526u%3D%25252Fnetahtml%25252FPTO%25252Fsearch-adv.htm%2526r%3D2%2526p%3D1%2526f%3DG%2526l%3D50%2526d%3DPTXT%2526S1%3D10,025,344%2526OS%3D10,025,344%2526RS%3D10,025,344&PageNum=&Rtype=&SectionNum=&idkey=NONE&Input=View+first+page https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DoyXsiE9CuK8&data=04%7C01%7Cnancy.s.hornung%40nasa.gov%7C25065add7bda43dc40b708d92cf2cac4%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637590243550521413%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mJ69zZ%2BWhxG%2Fl0F6IV%2BOyvGoKmnspx5YJ6G8zCXcbTY%3D&reserved=0 https://ntrs.nasa.gov/citations/20170007192 https://ntrs.nasa.gov/citations/20170007192 https://pdfpiw.uspto.gov/.piw?PageNum=0&docid=10736062&IDKey=361CAC1FD35F%0D%0A&HomeUrl=http%3A%2F%2Fpatft.uspto.gov%2Fnetacgi%2Fnph-Parser%3FSect1%3DPTO1%2526Sect2%3DHITOFF%2526d%3DPALL%2526p%3D1%2526u%3D%25252Fnetahtml%25252FPTO%25252Fsrchnum.htm%2526r%3D1%2526f%3DG%2526l%3D50%2526s1%3D10%2C736%2C062.PN.%2526OS%3DPN%2F10%2C736%2C062%2526RS%3DPN%2F10%2C736%2C062
2.3 The node shall communicate on one of the open frequency bands (e.g. 900 MHz, 2.4 GHz, 5 GHz) and follow FCC guidelines for radiated power.
2.4 The node shall transmit to other peer nodes on a separate channel within the chosen frequency band, i.e., without interfering with its peers and others who might be using some of these channels. Communication is based on the protocols in the patent.
2.5 Prior to operations, the channels used by the receivers and transmitter of the nodes shall be selected from the set of available channels in the frequency band.
2.6 The node’s transmission channel shall be selectable and distinct from its peer nodes, i.e., a node is not hardwired to a specific channel. The set of options = {NONE, Ch1, .. , Chk}, where k ≥ 5. NONE means the node will not transmit anything. This option is used for passive node operations as in Test Plans #3 and #4 (see below).
2.7 Each receiver of the node shall be selectable to receive communication messages from the set of channels associated with the transmitters, i.e., the set of options for a receiver = {Ch1, .. , Chk}, where k ≥ 5.
Below tables show one realization of the graph and how the nodes are connected:
Node Receivers N1 Ch1 = N2 Ch2 = N3 Ch3 = N4 Ch4 = N5
N2 Ch1 = N1 Ch2 = N3
N3 Ch1 = N1 Ch2 = N2
N4 Ch1 = N1 Ch2 = N2 Ch3 = N3
N5 Ch1 = N1 Ch2 = N2 Ch3 = N3 Ch4 = N4
2.8 The nodes shall broadcast communication messages (Synch, Init, Echo) per the format, content, and timing outlined in U.S. Patent No. 10,736,062 and NASA/TM. The Synch, Init, Echo messages are defined in the patent and NASA/TM at the application layer, i.e., not at the physical layer.
2.9 The nodes shall broadcast periodic navigational signals used by UAS, similar to GPS messages, i.e., (x, y, z,) and t, where (x, y, z,) is the node’s location and t its local time/clock.
2.10 The nodes shall have an onboard oscillator/digital clock. The bound on the oscillator drift rate shall be ρ, and 0 ≤ ρ << 1 (equal to a drift of no more than 10 parts per 1,000,000).
2.11 The node shall be portable and operate on one or more rechargeable batteries and be able to charge and run off of standard U.S. wall power (110/120V AC).
2.12 The node shall be portable, operate standalone, weigh up to 750 grams (about 1.6 pounds) with embedded antenna, and sized to fit on a 20lb UAV/UAS.
2.13 The node shall store communication data and have the capability of being downloaded for analysis.
2.13.1 The nodes shall have memory storage of no less than 128GB.
2.13.2 The node shall have a backend interface to a laptop running Microsoft
Windows (wired/ethernet), to download and display the data.
2.14 The Contractor shall develop a software Graphic User Interface (GUI) that is Microsoft Windows based and shall run on a laptop to collect, download, and display data from a node (any node)
2.15 The software shall aid in debugging and is used for visual purposes, displays the graph of network of nodes with their relative distances from each other and the position of the object/UAV/UAS as in Figure 5 of the U.S. Patent No. 10,736,062.
2.16 The GUI shall overlay the graph of network onto a digital map.
2.17 The software shall have the capability to connect the computer to any of the system nodes to collect and display the data in real-time.
3. Deliverables
3.1 The Contractor shall submit a Local Positioning Device/Node System design document and a validation and comprehensive test plan, for approval by the NASA Technical Point of Contact, within 2 months of award. The test plan shall include the following tests:
Test Plan #1: 4-node system, N1 through N4, to establish timing synchrony and network geometry, i.e., position of the nodes relative to each other.
Test Plan #2: 5-node system, N1 through N4 and N5, to establish timing synchrony and local positioning of the 5th node. This is referred to as Active Participant in the NASA/TM.
Test Plan #3: The 5th node is passive (does not transmit) and uses data from the synchronized 4-node system of Test Plan #1 to determine its own relative time and location to the graph. This is referred to as Passive Participant in the NASA/TM.
Note: For Test Plans #2 and #3, the system should demonstrate the 5th node is mobile but on the ground.
Note: NASA will conduct additional testing at NASA facilities. NASA future testing plans to perform the same as Test Plan #3 but the 5th node is flying on a UAV/UAS.
3.3 The Contractor shall provide a complete list of components compliant with all supply chain acquisition law to be approved by the Government within 2 months of contract award.
3.4 The Contractor shall build the Distributed Network Node System prototype within 6 months of award.
3.5 The Contractor shall within 10 months of award:
3.5.1 Complete testing of the Distributed Network Nodes System prototype per the approved Validation Test Plan outlined in Section 3.1 of the Deliverables noted above and provide documented evidence of the testing performed.
3.5.2 Deliver the Distributed Network Node System prototype, per the specifications outlined in SOW Section 2, including all documents and software (source code, executable, and software documentation), to NASA Technical Point of Contact at the following address: NASA Langley Research Center, Hampton, VA 23681
4. Place of Performance
4.1 Contractor’s facility within the United States.
4.2 Contractor shall be responsible for delivery/shipment of the Distributed Network Nodes
System to NASA Langley Research Center Hampton, VA 23681.
5. Period of Performance The Period of Performance shall be 12 months from the Date of Contract Award.
6. NASA Technical Point of Contact To be completed upon contract award.
FOR ANY ADDITIONAL QUESTIONS/CONCERNS PLEASE VISIT THE
BELOW PUBLICATION PAGE
https://shemesh.larc.nasa.gov/people/mrm/publications.htm
File details come from the government source that posted it. Updated .