<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=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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: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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.gmail-m6623856760081812322msolistparagraph, li.gmail-m6623856760081812322msolistparagraph, div.gmail-m6623856760081812322msolistparagraph
{mso-style-name:gmail-m_6623856760081812322msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#002060;}
.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><a name="_MailEndCompose"><span style='color:#002060'>DTOPP is nice and pronounceable, so I’m fine with that, though it seems just a little overly-directive. Updated in the attached. I was avoiding “Target” because Terry had issue with that term in our last telecon. <o:p></o:p></span></a></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#002060'>Mark, good comments, responses in the attached. I took issue only with the “contract” concern. Wow, that communique from NASA to NARA is huge. May cause me to rethink much of this. Need more time to absorb it. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#002060'>I saw Note 1 but I couldn’t find Item 1. I saw references to Item 1, but the items seemed to start at 101. Can you point me to Item 1? <o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#002060'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#002060'>Mike Kearney<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> MOIMS-DAI [mailto:moims-dai-bounces@mailman.ccsds.org] <b>On Behalf Of </b>David Giaretta<br><b>Sent:</b> Sunday, April 14, 2019 1:28 PM<br><b>To:</b> 'MOIMS-Data Archive Interoperability' <moims-dai@mailman.ccsds.org><br><b>Subject:</b> Re: [Moims-dai] IPELTU Annex D - DPOP Checklist<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB>Mike<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Mark’s comments make sense to me.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>My only comment is that since OAIS already uses “Preservation Objectives” in a specific way, we should change the name to “Digital Target of Preservation Proforma”, which would be DTOPP.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>..David<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><b>From:</b> MOIMS-DAI <<a href="mailto:moims-dai-bounces@mailman.ccsds.org">moims-dai-bounces@mailman.ccsds.org</a>> <b>On Behalf Of </b>Mark Conrad<br><b>Sent:</b> 12 April 2019 19:35<br><b>To:</b> MOIMS-Data Archive Interoperability <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>><br><b>Subject:</b> Re: [Moims-dai] IPELTU Annex D - DPOP Checklist<o:p></o:p></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-GB>Mike,<o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Thanks for putting this together. Overall it looks very good. I have attached a version with my comments. I have also attached a records disposition schedule from NASA that lists some of the types of records that need to be retained. See especially Item 1 and Note 1. I hope this information is helpful.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB><br clear=all><o:p></o:p></span></p><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal><span lang=EN-GB>Mark Conrad<br>NARA Information Services<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-GB>Systems Engineering Division (IT)<br>The National Archives and Records Administration<br>Erma Ora Byrd Conference and Learning Center<br>Building 494, Room 225<br>610 State Route 956<br>Rocket Center, WV 26726<br><br>Phone: 304-726-7820<br>Fax: 304-726-7802<br>Email: <a href="mailto:mark.conrad@nara.gov" target="_blank">mark.conrad@nara.gov</a> <o:p></o:p></span></p></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div><div><p class=MsoNormal><span lang=EN-GB>On Thu, Apr 11, 2019 at 6:39 PM Mike Kearney <<a href="mailto:kearneysolutions@gmail.com">kearneysolutions@gmail.com</a>> wrote:<o:p></o:p></span></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>DIA WG colleagues: In the telecon on Tuesday 4/9, we discussed my draft Annex D for IPELTU. For those that weren’t there, my original action was to develop an annex to instruct space <b><i>operations</i></b> teams what data should be preserved. I have expanded that to be an annex for spaceflight <b><i>programs/projects as a whole</i></b>, on the premise that at the beginning of a project we need for the top-level program/project manager to dictate to the rest of the team what will or will not be preserved, from his mission, in the long term. So it’s no longer just operations, it’s the whole mission. The checklist makes some pointed statements that should get the attention of management, about what results of his project are worth preserving in the long run. In this way, it encourages early (pre-phase A?) planning and recognition that resources should be allocated for preservation. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I’ve coined the phrase DPOP (Digital Preservation Objectives Proforma) Checklist. After some discussion, we discarded similar terms to PICS- and ICS-Proforma to avoid any implication of “compliance” guidance. Some discussion on “Proforma” is in the first page instructions. The single word version (proforma vs. pro forma) is used for compatibility with other CCSDS usage. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>While this one is for space missions, I envision other DPOP Checklists as annexes for other types of endeavors. Manufacturing, academia, oceaneering, information technology development, etc. CCSDS does space missions, but other disciplines can be invited to create DPOP Checklists for their industry. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>So, this is a very rough draft. Steve Hughes has agreed to try to expand section 1.5 with the experience of PDS, but of course other contributors and other comments are welcome. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Here are a few notes: <o:p></o:p></p><p class=gmail-m6623856760081812322msolistparagraph style='margin-left:.25in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span>I think it’s important to keep the first page instructions limited to one page. If it’s too long, it won’t be read or used. It has to be something a manager can pick up and start checking/revising quickly. <o:p></o:p></p><p class=gmail-m6623856760081812322msolistparagraph style='margin-left:.25in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span>For Level 0, 1 and 2 processing guidance, I used this website: <a href="http://www.srl.caltech.edu/ACE/ASC/level1/dpl_def.htm" target="_blank">http://www.srl.caltech.edu/ACE/ASC/level1/dpl_def.htm</a> Of course, different missions will have different terminology, so I reflected that in the first-page instructions. <o:p></o:p></p><p class=gmail-m6623856760081812322msolistparagraph style='margin-left:.25in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span>My intention in the check boxes is that this should be made available in Word format (perhaps from SANA) for managers to easily capture and modify for their program. <o:p></o:p></p><p class=gmail-m6623856760081812322msolistparagraph style='margin-left:.25in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span>Two levels of detail are represented. High level for the managers that want only 10 or so items to check off, and let the lower level teams interpret it. Detailed level (just barely begun) for the managers that understand what needs to be preserved, and want to manage the resources needed to preserve it. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>For discussion online and at Mountain View. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> -=- Mike<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Mike Kearney<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Huntsville, Alabama, USA<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><p class=MsoNormal><span lang=EN-GB>_______________________________________________<br>MOIMS-DAI mailing list<br><a href="mailto:MOIMS-DAI@mailman.ccsds.org" target="_blank">MOIMS-DAI@mailman.ccsds.org</a><br><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai" target="_blank">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai</a><o:p></o:p></span></p></blockquote></div></div></body></html>