docs: TallyFlow Scout marketing + Edge/Print/Capture feature refresh

Review tallyflow-assets-iot (TallyFlow Scout v0.5.3): Collect, Verify,
Locate with Edge remote reader / offline CSV locate. Clarify Scout does
not replace Core Assets. Refresh Edge, Print parent-container and multi-
unit identity notes, Capture share/offline/barcode notes, architecture,
use cases, capabilities, and website drafts after src/ repo pulls.
This commit is contained in:
TNB
2026-07-27 15:59:32 -04:00
parent cf1e09e1c4
commit 8f4ed8a306
23 changed files with 292 additions and 151 deletions
@@ -13,6 +13,7 @@ This note will contain ongoing code review findings across the TallyFlow ecosyst
- [x] tallyflow-print (print/encoding backend)-ui
- [x] tallyflow_spreadsheet_importer (Flutter spreadsheet import tool)
- [x] flutter_tallyflow_iot_rest_client (Flutter REST client for Edge)
- [x] tallyflow-assets-iot (**product: TallyFlow Scout**; Collect/Verify/Locate for Edge) — [[tallyflow-scout]]
## General Observations
(Notes will be added here as review progresses)
@@ -11,4 +11,7 @@ iOS implementation of PhotoTag (now TallyFlow Capture) — mobile photo + barcod
- Has submission docs (README-SUBMISSION.md)
## Note on Duplication
This is one of several implementations of capture functionality (compare to tallyflow-decode Flutter and phototag-web).
This is one of several implementations of capture functionality (compare to tallyflow-decode Flutter and phototag-web).
## Jul 2026 pull notes
- Offline categories cache; connection settings usable with Admin Lock; category filter; diagnostics upload with Admin PIN; multi-capture crash/race fixes; session counter persistence.
@@ -10,4 +10,8 @@ Web interface for PhotoTag (TallyFlow Capture).
- Likely mirrors some of tallyflow-web's asset/photo workflows
## Note on Duplication
Vue implementation of capture features that overlap with tallyflow-web. Good candidate for consolidation or clear branding separation in the new tallyflow.com site.
Vue implementation of capture features that overlap with tallyflow-web. Good candidate for consolidation or clear branding separation in the new tallyflow.com site.
## Jul 2026 pull notes
- **v2.2.x public share collections** — create/edit public shares, combine mode, SDG branding on public list, download/open fixes.
- Market as controlled external photo sharing for Capture web, not a full DAM.
@@ -1,33 +1,39 @@
# TallyFlow Edge Review (repo: tallyflow-iot)
**Tech Stack:** Rust (Cargo workspace) + Leptos (web UI)
**Product name:** TallyFlow Edge (repo/package still `tallyflow-iot`)
**Tech stack:** Rust (Cargo workspace) + Leptos CSR web UI
**Branches reviewed:** `develop` through `81fa9d8` (July 2026 pull)
## Structure
- `core/`: Main service/library
- RFID drivers (Impinj, Zebra, ATID ATF862 / Invengo XC-RF861 — same reader rebranded)
- Barcode support (Zebra, SNAPI)
- REST API v1
- Real-time tag streaming
- Reader config/control
- Runs as an always-on Windows or Linux service
- `web/`: Leptos CSR web interface
- Reader health monitoring
- Live tag streaming with filtering
- Start/stop controls
- Imports types directly from `core` (no duplication)
## Key Capabilities
- Hardware abstraction for multiple RFID vendors
- Real-time data pipeline from readers → REST → web UI
- Designed for always-on Edge deployment
- Strong documentation (REST_API.md, LIBRARY.md, etc.)
- `core/` — service/library
- RFID drivers: Impinj, Zebra, **ATID ATF862 / Invengo XC-RF861 (Master mode)**
- Barcode: SNAPI / Aurora / wedge paths
- **Remote reader** REST API (mobile/handheld submit — used by **TallyFlow Scout**)
- REST API v1, live tag streaming, reader start/stop/health
- **Reader-side filtering** (for quotes such as RMS tunnel/filter needs — validate in field)
- Keyboard wedge + optional lookup filter (e.g. Assa Abloy patterns)
- Egress processors: CSV logger, REST, AMQP → TallyFlow
- **MCP** Streamable HTTP at `/mcp` (health, readers, tags; statistics-oriented skills expanded)
- Windows Service install path
- `web/` — Leptos UI: reader health, live stream/filter, start/stop, improved statistics display
## Relevance to TallyFlow Platform
- Primary ingestion layer for RFID/Edge data
- Feeds the web app, reporting, and exception systems
- Complements tallyflow-web (which consumes the data)
## Key capabilities (market carefully)
## Next Steps for Review
- Inspect `core/src/` for reader driver implementations
- Review REST API endpoints in REST_API.md
- Check web/ Leptos components for UI patterns
- Multi-vendor fixed RFID + remote/handheld readers under one site edge
- Unified tag feed → CSV / REST / AMQP
- Ops UI without vendor tools
- MCP read-oriented copilot surface (not autonomous dock control by default)
- Companion handheld: [[TallyFlow Scout]] (Collect / Verify / Locate)
## Relevance
- Primary **site edge** ingestion for docks, tunnels, and multi-reader plants
- Can feed Core via AMQP; can stand alone with CSV/REST and customer apps (e.g. Alice+Olivia console)
- Scout is the supported mobile remote-reader experience for Edge
## Next review steps
- Confirm shipped MCP tool list vs docs after statistics/MCP skill commits
- Document ATF862 Master mode hardware prerequisites
- Field-test reader-side filtering before strong marketing claims
@@ -85,3 +85,15 @@ Operator → TallyFlow Print app → Print API → Print worker → Zebra printe
- Additional bug fixes and profile enhancements.
*Last updated: 2026-07-17 by Hermes Agent (after develop pull using hermes_agent_ed25519 key)*
## Recent Changes (develop pull - 2026-07-27)
**Theme:** Parent container namespace + safer multi-unit retail identity + register preflight.
- Reserve **SDG RAIN assignment 8000** for parent container tags (Internal/simple CIN and part-serial reject 8000 for customer unit tags).
- Inject **per-unit AI 21** into retail GS1-128 companion barcodes (quantity > 1 no longer identical GTIN+lot barcodes).
- **Reject print-and-register** when units share identity tags (post-print preflight; clear Core collision error).
- Print UI: hide retail parent linking; require serials for multi-unit register; same 8000 parent reservation on Internal tags.
*Marketing implication:* Prefer concrete language — parent/container EPC namespace, unique serials on multi-unit retail companions, register blocked on duplicate identities — over vague “better serialization.”
@@ -0,0 +1,43 @@
# TallyFlow Scout Review (repo: tallyflow-assets-iot)
**Product name:** TallyFlow Scout
**Package:** `tallyflow_scout`
**Version reviewed:** 0.5.3+10 (master `2c479fb`, July 2026)
**Tech stack:** Flutter (Material 3), `flutter_hardware_scanner`, optional camera barcode (ML Kit), HTTP client to Edge
## Role in platform
Handheld **Collect / Verify / Locate** app for **TallyFlow Edge**.
**Not** a replacement for **TallyFlow Assets** (`tallyflow_mobile` → Core).
## Destinations
1. **Collect** (nav key still `navUpdate` in l10n) — scan list, submit to Edge remote reader API or export CSV
2. **Verify** — GS1 barcode identity vs RFID EPC encodings (`gs1_verify_match`); optional auto-confirm
3. **Locate** — offline seek-and-find / geiger (`locate_screen`, RSSI colors aligned with Assets pick-list palette)
## Integration
- Client: `lib/services/tallyflow_iot_client.dart``{baseUrl}/api/v1/health`, `/reader/barcode`, `/reader/rfid`
- Remote reader must exist on Edge (`type = remote`, enabled); reader name must match Settings
- Offline: Collect + CSV + Locate without server; banner when Edge unreachable
## Hardware
- Android industrial devices via hardware scanner plugin (XR2, ATID AARs, SEUIC, URFID noted in tree)
- Camera barcode fallback when no hardware scanner / init failure
- Desktop: simulator always on
## Notable modules
- `epc_mask.dart`, `sdg_rain_decode.dart` — EPC type / Internal part decode
- `scan_csv_exporter.dart` — CSV share/save
- `l10n` — English + Spanish
- Tests cover EPC mask, GS1 verify match, locate finds, CSV export, symbology filter
## Marketing guardrails
- Say **Scout works with Edge**; **Assets works with Core**
- Three sections only: Collect, Verify, Locate
- Locate offline is a real differentiator for floor find without Core
- Do not claim full asset CRUD, zones, or scan-and-print in Scout
+49 -33
View File
@@ -1,6 +1,6 @@
# TallyFlow User's Guide
**Version:** June 2026
**Version:** July 2026
**Purpose:** This guide provides an overview of TallyFlows full product capabilities for operators, administrators, and systems integrators.
---
@@ -29,7 +29,7 @@ TallyFlow is particularly well suited for industries requiring reliable identifi
### 1. TallyFlow Core (Web Application)
The central web platform for managing assets, tags, categories, zones, and reporting.
**Integration Hub:** TallyFlow Assets (Mobile), TallyFlow Print, TallyFlow Capture, and TallyFlow Edge all integrate with TallyFlow Core.
**Integration hub (Core):** TallyFlow Assets (Mobile), TallyFlow Print, and TallyFlow Capture integrate with TallyFlow Core. **TallyFlow Edge** can feed Core (e.g. AMQP) or stand alone (CSV/REST). **TallyFlow Scout** connects to **Edge**, not Core, and does not replace Assets.
**Key Capabilities:**
- Add and manage assets manually
@@ -43,14 +43,17 @@ The central web platform for managing assets, tags, categories, zones, and repor
- Core web can display and filter photos with tags (integration with Capture app)
- Integration points for external systems (ERP via API and webhooks)
### 2. Mobile App (Enroll)
Mobile application for field data capture and tag enrollment.
### 2. TallyFlow Assets (Mobile)
Core-connected mobile app for field asset work (`tallyflow_mobile`). **This is not TallyFlow Scout.**
**Key Capabilities:**
- Enroll new tags and associate them with assets
- Scan and update asset information in the field
- Lightweight inventory with optional zone moves
- Geiger-style seek & find for one or many assets
- **Scan-and-print** — trigger Print jobs from mobile enrollment/scan workflows
- Support for both barcode and RFID workflows
- Works offline with later synchronization
- Works offline with later synchronization to Core
**UX Design (Industrial Focus):**
- Built with Material 3
@@ -64,7 +67,11 @@ Desktop and mobile application (Flutter) paired with a Rust backend service for
- Strong **GS1-128 / Case Label** support (GTIN-14 treated as case labels, proper AI (21) serial handling)
- Dedicated **FSMA 204** 300dpi label templates and ZPL configs for food traceability compliance
- Pre-configured **workflow profiles** for popular use cases including **FSMA**, **SSCC** (Serialized Shipping Container Code), and internal-use barcode/RFID labeling
- Support for Simple tags, GS1 case tags, parent/child tag structures
- Support for Internal tags, GS1 case tags, parent/child tag structures
- **Parent container tags:** SDG RAIN assignment **8000** reserved for parent/container namespace (customer internal tags cannot use 8000)
- Retail GS1-128 companion barcodes can inject **per-unit AI (21)** serials so multi-unit jobs are not identical GTIN+lot barcodes
- Print-and-register **rejects** jobs when units would share identity tags (blocks Core collisions)
- CSV part-catalog import for parts + quantities to print
- Category names printed on labels
- Multiple printer management and connection testing
- Optional automatic registration of printed items as assets in TallyFlow Core
@@ -77,29 +84,38 @@ Desktop and mobile application (Flutter) paired with a Rust backend service for
- Orchestrator (category/zone proxy + Core registration)
### 4. TallyFlow Capture
Automated data capture system for fixed and high-volume scanning environments.
Mobile photo documentation linked to barcodes, RFID, jobs/orders, and categories (formerly PhotoTag). iOS + Android apps with web review.
**Key Capabilities:**
- Fixed RFID reader integration for continuous asset movement detection
- Gateway and edge processing for real-time data collection
- High-throughput receiving and shipping workflows
- Exception flagging and automated alerts
- Seamless handoff to TallyFlow Core for record updates
- Capture photos tied to scanned IDs and categories
- Offline-friendly capture with later upload (categories cacheable; GPS fallback when address lookup fails)
- Library / detail review; full-resolution viewing
- **Public share collections** (web) for controlled external photo access
- Android: barcode symbology selection in Settings; highlight scanned barcodes
- Integrates with Core for tagged photo visibility where deployed
### 5. TallyFlow Edge
Connectivity layer for sensors, gateways, and connected devices. Runs as an always-on Windows or Linux service.
Site edge service for fixed and remote RFID/barcode readers. Runs as an always-on Windows or Linux service (repo `tallyflow-iot`).
**Key Capabilities:**
- Real-time location tracking via Edge gateways and beacons
- Environmental sensor data (temperature, humidity, shock) linked to assets
- Automated status updates without manual scanning
- Edge-to-cloud data pipelines feeding TallyFlow Core
- Support for both short-range (BLE, RFID) and wide-area (LoRa, cellular) IoT networks
- RFID GPIO support for reader triggers and control
- Endpoint configuration available for Edge and Mobile readers
- ERP integration via keyboard wedge, database integration, and spreadsheet output
- Optional custom receiving or shipping user interface that integrates with an ERP system
- Compatible with TallyFlow Core deployed in the cloud or on-premises
- Multi-reader management (e.g. Impinj, Zebra fixed readers; ATID ATF862 Master mode where supported)
- Unified tag stream with ops UI (start/stop, health, statistics)
- **Remote reader API** for handhelds — used by **TallyFlow Scout**
- Reader-side filtering (site-specific; validate before promising)
- Egress: CSV/spreadsheet, REST, AMQP → TallyFlow Core
- Keyboard wedge (+ optional lookup) into focused ERP/apps
- MCP read tools for AI copilots (health/readers/recent tags — not autonomous dock control by default)
- Compatible with Core in cloud or on-premises, or standalone without Core
### 6. TallyFlow Scout
Handheld Flutter app for **Edge** floors (`tallyflow-assets-iot`). **Does not replace TallyFlow Assets.**
**Three sections:**
- **Collect** — scan barcode/RFID; submit to Edge as a remote reader, or export CSV offline
- **Verify** — GS1 barcode vs RFID EPC identity match (SGTIN/SSCC/GRAI/GIAI-style)
- **Locate** — seek-and-find by EPC/GTIN/part with geiger feedback; works offline without Edge
**Hardware:** Industrial Android scanners (e.g. Janam XR2, ATID, SEUIC, URFID); camera barcode fallback; desktop simulator for demos. EN/ES UI.
---
@@ -107,8 +123,8 @@ Connectivity layer for sensors, gateways, and connected devices. Runs as an alwa
TallyFlow supports multiple ways to bring tags and asset data into the system:
1. **Mobile App Enroll**
Field operators enroll tags directly via the mobile application.
1. **TallyFlow Assets (Mobile)**
Field operators enroll, inventory, locate, and scan-and-print against Core.
2. **TallyFlow Core (Web)**
Manual asset creation with tag assignment.
@@ -119,11 +135,11 @@ TallyFlow supports multiple ways to bring tags and asset data into the system:
4. **TallyFlow Print**
On-demand tag printing and encoding with optional automatic Core registration. Supports prefix/serialization logic, parent/child relationships, and category-aware labeling.
5. **TallyFlow Capture (Automated)**
Fixed readers and gateways automatically detect and record tag movements.
5. **TallyFlow Capture**
Photo + barcode/RFID documentation into Capture/Core workflows.
6. **Edge Devices**
Sensors and connected devices push location, condition, or status data directly into the platform.
6. **TallyFlow Edge (+ Scout)**
Fixed readers and Scout handheld Collect submit into the site edge feed (CSV/REST/AMQP/Core as configured).
---
@@ -131,7 +147,7 @@ TallyFlow supports multiple ways to bring tags and asset data into the system:
TallyFlow is a **distributor** of Atid handheld RFID readers (such as the AT909) to systems integrators. These devices are commonly used for mobile scanning and enrollment workflows.
The platform also supports fixed RFID readers, edge gateways, and sensor devices through the Capture and Edge modules.
The platform also supports fixed RFID readers through **TallyFlow Edge**, and handheld industrial scanners for **Assets** and **Scout**.
**Note:** TallyFlow does not currently provide native support for AEI (Automatic Equipment Identification) tags used in the rail industry.
@@ -140,9 +156,9 @@ The platform also supports fixed RFID readers, edge gateways, and sensor devices
## Typical Workflows
- **Asset Onboarding:** Print/encode a tag using TallyFlow Print → optionally register in Core.
- **Field Operations:** Use mobile app to locate assets, update status, or enroll new items.
- **Automated Receiving/Shipping:** Fixed readers (Capture) detect tagged assets moving through dock doors or checkpoints.
- **Condition Monitoring:** IoT sensors track environmental data tied to specific assets or shipments.
- **Field Operations (Core):** Use **Assets** to locate assets, update status, enroll, or scan-and-print.
- **Field Operations (Edge):** Use **Scout** Collect / Verify / Locate with Edge remote reader or offline CSV/locate.
- **Automated Receiving/Shipping:** Fixed readers via **Edge** detect tagged assets at docks/tunnels; Scout can add handheld reads to the same site feed.
- **Bulk Operations:** Import large numbers of assets via Excel.
- **Compliance & Traceability:** Use category, zone, tag, and Edge data for reporting and audit trails (e.g., FSMA 204 food traceability scenarios).