Development of James Web Space Telescope (JWST)


Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Development of James Web Space Telescope (JWST)

  1. 1. Development of James Web Space Telescope (JWST) Ground Systems Using an Open Adaptable Architecture Bonnie Seaton Alan Johns Jonathan Gal-Edd NASA/GSFC Curtis Fatig GSFC/SAIC Ronald Jones GSFC/ASRC Aerospace Francis Wasiak GSFC/General Dynamics
  2. 2. Observatory <ul><li>JWST mission under development by NASA (launch planned for 2013) with major contributions from European and Canadian Space Agencies. The mission is designed to address four science themes: </li></ul><ul><ul><li>Observation of the first luminous objects after the Big Bang </li></ul></ul><ul><ul><li>Assembly of these objects into galaxies </li></ul></ul><ul><ul><li>Birth of stars and planetary systems </li></ul></ul><ul><ul><li>Formation of planets and origins of life </li></ul></ul><ul><li>The JWST ground segment is an open adaptable architecture that will be used to support evolving requirements for a mission with 10-year development and operational cycles </li></ul>
  3. 3. Open Adaptable Architecture <ul><li>JWST project requirement </li></ul><ul><ul><li>Same ground system will be used for science instrument and spacecraft development, I&T and mission operations </li></ul></ul><ul><ul><ul><li>Common Systems: real-time command and telemetry (C&T) system, database </li></ul></ul></ul><ul><ul><li>Intent is to ‘test-as-you-fly’ to identify problems early in the lifecycle </li></ul></ul><ul><ul><li>System will evolve during 10 year development cycle prior to launch </li></ul></ul><ul><li>Open Adaptable Architecture Themes </li></ul><ul><ul><li>Support design upgrades and take advantage of new technologies </li></ul></ul><ul><ul><ul><li>Each component independent of other components </li></ul></ul></ul><ul><ul><ul><li>Use ICDs, translators, ingest scripts for interfaces </li></ul></ul></ul><ul><ul><ul><li>Select best products (real-time, analysis, automation, etc.) </li></ul></ul></ul><ul><ul><li>Implement using COTS rather than a home grown system </li></ul></ul><ul><ul><li>Database is application independent </li></ul></ul><ul><ul><li>Follow industry standards (CCSDS, OMG, IEEE, etc.) </li></ul></ul><ul><ul><li>Phased approach for evolving ground system </li></ul></ul><ul><ul><ul><li>Phase 1: Development System </li></ul></ul></ul><ul><ul><ul><li>Phase 2: Integration and Test (I&T) System </li></ul></ul></ul><ul><ul><ul><li>Phase 3: Operations System </li></ul></ul></ul>
  4. 4. Ground System Implementation Decisions (1 of 3) <ul><li>Use the operational command and telemetry system for development and I&T </li></ul><ul><ul><li>Use the same data and interfaces throughout the life of JWST </li></ul></ul><ul><ul><li>Design modular components at the start of the development </li></ul></ul><ul><ul><li>Provide upgrade path from the beginning of the process </li></ul></ul><ul><ul><li>Explore automation technologies such as system messaging </li></ul></ul><ul><li>eXtensible Markup Language (XML) </li></ul><ul><ul><li>JWST XML compatible with Consultative Committee for Space Data Systems (CCSDS) XTCE </li></ul></ul><ul><ul><li>Database is just the data, not tied to a particular application </li></ul></ul><ul><ul><li>Allows for cross-referencing of command, telemetry and ops products </li></ul></ul><ul><ul><li>Engineering data saved in a manner to be application independent </li></ul></ul>To deal with a project of this scope where technology and software will evolve, the following implementation decisions have been made:
  5. 5. Ground System Implementation Decisions (2 of 3) <ul><li>Project Reference Database </li></ul><ul><ul><li>Common area for all mission-related information </li></ul></ul><ul><ul><li>Data independent of any system </li></ul></ul><ul><ul><li>Configuration management of mission related information </li></ul></ul><ul><li>Onboard scripts </li></ul><ul><ul><li>Increased processing power of flight processor for event driven operations </li></ul></ul><ul><ul><li>Use Java script COTS engine </li></ul></ul><ul><ul><li>Use modular and common components onboard </li></ul></ul><ul><ul><li>Data dictionary </li></ul></ul><ul><li>CCSDS File Delivery Protocol (CFDP) </li></ul><ul><ul><li>Reduce functionality needed at control center </li></ul></ul><ul><ul><ul><li>Use Deep Space Network to provide Level 0 processing of science data </li></ul></ul></ul><ul><ul><li>Increase data reliability by providing a reliable file downlink protocol </li></ul></ul><ul><ul><li>Use CCSDS standards for software and maintenance </li></ul></ul>
  6. 6. Ground System Implementation Decisions (3 of 3) <ul><li>Batch decommutated data </li></ul><ul><ul><li>Common generic format for all engineering data </li></ul></ul><ul><ul><li>Engineering exchange format for other ground system components </li></ul></ul><ul><ul><li>Data storage format prior to ingest into archive </li></ul></ul><ul><li>Engineering archive and trending </li></ul><ul><ul><li>Common engineering data store for the life of the mission </li></ul></ul><ul><ul><li>Provide automated reporting </li></ul></ul><ul><ul><li>Provide tools to analyze the status and performance of the JWST observatory </li></ul></ul>
  7. 7. Phased Approach Evolution of the Ground System C&T System Load & Dump Tools Database C&T System Database Analysis System Simulator Phase 1 (Development) Development and I&T ground systems built around eventual operations core components: Flight Operations System (FOS), and Project Reference Database System (PRDS) Phase 2 (I&T) Phase 3 (Operations) Wavefront Sensing & Control Exec (WFSC Exec) JPL Deep Space Network (DSN) GSFC Flight Dynamics Facility (FDF) STScI Science & Operations Center (S&OC) Flight Operations Subsystem (FOS) Data Management Subsystem (DMS) Wavefront Sensing & Control Exec (WFSC Exec) Proposal Planning Subsystem (PPS) Operations Script Subsystem (OSS) Project Reference DB Subsystem (PRDS) NISN Observatory Simulators (OTB/STS )
  8. 8. Phase 1 Development System <ul><li>Initial systems know as Science Instrument Development Units (SIDUs) are used during development of the science instruments and flight software </li></ul><ul><li>In 2004, Eighteen SIDU systems built and deployed to: GSFC; JPL; Abingdon, England; Palo Alto, California; Ottawa, Canada; Munich, Germany; Madrid, Spain; and Cambridge, Canada </li></ul>
  9. 9. Phase 2 I&T System <ul><li>In 2006/2007, the system evolves into an I&T system with the deployment of seven Science Instrument Integrated Test Sets (SITS) which will be used for testing of hardware components </li></ul><ul><ul><li>First delivered May 2006 to Abingdon, England </li></ul></ul><ul><li>In 2008/2009, the final two I&T systems, Instrument Test Support Systems (ITSSs), will be used for final integration testing </li></ul>
  10. 10. Phase 3 Operations Ground System <ul><li>The base Phase 1 development system will have evolved into the operations system </li></ul><ul><li>The flight build of the operations system will be delivered in 2011, two years before launch </li></ul>JPL Deep Space Network (DSN) GSFC Flight Dynamics Facility (FDF) STScI Science & Operations Center (S&OC) Flight Operations Subsystem (FOS) Data Management Subsystem (DMS) Wavefront Sensing & Control Exec (WFSC Exec) Proposal Planning Subsystem (PPS) Operations Script Subsystem (OSS) Project Reference DB Subsystem (PRDS) Observatory Simulators (OTB/STS ) Development, I&T Systems Heritage NISN
  11. 11. Lessons Learned to Date <ul><li>Various vendors supplying different components keep the total system open and adaptable </li></ul><ul><li>Interoperable plug and play concept works if ICDs are defined </li></ul><ul><li>Central XML database is application independent which minimizes cost and is CCSDS XTCE compliant </li></ul><ul><li>Open engineering and science data formats that are defined in an ICD allow for dissimilar systems to have access to the data without impacting the design </li></ul><ul><li>CCSDS CFDP reduces amount of processing needed at end user site, increases data efficiency, and eases onboard recorder management problems </li></ul><ul><li>Web-based technologies for user displays provide more flexibility, quicker development, and reduce long-term cost </li></ul><ul><li>Evolving common C&T and database systems for development through I&T to operations is the best approach to ensure mission success </li></ul><ul><li>Phased approach to system development allows for technology upgrades to occur naturally </li></ul>After four years of real-life experiences with an open adaptable architecture, the JWST ground system team has learned that:
  12. 12. Full Scale JWST Model at the Goddard Space Flight Center