Speco Technologies ACMC2 Mobile Credentials/Speco Bluetooth Reade

We've deployed the Speco ACMC2 across healthcare systems, office parks, and federally regulated data centers where credential portability and supply-chain compliance are non-negotiable. The appeal is straightforward: eliminate card stock entirely, reduce badge replacement overhead to near-zero, and inherit smartphone-native security without bolting on external token hardware. The 15-foot BLE range is practical for typical doorway readers — no need for flush-mount installation or reader proximity optimization. What differentiates the ACMC2 from competitor mobile credential systems (like HID Mobile Access or Salto) is its Wiegand 26-bit output compatibility. Many facilities have legacy access control panels that don't support modern mobile credential protocols or require costly firmware updates; the ACMC2 lets you drop mobile credentials into systems that were deployed 10–15 years ago without touching the backend. That's a capex win for institutions without budget for access control hardware refresh. The trade-off is that Wiegand 26-bit is not cryptographically strong by modern standards — it's a 26-bit format, so the theoretical credential space is only 67 million unique codes. For a facility with 5,000 users, that's not a problem. For a large enterprise managing 100,000+ simultaneous users across multiple properties, you'd want to pair ACMC2 with a credential server that rotates or masks codes per transaction, or consider a full mobile credential platform (Salto, Nedap, or Gallagher) that supports higher-entropy formats. In our experience, the sweet spot for ACMC2 is mid-market integrations — 500–5,000 users per property, single-vendor access control backend, and a procurement mandate to avoid Chinese manufacturing or supply-chain scrutiny. NDAA Section 889 Part B compliance is a hard gate-opener for federal GSA work, and the ACMC2 clears that bar cleanly.

Technical Highlights:

• Wiegand 26-Bit Format: Direct compatibility with any access control panel or reader interface accepting standard Wiegand input. No middleware gateway, no proprietary protocol translation. Credential transmission is simplex (reader → panel), meaning no round-trip authentication or network dependency between reader and central system — the credential data itself is self-contained and panel-recognized. This is critical for legacy systems running on isolated networks or sites with poor connectivity.
• BLE 15-Foot Range at 2.4 GHz: Sufficient for doorway and entrance-point readers without obstructive placement. The 2.4 GHz frequency is globally unlicensed and works indoors; 15 feet (4.6m) translates to roughly 4–5 meter radius, covering standard 8-foot hallways and double-door entrance points. Beyond 15 feet, credential read fails gracefully — the system does not attempt long-range transmission that would drain smartphone battery or create false positives.
• Smartphone Native Security: Credentials leverage the device's built-in Secure Enclave (iPhone) or TEE (Android). No separate credential storage hardware means no dependency on external token battery life, no physical loss risk beyond device theft, and no additional user enrollment friction. Revocation is atomic: remove the credential from the Speco enrollment system, and the smartphone app invalidates the local copy on next sync.
• Non-Transferable Codes: Each of the 25 credential codes per pack is cryptographically or administratively tied to a single user's registered device. Prevents credential sharing and simplifies compliance reporting — access logs directly attribute each event to a named user without credential-pool ambiguity. Particularly valuable for healthcare (HIPAA audit trails) and finance (SOX compliance).
• NDAA Section 889 Part B Compliance: No Chinese-origin supply chain components, no dual-use technology flagging. Procurement for federal GSA Schedule contracts, DCSA-cleared facilities, and Department of Defense contractors faces zero supply-chain delay. Verify compliance documentation before contract signature, but Speco's supply chain disclosure is clean.

Deployment Considerations:

• Reader Model Lock: The ACMC2 credential pack is tied to compatible Speco BLE readers — typically the ACSR35L. If your site has deployed alternative reader brands (Salto, Allegion, Nedap) or older Speco readers without BLE support, the credentials will not function. Audit your reader inventory before provisioning. Mixed-reader environments require separate credential systems per reader type, complicating management across multi-site deployments.
• Smartphone Dependency: End users must carry an enrolled smartphone with the Speco credential app installed. For BYOD (Bring Your Own Device) environments, this is seamless. For facilities requiring contractor or visitor access, you cannot provision a temporary credential on a shared device — each user must have a personal smartphone. Visitor access workflows may require fallback to temporary plastic cards or a separate temporary-credential mobile app.
• Credential Revocation Latency: Revocation is not instantaneous. When you deactivate a credential in the enrollment system, the smartphone app typically receives the update within seconds to minutes (depending on app polling frequency and network availability). If a user's smartphone is offline, the old credential may remain valid until the next sync. For high-security environments (SCIF, secure cleanrooms), implement a grace period during offboarding to ensure sync completion before the employee physically departs.
• BLE Reader Environmental Hardening: The ACMC2 credential standard does not specify IP or impact ratings for the reader hardware. The ACSR35L reader must be mounted in an enclosure or weather-sealed housing appropriate to your environment (outdoor, high-traffic, wet environments). Plan for reader replacement costs if environmental damage occurs — the credential codes themselves are replaceable at pack-purchase cost, but reader hardware requires separate capex.
• Integration with VMS/Security Management Platform: The ACMC2 is an access control credential system, not a video or alarm device. It integrates at the access panel level (Wiegand input), not directly with NVR or VMS platforms. If you need unified event logging (access + video + alarm), implement a middleware platform (Genetec Security Center, Milestone Integrated Platform) that accepts Wiegand events from the access panel and correlates them with video timeline. Standalone access panels do not automatically forward credential events to VMS — you must configure event export at the panel level.

The ACMC2 is the right fit for integrators modernizing access control at mid-market properties without the budget or appetite for full platform replacement, and for federal procurement contexts where Section 889 compliance is a gate. For more information, see the Speco Technologies catalog.