Filament Zkteco Adms Laravel Package

Product Decisions This Supports

• Feature prioritization: v1.0.1 makes attendance reporting more reliable by standardizing occurred_at for sorting, filtering, dashboards, and statistics while preserving recorded_at as the original device-local timestamp. This supports roadmap work around attendance dashboards, reporting accuracy, and auditability.
• Build vs. buy: For Laravel/Filament teams integrating ZKTeco ADMS devices, this package reduces the need to build device ingestion, timestamp normalization, timezone handling, and admin UI from scratch.
• Multi-tenant and multi-site rollout: The publishable filament-zkteco-adms-migrations stub and generated tenant migration timestamp support controlled tenant onboarding and migration workflows.
• Operational configuration: The configurable, searchable device timezone selector with PHP runtime fallback supports deployments across regions and reduces incorrect attendance attribution when device-local time differs from reporting time.
• Upgrade planning: The replacement of automatic migration loading with a publishable migration stub is an adoption/upgrade decision point. Teams should plan to publish and review migrations rather than relying on implicit loading.
• Dependency management: Requiring athwari/laravel-zkteco-adms v1.0.1 or newer makes the companion package version part of the product upgrade checklist for normalized timestamps and migration stubs.

When to Consider This Package

Consider this package when:

• You are building on Laravel and likely Filament for admin workflows.
• You need to integrate ZKTeco ADMS attendance devices without building the ingestion and reporting layer yourself.
• Attendance reporting must distinguish normalized reporting time (occurred_at) from original device-local time (recorded_at).
• You operate across timezones and need configurable device timezone selection with a runtime fallback.
• You need multi-tenant support and are comfortable with a publishable migration workflow.
• You can manage the required companion package version: athwari/laravel-zkteco-adms v1.0.1+.

Look elsewhere or defer adoption when:

• You are not using Laravel/Filament or do not use ZKTeco ADMS devices.
• Your team cannot accommodate the migration workflow change from automatic migration loading to published migration stubs.
• You need a fully managed attendance platform rather than an application-level package.
• You cannot validate or backfill historical attendance data after adopting normalized occurred_at semantics.
• You require integrations outside the package’s supported device/admin ecosystem.

How to Pitch It (Stakeholders)

For executives: This release improves attendance reporting accuracy and timezone correctness while giving teams more control over database migrations. It reduces custom development for ZKTeco device integration and supports multi-tenant, multi-site attendance workflows. The main adoption consideration is a planned upgrade that publishes and reviews migrations and validates historical reporting semantics.

For engineering: v1.0.1 standardizes occurred_at for reporting, sorting, filtering, and dashboard statistics, while retaining recorded_at for device-local audit context. It replaces automatic migration loading with a publishable migration stub, generates tenant migration timestamps on publish, adds a configurable searchable timezone selector with PHP runtime fallback, and requires athwari/laravel-zkteco-adms v1.0.1+. Upgrade work should include publishing migrations, confirming tenant migration behavior, validating timezone configuration, and checking reports/dashboards against expected historical data.