1. (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. (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 HYPERLINK "https://www.flrules.org/Gateway/reference.asp?No=Ref-15226" https://www.flrules.org/Gateway/reference.asp?No=Ref-15226. The EA Document establishes the Enterprise Architecture, which includes Standards and deliverables.
3. (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 HYPERLINK "http://www.flrules.org/Gateway/reference.asp?No=Ref-15227" 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. (4) Definitions. Capitalized terms used herein are defined in section 1 of the EA Document.
5. (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. (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.

   1. (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.
   2. (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.
   3. (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.

7. (7) Completion and Submission of the FL[DS]-01 or an Equivalent. For all new Technology Assets as of the effective date of this rule, Enterprise Agencies must complete and submit the FL[DS]-01, or an equivalent, to FL[DS] in accordance with subsections (5) through (7) of this rule.

   1. (a) Prior to initiating acquisition of a Technology Asset, Enterprise Agencies must complete and submit the Strategy, Business, and Systems Domains sections of the FL[DS]-01, or an equivalent, to FL[DS]. The FL[DS]-01, or an equivalent, is not required to be completed to publish a Request for Information, as defined in Section 287.012(22), F.S.

      1. Emergency Purchases. For emergency purchases, as described in Section 287.057(3)(a), F.S., the requirement to submit the FL[DS]-01, or an equivalent, prior to acquisition, does not apply. Within ninety (90) calendar days of initiating the emergency Technology Asset acquisition, Enterprise Agencies must complete and submit the Strategy, Business, and Systems Domain sections of the FL[DS]-01, or an equivalent, along with a copy of the agency head’s written determination, as required by Section 287.057(3)(a), F.S.

   2. (b) Prior to implementing a Solution, Enterprise Agencies must complete and submit the Security, Data, Infrastructure, and Testing Domains sections of the FL[DS]-01, or an equivalent, to FL[DS].

      1. Emergency Purchase. For emergency purchases, as described in Section 287.057(3)(a), F.S., the requirement to submit the FL[DS]-01, or an equivalent, prior to implementing a solution does not apply. Within one hundred and twenty (120) calendar days of implementing the Solution, Enterprise Agencies must complete and submit the Security, Data, Infrastructure, and Testing Domain sections of the FL[DS]-01, or an equivalent, to FL[DS].

   3. (c) If the Enterprise Agency makes any changes to Technology Asset(s) which alter previous information provided in a submitted FL[DS]-01, or an equivalent, the Enterprise Agency must submit an updated FL[DS]-01, or an equivalent, to FL[DS]. The Enterprise Agency must submit the updated FL[DS]-01, or equivalent, to FL[DS] prior to implementing the change.

      1. Emergency Purchases. For emergency purchases, as described in Section 287.057(3)(a), F.S., the requirement to submit the updated FL[DS]-01, or an equivalent, prior to making a change to the Technology Asset does not apply. Within sixty (60) calendar days of implementing the change, Enterprise Agencies must complete and submit the updated FL[DS]-01, or an equivalent, to FL[DS].

8. (8) Cabinet Agency Responsibilities. If a Cabinet Agency adopts alternative Standards in lieu of the Enterprise Architecture Standards, the Cabinet Agency must notify the Governor, the President of the Senate, and the Speaker of the House of Representatives in writing. The written notification must include a justification for adoption of the alternative Standards and explain how the Cabinet Agency will achieve Data Interoperability. A Cabinet Agency adopting alternative Standards should also provide the above-referenced notification to FL[DS].
9. (9) Documentation. Enterprise Agencies must maintain all supporting documentation to validate completion of the deliverables identified in all of the Enterprise Agency’s FL[DS]-01 forms, or equivalents. Upon request, Enterprise Agencies must submit copies of supporting documentation to the Enterprise Agency’s FL[DS]-01, or equivalent, to FL[DS]. Enterprise Agencies shall be responsible for maintaining all supporting documentation pursuant to the applicable retention schedule approved by the Department of State, Division of Library and Information Services.

10. (10) FL[DS] Responsibilities. FL[DS] shall support Initiatives which align with the Enterprise Architecture. If requested, FL[DS] will:

    1. (a) Assist an Enterprise Agency in determining whether Technology Asset(s) align to the Enterprise Architecture outlined within the EA Document,
    2. (b) Support an Enterprise Agency’s efforts to align Technology Asset(s) to the Enterprise Architecture as outlined in the EA Document, and
    3. (c) Provide an Enterprise Agency an assessment of its compliance with the Enterprise Architecture as outlined in the EA Document within forty-five (45) calendar days of FL[DS]’s receipt of the request.

Rulemaking Authority 282.0051(6) FS. Law Implemented 282.0051, 282.206, FS. History–New 4-5-23.