<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:x="urn:schemas-microsoft-com:office:excel" 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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Century Gothic";
panose-1:2 11 5 2 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>This inadvertently missed the general AB List, and the Space Task Force.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Larry<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Hause, Matthew [mailto:mhause@ptc.com] <br><b>Sent:</b> Sunday, March 11, 2018 7:14 PM<br><b>Subject:</b> CubeSat Reference Model Review<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Colleagues,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In its present form this RFP should be rejected. My reasons for doing so are below. I have added this statement at the beginning so that it is not lost in the details of my response. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am concerned about this RFP as it appears to be a fait acompli. The timetable is extremely short and the inclusion of several present tense rather than future tense statements makes me tend to believe that this is an RFP for a product that already exists. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“The CRM logical components are intended to be reused as a starting point for a mission-specific CubeSat logical architecture, followed by the development of physical architecture during CubeSat development. On the other hand, should the mission-specific team decide to adopt a different logical architecture, the CRM is sufficiently flexible to accommodate this change.”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This is also borne out by the fact that this was originally an RFC rather than an RFP. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Six months to build a complex reference architecture for instruction, education, commercial use and as a standard is a ridiculously short amount of time. There can reasonably be no other submission than the one that has already been created, and this is not fair to other potential submitters. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am also concerned that no effort has been made to ensure that the architecture will be tool-independent. For example, this is not listed as one of the issues in the first paragraph of the RFP. Why not? How can any of this be possible unless there is a tool-independent implementation that different organizations can use? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Also, references are made to models with no indications as to the format or type of model. For example: “6.4.1.4.2 A model overview of the CRM package organization.”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If a vendor in conjunction with others wishes to create an example model, then they should do so. I have done so within my own company but make no representation that it should be a reference model for a standards organization. Trying to create a standard within the OMG of a tool vendor specific tool should never be allowed and I will be lobbying hard against it unless the tool independent nature of the effort is firmly established. So there are some changes that will need to be made to the RFP before I will be willing to vote for it. Specifically, there needs to be multiple tool implementations of the CRM for this to be acceptable. The OMG should NOT be favoring one tool vendor over another and acceptance of a CRM in ONLY one tool would be blatant favoritism. This should NOT be allowed. The RFP team needs to address how they plan to remedy this problem. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>My review is below. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Section 6.1<o:p></o:p></p><p class=MsoNormal>The authors assume a certain level of knowledge. For example, the term “CubeSat” is used throughout the RFP without being defined. This needs to be defined up front so that a common understanding can be reached. What are the characteristics of a CubeSat that uniquely make it one? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>6.2 Scope of Proposals Sought<o:p></o:p></p><p class=MsoNormal>This RFP solicits proposals for a CRM (at the discretion of the submitter) based on the System Modeling Language TM [SysML] to facilitate the development of a mission specific CubeSat system.<o:p></o:p></p><p class=MsoNormal>I don’t know what this means? Why at the discretion of the submitter? Why is it just “based on” SysML? Section 6.4.1.11 says it must be implemented using SysML. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>6.3 Related non-OMG Activities, Documents and Standards<o:p></o:p></p><p class=MsoNormal>The list of organizations is USA-only. Surely other international organizations exist that would be interested in this. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>6.4.1.1<o:p></o:p></p><p class=MsoNormal>“Regarding these stakeholders, requirements, licenses, regulations, timelines, and procedures must be well understood and addressed as part of the CRM.” What licenses are being referred to here? None are mentioned in this RFP.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>6.4.1.2 The CRM will be extendable to accommodate other national stakeholders and associated regulations and guidelines.<o:p></o:p></p><p class=MsoNormal>Which ones? This is a very open ended requirement. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>6.4.1.3 The CRM shall provide well defined viewpoints and views for addressing stakeholder needs and objectives.<o:p></o:p></p><p class=MsoNormal>What makes a viewpoint “well-defined”? This needs to be further elaborated. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>6.4.1.8 The CRM shall provide power, cost, and mass roll-up capabilities starting at the CubeSat component level.<o:p></o:p></p><p class=MsoNormal>What is the plan for making this executable? How will this be possible except within a vendor specific tool?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>6.4.1.9 The CRM shall allow for the modification and extension of model elements and responsibilities to support mission objectives.<o:p></o:p></p><p class=MsoNormal>What is a model element responsibility? This requirement needs to be more exact. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>6.4.1.12 The CRM shall be self-documentation on how to apply CRM for creation of the mission specific CubeSat<o:p></o:p></p><p class=MsoNormal>This sentence makes no sense in its current form.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>6.4.1.13 The CRM must provide a model extraction in the form of a navigable document, preferably HTML and the associated XMI file.<o:p></o:p></p><p class=MsoNormal>Extraction from what exactly? Again, it appears that this will be a proprietary implementation in a single tool, which should NOT be allowed.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A.2 Glossary Specific to this RFP<o:p></o:p></p><p class=MsoNormal>[CRM] CubeSat Reference Model<o:p></o:p></p><p class=MsoNormal>There needs to be more of a glossary. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'><img width=72 height=28 id="Picture_x0020_7" src="cid:image001.png@01D3B9A1.D7B25C20" alt="cid:image007.png@01D1FFB8.695AD1C0"></span><b><span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></b></p><p class=MsoNormal><b><span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></b></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:"Century Gothic","sans-serif";color:#404040'>Matthew Hause<o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Century Gothic","sans-serif";color:#404040'>PTC Engineering Fellow<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Century Gothic","sans-serif";color:#404040'>MBSE Specialist<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Century Gothic","sans-serif";color:#404040'><o:p> </o:p></span></p><p class=MsoNormal><span lang=ES-MX style='font-size:9.0pt;font-family:"Century Gothic","sans-serif";color:#404040'>P +1 917 514 7581<o:p></o:p></span></p><p class=MsoNormal><span lang=ES-MX style='font-size:9.0pt;font-family:"Century Gothic","sans-serif";color:#404040'>E </span><span style='font-size:9.0pt;font-family:"Century Gothic","sans-serif";color:#404040'><a href="mailto:MHause@PTC.com"><span lang=ES-MX style='color:#0563C1'>MHause@PTC.com</span></a></span><span lang=ES-MX style='font-size:9.0pt;font-family:"Century Gothic","sans-serif";color:#404040'><o:p></o:p></span></p><p class=MsoNormal><span lang=ES-MX style='font-size:10.5pt;font-family:"Century Gothic","sans-serif";color:#404040'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:"Century Gothic","sans-serif";color:#404040'><a href="http://www.ptc.com/"><span lang=ES-MX style='color:#404040'>ptc.com</span></a></span></b><span style='font-size:10.5pt;font-family:"Century Gothic","sans-serif";color:#404040'> </span><span lang=ES-MX style='font-size:10.5pt;font-family:"Century Gothic","sans-serif";color:#404040'><o:p></o:p></span></p><p class=MsoNormal><span lang=ES-MX style='font-size:10.5pt;font-family:"Arial","sans-serif";color:#4C4D4F'><o:p> </o:p></span></p><p class=MsoNormal><a href="http://www.linkedin.com/company/ptc"><span style='font-size:10.5pt;font-family:"Arial","sans-serif";text-decoration:none'><img border=0 width=20 height=20 id="Picture_x0020_2" src="cid:image002.jpg@01D3B9A1.D7B25C20" alt="Linked In Icon"></span></a><span style='font-size:10.5pt;font-family:"Arial","sans-serif";color:#4C4D4F'> </span><a href="http://twitter.com/PTC"><span style='font-size:10.5pt;font-family:"Arial","sans-serif";text-decoration:none'><img border=0 width=20 height=20 id="Picture_x0020_3" src="cid:image003.jpg@01D3B9A1.D7B25C20" alt="Twitter Icon"></span></a><span style='font-size:10.5pt;font-family:"Arial","sans-serif";color:#4C4D4F'> </span><a href="http://www.slideshare.net/ptc"><span style='font-size:10.5pt;font-family:"Arial","sans-serif";text-decoration:none'><img border=0 width=20 height=20 id="Picture_x0020_4" src="cid:image004.jpg@01D3B9A1.D7B25C20" alt="Slide Share Icon"></span></a><span style='font-size:10.5pt;font-family:"Arial","sans-serif";color:#4C4D4F'> </span><a href="http://www.youtube.com/user/ptcstudio"><span style='font-size:10.5pt;font-family:"Arial","sans-serif";text-decoration:none'><img border=0 width=20 height=20 id="Picture_x0020_5" src="cid:image005.jpg@01D3B9A1.D7B25C20" alt="YouTube Icon"></span></a><span style='font-size:10.5pt;font-family:"Arial","sans-serif";color:#4C4D4F'> </span><a href="http://www.facebook.com/PTC.Inc"><span style='font-size:10.5pt;font-family:"Arial","sans-serif";text-decoration:none'><img border=0 width=20 height=20 id="Picture_x0020_6" src="cid:image006.jpg@01D3B9A1.D7B25C20" alt="Facebook Icon"></span></a><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>