The integrated dual-screen counter terminal provides separate staff and visitor interaction surfaces. It can coordinate staff calling, visitor confirmation and feedback, plus identity/document capture in one unit. Identify standard modules, options, and required software connections for each model.
Models and reference configurations
ModelReference configurationOperations and functionsCatalogue status
TYPJ-116 11.6-inch dual-screen terminal
Two 11.6-inch touchscreens with 1366×768 displays and an RK3288 platform; networking and extensions depend on configuration.
Staff calling, visitor guidance, and feedback; identity comparison, registration, and extensions require the relevant software.
Marked on sale in the 2026-08 catalogue; this does not confirm current stock or a standard project configuration.
Domestic-platform integrated counter terminal, no model code listed
Zhaoxin platform, 8 GB memory, 256 GB SSD, and UOS desktop operating system with two 11.6-inch touchscreens.
The catalogue lists document capture, reading, QR, recording, and camera modules; commission interface and application compatibility.
Configuration listed in the 2026-08 catalogue; sale status is not stated. Confirm current availability.
A closer look at each function
FunctionWhen to use itWhat users and systems doResult
Staff-side operation and visitor-side collaboration
For giving staff and visitors the information each needs during one interaction.
The staff screen runs configured calling, registration, or assistance software. The visitor screen presents guides, examples, confirmation, and ratings, with content deliberately shared rather than mirroring the whole internal desktop.
The screens have defined workflow roles rather than merely acting as an extended desktop.
Identity verification and code reading
For steps requiring identity documents or electronic credentials.
The configured reader and camera support identity comparison, while the QR module reads paper or mobile codes. Confirm supported documents, comparison software, and business connections separately.
Capture and verification are defined separately instead of treating a camera as every possible identity-check capability.
Document capture and service registration
For collecting electronic supporting material and recording visitor confirmation.
Configure document capture and registration software for the chosen model and pass the result into the relevant workflow. Fingerprints, printing, and external scanning require individual confirmation.
The terminal has defined input and confirmation tasks linked to its service record.
Recording and accessibility options
For counters needing authorised service records or additional communication support.
Recording modules work with management software to retain authorised interactions. Voice, image, and video assistance are selected for users and the setting, with software access and permissions demonstrated before inclusion.
Each extension has a defined scope rather than being described as universally standard.
How software, terminals and interfaces work together
ComponentRole in the workflowDependencies and integration
Two touchscreens and staff/visitor software
Separates staff operation from visitor confirmation.
Confirm display sizes, touch behaviour, and application environments by model.
Identity, scanning, and document peripherals
Provides the required reading, code, and capture inputs.
Check options together with drivers and interface software rather than inferring them from appearance.
Calling, registration, feedback, and recording software
Connects the two sides to the same service workflow.
Commission integration with the existing applications; dual-screen hardware does not connect business systems on its own.
Example: staff and visitor screens support one verification step
Staff open the service on the inner screen and select the required capture module.
The visitor reads a card or code and reviews the confirmation view on the outer screen.
Document capture and information confirmation follow the workflow, with staff explaining complex issues.
Staff request feedback after completion and link authorised registration and interaction records.
What the service producesBoth sides have a defined place in the workflow, and key confirmations do not depend solely on verbal prompts.
