ESTEC, Noordwijk, Netherlands 27 Oct 2009 SERVICE ARCHITECTURE FOR SPACE -- BOF 1.

Slides:



Advertisements
Similar presentations
CEOS WGISS & Subgroup Meeting, Budapest, May CCSDS Liaison Consultative Committee on Space Data Systems Wyn Cudlip BNSC/QinetiQ
Advertisements

Wyn Cudlip BNSC/QinetiQ Presentation to WGISS24 DLR, October 2007 CCSDS Liaison Consultative Committee on Space Data Systems.
1 Cross Support Architecture (CSAWG) Overview, Status, Goals Takahiro Yamada JAXA.
1 24 April 2009 SMWG SMWG Closing Report Colorado Springs, Colorado, USA 24 April 2009.
Folie 1 Service Oriented Architecture - Prototyping study - DLR/GSOC Author: S.Gully.
CSA WG Meeting 24 April 2009 Page 1 Colorado Springs CSA WG Service Agreement Status Prepared by Hugh Kelliher Space ConneXions Limited
CCSDS Message Bus Comparison Shames, Barkley, Burleigh, Cooper, Haddow 28 Oct 2010.
0 CCSDS Systems Engineering Area: Security Working Group Howard Weiss NASA/JPL/SPARTA (a Parsons Company) October.
Sep 2003 CCSDS Navigation WG Progress Report MOIMS Meeting Oct 2003 CSC, Maryland, USA Felipe Flores-Amaya CCSDS Navigation WG.
CSSM Meeting Summary Fall 2012 Meetings 15 – 18 October E. Barkley Chair (NASA/JPL) C. Haddow Co-Chair (ESA/ESOC) Cleveland, Ohio, USA.
1 CCSDS Information Architecture Working Group SEA Plenary Daniel J. Crichton, Chair NASA/JPL 12 September 2005.
1 CROSS SUPPORT SERVICE ARCHITECTURE Takahiro Yamada (JAXA/ISAS) CCSDS Meeting, Heppenheim, Germany 2 October 2007.
CSSM Meeting Summary Spring 2013 Meetings 15 – 18 April E. Barkley Chair (NASA/JPL) C. Haddow Co-Chair (ESA/ESOC) Bordeaux, France.
Institutsbezeichnung: Quellenangabe 1 CCSDS MANAGEMENT COUNCIL Canadian Space Agency St-Hubert, Quebec, Canada May 2004 DLR Report Martin Pilgram,
CCSDS Spacecraft Monitor & Control Working Group (SM&C WG) SpaceOps 2004.
Delta-DOR SIG: Report of the Fall 2007 Meeting Heppenheim, Germany October 5th, 2007 Roberto Maddè ESA/ESOC
System Engineering Area SANA BoF Kick-Off 12 May 2004 Peter Shames NASA/JPL.
1 Space Communications Cross Support Architecture WG: Charter and Work Plan October 2010 London, UK Takahiro Yamada, JAXA/ISAS.
1 Space Communications Cross Support Architecture WG: Charter and Work Plan October, 2009 ESTEC, The Netherlands Takahiro Yamada, JAXA/ISAS.
0 CCSDS Systems Engineering Area: Security Working Group Howard Weiss NASA/JPL/SPARTA (a Parsons Company) April.
PS 1 12 June 2006 SEA Opening Plenary Rome, Italy, 12 June 2006.
Information Architecture WG: Report of the Winter 2007 Meeting January 20, 2007 Dan Crichton, Chair NASA/JPL.
1 Cross Support Architecture (CSAWG) Overview, Status, Goals Takahiro Yamada JAXA.
Ajh January 2007 CCSDS “Books” Adrian J. Hooke CMC Meeting, Colorado Springs 26 January 2007.
0 CCSDS Systems Engineering Area: Security Working Group Howard Weiss NASA/JPL/PARSONS November 2014 BSI, London.
Information Architecture WG: Report of the Fall 2010 Meeting October 29, 2010 Dan Crichton, Chair Steve Hughes (presenting) NASA/JPL.
Cesg-1 CSS Area Report -- Super BOF Background From A. Hooke to CESG: (CSS AD emphasis ) Date: Fri 02 Oct 2009 To: CESG cc: CMC Subject: Proposed.
November MOIMS AREA PLENARY NAVIGATION WG REPORT November 2004 CONSULTATIVE COMMITTEE FOR SPACE DATA SYSTEMS.
1 CCSDS Information Architecture Working Group Daniel J. Crichton, Chair NASA/JPL 14 September 2005.
13-17 October 2008 Berlin, Germany ty - 1 Cross Support Architecture WG Closing Plenary Report Spring 2009 Meeting Takahiro Yamada (JAXA/ISAS) 25 April.
Nov11-cesg-1 SOIS Area Report Wireless WG Primary Objectives for the fall meeting Establish lessons learned from the Asset Management (AM) Magenta Book.
May 2004 CCSDS Navigation WG Activity Report CCSDS Spring Series May 2004 CSA, Montreal, Canada Felipe Flores-Amaya CCSDS Navigation WG.
DTS & CSTS REPORT 15 April 2005 Athens, Greece CSTS - 1 DTS & CSTS WG STATUS REPORT, End of Spring 2005 Meeting Yves Doat Chairman 15 April 2005.
Wyn Cudlip BNSC/QinetiQ Presentation to WGISS25 China, February 2008 CCSDS Liaison Consultative Committee on Space Data Systems.
Information Architecture WG: Report of the Spring 2004 Meeting May 13, 2004 Dan Crichton, NASA/JPL.
1 Space Communications Cross Support Architecture WG: Charter and Work Plan October 2012 Clevaland, Ohio, U.S.A. Takahiro Yamada, JAXA/ISAS.
1 Cross Support Architecture (CSAWG) Overview, Status, Goals Takahiro Yamada JAXA.
Ty - 1 Space Communication Cross Support Architecture WG Closing Plenary Report Spring 2011 Meeting Takahiro Yamada (JAXA/ISAS) 20 May May 2011.
Information Architecture WG: Report of the Fall 2005 Meeting September 16, 2005 Dan Crichton, Chair NASA/JPL.
SEA-1 20 Nov 2014 CCSDS System Engineering Area (SEA): System Architecture WG (SAWG) Restart Peter Shames, SEA AD 20 Nov 2014.
CSS-SM Refactoring Proposal Scope –Allow inclusion of services or modifications to existing ones without having to reedit the entire CSS-SM book. Objectives.
Adrian Hooke, CESG Chair ESTEC, Noordwijk, Netherlands 27 Oct 2009 SERVICE ARCHITECTURE FOR SPACE: why this BOF? 1.
PS -0 System Architecture Working Group RASDS Status 14 June 2006 Peter Shames NASA / JPL
CCSDS Reference Architecture Notes from SAWG discussion & from SEA Report to CESG/CMC 12 & 17 Nov 2014.
Djc -1 Daniel J. Crichton NASA/JPL 9 May 2006 CCSDS Information Architecture Working Group.
1 09 October SOIS Report to CESG/CMC 9 October 2007 Patrick Plancke, C. Taylor.
Information Architecture BOF: Report of the Fall 2003 Meeting October 28, 2003 Dan Crichton, NASA/JPL.
Delta-DOR SIG Minutes of the meeting Heppenheim, Germany October 2nd, 2007 Roberto Maddè ESA/ESOC
Information Architecture WG: Report of the Spring 2005 Meeting April 14, 2005 Steve Hughes, NASA/JPL.
Moving towards an IRS WG Charter Ross Callon IETF 85, Atlanta.
1 Systems Architecture WG: Charter and Work Plan October 23, 2003 Takahiro Yamada, JAXA/ISAS.
1 Steve Hughes Daniel J. Crichton NASA/JPL January 16, 2007 CCSDS Information Architecture Working.
CEOS WGISS Meeting, Hanoi May CCSDS Liaison Consultative Committee on Space Data Systems Wyn Cudlip BNSC/QinetiQ Presentation.
CSS AREA REPORT 24 January 2007 Colorado Springs, USA CSS AREA: CSEG/CMC Report, Winter 2007 Meeting Erik Barkley (NASA/JPL) Area Director Yves Doat (ESA)
Security WG: Report of the Spring 2014 Meeting NH Hotel Leeuwenhorst Noordwijkerhout, The Netherlands 3 April 2014 Howard Weiss NASA/JPL/PARSONS
1 Space Communications Cross Support Architecture WG: Charter and Work Plan April, 2009 Colorado Springs, CO, USA Takahiro Yamada, JAXA/ISAS.
CSA WG Meeting 17 May 2011 Page 1 Berlin, Germany CSA WG Service Agreement Status Prepared by Hugh Kelliher Space ConneXions Limited
Systems Architecture WG: Report of the Spring 2005 Meeting April 14, 2005 Takahiro Yamada, JAXA/ISAS.
DSN CCSDS SLE SM Prototype Plan Erik Barkley December 2006.
1 20 April 2009 Cross Support Service Area Cross Support Service Area Opening Plenary Colorado Springs, Colorado, USA 20 April 2009 Erik Barkley (AD) /
1 CCSDS Architectures: Issues and Proposals October 2010 London, UK Takahiro Yamada, JAXA/ISAS.
Security WG: Report of the Fall 2003 Meeting October 28, 2003 Howard Weiss, NASA/JPL/SPARTA.
Information Architecture WG: Report of the Fall 2004 Meeting November 16th, 2004 Dan Crichton, NASA/JPL.
1 Space Communications Cross Support Architecture WG: Charter and Work Plan May 2010 Portsmouth, Virginia, USA Takahiro Yamada, JAXA/ISAS.
National Aeronautics and Space Administration 1 CCSDS Information Architecture Working Group Daniel J. Crichton NASA/JPL 24 March 2005.
0 CCSDS Systems Engineering Area: Security Working Group Howard Weiss NASA/JPL/Cobham (Parsons) October 2011.
Systems Architecture WG: Charter and Work Plan
CCSDS Reference Architecture
CCSDS System Engineering
Application of ODP for Space Development
Presentation transcript:

ESTEC, Noordwijk, Netherlands 27 Oct 2009 SERVICE ARCHITECTURE FOR SPACE -- BOF 1

INTRODUCTION Erik Barkley (5 Min) 2

PROPOSED BOF Agenda Draft Agenda, Service Architecture for Space BOF, 27 October 2009 IDTopicLeadTime (min)Planning Comments 1IntroductionE. Barkley5Review BOF Agenda. 2Why this BOF?A. Hooke15 Motiviations for this BOF; programmatic considerations; What is the problem that we are to solve with this BOF/new WG? 3 MOIMS Area Inputs N. Peccia20 Scope of relevant WGs; Brief description of recommenations currently in progress; status of recommendations; What should new WG achieve from Area perspective? 4SE Area InputsP. Shames20 Scope of relevant WGs; Brief description of recommenations currently in progress; status of recommendations; What should new WG achieve from Area perspective? 5CSS Area InputsE. Barkley20 Scope of relevant WGs; Brief description of recommenations currently in progress; status of recommendations; What should new WG achieve from Area perspective? 6Overlap AnalysisP. Shames25CCSDS Reccomendations overlap analysis. Break 10(Because we will need it) 7 Potential WG Scope Discussion E. Barkley40 Based on WG surveys, analyses, etc what fits within the proposed new WG? What are its goals? E.g., A CCSDS service "map" ? Clear distinction between service layers, protocol layers? Develop precise lexicon/terminology definitions? Information Model ? Definition of acrhitecture framework & components? 8 Domain Knowledge Dicussion TBD20 Identification of key domain knowledge needed in composition of new WG (for input to CMC) 9 WG Formation Discussion E. Barkley40 From a technical perspective, based on proposed SOA scope, are some WGs dissolved? Which WG's have charters modified? What has to occur to close WGs that are folded into the new WG? 10ConclusionE. Barkley20 Considerations of next steps, e.g., drafting SOA for Space Charter, review of action items generated, etc. (Reserve Time) 5 3

Agenda Adjustments (If Any) 4

Suggested Ground Rules For input presentations, hold questions until end of presentation Presenters – allow 3 – 5 minutes for end of presentation Attempt to quickly determine need for an action item vs lengthy discussion (time budget) For discussions, generally suggest that action items be considered if no apparent resolution in a timely manner I will attempt to keep an eye on the clock, but I am only the junior AD, so I need your help 5

WHY THIS BOF? Adrian Hooke (15 Min) 6

MOIMS AREA INPUTS Nestor Peccia (20 Min) 7

SE AREA INPUTS Peter Shames (20 Min) 8

CSS AREA INPUTS Erik Barkley (20 Min) 9

CSS AD -- Potential First Goal/Step The Spacecraft Onboard Interfaces Services Area shall define the onboard data handling interface between a payload or subsystem and its carrier spacecraft. The Space Link Services Area shall define the data handling interfaces between two free-flying spacecraft and between a free- flying spacecraft and a ground support network. The Cross Support Services Area shall define the data handling interface between a ground support network and a ground user facility. The Mission Operations and Information Management Services Area shall define the mission control application protocols that traverse the logical (end-to-end) interface between a user facility and a payload or subsystem in space, and between two ground user facilities. The Space Internetworking Services Area supports the Mission Operations and Information Management Services Area and shall define the end-to-end data communications protocols that traverse interface between a user facility and a payload or subsystem in space. The Systems Engineering Area supports each of the other five Areas and shall define the common services (e.g., data security) that pervade the whole space system. (Extracted from Draft Strategic Operating Plan, CCSDS A01.1-Y-1.1, September 2006) + = ? (Extracted from Reference Model for Service Oriented Architecture 1.0, OASIS Standard, October 2006) Some common understanding between CCSDS Areas re some accepted general industry-wide understanding of what a “service” definition contains or “talks” about ? 10

CSS WG Survey CSTS Scope SM Scope CSA Scope Cross Support Architecture Contents: RASDS Views, Service Attributes Status: WB Prototypes: N/A Service Catalog Contents: Service Catalog Templates, XML Schema Status: WB Prototypes: Expression of Representative Agency Catalog(s) Service Agreement Contents: “Hi-Level” Service Agreement Templates, XML Schema Prototypes: Expression of Representative Mission Service Agreement(s) Contents: Document Exchange, “Lo-Level” Service Agreements, Service Configuration, Trajectory Predictions, Service Packages Status: BB Prototypes: ESA/JAXA/NASA Service Management Contents: Overview of SM; Use Cases of SM Status: Advanced WB Concept Contents: Overview of framework, operations, procedures Status: WB Prototypes: N/A Framework Contents: Core Operations and Procedures Status: ~R-1 Prototypes: NASA/ESA Guidelines Contents: Construction of new services re Framework Status: ~R-1 Prototypes: N/A Monitored Data Contents: CSTS Monitor Data Delivery Status: ~R-1 Prototypes: TBS Tracking Data Contents: Streaming TDMs Status: ~R-1 Prototypes: TBS SLE Reference Model SLE Recommendations 11

(Preliminary) CSS Area Goal for new WG Clear understanding of service (inter-area) service inter-relationships a CCSDS-wide model or service “map” [CCSDS Reference Model] Clear understanding of accepted CCSDS-wide “enterprise model” What are the parties/actors involved ? [CCSDS Reference Model] What do CCSDS recommended service standards contain? PDUs, State Tables, Behavioral Requirements, Information Exchange Protocol(s) ? [Guidelines, Normative Templates?] Common terminology/lexicon across CCSDS Where is the CCSDS acronym list? Where is the overall CCSDS information model ? [Information Model] When services are defined, what is expected in terms of cross support definitions? E.g, definition of PDUs What are the parameters of the service that need management, and how much? [Guidelines, Normative Templates?] What is the relationship of this architecture to the CSA architecture Is one more oriented to the overall picture (CSA)? Is one more oriented to the IT (Information Technology) aspects of cross support (Service Architecture for Space) [CCSDS Reference Model] 12

Information Model Example 13

RECOMMENDATIONS OVERLAP ANALYSIS Peter Shames (25 Min) 14

TAKE A BREAK (10 MIN) 15

POTENTIAL SCOPE FOR NEW WG (DISCUSSION) Erik Barkley (40 Min) 16

DOMAIN KNOWLEDGE (DISCUSSION) Erik Barkley (20 Min) 17

WG FORMATION (DISCUSSION) Erik Barkley (40 Min) 18

CONCLUSION (DISCUSSION) Erik Barkley (20 Min) 19