Tecom, Challenger and the GE/Aritech Heritage
Tecom Industries was founded in Adelaide and became the dominant commercial access-control brand in Australia and New Zealand throughout the 1990s and 2000s. The Challenger panel range — Challenger 10, Challenger v8, Challenger v10 — became a fixture in office buildings, government facilities, and multi-tenanted commercial premises across ANZ. Over time, Tecom was acquired by GE Security, then folded into UTC Fire & Security, and subsequently into Carrier's building-technology portfolio. Throughout those ownership changes, the Challenger product line and its proprietary credential formats remained intact in the field.
The Aritech brand — used across parts of Europe and occasionally appearing on ANZ-market documentation — shares lineage with the same GE/UTC umbrella. For credential-sourcing purposes, Aritech-labelled readers in an ANZ installation will almost always be operating on the same Tecom formats described here. Understanding the ownership chain matters because it explains why Tecom is an enterprise proprietary format: format specifications were never openly published, and the installed base was accumulated over decades before any secondary supplier market developed.
The Tecom Titan controller, introduced for mid-size commercial deployments, uses credentials within the same format families as the Challenger range. This consistency across panel generations means that a credential strategy developed for a Challenger v8 site applies equally to a Titan-managed installation, and procurement can be handled through a single compatible-credential source regardless of which panel generation is installed.
The Tecom 27-Bit Proximity Format
Tecom's standard proximity credential uses a 27-bit Wiegand data structure. The format encodes a variable site code alongside a 16-bit card number with no parity bits — a configuration that distinguishes it clearly from the more common 26-bit H10301 standard and from Gallagher's formats. Because the site-code field is variable in width, the same physical card number can appear under different site codes across different Tecom installations, which is standard practice for segmenting large multi-site deployments.
At the physical layer, a 27-bit Tecom prox card operates at 125 kHz using standard EM or T5577-compatible modulation. That means a correctly programmed Tecom 27-bit compatible card can be manufactured on a T5577-based blank that has been encoded to the correct bit structure, site code, and card number. Our guide T5577 Explained: The Universal 125 kHz Programmable Blank covers how this class of substrate works in more detail. The 27-bit Tecom format is also available as a swipe-style credential in some older installations; if you are working with a legacy Tecom swipe reader, the relevant format is the Tecom 15-bit swipe card compatible variant.
Because the 27-bit format is an open encoding structure on a standard LF substrate, compatible reproductions are straightforward to manufacture provided the correct site code and card number range for your system is known. Facilities managers ordering replacement or additional 125 kHz LF proximity cards for a Tecom installation should treat reading the site code from an existing sample card as the first step — the same process described in our guide to identifying your access card or key fob format.
In practice, the site code is either printed on the face of an existing card, recorded in your Challenger panel configuration, or documented in the original system commissioning notes kept by your integrator. In cases where none of these sources is immediately available, your security integrator can retrieve the site code from the panel directly. Having this value confirmed before placing an order avoids the most common sourcing delay for 27-bit Tecom compatible credentials.
The Hitag-Based Tecom Smart Card
The Tecom Smart card is a different credential class entirely. Rather than a passive 125 kHz prox card, it uses Hitag technology — a communicating chip architecture developed by NXP (then Philips Semiconductors) that operates a challenge-response exchange with the reader. In a Hitag-based system the reader interrogates the card, the card's chip responds using an onboard crypto engine, and access is granted only if the response matches the reader's expectations. This is fundamentally different from a proximity card, which simply broadcasts a fixed number when energised.
Manchester-encoded ASK modulation is used at the air-interface level for the Tecom Smart card, which is consistent with Hitag S and related Hitag variants. The practical consequence for procurement is that a Tecom Smart card compatible credential is not a straightforward blank-and-encode job — it requires the correct Hitag chip configured to respond to Tecom reader interrogations. Our Tecom smart card compatible credential stocks the appropriate Hitag-based chip and physical format, but the enrolment step is handled by the Challenger panel using the keys already in your system, not by the supplier.
The communicating architecture of the Hitag-based credential also means that the system's crypto keys never leave the panel infrastructure — they are generated and held internally, and the enrolment process does not require those keys to be shared with a card supplier. This is a significant operational advantage for security managers: replacement credentials can be sourced from a compatible supplier and enrolled through normal Challenger procedures without any exposure of the system's internal key material to third parties.
What's Plain-Compatible vs What Needs the Matching Chip
The distinction between the two Tecom formats has direct implications for ordering. For the 27-bit proximity format, a compatible blank encoded to your site code and card number range will present correctly to any standard Tecom Challenger reader expecting that format — no system-side enrolment step is required beyond adding the card number to your access management software. The compatibility path is clean and well understood for this format.
For the Tecom Smart card, the process differs. A compatible blank must be built on the correct Hitag chip so that the reader's challenge-response cycle completes successfully. The Challenger panel or associated enrolment terminal then registers the credential using the crypto keys held within the system — keys that were never shared with any card supplier and need not be. This is the same enrolment model used by other communicating-card systems such as Gallagher or Lenel 42-bit installations: the supplier provides a compatible blank substrate; the system operator enrols it through normal procedures. See our guide to compatible vs genuine access cards for a fuller discussion of how this model works across different technology tiers.
Key fob form-factor credentials follow the same split. The Tecom compatible smart card fob stocks both prox and Hitag-based variants for the respective format families. When specifying an order, confirm with your system administrator whether the readers in your installation are configured for the 27-bit prox format, the Smart card format, or a mixed deployment — some larger ANZ sites run both in parallel.
A useful rule of thumb for identifying which format is in use: 27-bit proximity readers are typically compact single-element units with no visible multi-zone antenna pattern, while Hitag-capable readers generally have a larger face to accommodate the interrogation field required for the challenge-response exchange. If the reader model number is visible, your security integrator can confirm which credential type it expects from Tecom or Carrier product documentation.
Ordering Compatible Tecom Credentials
Sourcing compatible Tecom credentials is a more specialised exercise than ordering standard 26-bit ISO cards, because Tecom remains a niche ANZ format with limited secondary supplier coverage. For the 27-bit proximity format, we need your site code and the card number range you want issued. These can usually be read from the face of an existing card or retrieved from your Challenger panel's configuration. For the Hitag-based Smart card format, we supply the correct blank and you handle enrolment through your panel — the site code and number range still apply, so have those on hand when you contact us.
Lead times for Tecom compatible credentials may be longer than for commodity formats such as 26-bit H10301 or HID standard prox, because the Hitag-based Smart card variant requires sourcing the appropriate chip rather than a generic T5577 blank. Planning ahead for credential orders — particularly for large-batch replacements or new-user onboarding across a multi-tenanted building — avoids the operational pressure of last-minute procurement against a short deadline.
If you are managing a mixed-technology estate that includes Tecom alongside other enterprise-proprietary formats — for example, a commercial building where some tenants use Avigilon or Software House CCOTZ readers — a multi-format office building credential strategy is worth discussing. We supply compatible credentials across dozens of proprietary formats, and a single procurement conversation can resolve multiple format requirements in parallel.
Security ID Systems is an independent manufacturer and supplier of compatible access-control credentials and is not affiliated with, authorised by, or endorsed by Tecom Industries, GE Security, UTC Fire & Security, Carrier, or Aritech.
Tecom 27-Bit Proximity vs Tecom Smart Card (Hitag): Technical Comparison
| Attribute | Tecom 27-Bit Proximity | Tecom Smart Card (Hitag) |
|---|---|---|
| Frequency | 125 kHz LF | 125 kHz LF |
| Chip / substrate | T5577-compatible (EM4100-class) | NXP Hitag S or equivalent Hitag-family chip |
| Air-interface modulation | ASK / Manchester or FSK | ASK / Manchester |
| Data structure | 27-bit Wiegand (variable site code + 16-bit card number, no parity) | Hitag challenge-response protocol |
| Reader interaction | Passive broadcast — card transmits fixed number | Communicating — reader/card exchange; crypto response required |
| Compatible supply path | Encode blank T5577 to correct 27-bit site code + card number | Supply correct Hitag-chip blank; system enrols with its own keys |
| Enrolment required by system? | Card number added to software only | Full enrolment via Challenger panel or terminal |
| Form factors available | ISO card, key fob | ISO card, key fob |
| Site code source | Card face, panel config, or commissioning notes | Same — confirm with integrator or panel config |