<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:804009745;
mso-list-type:hybrid;
mso-list-template-ids:-1477287066 702682286 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Dear All,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have placed an updated version of the MPS Information Model (Draft G) on the Google Drive. The Enterprise Architect model can be found at:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="https://drive.google.com/open?id=1D4YhgM-HJagGt5eYCdHhsV09_5Lx8rl5">https://drive.google.com/open?id=1D4YhgM-HJagGt5eYCdHhsV09_5Lx8rl5</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>and the RTF diagram report at:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="https://drive.google.com/open?id=1D4YhgM-HJagGt5eYCdHhsV09_5Lx8rl5">https://drive.google.com/open?id=1D4YhgM-HJagGt5eYCdHhsV09_5Lx8rl5</a> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The principle changes are:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Representation of MPS COM Objects changed to use the UML Template class approach discussed during the last telecon and subsequently via email with various members of the WG. The COM Object Body is now an attribute of the COM Object itself, and parameterised as a UML Template Parameter. This is then bound to various UML Classes representing the Object Body corresponding to each of the concrete MPS COM Objects. Each MPS COM Object now has a derived Class representing it (as before) that shows the relationships to other MPS COM Objects and Data Items, while the structure of its Object Body is represented as a separate “Details” class, that is bound to the COM Object template class as the Object Body. To keep the representation as simple and compact as possible, the Object Body is shown inside the COM Object.<br><br>Each MPS Data Item (Planning Requests, Plans, Planning Activities, Planning Events, Planning Resources and Functions) may have up to four distinct COM Objects representing Identity, Definition, Instance and Update according to the identified COM Object Patterns. The body of the Identity object is typically a single attribute corresponding to a MAL Identifier, so there is no specific Object Body “Details” structure.<br><br>Each concrete MPS COM Object will require specification of the Area, Service and Number elements of the COM Object Type. I have not yet added this to the model, but it can be done as constraints on either the COM Object class, or the binding relationship to the COM Object template class. I would suggest that this is better represented in the Blue Book Information Model section as a table listing all the COM Object Types. We need to agree a numbering scheme within the WG first.<br><br>There is a complication that two MPS Data Items (Events and Resources) have multiple sub-types of Definition, Instance and Update. There is more than one way to represent this and in the current model I have used different methods for Event and Resources to illustrate possible approaches. For Events, as there are only two subtypes representing Event Groups and Single Events, I have created two separate “Details” classes that each contain the common attributes, which avoids the need for a second level of “Details” classes for the sub-types. These are then directly bound to the COM Object template class. For Resources (where there are many more subtypes), I have used a second level of UML Templating to include the sub-type specific attributes. I assume that in practice there will need to be distinct COM Object Numbers for each concrete sub-type.<o:p></o:p></p><p class=MsoListParagraph><o:p> </o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Representation of Plans and PatchPlans has been merged, as discussed in the last telecon. All Plans (Plans or PatchPlans) are now represented as PlanVersions, which has a flag to indicate if it is a PatchPlan and relationships to both Predecessor (Source) and Target Plans, with associated constraints on how these can be used in conjunction.<o:p></o:p></p><p class=MsoListParagraph><o:p> </o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>I have included the proposed Pointing Constraint types from Peter’s note. However, please note that this was based on the note he released in February and not the new version released today. I have noted a number of discussion points within the model on this topic.<o:p></o:p></p><p class=MsoListParagraph><o:p> </o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>I have included a new summary diagram for Planning Configuration Data<o:p></o:p></p><p class=MsoListParagraph><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best regards,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Roger<o:p></o:p></p></div></body></html>