Challenges and Opportunities for Innovation in the Public Works ...

More documents

Recommendations

Info

Sharing Experience Between Manufacturing and Construction decisions in a manner suitable for communication. The following functional requirements must be considered: (R-c-1) Support the least commitment approach: A way to facilitate upstream and downstream communications is not to make premature commitments or specifications, leaving room for others to express their concerns later on. This is called the least commitment approach to problem solving in Al, and is a very useful concept to promote communications in concurrent engineering. For example, one way to support the least commitment approach is to develop computer tools that allow interval value specifications. In the early stages of product development, few details may be explicitly known. Engineers can use intervals to specify acceptable ranges of values based on upstream concerns, leaving these intervals to be further refined by others at later stages where downstream concerns become apparent. Traditional tools only support atomic value specifications (e.g., single numbers or symbols) and, hence, force engineers to commit to specific values unnecessarily. In contrast, interval values, much like the tolerance concept in design and manufacturing integration, can make product decisions more "communicable" to promote concurrent engineering. (R-c-2) Adaptive focus at multiple abstraction levels: Upstream and downstream product concerns are often expressed with different levels of abstraction. Therefore, computer tools must be able to support reasoning with adaptive focus for concurrent engineering communication. Given a specification of "interests" based on engineers' different roles in the product development team, such tools must be able to automatically mine out relevant information from generic product specifications. As engineers change their interests at different stages, these tools must adapt their focus of information mining accordingly. Without such tools to support adaptive focus, engineers will be overwhelmed by the amount of information, most of which is not directly relevant to their current interests, and unable to communicate effectively at the proper time. (R-c-3) Facilitate early evaluation of decisions: Early evaluations are important because they can eliminate unpromising choices before major resources are consumed. However, upstream evaluations are difficult because most traditional analysis tools require very detailed decision specifications and, therefore, can only be used for downstream analyses. Methods must be developed to form analysis models based on downstream detailed knowledge to support early evaluations of upstream decisions. With these early evaluation models extracted from downstream knowledge, product decisions can be gradually refined at optimized at various stages. (R-c-4) Provide hypothetical reasoning: Since not all the concerns are explicitly known at upstream, engineers often need to hypothesize downstream conditions to generate several different product scenarios. Hypothetical reasoning is an important activity in product development, and good computer support for this activity can greatly assist concurrent engineering. There are several software techniques from AI, such as multiple worlds and truth maintenance systems, which can be used to support multi-scenario reasoning based on different hypotheses and can automatically merge different scenarios when necessary. These techniques must be further developed and integrated to support hypothetical reasoning at different abstraction levels for concurrent engineering. 61
Arthur Baskin and Stephen C-Y Lu 5.4 Coordination of Group Problem-Solving Activities Concurrent engineering is inherently a group activity and, therefore, group productivity" is a main concern. To date, most computer tools are design for enhancing individual productivity. New tools must be developed to support group interaction of engineering teams with different technical backgrounds and geographical locations (17). These interactions could be centralized or distributed, synchronous or asynchronous, technical or administrative, and involving both people and machines. For the concurrent engineering purpose, these group productivity tools must meet the following requirements: (R-d-1) Deal with homogeneous and heterogeneous tools: Unlike small groups where members are likely to use similar tools in problem solving, heterogeneity of computer tools always exists when dealing with large engineering groups or a collection of small groups. Group productivity tools must be able to accommodate small and large groups with similar and different tools. These group tools should act as a common platform for group work, allowing results generated from different tools to be integrated. The issues related to unified representations, standard data definitions, and automatic consistency management discussed above play important roles in supporting this group-work platform. (R-d-2) Manage ownerships among group members: Although engineers are encouraged to share ideas and work cooperatively in concurrent engineering, they must declare and control ownership of some product decisions in order for the product development team to be effective. Without some technical authority of decisions, it is impossible to assign and evaluate the responsibilities of engineers in the team. Computer tools must automatically manage these ownerships and responsibilities of decisions as they are declared and agreed by the group members. These tools should also allow sharing and changing of ownerships as necessary and manage these situations accordingly. (R-d-3) Support synchronous and asynchronous interaction: Depending on the nature and stages of product development, the required interactions in a product team can be either synchronous or asynchronous. Supporting synchronous interaction is important because it allows implications and feedback of one engineer's decisions to be immediately known by the group members. However, such instantaneous interactions could sometime cause instability of the overall team development efforts and discourage innovation by team members who might wish to try out some new ideas without being publicized right away. Since good ideas take time to mature before they can be seriously shared, engineers may sometime prefer asynchronous interaction with large time delay. Group productivity tools for concurrent engineering should be able to support both types of interactions. (R-d-4) Promote local and remote interaction: Engineers who have required product development expertise may not come from the same location, and yet still need to interact during the product development process. Computer tools which can create "virtual co-location' among engineers regardless of their actual geographic locations are needed for concurrent engineering. New hardware and software technologies, such as local and global area networking, multimedium information systems, and distributed databases supporting consistent and persistent data storage, are all important to this activity. 62
Page 1 and 2:
.. . AD-A281 083 ' US-m op fEomsA -
Page 3 and 4:
CEWRC-IWR DEPARTMENT OF THE ARMY CO
Page 5 and 6:
CONTENTS INTRODUCTION .............
Page 7 and 8:
CHALLENGES AND OPPORTUNITIES FOR IN
Page 9 and 10:
WORKSHOP PRESENTATIONS
Page 11 and 12:
growing threat from major fires, an
Page 13 and 14: - provide the highest technological
Page 15 and 16: SEARCHING FOR THE INFRASTRUCTURE OF
Page 17 and 18: Because of the large investment emb
Page 19 and 20: Finally, the substantial public wor
Page 21 and 22: COST-EFFECTIVE INFRASTRUCTURE PERFO
Page 23 and 24: 0 Infrastructure innovation will su
Page 25 and 26: REFERENCES Balzhiser, R. E. 1989. M
Page 27 and 28: highways based on this total govern
Page 29 and 30: important aspect of a nations infra
Page 31 and 32: Universities Universities face chal
Page 33 and 34: Table 3. Federal, State & Local - f
Page 35 and 36: C 0 > Ep - LII> 6- 322 El
Page 37 and 38: INTRODUCTIO Stone & Webster Enginee
Page 39 and 40: correct. Conduit is not usually mod
Page 41 and 42: the duct section. The design of the
Page 43 and 44: mechanical and structural design. T
Page 45 and 46: its| ISOC [ FAN OUTLET TO STACK BRE
Page 47 and 48: Figure 4. Construction Sequence Mod
Page 49 and 50: Arthur Baskin and Stephen C-Y Lu Ma
Page 51 and 52: Arthur Baskin and Stephen C-Y Lu 2.
Page 55 and 56: Arthur Baskin and Stephen C-Y Lu "*
Page 57 and 58: Arthur Baskin and Stephen C-Y Lu Ex
Page 59 and 60: Arthur Baskin and Stephen C-V Lu Di
Page 63: Arthur Baskin and Stephen C-Y Lu de
Page 67 and 68: Arthur BasiWn and Stephen C-Y Lu To
Page 69 and 70: Arthur Baskin and Stephen C-Y Lu Th
Page 71 and 72: Arthur Baskin and Stephen C-Y Lu co
Page 73 and 74: Arthur Baskin and Stephen C-Y Lu b-
Page 77 and 78: Arthur Baskin and Stephen C-Y Lu (1
Page 79 and 80: Arthur B"sWin and Stephen C-Y Lu (3
Page 81 and 82: But SHRP's success further undersco
Page 83 and 84: For all this new Research Activity,
Page 85 and 86: Technological Advances and Public W
Page 87 and 88: limits of existing technologies and
Page 89 and 90: through the formulation of visions
Page 91 and 92: proposed that it develop a soil com
Page 93 and 94: of each side, the time for completi
Page 95 and 96: compensation structure that not onl
Page 97 and 98: PSOCIETAL NEEDI ICONCEPT DEVELOPM:E
Page 99 and 100: JAPAN U.S.A. * REASONS FOR RESEARCH
Page 101 and 102: U.S. PRESSS PROGRAM Executive IwU.
Page 103 and 104: 1. Information is lacking or scarce
Page 105 and 106: exist, offer explanations of these
Page 107 and 108: WORKSHOP CHALLENGES AND OPPORTUNITI
Page 109 and 110: Table 1, Ranking of Agencies or Gro
Page 111 and 112: From the overall study, three gener
Page 113 and 114: 3. INTRODUCTION The Nation's infras
Page 115:
A group of recognized experts on is
Page 118 and 119:
abound to the point where I have op
Page 120 and 121:
Is the bottom line that the first b
Page 122 and 123:
SUPPLY DEMAND Provider of Public Wo
Page 124 and 125:
The GFRC has assisted other federal
Page 126 and 127:
Financial Sources - - The Intergove
Page 128 and 129:
constraint upon state and local gov
Page 130 and 131:
To understand the implications of t
Page 132 and 133:
Intergovernmental Sources of Fundin
Page 134 and 135:
Tremendous differences exist among
Page 136 and 137:
funds, these have the effect of low
Page 138 and 139:
population growth over the last thr
Page 140 and 141:
Table I Sources of Funds for State
Page 142 and 143:
0000 ' O C 00 - ' Ir . c - q - . '0
Page 144 and 145:
equirements of construction; those
Page 146 and 147:
in the birth of engineering as the
Page 148 and 149:
allocate known risks among themselv
Page 150 and 151:
outine infrastructure project fully
Page 152 and 153:
Innovation and Technology Transfer
Page 154 and 155:
Technology Transfer Plan for Each P
Page 156 and 157:
The ATLSS Integrated Buildings Syst
Page 158 and 159:
Technology Transfer (T) as a Work-P
Page 160 and 161:
In the end, one may find that there
Page 162 and 163:
different evolutionary stages. Each
Page 164 and 165:
References. 1. Bonnett, R. K., 1989
Page 166 and 167:
The typical approach for the captur
Page 168 and 169:
of loss does exist. Conversely, in
Page 170 and 171:
B. LIABILITY ARISING OUT OF NEGLIGE
Page 172 and 173:
(or a commercialization entity unde
Page 174 and 175:
to properly manage and structure it
Page 176 and 177:
While express disclaimers of warran
Page 178 and 179:
Each question bears on the degree t
Page 180 and 181:
ights to the discovery, indemnify t
Page 182 and 183:
2. Licensing of Discoveries Through
Page 184 and 185:
To a substantial degree, the partic
Page 186 and 187:
Institutional risk control: High. I
Page 188 and 189:
Implementation Innovation Through T
Page 190 and 191:
evealing. When categorized into eig
Page 192 and 193:
egin development in Fall of '92. Th
Page 194 and 195:
Mission Implemrentation of Innovati
Page 196 and 197:
Sampling of Products Active Task Fo
Page 198 and 199:
Typical Company Product Catalog c P
Page 200 and 201:
Cil Education Program Pilot Short C
Page 202 and 203:
10 May 1992 Technology Transfer and
Page 204 and 205:
The risk in trying something new ma
Page 206 and 207:
existence of the technology, its ap
Page 208 and 209:
development effort. Developing inno
Page 210 and 211:
among potential users, 2) provide i
Page 212 and 213:
Jeffrey J. Walaszek USACERL, Public
Page 214 and 215:
"O&M Chiefs" fto,, Page i meeting o
Page 216 and 217:
Technical Reports - Videos, cont'd
Page 218 and 219:
Fort Harrison Expects Quick Payback
Page 220 and 221:
Test Water Quality at Minimal Cost
Page 222 and 223:
Noise Monitor Helps Installations R
Page 224 and 225:
Trenchless Pipe Replacement PIM: Th
Page 226 and 227:
PRR-4 Geotextile Applications PRR-1
Page 228 and 229:
After addressing these initial matt
Page 230 and 231:
Concluding thoughts The chairman as
Page 232 and 233:
The APWA has been very successful i
Page 234 and 235:
challenge these constraints for jus
Page 236 and 237:
Group C: Enhancing Technology Trans
Page 238 and 239:
A national catalyst must not be a b
Page 240 and 241:
WORKSHOP AGENDA Tuesday March 3. 19
Page 242 and 243:
Summary of Session C & Group Discus
Page 244 and 245:
infrastructure. He also asserts tha
Page 246 and 247:
alternatives available for funding
Page 248 and 249:
BIOGRAPHICAL SKETCHES APPENDIX C Ar
Page 250 and 251:
Publications include: "The Manageme
Page 252 and 253:
concrete beams. From the American C
Page 254 and 255:
William D. Michalerya William Micha
Page 256 and 257:
Mr. Schilling graduated in 1963 as
Page 258 and 259:
Dr. Walton has been involved in res
Page 260 and 261:
REPORT DOCUMENTATION PAGE 1p Pubkc
show all

Challenges and Opportunities for Innovation in the Public Works ...

Create successful ePaper yourself

Delete template?

Save as template?