<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 15 (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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1559047325;
mso-list-type:hybrid;
mso-list-template-ids:2101908266 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
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;
margin-left:1.25in;
text-indent:-.25in;
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;
margin-left:1.75in;
text-indent:-.25in;
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;
margin-left:2.25in;
text-indent:-.25in;
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;
margin-left:2.75in;
text-indent:-.25in;
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;
margin-left:3.25in;
text-indent:-.25in;
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;
margin-left:3.75in;
text-indent:-.25in;
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;
margin-left:4.25in;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>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><o:p> </o:p></p><p class=MsoNormal>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><o:p> </o:p></p><p class=MsoNormal>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><o:p> </o:p></p><p class=MsoNormal>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><o:p> </o:p></p><p class=MsoNormal>Here are a few notes: <o:p></o:p></p><p class=MsoListParagraph style='margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>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=MsoListParagraph style='margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>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">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=MsoListParagraph style='margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>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=MsoListParagraph style='margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>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><o:p> </o:p></p><p class=MsoNormal>For discussion online and at Mountain View. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> -=- Mike<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Mike Kearney<o:p></o:p></p><p class=MsoNormal>Huntsville, Alabama, USA<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>