Replied: Wed, 17 Jun 1998 18:26:07 -0400 Replied: Sandie Kappes Received: from ex1.ncsa.uiuc.edu (ex1.ncsa.uiuc.edu [141.142.3.16]) by postoffice.npac.syr.edu (8.7.5/8.7.1) with ESMTP id RAA13021; Wed, 17 Jun 1998 17:58:25 -0400 (EDT) Received: from mx1.ncsa.uiuc.edu (mx1.ncsa.uiuc.edu [141.142.3.15]) by ex1.ncsa.uiuc.edu (8.8.8/8.8.8) with ESMTP id QAA02567; Wed, 17 Jun 1998 16:58:27 -0500 (CDT) Received: from kappes.ncsa.uiuc.edu (kappes.ncsa.uiuc.edu [141.142.20.8]) by mx1.ncsa.uiuc.edu (8.8.8/8.8.8) with SMTP id QAA20309; Wed, 17 Jun 1998 16:58:27 -0500 (CDT) Received: by kappes.ncsa.uiuc.edu with Microsoft Mail id <01BD9A11.3FDE59A0@kappes.ncsa.uiuc.edu>; Wed, 17 Jun 1998 16:59:11 -0500 Message-ID: <01BD9A11.3FDE59A0@kappes.ncsa.uiuc.edu> X-UIDL: 898121107.001 From: Sandie Kappes To: "E. J. Grabert (E-mail)" , "David Bernholdt (E-mail)" , "Geoffrey Fox (E-mail)" Subject: IC Objectives Date: Wed, 17 Jun 1998 16:59:08 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="---- =_NextPart_000_01BD9A11.4010B440" Content-Length: 8445 Status: U ------ =_NextPart_000_01BD9A11.4010B440 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To all, =20 I hope you don't mind but I've taken some liberties with develoment of = the I/C vision and tasks document. (My many years of writing proposals = and R&D statements for a Govt R&D agency made me do it.) I didn't feel = that what was written was a "vision" statement although it contained the = elements of the vision. So I have tried to add some more vision = statement type words and organized it differently. I'm not done yet but = thought I would send it on so you can see what I'm up to. Right now I'm = taking the tasks you defined in one of your documents and putting them = in the appropriate spot of the new document structure. I got as far as = the point where it says "Start Here". I think all of the tasks will fit = neatly into the 4 categories. I am also adding NCSA tasks where I feel = it is appropriate. Hopefully, you won't think I've overstepped my = bounds and will accept my input. Unless you tell me that you don't like = what I'm doing, I should finish it tomorrow morning. =20 Sandie =00 ------ =_NextPart_000_01BD9A11.4010B440 Content-Type: text/html; name="IC Objectives.html" Content-Transfer-Encoding: quoted-printable IC Objectives

ARL MSRC PET I/C Vision Statement


The vision of the Information and Communication (I/C) effort at ARL = is to establish the ARL MSRC PET as a leader in facilitating and = promoting effective uses of I/C technology in support of the DoD HPC = user community.

To achieve this vision, the I/C effort provides expertise in = information technologies to support information dissemination and = management, training, and collaboration for the MSRC PET effort. I/C's = role cuts across Computational Technology Areas to provide a wide range = of technologies that enhance the MSRC PET effort to support HPC users. = The main objectives of I/C are to:

  • Enable timely dissemination of information relevant to the PET = effort.
  • Provide technology support to enable delivery of high-quality = training to HPC users.
  • Provide collaborative environments to support research and = management activities within the PET and DoD HPC user community.
  • Provide information technologies to support effective management of = HPC data.

To achieve the I/C vision for ARL, the following goals must be met by = Year 5 of the PET Program:

Goal 1: Outreach - Achieve effective outreach to the = PET user community through interaction with users, technology transfer = of I/C technologies, and timely information disemination.

Goal 2: Training Support - Deploy a collaborative PET = Learning Environment to support training of DoD HPC users in = state-of-the-art HPC technologies. This integrated environment will = include both asynchronous and synchronous technologies for training = delivery and will enable training needs assessment, rapid course = development and enhancement, course evaluation, and course = administration.

Goal 3: Collaboration - Deploy collaboration tools to = improve communication and collaboration among the PET and DoD HPC user = community. These tools shall impact multiple collaborative activities = to include PET administration, virtual meetings, application development = and utilization, and research project management.

Goal 4: Information Management - Deploy database = technologies which enable effective management and analysis of HPC = data.

 

The following tasks are necessary to meet these goals:

Goal 1: Outreach

Year 3:

1a) Determine user needs in respect to database management tools for = the ARL PET Web Site. Where appropriate, develop implentation plans and = deploy database management tools and provide user training. (G1A)

1b) Monitor ARL PET Web Site usage statistics to determine impact of = the site on providing effective information disemination.

1c) Assist ARL PET Web Site content providers in the development of = web-based materials by providing tool recommendations, training, and = guidance documents. (G1B)

1d) Interact regularly with CTA leads and HPC users to identify I/C = user needs.

Year 4,5:

1e) Conduct ongoing work as determined by user needs and technology = evolution. (G1C)

Goal 2: Training Support

 

Goal 3: Collaboration

Year 3:

3a) Deploy basic synchronous and asynchronous collaboratory (via = Tango) to small prototype group. This user group should include one CTA = group (where emphasis "science") and a (subset) of PET team itself = (where emphasis would be "management"). Provide training support and = evaluation function. Support includes "bug database" and ongoing product = improvement. (G2A) (Sept 1 98)

3b) Deploy one or more selected additional tools for comparison with = Tango capabilities. Note in 3a) and 3b) there is an implied interaction = between deployment and technical support teams. = (G2B)(Jan 1 99):

By this do you mean, evaluate = tools that could potentially replace current components within Tango or = do you mean commercial tools which provide similar overall capability as = Tango (e.g. Symposium)? Please don't take that wrong - I know Tango is = much more than that but, for delivery of distance training, tools like = Symposium could be a viable option.

3c) Deploy initial advanced features such as shared = visualization (CTA) or calendar/documents (with shared editing = capabilities) (management user group) (G2C) (Jan 1 99)

3d) Evaluate lessons of 3a/3b) and broaden = deployment if possible. (G2D) Year 3 (June 1 = 99)

3e) Deploy asynchronous collaboration environment, the PET Community, = which leverages efforts of the Alliance Community Intranet.

Year 4,5:

3f) Implement environments to support collaborative application = development.

3g) Implement collaborative project management environment.

 

Our plan is not consistent with details of Pet Vision but this Vision = needs to be modified. However the general structure is clear -- we = continue to iterate the train/deploy/evaluate/improve = functionality/implementation structure so as to achieve collaborative = scientific research and collaborative technical management support for a = broad range of users. The goal is extensive deployment and rich = functionality by end of year 5 with most of technical development in = years 3 and 4.

??? In reference to the above paragraph. When will this vision be = modified if at all? Not sure it's good to make such a statement. Would = be better to just state the general structure for the plan leaving the = overall task fairly vague. My quick attempt at this is 3f and 3g.

Start here:

G3) Produce an evaluation and associated training to allow use of = multimedia (audio/video over foils) enhancements to training = material. Phase in use of databases as back-end support

G3A) Year 2(July 98 Evaluate) and Year 3(October 1 Deploy) Produce = evaluation of existing systems for pure file system and database support = of multimedia. In particular establish process and standards for = audio/video over foils in both "real-time" and stylized situations. = Evaluate importance of and tools for editing. This task should not need = to be extended into years 4 and 5 as can be lumped into G1) G2) and = G4)

 

Goal 4: Information Management

------ =_NextPart_000_01BD9A11.4010B440--