Project fit & buying priorities
Government-project integrators, identity vendors, facility operators and HR information teams can assess the workflow, integration and ongoing support together. Operations should define tasks and exceptions, IT should validate interfaces and access, and procurement should compare complete configurations and service scope.
Define verification mode, user population, controller interface and offline policy. Keep identity matching and door authorization responsibilities explicit.
From field action to a complete record
- 01Enroll personnel under project rules
- 02Capture palm-vein samples and check quality
- 03Verify identity and request authorization
- 04Return an access or attendance event
System integration & delivery responsibilities
Use person ID, verification, authorization, device, shift, attendance event as the integration checklist. Define field ownership, required values and exception handling. Complete one representative job from terminal to API and backend review before scaling to more teams or sites.
SOTEN supplies confirmed device configurations, capture modules and SDK integration. Solution partners own business rules, matching services, access and deployment. Review tender qualifications and compliance documents for the exact delivery configuration.
Turn requirements into testable selection criteria
| Criterion | Confirm with the project team | Evidence to request |
|---|---|---|
| Use and configuration | Confirm capture methods, environment and operator interaction against the criteria above | Representative jobs, tags and peripheral list |
| Systems and interfaces | Enrollment / verification / access / attendance application version, fields, SDKs and protocols | Installable software, API specification and test account |
| Operations and support | Actual shifts, power, network, mounting and spare-unit plan | Full-shift test, installation drawing and support responsibilities |
Product platforms to evaluate
Select a platform by workflow, then confirm the branch, operating-system version and modules. The suggestions below do not mean every option is included in every configuration.
Palm-vein projects use the corresponding device and SDK solution. The platforms below are candidates for mobile forms, multimodal enrollment or supporting workstations; they do not imply palm-vein capture is standard on every version. Confirm the dedicated device, mounting and controller interfaces with the team.
B81
Document & identity captureIdentity-capture platform; confirm SDKs and interfaces for the selected document and biometric modules.
View platform and configurations ↗
DH83
Multimodal enrollment workstationMultimodal enrollment candidate; validate capture modalities, workflow and project data formats.
View platform and configurations ↗
H81
Mobile forms & supporting workstationMultifunction tablet for business forms and capture options; select the system platform and module combination.
View platform and configurations ↗Pilot validation & procurement acceptance
Test hand positions, ambient light, repeat attendance and outages, including event deduplication and revoked access.
- Operations: confirm completion, exception review and result retrieval against real workflows.
- IT / integration: verify fields, permissions, offline recovery and duplicate handling.
- Procurement / support: freeze the tested device, software and accessories, and agree delivery, spares and service terms.
Questions before the project starts
Can this connect to our existing system?
Enrollment / verification / access / attendance are integration targets, subject to application compatibility, interface access and SDK validation. Share the software version, API specification and an anonymized workflow sample for a device pilot. Agree device supply, integration and rollout as explicit work packages.
What should we prepare before selecting pilot devices?
Provide document protocols, capture modalities, template formats, SDK requirements, user population and anonymized test material. Include deployment region, estimated quantity, project stage and intended rollout date to define candidate configurations and a test plan.
