[Css-csts] WebEx meeting changed: CSTS Telecon #2

[YOSHIKAZU MIYANO]

Holger-san,

Thank you for having a slot. 30 minute(10:45 - 11:15) is enough including
discussion, because developing gateway will take several years and 
discussion
will not be concluded just in one workshop.
  Before meeting in Berlin, I will send several page slides including
following discussion points to mailing list.
a) Documentation Priorities
Which documents is highly prioritized after current drafts (Concept 
Book, Guideline,
TD-CSTS, FF-CSTS) are documented ?  When will API books be documented if 
they are
prioritized?
b) MBSE/MBD
If developing gateway is approved within JAXA, I will manage the 
development by Model Based
Development in order for agencies to check the projects of UML/SysML 
tools.  Wiithout
disagreement,  JAXA will design the gateway using Enterprise Architect 
by SparxSystems, which is mostly used in Japan Manufacturing Industry

Regards,

Miyano




On 2018/09/05 14:55, Holger.Dreihahn at esa.int wrote:
> Hi Miyano-san,
> Nice to hear from you. Of course you can have a slot on Tuesday morning
> for a presentation, I suggest to use the session after the coffee break in
> the morning to lunch (10:45 - 12:30). That leaves some room for a
> discussion afterwards. Looking at your summary, there might be indeed some
> things to discuss.
>
> Regards,
> Holger
>
> Holger Dreihahn
> European Spacecraft Operations Centre | European Space Agency | S-431
> +49 6151 90 2233 | http://www.esa.int/esoc
>
>
>
> From:   YOSHIKAZU MIYANO <miyano.yoshikazu at jaxa.jp>
> To:     css-csts at mailman.ccsds.org
> Date:   05/09/2018 06:10
> Subject:        Re: [Css-csts] WebEx meeting changed: CSTS Telecon #2
> Sent by:        "CSS-CSTS" <css-csts-bounces at mailman.ccsds.org>
>
>
>
> Holger-san,
>
> I will join tomorrow's telecon as soon as another telecon will be
> finished.
>
> Regarding CSTS meeting in Berlin, it possible for me to have
> 10 minute presentation related to MD-CSTS implementation in the morning of
> Tuesday?
> I wish to have presentation based on following summary, but I hesitate
> to do because MD-CSTS and SFW BB were published last year.
>
> Summary:
> JAXA does not decide whether MD-CSTS should be implemented especially from
> Service
> Provider Side. However, Service User Side in JAXA currently studies how to
> implement
>   MD-CSTS gateway to have interoperability with other agencies.
> Apart from interoperability with legacy systems within JAXA, I recognize
> the following
> issues to decide.
> 1) FR SANA Registry
> The following FR, example described in MD-CSTS BB, should be approved
> from "provisional".
> – Antenna;
> – Forward Space Link Carrier Transmission;
> – Forward TC PLOP, Sync, and Channel Encoding;
> – Forward CLTU Transfer Service Provider;
> – Return Space Link Carrier Reception;
> – Return TM Synchronization and Decoding;
> – Return All Frames Transfer Service Provider;
> – Monitored Data CSTS Provider; and
> – Monitored Data Collection.
> 2)Application Program Interface MB books
> Equivalent books of SLE API MB should be documented in order to be
> interoperable
> between agencies.  I wish to confirm whether tech notes such as FR
> reference model exists
> and whether documents of prototyping in MD-CSTS BB can be applied to parts
> of API books.
>
> Regards,
>
> Miyano
>
>
>
>