<font size=2 face="sans-serif">Hi Sam,</font>
<br>
<br><font size=2 face="sans-serif">In the discussions with MO new comers
and even with some of the people who have been around for a long time,
the separation between "MO Framework" and concrete "MO Services"
has always been a source of confusion.</font>
<br><font size=2 face="sans-serif">When people talk about MO, they very
often mix the MAL design time aspects, its run time aspects, the role of
COM and COM services and the concrete MO Services on top of the MO Framework
as well as their relationship to a particular encoding and binding.</font>
<br>
<br><font size=2 face="sans-serif">The best example is the discussion we
had recently where after performing a detailed analysis for a possible
implementation, the involved persons had missed after reading the standards
(apparently they had missed the M&C book) the point that "MO"
includes also concrete services and is not just an abstract framework!</font>
<br>
<br><font size=2 face="sans-serif">I see that the proposed ToC tackles
this in a number of places: "MO Operations Technology" chapter
as well as in "Mission Operations Design", "integrating
MO Systems" and probably to some extent in "Developing
MO Applications". </font>
<br><font size=2 face="sans-serif">This is good on one side as it is looking
into different aspects and can provide input for each aspect separately,
at the other side the basic questions and the big picture could easily
get lost, if the information is scattered in different sections.</font>
<br>
<br><font size=2 face="sans-serif">It may be good to have early in the
document a short chapter which shall not be technical at all and written
in a way that can be understood without getting too much in the details
explaining these concepts. Something like</font>
<br>
<br><font size=4 face="sans-serif">What is MO?</font>
<ul>
<li><font size=3 face="sans-serif"><b>The MO Framework</b></font></ul>
<ul>
<li><font size=2 face="sans-serif"><b>What is a Generic Service and Data
Specification Language good for? </b>(</font><font size=2 color=blue face="sans-serif">Design
Time role of MAL and COM</font><font size=2 face="sans-serif">)</font>
<ul>
<li><font size=2 face="sans-serif">Model Driven Architecture: CIM-PIM-PSM</font>
<li><font size=2 face="sans-serif">Implementation and communication independence</font>
<li><font size=2 face="sans-serif">Machine Readable specification of interfaces
</font>
<li><font size=2 face="sans-serif">Auto Generation of Artefacts</font>
<li><font size=2 face="sans-serif">Common Service and Data Meta-Model (common
set of meta-data)</font>
<li><font size=2 face="sans-serif">Service and Data Taxonomy </font>
<li><font size=2 face="sans-serif">SOA Governance (Service Template, common
design patterns and best practices for capability specification, ...)</font>
<li><font size=2 face="sans-serif">....</font></ul>
<li><font size=2 face="sans-serif"><b>Why do we need a Common Object Model
and what is it good for? (</b></font><font size=2 color=blue face="sans-serif">Common
Object Model Part of the COM</font><font size=2 face="sans-serif"><b>)</b></font>
<ul>
<li><font size=2 face="sans-serif">Interrelating Objects from different
Mission Operation functional contexts (e.g. Alert --> Check --> TM
Parameter --> Action --> Plan --> Planning Request, ...)</font>
<li><font size=2 face="sans-serif">Historical View of Mission Operation
Entities</font>
<li><font size=2 face="sans-serif">Unified handling of the common aspects
of objects at service level</font></ul>
<li><font size=2 face="sans-serif"><b>Removing Abstraction and getting
very concrete (</b></font><font size=2 color=blue face="sans-serif">Role
Bindings</font><font size=2 face="sans-serif"><b>)</b></font>
<ul>
<li><font size=2 face="sans-serif">Selecting the Implementation Technology:
(Explain Language binding and what is it good for)</font>
<li><font size=2 face="sans-serif">Selecting Communication Technology:
(Explain encoding and communication binding, at this level I think it is
good enough to handle encoding/transport as one)</font>
<li><font size=2 face="sans-serif">Mission Architecture removes generality
by fixing the choices: Deployment Architecture, Selection of services and
required capabilities, optimisation, ...</font></ul>
<li><font size=2 face="sans-serif"><b>What does MO Framework provide as
added value in terms of functionality </b>(why shall I use MO as a framework)</font>
<ul>
<li><font size=2 face="sans-serif">Non-Functional aspects of Mission Operations
(</font><font size=2 color=blue face="sans-serif">Run-time aspects of MAL</font><font size=2 face="sans-serif">)</font>
<ul>
<li><font size=2 face="sans-serif"><u>Addressing and Routing </u>of in
complex operation deployment architectures (where multiple operations entities,
ground stations, relay satellites, rovers, etc. are involved)</font>
<li><font size=2 face="sans-serif"><u>Reliable interaction</u> provided
at higher level than communication, e.g. when using a non-reliable comms
(reliable messaging provided at MAL level, ensuring sequence of interaction
messages based on selected pattern)</font>
<li><font size=2 face="sans-serif"><u>Incorporated Security at application
layer</u> (explain how MO Framework architecture allows pluging in of security
provider elements that would allow authorisation at operation level or
even content based, for instance depending on the value of a parameter
of an action) explain the difference to communication layer security </font>
<li><font size=2 face="sans-serif"><u>Ensuring Operations Consistency at
Application Layer</u>: Explain Transaction Management possibilities </font>
<li><font size=2 face="sans-serif"><u>Tractability and Auditing: </u>Explain
how the framework provisions means for tractability of every invocation
(Activity Tracking Service, ...)</font>
<li><font size=2 face="sans-serif"><u>Service Level Agreements and Quality
of Service</u></font></ul>
<li><font size=2 face="sans-serif">Interoperability: Bridging the disparity
in implementation (comms and implementation technology)</font>
<li><font size=2 face="sans-serif">Reusable Common Functionalities provided
by the framework (</font><font size=2 color=blue face="sans-serif">COM
Services and COMMON Services</font><font size=2 face="sans-serif"> + Broker
which I believe should be a Service similar to other COM Services)</font>
<ul>
<li><font size=2 face="sans-serif">COM and COMMON Services (utilities)</font>
<li><font size=2 face="sans-serif">Multi-Casting of information (I think
we should seperate the Pub-Sub pattern from the generic broker multi-casting
functionality/service)</font>
<li></ul></ul>
<li></ul>
<li><font size=3 face="sans-serif"><b>The MO Services </b></font>
<ul>
<li><font size=2 face="sans-serif">Standardised Services</font>
<li><font size=2 face="sans-serif">Custom Services</font></ul>
<br><font size=2 face="sans-serif">The Blue text is for your information
only. I added it to illustrate how the basic concepts of MAL (Design Time
vs Run-time), COM (COM and COM Services), Technology Bindings and COMMON
Services are captured in a non-technical way. The above structure could
translate in a more technical perspective to </font>
<br><font size=2 face="sans-serif">- MO </font>
<br><font size=2 face="sans-serif"> -MO Framework</font>
<br><font size=2 face="sans-serif"> - MAL</font>
<br><font size=2 face="sans-serif"> - Design
Time</font>
<br><font size=2 face="sans-serif"> - Runtime</font>
<br><font size=2 face="sans-serif"> -COM</font>
<br><font size=2 face="sans-serif"> - Common
Object Model</font>
<br><font size=2 face="sans-serif"> - COM Services</font>
<br><font size=2 face="sans-serif"> - COMMON Services</font>
<br><font size=2 face="sans-serif"> - Technology Binding</font>
<br><font size=2 face="sans-serif"> - Language Bindings</font>
<br><font size=2 face="sans-serif"> - Encoding and
Transport bindings</font>
<br><font size=2 face="sans-serif"> -MO Services</font>
<br><font size=2 face="sans-serif">- Standard Services: M&C, MP&S,
MDPDS, ...</font>
<br><font size=2 face="sans-serif">- Custom Services</font>
<br>
<br>
<br><font size=2 face="sans-serif">Another point, which I think could be
useful to cover in the green book is related to the "Operability Requirements"
and how they are full-filled by MO. At European level this is more formalised
by corresponding ECSS standard and how it could be mapped to PUS or MO.
But more generically I think the basic concepts of the Operability Requirements
could speak the language of the Mission Operators, hence useful for the
Green Book.</font>
<br>
<br><font size=2 face="sans-serif">Last but not least the link to the concepts
of the Space System Model could be incorporated in the Green Book. Also
here at European level we have the corresponding ECSS standard. The generic
concepts can be useful to explain the system context, especially for the
M&C services part.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Mehran</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Sam Cooper"
<sam@brightascension.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">MOIMS-SC@mailman.ccsds.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">06/04/2017 10:19</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Moims-sc] CCSDS
MO Green Book update</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"MOIMS-SC"
<moims-sc-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>Dear All,<br>
<br>
As discussed during the last teleconference, please find below the outline
we are proposing for the Green Book update for your comments.<br>
</font>
<br><font size=4 color=#4f4f4f face="Trebuchet MS"><b>Green Book Skeleton</b></font>
<p><font size=1 color=#2f2f2f face="Verdana">Introduction (2-3 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Aim of this Green Book</font>
<li><font size=1 color=#2f2f2f face="Verdana">Structure of this Green Book</font>
<li><font size=1 color=#2f2f2f face="Verdana">How to read and use this
Green Book</font></ul><font size=1 color=#2f2f2f face="Verdana">Mission
Operations Motivation and Rationale (6-8 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Background and context</font>
<li><font size=1 color=#2f2f2f face="Verdana">Scope under consideration</font>
<li><font size=1 color=#2f2f2f face="Verdana">Challenges facing operations
and space systems development</font>
<li><font size=1 color=#2f2f2f face="Verdana">Stakeholder identification</font>
<li><font size=1 color=#2f2f2f face="Verdana">User needs</font>
<li><font size=1 color=#2f2f2f face="Verdana">Role of software, and mission
operations services, in addressing the user needs</font>
<li><font size=1 color=#2f2f2f face="Verdana">Requirements on MO</font></ul><font size=1 color=#2f2f2f face="Verdana">Mission
Operations Design (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Terminology</font>
<li><font size=1 color=#2f2f2f face="Verdana">Design principles (e.g. SOA,
messaging, at a high-level)</font>
<li><font size=1 color=#2f2f2f face="Verdana">The MO service model (non-technical
description)</font>
<li><font size=1 color=#2f2f2f face="Verdana">Providing and consuming services
(non-technical description)</font>
<li><font size=1 color=#2f2f2f face="Verdana">Applications and services</font>
<li><font size=1 color=#2f2f2f face="Verdana">Standard services</font>
<li><font size=1 color=#2f2f2f face="Verdana">MO in practice - some example
case studies</font></ul><font size=1 color=#2f2f2f face="Verdana">Mission
Operations Technology (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">The MO service model in more
detail</font>
<li><font size=1 color=#2f2f2f face="Verdana">Layering in MO</font>
<li><font size=1 color=#2f2f2f face="Verdana">Common services</font>
<li><font size=1 color=#2f2f2f face="Verdana">The role of the common object
model</font>
<li><font size=1 color=#2f2f2f face="Verdana">The Message Abstraction Layer</font></ul><font size=1 color=#2f2f2f face="Verdana">Developing
MO Applications (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Typical MO applications</font>
<li><font size=1 color=#2f2f2f face="Verdana">Relationship between applications
and services</font>
<li><font size=1 color=#2f2f2f face="Verdana">Standard vs application-specific
services</font>
<li><font size=1 color=#2f2f2f face="Verdana">MO application development
tools</font>
<li><font size=1 color=#2f2f2f face="Verdana">...</font></ul><font size=1 color=#2f2f2f face="Verdana">Integrating
MO Systems (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Essential services</font>
<li><font size=1 color=#2f2f2f face="Verdana">Detailed description of common
services and COM services</font>
<li><font size=1 color=#2f2f2f face="Verdana">The role of the MAL and communications
protocols</font>
<li><font size=1 color=#2f2f2f face="Verdana">Reference implementations</font>
<li><font size=1 color=#2f2f2f face="Verdana">Implementing an MO system
using the reference tools</font>
<li><font size=1 color=#2f2f2f face="Verdana">...</font></ul><font size=1 color=#2f2f2f face="Verdana">Managing
and Administering MO Systems (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">The role of the common services</font>
<li><font size=1 color=#2f2f2f face="Verdana">Audit trail</font>
<li><font size=1 color=#2f2f2f face="Verdana">Archiving</font>
<li><font size=1 color=#2f2f2f face="Verdana">Security</font>
<li><font size=1 color=#2f2f2f face="Verdana">...</font></ul><font size=1 color=#2f2f2f face="Verdana">MO
Communications (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Detailed look at the architecture
and the way communications works</font>
<li><font size=1 color=#2f2f2f face="Verdana">Overview of different communications
bindings</font>
<li><font size=1 color=#2f2f2f face="Verdana">...</font></ul><font size=1 color=#2f2f2f face="Verdana">Overview
of the Standards (2-3 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Top level view of the standards/books</font>
<li><font size=1 color=#2f2f2f face="Verdana">Mapping of the standards
onto topics and stakeholders</font>
<li><font size=1 color=#2f2f2f face="Verdana">Mapping of the standards/topics/stakeholders
onto the following chapters</font></ul><font size=3><br>
Stakeholders </font>
<p><font size=1 color=#2f2f2f face="Verdana">Preliminary list of stakeholders:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Managers </font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Mission level</font>
<li><font size=1 color=#2f2f2f face="Verdana">Infrastructure</font>
<li><font size=1 color=#2f2f2f face="Verdana">Programme managers</font></ul>
<li><font size=1 color=#2f2f2f face="Verdana">Operators (Ops)</font>
<li><font size=1 color=#2f2f2f face="Verdana">System Integrators (EGSE
and AIT)</font>
<li><font size=1 color=#2f2f2f face="Verdana">Software Developers </font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Infrastructure</font>
<li><font size=1 color=#2f2f2f face="Verdana">Applications</font></ul></ul><a href="https://issues.brightascension.com/projects/ccsds-mo-support/wiki/Green_Book_Revisions/edit?section=3"><font size=1 color=#0060a0 face="Verdana">Edit
this section</font></a>
<br>
<br><font size=3 color=#4f4f4f face="Trebuchet MS"><b>Stakeholder to Section
Mapping</b></font>
<p><font size=1 color=#2f2f2f face="Verdana">For <b>Managers</b>:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Managing and Administering
MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required,
read Mission Operations Technology</font></ul><font size=1 color=#2f2f2f face="Verdana">For <b>Operators</b>:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Mission Operations Technology</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on management, read Managing and Administering MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on development, read Developing MO Applications</font></ul><font size=1 color=#2f2f2f face="Verdana">For <b>System
Integrators</b>:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Mission Operations Technology</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Integrating MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on management, read Managing and Administering MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on development, read Developing MO Applications</font></ul><font size=1 color=#2f2f2f face="Verdana">For <b>Application
Software Developers</b>:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Mission Operations Technology</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Developing MO Applications</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on integration, read Integrating MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on management, read Managing and Administering MO Systems</font></ul><font size=1 color=#2f2f2f face="Verdana">For <b>Infrastructure
Software Developers</b></font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Mission Operations Technology</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Integrating MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read MO Communications</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on management, read Managing and Administering MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on development, read Developing MO Applications</font></ul><font size=3><br>
<br>
<br>
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.....<br>
<br>
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.<br>
<br>
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.<br>
<br>
Thanks,<br>
Sam.<br>
<br>
<br>
<br>
<br>
<br>
</font><tt><font size=2>_______________________________________________<br>
MOIMS-SC mailing list<br>
MOIMS-SC@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-sc"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-sc</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><PRE>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.
</PRE>