These established contracts were specifically designed to capture at least 80% of DOI’s technical requirements, taking into account that some bureaus and office hardware requirements may fall outside this range. In these particular instances, DOI bureaus and offices may choose to utilize the existing waiver process.
Procedures
The process, supported by the DOI’s Chief Technology Officers (CTOs) Council, calls for the bureau Chief Information Officers (CIOs) to review waiver requests for hardware purchases outside the mandatory-for-use ID/IQ to support bureau-unique missions and programs, and make final decisions whether to accept or reject specific requests. These waivers must be kept on file with each bureau. For hardware deemed out of scope for the bureau, in order to support DOI-wide initiatives, the bureau CIOs need to forward the waiver requests to the DOI Chief Technology Officer who will present them to the CTO Council for final vote. Upon receiving the final vote results, the DOI CTO will make a recommendation to the DOI CIO who will have the final authority whether to reject or accept the bureau’s waiver request. This process will be reexamined and modified as needed in updated versions of the DOI’s Enterprise Architecture Technical Reference Model.
(source: Memo from DOI CIO in November 2005)
Waiver Process
Instructions for the waiver process are part of the Technical Reference Model (TRM) which can be found on the CTO Council (CTOC) website in the TRM section:
That link is only available from within DOI networks (no public Internet access).
For details on your Bureau or Office's Waiver procedure, contact your HAT Team representative.
Note: if you purchase off contract, you must ensure you comply with all items cited on the compliance page. Items purchased with micro-purchase cards are also required to meet all the requirements cited on the compliance page.