The Y2K response team needs to be able to quickly assess the size and scope of the problem. With this access, the team can work to pinpoint the source of the problem. If direct access to critical systems is not possible, the team should know the appropriate technical contact for them. In many organizations, system monitors and logs have been established to serve as early warnings of application and network problems. The Y2K response team should also have access to these monitors and logs.
Some monitors observe the performance of applications and jobs running on each platform.
With system monitors, system logs, and other tools, problem determination and resolution will be more prompt. Documentation is another key component needed to create an effective response to Y2K issues. The team needs to be aware of all Y2K changes and of areas where changes were not made. The method of problem solving will differ depending upon whether an application has or does not have Y2K corrections. Documentation should not be limited to application changes.