Setting Up Code Enforcement Inspection Summary Assistant

The Code Enforcement Inspection Summary Assistant provides authorized Code Enforcement users with an AI-generated preinspection summary for scheduled and completed inspections. The summary brings together prior incident and case inspection information so users can quickly review inspection outcomes, code violations and corrective actions, notices, and comments before or during an inspection.

The application generates and stores the summary in the background. Users can also refresh the summary from the Preinspection summary drawer to include the latest information.

Here's how to set up the Code Enforcement Inspection Summary Assistant:

1. Enable AI functionality for Code Enforcement.

   In Functional Setup Manager, select Offering: Code Enforcement > Change Feature Opt In. Edit the Public Sector Code Enforcement features and enable Enable AI Functionality for Code Enforcement.

2. Review AI agent security requirements.

   Ensure that users who access the assistant have the required Code Enforcement and AI agent security. The Code Enforcement Inspection Summary Assistant is available to users with these roles:

   • PSC Code Enforcement Technician

   • PSC Code Enforcement Officer

   • PSC Code Enforcement Supervisor

   For more information about setting up AI agent security, see Securing AI Agents and Agentic Apps.

3. Verify that the Code Enforcement Inspection Summary Assistant is published.

   In AI Agent Studio, open the Agent Team tab and then the Published tab. Search for Code Enforcement Inspection Summary Assistant and verify that the agent is published.

4. Run or schedule the process that generates preinspection summaries.

   Use Process Monitor to run the Create Incident and Case Inspection Summary process. This process identifies eligible incident and case inspections and queues their summaries for generation.

   To submit the process:

   1. Navigate to Permitting and Licensing Process Monitor.

   2. Click Schedule New Process.

   3. Select Create Incident and Case Inspection Summary.

   4. Submit the process.

   You can schedule the process to run at a frequency appropriate for your agency. Running the process regularly keeps stored preinspection summaries current while reducing the need for users to generate summaries individually from the Inspection Tasks page.

   You must have one of these roles to run the process:

   • PSC System Administrator

   • PSC Code Enforcement Application Administrator

How the Preinspection Summary Is Generated

The Code Enforcement Inspection Summary Assistant is a workflow agent that generates a concise summary of information associated with an inspection and its related incident or case.

The scheduled Create Incident and Case Inspection Summary process queues eligible inspections for background processing. The generated summary is stored so that it can be displayed when a user opens the Preinspection summary drawer. A user can also select the refresh icon in the drawer to run the assistant on demand and update the stored summary with more recent information.

The assistant can use information from the inspection and its related incident or case, including:

• Prior completed incident and case inspections and their outcomes

• Code violations and corrective actions

• Notices

• Incident, case, and inspection comments

• Attachments

• Incident and case descriptions

• Compliance information, including days remaining to comply

• Priority

• Assigned code officer

The generated content depends on the information available for the incident or case. Comments and other lengthy information are summarized rather than reproduced in full.

The assistant uses the agency time preference when processing date and time information to maintain time zone consistency.

Reviewing the Agent Configuration

The Code Enforcement Inspection Summary Assistant uses LLM summarization with the delivered default prompts. Ensure that LLM summarization is enabled for the agent and that the generic agency time preference is applied.

After confirming the configuration, verify that the published version of the agent is available to the appropriate Code Enforcement users.

Verifying the Preinspection Summary

After completing the setup, verify that an authorized Code Enforcement user can access a generated summary:

1. Open the Code Enforcement Inspection Tasks page.

2. Locate a scheduled or completed inspection with prior inspection history.

3. Open the row-level Actions menu and select Preinspection summary.

4. Verify that the Preinspection summary drawer opens and displays the generated inspection information.

The summary can provide an overview of the inspection history along with information about incident-level inspections, case-level inspections, code violations, corrective actions, notices, and comments.

If the latest information isn't included in the summary, select the refresh icon to run the assistant again. While updated content is being generated, the drawer displays the content-generation state. The drawer also identifies the summary as AI-generated and provides the standard AI feedback controls.

For information about how Code Enforcement users review preinspection summaries, see Viewing Code Officer Inspection Tasks.

Considerations for Reviewing the Preinspection Summary

The preinspection summary is read-only and is intended to help Code Enforcement users quickly review relevant inspection history. It doesn't update the incident, case, inspection, code violations, notices, or other source information.

Because summaries are generated and stored through background processing, the information in a saved summary reflects the source information available when the summary was last generated. Users can refresh the summary on demand when they need to include more recent changes.

The content of a generated summary varies based on the inspection history and information available for the related incident or case.

For information about submitting and scheduling background processes, see Using the Process Monitor.