888-973-2867
Solution Headline Goes Here
Sub-headline text goes here underneath the main headline. This line of text is not absolutely necessary, but can help in providing extra context or intent for the solution being showcased on this page. 1-3 lines of text.
The Problem
This is the body text for the problem section. As the name implies, this section is intended to be an introduction to the problems faced in regards to the solution we are proposing, and framing that we know how to solve these problems. This may either span a broad/generic scope, or be more industry-focused, although that would more likely be for the child pages of a solution, which hone in more on how a solution applies to a specific industry. This section is universal and should be included in every landing page, unless somehow there's no reason for it, which I personally doubt since why sell a solution that isn't solving a discernable problem?
Section includes full or content-width background toggle. Content-width gives the rounded inset image treatment. Background can be image or video. Add background image only when the solution warrants emotional framing; leave blank for solid color otherwise. Whatever you do, the body text width can be adjusted to cover more/less of the image/video or background.
WHO THIS SERVES
Heading
Body text, used to give insight, or moreso a preview into the child page, which is the point of this section; acting as a routing point from the main broad solution, to a more in-depth, industry specific version of the solution landing pages. Therefore, this section has no business being placed in child pages, nor does it really have any business being in a parent page that doesn't have or require child pages, unless you want to specifically point at specific audiences with CTAs, and route them to the contact/quote page. Otherwise, remove this section entirely.
By default, this text column takes the full content width if there is no image. If you include an image, it would by default go to 60% of the width, image taking the remaining width, and can be adjusted via slider.
Heading
Body text.
Heading
Body text.
HOW WE APPROACH THIS
Heading
First instance of this section — methodology cards. 4 columns recommended for "How We Approach This" with numbered eyebrows ("01", "02", "03", "04"). Card content alignment: top (default). No card background images on this instance — text-only for clean methodology feel. Card min-height optional; set to ~280px if cards have wildly different body lengths
Heading
Body Text
Heading
Body text
Heading
Body text
DEEP DIVE SECTION (Optional)
Block Heading
Body text, used for deeper explanations and component-based breakdowns of a solution. Each block of this section is intended to be used to break down each individual component or topic of a solution. Include an image if possible; takes half of the section, otherwise text takes full content width. Images can be positioned left or right; it's recommended to alternate sides for each block.
May not be neccessary for outcome-driven solutions (Alyssa's Law, Cellular Resilience capability-focused parents). Critical for component-heavy solutions (Upfitting, SMART Vehicle, Rugged Compute). Each block has anchor_id — to be used for jump navigation and acts as an anchor linik (e.g., /pages/.../#compute, connectivity, video). Per-block image position can alternate left/right for visual rhythm. Callout tags useful for "Brands covered" or "Key components".
Heading
Body text, used for deeper explanations and component-based breakdowns of a solution. Each block of this section is intended to be used to break down each individual component or topic of a solution. Include an image if possible; takes half of the section, otherwise text takes full content width. Images can be positioned left or right; it's recommended to alternate sides for each block.
Heading
Body text, used for deeper explanations and component-based breakdowns of a solution. Each block of this section is intended to be used to break down each individual component or topic of a solution. Include an image if possible; takes half of the section, otherwise text takes full content width. Images can be positioned left or right; it's recommended to alternate sides for each block.
WHY SECTOR FOR THIS SOLUTION
Heading
Second instance of this section — positioning cards. 3 columns recommended for "Why Sector For This". Visually differentiate from first Approach instance: no numbered eyebrows, use background images per card (deployment photos, team photos, brand wall). Card content alignment: center if cards are short, top if they have body text. This is the section to remove if Why Sector content would feel redundant after the first Approach instance
Heading
Body text.
Heading
Body text.
PROCESS SECTION (Optional)
Optional subheading, not necessary unless it is felt some context or introduction is needed before breaking down the process. Skip this section for solutions where the engagement isn't a clear process (pure product-category solutions)
Tell us about your situation
Description text
Sector specs the build
Description
You review and approve
Description
We source, configure, and support
Description
WHAT OUR CUSTOMERS SAY
Quote. Remove if you don't have real quotes. Background image optional with overlay. Can also add avatar photo.
COMPARISON TABLE SECTION (Optional)
| Sector | Buying Direct | |
|---|---|---|
| Component compatibility | ✓ | ✗ |
| Installation guidance | ✓ | ✗ |
| Ongoing support | ✓ | ✗ |
| Warranty coverage | ✓ | ✗ |
FEATURED PRODUCTS FOR THIS SOLUTION
View all products →NHP-P100 - IP Controller
HanwhaPowered by OnCAFE IP Controller supporting (1) door featuring (1) Wiegand/OSDP reader port (up to 2 OSDP Readers) (3) Supervised Inputs up to (2) ...
View full detailsNHP-P200 - IP Controller
HanwhaPowered by OnCAFE IP Controller supporting (2) doors featuring (2) Wiegand/OSDP reader ports (up to 4 OSDP Readers) (5) Supervised Inputs up to (4...
View full detailsNOP-IC2 - Intelligent Controller
HanwhaPowered by OnCAFE Intelligent controller supporting (2) doors featuring (2) Wiegand/OSDP reader ports up to (16 OSDP Readers) (8) High-Precision S...
View full detailsNOP-RI2MS - Downstream Reader Interface Panel
HanwhaA downstream reader-interface panel supporting (2) Wiegand/OSDP reader ports (6) High Precision Supervised alarm inputs (2) Unsupervisered Dedicat...
View full detailsNOP-IO168S - Downstream I/O Interface Panel
HanwhaAccess control I/O expansion panel with (16) high-precision supervised inputs and (8) Form-C relay outputs for auxiliary device and zone control e...
View full detailsNOD-AX10S - Mullion Mount Credential Reader
HanwhaMulti-technology mullion reader 13.56 MHz (NFC) 125 kHz (PROX) Bluetooth BLE 5.3 Auto-Detect for Wiegand or OSDP infrastructures Remote firmware u...
View full detailsNOD-AX15S - Mullion Mount Credential Reader w/ Keypad
HanwhaMulti-technology mullion keypad reader 13.56 MHz (NFC) 125 kHz (PROX) Bluetooth BLE 5.3 Auto-Detect for Wiegand or OSDP infrastructures Remote fir...
View full detailsNOD-AX20S - Single Gang Credential Reader
HanwhaMulti-technology single gang reader 13.56 MHz (NFC) 125 kHz (PROX) Bluetooth BLE 5.3 Auto-Detect for Wiegand or OSDP infrastructures Remote firmwa...
View full detailsNOD-AX25S - Single Gang Credential Reader w/ Keypad
HanwhaMulti-technology single gang keypad reader 13.56 MHz (NFC) 125 kHz (PROX) Bluetooth BLE 5.3 Auto-Detect for Wiegand or OSDP infrastructures Remote...
View full detailsNOC-60L8 - Credential - Fob
HanwhaHigh-security smart keyfob credential with MIFARE DESFire® EV3 technology EAL 5+ security certification 13.56 MHz operating frequency Typical read...
View full detailsBRANDS FOR THIS SOLUTION
Answer
Answer
Answer
RELATED RESOURCES
Need a configured solution for your agency?
Our tech team works directly with law enforcement, fire, and EMS to spec, source, and deploy the right technology.

