Slide 5 of 5
Notes:
- Last February, J2FT surveyed the Space Control community as to what types of information an SCDB should include. We received extremely detailed and extensive replies, which have now been consolidated into a single master list (thanks, Joint Aerospace Reserve Program--JARP!)
- SCDB has also been incorporated into the Space COI’s formal proposal to JIMO for the development of a space intelligence Knowledge Map. We are awaiting JIMO’s approval of that proposal, and with their support anticipate beginning work next year.
- A CONOPS for the SCDB is already under development
- Once we have matured/detailed whatever, work must begin immediately to develop the “permissions” required for the SCDB and K-Map to pull information from various agencies. As mentioned earlier, this will be a challenge. We must also figure out how we will address information that is produced or published by more than one agency: whose data will be used? How will conflicts be resolved? This will require close coordination with DoDIPP as to “lanes of the road” issues--who has the mandate to produce what intel.
- As we identify intelligence gaps, i.e. requirements from the list for which there is no data, then collection and production responsibilities must be determined, and local datastores reconfigured as required.
- Additionally, the software and hardware support for SCDB must be finalized. SCDB is envisioned to be a distributed data portal, with a unified web “front end” for ease of use. Continued JIMO development of JADE architecture can support the security requirements of accessing these distributed data stores.
(also need to address what Col Huff said about linking databases and analytical tools)
