|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conduct of science and engineering research |
|
|
|
|
|
|
|
|
|
|
|
|
Applications of information technology to |
|
|
|
|
|
|
|
|
science and engineering research |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Cyberinfrastructure supporting applications |
|
|
|
|
|
|
|
|
|
|
|
Core technologies incorporated into |
|
|
|
|
|
|
cyberinfrastructure |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Figure
4.1. A layered architectural view of the ACP. |
|
|
|
|
|
The top and bottom layers fall outside the scope of this project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conduct of science and engineering research |
|
|
|
|
|
|
|
|
|
|
|
|
Applications (discipline specific) |
|
|
|
|
|
|
|
|
Applications (generic) |
|
|
|
|
|
|
|
|
|
|
|
|
|
Technological and social systems |
|
|
|
|
|
|
|
|
|
|
|
Core information technologies
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Figure
4.3. Relationship of the layers of Figure 4.1 to underlying |
|
|
|
|
disciplines. Applications are a hybrid case with
shared responsibility |
|
|
|
|
between technological and disciplinary programs. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Long-term and applied researchers |
Research in technologies, |
|
|
|
(applications, systems, core technolgies) |
systems, and applications |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Commercial suppliers, development |
|
|
|
|
|
centers (whose products are based on |
Development or |
|
|
|
research
prototypes), community developers, |
or acquisition |
|
|
|
|
integrators |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
End-user staff support, operational |
Operations in support |
|
|
|
centers, service providers |
of end users |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Figure
4.4. Summary of specific players |
|
|
|
|
delivering parts of the ACP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Community-Specific Knowledge Environments for Research
and Education |
|
|
|
(collaboratory, so-laboratory, grid community, |
|
|
|
e-science community, virtual community) |
|
|
|
|
|
|
|
|
|
Customization for discipline-and project-specific
applications |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
High |
Data, information, |
Observation, |
Interfaces, |
Collaboration |
|
|
|
performance |
knowledge |
measurement |
visualization |
services |
|
|
|
computation |
management |
fabrication |
services |
|
|
|
|
services |
services |
services |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Networking, Operating Systems, Middleware |
|
|
|
|
|
|
|
|
|
|
|
|
Base Technolgy: computation, storage, communication |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Grey area indicates cyberinfrastructure: hardware,
software, services, personnel, organizations |
|
|
|
|
|
|
|
Figure 2.1 Integrated cyberinfrastructure services
to enable new knowledge |
|
|
|
environments for research and education |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Push |
The Goal of an ACP |
The Pull |
|
|
|
|
|
|
|
Computation |
Cyberinfrastructure to enable |
Vision & requirements |
|
|
|
knowledge environments to |
from the frontiers of |
|
|
Content |
revolutionize science and |
science and engineering |
|
|
|
engineering education and |
research |
|
|
|
Interaction |
research |
|
|
|
|
|
|
|
|
|
|
|
|
Figure 3.1. The push and pull for an ACP. |
|
|
|
|
|
|
|
|
|
|
|
|