[Moims-sc] CCSDS MO Green Book update

Thu Apr 20 15:48:05 UTC 2017

Hi Sam,

I believe that we should define a concrete set of terminology and use it 
consistently throughout the documents. 
Nowadays we just use "MO services" for everything which makes things 
harder to read/explain.

My initial suggestion is to coin the following terms:      (feel free to 
make changes or include other suggestions)

MO Architecture: A stratified service-oriented architecture that abstracts 
the service layer from the transport layer.
MO Technology: The technology for mission operations of space assets 
developed on top of the MO Architecture.
MO service: A service defined using the MO Technology.
        MO standard service: An MO service standardized by the CCSDS 
Agency.
        MO bespoke service: An MO service defined for a dedicated use 
case, typically a mission-specific service.

MO Application: An application that uses the MO Technology.
MO Core: The combination of the elements: MAL, COM services, and Common 
services. These elements are expected to be present in a typical 
deployment of an MO Application.
MO System: A system composed of MO Applications.

(Others that I can think of: MO Provider, MO binding, MO standard binding, 
MO bespoke binding, MO encoding, MO standard encoding, MO bespoke 
encoding)
Adding one page at the beginning of the document with consistent 
terminology will make the reading/writing much simpler.

Best regards,
César Coelho

From:   Sam Cooper <sam at brightascension.com>
To:     MOIMS-SC at mailman.ccsds.org
Date:   06/04/2017 10:19
Subject:        [Moims-sc] CCSDS MO Green Book update
Sent by:        "MOIMS-SC" <moims-sc-bounces at mailman.ccsds.org>

Dear All,

As discussed during the last teleconference, please find below the outline 
we are proposing for the Green Book update for your comments.

Green Book Skeleton
Introduction (2-3 pages)
Aim of this Green Book
Structure of this Green Book
How to read and use this Green Book
Mission Operations Motivation and Rationale (6-8 pages)
Background and context
Scope under consideration
Challenges facing operations and space systems development
Stakeholder identification
User needs
Role of software, and mission operations services, in addressing the user 
needs
Requirements on MO
Mission Operations Design (4-6 pages)
Terminology
Design principles (e.g. SOA, messaging, at a high-level)
The MO service model (non-technical description)
Providing and consuming services (non-technical description)
Applications and services
Standard services
MO in practice - some example case studies
Mission Operations Technology (4-6 pages)
The MO service model in more detail
Layering in MO
Common services
The role of the common object model
The Message Abstraction Layer
Developing MO Applications (4-6 pages)
Typical MO applications
Relationship between applications and services
Standard vs application-specific services
MO application development tools
...
Integrating MO Systems (4-6 pages)
Essential services
Detailed description of common services and COM services
The role of the MAL and communications protocols
Reference implementations
Implementing an MO system using the reference tools
...
Managing and Administering MO Systems (4-6 pages)
The role of the common services
Audit trail
Archiving
Security
...
MO Communications (4-6 pages)
Detailed look at the architecture and the way communications works
Overview of different communications bindings
...
Overview of the Standards (2-3 pages)
Top level view of the standards/books
Mapping of the standards onto topics and stakeholders
Mapping of the standards/topics/stakeholders onto the following chapters

Stakeholders 
Preliminary list of stakeholders:
Managers 
Mission level
Infrastructure
Programme managers
Operators (Ops)
System Integrators (EGSE and AIT)
Software Developers 
Infrastructure
Applications
Edit this section

Stakeholder to Section Mapping
For Managers:
Read first three sections
Read Managing and Administering MO Systems
If further detail required, read Mission Operations Technology
For Operators:
Read first three sections
Read Mission Operations Technology
If further detail required on management, read Managing and Administering 
MO Systems
If further detail required on development, read Developing MO Applications
For System Integrators:
Read first three sections
Read Mission Operations Technology
Read Integrating MO Systems
If further detail required on management, read Managing and Administering 
MO Systems
If further detail required on development, read Developing MO Applications
For Application Software Developers:
Read first three sections
Read Mission Operations Technology
Read Developing MO Applications
If further detail required on integration, read Integrating MO Systems
If further detail required on management, read Managing and Administering 
MO Systems
For Infrastructure Software Developers
Read first three sections
Read Mission Operations Technology
Read Integrating MO Systems
Read MO Communications
If further detail required on management, read Managing and Administering 
MO Systems
If further detail required on development, read Developing MO Applications

The idea of the book is that it has some general overview sections at the 
beginning and then, depending on your interest, you have a set of sections 
that are applicable to you that you should read. The hope is that these 
later sections can be more focussed and relevant that trying to cover 
everything for everybody which I think the previous document suffered 
from. Also, we are trying to emphasise the goals and uses of MO rather 
than the technology, so putting the horse back in front of the cart.....

So, please, any comments you have on anything, but ideally other 
stakeholders and the sections they would want. If you could send those to 
me by Monday the 24th of April that would be brilliant.

We hope to release a first draft of the document in time for us to discuss 
in San Antonio. It will not be complete and will most likely only cover a 
few sections but should give us an idea of direction and style.

Thanks,
Sam.

This message and any attachments are intended for the use of the addressee 
or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in 
whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete 
it from your system.
Emails can be altered and their integrity cannot be guaranteed by the 
sender.

Please consider the environment before printing this email.

_______________________________________________
MOIMS-SC mailing list
MOIMS-SC at mailman.ccsds.org
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-sc

This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-sc/attachments/20170420/c342fdfd/attachment.html>