[cssm] Use of SICF in Service Management - again

[Colin.Haddow at esa.int]

Dear all,
                  I've been checking how the SICF is originated at ESOC 
and it appears that generally (but not always) the Service provider is 
proposing the SICF and the managed parameters set up. Not sure how other 
agencies handle this.

It does however leave me somewhat confused with how the SICF is supposed 
to fit in with the SMURF and SPDF, e.g.

Who submits the SICF?
Does a SICF needs to be referenced in a Service Package Request?
Does the SICF get referenced at the Service Package level, or do we need 
to specify the SI at service level (possibly in both SMURF and SPDF)?
How do we handle the different approaches to the SICF, i.e. some agencies 
have multiple SIs per SICF, others have a one to one mapping of SI to 
SICF?
Do we need to come up with a standard SICF format? (I hope the answer to 
this is no...)

Perhaps we need a splinter webex or 2 to try and thrash this out ?


Cheers for now,

Colin

---------------------------------------------------------------------------------------------------------
Dr. Colin R. Haddow,
HSO-GI, European Space Agency,
European Space Operations Centre,
Robert-Bosch-Str 5,
64293 Darmstadt,
Germany.

Phone; +49 6151 90 2896
Fax;      +49 6151 90 3010
E-Mail;  colin.haddow at esa.int
---------------------------------------------------------------------------------------------------------

This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20210225/9a80e6f1/attachment.htm>