VERIFIABLE PUBLIC CONTRACT
Medellín geographic platform: verifiable public scope
SECOP II documents specialized support, maintenance and update services for the District geographic platform without substantiating unpublished outcomes.
ENTITY / RELATIONSHIP
Special District of Science, Technology and Innovation of Medellín
LOCATION
Medellín, Antioquia, Colombia
EVIDENCE
Contract object published in SECOP II
The object that can be verified
The cited 2025 public opportunity describes specialized support, maintenance and update services for the Medellín District geographic platform. GeoSAT's project register contains a corresponding scope. This alignment supports relevant experience with continuity for an institutional platform without expanding the object into outcomes that the source does not publish.
The evidence is deliberately narrow. The notice identifies a platform and an operational continuity need, but it does not set out its architecture, components, integrations, layer catalogue, access profiles or service level here. It also does not establish that a particular update was deployed or produced a measurable improvement.
Operations are different from launch
The case is relevant to geoportals because it documents a category of work that follows first publication: support, maintenance and updates. An institutional geographic platform depends on sources, services, permissions, infrastructure and editorial processes that change over time. The cited contract, however, does not support claims about which specific tasks were performed within each category.
This page therefore does not claim availability, response times, query volume, user satisfaction, cost reduction or increased adoption. It also does not present the contractual relationship as endorsement of a universal architecture. Every organization has different sources, obligations, integrations and operating capacity.
Questions the scope helps frame
When sizing a similar service, incident response, preventive maintenance, security, compatibility, data updates, functional changes and infrastructure evolution should be separated. Responsibilities must also be assigned across technology, the GIS team and data producers. An upstream source failure is not handled like a viewer defect, and a schema change needs controls different from those used for a visual update.
Acceptance criteria can cover observable availability, agreed response targets, regression checks, change traceability, documentation and a rollback procedure. Those criteria belong to the new context; they cannot be inferred from the SECOP notice.
How the case is presented
The public source is used as evidence of the contractual object and as a direct reference for review. GeoSAT does not publish the District's private data or internal metrics. The case provides a verifiable reference for platform-continuity experience, while OpenGIS and the architecture estimator remain separate GeoSAT diagnostic tools rather than claimed outputs of this contract.