Y2K Strategy

Tactical steps to be taken to successfully tackle the Y2K issue.

Create AWARENESS about the issue among all the members of the organisation

• Means

  • Conduct quizzes.
  • Distribute information materials
  • Paste posters about Y2K in lobbies, coffee-lounges, etc.
  • Promotional material like caps, T-shirts may be distributed
  • Infromation repositories, Intranet pages shud be built.
  • Recognize contributers to the issue

• Benefits

  • Helps identify problem areas in each member's area of activity
  • Gsin commitment and support from all members of the organisation

Use suitable tools for collating and analysis of inputs.

Formulate an APPROACH taking the holistic view of all systems and processes with due consideration to constraints of time, resources and money

This is very important. A wrong step could prove fatal and could lead to a complete wreckage.

• Create a Year 2000 committee

  • Chief coordinator directly reporting to CIO/CTO & CEO
  • With members from business, technology and user groups.

• Wherever possible REPLACE legacy systems with Y2K-compliant, functionally rich, advance tech solutions

  • Migration to new system should be well in advance
  • Care and choice of new system is very important
  • Training of users to new system is necessary.

• If problem areas are too many, prioritize the key areas.

  • Ensure appropriate solution is in place for all critical areas.
  • Non-critical areas may be tackled at a later stage.

• Adopt appropriate standards

  • Date data internal storage.
  • Date handling routines
  • Keep documentation of any deviations.

• Outsource bulk of the activities

  • Choose a reliable, established vendor
  • Only non-key areas of systems should
  • Get a contract done with legal binding.

• Vital and sensitive parts of the systems should be handled by the internal IS dept.

  • To prevent security breach
  • Maintain customer data secrecy

Get into ACTION with all the vigour

This key to successfully tiding over the crisis.

• Select the vendor and outsource the activity.

  • Get a legal binding solution agreement done.
  • Ensure appropriate care is taken while chosing the vendor.

• Continously monitor the progress and keep the top management informed

  • Take appropriate action depending on the progress
  • Assess the strategy and make suitable changes.

• Develop contingency plans to mitigate risks

  • Buy a insurance policy in case of critical systems
  • Have fallback plans ready for all key areas.

• In case of mission critical systems, keep a legal counsel/firm to handle any litigation arising of the issue

  • Non-compliance of the vendor.
  • Litigations from your customers due to your process/system failure
  • Compensation to loss due to your counterparties system failure.

• Thorough testing of the changes

  • To ensure that system handles properly year 2000 and beyond.
  • Make sure no other problem arises due to the fixes.

• Implementation.

  • Get the user trained to new interfaces
  • Select a non-critical time much before year 2000.

This page construction began on Mar.09,1997
U R VISITOR NO. since the construction start date Feb.17th,1997.
Welcome to visit My Home Page

Member of 123Counters

You are visitor No since 15th Nov. 1997

---

You are visitor number since 15th Nov. 1997