2. The Government is interested in innovative approaches for developing a low cost, configurable, small form factor (5cm x 5cm or smaller), low power (20mW-100mW), releasable NSA Type-1 using Suite B algorithms for telemetry, tracking, and commanding (TT&C) and mission data decryption/encryption AVE ECU for CubeSats. For this RFI, CubeSats will be defined as having relatively short mission lives and 1U form factor (10cmX10cmX10cm).
3. The Government is also interested in innovative approaches for developing a low cost, configurable GOE ECU with NSA Type-1 using Suite B algorithms for TT&C and mission data decryption/encryption for CubeSats.
4. The vendor should provide a white paper with schedule and Rough Order of Magnitude (ROM) for both the AVE and GOE ECU solution(s) and should address their recommended approach for each listed item while keeping in mind the following order of importance:
a. AVE ECU Size/Weight/Power-show your analysis and prioritization in optimizing these criteria for your AVE solution, ideally smaller than 5cmx5cm and use 20mW-100mW of power.
b. Cost to reach prototype demonstration for AVE and GOE
c. Cost and schedule to reach prototype demonstration and estimated unit cost at production for AVE and GOE
d. NSA Certification Approach for AVE and GOE
e. Suite B Algorithm(s) employment-explain what algorithm you will use and how you will implement the algorithm for AVE and GOE
f. Minimum and maximum data rate-explain your analysis and assumptions for AVE and GOE
g. Interfaces-explain your choice of already established commercial standard interfaces for data, control, and power connections (physical layer architecture) for AVE and GOE. The GOE should utilize a commercial standard IPv6 interface, with the ability to be actively remotely managed by a network management system utilizing commercial standard practices.
h. GOE and AVE cryptographic capability-explain how your solution is capable of encryption/decryption with the same algorithm, mode, and key management plan and how it is compatible with your AVE device overall. Also discuss your data dissemination plan.
i. Key Management-explain your key storage and key management plan for the AVE and GOE. The GOE should use a standard DS-101 interface for key fill.
j. Environment-define the intended operating environments for the GOE device.
k. Channels-define the number of channels that would be available for the AVE and GOE. Explain whether each channel will be duplex or simplex in relations to the data rates.
5. This Sources Sought Announcement issued by CPSD solicits industry to provide information for a miniaturized, modular, cryptographic AVE/GOE solution with decreased size, weight, and power (SWaP) via innovative processes, novel technologies, and improvement of existing products for CubeSats.
6. Interested parties for this Sources Sought Announcement should respond to Lt Lauren White at (210) 925-6814, or e-mail: [email protected] or Sheena Burney at (210) 925-7160, or email: [email protected]. All inquiries must be received on or before 25 March 2011, 4:00PM CST.