Writing the technical annex for a 911 CAD tender: what to include
In a Mexican public tender, the technical annex (anexo técnico) decides which computer-aided dispatch (CAD) system a 911 center or C5 buys, and whether it can hold the vendor to it later. This guide lists the sections to include, with sample wording for each, aligned with the SESNSP’s Norma Técnica 9-1-1 v2.0.
Why the technical annex matters most
A vague annex lets bids comply on paper and fail in operation; one written around a brand narrows competition and invites challenges. Since April 2025, federal purchases follow the new public procurement law (LAASSP) and are published on Compras MX, which replaced CompraNet; states and municipalities apply their own laws and portals. Either way, what protects the center is an annex that describes measurable functions, not products.
The sections it should have
1. Purpose and scope
Which center or centers, how many call-taking and dispatch positions, which agencies dispatch from the system (police, fire, EMS, civil protection) and its hours of operation.
Sample wording: “The system shall operate 24/7 for N call-taking and N dispatch positions, with police, fire and EMS users on one incident record.”
2. CAD functional requirements
The minimums in section 4.2 of the Norma Técnica 9-1-1: an integrated map with incidents, cameras and GPS units; mobile viewing; decision support.
Sample wording: “The CAD shall meet the minimum requirements of section 4.2 of the Norma Técnica 9-1-1 v2.0, which the bidder shall demonstrate clause by clause.”
3. Integrations with existing systems
List the existing systems the CAD must connect to: the phone switch via CTI with ANI and ALI, voice recording, AVL, video surveillance, radio (P25, TETRA or DMR), other CADs and the IPH police report system.
Sample wording: “The bidder shall describe how it integrates each system in Annex A, stating whether the integration already runs at another center.”
4. National incident catalogue
Clause 4.2.5.8 requires information to be stored using the current National Catalogue of Emergency Incidents (CNIE).
Sample wording: “The CAD shall classify incidents natively with the current national catalogue and be updated when the catalogue changes.”
5. Platform and availability
High availability with redundancy, transparent disk failure, a commercial non-proprietary database and backup without stopping operation (4.2 to 4.2.4).
Sample wording: “The bidder shall present the proposed redundant architecture and its live backup procedure.”
6. Geographic information system
A GIS linked to or integrated with the CAD, with layers down to neighbourhood, standard formats (SHP, KML, TAB, DXF or GML) and address search (4.8).
Sample wording: “Mapping shall include state, municipality, neighbourhood, street and point-of-interest layers and import the formats in clause 4.8.6.”
7. Indicators and reports
The CAD must measure what the Norma evaluates: average reception and dispatch times of 90 seconds and urban arrival within 10 minutes (7.3.1).
Sample wording: “The system shall timestamp each stage and report times per incident, shift and agency.”
8. Deployment and data hosting
State whether cloud, on-premise or hybrid is acceptable, and where data must reside.
Sample wording: “The bidder shall state the deployment model and data location, in line with the institution’s security policy.”
9. Migration and parallel operation
Replacing a CAD is the riskiest moment. Require a phased plan with the current system running until cut-over.
Sample wording: “The implementation plan shall include parallel operation and cut-over criteria agreed with the institution.”
10. Training, support and service levels
Training by role (call taker, dispatcher, supervisor, administrator), 24/7 support and response times by severity.
Sample wording: “The bidder shall define response and resolution times by severity and penalties for non-compliance.”
11. Information security
Role-based access, an audit log, encryption and continuity, in line with the center’s cybersecurity policy.
Sample wording: “The system shall keep a tamper-proof log of every user action.”
12. Acceptance tests and demonstration
Require a demonstration on the center’s real scenarios and acceptance tests before go-live.
Sample wording: “In a technical session, the bidder shall demonstrate call handling and dispatch of the scenarios in Annex B.”
How KabatOne can help
- Emergency call handling and dispatch in one platform: the call moves from call taker to dispatcher without re-entry.
- Caller location generated automatically; incident, units, cameras and sensors on one live map.
- AI Co-Pilot for call takers and dispatchers: live transcription, scenario guidance and unit recommendations. The operator always decides.
- Cloud, on-premise or hybrid deployment, with parallel operation during the transition.
- Trusted by C5 CDMX. We can support your team with a demonstration on your own scenarios.
Frequently asked questions
What is a technical annex in a Mexican tender?
It is the part of the tender documents where the institution describes what it needs: scope, functional and technical requirements, integrations, service levels and how compliance must be shown. Bids are evaluated against it and the contract is enforced by it.
Which law governs buying a 911 CAD in Mexico?
For the federal government, the public procurement law (LAASSP) in force since 17 April 2025, with procedures published on Compras MX. States and municipalities apply their own procurement laws and portals.
Should the annex cite the Norma Técnica 9-1-1?
It is advisable. The SESNSP’s Norma Técnica 9-1-1 v2.0 sets the minimum CAD and GIS requirements for every state and municipal center, so citing its clauses gives an objective standard for comparing bids.
How do you avoid an annex that favors one vendor?
Describe measurable functions and outcomes, not brands or exclusive features, and require each bidder to show compliance clause by clause and in a demonstration on your own scenarios.
Tell us about your 911 center, command center or city. A specialist replies within one business day.