Reuse existing components before acquiring new ones


Reuse of existing environments is encouraged and technological diversity is controlled to minimize the non-trivial cost of maintaining and interconnecting multiple environments.


There are real infrastructure, support and maintenance costs associated with each technology or environment in use. There are further costs incurred to interconnect multiple environments and maintain those links. Limiting the number of supported components will simplify maintainability and reduce costs. The acquisition of developed or open source solutions allows the institution to benefit from already tested solutions incorporating industry leading practices and provides access to support services or communities.


  • Existing solutions should be examined before new environments are introduced. Commercial or open source offerings should be considered before deciding on in-house development.
  • Service oriented architecture will be favored to ensure reutilization of services and components.
  • Policies, standards, and procedures that govern the acquisition of technology must be tied directly to this principle.
  • Technology choices will be constrained by the choices available within the technology blueprint.
  • This principle doesn’t have the objective not freezing the technology baseline. Technology advances will be welcome and will be integrated in the technology blueprint when compatibility with the current infrastructure, improvement in operational efficiency, or a required capability has been demonstrated.
  • All technology acquisitions, including research and local departmental initiatives, should be reviewed to validate the possibility of reusing existing IT assets.
Back to top