1 2 3 4 5 6 7 8 9 10 11 12 13 14

A good example of this rapid response and prototype evolution was the implementation (1993-94) of the GOES 2 link. However, after GOES was successfully run for the winter 1993-94 season, there was no follow-up replacement of prototype electronics with acceptance grade items. Even though GOES 2 became unavailable, it was known that GOES 3 would use its electronics. No documentation was made available to the next year's staff. The summer season should have been used to incorporate breadboard circuitry into a more reliable state.

9. Spares

How much spare equipment should we require? How much risk should we accept?

II. Network

Good Communications is founded on good networking. Routers and network design should be considered as part of the communications infrastructure. Indeed, that infrastructure could even be considered to extend into the very desktop computers used by researchers.

One of the problems with the station network is, as we see it, the continued dominance of the network by ASA's managerial data traffic (MAPCON, etc.) on the backbone. We propose a plan to continue use of the Novell system for ASA Operations personnel, while creating a more research oriented design for the network. We also discuss a Distributed Management scenario.


1. Network Plan

An example of a possible network architecture that is modular and responsive to changing technology is shown below:

(Novell server any branch)
domain serverOPS_router
(sun or alpha)|
____|________________|___________________backbone (sci or comms or both)
Science router|
_______________________________|_______ Comms_router
Skylab Clean_air MOPF |Science bldg|
IRISrouter | (+appletalk to TCP/IP)(voice MUX)
|| (general printer)
||____CARA astronomy net
(Appletalk to TCP/IP)
(general printer)

- 7 -