Calanasan MDRRMO Emergency Operations Center Portal

The description states that Calanasan MDRRMO Emergency Operations Center Portal is a locally developed digital platform for emergency monitoring, response coordination, and public safety in Calanasan, Apayao. It is described as a single-developer project built with web technologies (HTML5, CSS3, JavaScript) and integrated with external hazard and weather data sources. The author claims the system supports features such as weather monitoring, incident reporting, evacuation information, interactive maps, and operational tools — all tailored to Calanasan’s geography and hazards.

The project is positioned as a pilot for a configurable platform that could be adapted by other remote or hazard-prone communities. However, no evidence of revenue, customers, traction, or adoption beyond the author's own development exists in the description.

Most important open question: Is there any indication that this system has been deployed or used operationally by local emergency personnel or residents, or whether it is merely a prototype?

The description states that the portal functions as a digital Emergency Operations Center and public-safety information hub. It brings together:

• Weather and hazard monitoring (e.g., PAGASA, PHIVOLCS, NASA FIRMS)
• Incident reporting and monitoring
• Evacuation-center information
• Interactive maps and road-obstruction tracking
• Operational tools such as ICS forms, training resources, and resource logs
• Emergency contacts and quick-help guidance

It is described as a responsive website with Progressive Web App capabilities, designed for both desktop and mobile use, and intended to function under limited connectivity conditions.

The system uses HTML5, CSS3, JavaScript, Leaflet.js, GeoJSON, Firebase Hosting, Google Apps Script, and integrates external APIs from OpenWeatherMap, Open-Meteo, PAGASA, PHIVOLCS, and NASA FIRMS.

Inference: The portal is a web-based platform with geospatial and data integration capabilities, built for local emergency response in a specific municipality.

The description states that the project was inspired by the need to centralize emergency information in Calanasan, where hazards like typhoons, flooding, landslides, and communication limitations affect operations. It is positioned as more than a general information website — it is shaped by local geography, hazards, and public-service needs.

The author claims that the portal was not built to replace official advisories but to support situational awareness and coordination for residents, responders, barangay officials, schools, and local disaster-management personnel.

It is described as a pilot project with potential for adaptation by other communities. The author states this is a future direction, not an existing claim of national or international adoption.

Inference: The positioning is localized and community-driven, with a stated intent to scale through configuration rather than replication.

The description states that the portal targets:

• Residents of Calanasan
• Barangay officials
• Schools
• Local disaster-management personnel

It also mentions that the system supports both public users and emergency personnel, with protected officer functions and a public experience that can be reviewed without an account.

Inference: The primary ICP is local emergency responders and community members in hazard-prone areas. The system is designed for low-connectivity use and includes role-based access.

Not evidenced.

The description does not state any pricing, monetization, or business model. It is described as a public-service initiative with no indication of revenue streams or customer charges.

The portal is built using:

• HTML5, CSS3, JavaScript
• Leaflet.js and GeoJSON for maps
• Firebase Hosting
• Google Apps Script for backend workflows
• Progressive Web App features (manifest, service workers, caching)
• Integration with external APIs from OpenWeatherMap, Open-Meteo, PAGASA, PHIVOLCS, NASA FIRMS

The author used Codex and GPT-5.6 to assist in reviewing, improving, testing, documenting, and extending the system during the hackathon.

Inference: The technical stack is standard for a web-based emergency portal with offline and mobile capabilities. AI was used as an assistant tool, not as a source of official information.

Not evidenced.

There is no mention of users, adoption, or operational deployment beyond the author’s own development. No data on usage, feedback, or performance in real-world conditions is provided.

Not evidenced.

The description does not reference existing platforms or competitors in emergency management or public safety portals. It is unclear whether similar systems exist or how this one compares to them.

• No operational use: The system is described as a prototype, with no evidence of real-world deployment or usage.
• AI dependency: While AI was used for development assistance, the author emphasizes that it is not a source of official information and that human judgment remains central.
• Limited scalability claims: The potential for adaptation to other communities is stated but not demonstrated.
• No revenue or customer data: No evidence of monetization, customers, or traction exists.

Inference: The project is in early development with no proven market or operational track record. Risks include lack of validation and limited real-world testing.

1. Has the portal been deployed or used operationally by local emergency personnel or residents?
2. What is the process for validating and updating hazard and weather data from external sources?
3. How are user reports or incident entries handled, and what is the role of local officials in this process?
4. Are there any plans to test or validate the system with actual emergency operations?
5. What is the long-term vision for replication — and how will that be supported technically and operationally?