| 1 | 1 | | CALIFORNIA LEGISLATURE 20192020 REGULAR SESSION Assembly Bill No. 1587Introduced by Assembly Member ObernolteFebruary 22, 2019 An act to amend Section 13300.5 of the Government Code, relating to state government. LEGISLATIVE COUNSEL'S DIGESTAB 1587, as introduced, Obernolte. The Financial Information System for California: project office: report. The Financial Information System for California Act establishes the FISCal system, a single integrated financial management system for the state. The act establishes the Department of FISCal and the FISCal Project Office to exist concurrently during the phased implementation of the system and requires the department, upon full implementation and final acceptance of the system, to supersede the office and perform all administration, maintenance, and operation of the system. Existing law requires the office to annually report, until the completion of the system, as specified, an update on the project to the Legislature.This bill would expand the reporting requirements of the office to include specified information on state departments and agencies using FISCal, user service requests, unplanned outages, and the offices vacancy rates. Digest Key Vote: MAJORITY Appropriation: NO Fiscal Committee: YES Local Program: NO Bill TextThe people of the State of California do enact as follows:SECTION 1. Section 13300.5 of the Government Code is amended to read:13300.5. (a) The Legislature finds and declares that the system to modernize the states internal financial systems is a critical project that must be subject to the highest level of oversight. According to the Department of Technology, the size and scope of this modernization and automation effort make this project one of the highest risk projects undertaken by the state. Therefore, the Legislature must take steps to ensure it is fully informed as the project is implemented. It is the intent of the Legislature to adopt additional reporting requirements for the office to adequately manage risk and ensure the successful implementation of this effort.(b) The office shall report to the Legislature, on or before February 15 of each year, on all of the following:(1) An executive summary and overview of the systems status.(2) An overview of the systems history.(3) Significant events of the system within the current reporting period and a projection of events during the next reporting period.(4) A discussion of mitigation actions being taken by the office for any missed major milestones.(5) A comparison of actual to budgeted expenditures, and an explanation of variances and any planned corrective actions, including a summary of the system and staffing levels and an estimate of staff participation from partner agencies.(6) An articulation of expected functionality and qualitative benefits from the system that were achieved during the reporting period and that are expected to be achieved in the subsequent year.(7) An overview of change management activities and stakeholder engagement during the system implementation process, including a summary of departmental participation in the system.(8) A discussion of lessons learned and best practices that will be incorporated into future changes in management activities.(9) A description of any significant software customization, including a justification for why, if any, customization was granted.(10) Updates on the progress of meeting the systems objectives.(11) Whether each state department and agency produced a monthly financial statement and a description of the offices corrective actions for each state department and agency that did not produce a monthly financial statement or produced a monthly financial statement more than 30 days late.(12) The identity of any state department and agency that did not prepare a yearend financial statement using FISCal by the date requested by the Controller.(13) The number of user service requests by priority level, the number of user service requests successfully resolved, and the number of resolutions that took longer than the service level objectives defined by the project.(14) (A) The number and length of unplanned outages that occurred during normal business hours.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(15) The number of state departments and agencies that reported concerns with using FISCal to meet federal requirements and a description of the offices efforts to resolve those concerns.(16) (A) The offices vacancy rate for staff positions, including technical support center positions, and a description of the offices efforts to fill vacancies.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(17) The number of state departments and agencies that are operating a legacy financial management system, including the projected date each state department and agency will retire its legacy financial management system, and the volume of backlog transactions that each state department and agency still needs to input into FISCal.(c) Reports shall describe deviations to the project scope, cost, or schedule from Special Project Report 6.(d) This section shall remain operative until the completion of the system, as specified in paragraph (2) of subdivision (a) of Section 11890, and thereafter shall be inoperative.(e) The definitions in Section 11852 shall apply to the applicable terms in this section. |
|---|
| 2 | 2 | | |
|---|
| 3 | 3 | | CALIFORNIA LEGISLATURE 20192020 REGULAR SESSION Assembly Bill No. 1587Introduced by Assembly Member ObernolteFebruary 22, 2019 An act to amend Section 13300.5 of the Government Code, relating to state government. LEGISLATIVE COUNSEL'S DIGESTAB 1587, as introduced, Obernolte. The Financial Information System for California: project office: report. The Financial Information System for California Act establishes the FISCal system, a single integrated financial management system for the state. The act establishes the Department of FISCal and the FISCal Project Office to exist concurrently during the phased implementation of the system and requires the department, upon full implementation and final acceptance of the system, to supersede the office and perform all administration, maintenance, and operation of the system. Existing law requires the office to annually report, until the completion of the system, as specified, an update on the project to the Legislature.This bill would expand the reporting requirements of the office to include specified information on state departments and agencies using FISCal, user service requests, unplanned outages, and the offices vacancy rates. Digest Key Vote: MAJORITY Appropriation: NO Fiscal Committee: YES Local Program: NO |
|---|
| 4 | 4 | | |
|---|
| 5 | 5 | | |
|---|
| 6 | 6 | | |
|---|
| 7 | 7 | | |
|---|
| 8 | 8 | | |
|---|
| 9 | 9 | | CALIFORNIA LEGISLATURE 20192020 REGULAR SESSION |
|---|
| 10 | 10 | | |
|---|
| 11 | 11 | | Assembly Bill No. 1587 |
|---|
| 12 | 12 | | |
|---|
| 13 | 13 | | Introduced by Assembly Member ObernolteFebruary 22, 2019 |
|---|
| 14 | 14 | | |
|---|
| 15 | 15 | | Introduced by Assembly Member Obernolte |
|---|
| 16 | 16 | | February 22, 2019 |
|---|
| 17 | 17 | | |
|---|
| 18 | 18 | | An act to amend Section 13300.5 of the Government Code, relating to state government. |
|---|
| 19 | 19 | | |
|---|
| 20 | 20 | | LEGISLATIVE COUNSEL'S DIGEST |
|---|
| 21 | 21 | | |
|---|
| 22 | 22 | | ## LEGISLATIVE COUNSEL'S DIGEST |
|---|
| 23 | 23 | | |
|---|
| 24 | 24 | | AB 1587, as introduced, Obernolte. The Financial Information System for California: project office: report. |
|---|
| 25 | 25 | | |
|---|
| 26 | 26 | | The Financial Information System for California Act establishes the FISCal system, a single integrated financial management system for the state. The act establishes the Department of FISCal and the FISCal Project Office to exist concurrently during the phased implementation of the system and requires the department, upon full implementation and final acceptance of the system, to supersede the office and perform all administration, maintenance, and operation of the system. Existing law requires the office to annually report, until the completion of the system, as specified, an update on the project to the Legislature.This bill would expand the reporting requirements of the office to include specified information on state departments and agencies using FISCal, user service requests, unplanned outages, and the offices vacancy rates. |
|---|
| 27 | 27 | | |
|---|
| 28 | 28 | | The Financial Information System for California Act establishes the FISCal system, a single integrated financial management system for the state. The act establishes the Department of FISCal and the FISCal Project Office to exist concurrently during the phased implementation of the system and requires the department, upon full implementation and final acceptance of the system, to supersede the office and perform all administration, maintenance, and operation of the system. Existing law requires the office to annually report, until the completion of the system, as specified, an update on the project to the Legislature. |
|---|
| 29 | 29 | | |
|---|
| 30 | 30 | | This bill would expand the reporting requirements of the office to include specified information on state departments and agencies using FISCal, user service requests, unplanned outages, and the offices vacancy rates. |
|---|
| 31 | 31 | | |
|---|
| 32 | 32 | | ## Digest Key |
|---|
| 33 | 33 | | |
|---|
| 34 | 34 | | ## Bill Text |
|---|
| 35 | 35 | | |
|---|
| 36 | 36 | | The people of the State of California do enact as follows:SECTION 1. Section 13300.5 of the Government Code is amended to read:13300.5. (a) The Legislature finds and declares that the system to modernize the states internal financial systems is a critical project that must be subject to the highest level of oversight. According to the Department of Technology, the size and scope of this modernization and automation effort make this project one of the highest risk projects undertaken by the state. Therefore, the Legislature must take steps to ensure it is fully informed as the project is implemented. It is the intent of the Legislature to adopt additional reporting requirements for the office to adequately manage risk and ensure the successful implementation of this effort.(b) The office shall report to the Legislature, on or before February 15 of each year, on all of the following:(1) An executive summary and overview of the systems status.(2) An overview of the systems history.(3) Significant events of the system within the current reporting period and a projection of events during the next reporting period.(4) A discussion of mitigation actions being taken by the office for any missed major milestones.(5) A comparison of actual to budgeted expenditures, and an explanation of variances and any planned corrective actions, including a summary of the system and staffing levels and an estimate of staff participation from partner agencies.(6) An articulation of expected functionality and qualitative benefits from the system that were achieved during the reporting period and that are expected to be achieved in the subsequent year.(7) An overview of change management activities and stakeholder engagement during the system implementation process, including a summary of departmental participation in the system.(8) A discussion of lessons learned and best practices that will be incorporated into future changes in management activities.(9) A description of any significant software customization, including a justification for why, if any, customization was granted.(10) Updates on the progress of meeting the systems objectives.(11) Whether each state department and agency produced a monthly financial statement and a description of the offices corrective actions for each state department and agency that did not produce a monthly financial statement or produced a monthly financial statement more than 30 days late.(12) The identity of any state department and agency that did not prepare a yearend financial statement using FISCal by the date requested by the Controller.(13) The number of user service requests by priority level, the number of user service requests successfully resolved, and the number of resolutions that took longer than the service level objectives defined by the project.(14) (A) The number and length of unplanned outages that occurred during normal business hours.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(15) The number of state departments and agencies that reported concerns with using FISCal to meet federal requirements and a description of the offices efforts to resolve those concerns.(16) (A) The offices vacancy rate for staff positions, including technical support center positions, and a description of the offices efforts to fill vacancies.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(17) The number of state departments and agencies that are operating a legacy financial management system, including the projected date each state department and agency will retire its legacy financial management system, and the volume of backlog transactions that each state department and agency still needs to input into FISCal.(c) Reports shall describe deviations to the project scope, cost, or schedule from Special Project Report 6.(d) This section shall remain operative until the completion of the system, as specified in paragraph (2) of subdivision (a) of Section 11890, and thereafter shall be inoperative.(e) The definitions in Section 11852 shall apply to the applicable terms in this section. |
|---|
| 37 | 37 | | |
|---|
| 38 | 38 | | The people of the State of California do enact as follows: |
|---|
| 39 | 39 | | |
|---|
| 40 | 40 | | ## The people of the State of California do enact as follows: |
|---|
| 41 | 41 | | |
|---|
| 42 | 42 | | SECTION 1. Section 13300.5 of the Government Code is amended to read:13300.5. (a) The Legislature finds and declares that the system to modernize the states internal financial systems is a critical project that must be subject to the highest level of oversight. According to the Department of Technology, the size and scope of this modernization and automation effort make this project one of the highest risk projects undertaken by the state. Therefore, the Legislature must take steps to ensure it is fully informed as the project is implemented. It is the intent of the Legislature to adopt additional reporting requirements for the office to adequately manage risk and ensure the successful implementation of this effort.(b) The office shall report to the Legislature, on or before February 15 of each year, on all of the following:(1) An executive summary and overview of the systems status.(2) An overview of the systems history.(3) Significant events of the system within the current reporting period and a projection of events during the next reporting period.(4) A discussion of mitigation actions being taken by the office for any missed major milestones.(5) A comparison of actual to budgeted expenditures, and an explanation of variances and any planned corrective actions, including a summary of the system and staffing levels and an estimate of staff participation from partner agencies.(6) An articulation of expected functionality and qualitative benefits from the system that were achieved during the reporting period and that are expected to be achieved in the subsequent year.(7) An overview of change management activities and stakeholder engagement during the system implementation process, including a summary of departmental participation in the system.(8) A discussion of lessons learned and best practices that will be incorporated into future changes in management activities.(9) A description of any significant software customization, including a justification for why, if any, customization was granted.(10) Updates on the progress of meeting the systems objectives.(11) Whether each state department and agency produced a monthly financial statement and a description of the offices corrective actions for each state department and agency that did not produce a monthly financial statement or produced a monthly financial statement more than 30 days late.(12) The identity of any state department and agency that did not prepare a yearend financial statement using FISCal by the date requested by the Controller.(13) The number of user service requests by priority level, the number of user service requests successfully resolved, and the number of resolutions that took longer than the service level objectives defined by the project.(14) (A) The number and length of unplanned outages that occurred during normal business hours.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(15) The number of state departments and agencies that reported concerns with using FISCal to meet federal requirements and a description of the offices efforts to resolve those concerns.(16) (A) The offices vacancy rate for staff positions, including technical support center positions, and a description of the offices efforts to fill vacancies.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(17) The number of state departments and agencies that are operating a legacy financial management system, including the projected date each state department and agency will retire its legacy financial management system, and the volume of backlog transactions that each state department and agency still needs to input into FISCal.(c) Reports shall describe deviations to the project scope, cost, or schedule from Special Project Report 6.(d) This section shall remain operative until the completion of the system, as specified in paragraph (2) of subdivision (a) of Section 11890, and thereafter shall be inoperative.(e) The definitions in Section 11852 shall apply to the applicable terms in this section. |
|---|
| 43 | 43 | | |
|---|
| 44 | 44 | | SECTION 1. Section 13300.5 of the Government Code is amended to read: |
|---|
| 45 | 45 | | |
|---|
| 46 | 46 | | ### SECTION 1. |
|---|
| 47 | 47 | | |
|---|
| 48 | 48 | | 13300.5. (a) The Legislature finds and declares that the system to modernize the states internal financial systems is a critical project that must be subject to the highest level of oversight. According to the Department of Technology, the size and scope of this modernization and automation effort make this project one of the highest risk projects undertaken by the state. Therefore, the Legislature must take steps to ensure it is fully informed as the project is implemented. It is the intent of the Legislature to adopt additional reporting requirements for the office to adequately manage risk and ensure the successful implementation of this effort.(b) The office shall report to the Legislature, on or before February 15 of each year, on all of the following:(1) An executive summary and overview of the systems status.(2) An overview of the systems history.(3) Significant events of the system within the current reporting period and a projection of events during the next reporting period.(4) A discussion of mitigation actions being taken by the office for any missed major milestones.(5) A comparison of actual to budgeted expenditures, and an explanation of variances and any planned corrective actions, including a summary of the system and staffing levels and an estimate of staff participation from partner agencies.(6) An articulation of expected functionality and qualitative benefits from the system that were achieved during the reporting period and that are expected to be achieved in the subsequent year.(7) An overview of change management activities and stakeholder engagement during the system implementation process, including a summary of departmental participation in the system.(8) A discussion of lessons learned and best practices that will be incorporated into future changes in management activities.(9) A description of any significant software customization, including a justification for why, if any, customization was granted.(10) Updates on the progress of meeting the systems objectives.(11) Whether each state department and agency produced a monthly financial statement and a description of the offices corrective actions for each state department and agency that did not produce a monthly financial statement or produced a monthly financial statement more than 30 days late.(12) The identity of any state department and agency that did not prepare a yearend financial statement using FISCal by the date requested by the Controller.(13) The number of user service requests by priority level, the number of user service requests successfully resolved, and the number of resolutions that took longer than the service level objectives defined by the project.(14) (A) The number and length of unplanned outages that occurred during normal business hours.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(15) The number of state departments and agencies that reported concerns with using FISCal to meet federal requirements and a description of the offices efforts to resolve those concerns.(16) (A) The offices vacancy rate for staff positions, including technical support center positions, and a description of the offices efforts to fill vacancies.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(17) The number of state departments and agencies that are operating a legacy financial management system, including the projected date each state department and agency will retire its legacy financial management system, and the volume of backlog transactions that each state department and agency still needs to input into FISCal.(c) Reports shall describe deviations to the project scope, cost, or schedule from Special Project Report 6.(d) This section shall remain operative until the completion of the system, as specified in paragraph (2) of subdivision (a) of Section 11890, and thereafter shall be inoperative.(e) The definitions in Section 11852 shall apply to the applicable terms in this section. |
|---|
| 49 | 49 | | |
|---|
| 50 | 50 | | 13300.5. (a) The Legislature finds and declares that the system to modernize the states internal financial systems is a critical project that must be subject to the highest level of oversight. According to the Department of Technology, the size and scope of this modernization and automation effort make this project one of the highest risk projects undertaken by the state. Therefore, the Legislature must take steps to ensure it is fully informed as the project is implemented. It is the intent of the Legislature to adopt additional reporting requirements for the office to adequately manage risk and ensure the successful implementation of this effort.(b) The office shall report to the Legislature, on or before February 15 of each year, on all of the following:(1) An executive summary and overview of the systems status.(2) An overview of the systems history.(3) Significant events of the system within the current reporting period and a projection of events during the next reporting period.(4) A discussion of mitigation actions being taken by the office for any missed major milestones.(5) A comparison of actual to budgeted expenditures, and an explanation of variances and any planned corrective actions, including a summary of the system and staffing levels and an estimate of staff participation from partner agencies.(6) An articulation of expected functionality and qualitative benefits from the system that were achieved during the reporting period and that are expected to be achieved in the subsequent year.(7) An overview of change management activities and stakeholder engagement during the system implementation process, including a summary of departmental participation in the system.(8) A discussion of lessons learned and best practices that will be incorporated into future changes in management activities.(9) A description of any significant software customization, including a justification for why, if any, customization was granted.(10) Updates on the progress of meeting the systems objectives.(11) Whether each state department and agency produced a monthly financial statement and a description of the offices corrective actions for each state department and agency that did not produce a monthly financial statement or produced a monthly financial statement more than 30 days late.(12) The identity of any state department and agency that did not prepare a yearend financial statement using FISCal by the date requested by the Controller.(13) The number of user service requests by priority level, the number of user service requests successfully resolved, and the number of resolutions that took longer than the service level objectives defined by the project.(14) (A) The number and length of unplanned outages that occurred during normal business hours.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(15) The number of state departments and agencies that reported concerns with using FISCal to meet federal requirements and a description of the offices efforts to resolve those concerns.(16) (A) The offices vacancy rate for staff positions, including technical support center positions, and a description of the offices efforts to fill vacancies.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(17) The number of state departments and agencies that are operating a legacy financial management system, including the projected date each state department and agency will retire its legacy financial management system, and the volume of backlog transactions that each state department and agency still needs to input into FISCal.(c) Reports shall describe deviations to the project scope, cost, or schedule from Special Project Report 6.(d) This section shall remain operative until the completion of the system, as specified in paragraph (2) of subdivision (a) of Section 11890, and thereafter shall be inoperative.(e) The definitions in Section 11852 shall apply to the applicable terms in this section. |
|---|
| 51 | 51 | | |
|---|
| 52 | 52 | | 13300.5. (a) The Legislature finds and declares that the system to modernize the states internal financial systems is a critical project that must be subject to the highest level of oversight. According to the Department of Technology, the size and scope of this modernization and automation effort make this project one of the highest risk projects undertaken by the state. Therefore, the Legislature must take steps to ensure it is fully informed as the project is implemented. It is the intent of the Legislature to adopt additional reporting requirements for the office to adequately manage risk and ensure the successful implementation of this effort.(b) The office shall report to the Legislature, on or before February 15 of each year, on all of the following:(1) An executive summary and overview of the systems status.(2) An overview of the systems history.(3) Significant events of the system within the current reporting period and a projection of events during the next reporting period.(4) A discussion of mitigation actions being taken by the office for any missed major milestones.(5) A comparison of actual to budgeted expenditures, and an explanation of variances and any planned corrective actions, including a summary of the system and staffing levels and an estimate of staff participation from partner agencies.(6) An articulation of expected functionality and qualitative benefits from the system that were achieved during the reporting period and that are expected to be achieved in the subsequent year.(7) An overview of change management activities and stakeholder engagement during the system implementation process, including a summary of departmental participation in the system.(8) A discussion of lessons learned and best practices that will be incorporated into future changes in management activities.(9) A description of any significant software customization, including a justification for why, if any, customization was granted.(10) Updates on the progress of meeting the systems objectives.(11) Whether each state department and agency produced a monthly financial statement and a description of the offices corrective actions for each state department and agency that did not produce a monthly financial statement or produced a monthly financial statement more than 30 days late.(12) The identity of any state department and agency that did not prepare a yearend financial statement using FISCal by the date requested by the Controller.(13) The number of user service requests by priority level, the number of user service requests successfully resolved, and the number of resolutions that took longer than the service level objectives defined by the project.(14) (A) The number and length of unplanned outages that occurred during normal business hours.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(15) The number of state departments and agencies that reported concerns with using FISCal to meet federal requirements and a description of the offices efforts to resolve those concerns.(16) (A) The offices vacancy rate for staff positions, including technical support center positions, and a description of the offices efforts to fill vacancies.(B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period.(17) The number of state departments and agencies that are operating a legacy financial management system, including the projected date each state department and agency will retire its legacy financial management system, and the volume of backlog transactions that each state department and agency still needs to input into FISCal.(c) Reports shall describe deviations to the project scope, cost, or schedule from Special Project Report 6.(d) This section shall remain operative until the completion of the system, as specified in paragraph (2) of subdivision (a) of Section 11890, and thereafter shall be inoperative.(e) The definitions in Section 11852 shall apply to the applicable terms in this section. |
|---|
| 53 | 53 | | |
|---|
| 54 | 54 | | |
|---|
| 55 | 55 | | |
|---|
| 56 | 56 | | 13300.5. (a) The Legislature finds and declares that the system to modernize the states internal financial systems is a critical project that must be subject to the highest level of oversight. According to the Department of Technology, the size and scope of this modernization and automation effort make this project one of the highest risk projects undertaken by the state. Therefore, the Legislature must take steps to ensure it is fully informed as the project is implemented. It is the intent of the Legislature to adopt additional reporting requirements for the office to adequately manage risk and ensure the successful implementation of this effort. |
|---|
| 57 | 57 | | |
|---|
| 58 | 58 | | (b) The office shall report to the Legislature, on or before February 15 of each year, on all of the following: |
|---|
| 59 | 59 | | |
|---|
| 60 | 60 | | (1) An executive summary and overview of the systems status. |
|---|
| 61 | 61 | | |
|---|
| 62 | 62 | | (2) An overview of the systems history. |
|---|
| 63 | 63 | | |
|---|
| 64 | 64 | | (3) Significant events of the system within the current reporting period and a projection of events during the next reporting period. |
|---|
| 65 | 65 | | |
|---|
| 66 | 66 | | (4) A discussion of mitigation actions being taken by the office for any missed major milestones. |
|---|
| 67 | 67 | | |
|---|
| 68 | 68 | | (5) A comparison of actual to budgeted expenditures, and an explanation of variances and any planned corrective actions, including a summary of the system and staffing levels and an estimate of staff participation from partner agencies. |
|---|
| 69 | 69 | | |
|---|
| 70 | 70 | | (6) An articulation of expected functionality and qualitative benefits from the system that were achieved during the reporting period and that are expected to be achieved in the subsequent year. |
|---|
| 71 | 71 | | |
|---|
| 72 | 72 | | (7) An overview of change management activities and stakeholder engagement during the system implementation process, including a summary of departmental participation in the system. |
|---|
| 73 | 73 | | |
|---|
| 74 | 74 | | (8) A discussion of lessons learned and best practices that will be incorporated into future changes in management activities. |
|---|
| 75 | 75 | | |
|---|
| 76 | 76 | | (9) A description of any significant software customization, including a justification for why, if any, customization was granted. |
|---|
| 77 | 77 | | |
|---|
| 78 | 78 | | (10) Updates on the progress of meeting the systems objectives. |
|---|
| 79 | 79 | | |
|---|
| 80 | 80 | | (11) Whether each state department and agency produced a monthly financial statement and a description of the offices corrective actions for each state department and agency that did not produce a monthly financial statement or produced a monthly financial statement more than 30 days late. |
|---|
| 81 | 81 | | |
|---|
| 82 | 82 | | (12) The identity of any state department and agency that did not prepare a yearend financial statement using FISCal by the date requested by the Controller. |
|---|
| 83 | 83 | | |
|---|
| 84 | 84 | | (13) The number of user service requests by priority level, the number of user service requests successfully resolved, and the number of resolutions that took longer than the service level objectives defined by the project. |
|---|
| 85 | 85 | | |
|---|
| 86 | 86 | | (14) (A) The number and length of unplanned outages that occurred during normal business hours. |
|---|
| 87 | 87 | | |
|---|
| 88 | 88 | | (B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period. |
|---|
| 89 | 89 | | |
|---|
| 90 | 90 | | (15) The number of state departments and agencies that reported concerns with using FISCal to meet federal requirements and a description of the offices efforts to resolve those concerns. |
|---|
| 91 | 91 | | |
|---|
| 92 | 92 | | (16) (A) The offices vacancy rate for staff positions, including technical support center positions, and a description of the offices efforts to fill vacancies. |
|---|
| 93 | 93 | | |
|---|
| 94 | 94 | | (B) The first report containing the information required by subparagraph (A) shall include information dating back to July 2018. Each report thereafter shall include information for the relevant reporting period. |
|---|
| 95 | 95 | | |
|---|
| 96 | 96 | | (17) The number of state departments and agencies that are operating a legacy financial management system, including the projected date each state department and agency will retire its legacy financial management system, and the volume of backlog transactions that each state department and agency still needs to input into FISCal. |
|---|
| 97 | 97 | | |
|---|
| 98 | 98 | | (c) Reports shall describe deviations to the project scope, cost, or schedule from Special Project Report 6. |
|---|
| 99 | 99 | | |
|---|
| 100 | 100 | | (d) This section shall remain operative until the completion of the system, as specified in paragraph (2) of subdivision (a) of Section 11890, and thereafter shall be inoperative. |
|---|
| 101 | 101 | | |
|---|
| 102 | 102 | | (e) The definitions in Section 11852 shall apply to the applicable terms in this section. |
|---|