Maryann Hutchison (The Aerospace Corporation), Kristen M. Kolarik (The Aerospace Corporation), Jeffry Waters (SPAWAR Systems Center Pacific)
Keywords: SSA
Abstract:
The space situational awareness (SSA) data we access and use through existing SSA systems is largely provided in formats which cannot be readily understood by other systems (SSA or otherwise) without translation. As a result, while the data is useful for some known set of users, for other users it is not discoverable (no way to know it is there), accessible (if you did know, there is no way to electronically obtain the data) or machine-understandable (even if you did have access, the data exists in a format which cannot be readily ingested by your existing systems). Much of this existing data is unstructured, stored in non-standard formats which feed legacy systems. Data terms are not always unique, and calculations performed using legacy functions plugged into a service-oriented backbone can produce inconsistent results. The promise of data which is interoperable across systems and applications depends on a common data model as an underlying foundation for sharing information on a machine-to-machine basis. M2M interoperability is fundamental to performance, reducing or eliminating time-consuming translation and accelerating delivery to end users for final expert human analysis in support of mission fulfillment. A data model is common when it can be used by multiple programs and projects within a domain (e.g., C2 SSA). Model construction begins with known requirements and includes the development of conceptual and logical representations of the data. The final piece of the model is an implementable physical representation (e.g., XML schema) which can be used by developers to build working software components and systems. The JMS Common Data Model v1.0 was derived over six years from the National SSA Mission Threads under the direction of AFSPC/A5CN. The subsequent model became the A5CN approved JMS Requirements Model. The resulting logical and physical models have been registered in the DoD Metadata Registry under the C2 SSA Namespace and will be made available through bidders’ libraries to contractors for both JMS and Space Fence. Harmonizing legacy JMS data interfaces is expected to take place incrementally during the next two years. As we add capabilities and services to JMS, the Common Data Model will continue to be extended as needed to support new development.
Date of Conference: September 11-14, 2012
Track: Poster