American Red CrossAmerican Red CrossShort answers to the questions an IT leader raises about a Red Cross home for operational applications. None of them require a technology decision today.
A web page that works like a program. Not a file you open in Excel, Word, Power BI, or ArcGIS — its own small piece of software, built for one job, used by staff and volunteers.
Ordinary web files — the same kind every website is built from — plus the data files they read. No server software, no database. Where data is prepared ahead of time, that happens in a script on a laptop, not on a server. Anything more than that is a question for the path to answer, not for this conversation.
Power BI is excellent for dashboards and analytics. These tools are applications: they guide users through timelines, workflows, decisions, simulations, and experiences. The use case is different.
ArcGIS answers location questions extraordinarily well. These applications combine geography with workflow, narrative, operations, decision support, and training. ArcGIS is usually part of the solution, not the entire solution.
SharePoint provides content management. The issue here is application ownership, lifecycle management, supportability, and continuity.
No. This describes a missing capability and asks for a repeatable path. The technical implementation should be determined through the normal process.
No. This asks for organizational ownership and continuity. The hosting model is an implementation detail.
No. The goal is exactly the opposite: to move operational tools into a visible, governed environment.
That is precisely the problem to solve. The organization should not depend on a volunteer for continuity.
Today, a handful. Over time, likely more. The goal is a repeatable process before the volume grows.
Because building one got cheap. A small custom web application used to need a team and a budget; now one person builds it in days. They are appearing whether or not a path exists, and the ownership question is showing up after adoption instead of before it.
Reduced continuity risk. Improved knowledge retention. Greater operational agility. A defined path from idea to organizational asset.
The business owner — the same principle already used for dashboards, reports, maps, and other operational products.
That is one of the reasons for this conversation. The request is for guidance on what a durable path should look like.
A documented process by which an operational application moves from individual ownership to organizational ownership without a special exception.
Because valuable operational knowledge currently resides with the creator rather than with the organization.
Agreement that operational applications are a legitimate category of organizational asset and deserve a repeatable ownership path.
The Hurricane Ian replay — one file, public NOAA data, no login, opens on any phone. Open it. The replay is only a visible example; the category is operational applications.