IBM Software / SaaS Spain

Prometeo Platform S.L.

Real-time Analytics

Prometeo needed a scalable way to monitor firefighters' smoke and toxin exposure in the field and present actionable health status data to command centers in near real time.

Reported impact

Business outcome

Prometeo created a portable, cloud-native health-monitoring platform that can scale with field testing and international deployment while giving fire-command teams clearer insight into firefighter smoke and toxin exposure.

  • Risk Reduction
  • Scalability

Solution

Prometeo built its firefighter-monitoring application on multiple IBM Cloud services so sensor data from field devices could be processed and surfaced rapidly. Ruggedized Samsung smartphones and smart watches worn by firefighters send measurements over the network into a cognitive platform on IBM Cloud, where machine-learning logic converts raw values into a simplified color-coded status for the Prometeo dashboard. IBM Cloudant stores the application data, and IBM Cloud Kubernetes Service now runs a set of Docker-based microservices that split the original monolithic application into smaller services for processing data, managing devices and building the dashboard. IBM Cloud App ID secures logins on the field devices, and the architecture is designed to support regional data residency as the solution expands internationally. By adopting cloud-native microservices, Prometeo gained a more maintainable and portable operating model for an IoT safety application that must ingest field telemetry, analyze it quickly and make the results usable during wildfire response.

Data flow

Measurements from field devices are transmitted to IBM Cloud, processed by machine-learning logic and microservices running on Kubernetes, stored in Cloudant, and surfaced as a color-coded status dashboard for fire command centers.

Solution architecture

4 components · 4 layers
  1. Storage
    • IBM Cloudant Stores the application data collected from field devices and supporting services.
  2. Serving
    • IBM Cloud Hosts the cognitive platform and dashboard environment that receives firefighter sensor data and serves monitoring outputs.
  3. Orchestration
    • IBM Cloud Kubernetes Service Runs the Docker-based microservices that process telemetry and build the monitoring dashboard.
  4. Governance
    • IBM Cloud App ID Secures firefighter logins on the field devices used by the Prometeo solution.

Architecture clues

  • IBM Cloud data centers were chosen in part to keep data secure in each region as the project grows.
  • The application was refactored from a monolith into multiple microservices housed in Docker containers on Kubernetes.
  • The next roadmap item is Samsung Health API integration for more granular recovery metrics.

Evidence from the source

IBM Cloud Kubernetes Service
IBM Cloudant
The app has been split into a handful of microservices
The values from the device are collected and transmitted over a network to a cognitive platform
Transparency Evidence & methodology 71/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value71/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    Prometeo Platform S.L. customer story

    First-party
    https://www.ibm.com/case-studies/prometeo-platform
    Source type
    Vendor-published customer story
    Published
    Apr 8, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.