Section 215.96, Florida Statutes 2003
215.96 Coordinating council and design and coordination staff.--
(1) The Chief Financial Officer, as chief fiscal officer of the state, shall establish a coordinating council to function on a continuing basis. The coordinating council shall review and recommend to the board solutions and policy alternatives to ensure coordination between functional owners of the various information subsystems described in ss. 215.90-215.96 to the extent necessary to unify all the subsystems into a financial management information system.
(2) The coordinating council shall consist of the Chief Financial Officer; the secretary of the Department of Management Services; the Attorney General; and the Director of Planning and Budgeting, Executive Office of the Governor, or their designees. The Chief Financial Officer, or his or her designee, shall be chair of the coordinating council, and the design and coordination staff shall provide administrative and clerical support to the council and the board. The design and coordination staff shall maintain the minutes of each meeting and shall make such minutes available to any interested person. The Auditor General, the State Courts Administrator, an executive officer of the Florida Association of State Agency Administrative Services Directors, and an executive officer of the Florida Association of State Budget Officers, or their designees, shall serve without voting rights as ex officio members on the coordinating council. The chair may call meetings of the coordinating council as often as necessary to transact business; however, the coordinating council shall meet at least once a year. Action of the coordinating council shall be by motion, duly made, seconded and passed by a majority of the coordinating council voting in the affirmative for approval of items that are to be recommended for approval to the Financial Management Information Board.
(3) The coordinating council, assisted by the design and coordination staff, shall have the following duties, powers, and responsibilities pertaining to the Florida Financial Management Information System:
(a) To conduct such studies and to establish committees, workgroups, and teams to develop recommendations for rules, policies, procedures, principles, and standards to the board as necessary to assist the board in its efforts to design, implement, and perpetuate a financial management information system, including, but not limited to, the establishment of common data codes, the development of integrated financial management policies that address the information and management needs of the functional owner subsystems, and the development of a strategic plan pursuant to the requirements set forth in s. 186.022. The coordinating council shall make available a copy of the approved plan in writing or through electronic means to each of the coordinating council members, the fiscal committees of the Legislature, and any interested person.
(b) To recommend to the board solutions, policy alternatives, and legislative budget request issues that will ensure a framework for the timely, positive, preplanned, and prescribed data transfer between information subsystems and to recommend to the board solutions, policy alternatives, and legislative budget request issues that ensure the availability of data and information that support state planning, policy development, management, evaluation, and performance monitoring.
(c) To report to the board all actions taken by the coordinating council for final action.
(d) To review the annual work plans of the functional owner information subsystems by October 1 of each year. The review shall be conducted to assess the status of the Florida Financial Management Information System and the functional owner subsystems in regard to the provisions of s. 215.91. The coordinating council, as part of the review process, may make recommendations for modifications to the functional owner information subsystems annual work plans.
1(4) The Financial Management Information Board, through the coordinating council, shall provide the necessary planning, implementation, and integration policies, coordination procedures, and reporting processes to facilitate the successful and efficient integration of the central administrative and financial management information systems, including the Florida Accounting Information Resource system (FLAIR), Cash Management System (CMS), and FLAIR/CMS replacement project, the payroll system in the Department of Financial Services, the Legislative Appropriations System/Planning and Budgeting Subsystem (LAS/PBS), the State Purchasing System (SPURS) and MyFlorida Marketplace project, the Cooperative Personnel Employment Subsystem (COPES) and the PeopleFirst Outsourcing project, and the State Unified Tax system (SUNTAX).
(a) To fulfill this role, the coordinating council shall establish an Enterprise Resource Planning Integration Task Force, which shall consist of the coordinating council members plus the Chief Information Officer in the State Technology Office and the Executive Director or designee in the Department of Revenue, who shall serve with voting rights on the task force. The nonvoting ex officio members of the coordinating council shall be nonvoting members of the task force.
(b) The task force shall be established by August 1, 2003, and shall remain in existence until the integration goals have been achieved among the FLAIR/CMS Replacement project, SPURS and MyFlorida Marketplace project, COPES and PeopleFirst project, payroll system, LAS/PBS, and SUNTAX system, or until June 30, 2005, whichever is later. The task force shall hold its initial meeting no later than September 1, 2003, and shall meet at the call of the chair or at least once every 60 days. In its initial meeting, task force members shall:
1. Adopt a task force charter that identifies major objectives, activities, milestones and deliverables, significant assumptions, and constraints on the task force functions and major stakeholder groups interested in the outcome of the task force.
2. Consider and adopt processes by which information will be collected and business process and technical integration issues will be raised for analysis and recommendation by the task force.
3. Elect a member to serve as vice chair. Any vacancy in the vice chair position shall be filled by similar election within 30 days after the date the vacancy is effective.
(c) The coordinating council shall provide administrative and technical support to the task force as is reasonably necessary for the task force to effectively and timely carry out its duties and responsibilities. The cost of providing such support may be paid from funds appropriated for the operation of the council or the FLAIR/CMS Replacement project. The task force also may contract for services to obtain specific expertise to analyze, facilitate, and formulate recommendations to address process and technical integration problems that need to be resolved.
(d) Using information and input from project teams and stakeholders responsible for the FLAIR/CMS Replacement project, SPURS and MyFlorida Marketplace project, COPES and PeopleFirst project, payroll system, LAS/PBS, and SUNTAX system, the responsibilities of the task force shall include, but not be limited to:
1. Identifying and documenting central administrative and financial management policies, procedures, and processes that need to be integrated and recommending steps for implementation.
2. Collecting information from the subsystem owners and project teams and developing and publishing a consolidated list of enterprise resource planning functional and technical integration requirements.
3. Publishing integration plans and timelines based on information collected from task force members.
4. Forming committees, workgroups, and teams as provided in subsection (3).
5. Developing recommendations for the Financial Management Information Board which clearly describe any business or technical problems that need to be addressed, the options for resolving the problem, and the recommended actions.
6. Developing and implementing plans for reporting status of integration efforts.
(e) The task force shall provide recommendations to the Financial Management Information Board for review and approval regarding the technical, procedural, policy, and process requirements and changes that are needed to successfully integrate, implement, and realize the benefits of the enterprise resource planning initiatives associated with the FLAIR/CMS Replacement project, SPURS and MyFlorida Marketplace project, COPES and PeopleFirst project, payroll system, LAS/PBS, and SUNTAX system. The first of these reports should be provided no later than October 3, 2003.
(f) The task force shall monitor, review, and evaluate the progress of the FLAIR/CMS Replacement project, SPURS and MyFlorida Marketplace project, COPES and PeopleFirst project, payroll system, LAS/PBS, and SUNTAX system, in implementing the process and technical integration requirements and changes approved by the Financial Management Information Board and in achieving the necessary integration among the central administrative and financial management information systems represented on the task force. The task force shall prepare and submit quarterly reports to the Executive Office of the Governor, the chairs of the Senate Appropriations Committee and the House Appropriations Committee, and the Financial Management Information Board. Each quarterly report shall identify and describe the technical, procedural, policy, and process requirements and changes proposed and adopted by the board and shall describe the status of the implementation of these integration efforts, identify any problems, issues, or risks that require executive-level action, and report actual costs related to the Enterprise Resource Planning Integration Task Force.
(g) By January 15, 2004, and annually thereafter, until it is disbanded, the Enterprise Resource Planning Integration Task Force shall report to the Financial Management Information Board, the Speaker of the House of Representatives, and the President of the Senate the results of the task force's monitoring, review, and evaluation of enterprise resource planning integration activities and requirements, and any recommendations for statutory changes to be considered by the Legislature.
(h) This subsection expires July 1, 2004.
History.--s. 1, ch. 80-45; s. 1, ch. 82-46; s. 9, ch. 83-92; s. 2, ch. 87-137; ss. 1, 2, 3, ch. 89-2; s. 5, ch. 91-429; s. 86, ch. 92-279; s. 55, ch. 92-326; s. 11, ch. 94-226; s. 1508, ch. 95-147; s. 25, ch. 97-286; s. 25, ch. 98-73; s. 85, ch. 99-2; s. 1, ch. 2001-61; s. 12, ch. 2003-6; s. 52, ch. 2003-399.
A. Section 52, ch. 2003-399, created subsection (4) "[i]n order to implement Specific Appropriation 2286AT of the 2003-2004 General Appropriations Act." Some proviso language relating to specific appropriation 2286AT was vetoed. See ch. 2003-397, the 2003-2004 General Appropriations Act.
B. Section 92, ch. 2003-399, provides that "[a] section of this act that implements a specific appropriation or specifically identified proviso language in the 2003-2004 General Appropriations Act is void if the specific appropriation or specifically identified proviso language is vetoed. A section of this act that implements more than one specific appropriation or more than one portion of specifically identified proviso language in the 2003-2004 General Appropriations Act is void if all the specific appropriations or portions of specifically identified proviso language are vetoed." Not all portions of specifically identified proviso language relating to the creation of subsection (4) were vetoed.