Florida Administrative Code › 60 - DEPARTMENT OF MANAGEMENT SERVICES › 60GG - Florida Digital Service › Chapter 60GG-5 - STATE OF FLORIDA ENTERPRISE ARCHITECTURE › Section 60GG-5.002 - Enterprise Architecture

Current through Reg. 50, No. 138; July 16, 2024
(1) Purpose and
				intent. The purpose of this Enterprise Architecture rule is for the Florida
				Digital Service ("FL[DS]") to establish a statewide Enterprise Architecture.
				The intent of this Enterprise Architecture rule is to provide a comprehensive
				operational framework, including Standards and deliverables, that contemplates
				the needs and assets of the Enterprise to support Digital
				Interoperability.
(2) "State of
				Florida Enterprise Architecture: Transforming the Way Florida Purchases and
				Manages State Technology Resources" ("EA Document"), effective 04/23, is hereby
				adopted and incorporated by reference and available at
https://www.flrules.org/Gateway/reference.asp?No=Ref-15226
.
				The EA Document establishes the Enterprise Architecture, which includes
				Standards and deliverables.
(3)
				Form FL[DS]-01, Technology Initiative Management Form ("FL[DS]-01"), effective
				04/23, is hereby adopted and incorporated by reference and available at
http://www.flrules.org/Gateway/reference.asp?No=Ref-15227
.
				When submission of the FL[DS]-01 is required pursuant to this rule, FL[DS] may
				accept submission of an alternative format provided it is equivalent to the
				FL[DS]-01. The equivalent form must include the deliverables identified in the
				FL[DS]-01, as verified by FL[DS]. If FL[DS] determines that the alternative
				format is not an equivalent to the FL[DS]-01, the Enterprise Agency must update
				and resubmit the equivalent form to FL[DS] within thirty (30) calendar days of
				being notified by FL[DS].
(4)
				Definitions. Capitalized terms used herein are defined in section 1 of the EA
				Document.
(5) Thresholds. For
				procurement or acquisition of Technology Asset(s) exceeding $195, 000,
				Enterprise Agencies must complete and submit the FL[DS]-01, or an equivalent,
				in accordance with subsections (6) and (7) of this rule.
(6) Implementation. FL[DS] recognizes three
				categories of Technology Asset(s). They are Technology Asset(s) Planned,
				Technology Asset(s) in Development, and Technology Asset(s) in Operation.
(a) Technology Asset(s) Planned. A Technology
				Asset for which the intent to acquire has occurred but overt acts to initiate
				acquisition have not begun. This requirement applies regardless of the
				procurement method utilized. For all Technology Asset(s) Planned, the
				Enterprise Agency shall comply with the Standards and deliverables identified
				in the EA Document and FL[DS]-01, or equivalent. To document alignment with the
				EA Document and Standards and Deliverables, the Enterprise Agency must submit
				the FL[DS]-01, or an equivalent, in accordance with subsection (7) of this rule
				and must maintain supporting documentation in accordance with subsection (9) of
				this rule.
(b) Technology Asset(s)
				in Development. A Technology Asset for which the purchase is complete, work has
				begun, but Implementation has not yet occurred. For Technology Asset(s) in
				Development as of the effective date of this rule, the Enterprise Agency should
				find the Enterprise Architecture instructive wherever reasonably
				possible.
(c) Technology Asset(s)
				in Operation. A Technology Asset which has been made operational to
				Stakeholders or has been implemented. For Technology Asset(s) in Operation as
				of the effective date of this rule, the Enterprise Agency may find this rule
				instructive.