Bill Text: CA AB1990 | 2015-2016 | Regular Session | Introduced

---

Bill Title: The Financial Information System for California (FISCal).

Spectrum: Partisan Bill (Republican 1-0)

Status: (Failed) 2016-11-30 - From committee without further action. [AB1990 Detail]

Download: California-2015-AB1990-Introduced.html

---

BILL NUMBER: AB 1990	INTRODUCED
	BILL TEXT


INTRODUCED BY   Assembly Member Jones

                        FEBRUARY 16, 2016

   An act to amend Section 13300.5 of the Government Code, relating
to state government.


	LEGISLATIVE COUNSEL'S DIGEST


   AB 1990, as introduced, Jones. The Financial Information System
for California (FISCal).
   The Financial Information System for California (FISCal) Act
establishes the FISCal system, a single integrated financial
management system for the state. The act establishes the FISCal
Service Center and the FISCal Project Office to exist concurrently
during the phased implementation of the FISCal system and requires
the FISCal Service Center, upon full implementation and final
acceptance of the FISCal system, to perform all maintenance and
operation of the FISCal system. Existing law requires the FISCal
Project Office to annually report, until a specified act is
completed, an update on the FISCal project to the Legislature and
makes findings and declarations in this regard.
   This will would expand the annual reporting requirements to
include, among other additional information, a discussion of any
changes in total projected quantitative benefits.
   Vote: majority. Appropriation: no. Fiscal committee: yes.
State-mandated local program: no.


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 project
of the FISCal Project to modernize the state's 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 FISCal
Project Office to adequately manage the project's risk and to ensure
the successful implementation of this effort.
   (b) The FISCal Project Office shall report to the Legislature, by
February 15 of each year, an update on the project. The report shall
include all of the following:
   (1) An executive summary and overview of the project's status.
   (2) An overview of the project's history.
   (3) Significant events of the project 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 project
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 FISCal project and staffing levels and an
estimate of staff participation from partner agencies.
   (6) An articulation of expected functionality and qualitative
benefits from the project that were achieved during the reporting
period and that are expected to be achieved in the subsequent year.

   (7) A comparison of actual and projected quantitative benefits
along with actual and projected costs, a discussion of any changes in
total projected quantitative benefits, and total quantitative
benefits achieved.  
   (7) 
    (8)  An overview of change management activities and
stakeholder engagement in the project, including a summary of
departmental participation in the FISCal  project. 
 project and the associated cost of department subject matter
expert staff.  
   (8) 
    (9)  A discussion of lessons learned and best practices
that will be incorporated into future changes in management
activities. 
   (9) 
    (10)  A description of any significant software 
customization,   customization and associated costs,
 including a justification for why, if any, customization was
granted. 
   (10) 
    (11)  Updates on the progress of meeting the project
objectives.
   (c) The initial report, due February 15, 2013, shall provide a
description of the approved project scope. Later reports shall
describe any later deviations to the project scope, cost, or
schedule.
   (d) The initial report shall also provide a summary of the project
history from Special Project Report 1 to Special Project Report 4,
inclusive.
   (e) This section shall remain in effect until a postimplementation
evaluation report has been approved by the Department of Technology.
The Department of Technology shall post a notice on its Internet Web
site when the report is approved.