1 / 18

CCSDS Engineering Steering Group: report to the CCSDS Management Council

CCSDS Engineering Steering Group: report to the CCSDS Management Council. SEA Report – P Shames Renaissance Hotel, Portsmouth, VA 09 May 2010. SYSTEMS ENGINEERING AREA (SEA). Peter Shames (AD) Takahiro Yamada (DAD). Systems Engineering Area Report. CURRENT GROUPS WITHIN THE AREA.

danno
Download Presentation

CCSDS Engineering Steering Group: report to the CCSDS Management Council

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CCSDS Engineering Steering Group: report to the CCSDS Management Council SEA Report – P Shames Renaissance Hotel, Portsmouth, VA 09 May 2010

  2. SYSTEMS ENGINEERING AREA (SEA) Peter Shames (AD) Takahiro Yamada (DAD)

  3. Systems Engineering Area Report • CURRENT GROUPS WITHIN THE AREA • Information Architecture WG (& joint IPRWG meetings on registries, ISA BoF) • Security WG • Delta-DOR WG • SANA WG (completed, Yellow Book sent for review) • TimecodeWG (completed, Pink Sheets, waiting on test report completion) • Time Synchronization & Correlation BoF(charter meeting) • Space Link Security BoF (joint w/ SLS, reported in SLS) • SEA Responsibilities • Overall architecture for space mission communications, operations, and cross-support • Coordinate and collaborate with the other areas about architectural choices and options • Support the CESG in evaluating consistency of all area programs of work with the defined architecture • Create such working groups and BoFs as are required to progress the work of CCSDS

  4. Systems Engineering Area Report B. MEETING DEMOGRAPHICS UPDATE

  5. Systems Engineering Area Report • SUMMARY TECHNICAL STATUS • Information Architecture WG Goals: • Develop a high level Information Architecture Reference Model • Define Registry / Repository Reference model & associated registry information model (w/ IPR WG) • Develop Information System Architecture (ISA, SOA-like) reference model and services (BoF /charter discussions) • Working Group Status: • IAWG developed top down registry model & prototypes, info model & services interfaces, IPR WG developed bottom up XML registry & prototypes to be coordinated in joint meetings, White Book in development derived from ebXML • Extensive discussion on the Registry-Repository Architecture White Book; expect Red Book Aug 2010 • Agreement between IAWG and IPR WG members on creation of new Information Services Architecture (ISA) BoF, expect to subsume Reg/Rep work & collaborate with SM&C WG • A concept paper on the Information Service Architecture was produced along with a presentation. The presentation was given in the IPR/IA and Super SIG groups. • Working Group Summary Situation:

  6. Systems Engineering Area Report • Security WG Goals: • Develop security overview & threat assessment, and security architecture, framework and related standards • Current focus (security architecture, algorithms, key management, mission planners, glossary) • Working Group Status: • Progress • Algorithm document (BB draft Red-1) editing to be completed in Fall 2010. Planning for implementation & testing since doc is now Blue. • Security Architecture RIDs resolved, to be sent to CESG this summer. • Mission Planners Guide needs minor edits and then to Secretariat. • Key Management Green Book essentially completed. Initial draft of KM Blue Book for symmetric KM. • Reviewed 2nd draft of Security Glossary, complete by Fall 2010 • Network layer security – IPSec with Encapsulating Security Payload (ESP), only relevant in near Earth (out to Lunar) operations domain. • Good joint progress on Space Link Layer Security WG, reported in SLS • Working Group Summary Situation:

  7. Systems Engineering Area Report • Delta-DOR WG • Goals: • Develop detailed requirements for delta differential one-way ranging (Delta-DOR) service • Coordinate work in other WGs (SIS/Ranging, CSS/CSTS, MOIMS/Nav, CSS/SM) • Develop integrated vision of service and interoperability points • Working Group Status: • Magenta Book: second Agency review in process now. RIDs to be resolved during summer, expect MB publication in Fall 2010. • Delta-DOR Raw Data Exchange Format (DRDEF) Blue Book draft (Red-1): remaining issues were resolved. Book to be submitted for Editorial Reviewby Aug 2010, complete agency review of Red-1 by Dec 2010. • Raw Data Exchange document similar to TDM Blue Book (CCSDS 503.0-B-1) • Schedule for the Green Book has been pushed to Spring 2011 • Good progress on early & near term 3 agency interoperability validation, all three agencies committed to doing interoperability testing, YB test report being planned • There were meeting room issues, D-DOR was in lunch area, really not workable • WG reports that current CCSDS scheduling tool requires prototyping only AFTER the second Red Book review, this does not seem right • Working Group Summary Situation:

  8. Systems Engineering Area Report • SANA WG Goals: • Develop procedure for the Space Assigned Numbers Authority (SANA) • Working Group Status: • SANA operator in place, has met with most ADs and several WGs, several potential registries identified • Draft Yellow Book procedure CCSDS 313.0-Y-0.1 sent for final CESG review • Requests new “SANA Considerations” section and WG interaction on registry items • Includesdelegation, “grandfathers”, initial conditions, and future procedures, requests changes to CCSDS Procedures & Publications YBs • SANA WG to disband, SANA Steering Group formed • CESG Chair, SEA AD, SANA WG rep, and at least two other members to ensure stakeholder & agency balance • Working Group Summary Situation:

  9. Systems Engineering Area Report • Timecode WG Goals: • Update timecode formats • Explore need for time and synchronization standards • Working Group Status: • No meeting in Portsmouth • Revised Pink Sheets for Time Code reviewed & RIDs resolved • WG ready to disband once Pink Sheets are published • WG has done validation prototyping, needs to complete last tests and finalize interoperability report • Working Group Summary Situation:

  10. Systems Engineering Area Report • Time Correlation & Synchronization BoF Goals: • Develop outline for White Paper and requirements for time correlation and synchronization standards • Develop WG charter • Working Group Status: • BOF met on Wednesday afternoon with limited attendance (Greenberg (JPL), Pitts (MSFC), Sank (GSFC), Enrich (ESA)) . • The discussions defined the scope of the proposed working group and explored if there was adequate support for the effort • The only representatives were from NASA and ESA and both agencies expressed their desire to support the activity. • Plan to develop a Green Book on end to end Time Correlation methods and performance, error sources, and terminology. • Could not yet reach agreement on a recommended practice (MB) approach, but one is to be developed as a phased activity. • There is an interest in Time Synchronization for space networks and remote enterprises but the group felt that significant requirements gathering was necessary in this area as a first step. • A Working Group Charter was completed • BoFSummary Situation:

  11. Joint IA/IPR Meeting Reviewed registry-repository service architectures, agree on how to deal with ebXML, Red-1 to be available for review Aug 2010 Discussed relationship of registry-repository standards tospace Information Services Architecture (ISA) reference model and service architecture Agree to form a single new WG to tackle the ISA effort, agree to subsume Reg/Rep into ISA WG Met with RA SIG to present ISA concepts and BoF plans, explore how these efforts relate Joint SM/IA/IPR Meeting Discussed what the space Information Services Architecture (ISA) reference model and service architecture covers and its relationship to the rest of the CCSDS services Discussed the relationship between the SM&C “directory service” and the ISA framework Agreed to coordinate with SM&C and to evaluate the SM&C MAL as a possible messaging layer for ISA Sec WG / SDLS Meeting Joint meeting was productive and work is largely on track On-going discussions of how and where the security block is to be inserted in the space link frames Details reported by SDLS WG chair in SLS report Will require resources for interoperability testing … • Systems Engineering Area Report D. Cross Area Meetings

  12. Systems Engineering Area Report D. Cross Area Meetings, contd • IA WG / Reference Architecture SIG • Draft Information System Architecture (ISA), aka “SOA for Space”, presented to RA SIG • Relationship between CCSDS Reference Architecture and ISA seems to be understood and agreed • CCSDS Reference Architecture has a very broad charter to map CCSDS services and provide CCSDS scenarios, use cases, business cases, and reference and information models for existing and in-work CCSDS services • Seems to be agreement on a reference architecture framework consisting of RASDS with an added Service Viewpoint ala the Cross Support Services Architecture (also used in IOAG SISG efforts) • General concern that the very broad charter of this SIG is slowing efforts to resolve some critical issues vis-à-vis overlaps among CCSDS WGs • SEA recommends adopting a streamlined approach that focuses immediately on two items: • A rapid process to parse the CCSDS work products into the bins specified in the reference architecture, leveraging the work done in the SIG and the CCSDS Ref Arch Sketches, 24Nov09 • An analysis of the overlaps among current and planned CCSDS standards, using that binning, focusing particularly on the Functional Viewpoint (for layers 5-7) and the Protocol Viewpoint (for layers 1-4) • Do the rest of the modeling only after these initial efforts are completed

  13. Systems Engineering Area Report E. SUMMARY: MAJOR ACCOMPLISHMENTS AND CONCERNS IN LAST REPORTING PERIOD • IA WG • RASIM Reference Model Green Book Ready for final CESG review (June 2010) • General Registry-Repository Magenta Book drafted (Red-1 Aug 2010) • Information Services Architecture Concept Paper drafted (WP Aug 2010) • Sec WG • Security Algorithms Integrated Blue Book drafted (Red-1 Fall 2010) • Key Management Green Book to CESG (June 2010) • Symmetric Key Management Blue Book being drafted (WB Fall 2010) • Mission Planners Security Guide Green Book final to editor (June 2010) • Network Layer Security Green Book in planning (WB Fall 2010) • Delta DOR WG • D-DOR Reference Model Magenta Book in Agency review (Red-2 Jun 2010) • D-DOR Data Exchange Blue Book to Agency review (Red-1 Aug 2010) • D-DOR Overview Green Book draft begun (GB Apr 2011)

  14. Systems Engineering Area Report E. SUMMARY: MAJOR ACCOMPLISHMENTS AND CONCERNS IN LAST REPORTING PERIOD, contd • SANA WG • SANA Policy & ProceduresYellow Book final CESG review (May 2010) • Time Code WG • Time Code Pink Sheets Ready for final CESG review • Time Code Test Report Yellow Book pending tests (Aug 2010) • Time Synchronization & Correlation BoF • Time Sync & Correlation White Paper in discussion • Time Sync & Correlation WG Charter developed (CESG May 2010)

  15. CESG SPRING 2010: Items to be brought to attention of the CMC

  16. Sometimes organizations have these little internal conflicts … “Separation of church and state” “Separation of church and state” Differences between policy and practice Differences between policy and practice “Model clashes” terminology and other disconnects

  17. CCSDS Procedures update Out for CESG review, needs badly to be published Requires CMC approval SANA Considerations The SANA YB requests that the CCSDS Procedures & Publications manuals be updated to reference a mandatory “SANA Considerations” section SANA Operator has been asked to initiate some new registries, including a CCSDS Glossary All new WG projects should analyze SANA issues as part of their process, and ensure that they address them, potentially with support of the SANA operator SM WG has identified a need to have agency reps as part of approving monitor data updates, needs to be service operators, light-weight, but adequately complete SEA IA and MOIMS IPR WGs Working groups have been operating increasingly well as a joint effort for a few years now SEA AD recommends that these two groups be re-organized into one, with a new charter that is focused on the Information Services Architecture and also incorporates the present registry-repository and information modeling and architecture tasks A presentation and a Concept Paper in draft form is available and the members of the two WGs appear ready to join forces Words of appreciation The SEA wishes to thank the workshop organizers for doing an excellent job of arranging the facility, managing meetings rooms, and providing great food and speakers • SPRING 2010: ITEMS BROUGHT TO CMC ATTENTION (1)

More Related