CueBridge

DeCA Phase I demo · synthetic data only





Demo accounts (synthetic):
admin / Demo123! — Administrator: everything, incl. audit log
cmanager / Demo123! — Category Manager: approves planograms, works exceptions
associate / Demo123! — Store Associate: works the exception queue

DeCA Phase I — Catalog Data Integrity & Planogram Sync

— SYNTHETIC DATA ONLY

Live monitoring — agent heartbeat

—
live round-trip latency (target < 500 ms)
—
avg self-check latency
—
process uptime
—
availability (synthetic 60-second checks)
One bar per synthetic agent self-check, fired every 60 seconds against the telemetry pipeline. Height = latency.

Exceptions by reason

Recent sync activity

No sync events yet.

POS Ingestion — change-data-capture feed

Simulates the commissary point-of-sale CDC (change data capture) feed: incremental item change events delivered over a secure API. Every event is checked against the validation rules — GTIN-12 check digit, case-pack consistency, item-vs-case dimensions, price drift vs catalog, category-code collisions, and discontinued SKUs still on an active layout. Failures go straight to the Exception Queue. Every batch is delivery-verified with a SHA-256 checksum and record count.

No batch run yet this session.

CSV Batch Import

Batch mode of the same feed for store systems that drop flat files. Columns: upc,description,brand,case_pack,item_l,item_w,item_h,case_l,case_w,case_h,price (optional: category_code)

Exception Queue

IDIngested (UTC)UPCDescriptionReasonDetailStatusResolution

Planograms

Marking a planogram Approved (Administrator or Category Manager) fires a two-way sync: the approved layout pushes to the store shelf system, and the store's acknowledgment plus on-shelf adjustments pull back — reverse-flow updates without republication. Click a row for full detail.

NameAisleItemsStatusApproved byApproved at (UTC)

Bidirectional Sync Log — delivery-verified

Every transfer, in both directions, is recorded with record counts and checksum verification: what was sent, what was received, and what was lost — so "no record loss" is visible on every line.

Time (UTC)Channel / PlanogramDirectionRecordsDelivery verification

Item Catalog

DescriptionUPC / GTIN-12BrandCategoryGPC familyGPC classCase pkItem L×W×H (in)Price

Daily Integrity Report

Loading...

Exports — CSV / JSON / XLSX

Ad-hoc extracts for buyer reporting, in the three formats the SOO calls out. Every export is written to the audit log.

Exceptions
Catalog
Sync log

Connection security

Probing public TLS endpoint...
  • HTTPS enforced end-to-end; this page reports the cipher suite actually negotiated with the public endpoint, re-probed every 5 minutes.
  • This demo environment runs TLS 1.3 (AES-128-GCM, shown above). The production deployment is specified in our proposal as AES-256 at rest and TLS 1.3/AES-256 in transit, with cryptographic details submitted for Government validation during the approved engineering design phase.
  • Sessions are short-lived, signed cookies: HttpOnly; Secure; SameSite=Lax.
  • Passwords stored salted and hashed (SHA-256); never in cleartext, never logged.
  • Every API route is role-gated; data access follows the signed-in role.

Availability & heartbeat

—
process uptime
—
availability (target 99.5%)
—
avg self-check latency (target < 500 ms)
Check time (UTC)EndpointResultLatencyDetail

Access control — role-based (RBAC)

RoleScopeDemo account

Signed in as . Switch accounts from the sign-in screen to see each role's scoped view.

Accountability

  • — events in the tamper-evident audit log (sign-ins, batches, approvals, resolutions, exports).
  • — open exceptions under remediation right now.
  • Administrators can review the full trail on the Audit Log page and export it as CSV, JSON, or XLSX.

Audit Log (Administrator)

Time (UTC)UserRoleActionDetail

Help & Training

What CueBridge does

CueBridge keeps commissary shelf data clean. Store systems send item changes over a change-data-capture (CDC) feed. CueBridge checks every event, parks the bad ones in a fix-it list, keeps planograms in sync both ways with the store, and shows the whole story on one dashboard — with delivery verification (record counts + SHA-256 checksums) on every transfer.

The five-minute tour

  1. Sign in as cmanager / Demo123! (Category Manager).
  2. Open POS Ingestion and click Generate & ingest synthetic CDC batch. Note the delivery line: sent / received / lost, plus the batch checksum.
  3. Open Exception Queue. Each red pill is a record that failed a rule: bad UPC check digit, case pack that does not match the catalog, item bigger than its case, a price that moved more than 2%, a category-code collision, or a discontinued SKU still sitting on an active layout.
  4. Click Resolve on a few rows and add a note. Use the filters (reason, date range, free text) to slice the queue. Reopen one to replay it.
  5. Open Planograms, click a row to see its items, then click Approve & sync. Watch the Sync Log: the layout pushes out to the store and the store's answer pulls back, each line verified.
  6. Open Overview: the heartbeat widget shows the monitoring agent checking the pipeline every 60 seconds. Open Security & Status for the full availability picture.
  7. Open Reports for the daily integrity report and CSV / JSON / XLSX exports.

Who can do what

  • Administrator (admin): everything, plus the Audit Log of every action.
  • Category Manager (cmanager): approves planograms and works exceptions.
  • Store Associate (associate): works the exception queue.

Documentation & support set (Phase I deliverables)

  • Administrator Manual — installation, configuration, RBAC administration, audit review procedures.
  • User Operating Guide — daily workflows for category managers and store associates.
  • Standard Operating Procedures (SOPs) — POS CDC feed operations, exception remediation, planogram approval & sync, replay/requeue handling.
  • Interactive training — this guided tour plus the live initial session and quarterly refreshers.
  • Tier-3 support — 30-minute response escalation path for unresolved issues.

Good to know

  • All data is synthetic. Nothing here touches a real store.
  • Every sign-in, batch, approval, resolve, and export is written to the audit log.
  • Sessions are secure cookies over HTTPS; passwords are stored salted and hashed.