The concept of reengineering, as popularized by Champy and Hammer (1993), relies on ubiquitous access to corporate data. Also, reengineering focuses on how the processes of an organization can be modified, to capitalize on this ubiquitous data access, to be significantly more productive. These two features of their program, while often put to good use by corporate executives, have perplexed many information system managers who have tried to reap similar benefits by reengineering their information systems. The paper discusses architectural issues that arise from the reengineering process and what types of architectures survive this process in the most painless way.