Some Thoughts on the FGCS Project[*]

Rick Stevens
Argonne National Laboratory

next previous contents
lead in knowledge-based systems-an important new paradigm-with little Western 
response possible in the short term. 

This shakeup caused many government-sponsored projects to be created in the 
West (MCC, ECRC, Alvey, SICS), and even now we see the United States federal High 
Performance Computing and Communications project to have been influenced by the 
FGCS project. In this initiative government and industrial firms are teaming to de-
velop systems and software. 

Lessons Learned. 

What lessons have I learned from the FGCS project? 

1. Be aware that government-supported industrial consortia may not be able to 
   "read the market," particularly over the long term. This limitation probably 
   means that joint government-industry projects should be short term. 

2. Do not confuse basic research and advanced development (i.e., know what you are 
   doing, and don't confuse the evaluation criteria for the two). It is important that 
   funding agencies and the community know what type of project one is working 
   on and how that project will be evaluated. 

3. Expect negative results but hope for positive. Mid-course corrections are a good 
   thing. Assessing the direction and expecting that research may change direction 
   are key to keeping projects relevant to the goals and to changes in the "real 
   world." 

4. Ensure that the basic research infrastructure has stability, a strong sense of the 
   important core problems, flexibility, and an evaluation mechanism that can dis-
   tinguish between negative results and incompetence. 

5. Have vision. The vision is critical: people need a big dream to make it worthwhile 
   to get up in the morning. The most important role of a project leader is to focus 
   energy and attention on maintaining the vision and direction of large projects. 
   The vision has the power to unify a group and motivate them to work through 
   hard problems. "Make no small plans, for small plans have no power to stir men's 
   souls." 

Impact and Accomplishments of ICOT. 

I've been thinking about the impact and accomplishments of ICOT since my first 
interactions in 1988. I have included here a specific list of accomplishments of ICOT 
based on my discussions and experience during the past four years. 

+ Can one built a whole computing system based on logic programming and pro-
vide a useful tool for applications use?                         Answer: YES 


					- l03 -