Overview
FacilityBot Studio is an AI-powered app and dashboard builder built into FacilityBot. It enables custom applications and dashboards to be easily created simply by describing their requirements in natural language, without engineering support or manual dashboard configuration.
From “Here’s what we need…” to “Here’s the dashboard.” ⚡Just describe what you need. FacilityBot Studio builds it.
In this case study, FacilityBot Studio was used at a Manufacturing Facility in Florida to build two dashboards. The first turned the site’s Permit-to-Work (PTW) requests into an enhanced table, split by permit type. The second turned daily facility rounds into a dashboard the team can review and export.
The Requirement
The facility uses two permit types: a Site Incident Prevention Plan (SIPP) Work Permit and a Daily Work Log. The team needed the existing Permit-to-Work table to show more of what contractors fill in on each form.
Specifically, they asked for one tab per permit type, each adding six columns taken from the form: Company Name, Name of Person Requesting Permit, Project Name, the step-by-step description of the work being performed, Start Date/Time and End Date/Time.
The facility also runs an 80-item daily rounds checklist, with AM and PM readings for chillers, boilers, vacuum pumps, compressed air, water treatment and electrical rooms. The team wanted every completed round in one place, with failed checks easy to spot and readings they could export.
Until these were built, reviewing permits or rounds meant opening records one at a time and copying details out by hand.
How It Was Built with FacilityBot Studio
Once the request was scoped, FacilityBot Studio was switched on for the facility and the PTW dashboard was built by describing the columns needed in a single instruction.
Here is an example of a prompt used:
“Build an enhanced Permit-to-Work dashboard with two tabs: one for SIPP Work Permits and one for Daily Work Logs. In each tab, add columns for Company Name, Name of Person Requesting Permit, Project Name, Describe the work being performed step by step, Start Date/Time and End Date/Time, taken from the permit form.”
After the first version went live, the team asked for the table to be shown in full, without a bar cutting it off. Studio was used again, the same way, to refine the layout by describing the fix.
As the team used the dashboard day to day, they asked for three more improvements:
- Open a permit’s details by selecting its Permit/Application ID directly from the dashboard.
- Search permits by Project Name or Work Description.
- Sort permits by Submission Date and filter them by Status.
Each one was added by describing it to Studio, not by rebuilding the dashboard.
The team then used Studio to build a second dashboard for daily facility rounds. Here is an example of a prompt used:
“Build a Daily Facility Rounds dashboard with From and To date filters and quick options for This month, Last month, Last 30 days and Last 90 days. Show summary cards for Rounds in range, Failed checks, Technicians and Latest round. Add a table with Round date, Checklist ref, Technician, Completed, Fails, Answered and Staff remarks, and a View button that opens each round’s full checklist grouped by section. Add Excel, CSV and PDF export buttons.”
The Result
The facility now has a Permit-to-Work dashboard with a tab for each permit type. Each tab shows who requested the permit, which company and project it is for, what work is being done and when it starts and ends.
The team can open any permit from its ID, search by project or work description, sort by submission date and filter by status, all in a table shown in full.
The Daily Inspections dashboard shows rounds completed, failed checks, technicians and the latest round for any date range. Failed checks are flagged in red, and View opens every AM and PM reading for a round. With one click, the period exports to Excel, CSV, or a PDF with one page per round.
FacilityBot Studio took both from a feature request to a working dashboard without a dedicated engineering build. It also let the team refine each one as real usage showed what else they needed.