VERIFIABLE PUBLIC CONTRACT
SGVIAL Medellín: verifiable contractual scope
The SECOP II object documents procurement of SGVIAL support, maintenance and update services without turning the contract into proof of unpublished outcomes.
ENTITY / RELATIONSHIP
District of Medellín
LOCATION
Medellín, Antioquia, Colombia
EVIDENCE
Contract object published in SECOP II
What SECOP II publishes
The cited public opportunity describes the purchase of a subscription to support, maintenance and update services for SGVIAL, Medellín's Road Network Management System. GeoSAT's project register contains a corresponding scope. Together, these records support relevant experience with continuity for a road-management platform while keeping the public evidence separate from operational information that has not been disclosed.
The wording of the object matters. It does not describe a complete new system build and does not list modules, users, integrations, service levels or network indicators. This case therefore does not attribute features or results to the procurement record that the consulted notice does not document.
What the scope demonstrates
Support, maintenance and updates are software lifecycle activities. In a road GIS they may involve incident response, technical compatibility, corrections or evolution, but the source does not establish which specific activities were contracted or performed. It demonstrates a published institutional need around SGVIAL continuity and a GeoSAT portfolio record associated with that type of scope.
The source is also insufficient to establish when the system first entered operation, how many kilometres or assets it manages, which decisions it automates, how broadly it is used or what improvement it produced. Those claims would require additional public documents, comparable measurements or explicit permission to disclose private operational evidence.
Relevance to a current road GIS
The practical lesson is that a road platform must be budgeted beyond its launch. A buyer needs to define who corrects data, who responds to failures, how changes are approved, which versions remain supported and how the history of segments, inspections and interventions is retained. Responsibility for software operation should also remain distinct from technical responsibility for road information.
To assess a similar phase, the team should inspect the current inventory, critical workflows, integrations, change volume, user profiles and availability expectations. That work supports observable acceptance and operating criteria without using a past procurement object as a promise of future performance.
Boundary of the reference
SECOP II is cited here as the source of the contractual object. This page does not present the procurement as a quality certification, institutional endorsement or evidence of savings. Any decision involving SGVIAL, SINC readiness or a new road inventory must be evaluated against the buyer's current system, data and responsibilities.