CAUTION: READ FULL TEXT OF SECTION FOR SPECIAL NOTE

      (a)      (1)      A unit of State government may not purchase, lease, or rent information technology unless consistent with the statewide information technology master plan.

            (2)      A unit of State government other than a public institution of higher education may not make expenditures for major information technology development projects except as provided in § 3-410.1 of this subtitle.

      (b)      (1)      The Chief may review any information technology project for consistency with the statewide information technology master plan.

            (2)      Any information technology project selected for review may not be implemented without the approval of the Chief and the Secretary.

      (c)      (1)      A unit of State government shall advise the Chief of any information technology proposal involving resource sharing, the exchange of goods or services, or a gift, contribution, or grant of real or personal property.

            (2)      The Chief shall determine if the value of the resources, services, and property to be obtained by the State under the terms of any proposal submitted in accordance with the provisions of paragraph (1) of this subsection equals or exceeds $100,000.

            (3)      If the value of any proposal submitted in accordance with this subsection equals or exceeds $100,000 and the Secretary and unit agree to proceed with the proposal, information on the proposal shall be:

                  (i)      advertised for a period of at least 30 days in the "Contract Weekly", as published by the Office of the Secretary of State; and

                  (ii)      submitted, simultaneously with the advertisement, to the Legislative Policy Committee for a 60-day review and comment period, during which time the Committee may recommend that the proposal be treated as a procurement contract under Division II of this article.

            (4)      Following the period for review and comment by the Legislative Policy Committee under paragraph (3) of this subsection, the proposal is subject to approval by the Board of Public Works.

            (5)      This subsection may not be construed as authorizing an exception from the requirements of Division II of this article for any contract that otherwise would be subject to the State procurement process.

** SPECIAL NOTE: EFFECTIVE - JULY 1, 2006 - CHAPTER 515 - 2004 **

      (a)      (1)      A unit of State government may not purchase, lease, or rent information technology unless consistent with the statewide information technology master plan.

            (2)      A unit of State government other than a public institution of higher education may not make expenditures for major information technology development projects except as provided in § 3-410.1 of this subtitle.

      (b)      (1)      The Chief may review any information technology project for consistency with the statewide information technology master plan.

            (2)      Any information technology project selected for review may not be implemented without the approval of the Chief and the Secretary.

      (c)      (1)      A unit of State government shall advise the Chief of any information technology proposal involving resource sharing, the exchange of goods or services, or a gift, contribution, or grant of real or personal property.

            (2)      The Chief shall determine if the value of the resources, services, and property to be obtained by the State under the terms of any proposal submitted in accordance with the provisions of paragraph (1) of this subsection equals or exceeds $100,000.

            (3)      If the value of any proposal submitted in accordance with this subsection equals or exceeds $100,000 and the Secretary and unit agree to proceed with the proposal, information on the proposal shall be:

                  (i)      advertised for a period of at least 30 days in eMaryland Marketplace; and

                  (ii)      submitted, simultaneously with the advertisement, to the Legislative Policy Committee for a 60-day review and comment period, during which time the Committee may recommend that the proposal be treated as a procurement contract under Division II of this article.

            (4)      Following the period for review and comment by the Legislative Policy Committee under paragraph (3) of this subsection, the proposal is subject to approval by the Board of Public Works.

            (5)      This subsection may not be construed as authorizing an exception from the requirements of Division II of this article for any contract that otherwise would be subject to the State procurement process.