Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Facility Planning topic
No spam. Unsubscribe anytime.
Plano ISD previews Facility Insight tool, shows preliminary assessments and asks for SOPs for data entry
Summary
District staff previewed Facility Insight, a capital-planning platform; initial entries cover 42 elementary campuses and 61 projects with an assessed replacement value shown as $269 million and escalation-inflation estimate of about $296.75 million; trustees pressed for SOPs, prioritization rules and careful public sharing.
District staff presented a preview of Facility Insight, the capital-planning software Plano ISD is using to centralize facility data, run condition assessments and model bond scenarios.
Steve Ewing, chief of business operations, and Deputy Superintendent Johnny Hill outlined a multi-step implementation: build a facility catalog, identify systems and line items, create subprojects, apply escalation/inflation rates and use the tool to develop bond phasing scenarios. Staff emphasized that the data shown are initial and not complete.
Key figures presented for the initial dataset (elementary schools only) included 42 campuses covering roughly 3,250,000 square feet, an assessed/replacement asset value entered as $269,000,000 and 61 projects currently identified. With inflation/escalation factored in staff showed an estimate of approximately $296,750,000 for those projects (staff noted escalation inputs and placeholders are still being refined).
Jason Wink and interim executive director Blake Vaughn were introduced as implementation leads; staff said the facility condition index (FCI) used by the software is intended to help decide whether to repair or replace components and that anything over roughly 15 percent warrants conversation about replacement versus repair. Ewing said staff are using a 6 percent construction-inflation escalator as a working assumption.
Trustees asked detailed questions about data governance and operational use: they requested standard operating procedures (SOPs) to maintain consistency if key staff change, asked how the tool will prioritize emergency systems (for example, a failing HVAC that could close a school) versus longer‑term structural issues, and discussed whether and how campus-level data should be shared publicly without creating misleading or panic-inducing headlines. Staff agreed SOPs need to be developed and that the system will allow component-level prioritization and phasing.
Quote: “This system will allow us to actually put it in buckets based on need, not necessarily based on dollar amounts,” a staff member said, describing how phasing could be driven by need rather than only size.
Provenance: topicintro: {"block_id_start":"SEG 1293","block_id_end":"SEG 1300","evidence_excerpt":"Agenda item 9.2, facility planning update...","reason_code":"topicintro"} topicfinish: {"block_id_start":"SEG 2468","block_id_end":"SEG 2472","evidence_excerpt":"We are now ready for item 10, which is adjournment.","reason_code":"topicfinish"}.
