HES 1006 and 9000 Series Electric Strikes
HES electric strikes include the versatile 1006 family for cylindrical and mortise lock applications and multiple 9000-series surface-mounted models for rim exit-device and specialty openings. A correct choice requires the exact lock and latch geometry, frame condition, fire and wind requirements, fail mode, monitoring and power system engineering.
The whole system is the decision, not one headline feature
Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the system engineering.
The opening survey points to a strike family
Every opening is recorded before anything is ordered: door and frame, handing and swing, lock manufacturer and model, latch or deadbolt dimensions, any existing ANSI preparation, the closer and the preload. Photographs and measurements leave credential data out. Fail mode waits until fire labels, smoke requirements, windstorm or exterior exposure and the governing code path are confirmed.
Matching a 1006 or the right 9000-series model means working from current HES compatibility and faceplate information rather than memory. Pullman latch geometry varies, and a surface strike built for one will not necessarily accept another. Keeper depth, latch throw, frame material, reveal, mounting surface and the monitor options required all go on the record.
Discovery needs to identify protected areas, users, schedules, response procedures, privacy expectations, existing equipment and the party who will administer the finished system. Product claims only become useful after they are translated into measurable coverage, capacity, availability and response requirements.
- Identifying the lock and latch
- Measured frame and opening
- Fire/wind/environment labels
- Egress review with fail mode
Frame preparation, faceplate and power system engineering
For a 1006 field installation, coordinate strike body depth, faceplate, shims, lip extension and trim condition with the actual frame. Surface-mounted models require adequate frame face, latch engagement and listed hardware where ratings apply. Do not remove frame material until the complete opening has been approved.
Filtered 12 or 24 VDC power is sized from the actual current draw, the cable run and the loads that operate at the same time. The controller relay, a fire-alarm interface where one is required, door position, latch or strike monitoring and suppression get coordinated together. Wire color is not documentation: fail-safe and fail-secure behavior is written down.
Addressing, PoE or low-voltage power, pathways, environmental ratings, mounting, door or camera interfaces and backup power are settled together. Before a purchase order goes out, exact model compatibility and supported software are confirmed, because names that look alike can hide different capacity, license or integration limits.
- The precise faceplate or surface model
- Approved frame prep
- Voltage drop on filtered power
- Mapping of relays and monitors
| Opening | Typical family question | Confirm |
|---|---|---|
| Mortise/cylindrical lock | Does a 1006 faceplate match? | Latch, deadbolt and frame prep |
| Rim exit device | Which 9000 surface strike fits? | Latch shape, throw and rating |
| Monitored door | Which contacts are supported? | LBM/LBSM and faceplate |
| Rated opening | Is the complete assembly listed? | Model, fail mode and fire label |
Field Installation, alignment and system integration
The strike is not a tool for defeating preload. Closer, hinges and lock get adjusted first so the latch enters and releases cleanly, and only then does the strike go in, using the manufacturer template with the door and frame protected and the mounting surface flat. Wire routing is checked so nothing pinches at the frame or compromises rated construction.
Integrate unlock schedules, credential grants, request-to-exit and forced/held-open alarms with the access platform. Test local mechanical egress independently from electronic release. Monitoring contacts needs to represent the intended physical state and be named clearly in the software.
Use named administrators, least privilege and multifactor authentication where supported. Establish backup, update, health-monitoring and escalation ownership. Firmware and software needs to come from the manufacturer portal after compatibility and release-note review, with rollback or recovery prepared before change.
- Template-based field installation
- Alignment of door to latch
- Access-control sequence
- Egress that works mechanically
Acceptance, documentation and preventive maintenance
Cycling the opening repeatedly from both sides is the real test: secure, release, under door pressure, with power removed, on schedule, by credential, through the fire interface where one applies, and in after-hours alarm states. Then watch the latch engage and the door close and latch without scraping.
Deliver strike model, faceplate, voltage, fail mode, current, controller output, monitoring point, wiring path, photographs and test record. Keep templates and official instructions with the protected opening schedule and include alignment and fastener inspection in preventive maintenance.
Acceptance needs to test normal use, denied or alarm conditions, loss of network or power, notification, audit history and administrator recovery. Deliver protected configuration records, licenses, serials, diagrams, test evidence, support links and clearly owned exceptions.
- Normal-state and failure-state tests
- Record of opening and wiring
- Official instructions on file
- Alignment preventive maintenance plan
Our method, start to finish
The final system engineering depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Discover
Record people, assets, workflows, risk and installed systems.
System Engineering
Choose supported devices, licenses, integrations and the architecture behind them.
Install
Staging, labeling and commissioning run as controlled changes.
Validate
Run the operating scenarios, then hand over lifecycle records.
Information to gather before system engineering
Good decisions are easier when the security engagement team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Use cases and how staff respond
- Compatibility between devices and software
- Physical interfaces plus network and power
- Identity, cybersecurity and licensing
- Sign-off, support and lifecycle ownership
Questions that come up
These are common engineering assessment questions. A site-specific answer needs to be confirmed during discovery and system engineering.
Is door width enough information to select a strike?
No. Compatibility comes from lock, latch, frame, rating, preload, fail mode and monitoring.
Can the strike correct a door that sits wrong?
No. Fix the hinges, closer, frame and latch alignment first; a strike asked to cover a mechanical fault is doing the wrong job.
Is fail safe interchangeable with fail secure?
No. The two behave differently when power drops, and the choice has to satisfy code, egress and security requirements.
What needs to be recorded after field installation?
Opening photographs, model, faceplate, voltage, fail mode, monitoring, controller point, wiring and test results.
The manufacturer’s website is where software, firmware and technical files live, and that is where they stay. Firmware is not mirrored on KSEDCO servers.
Discuss a commercial security engagement
Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and system engineering conversation.