reglab/statecodes huggingface dataset:
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-4 - FLORIDA STATEWIDE LAW ENFORCEMENT RADIO SYSTEM › Section 60FF-4.007 - Service and Maintenance Priorities

Current through Reg. 50, No. 138; July 16, 2024
(1)
				If traffic loading at a site causes queuing of calls such that the busy hour
				average waiting time per call exceeds 0.5 seconds, the Department, in
				consultation with the Contractor and system users, is authorized to take
				measures to restrict system use. Such measures shall include: disabling of
				individual calling and telephone interconnect calling; patching of talk groups;
				disabling of talk groups; disallowing the addition of radios to the system;
				limiting usage to essential traffic only; or partitioning of channels. These
				measures will be employed when public safety emergencies result in heavier than
				normal radio traffic in an area and priorities must be invoked to ensure that
				essential radio communications can be maintained.
(2) Local First Responders will be granted
				call priorities equivalent to those granted to State Law Enforcement Users. All
				other SLERS Partners shall have lower call priorities.
(3) In no case shall any SLERS Partner be
				granted a higher priority for traffic or provided a faster response for
				maintenance than required for JTF Agency Users of the Statewide Law Enforcement
				Radio System.
Rulemaking Authority
					 282.702(9) FS.
					 Law Implemented 282.709
					 FS.
New 5-11-08.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-5 - E911 BOARD › Section 60FF-5.001 - Requirements for Sworn Invoices and Cost Recovery Proposals Submitted by or on Behalf of Wireless Service Providers (Transferred)

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11. FS. Law Implemented
					 365.173(2)(d)
					 FS.
New 12-20-09, Transferred to
					 60FF1-5.001.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-5 - E911 BOARD › Section 60FF-5.002 - Rural County Grants (Transferred)

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11. FS. Law implemented
					 365.173(2)(g),
					 365.172(9)(a), (b),
					 (c)
					 FS.
New 12-7-08, Amended 10-19-09, 4-15-10, 10-27-10,
					 Transferred to 60FF1-5.002.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-5 - E911 BOARD › Section 60FF-5.003 - State Grant Programs (Transferred)

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11. FS. Law implemented
					 365.172(6)(a)3.b., 365.173(2)(i),
					 365.172(9)(a), (b),
					 (c)
					 FS.
New 12-7-08, Amended 10-27-10, Transferred to
					 60FF1-5.003.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-5 - E911 BOARD › Section 60FF-5.004 - Requirements for Fee Remittance Submitted by or on Behalf of Wireless and Non-Wireless Service Providers (Transferred)

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11.,
					 365.172(8) FS.
					 Law Implemented 365.172(8)
					 FS.
New 11-16-10, Transferred to
					 60FF1-5.004.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-5 - E911 BOARD › Section 60FF-5.005 - Emegency Grants (Transferred)

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11. FS. Law implemented
					 365.172(6)(a)3.b., 365.173(2)(g),
					 365.173(2)(i)
					 FS.
New 10-19-09, Amended 10-27-10, Transferred to
					 60FF1-5.005.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-5 - E911 BOARD › Section 60FF-5.006 - Requirements for County Carry Forward Funds and Excess Funding (Transferred)

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11. FS. Law implemented
					 365.173(2)(c)
					 FS.
New 10-6-09, Amended 10-27-10, Transferred to
					 60FF1-5.006.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-5 - E911 BOARD › Section 60FF-5.007 - Requirements for T1 and Primary Rate Interface Fee Remittance Submitted by or on Behalf of Non-wireless Service Providers (Transferred)

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11.,
					 365.172(8) FS.
					 Law Implemented 365.172(8)
					 FS.
New 10-27-10, Transferred to
					 60FF1-5.007.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-6 - STATE E911 PLAN › Section 60FF-6.001 - Purpose

Current through Reg. 50, No. 138; July 16, 2024
(1) The purpose of this rule chapter is to
				prescribe necessary rules for implementing, coordinating and maintaining a
				statewide emergency Enhanced 911 communication system. It also prescribes the
				necessary procedures to be followed by an entity of local government for
				implementation of the Florida Emergency Communications Number E911 State
				Plan.
(2) Definitions:
(a) "Automatic location identification" (ALI)
				- The capability of the E911 service which enables the automatic display of
				information that defines the approximate geographic location of the wireless
				telephone, or the location of the address of the wireline or VoIP telephones,
				used to place a 911 call.
(b)
				"Automatic number identification" (ANI) - The capability of the E911 service
				which enables the automatic display of the service number used to place a 911
				call.
(c) "Customer Premises
				Equipment" (CPE) including communications or terminal equipment located at a
				PSAP for 911 call processing and answering.
(d) "Enhanced 911" (E911) - A telephone
				system which includes network switching, data base and Public Safety Answering
				Point premise elements capable of providing automatic location identification
				data, selective routing, selective transfer, fixed transfer, and a call back
				number.
(e) "Master Street
				Addressing Guide" (MSAG) - The database of street names and number ranges used
				to define unique addresses recognized for public safety agencies response to
				911 calls.
(f) "Public Safety
				Answering Point" (PSAP) - A public safety agency answering point that receives
				incoming 911 calls for dispatching of appropriate public safety agencies to
				respond to the 911 calls.
1. "Primary PSAP" -
				An answering point that has 911 calls routed directly from an E911 control
				office, 911 selective router, or directly from the service providers.
2. "Secondary PSAP" - An answering point that
				receives 911 calls transferred from a primary PSAP for the purpose of handling
				public safety agency calls. A secondary PSAP receives transfers of the voice,
				ANI, and ALI data for 911 calls from primary PSAPs.
(g) "Teletypewriters" (TTY) - A
				telecommunications device for the deaf that permits typed telephone
				conversations with or between deaf, hard of hearing, or speech impaired
				people.
(h) "Uninterruptible Power
				Supply" (UPS) - A device designed to provide a continuing source of power
				without regard to the interruption or loss of commercial power.
(i) "Department" - The Department of
				Management Services (DMS).
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-6 - STATE E911 PLAN › Section 60FF-6.002 - County E911 Plan Compliance

Current through Reg. 50, No. 138; July 16, 2024
(1) Each County
				E911 plan shall include:
(a) System Summary
				including identification of all public safety agencies (law enforcement, fire
				protection, emergency medical, and rescue agencies), within the boundaries of
				the 911 system including PSAPs, government agencies, type of systems and
				service providers and any major distinguishing features.
(b) System Management including a brief
				description of how the system is presently being or will be managed.
(c) Agreements including briefly described
				agreements between PSAPs (inter-local agreements) and counties (regional
				agreements).
(d) System definition
				section defining each PSAP and its equipment compliance with the technical and
				operational standards in Rule 60FF-6.005, F.A.C., and shall include the number
				of answering positions, total staff and the number of incoming
				trunks.
(e) Call handling section
				defining how each PSAP handles calls intended for each emergency service agency
				within its jurisdiction.
(f) System
				serving area showing each PSAP, each central office area, central office
				overlap areas. This information will not be posted on the State E911 Web site
				with the County E911 plan.
(g) PSAP
				911 Trunk Network, a functional diagram, showing the routing of calls from the
				various central offices and other E911 circuits to the various PSAPs. This
				information will not be posted on the State E911 Web site with the County E911
				plan.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-6 - STATE E911 PLAN › Section 60FF-6.003 - Request for Certification of Compliance

Current through Reg. 50, No. 138; July 16, 2024
(1) A certification inspection will determine
				if the E911 systems operated or planned to be operated by entities of local
				government meets the minimum technical and operational standards in subsection
				60FF-6.002(1) and Rule 60FF-6.005, F.A.C., so that an established minimum
				standard of service is available to citizens within any given E911 serving
				area. Entities of local government shall coordinate closely with Department of
				Management Services' personnel in the development of their respective E911
				systems per Rule 60FF-6.002, F.A.C.
(2) A DMS representative will coordinate the
				scheduling of inspections with county 911 coordinators.
(3) Upon completion of the inspection, the
				statewide 911 coordinator will send to the county 911 coordinator a list of all
				PSAPs that have passed the inspection and or a list of all PSAPs that have
				deficiencies. Any deficiencies will be explained and if applicable, specific
				directions detailing how to correct deficiencies will be included. DMS will
				rely on the county 911 coordinator and PSAP supervisors to make the necessary
				corrections. Upon receipt of written correspondence from the county 911
				coordinator stating that corrections have been made, DMS will add the newly
				approved PSAP(s) to the list of certified PSAPs.
(4) PSAPs that pass the inspection of the
				minimum technical and operational standards in subsection 60FF-6.002(1) and
				Rule 60FF-6.005, F.A.C., will be certified as compliant with the State E911
				Plan pursuant to Section
				 365.171(10),
				F.S.
Rulemaking Authority
					 365.171(4) FS.
					 Law Implemented 365.171(4),
					 (10)
					 FS.
New 2-17-11.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF - Technology Program › Chapter 60FF-6 - STATE E911 PLAN › Section 60FF-6.005 - Florida Emergency Communications Number E911 State Plan Technical and Operations Rule

Current through Reg. 50, No. 138; July 16, 2024
(1) Public Safety
				Answering Point.
(a) Each 911 primary PSAP
				shall operate 24 hours a day, seven days a week.
(b) All primary PSAPs shall be staffed with
				an adequate number of answering positions to ensure that a minimum of 90
				percent of voice calls shall be answered within 10 seconds of call arrival at
				the PSAP and 20 seconds for Teletypewriter (TTY) calls. All secondary PSAPs
				shall also meet this standard.
(c)
				The county 911 coordinator must anticipate and consider increases in emergency
				call volume. A determination must be made as to whether the existing staff can
				handle an increased work load and still meet the technical standards in
				paragraph 60FF-6.005(1)(b), F.A.C. If not, additional call taker positions and
				staff must be added. It is the responsibility of the county 911 coordinator to
				evaluate the situation and take appropriate action to assure adequate staffing.
				Criteria shall include busy hour call volume, call length and telephone grade
				of service.
(d) For wireline 911
				calls, a minimum number of dedicated 911 lines shall be provided from the
				service provider's central office(s) to the 911 selective router and from that
				selective router to the 911 PSAP to supply a P.01 grade of service or better. A
				P.01 grade of service allows one busy signal in 100 attempted calls during the
				average busy hour. For wireline 911 calls, there shall be a minimum of two
				lines from each central office to the selective router and there shall be a
				minimum of two lines from the selective router to each PSAP.
(e) The agency shall take into account the
				estimated volume of calls that the remote agency will receive during the busy
				hour when determining the number of lines required.
(f) The county 911 coordinator shall analyze
				MIS and E911 traffic data and determine wireless call routing and act upon this
				information as necessary for congestion control management to the
				PSAP(s).
(g) The county 911
				coordinator shall work closely with PSAP managers, supervisors, public safety
				providers, and call takers to develop standard operation procedures for call
				handling and ADA compliance. Each PSAP shall review and update these call
				handling procedures regularly with the county 911 coordinator. Call takers
				shall have ready access to county and or agency 911 policy and procedure
				manuals.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.001 - Requirements for Sworn Invoices and Cost Recovery Proposals Submitted by or on Behalf of Wireless Service Providers (Repealed)

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11. FS. Law Implemented
					 365.173(2)(d)
					 FS.
New 12-20-09, Formerly 60FF-5.001, Repealed
					 10-1-23.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.002 - Rural County Grants

Current through Reg. 50, No. 138; July 16, 2024
The Rural County Grant program is a semi-annual grant program
				  provided for the purpose of assisting rural counties, as defined by Section
				   365.172(3)(bb),
				  F.S., with the installation and maintenance of 911 systems.
(1) Eligibility. Any Board of County
				Commissioners in the State of Florida, with a county population of fewer than
				75, 000 is eligible to apply. Two or more rural counties may apply for a joint
				grant, but each county must complete and submit an individual Form 6A "County
				E911 Fiscal Information."
(2)
				General conditions.
(a) Each rural county
				applying for rural county grant funds shall complete and submit W Form 1A, "911
				Rural County Grant Program Application, " revised 9/2023, which is incorporated
				herein by reference and which may be obtained from the E911 Board office at the
				following address:
http://www.flrules.org/Gateway/reference.asp?No=Ref-16516
or
State of Florida Emergency Communications Board
ATTN: 911 Communications Section
4030 Esplanade Way, Suite 135
Tallahassee, Florida 32399-0950
The applicant must provide the completed, signed Application
				  Form, and the related procurement documents. The grant application package must
				  be postmarked or delivered by hand or email to:
				  E911BoardElectronicGrantReports@dms.fl.gov on or before April 1 or October 1 of
				  each year, dependent on the spring or fall application period. If the due date
				  falls on a weekend or holiday, the due date will be the next business
				  day.
(b) Priorities for
				awarding of grants will be determined by the Board. Grant priorities may be
				adjusted by the Board and published with the grant application package three
				months prior to the application submission date. The grant priority list is
				available as an addendum with the grant application at the start of each grant
				cycle at the address shown in paragraph (2)(a), above.
(c) The amount and availability of funds in
				the Trust Fund for allocation each year is subject to an annual appropriation
				by the Legislature. The Board will adjust the funds awarded to a rural county
				based upon eligibility of requested items, published quotes, increased
				effectiveness of grant funds, minimum system requirements for performing the
				needed 911 function as specified in the State 911 plan, or documented factors
				provided in the grant application submission.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.0035 - Florida 911 Reporting Forms

Current through Reg. 50, No. 138; July 16, 2024
The following 911 forms are approved for use in grant and
				  financial reporting and can be obtained by mail from the State of Florida E911
				  Board, ATTN: Administrative Staff, 4030 Esplanade Way, Tallahassee, FL
				  32399-0950.
(1) The Budget Report
				(06/2021), which is incorporated herein by reference and available at
http://www.flrules.org/Gateway/reference.asp?No=Ref-13526
;
(2) The Quarterly Status Report (06/2023),
				which is incorporated herein by reference and available at
http://www.flrules.org/Gateway/reference.asp?No=Ref-15952
;
(3) The Change Request (06/2021), which is
				incorporated herein by reference and available at
http://www.flrules.org/Gateway/reference.asp?No=Ref-13528
;
(4) The Financial Reimbursement of
				Expenditures Report Form (06/2021), which is incorporated herein by reference
				and available at
http://www.flrules.org/Gateway/reference.asp?No=Ref-13530
.
(5) This rule shall be reviewed, and if
				necessary, repealed, modified, or renewed through the rulemaking process five
				years from the effective date.
Rulemaking Authority
					 365.172 (6)(a)11. FS. Law
					 implemented 365.172, 365.173
					 FS.
New 9-27-21, Amended
					 10-2-23.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.006 - Requirements for County Carry Forward Funds and Excess Funding

Current through Reg. 50, No. 138; July 16, 2024
(1) This rule implements the carry forward
				provision in Section  365.173(2)(d),
				F.S. All boards of county commissioners shall return funds not used by the
				county in accordance with this rule.
(2) General conditions: All counties shall
				provide financial information on the county fiscal year fee revenues received,
				the county fiscal year Emergency Communications expenditures and the carry
				forward amount for the county fiscal year. The information shall be provided on
				the E911 Board Form 6A, "County E911 Fiscal Information, " (revised 04/2020),
				which is incorporated herein by reference and may be obtained at
http://www.flrules.org/Gateway/reference.asp?No=Ref-12015
on the Florida E911 website at URL http://florida911.myflorida.com, or from the
				Emergency Communications Board office at the following address:
State of Florida Emergency Communications Board
Attn: Administrative Assistant
4030 Esplanade Way, Suite 135-F
Tallahassee, Florida 32399-0950
(3) Definitions.
(a) Fixed Capital Outlay: Real property
				(land, buildings, including appurtenances, fixtures and fixed equipment,
				structures, etc.), including additions, replacements, major repairs, and
				renovations to real property which materially extend its useful life or
				materially improve or change its functional use and including furniture and
				equipment necessary to furnish and operate a new or improved
				facility.
(b) Operating Capital
				Outlay: Equipment, fixtures and other tangible personal property of a
				non-consumable nature and has a normal expected life of one year or
				more.
(c) Capital Improvements:
				Improvement costs increasing the useful life or value of the asset. Capital
				improvements are accounted for as assets and do not include deductible minor
				improvements or repairs which are expenses. These items can include building
				modifications necessary to maintain the security and environmental integrity of
				the Public Safety Answering Point (PSAP) and E911 equipment rooms specifically
				listed in Section  365.172(10)(c),
				F.S.
(d) Equipment Replacement:
				Replacement of 911 equipment specifically listed in Section
				 365.172(10)(c),
				F.S., as allowable expenditures.
(e) "Implementation of a hosted system"
				includes costs associated with initial start-up and continuing provision of a
				hosted system that meets industry accepted standards.
(f) Services include systems and
				functionality such as database maintenance, next-generation 911 network
				services, next-generation 911 database services, the installation of network
				equipment or communication devices within the PSAP, and all other services that
				are provided remotely to a PSAP.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.007 - Requirements for T1 and Primary Rate Interface Fee Remittance Submitted by or on Behalf of Non-wireless Service Providers (Repealed)

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11.,
					 365.172(8) FS.
					 Law Implemented 365.172(8)
					 FS.
New 10-27-10, Formerly 60FF-5.007, Repealed
					 1-7-13.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.008 - Public Comment

Current through Reg. 50, No. 138; July 16, 2024
The Board invites and encourages all members of the public to
				  provide comment on matters or propositions before the Board or a committee of
				  the Board. The opportunity to provide comment shall be subject to the
				  following:
(1) Members of the public
				will be given an opportunity to provide comment on subject matters before the
				Board after an agenda item is introduced at a properly noticed board
				meeting.
(2) Members of the public
				shall be limited to five (5) minutes to provide comment. This time shall not
				include time spent by the presenter responding to questions posed by Board
				members, staff or board counsel. The chair of the Board may extend the time to
				provide comment if time permits.
(3) Members of the public shall notify board
				staff in writing of his or her interest to be heard on a proposition or matter
				before the Board. The notification shall identify the person or entity,
				indicate its support, opposition, or neutrality, and identify who will speak on
				behalf of a group or faction of persons.
Rulemaking Authority
					 286.0114 FS. Law Implemented
					 286.0114
					 FS.
New 1-26-14.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.010 - Fee Allocation

Current through Reg. 50, No. 138; July 16, 2024
Rulemaking Authority 365.172(6)(a)11. FS. Law implemented
					 365.172(6)(a)3.e., 365.172(8)(g),
					 365.173(2)(a), (e), (f),
					 (g)
					 FS.
New 1-3-19, Amended 10-12-21,
					 10-1-23.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.011 - Text to 911

Current through Reg. 50, No. 138; July 16, 2024
(1) Counties may
				request funding for "Text to 911" by completing and submitting "Text-to-911
				Reimbursement Request Form 1T, " revised 02/2020, which is incorporated herein
				by reference and may be obtained from the E911 Board office at the following
				address: State of Florida, E911 Board, Attn: Administrative Assistant, 4030
				Esplanade Way, Suite 135-F, Tallahassee, FL 32399-0950 or
http://www.flrules.org/Gateway/reference.asp?No=Ref-11896
.
(2) Funding is subject to the Board's
				determination of reasonable costs and availability of funds.
(3) The Board will consider costs for Text to
				911 per PSAP as follows:
(a) Reasonable "last
				mile" construction costs, if necessary;
(b) $800 per circuit per PSAP;
(c) The integrated annual recurring fee up to
				$11, 400 for each PSAP; and
(d) One
				year of service costs, if not included in the integrated annual recurring PSAP
				fee.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.012 - Training/Regional Planning Reimbursement

Current through Reg. 50, No. 138; July 16, 2024
The Board may reimburse training and regional planning costs
				  based on availabilty of funds as determined by the Board.
(1) All funding requests must be submitted in
				writing, and include the following information:
(a) Training:
1. The Next Generation 911 (NG-911) related
				purpose of the training;
2. The
				name of the organizer of the presentation;
3. A short synopsis of the training
				program;
4. The names and
				curriculum vita of the presenters;
5. Location of the training
				program;
6. The cost of the
				program, per attendee and total;
7.
				A list of the counties invited to attend (the training must be open to multiple
				counties);
8. The name and address
				of the entity submitting the request; and
9. The training must allow for two Board
				members or staff to attend.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60FF1 - Emergency Communications Board › Chapter 60FF1-5 - EMERGENCY COMMUNICATIONS BOARD › Section 60FF1-5.013 - Call Handling System Maintenance

Current through Reg. 50, No. 138; July 16, 2024
(1) Call Handling System (CHS) maintenance is
				defined as only those devices, software, and peripherals that are associated
				with the PSAP that are used exclusively for the receipt and processing of 9-1-1
				calls. These items include switches, gateways, customer portal, remote
				monitoring, routers, monitors, keyboards, videos and mouse, KVA's, and
				software. Software is further defined as the software provided by the
				manufacturer to maintain the integrity and functionality of the system.
				Additional software to provide other enhancements cannot be included in the
				maintenance disbursement. Excluded items include Graphic Information System
				(GIS) software, logging recorder, location services, and location
				repositories.
(2) CHS maintenance
				cost is disbursed to Rural Counties by way of the Rural County Grant
				Program.
(3) CHS maintenance cost
				for medium and large counties, subject to the Board's determination of
				reasonable costs and availability of funds, will be distributed by disbursement
				on a per capita basis.
(4) Method
				of distribution for medium and large counties.
(a) To participate in this program, each
				medium and large county must submit its documented CHS maintenance cost for one
				system for the fiscal year beginning October 1 and ending September 30 by
				January 1 of the following year.
(b) The total of all medium and large county
				CHS maintenance for a single system will be reevaluated annually by the E911
				Board.
(c) County population shall
				be determined each Fall from the most current available Florida Association of
				Counties data source.
(d) A
				disbursement will be distributed to each participating medium and large county
				at the amount to be determined on a per capita basis at the April E911 Board
				meeting each year.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-1 - DEPARTMENT OF MANAGEMENT SERVICES PROJECT MANAGEMENT AND OVERSIGHT › Section 60GG-1.002 - Risk and Complexity Assessment

Current through Reg. 50, No. 138; July 16, 2024
(1)
				The Agency will perform Risk & Complexity Assessments (R&C Assessments)
				for information technology (IT) projects to evaluate the risk and complexity
				factors for each IT project
https://www.flrules.org/Gateway/reference.asp?No=Ref-05569
.
				The purpose of the assessments is to determine the minimum level of project
				management control necessary to manage a given project in order to reduce risk
				and increase the probability of success.
(2) These assessments align projects by risk
				and complexity levels into one (1) of four (4) Risk and Complexity (R&C)
				Categories, which determine the amount of project management control required.
				The following diagram indicates the distribution of risk and complexity levels
				into the R&C Category:
Complexity
Low
Medium
High
Risk
Low
1
1
2
Medium
2
2
3
High
3
3
4
(a) Category 4
				represents High Risk and High Complexity projects.
(b) Category 3 represents High Risk and
				Medium Complexity projects, High Risk and Low Complexity projects, or Medium
				Risk and High Complexity projects.
(c) Category 2 represents Medium Risk and
				Medium Complexity projects, Medium Risk and Low Complexity projects, or Low
				Risk and High Complexity projects.
(d) Category 1 represents Low Risk and Medium
				Complexity projects or Low Risk and Low Complexity projects.
(e) Specific lifecycle phase requirements for
				each category are identified in Rule 60GG-1.003, F.A.C. - Initiation; Rule
				60GG-1.004, F.A.C. - Planning; Rule 60GG-1.005, F.A.C. - Execution; Rule
				60GG-1.006, F.A.C. - Monitoring and Controlling; and Rule 60GG-1.007, F.A.C. -
				Closure.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-1 - DEPARTMENT OF MANAGEMENT SERVICES PROJECT MANAGEMENT AND OVERSIGHT › Section 60GG-1.005 - Execution

Current through Reg. 50, No. 138; July 16, 2024
(1) The Execution phase involves carrying out
				and managing all the activities described in the Project Management
				Plan.
(2) The majority of Execution
				phase activities and documentation will be associated with the Agency's
				specific Systems Development Life Cycle (SDLC) process and requirements.
EXECUTION PHASE - Requirements by Risk &
							 Complexity Category
4
3
2
1
Operations and
Maintenance (O&M) Plan
Required - Develop an O&M Plan prior to the
							 scheduled completion of the project's Execution phase. Document concurrence
							 from those responsible for the operation and maintenance (e.g., financial,
							 information technology, and operational managers, etc.) on their readiness to
							 support the system from a budgetary, staffing, technology, and operational
							 perspective after go-live.
Recommended
4
3
2
1
Project Management Plans
Required - As necessary, update Project Management
							 Plan documents.
(4)
				Agency project management activities required during the Execution phase are
				further described in Rule 60GG-1.006, F.A.C. - Monitoring and
				Controlling.
Rulemaking Authority
					 282.0051(6) FS.
					 Law Implemented 282.0041,
					 282.0051
					 FS.
New 7-16-15, Amended 8-1-16, Formerly
					  74-1.005.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-1 - DEPARTMENT OF MANAGEMENT SERVICES PROJECT MANAGEMENT AND OVERSIGHT › Section 60GG-1.006 - Monitoring and Controlling

Current through Reg. 50, No. 138; July 16, 2024
(1) Project
				Monitoring and Controlling spans all phases of the project and involves the
				regular review of project status in order to identify variances from baselined
				project schedule, cost, and scope. In addition, all project management plan
				components developed pursuant to Rule 60GG-1.004, F.A.C., Planning, must be
				monitored, controlled and maintained.
(2) Risk and Complexity (R&C) Category 4
				and 3 Projects will use Earned Value analysis to ensure that the schedule
				provides an accurate representation of project status.
(a) Schedule Performance Index (SPI)
1. SPI is a measure of schedule efficiency
				expressed as a ratio of Earned Value (EV) to Planned Value (PV): SPI = EV/PV,
				where Earned Value is the measure of work performed expressed in terms of the
				budget amount authorized for that work, and Planned Value is the authorized
				budget assigned to scheduled work. Planned Value corresponds to the approved
				baseline budget.
2. A SPI value of
				less than 1.0 indicates that less work was completed, in a given time frame,
				than was planned.
3. A SPI value
				greater than 1.0 indicates that more work was completed, in a given time frame,
				than was planned.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-1 - DEPARTMENT OF MANAGEMENT SERVICES PROJECT MANAGEMENT AND OVERSIGHT › Section 60GG-1.007 - Closeout

Current through Reg. 50, No. 138; July 16, 2024
(1) The Agency must perform Project Closeout
				phase activities after the defined project objectives have been met and the
				Agency has accepted the project's product in accordance with their deliverable
				acceptance criteria and governance process.
(2) The following matrix lists the closeout
				activities and documents required for the project based on its Risk and
				Complexity (R&C) Category.
(3)
				Specific document templates are not prescribed - any project documentation that
				contains the information specified in the requirements below is acceptable.
CLOSEOUT PHASE - Requirements by Risk &
							 Complexity Category
4
3
2
1
Project Closeout Report
(PCR)
Required - Document the project's accomplishments
							 against the project budget, scope, schedule, and performance baselines. Include
							 a discussion of the lessons learned compiled by the project team and
							 stakeholders. The PCR must be completed as defined in the project
							 schedule.
Required - Document the project's accomplishments
							 against the project budget, scope, and schedule. Include a discussion of the
							 lessons learned.
4
3
2
1
Post Implementation
Review (PIR) Report
Required - Document whether the products or services
							 delivered by the project meet the Agency's business objectives, and provide the
							 expected results and benefits as documented in the Initiation and Planning
							 phases. Validate the cost benefit analysis and projected return on investment
							 analysis. This analysis should be performed six months to one year after the
							 product or service has been implemented.
Not Required
(4)
				The Agency must archive all Agency and third-party project documentation or
				artifacts.
(5) The Agency will
				ensure that system operations are transitioned to the appropriate support and
				operational entities in conformance with the Operations and Maintenance
				Plan.
Rulemaking Authority
					 282.0051(6) FS.
					 Law Implemented 282.0041,
					 282.0051
					 FS.
New 7-16-15, Amended 8-1-16, Formerly
					  74-1.007.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-1 - DEPARTMENT OF MANAGEMENT SERVICES PROJECT MANAGEMENT AND OVERSIGHT › Section 60GG-1.008 - Compliance with the Florida Information Technology Project Management and Oversight Standards

Current through Reg. 50, No. 138; July 16, 2024
(1) Agencies as
				defined in Rule 60GG-1.001, F.A.C., must comply with the Florida Information
				Technology Project Management and Oversight Standards.
(2) The Florida Information Technology
				Project Management Standards set forth in Rules 60GG-1.001 through 60GG-1.008,
				F.A.C. will be applied to existing Agency information technology projects based
				on their current project management lifecycle phase as of July 1, 2015.
(a) Projects that have not been approved for
				Initiation by the Agency must implement all sections of the standards set forth
				in this rule.
(b) Projects that are
				in the Planning phase will undergo a Planning Gate Risk and Complexity
				Assessment upon completion of their detailed plans and will be subject to the
				project management control requirements of the standards authorized in this
				rule from that point. (See Rules 60GG-1.002, F.A.C. - Risk and Complexity
				Assessment, and 60GG-1.004, F.A.C. - Planning)
(c) Projects that are in the Execution phase
				will continue to operate under the specific Agency's project management
				procedures, unless a significant Change Request is submitted (see Rule
				60GG-1.006 F.A.C. for the monitoring and controlling requirements for project
				change).
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-1 - DEPARTMENT OF MANAGEMENT SERVICES PROJECT MANAGEMENT AND OVERSIGHT › Section 60GG-1.009 - Department of Management Services (DMS) Oversight

Current through Reg. 50, No. 138; July 16, 2024
(1) Section
				 282.0051(d),
				F.S., requires DMS oversight on State Agency information technology projects
				that have total project costs of $10 million or more and that are funded in the
				General Appropriations Act or any other law.
(2) Section
				 282.0051(1)(n),
				F.S., requires DMS oversight on Cabinet Agency information technology projects
				with a total project cost of $25 million or more and that impacts one or more
				other agencies. Cabinet Agencies must adopt the standards contained in Rules
				60GG-1.001 through 60GG-1.008, F.A.C., for IT projects that have a total cost
				of $25 million or more and that impact one or more other agencies.
(3) Agencies will participate and assist DMS
				in oversight of a project as follows:
(a) The
				Agency will provide access to all required documentation as defined within this
				rule to DMS upon initiation of DMS oversight.
(b) DMS will assess schedule, cost, and scope
				variance based on the defined, documented, and approved Project Management
				Plan, budget, and the baselined schedule and spending plan.
(c) The Agency will update the project
				schedule weekly and provide the updated schedule to DMS. DMS will review the
				project schedule weekly and will identify and track trends in Schedule
				Performance Index and Cost Performance Index.
(d) The Agency will update project
				documentation (schedule, spend plan, scope, risk and issues) at the end of each
				month and provide these documents to DMS no later than the 10th day of the
				following month.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-2 - STATE OF FLORIDA CYBERSECURITY STANDARDS › Section 60GG-2.004 - Detect

Current through Reg. 50, No. 138; July 16, 2024
The detect function of the SFCS is visually represented as
				  such:
Function
Category
Subcategory
Detect (DE)
Anomalies and Events (AE)
DE.AE-1: Establish and manage a baseline of network
							 operations and expected data flows for Users and systems
DE.AE-2: Analyze detected Cybersecurity Events to
							 understand attack targets and methods
DE.AE-3: Collect and correlate Cybersecurity Event
							 data from multiple sources and sensors
DE.AE-4: Determine the impact of Cybersecurity
							 Events
DE.AE-5: Establish Incident alert thresholds
Security Continuous Monitoring (CM)
DE.CM-1: Monitor the network to detect potential
							 Cybersecurity Events
DE.CM-2: Monitor the physical environment to detect
							 potential Cybersecurity Events
DE.CM-3: Monitor personnel activity to detect
							 potential Cybersecurity Events
DE.CM-4: Detect malicious code
DE.CM-5: Detect unauthorized mobile code
DE.CM-6: Monitor external service provider activity
							 to detect potential Cybersecurity Events
DE.CM-7: Monitor for unauthorized personnel,
							 connections, devices, and software
DE.CM-8: Perform vulnerability scans
Detection Processes (DP)
DE.DP-1: Define roles and responsibilities for
							 detection to ensure accountability
DE.DP-2: Ensure that detection activities comply with
							 all applicable requirements
DE.DP-3: Test detection processes
DE.DP-4: Communicate event detection information to
							 stakeholders that should or must receive this information
DE.DP-5: Continuously improve detection
							 processes
(1) Anomalies
				and Events. Each Agency shall develop policies and procedures that will
				facilitate detection of anomalous activity and that allow the Agency to
				understand the potential impact of events.
Such policies and procedures shall:
(a) Establish and manage a baseline of
				network operations and expected data flows for Users and systems
				(DE.AE-1).
(b) Detect and analyze
				anomalous Cybersecurity Events to determine attack targets and methods
				(DE.AE-2).
1. Monitor for unauthorized
				wireless access points connected to the Agency internal network, and
				immediately remove them upon detection.
2. Implement procedures to establish
				accountability for accessing and modifying exempt, or confidential and exempt,
				data stores to ensure inappropriate access or modification is
				detectable.
(c) Collect
				and correlate Cybersecurity Event data from multiple sources and sensors
				(DE.AE-3).
(d) Determine the impact
				of Cybersecurity Events (DE.AE-4).
(e) Establish incident alert thresholds
				(DE.AE-5).
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-2 - STATE OF FLORIDA CYBERSECURITY STANDARDS › Section 60GG-2.006 - Recover

Current through Reg. 50, No. 138; July 16, 2024
The recover function of the SFCS is visually represented as
				  such:
Function
Category
Subcategory
Recover (RC)
Recovery Planning (RP)
RC.RP-1: Execute recovery plan during or after a
							 Cybersecurity Incident
Improvements (IM)
RC.IM-1: Incorporate lessons learned in recovery
							 plans
RC.IM-2: Periodically update recovery
							 strategies
Communications (CO)
RC.CO-1: Manage public relations
RC.CO-2: Repair reputation after an event
RC.CO-3: Communicate recovery activities to internal
							 Stakeholders and executive and management teams
(1) Recovery
				Planning. Each Agency shall execute and maintain recovery processes and
				procedures to ensure restoration of systems or assets affected by Cybersecurity
				Incidents. Each Agency shall:
(a) Execute a
				recovery plan during or after an Incident (RC.RP-1).
(b) Mirror data and software, essential to
				the continued operation of critical Agency functions, to an off-site location
				or regularly back up a current copy and store at an off-site
				location.
(c) Develop procedures to
				prevent loss of data, and ensure that Agency data, including unique copies, are
				backed up.
(d) Document disaster
				recovery plans that address protection of critical IT Resources and provide for
				the continuation of critical Agency functions in the event of a disaster. Plans
				shall address shared resource systems, which require special consideration,
				when interdependencies may affect continuity of critical Agency
				functions.
(e) IT disaster recovery
				plans shall be tested at least annually; results of the annual exercise shall
				document plan procedures that were successful and specify any modifications
				required to improve the plan.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-2 - STATE OF FLORIDA CYBERSECURITY STANDARDS › Section 60GG-2.0075 - Unmanned Aerial Systems (UAS) Minimum Security Requirements

Current through Reg. 50, No. 138; July 16, 2024
(1) Definitions.
(a) "Critical Component" means a Drone
				component related to: flight controllers, radio, data transmission devices,
				cameras, gimbals, ground control systems, operating software (including cell
				phone or tablet applications, but not cell phone or tablet operating systems),
				network connectivity, or data storage. Critical Components do not include, for
				example, passive electronics such as resistors, and non-data transmitting
				motors, batteries, and wiring.
(b)
				"Data" means any electronic information of a Governmental Agency that is a
				public record, as defined in Section
				 119.011(12),
				F.S.
(c) "Drone" has the same
				meaning as provided in Section
				 934.50(2)(a),
				F.S.
(d) "Florida College System
				Institution" has the same meaning as provided in Section
				 1000.21(3),
				F.S.
(e) "Foreign Country of
				Concern" has the same meaning as provided in Section
				 286.101(1)(b),
				F.S.
(f) "Governmental Agency" has
				the same meaning as provided in Section 934.50(7)(a)2., F.S.
(g) "Instructional Technology" means an
				interactive device used by a School that assists in instructing a class or a
				group of students and includes the necessary hardware and software to operate
				the interactive device. The term also includes support systems in which an
				interactive device may mount and is not required to be affixed to the
				facilities.
(h) "Open Data" means
				Data that is structured in a way that enables the Data to be fully discoverable
				and usable by the public. The term does not include Data that are restricted
				from public disclosure based on federal or state laws and regulations,
				including, but not limited to, those related to privacy, confidentiality,
				security, personal health, business or trade secret information, and exemptions
				from state public records laws; or Data for which a Governmental Agency is
				statutorily authorized to assess a fee for its distribution.
(i) "Research and Accountability Purposes"
				means Drone use by a Florida College System Institution or a State University
				in direct support of research on Drone hardware, operating systems, software,
				communications systems and protocols, components, and data practices for the
				purpose of understanding the existence and extent of potential threats and
				vulnerabilities, and mitigations thereto. This research must be conducted at
				the direction of a state of Florida agency or a federal agency, or a party
				contracted by a state of Florida agency or a federal agency to conduct the
				research.
(j) "School" has the same
				meaning as provided in Section
				 1003.01(2),
				F.S.
(k) "State University" has the
				same meaning as provided in Section
				 1000.21(6),
				F.S.
Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-3 - DATA CENTER OPERATIONS › Section 60GG-3.001 - Definitions

Current through Reg. 50, No. 138; July 16, 2024
The following terms are defined:
(1) Infrastructure as a Service (IaaS) - a
				data center service offering that provides processing, storage, networks and
				other fundamental computing resources used to deploy and run arbitrary
				software, which can include operating systems and applications.
(2) Mechanical Room/High-Power Room - those
				areas at the State Data Center dedicated to the mechanical equipment (e.g.,
				switchgear, uninterruptible power supply, batteries, generators, and
				transformers) that serves this facility.
(3) Raised Floor - the area at the State Data
				Center where an elevated floor is constructed above the solid substrate leaving
				the open space created between the two for cables, wiring, electrical supply,
				and/or cooling infrastructure.
(4)
				Service Request - a request by a customer entity, made to the State Data
				Center, for data center services.
(5) Vendor(s) - means a person who is under
				contract with a customer entity or DMS to deliver or install equipment at the
				SDC, or provide contractual services for the DMS or a customer entity at the
				SDC.
(6) Visitor(s) - any person(s)
				who is not a Department of Management Services (DMS) employee employed at the
				SDC who is requesting or has been approved to enter the SDC facility pursuant
				to these rules. Examples of Visitors include employees of customer entities,
				State of Florida employees, and Vendors of customer
				entities.
Rulemaking Authority
					 282.0051(6) FS.
					 Law Implemented 282.0051
					 FS.
New 6-16-16, Formerly
					  74-3.001.