35 lines
3.9 KiB
Markdown
35 lines
3.9 KiB
Markdown
# TallyFlow Clarifying Questions
|
|
|
|
**Purpose:** Persistent record of clarifying questions asked during daily product research cycles to avoid repetition and build on prior knowledge. Questions are cycled by weekday product focus.
|
|
|
|
## Previously Asked Questions
|
|
|
|
*(No prior questions recorded as of start of cycle - June 2026)*
|
|
|
|
## Tuesday - Mobile App (Enroll, update, inventory, and locate)
|
|
**Question Asked:** How does the Mobile App handle asset 'locate' and inventory updates in offline mode, including sync behavior upon reconnection, and are there any specific features or limitations for use in large-scale environments like rail yards or manufacturing facilities with intermittent connectivity?
|
|
|
|
**Context/Notes:** This question builds on the brief mentions of offline sync and field operations in the User's Guide. It aims to clarify details for improving website content, documentation, and marketing around mobile reliability in challenging environments (e.g., rail, remote sites). Addresses potential gaps in integration with IoT/Capture for real-time locate.
|
|
|
|
**Date Asked:** Tuesday, June 16, 2026
|
|
|
|
## Wednesday - TallyFlow Print
|
|
**Question Asked:** What Zebra printer models and RFID tag encoding options (e.g., specific memory banks like EPC, TID, user memory; password protection; serialization/prefix logic) are supported or tested in TallyFlow Print, and how does the print job orchestration handle multi-printer environments, queuing, error recovery (printer offline, encoding failures), and safeguards against duplicate asset registrations when using the optional Core auto-registration feature?
|
|
|
|
**Context/Notes:** Builds on the known Zebra printer support, parent/child structures, multi-printer management, and optional registration in the User's Guide and code reviews. Targets gaps in hardware compatibility details, reliability for industrial/rail use cases, and integration robustness to improve docs, website feature descriptions, and marketing for on-site labeling workflows. Addresses potential AEI/rail-adjacent tag encoding questions indirectly through custom RFID support.
|
|
|
|
**Date Asked:** Wednesday, June 17, 2026
|
|
|
|
## Thursday - TallyFlow Capture
|
|
**Question Asked:** In TallyFlow Capture, which specific fixed RFID reader hardware (brands/models like Impinj R420/R680, Zebra FX series, or others) and communication protocols are natively supported or have integration examples, how does the edge/gateway processing handle real-time tag event filtering, deduplication, and local decision-making before syncing to Core, and what mechanisms are available for configuring and delivering automated alerts and exception notifications (e.g., email, SMS, webhooks, dashboard flags) in high-throughput environments like receiving docks or manufacturing lines?
|
|
|
|
**Context/Notes:** Builds on the high-level description of fixed reader integration, gateway/edge processing, exception flagging, and handoff to Core in the User's Guide, as well as the noted gap in AEI rail support and hardware requirements. Targets hardware compatibility details, edge vs cloud architecture, and alerting capabilities to improve website feature clarity, product documentation (e.g., User's Guide, code reviews), marketing for automated high-volume workflows, and positioning for industrial/rail-adjacent use cases. Addresses potential gaps in integration robustness, real-world deployment considerations, and exception handling details.
|
|
|
|
**Date Asked:** Thursday, June 18, 2026
|
|
|
|
**Source Code Review Note (2026-06-18):** Reviewed related repos (tallyflow-decode, tallyflow-iot, impinj-iot, zebra-iot, photomicroservice) in /Users/tnb/src/. High-level architecture confirms edge processing and multi-vendor reader support potential via MQTT/REST, but specific models and alert delivery details remain to be clarified with product owner. No changes to question needed.
|
|
|
|
## Other Days
|
|
- Monday (Core): [To be added next cycle]
|
|
- Friday (IoT): [To be added]
|