James, 'Planning blight' is a phrase used by Matt earlier. Sorry I managed to separate my comments from your and his conversation (as I am new the to NDG technical list).
I see my deliverable in the 'revitalizing' project to be setting up the procedures to ensure that new DDS can cope with change in a managed way, whereas the IA project (or another project if that's not the remit of the IA project?) will think about the changes that will be required for future the development of the DDS, thereby allowing the new DDS to evolve as required. Kay From: [email protected] [mailto:[email protected]] On Behalf Of James Doughty Sent: 30 September 2010 10:42 To: NERC DataGrid Technical List Cc: Thomas, David A; Brown, Mike J Subject: Re: [ndg-technical] SIS Information Architecture - Business Processes and People - Configuration Management Kay New phrase to me is that there 'planning blight'. What do you actually mean by it? In your second paragraph it sounds like the 'Revitalise Data Discovery Service' project is handling this specifically and as such I will refer to this in our summary. Clearly it is a very important process and should be included in the IA Implementation Plan in some shape or form. Regards James On 30 September 2010 09:41, Thorne, Kay <[email protected]<mailto:[email protected]>> wrote: Hi James/Matt As Matt mentions: 'With the "revitalized" service, we've got a new setup now, with the backend services (DWS, DPWS) completely separated from the front end portal (DDS, DPP). Clearly there's a need to ensure that updates to any of these 4 (and the vocab service) are managed together, but also to overcome planning blight and ensure that progress can be made with them when needed.' The back-end services are hosted at CEDA and the front-end portal will be hosted at BODC. Consequently, it has already been recognized that the change management procedures are an important component of the 'revitalizing' project. Therefore the project brief contains the deliverable 'Produce protocol document to disseminate procedures and responsibilities for robust testing, routine maintenance, trouble shooting, and change management.' by 31/10/2010. It is envisaged that this document will be authored by all concerned. However as Steve Donegan and I undertook the preparation of an important (but out of the original 'revitalizing' project scope) document to finalize NERC Metadata Standard I've anticipated that this deliverable will be a little behind schedule as work is yet to start. This delay has already be communicated to SIB. Kay -- This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. _______________________________________________ NDG-technical mailing list [email protected]<mailto:[email protected]> http://lists.ncas.ac.uk/mailman/listinfo/ndg-technical -- James Doughty Director Diass Limited 07985 443973 [email protected]<mailto:[email protected]>
_______________________________________________ NDG-technical mailing list [email protected] http://lists.ncas.ac.uk/mailman/listinfo/ndg-technical
