Functional Fit & Usability
Does the platform match the District's workflows across the bid modules.
Pre-bid brief · Live RFP · Under NDA 
A prime's pre-bid brief for West Metro WMRFP2026-1.
West Metro Fire Protection District, Colorado, an RFP for Enterprise Technology Platforms across seven functional areas. One CJIS boundary decides what offshore support can legally touch. Techtiz drafts the non-CJIS technical and back-office work behind a US prime, NDA-first, and never agency-facing.
Live · closes Jun 29, 4 PM EDT
Awarding body West Metro Fire
Jurisdiction Jefferson County, Colorado
Status Drafting under NDA
Solicitation
WMRFP2026-1Ref 0000426216
Scope
7 platformsModular or integrated
Award
Best valueLine-item award reserved
Techtiz role
Back-officeNon-CJIS, NDA-first
Schedule of events
One hard deadline, stated in Eastern time.
Proposals are due June 29 at 4:00 p.m. EDT, electronic PDF only, with no exceptions for a late upload. The District sits in Mountain time, so confirm the local-clock equivalent before submitting. The July 6 vendor demonstration is a scored, live stage.
Published
RFP issued, 2:12 PM EDT, ref 0000426216
Questions due
Stated 2:00 AM EDT, confirm, reads like a 2:00 PM typo
Bid intent, optional
Notice of intent due 4:00 PM EDT
Answers released
District posts Q&A responses
Proposals due, 4 PM EDT
Electronic PDF only. No late submission
Demonstrations
Scored, live integration demo, not screenshots
Selection target
Final selection expected
The award model
Single best-value, but the District can split by area.
A vendor covering one or two of the seven functional areas can compete and win on those areas. No stated weights, no guaranteed minimum, and the July 6 demonstration is scored.
The defaultOne best-value award. A single multi-criteria, best-value selection across the seven factors, with no published numeric weights.
The reservationAward by functional-area line item. The District explicitly reserves the right to award by area to more than one vendor, so a focused, two-module bid is viable.
No floorNo guaranteed minimum. One-year base period with annual renewal options, the number of options not specified. No sample agreement was provided, so no term or insurance conflict is asserted.
The scored stageJuly 6 demonstration. A live integration demo, scored, is its own stage of the evaluation.
The differentiator · The CJIS boundary
Section 6.6 names CJIS alongside NIST CSF and NIST 800-53, and knowing exactly where the CJIS line falls is the specialized knowledge a prime is buying.
CJIS Security Policy Section 5.12 requires fingerprint-based background checks for anyone with logical access to CJIS-controlled data, available only to US citizens and certain lawful permanent residents. That is a hard personnel-security line. Structuring the work so offshore support never crosses it, while the prime owns everything CJIS-adjacent, is the domain read that separates a credible bid from a generic one. A second proof of reading sits in Section 6.7: a 30 to 60-day full data return at termination in non-proprietary formats, a clause that reads like a District burned by a prior vendor and that rewards a vendor who speaks to portability directly.
Techtiz hands the prime a ready CJIS-aware work-package separation, so offshore support is briefed and productive without ever seeing CJIS-controlled material.
The offshore allocation matrix
What a remote team drafts, and what stays with the prime.
The centerpiece of this engagement. The boundary that keeps a compliant Subcontracting model on the right side of a federal personnel-security bar.
A hybrid basis. A hard statutory bar, CJIS Security Policy Section 5.12.1 personnel security enforced under 28 C.F.R. Part 20, exposes the US prime to criminal liability on all CJIS-controlled work, so that work never moves offshore. Around it sit contractual gates: a signed NDA before any data moves, Colorado-law NDA scope, CORA-confidential marking, and CJIS-compliant or FedRAMP-authorized residency for any hosted CJIS data. Subcontracting is not addressed in the RFP, so confirm any Subcontracting-disclosure expectation with the contracting officer.
Offshore-eligible, post-NDA
Non-CJIS drafting and build
RFP and solicitation text analysis
Non-CJIS proposal content for LMS, analytics, staffing, personnel, asset, and prevention modules
Pricing models and five-year budget worksheets
NIST CSF and NIST 800-53 control-mapping documentation, framework mapping only, no credentials or system configs
Generic non-CJIS API documentation and integration code development
LMS configuration and course migration
Analytics and BI dashboard development on synthetic or anonymized data
Techtiz operates only in this column, behind the prime, under NDA, and never touches the District, CJIS data, or any RMS, ePCR, or CAD work product.
US prime only
CJIS, live data, the submission
RMS and ePCR architecture and configuration
CJIS system configurations and credentials
CAD integration build and testing, CAD is CJIS-adjacent
CJIS compliance documentation and review
Live District operational data, incident records and personnel data
User acceptance testing with live District data
Where bids fail
Submitting after the deadline Jun 29, 4 PM EDT
The rule
Late submission has no stated exception. The clock is Eastern time for a Mountain-time district.
If you miss it
Submit a full day early, confirm the cutoff against the local clock, and screenshot the upload confirmation.
Scope
Seven functional areas, one or more integrated platforms.
Modular or integrated bids are both acceptable. API-based integration with CAD, RMS, NERIS, payroll, and GIS is demonstrated live on July 6. The RMS and ePCR area is the one that pulls in CJIS, and it stays with the prime.
Integration Capability
Live API integration with CAD, RMS, NERIS, payroll, and GIS, proven July 6.
Reporting & Analytics
Data warehouse, dashboards, and reporting depth.
Cybersecurity & Compliance
CJIS, NIST CSF, NIST 800-53, with a control map and pen-test summary.
Vendor Support & Stability
Support model and financial and organizational stability.
Cost
Five-year TCO with disclosed escalation. Hidden costs risk a non-responsive ruling.
Implementation Approach
Phasing, migration, and the path to go-live.
Scored demonstration
July 6 live demo is its own scored stage of the evaluation.
Value model
Three five-year scenarios, driven by module count.
No budget is stated in the RFP. The ranges below are market estimates for planning only, not a District figure and not a bid. Total cost of ownership transparency is the pricing variable that matters most, since hidden or undisclosed costs may be ruled non-responsive.
Low
$500-800k5-yr TCO
2 to 3 modules. Year 1 about $180-320k, then $80-120k a year.
MidBase case
$1.05-1.7M5-yr TCO
4 to 5 modules. Year 1 about $450-700k, then $150-250k a year. Model under NDA
High
$1.7-2.8M5-yr TCO
Full seven-area suite. Year 1 about $700k-1.2M, then $250-400k a year.
All figures are market estimates for planning only, not District figures and not a bid. Completeness beats a low Year 1 headline; a transparent five-year TCO is what survives the cost factor.
Techtiz back-office pricing is scoped per engagement after NDA and is not part of the public RFP intelligence.
Agency context
Who is buying, and the single channel.
West Metro Fire Protection District is an independent special district in Jefferson County, Colorado, organized under the Colorado Special District Act, C.R.S. Title 32, governed by an elected board and funded largely through property taxes in Jefferson and Douglas Counties. It serves about 300,000 residents across 108 square miles and 17 stations, running more than 42,000 incidents a year in a mixed urban, wildland, and interface area. Procurement runs through one channel only: Todd Heinl, RFP Contact and Contracting Officer, at RFP2026@westmetrofire.org. The prime, not Techtiz, uses that channel.
300k
Residents served
17
Stations, 108 sq mi
42k+
Incidents per year
The competing field
Fifteen primes mapped, two in Colorado.
Computed from the U.S. PRIMES database sheet, public-source estimates for partner targeting, not District or audited numbers. Revenue suffixes were normalized before summing.
15
Primes mapped
7 / / 8
Highly vs partially relevant
2
Colorado in-jurisdiction
~$101.4B
Combined est. revenue
5
National, ~$1B or more
1
Large, $100M to $1B
5
Mid-market, $10M to $100M
4
Boutique, under $10M
The three largest by estimated revenue are Oracle (~$53B), Salesforce (~$34.8B), and Workday (~$7.8B). The largest fire and EMS specialists are UKG Kronos (~$4.2B), Vector Solutions (~$85M), and ImageTrend (~$70.6M). The two Colorado primes, both in Denver, are Intellectyx and Applied Future Technologies. Named under NDA
All figures are public-source estimates for partner targeting, normalized from the U.S. PRIMES sheet, not District or audited numbers.
Before June 12
Four questions worth filing.
Questions the prime can send to the single email channel before the question deadline. Techtiz never contacts the District; these are questions Techtiz can help draft.
Question 01
Which CAD system is in use?
The CAD platform sets the integration scope for the July 6 demo and defines the CJIS-adjacent boundary.
Question 02
What is the current NERIS submission status?
The District's NERIS position shapes how the RMS and ePCR area is scoped and demonstrated.
Question 03
Will the District supply July 6 demo data?
Whether the demo runs on District data or vendor data changes how the live integration is staged.
Question 04
What is the CJIS data-residency requirement?
Confirming the residency expectation fixes where hosted CJIS data must sit and what offshore support can never touch.
How Techtiz fits
The non-CJIS work, behind your firm.
Techtiz drafts the non-CJIS technical and back-office content and hands a review-ready package to the prime. The prime holds the single point of accountability to the District, owns the CJIS scope, the references, the sign-off, and every word said to the agency.
NDA before any data
A mutual NDA that excludes CJIS-controlled data from offshore access, with Colorado-law scope, before a single draft moves.
Draft the non-CJIS scope
Proposal content for the non-CJIS modules, the NIST control map, the LMS migration, the analytics build on synthetic data, pricing, and the five-year TCO.
Validate & package
Your team validates every claim and owns the CJIS and RMS work; Techtiz assembles the eight sections in order, PDF-ready.
Your firm owns the response
The submission, the live July 6 demo, the references, the sign-off, and all District contact stay with the prime.
NDA Prime name, engagement value, and proprietary content stay under NDA. Techtiz never contacts the District and never touches CJIS-controlled data.
Bidding WMRFP2026-1? The window is open.
Request the full document pack.
The decoded seven-area scope read, the CJIS work-package separation, the NIST control-map structure, the five-year TCO model, the compliance matrix, and the where-bids-fail checklist. A US partner manager replies within one business day, under a mutual NDA, never agency-facing, and never touching CJIS-controlled data.
Frequently asked questions
Pre-bid brief & confidentiality
Quick answers about how to use this engagement example and what detail is available under NDA.
Why is the prime contractor name withheld?
Most SLED subcontract work sits under mutual NDA and prime branding requirements. Public summaries describe engagement type, technical surface, and outcomes. Partner names and proposal content are shared only with explicit written permission or under an executed teaming agreement.
Can Techtiz support our bid on a similar pursuit?
Yes. If your pursuit matches this engagement type, email sled@techtiz.co or use the teaming intake form. Within 1 business day a U.S.-based partner manager replies with a mutual NDA template and a calendar slot—never agency-facing.
What do we receive under NDA?
Full RFP-decode packs, compliance matrices, technical volumes, submission runbooks, and named-resume options scoped to your vehicle and timeline. Prime name, pricing, and agency data stay inside the prime boundary.
Does Techtiz contact the procuring agency?
No. Techtiz is subcontract-only and never faces the agency. Your program manager holds the client relationship, sign-off, and all agency communication.