Rename product TallyFlow IoT → TallyFlow Edge across vault

Update product naming in docs, marketing, architecture, use cases, and capabilities materials. Rename related notes, screenshot folder, and marketing image filenames. Keep git/repo identifiers (e.g. tallyflow-iot) and generic industry IoT language unchanged.
2026-07-27 15:48:08 -04:00
parent 4d09d3195b
commit cf1e09e1c4
33 changed files with 128 additions and 128 deletions
@@ -6,13 +6,13 @@ This note will contain ongoing code review findings across the TallyFlow ecosyst
 - [x] phototag-swift (iOS Swift capture app)
 - [x] phototag-connector (Rust connector)
 - [x] phototag-web (Vue web interface)
- [x] tallyflow-iot (Rust core + Leptos web; RFID/reader management + REST API)
+- [x] tallyflow-iot (**product: TallyFlow Edge**; Rust core + Leptos web; RFID/reader management + REST API) — note: [[tallyflow-edge]]
 - [x] tallyflow-web (initial pass complete — core views + entities documented)
 - [x] tallyflow-decode (Flutter mobile app for tag decoding)
 - [x] tallyflow-print (print/encoding backend)
 - [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 IoT)
+- [x] flutter_tallyflow_iot_rest_client (Flutter REST client for Edge)

 ## General Observations
 (Notes will be added here as review progresses)
@@ -20,4 +20,4 @@ This note will contain ongoing code review findings across the TallyFlow ecosyst
 ## Action Items
 - [ ] 
 ## Architecture Notes
- **TallyFlow Core as central hub**: TallyFlow Assets (Mobile), TallyFlow Print, TallyFlow Capture, and TallyFlow IoT all integrate with TallyFlow Core (web) for asset registration, synchronization, reporting, and configuration.
+- **TallyFlow Core as central hub**: TallyFlow Assets (Mobile), TallyFlow Print, TallyFlow Capture, and TallyFlow Edge all integrate with TallyFlow Core (web) for asset registration, synchronization, reporting, and configuration.
@@ -1,4 +1,4 @@
-# tallyflow-iot Review
+# TallyFlow Edge Review (repo: tallyflow-iot)

 **Tech Stack:** Rust (Cargo workspace) + Leptos (web UI)

@@ -19,11 +19,11 @@
 ## Key Capabilities
 - Hardware abstraction for multiple RFID vendors
 - Real-time data pipeline from readers → REST → web UI
- Designed for always-on IoT deployment
+- Designed for always-on Edge deployment
 - Strong documentation (REST_API.md, LIBRARY.md, etc.)

 ## Relevance to TallyFlow Platform
- Primary ingestion layer for RFID/IoT data
+- Primary ingestion layer for RFID/Edge data
 - Feeds the web app, reporting, and exception systems
 - Complements tallyflow-web (which consumes the data)

@@ -71,7 +71,7 @@ Operator → TallyFlow Print app → Print API → Print worker → Zebra printe

 ## Roadmap / Integration Opportunities
 - ~~**Mobile (Assets) integration** for Scan-and-Print~~ — **Shipped:** mobile can trigger print jobs (reprint, on-demand encoding during field scans or enrollment).
- **IoT integration** — Expose print job status/events and printer health to TallyFlow IoT for unified dashboards and alerts.
+- **Edge integration** — Expose print job status/events and printer health to TallyFlow Edge for unified dashboards and alerts.

 ## Recent Changes (develop branch pull - July 2026)
 **Major theme:** CSV import for batch printing, GS1 Sunrise dual-carrier retail tags, custom field registration, internal profile standardization.
@@ -10,7 +10,7 @@

 ## Key Areas to Investigate
 - Asset / Zone management
- RFID / IoT integration points
+- RFID / Edge integration points
 - Reporting & exports
 - User workflows (receiving, movement, printing)
 - ERP integration surface (API and webhooks)
@@ -26,4 +26,4 @@
  - Reporting on zone durations, events, zone categories (`ReportZoneDurations.vue`, etc.)
  - Map-based visualization (`Map.vue`)
 - **Tech Notes**: Uses Leaflet for maps, Chart.js for reports, Vuetify for UI. Strong emphasis on ERP-adjacent data flows (imports, reports, exceptions).
- **Next**: Review API layer and shared components for integration patterns (RFID, printing, IoT).
+- **Next**: Review API layer and shared components for integration patterns (RFID, printing, Edge).
@@ -11,13 +11,13 @@ Dedicated mobile application for TallyFlow.
 - Appears to be the primary/official TallyFlow mobile client

 ## Relevance to Platform
-This repo represents the **mobile pillar** of TallyFlow, distinct from the web, IoT, print, and capture components.
+This repo represents the **mobile pillar** of TallyFlow, distinct from the web, Edge, print, and capture components.

 ## Status
 Initial structure review complete.
 ## Roadmap / Integration Opportunities
 - ~~Integration with **TallyFlow Print** for Scan-and-Print~~ — **Shipped:** scan existing asset or enroll → trigger print job for new/replacement labels from mobile.
- Integration with **TallyFlow IoT** for real-time location, sensor data, and zone-based workflows directly in the mobile Assets app.
+- Integration with **TallyFlow Edge** for real-time location, sensor data, and zone-based workflows directly in the mobile Assets app.

 ## UX Design
 - Built with **Material 3**
@@ -9,7 +9,7 @@
 ## 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.
+**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 Edge/Capture for real-time locate.

 **Date Asked:** Tuesday, June 16, 2026

@@ -29,14 +29,14 @@

 **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.

-## Friday - IoT Integration
-**Question Asked:** Building on the high-level IoT capabilities for real-time location tracking via gateways and beacons, environmental sensor data (temperature, humidity, shock), automated status updates, and edge-to-cloud pipelines supporting short-range (BLE, RFID) and wide-area (LoRa, cellular) networks, what specific IoT gateway hardware, beacon/sensor vendors or protocols (e.g., particular BLE beacons, LoRaWAN providers, cellular IoT modules), and data normalization approaches does TallyFlow IoT support or have tested integrations for? How are sensor readings and location events ingested, associated with asset records in Core, and used to trigger rules-based alerts, workflows, or status updates—especially in rail, manufacturing, or compliance-heavy environments—and what are the options for local edge processing vs. cloud-only handling to support intermittent connectivity or high-reliability needs?
+## Friday - Edge Integration
+**Question Asked:** Building on the high-level Edge capabilities for real-time location tracking via gateways and beacons, environmental sensor data (temperature, humidity, shock), automated status updates, and edge-to-cloud pipelines supporting short-range (BLE, RFID) and wide-area (LoRa, cellular) networks, what specific IoT gateway hardware, beacon/sensor vendors or protocols (e.g., particular BLE beacons, LoRaWAN providers, cellular IoT modules), and data normalization approaches does TallyFlow Edge support or have tested integrations for? How are sensor readings and location events ingested, associated with asset records in Core, and used to trigger rules-based alerts, workflows, or status updates—especially in rail, manufacturing, or compliance-heavy environments—and what are the options for local edge processing vs. cloud-only handling to support intermittent connectivity or high-reliability needs?

-**Context/Notes:** This question builds directly on the IoT section in the User's Guide and ties into known gaps around rail/AEI support, hardware specifics, and integrations (e.g., RFIDKnow partnership, environmental compliance). It incorporates insights from source code review of tallyflow-iot (new MCP support for AI agents, keyboard wedge, RFID write fixes, and TallyFlow_IoT_Datasheet.md) to seek clarification on production hardware support and event-driven workflows. Aims to improve website feature descriptions, product documentation, marketing for automated/sensor-driven use cases, and positioning for industrial/rail applications. Addresses potential gaps in concrete examples, vendor ecosystem, and edge intelligence details.
+**Context/Notes:** This question builds directly on the Edge section in the User's Guide and ties into known gaps around rail/AEI support, hardware specifics, and integrations (e.g., RFIDKnow partnership, environmental compliance). It incorporates insights from source code review of tallyflow-iot (new MCP support for AI agents, keyboard wedge, RFID write fixes, and TallyFlow_IoT_Datasheet.md) to seek clarification on production hardware support and event-driven workflows. Aims to improve website feature descriptions, product documentation, marketing for automated/sensor-driven use cases, and positioning for industrial/rail applications. Addresses potential gaps in concrete examples, vendor ecosystem, and edge intelligence details.

 **Date Asked:** Friday, June 19, 2026

-**Source Code Review Note (2026-06-19):** Pulled latest from tallyflow-iot develop branch (96b5fe7). Key additions include initial MCP (Model Context Protocol) support for AI agents via 'rmcp' crate serving at /mcp with tools for API info, health, reader status; keyboard wedge filter/lookup for Assa Abloy/customers; RFID write command fixes (saving PC Word); new TallyFlow_IoT_Datasheet.md (393 lines); consistent icons and barcode printing in tag stream. Confirms ongoing multi-vendor RFID/IoT evolution and AI integration potential. No changes to question needed; question targets production hardware and workflow details not yet in code/docs.
+**Source Code Review Note (2026-06-19):** Pulled latest from tallyflow-iot develop branch (96b5fe7). Key additions include initial MCP (Model Context Protocol) support for AI agents via 'rmcp' crate serving at /mcp with tools for API info, health, reader status; keyboard wedge filter/lookup for Assa Abloy/customers; RFID write command fixes (saving PC Word); new TallyFlow_IoT_Datasheet.md (393 lines); consistent icons and barcode printing in tag stream. Confirms ongoing multi-vendor RFID/Edge evolution and AI integration potential. No changes to question needed; question targets production hardware and workflow details not yet in code/docs.

 ## Monday - TallyFlow Core (Web Application)
 **Question Asked:** Building on the high-level description of TallyFlow Core as the central web platform for asset management, reporting, and integrations (including manual asset creation, Excel import, category/zone configuration, exception management, and ERP integration points), what specific features does the Core web application offer for advanced asset search and filtering (e.g., by zone history, custom attributes, tag status, movement events), customizable reporting and dashboard capabilities (including scheduled reports, export formats like CSV/PDF, visualization types such as charts or maps, zone duration analytics), exception management workflows (flagging rules, assignment, escalation, resolution tracking, notifications), role-based access control (RBAC) and multi-user collaboration features, and the extent of its REST API, webhooks, or other integration mechanisms for real-time or batch sync with ERP systems (SAP, NetSuite, JD Edwards)?
@@ -48,9 +48,9 @@
 **Source Code Review Note (2026-06-22):** Reviewed recent commits in tallyflow-web (v1.33.2 hotfixes for tags array conversion, duplicate handling, import startsWith fix; v1.33.1/1.33.0 with import-zone feature merged). Confirmed strong emphasis on zone/asset import, exception handling, and reporting. No changes to question needed; question seeks production details on search, RBAC, API surface, and dashboard customization not fully documented yet.

 ## Tuesday - Mobile App (Enroll, update, inventory, and locate) [June 23, 2026 Cycle]
-**Question Asked:** Building on the high-level description of the Mobile App for field enrollment, scanning, updates, locate, and inventory, what specific details exist around the enrollment workflow (required/custom fields, support for bulk/rapid scanning, parent-child asset association during enrollment, photo attachments or condition logging, validation against duplicates or existing records), mobile UI/UX considerations for industrial environments (e.g., large buttons, glove-friendly, dark mode, offline-first design), integration points with TallyFlow Print (e.g., triggering print jobs from mobile during enrollment), TallyFlow Capture/IoT (real-time locate handoff), and Core (sync priorities, conflict resolution), and any support for advanced locate features like indoor positioning, asset history trails, or proximity alerts?
+**Question Asked:** Building on the high-level description of the Mobile App for field enrollment, scanning, updates, locate, and inventory, what specific details exist around the enrollment workflow (required/custom fields, support for bulk/rapid scanning, parent-child asset association during enrollment, photo attachments or condition logging, validation against duplicates or existing records), mobile UI/UX considerations for industrial environments (e.g., large buttons, glove-friendly, dark mode, offline-first design), integration points with TallyFlow Print (e.g., triggering print jobs from mobile during enrollment), TallyFlow Capture/Edge (real-time locate handoff), and Core (sync priorities, conflict resolution), and any support for advanced locate features like indoor positioning, asset history trails, or proximity alerts?

-**Context/Notes:** This new question avoids repeating the previous Tuesday focus on offline sync/locate limitations and instead targets enrollment details, industrial UX, cross-product integrations (Print, Capture, IoT, Core), and advanced locate capabilities to improve website feature descriptions, User's Guide depth (currently high-level), marketing for field operations in rail/manufacturing/waste management, and documentation gaps around mobile as the primary on-site tool. Addresses known emphasis on mobile enrollment/on-site workflows and potential for tighter product integration.
+**Context/Notes:** This new question avoids repeating the previous Tuesday focus on offline sync/locate limitations and instead targets enrollment details, industrial UX, cross-product integrations (Print, Capture, Edge, Core), and advanced locate capabilities to improve website feature descriptions, User's Guide depth (currently high-level), marketing for field operations in rail/manufacturing/waste management, and documentation gaps around mobile as the primary on-site tool. Addresses known emphasis on mobile enrollment/on-site workflows and potential for tighter product integration.

 **Date Asked:** Tuesday, June 23, 2026

@@ -7,7 +7,7 @@

 ## Overview

-TallyFlow is an asset tracking and management platform designed to reduce time and material waste in operations that rely on physical assets, tools, and tagged items. It combines mobile data capture, web-based core management, on-site printing/encoding, automated capture, and IoT connectivity.
+TallyFlow is an asset tracking and management platform designed to reduce time and material waste in operations that rely on physical assets, tools, and tagged items. It combines mobile data capture, web-based core management, on-site printing/encoding, automated capture, and Edge connectivity.

 TallyFlow is particularly well suited for industries requiring reliable identification and traceability, including manufacturing, logistics, rail, and agriculture.

@@ -20,7 +20,7 @@ TallyFlow is particularly well suited for industries requiring reliable identifi
 - Fast asset enrollment and editing
 - Reduce time spent locating and managing assets  
 - Minimize material waste through better visibility and accountability  
- Provide practical, affordable RFID, barcode, and IoT solutions for systems integrators
+- Provide practical, affordable RFID, barcode, and Edge solutions for 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 IoT all integrate with TallyFlow Core.
+**Integration Hub:** TallyFlow Assets (Mobile), TallyFlow Print, TallyFlow Capture, and TallyFlow Edge all integrate with TallyFlow Core.

 **Key Capabilities:**
 - Add and manage assets manually
@@ -86,17 +86,17 @@ Automated data capture system for fixed and high-volume scanning environments.
 - Exception flagging and automated alerts
 - Seamless handoff to TallyFlow Core for record updates

-### 5. TallyFlow IoT
+### 5. TallyFlow Edge
 Connectivity layer for sensors, gateways, and connected devices. Runs as an always-on Windows or Linux service.

 **Key Capabilities:**
- Real-time location tracking via IoT gateways and beacons
+- 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 IoT and Mobile readers
+- 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
@@ -122,7 +122,7 @@ TallyFlow supports multiple ways to bring tags and asset data into the system:
 5. **TallyFlow Capture (Automated)**  
   Fixed readers and gateways automatically detect and record tag movements.

-6. **IoT Devices**  
+6. **Edge Devices**  
   Sensors and connected devices push location, condition, or status data directly into the platform.

 ---
@@ -131,7 +131,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, IoT gateways, and sensor devices through the Capture and IoT modules.
+The platform also supports fixed RFID readers, edge gateways, and sensor devices through the Capture and Edge modules.

 **Note:** TallyFlow does not currently provide native support for AEI (Automatic Equipment Identification) tags used in the rail industry.

@@ -144,7 +144,7 @@ The platform also supports fixed RFID readers, IoT gateways, and sensor devices
 - **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.
 - **Bulk Operations:** Import large numbers of assets via Excel.
- **Compliance & Traceability:** Use category, zone, tag, and IoT data for reporting and audit trails (e.g., FSMA 204 food traceability scenarios).
+- **Compliance & Traceability:** Use category, zone, tag, and Edge data for reporting and audit trails (e.g., FSMA 204 food traceability scenarios).

 ---

@@ -163,15 +163,15 @@ TallyFlow is designed to work alongside existing systems:
 - No native AEI rail tag support
 - TallyFlow Print requires a local print server (Print API + Worker) for production use
 - Some advanced rail-specific compliance features are not yet implemented
- IoT and Capture modules may require additional gateway hardware and configuration
+- Edge and Capture modules may require additional gateway hardware and configuration

 ---

 ## Getting Started

-1. Work with your systems integrator to deploy TallyFlow Core and any required backend services (Print, Capture, IoT gateways).
+1. Work with your systems integrator to deploy TallyFlow Core and any required backend services (Print, Capture, Edge gateways).
 2. Configure categories, zones, and org settings in Core.
-3. Install the Mobile App, TallyFlow Print, and/or Capture/IoT components as needed.
+3. Install the Mobile App, TallyFlow Print, and/or Capture/Edge components as needed.
 4. Begin enrolling, printing, or automatically capturing tagged assets using the methods that best fit your operation.

 For detailed Print-specific instructions, see the **TallyFlow Print – User Guide**.