The following points should be considered when evaluating candidate TT&C system designs:
* Key functions, interfaces, and performance drivers should be properly identified and delineated.
* System sizing should be supported by an analysis of performance drivers (Telemetry, Commanding, Orbit Analysis, LAN, DBMS, etc.)
* TT&C system designs should demonstrate an understanding and proper application of relevant technologies. In particular, proper use of middleware is very important.
The future work related to this reference architecture relates primarily to applying the architecture, improving it, and reformulating it. Several applications were discussed at the beginning of this report including using of this reference architecture as a baseline for evaluating GFE TT&C systems and for comparing against the DCCS architecture. The latter exercise will also provide valuable feedback regarding the utility of the reference architecture itself.
The DCCS comparison will also help frame the DCCS system in terms of this architecture, facilitating development of architecture options that can help evolve the DCCS architecture, so it can satisfy the more general requirements of the core TT&C system. This effort will also help to define the core boundaries and exploring options for incorporating the core into the satellite mission control segments.
Our work with the vendor and user communities in defining a standard TT&C architecture will provide further feedback. Hopefully, working with experts in the reference architecture technology will help us improve the methods of representing this architecture.
Finally, it is important to continue refining our definition of generic APIs between TT&C applications and service layer components such as DSSs and DBMSs. This will encourage the standardization of the interfaces between TT&C applications and drive vendors to meet these standards. The overall effect will be to lower system development costs and simplify the whole COTS integration process.