RSA 21-R Department of Information Technology
Write the words of this act the way you think they should read. Solon shows your change as a redline against the published text and pins it to that exact text, so it can never be applied to wording you did not see.
Change 1
21-R:11 Use of Technology Solutions by State Agencies.
I. For all technology acquisitions, each state agency, in consultation with the department of information technology, shall: (a) Consider whether technology solutions containing proprietary or open source software offer the most cost effective solution for the agency, based on consideration of all associated acquisition, support, maintenance, and training costs; (b) Except as provided in subparagraphs (d) and (e), acquire technology solutions primarily on a value-for-money basis, based on consideration of the cost factors as described in subparagraph (a); (c) Provide a brief analysis of the purchase decision, including consideration of the cost factors in subparagraph (a), to the chief information officer; (d) Avoid the acquisition of products that do not comply with open standards for interoperability or data storage; and (e) Avoid the acquisition of products that are known to make unauthorized transfers of information to, or permit unauthorized control of or modification of a state agency's computer. II. All state procurement documents related to technology acquisitions shall include language that requires adherence to this section. Source. 2012, 5:2, eff. May 11, 2012. 2012, 265:8, eff. June 18, 2012. 2013, 118:8, eff. June 25, 2013. 2018, 81:4, eff. May 25, 2018. 2022, 44:1, eff. July 2, 2022.
21-R:11 Use of Technology Solutions by State Agencies.
I. For all technology acquisitions, each state agency, in consultation with the department of information technology, shall: (a) Consider whether technology solutions containing proprietary or open source software offer the most cost effective solution for the agency, based on consideration of all associated acquisition, support, maintenance, and training costs; (b) Except as provided in subparagraphs (d) and (e), acquire technology solutions primarily on a value-for-money basis, based on consideration of the cost factors as described in subparagraph (a); (c) Provide a brief analysis of the purchase decision, including consideration of the cost factors in subparagraph (a), to the chief information officer; (d) Avoid the acquisition of products that do not comply with open standards for interoperability or data storage; and (e) Avoid the acquisition of products that are known to make unauthorized transfers of information to, or permit unauthorized control of or modification of a state agency's computer. II. All state procurement documents related to technology acquisitions shall include language that requires adherence to this section. Source. 2012, 5:2, eff. May 11, 2012. 2012, 265:8, eff. June 18, 2012. 2013, 118:8, eff. June 25, 2013. 2018, 81:4, eff. May 25, 2018. 2022, 44:1, eff. July 2, 2022.
One line that says what changes, such as "Halve the dog tax".
Who it helps, what it costs, what it fixes. It is what persuades people to support it.
A proposal here is not law. Support on Solon is evidence that people want the change; the official route says what it takes to make it law.
Sign in to file your proposal. What you have written stays on this page.
Sign in to file itThink it through
Ask what your change would do, who would gain and who would bear a cost, and where something like it is already law. The assistant reads your draft as it stands, cites the law and the studies it finds, and takes no side. What you file stays yours.