1 | 1 | | |
---|
2 | 2 | | |
---|
3 | 3 | | EXPLANATION: CAPITALS INDICATE MAT TER ADDED TO EXISTIN G LAW. |
---|
4 | 4 | | [Brackets] indicate matter deleted from existing law. |
---|
5 | 5 | | *sb0487* |
---|
6 | 6 | | |
---|
7 | 7 | | SENATE BILL 487 |
---|
8 | 8 | | P2 5lr2860 |
---|
9 | 9 | | SB 832/20 – EHE |
---|
10 | 10 | | By: Senators Jennings and Hester |
---|
11 | 11 | | Introduced and read first time: January 22, 2025 |
---|
12 | 12 | | Assigned to: Budget and Taxation |
---|
13 | 13 | | |
---|
14 | 14 | | A BILL ENTITLED |
---|
15 | 15 | | |
---|
16 | 16 | | AN ACT concerning 1 |
---|
17 | 17 | | |
---|
18 | 18 | | Procurement – Major Information Technology Development Projects 2 |
---|
19 | 19 | | |
---|
20 | 20 | | FOR the purpose of requiring the Secretary of Information Technology to conduct a certain 3 |
---|
21 | 21 | | risk assessment of certain major information technology development projects under 4 |
---|
22 | 22 | | certain circumstances; authorizing the Secretary to recommend an increase in a 5 |
---|
23 | 23 | | certain limitation of liability amount under certain circumstances; requiring the 6 |
---|
24 | 24 | | Chief Procurement Officer to review a certain recommendation; authorizing the 7 |
---|
25 | 25 | | Chief Procurement Officer to approve a certain change to a certain limitation of 8 |
---|
26 | 26 | | liability; requiring a procurement contract for a major information technology 9 |
---|
27 | 27 | | development project to include certain terms and conditions; requiring the Chief 10 |
---|
28 | 28 | | Procurement Officer and the Secretary to study certain procurement processes of 11 |
---|
29 | 29 | | major information technology development projects with certain stakeholders and 12 |
---|
30 | 30 | | make certain recommendations; and generally relating to procurement and major 13 |
---|
31 | 31 | | information technology development projects. 14 |
---|
32 | 32 | | |
---|
33 | 33 | | BY repealing and reenacting, without amendments, 15 |
---|
34 | 34 | | Article – State Finance and Procurement 16 |
---|
35 | 35 | | Section 3.5–301(a), (e), (h), and (k) 17 |
---|
36 | 36 | | Annotated Code of Maryland 18 |
---|
37 | 37 | | (2021 Replacement Volume and 2024 Supplement) 19 |
---|
38 | 38 | | |
---|
39 | 39 | | BY repealing and reenacting, with amendments, 20 |
---|
40 | 40 | | Article – State Finance and Procurement 21 |
---|
41 | 41 | | Section 3.5–308 and 3.5–309(n) 22 |
---|
42 | 42 | | Annotated Code of Maryland 23 |
---|
43 | 43 | | (2021 Replacement Volume and 2024 Supplement) 24 |
---|
44 | 44 | | |
---|
45 | 45 | | BY adding to 25 |
---|
46 | 46 | | Article – State Finance and Procurement 26 |
---|
47 | 47 | | Section 13–228 27 |
---|
48 | 48 | | Annotated Code of Maryland 28 2 SENATE BILL 487 |
---|
49 | 49 | | |
---|
50 | 50 | | |
---|
51 | 51 | | (2021 Replacement Volume and 2024 Supplement) 1 |
---|
52 | 52 | | |
---|
53 | 53 | | SECTION 1. BE IT ENACTED BY THE GENERAL ASSEMBLY OF MARYLAND, 2 |
---|
54 | 54 | | That the Laws of Maryland read as follows: 3 |
---|
55 | 55 | | |
---|
56 | 56 | | Article – State Finance and Procurement 4 |
---|
57 | 57 | | |
---|
58 | 58 | | 3.5–301. 5 |
---|
59 | 59 | | |
---|
60 | 60 | | (a) In this subtitle the following words have the meanings indicated. 6 |
---|
61 | 61 | | |
---|
62 | 62 | | (e) (1) “Development” means all expenditures for a new information 7 |
---|
63 | 63 | | technology system or an enhancement to an existing system including system: 8 |
---|
64 | 64 | | |
---|
65 | 65 | | (i) planning; 9 |
---|
66 | 66 | | |
---|
67 | 67 | | (ii) creation; 10 |
---|
68 | 68 | | |
---|
69 | 69 | | (iii) installation; 11 |
---|
70 | 70 | | |
---|
71 | 71 | | (iv) testing; and 12 |
---|
72 | 72 | | |
---|
73 | 73 | | (v) initial training. 13 |
---|
74 | 74 | | |
---|
75 | 75 | | (2) “Development” does not include: 14 |
---|
76 | 76 | | |
---|
77 | 77 | | (i) ongoing operating costs, software or hardware maintenance, 15 |
---|
78 | 78 | | routine upgrades, or modifications that merely allow for a continuation of the existing level 16 |
---|
79 | 79 | | of functionality; or 17 |
---|
80 | 80 | | |
---|
81 | 81 | | (ii) expenditures made after a new or enhanced system has been 18 |
---|
82 | 82 | | legally accepted by the user and is being used for the business process for which it was 19 |
---|
83 | 83 | | intended. 20 |
---|
84 | 84 | | |
---|
85 | 85 | | (h) “Information technology” means all electronic information processing, 21 |
---|
86 | 86 | | including: 22 |
---|
87 | 87 | | |
---|
88 | 88 | | (1) maintenance; 23 |
---|
89 | 89 | | |
---|
90 | 90 | | (2) networking; 24 |
---|
91 | 91 | | |
---|
92 | 92 | | (3) telecommunications; 25 |
---|
93 | 93 | | |
---|
94 | 94 | | (4) hardware; 26 |
---|
95 | 95 | | |
---|
96 | 96 | | (5) software and applications; and 27 |
---|
97 | 97 | | SENATE BILL 487 3 |
---|
98 | 98 | | |
---|
99 | 99 | | |
---|
100 | 100 | | (6) associated services. 1 |
---|
101 | 101 | | |
---|
102 | 102 | | (k) (1) “Major information technology development project” means any 2 |
---|
103 | 103 | | information technology development project that meets one or more of the following 3 |
---|
104 | 104 | | criteria: 4 |
---|
105 | 105 | | |
---|
106 | 106 | | (i) except as provided in paragraph (2) of this subsection, the 5 |
---|
107 | 107 | | estimated total cost of development equals or exceeds $5,000,000; 6 |
---|
108 | 108 | | |
---|
109 | 109 | | (ii) the project is undertaken to support a critical business function 7 |
---|
110 | 110 | | associated with the public health, education, safety, or financial well–being of the residents 8 |
---|
111 | 111 | | of Maryland; or 9 |
---|
112 | 112 | | |
---|
113 | 113 | | (iii) the Secretary determines that the project requires the special 10 |
---|
114 | 114 | | attention and consideration given to a major information technology development project 11 |
---|
115 | 115 | | due to: 12 |
---|
116 | 116 | | |
---|
117 | 117 | | 1. the significance of the project’s potential benefits or risks; 13 |
---|
118 | 118 | | |
---|
119 | 119 | | 2. the impact of the project on the public or local 14 |
---|
120 | 120 | | governments; 15 |
---|
121 | 121 | | |
---|
122 | 122 | | 3. the public visibility of the project; or 16 |
---|
123 | 123 | | |
---|
124 | 124 | | 4. other reasons as determined by the Secretary. 17 |
---|
125 | 125 | | |
---|
126 | 126 | | (2) “Major information technology development project” does not include: 18 |
---|
127 | 127 | | |
---|
128 | 128 | | (i) technology that is reoccurring, standard operating technology as 19 |
---|
129 | 129 | | determined by the Secretary and submitted to the Legislative Policy Committee for a 20 |
---|
130 | 130 | | 30–day review and comment period; or 21 |
---|
131 | 131 | | |
---|
132 | 132 | | (ii) a project with an estimated total cost of development that is: 22 |
---|
133 | 133 | | |
---|
134 | 134 | | 1. less than $5,000,000 and is funded with money set aside 23 |
---|
135 | 135 | | for expedited projects in the Fund; or 24 |
---|
136 | 136 | | |
---|
137 | 137 | | 2. more than $5,000,000 and is funded with the money set 25 |
---|
138 | 138 | | aside for expedited projects in the Fund if the Secretary determines that: 26 |
---|
139 | 139 | | |
---|
140 | 140 | | A. the unit of State government has sufficient 27 |
---|
141 | 141 | | implementation resources, including human capital, subject matter expertise, and 28 |
---|
142 | 142 | | technological infrastructure, or has the means to obtain these resources before project 29 |
---|
143 | 143 | | initiation; 30 |
---|
144 | 144 | | |
---|
145 | 145 | | B. there is no sufficient alternative within the State’s 31 |
---|
146 | 146 | | information technology inventory; and 32 4 SENATE BILL 487 |
---|
147 | 147 | | |
---|
148 | 148 | | |
---|
149 | 149 | | |
---|
150 | 150 | | C. the project will result in a comprehensive solution 1 |
---|
151 | 151 | | designed to meet a cohesive set of business and technological objectives. 2 |
---|
152 | 152 | | |
---|
153 | 153 | | 3.5–308. 3 |
---|
154 | 154 | | |
---|
155 | 155 | | (a) This section does not apply to a public institution of higher education. 4 |
---|
156 | 156 | | |
---|
157 | 157 | | (b) Before submitting its information technology project requests, a unit of State 5 |
---|
158 | 158 | | government shall submit information in support of the request required by the Secretary 6 |
---|
159 | 159 | | for review and determination consistent with § 3.5–301(k) of this subtitle. 7 |
---|
160 | 160 | | |
---|
161 | 161 | | (c) In reviewing information technology project requests, the Secretary may 8 |
---|
162 | 162 | | change a unit’s designation of a major information technology development project. 9 |
---|
163 | 163 | | |
---|
164 | 164 | | (d) (1) The Secretary shall review and, with the advice of the Secretary of 10 |
---|
165 | 165 | | Budget and Management, approve major information technology development projects and 11 |
---|
166 | 166 | | specifications for consistency with all statewide plans, policies, and standards, including a 12 |
---|
167 | 167 | | systems development life cycle plan. 13 |
---|
168 | 168 | | |
---|
169 | 169 | | (2) (I) IF, AFTER A REVIEW UNDER PARAGRAPH (1) OF THIS 14 |
---|
170 | 170 | | SUBSECTION, THE SECRETARY BELIEVES A MAJOR INFORMATION TE CHNOLOGY 15 |
---|
171 | 171 | | DEVELOPMENT PROJECT MAY PRESENT AN EXCEP TIONAL RISK TO THE STATE, THE 16 |
---|
172 | 172 | | SECRETARY SHALL CONDU CT A RISK ASSESSMENT PRIOR TO APPROVING T HE 17 |
---|
173 | 173 | | MAJOR INFORMATION TE CHNOLOGY DEVELOPMENT PROJECT. 18 |
---|
174 | 174 | | |
---|
175 | 175 | | (II) A RISK ASSESSMENT COND UCTED UNDER SUBPARAG RAPH 19 |
---|
176 | 176 | | (I) OF THIS PARAGRAPH SH ALL CONSIDER THE NAT URE, PROCESSING, AND USE OF 20 |
---|
177 | 177 | | SENSITIVE OR PERSONA LLY IDENTIFIABLE INF ORMATION. 21 |
---|
178 | 178 | | |
---|
179 | 179 | | (III) IF THE RISK ASSESSMEN T CONCLUDES THAT THE MAJOR 22 |
---|
180 | 180 | | INFORMATION TECHNOLO GY DEVELOPMENT PROJECT PRESE NTS AN EXCEPTIONAL 23 |
---|
181 | 181 | | RISK TO THE STATE AND THE LIMITAT ION OF LIABILITY AMO UNT PROVIDED UNDER 24 |
---|
182 | 182 | | § 13–228 OF THIS ARTICLE IS N OT ADEQUATE TO PROTE CT THE INTEREST OF T HE 25 |
---|
183 | 183 | | STATE, THE SECRETARY MAY RECOMME ND THE UNIT INCREASE THE LIMITATION OF 26 |
---|
184 | 184 | | LIABILITY AMOUNT . 27 |
---|
185 | 185 | | |
---|
186 | 186 | | (IV) A RECOMMENDATION MADE UNDER SUBPARAGRAPH (III) 28 |
---|
187 | 187 | | OF THIS PARAGRAPH SH ALL: 29 |
---|
188 | 188 | | |
---|
189 | 189 | | 1. BE IN WRITING; 30 |
---|
190 | 190 | | |
---|
191 | 191 | | 2. DESCRIBE THE RISKS T O THE STATE; 31 |
---|
192 | 192 | | |
---|
193 | 193 | | 3. EXPLAIN THE REASONS THAT THE LIMITATIONS 32 SENATE BILL 487 5 |
---|
194 | 194 | | |
---|
195 | 195 | | |
---|
196 | 196 | | REQUIRED UNDER § 13–228 OF THIS ARTICLE ARE NOT ADEQUATE TO MITI GATE THE 1 |
---|
197 | 197 | | RISKS DESCRIBED ; AND 2 |
---|
198 | 198 | | |
---|
199 | 199 | | 4. RECOMMEND A REASONAB LE MAXIMUM 3 |
---|
200 | 200 | | ALTERNATIVE LIMITATI ON OF LIABILITY AMOU NT, CALCULATED AS A MULT IPLE OF 4 |
---|
201 | 201 | | THE CONTRACT VALUE . 5 |
---|
202 | 202 | | |
---|
203 | 203 | | (3) THE CHIEF PROCUREMENT OFFICER: 6 |
---|
204 | 204 | | |
---|
205 | 205 | | (I) SHALL REVIEW A RECOM MENDATIO N MADE UNDER 7 |
---|
206 | 206 | | PARAGRAPH (2) OF THIS SUBSECTION ; AND 8 |
---|
207 | 207 | | |
---|
208 | 208 | | (II) MAY APPROVE A CHANGE TO THE LIMITATION OF LIABILITY 9 |
---|
209 | 209 | | REQUIRED UNDER § 13–228 OF THIS ARTICLE. 10 |
---|
210 | 210 | | |
---|
211 | 211 | | (e) The Secretary shall be responsible for overseeing the implementation of major 11 |
---|
212 | 212 | | information technology development projects, regardless of fund source. 12 |
---|
213 | 213 | | |
---|
214 | 214 | | (f) (1) With the advice of the Secretary of Budget and Management, 13 |
---|
215 | 215 | | expenditures for major information technology development projects shall be subject to the 14 |
---|
216 | 216 | | approval of the Secretary who shall approve expenditures only when those projects are 15 |
---|
217 | 217 | | consistent with statewide plans, policies, and standards. 16 |
---|
218 | 218 | | |
---|
219 | 219 | | (2) The Secretary shall make a recommendation to the Secretary of Budget 17 |
---|
220 | 220 | | and Management that project funds, regardless of fund source, be withheld if: 18 |
---|
221 | 221 | | |
---|
222 | 222 | | (i) a unit of State government is not consistently reporting on the 19 |
---|
223 | 223 | | status of a project or projects to the Department in the form and manner required by the 20 |
---|
224 | 224 | | Department; or 21 |
---|
225 | 225 | | |
---|
226 | 226 | | (ii) the Department determines that project implementation issues 22 |
---|
227 | 227 | | exist, including project timeline delays, significant cost increases, vendor nonperformance, 23 |
---|
228 | 228 | | decreased agency capacity, or other issues that indicate issues of concern that could 24 |
---|
229 | 229 | | jeopardize successful implementation. 25 |
---|
230 | 230 | | |
---|
231 | 231 | | (g) (1) The Secretary shall approve funding for major information technology 26 |
---|
232 | 232 | | development projects, expedited projects, and other expenditures from the Fund only when: 27 |
---|
233 | 233 | | |
---|
234 | 234 | | (i) the major information technology development projects or the 28 |
---|
235 | 235 | | expedited projects are in compliance with statewide plans, policies, and standards, as 29 |
---|
236 | 236 | | determined by the Secretary; and 30 |
---|
237 | 237 | | |
---|
238 | 238 | | (ii) the major information technology development projects are 31 |
---|
239 | 239 | | supported by an approved systems development life cycle plan. 32 |
---|
240 | 240 | | 6 SENATE BILL 487 |
---|
241 | 241 | | |
---|
242 | 242 | | |
---|
243 | 243 | | (2) An approved systems development life cycle plan shall include 1 |
---|
244 | 244 | | submission of: 2 |
---|
245 | 245 | | |
---|
246 | 246 | | (i) a project planning request that details initial planning for the 3 |
---|
247 | 247 | | project, including: 4 |
---|
248 | 248 | | |
---|
249 | 249 | | 1. the project title, appropriation code, and summary; 5 |
---|
250 | 250 | | |
---|
251 | 251 | | 2. a description of: 6 |
---|
252 | 252 | | |
---|
253 | 253 | | A. the business and technology outcomes to be achieved by 7 |
---|
254 | 254 | | the project; 8 |
---|
255 | 255 | | |
---|
256 | 256 | | B. the features available to the end user on completion, 9 |
---|
257 | 257 | | including user acceptance testing and accessibility plans; 10 |
---|
258 | 258 | | |
---|
259 | 259 | | C. the potential risks associated with the project; 11 |
---|
260 | 260 | | |
---|
261 | 261 | | D. possible alternatives; and 12 |
---|
262 | 262 | | |
---|
263 | 263 | | E. the scope and complexity of the project; and 13 |
---|
264 | 264 | | |
---|
265 | 265 | | 3. an estimate of: 14 |
---|
266 | 266 | | |
---|
267 | 267 | | A. the total costs required to complete through planning; and 15 |
---|
268 | 268 | | |
---|
269 | 269 | | B. the fund sources available to support planning costs; and 16 |
---|
270 | 270 | | |
---|
271 | 271 | | (ii) a project implementation request to begin full design, 17 |
---|
272 | 272 | | development, and implementation of the project after the completion of planning, including: 18 |
---|
273 | 273 | | |
---|
274 | 274 | | 1. the project title, appropriation code, and summary; 19 |
---|
275 | 275 | | |
---|
276 | 276 | | 2. a description of: 20 |
---|
277 | 277 | | |
---|
278 | 278 | | A. the business and technology outcomes to be achieved by 21 |
---|
279 | 279 | | the project and the metrics by which the success of those outcomes will be measured; 22 |
---|
280 | 280 | | |
---|
281 | 281 | | B. the features available to the end user on completion, 23 |
---|
282 | 282 | | including user acceptance testing and accessibility plans; 24 |
---|
283 | 283 | | |
---|
284 | 284 | | C. the potential risks associated with the project; 25 |
---|
285 | 285 | | |
---|
286 | 286 | | D. possible alternatives; 26 |
---|
287 | 287 | | |
---|
288 | 288 | | E. the scope and complexity of the project; and 27 |
---|
289 | 289 | | SENATE BILL 487 7 |
---|
290 | 290 | | |
---|
291 | 291 | | |
---|
292 | 292 | | F. how the project meets the goals of the statewide master 1 |
---|
293 | 293 | | plan; and 2 |
---|
294 | 294 | | |
---|
295 | 295 | | 3. an estimate of: 3 |
---|
296 | 296 | | |
---|
297 | 297 | | A. the total project cost, by phase; and 4 |
---|
298 | 298 | | |
---|
299 | 299 | | B. the fund sources to be utilized. 5 |
---|
300 | 300 | | |
---|
301 | 301 | | (3) The Secretary may approve funding incrementally, consistent with the 6 |
---|
302 | 302 | | systems development life cycle plan. 7 |
---|
303 | 303 | | |
---|
304 | 304 | | (h) The Department, in consultation with the Modernize Maryland Commission 8 |
---|
305 | 305 | | established under § 3.5–316 of this subtitle, shall: 9 |
---|
306 | 306 | | |
---|
307 | 307 | | (1) develop standards for units of State government to assist in identifying 10 |
---|
308 | 308 | | legacy systems that require modernization projects appropriate to be financed as an 11 |
---|
309 | 309 | | expedited project through the Fund; 12 |
---|
310 | 310 | | |
---|
311 | 311 | | (2) adopt an Information Technology Investment Maturity Model that 13 |
---|
312 | 312 | | includes: 14 |
---|
313 | 313 | | |
---|
314 | 314 | | (i) criteria to inform and prioritize investment decisions; 15 |
---|
315 | 315 | | |
---|
316 | 316 | | (ii) processes to develop the information required to evaluate 16 |
---|
317 | 317 | | investment proposals against the criteria under item (i) of this item; and 17 |
---|
318 | 318 | | |
---|
319 | 319 | | (iii) management processes to monitor the impl ementation of 18 |
---|
320 | 320 | | approved modernization projects; and 19 |
---|
321 | 321 | | |
---|
322 | 322 | | (3) develop a State Modernization Plan. 20 |
---|
323 | 323 | | |
---|
324 | 324 | | (I) IN THE ANNUAL REPORT SUBMITTED IN ACCORDA NCE WITH § 21 |
---|
325 | 325 | | 3.5–309(N) OF THIS SUBTITLE , BEGINNING WITH THE A NNUAL REPORT SUBMITT ED 22 |
---|
326 | 326 | | IN 2026, THE SECRETARY SHALL PU BLISH A LIST OF RECO MMENDATIONS MADE 23 |
---|
327 | 327 | | UNDER SUBSECTION (D)(2) OF THIS SECTION AND THE OUTCOME OF THE 24 |
---|
328 | 328 | | RECOMMENDATION REVIE W CONDUCTED UNDER SU BSECTION (D)(3) OF THIS 25 |
---|
329 | 329 | | SECTION DURING THE P RECEDING FISCAL YEAR . 26 |
---|
330 | 330 | | |
---|
331 | 331 | | 3.5–309. 27 |
---|
332 | 332 | | |
---|
333 | 333 | | (n) (1) On or before November 1 of each year, the Secretary shall report to the 28 |
---|
334 | 334 | | Governor and the Secretary of Budget and Management and, in accordance with § 2–1257 29 |
---|
335 | 335 | | of the State Government Article, to the Senate Budget and Taxation Committee, the Senate 30 |
---|
336 | 336 | | Committee on Education, Energy, and the Environment, the House Appropriations 31 8 SENATE BILL 487 |
---|
337 | 337 | | |
---|
338 | 338 | | |
---|
339 | 339 | | Committee, the House Health and Government Operations Committee, and the Joint 1 |
---|
340 | 340 | | Committee on Cybersecurity, Information Technology, and Biotechnology. 2 |
---|
341 | 341 | | |
---|
342 | 342 | | (2) The report shall include: 3 |
---|
343 | 343 | | |
---|
344 | 344 | | (i) the financial status of the Fund and a summary of its operations 4 |
---|
345 | 345 | | for the preceding fiscal year; 5 |
---|
346 | 346 | | |
---|
347 | 347 | | (ii) an accounting for the preceding fiscal year of all money from each 6 |
---|
348 | 348 | | of the revenue sources specified in subsection (e) of this section, including any expenditures 7 |
---|
349 | 349 | | made from the Fund; [and] 8 |
---|
350 | 350 | | |
---|
351 | 351 | | (iii) for each project receiving money from the Fund in the preceding 9 |
---|
352 | 352 | | fiscal year and for each major information technology development project or expedited 10 |
---|
353 | 353 | | project receiving funding from any source other than the Fund in the preceding fiscal year: 11 |
---|
354 | 354 | | |
---|
355 | 355 | | 1. the status of the project and project funding decisions; 12 |
---|
356 | 356 | | |
---|
357 | 357 | | 2. a comparison of estimated and actual costs of the project; 13 |
---|
358 | 358 | | |
---|
359 | 359 | | 3. any known or anticipated changes in scope or costs of the 14 |
---|
360 | 360 | | project; 15 |
---|
361 | 361 | | |
---|
362 | 362 | | 4. an evaluation of whether the project is using best 16 |
---|
363 | 363 | | practices; and 17 |
---|
364 | 364 | | |
---|
365 | 365 | | 5. a summary of any monitoring and oversight of the project 18 |
---|
366 | 366 | | from outside the agency in which the project is being developed, including a description of 19 |
---|
367 | 367 | | any problems identified by any external review and any corrective actions taken; AND 20 |
---|
368 | 368 | | |
---|
369 | 369 | | (IV) THE LIST OF RECOMMEN DATIONS AND REVIEW O UTCOMES 21 |
---|
370 | 370 | | REQUIRED UNDER § 3.5–308(I) OF THIS SUBTITLE . 22 |
---|
371 | 371 | | |
---|
372 | 372 | | 13–228. 23 |
---|
373 | 373 | | |
---|
374 | 374 | | (A) EXCEPT AS PROVIDED UN DER SUBSECTION (B) OF THIS SECTION AND § 24 |
---|
375 | 375 | | 3.5–308(D)(2)(III) OF THIS ARTICLE, EACH PROCUREMENT CONTRACT FOR A MAJOR 25 |
---|
376 | 376 | | INFORMATION TECHNOLO GY DEVELOPMENT PROJE CT SHALL INCLUDE TER MS AND 26 |
---|
377 | 377 | | CONDITIONS GOVERNING THE INDEMNIFICATION OBLIGATIONS AND LIMI TATION OF 27 |
---|
378 | 378 | | LIABILITY OF THE CON TRACTOR THAT ARE REASONABLE AND M AY NOT EXCEED IN 28 |
---|
379 | 379 | | AGGREGATE TWICE THE VALUE OF THE CONTRACT . 29 |
---|
380 | 380 | | |
---|
381 | 381 | | (B) A CONTRACT PROVISION A DOPTED IN ACCORDANCE WITH SUBSECTION 30 |
---|
382 | 382 | | (A) OF THIS SECTION MAY NOT LIMIT THE LIABIL ITY OF A CONTRACTOR FOR: 31 |
---|
383 | 383 | | SENATE BILL 487 9 |
---|
384 | 384 | | |
---|
385 | 385 | | |
---|
386 | 386 | | (1) INTENTIONAL OR WILLF UL MISCONDUCT , FRAUD, OR 1 |
---|
387 | 387 | | RECKLESSNESS OF THE CONTRACTOR OR AN EMP LOYEE OF THE CONTRACTOR ; OR 2 |
---|
388 | 388 | | |
---|
389 | 389 | | (2) CLAIMS FOR BODILY IN JURY, INCLUDING DEATH , AND DAMAGE TO 3 |
---|
390 | 390 | | REAL PROPERTY OR TAN GIBLE PERSONAL PROPE RTY RESULTING FROM T HE 4 |
---|
391 | 391 | | NEGLIGENCE OF THE CO NTRACTOR OR AN EMPLO YEE OF THE CONTRACTO R. 5 |
---|
392 | 392 | | |
---|
393 | 393 | | (C) NOTHING IN THIS SECTI ON PROHIBITS A UNIT FROM AGREEING TO A 6 |
---|
394 | 394 | | LIMITATION OF LIABIL ITY THAT IS LESS THA N TWICE THE VALUE OF THE CONTRACT . 7 |
---|
395 | 395 | | |
---|
396 | 396 | | SECTION 2. AND BE IT FURTHER ENACTED, That the Chief Procurement Officer 8 |
---|
397 | 397 | | in the Department of General Services and the Secretary of Information Technology shall: 9 |
---|
398 | 398 | | |
---|
399 | 399 | | (1) together with appropriate stakeholders, examine the procurement 10 |
---|
400 | 400 | | processes for major information technology development projects, including: 11 |
---|
401 | 401 | | |
---|
402 | 402 | | (i) the time frames for competitive sealed procurements for major 12 |
---|
403 | 403 | | information technology development projects, from issuing the request for proposal through 13 |
---|
404 | 404 | | evaluation and contract award; and 14 |
---|
405 | 405 | | |
---|
406 | 406 | | (ii) how the associated time frames impact the allocation of 15 |
---|
407 | 407 | | personnel within companies bidding on major information technology development 16 |
---|
408 | 408 | | projects; 17 |
---|
409 | 409 | | |
---|
410 | 410 | | (2) make recommendations on adjusting the procurement process and 18 |
---|
411 | 411 | | associated timeline for major information technology development projects to ensure 19 |
---|
412 | 412 | | personnel with required expertise are available to work on an awarded contract; and 20 |
---|
413 | 413 | | |
---|
414 | 414 | | (3) on or before December 1, 2026, report to the General Assembly, in 21 |
---|
415 | 415 | | accordance with § 2–1257 of the State Government Article, on the examination and 22 |
---|
416 | 416 | | recommendations conducted under this section. 23 |
---|
417 | 417 | | |
---|
418 | 418 | | SECTION 3. AND BE IT FURTHER ENACTED, That this Act shall take effect 24 |
---|
419 | 419 | | October 1, 2025. 25 |
---|