[Moims-dai] Digital Archive Architecture Design Document Project Plan

[John Garrett]

Thanks.

 

Good luck with your presentation.

 

From: MOIMS-DAI [mailto:moims-dai-bounces at mailman.ccsds.org] On Behalf Of Robert R Downs
Sent: Thursday, December 8, 2016 9:05 AM
To: moims-dai at mailman.ccsds.org
Subject: Re: [Moims-dai] Digital Archive Architecture Design Document Project Plan

 

Hi John,

Since I will be attending the 2016 Fall AGU Meeting next week and will not be able to join the telecon, I am sharing my response with you now. 

The draft looks good. I do not have any objections to the later ending date and believe that it is better to be realistic about the times that tasks will take and even to include appropriate buffers for unexpected or potential delays instead of creating schedules based on unrealistic time predictions that cannot be achieved.

Thanks,

Bob

Robert R. Downs, PhD
Senior Digital Archivist and Senior Staff Associate Officer of Research
Acting Head of Cyberinfrastructure and Informatics Research and Development
Center for International Earth Science Information Network (CIESIN),
The Earth Institute, Columbia University
P.O. Box 1000, 61 Route 9W, Palisades, NY 10964 USA
Voice: 845-365-8985; fax: 845-365-8922
E-mail: rdowns at ciesin.columbia.edu <mailto:rdowns at ciesin.columbia.edu> 
Columbia University CIESIN Web site: http://www.ciesin.columbia.edu
ORCID: 0000-0002-8595-5134 

 

On 12/8/2016 1:23 AM, John Garrett wrote:

Hi,

 

I have an Action Item to add a project plan for Digital Archive Architecture Design Document  to CCSDS CWE Framework.  I’ve attached a draft of what I intend to enter into the CCSDS System before our Tuesday telecon (or I can try to enter it after if people want to discuss it at the telecon.)

Please feel free to provide any updates you think are appropriate.

 

>From the overall DAI plan, our plan was to start this project early the coming year and finish in 2020.  I came close but show the project ending in early 2021.  I’ve created a spreadsheet with estimated times to complete all the activities throughout the project.  I’ve included the one’s required to show completion dates for in the CCSDS system (the unshaded rows).  I’ve also added background activities that do not need dates in the CCSDS form, but they are activities which we need to allot time for and get through.  These are the lightly shaded rows and many of those activities are performed by CCSDS and are out of our control.  I’ve assigned what I consider as optimistic times for completion of those tasks.  Personally, based on past experience, I think we may end up behind schedule on those items.  I’ve also currently included ISO reviews in this document.  I planned with the presumption that we will want to have concurrent CCSDS and ISO reviews.  Is that what others expect for this document?  Those activities are shown with darker shading.   Note that the ISO processing takes place in parallel to the CCSDS review so the time required for the CCSDS review overlaps with ISO processing and review.  Alternatively we could start and end the CCSDS and ISO reviews at the same time, which we have sometimes done in the past.

 

Let me know what you think.

 

Wishing you prosperity and peace,

-JOhn 

 






_______________________________________________
MOIMS-DAI mailing list
MOIMS-DAI at mailman.ccsds.org <mailto:MOIMS-DAI at mailman.ccsds.org> 
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20161208/669a3f4d/attachment.html>