1 / 9

SMWG Closing Plenary Report

SMWG Closing Plenary Report. Erik Barkley Chair, SMWG CSSA Workshop Rome, Italy 16 June 2006. The service management working group managed itself very well and processed 278 RIDs Primary goal/top priority for service management working group at Rome meetings achieved

udell
Download Presentation

SMWG Closing Plenary Report

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. SMWG Closing Plenary Report Erik Barkley Chair, SMWG CSSA Workshop Rome, Italy 16 June 2006

  2. The service management working group managed itself very well and processed 278 RIDs Primary goal/top priority for service management working group at Rome meetings achieved Represents complete set of RIDs submitted against the draft recommendation from the March 17 through June 09 agency reviews Dynamic = RIDS raised by WG during course of Rome meetings The Good News

  3. Summary of Meeting Results (1/4) • Event sequences will be remodeled • To be treated somewhat analogous to trajectory prediction handling • Removes a stumbling block for bilateral specification of event sequences • For Red-2 • Management of radiometric and ranging services to be added to the draft recommendation • For Red-2 • Charter issue • ProposedServicePackage operation to be considered for RED-2 • Service “package” from CM  UM • Useful to GSFC and NOAA operations • Concept “paper” to be developed and reviewed before further work • Contact planning services may be considered as a separate management services (ie not for RED-2) • Appears to be mostly applicable to deep space domain • JPL and ESA to work in tandem to develop coherent process model/concept • May need to be examined with respect to proposed service package operation • Charter issue

  4. Summary of Meeting Results (2/4) • Coordination with SLS area needed for proper definition of CCSDS space link parameters • Multiple RIDs requesting additional values for Spacelink section of configuration profiles that cannot be found in CCSDS 401.x • For RED-2 • Management of off-line transfer services to be considered • Concept “paper” to be developed and reviewed before further work • For RED-2 • Charter issue • Query service may be addressed as a separate management service (ie not for RED-2) • For example, given trajectory X, return a list of referencing service packages • Charter issue • Logging may be addressed as a separate management service (i.e. not for RED-2) • Would likely be considered with respect to service accountability • Charter issue • “Higher level” configuration profiles to be considered for RED-2 • Define the configuration profile to include both forward and return carriers • Will likely simplify service package definition with minimal complication to configuration profile • Concept “paper” to be developed and reviewed before further work

  5. Summary of Meeting Results (3/4) • EIRP “offset” to be added to configuration profile definitions for forward and return carriers • Used in conjunction with current EIRP parameter • Eliminates the need for CM to be aware of spacecraft attitude, geometry, and antenna patterns • Assumed that UM can adequately model above sufficiently to provide the offset with respect to the EIRP if/when the spacecraft is attempting to communicate off Earth point, etc. • For RED-2 • Notion of support “level” to be included in service package definition • Distinct from urgent parameter • Indicates the “criticality” of the service package for UM • For example, top-level support would be indicated for Cassini deploying the Huygens probe to Titan • For RED-2 • Trajectory “business processes” need better understanding • Discrepancies between multiple current agency processes for trajectory updates and draft recommendation

  6. Summary of Meeting Results (4/4) • Use case material from operations concept document to be released as its own document to help future reviewers of Red-2 • Several “sophisticated” use cases need to be supplied • For example, an event sequence may be best dealt with by invoking a CreateServicePackage operation and deferring the event sequence followed by supplying an event sequence via a ReplaceServicePackage operation once the exact times are known as the result of the CreateServicePackage operation • UML diagrams in the draft recommendation should be captured via a tool capable of producing XMI output • Service package state diagrams need further development • Decision as to incorporation into RED-2 is pending • Splitting up of the current draft recommendation is not warranted given current resources and scope of planned changes to RED-2

  7. Overall SMWG Status with respect to status of deliverables

  8. Near-Term Work Plan Approach • Available Resources (Projected work weeks for next 6 months) • JPL: 2.6 WG Chair, 6.5 Prototype upgrades • GST: 5.2 • Vega: 4.0 (Not firm yet) • CNES: 0/TBD • ESA: 0/TBD • BNSC: 1.0 • Effective manpower available for SMWG appears to be about 8 – 12 work weeks total • Update Red Book 1  Red Book 2 • Goal is to have the updated Red Book available for review at the January 2007 meetings • Intermediate meeting proposed for approximately third week of October to check status and various concepts (as noted in previous slides). • Concept document • Telecon proposed for second week of August for review of concept document

  9. Schedule Update Given Lack of Resources

More Related