FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2013647281> ?p ?o ?g. }

• W2013647281 abstract "The Cassini-Huygens operations design, as described in a companion paper, relies on telecommunications and distributed computing to share operational responsibilities among JPL and instrument teams. From their home institutions, scientists are actively involved in planning, developing sequences, and commanding and monitoring the spacecraft. This paper proposes design guidelines, based on Cassini-Huygens experience, for future ground systems that face similar challenges of spatial decentralization and functional reallocation. In contrast to past deep space missions in which there was simply data exchange between JPL and scientists, the Cassini-Huygens environment has progressed into a complex of integrated systems. The lessons learned during this evolution include the following: (a) A logical architecture that can be overlaid on different physical implementations will reduce re-engineering for multiple environments. (b) Platform decisions should recognize the cost constraints of all potential users of project-supplied software. In a world accustomed to heterogeneous hardware, standardization on a single, expensive platform will create recurring conflict. (c) Separate systems will be bound by differing institutional restrictions, and upgrade patterns will differ according to institutional drivers and funding. The distributed operations paradigm has also accelerated the blurring of responsibilities between scientists and engineers. As the tools in the Cassini-Huygens ground system have evolved to support the dispersion of responsibilities such as spacecraft pointing and health & safety, these issues have been worked out: (d) Connectivity alone does not suffice. An electronic, up to date, widely accessible picture of the collective plan is required. (e) Allocation of functionality to tool must be managed at the project level to minimize redundancy. (f) Changes to the underlying constructs in the software architecture such as models and flight rules will apply to multiple tools in multiple systems. When the enhancements are introduced earlier in some places than in other places, substantial confusion can result from differing answers to the same question. The payoff for rapid introduction of improvements needs to be weighed against the penalty of discrepancies due to lack of synchronization. (g) Without specialist operators, tools need to be easier to use, have better documentation, and come with tech support. (h) When tools meet both engineering and science needs, contention for development resources intensifies. An arbitration process for prioritizing development tasks needs to be in place. (i) As in many modern systems with ongoing development, late interface changes due to asynchronous development of various systems are to be expected. BACKGROUND: The Paradigm Shift to Distributed, Networked Operations and Its Impact on the Cassini-Huygens Ground System Design For previous deep space missions, the spacecraft was operated from a mission center at JPL by a team composed of specialists for the various subsystems and of representatives for the science instruments. During the early stages of Cassini-Huygens operations planning, nascent telecommunications capabilities suggested the possibility of decentralizing operations. The operations activity was divided among JPL staff and science teams working from their home institutions. Meetings and office conversations have been supplanted by teleconferences and email. The change in philosophy, along with the explosion in networking, induced a supporting distribution of ground system capability. The mainframe computer with local terminals for each analyst has been replaced by multiple local area networks connected to the institutional networks of JPL and the other participating institutions and thence to the Internet. The project specific hardware has been Solaris workstations and servers since 1998, but most of the operations staff, whether at JPL or at the distributed sites use other machines as well including Windows PCs, Macs, or Linux boxes. Along with the decentralization of operations came a redivision of responsibility between engineers and scientists. The presence of onboard microcomputers in the instruments also contributed to a larger role for the science teams. Tasks that are now split between scientists and engineers (and are therefore done at various locales) include sequence construction, monitoring health and safety, spacecraft pointing, and flight rule checking. This has meant that the ground software tools are used by a wider community of diverse users rather than by a few specialist tool operators. Mission software that was previously executed in one room at JPL now runs all over the world in a variety of infrastructure settings. Figure 1. Overview of the Cassini Ground System opsnet instrument operations" @default.
• W2013647281 created "2016-06-24" @default.
• W2013647281 creator A5002586890 @default.
• W2013647281 creator A5044576119 @default.
• W2013647281 date "2004-05-17" @default.
• W2013647281 modified "2023-10-16" @default.
• W2013647281 title "Distributed Ground Systems for a Large Multi-Instrument Space Mission: Lessons Learned from the Cassini-Huygens Program" @default.
• W2013647281 doi "https://doi.org/10.2514/6.2004-606-403" @default.
• W2013647281 hasPublicationYear "2004" @default.
• W2013647281 type Work @default.
• W2013647281 sameAs 2013647281 @default.
• W2013647281 citedByCount "0" @default.
• W2013647281 crossrefType "proceedings-article" @default.
• W2013647281 hasAuthorship W2013647281A5002586890 @default.
• W2013647281 hasAuthorship W2013647281A5044576119 @default.
• W2013647281 hasConcept C104060986 @default.
• W2013647281 hasConcept C111919701 @default.
• W2013647281 hasConcept C121332964 @default.
• W2013647281 hasConcept C127313418 @default.
• W2013647281 hasConcept C127413603 @default.
• W2013647281 hasConcept C146978453 @default.
• W2013647281 hasConcept C178802073 @default.
• W2013647281 hasConcept C201995342 @default.
• W2013647281 hasConcept C2778572836 @default.
• W2013647281 hasConcept C2994201174 @default.
• W2013647281 hasConcept C41008148 @default.
• W2013647281 hasConcept C62649853 @default.
• W2013647281 hasConcept C92851284 @default.
• W2013647281 hasConceptScore W2013647281C104060986 @default.
• W2013647281 hasConceptScore W2013647281C111919701 @default.
• W2013647281 hasConceptScore W2013647281C121332964 @default.
• W2013647281 hasConceptScore W2013647281C127313418 @default.
• W2013647281 hasConceptScore W2013647281C127413603 @default.
• W2013647281 hasConceptScore W2013647281C146978453 @default.
• W2013647281 hasConceptScore W2013647281C178802073 @default.
• W2013647281 hasConceptScore W2013647281C201995342 @default.
• W2013647281 hasConceptScore W2013647281C2778572836 @default.
• W2013647281 hasConceptScore W2013647281C2994201174 @default.
• W2013647281 hasConceptScore W2013647281C41008148 @default.
• W2013647281 hasConceptScore W2013647281C62649853 @default.
• W2013647281 hasConceptScore W2013647281C92851284 @default.
• W2013647281 hasLocation W20136472811 @default.
• W2013647281 hasOpenAccess W2013647281 @default.
• W2013647281 hasPrimaryLocation W20136472811 @default.
• W2013647281 hasRelatedWork W1963774162 @default.
• W2013647281 hasRelatedWork W1977554751 @default.
• W2013647281 hasRelatedWork W1985270746 @default.
• W2013647281 hasRelatedWork W1990199580 @default.
• W2013647281 hasRelatedWork W2018004030 @default.
• W2013647281 hasRelatedWork W2090960668 @default.
• W2013647281 hasRelatedWork W2092160403 @default.
• W2013647281 hasRelatedWork W2167443653 @default.
• W2013647281 hasRelatedWork W4240500675 @default.
• W2013647281 hasRelatedWork W4244562463 @default.
• W2013647281 isParatext "false" @default.
• W2013647281 isRetracted "false" @default.
• W2013647281 magId "2013647281" @default.
• W2013647281 workType "article" @default.