04. Discovery, Architecture & Pilot  •  TECH & PILOT
CLIENT & FULFILLMENT ENTERPRISE
LOWE-MARTIN GROUP • EST. 1908
•
LMX SOLUTIONS FULFILLMENT • OMNICONNEX
×
COMMERCIAL CREATIVE & AGENTIC AI PARTNERS
BRILLIANTZ COMMERCIAL & BRAND SYSTEMS
•
Cogneris. SANDY PLATFORM & PACE AI

Integrated Architecture, Technical Discovery Questionnaire & 90-Day Pilot Roadmap

Classification: CONFIDENTIAL — Cogneris Technical & Commercial Blueprint

Client Target: The Lowe-Martin Group / LMX Solutions

Date: 2026-11-18

Version: 1.0


1. End-to-End Integrated Architecture: The PACE × Sandy Bridge

The diagram below illustrates how Offering 2 (Commercial CRM & RFx Engine on the Sandy Platform) and Offering 1 (PACE Agent Assistant for Planning & Scheduling) operate either independently or as an integrated closed loop across Lowe-Martin's Ottawa and Mississauga operations:

flowchart TB subgraph External["External Demand & Procurement Channels"] T1["Public Tenders
(CanadaBuys, OECM, Merx, Biddingo)"] T2["Enterprise RFPs / Inbound Email RFQs"] T3["OmniConnex e-Business Portals"] end subgraph Offering2["OFFERING 2: Sandy Commercial CRM & RFx Engine"] S_RAD["Opportunity Search Radar
(External Tenders + Internal PACE Reorder Mining)"] S_MAT["Evidence-Based Team Matcher
(Buyer → Rep + LMX/Packaging Specialist)"] S_BRF["6-Part Editable Account Strategy Brief
(Commercial Context + PACE History)"] S_RFX["RFI / RFP / RFQ Bid Desk System
(Lot Parser, Go/No-Go, Compliance Matrix)"] S_OUT["Closed-Loop Outcome & Fairness Ledger"] S_RAD --> S_MAT --> S_BRF --> S_RFX --> S_OUT end subgraph Bridge["THE PACE × SANDY INTEGRATION BRIDGE"] BR_REQ["Normalized Job Spec Payload
(JSON/XML: Parts, Quantities, Stocks, Operations, Due Date)"] BR_RES["Approved Costing, Lead-Time Feasibility &
Post-Job Actual Margin Feedback"] end subgraph Offering1["OFFERING 1: PACE Agent Assistant (Planning & Scheduling)"] P_GATE["Spec Validator & Missing-Spec Gate"] P_HIST["Historical Job Look-Alike &
Actual-vs-Estimate Variance Analyzer"] P_PLAN["Multi-Plant Production Route Planner
(Ottawa vs. Mississauga / Offset vs. Digital)"] P_SCHED["Live Schedule & Readiness Co-Pilot
(Capacity, Paper POs, Proofs, Rush Simulator)"] P_GATE --> P_HIST --> P_PLAN --> P_SCHED end subgraph LoweMartinEnv["Lowe-Martin ePS Pace & Plant Backbone"] PACE_API["ePS Pace SOAP Web Services & InvokeAction
(EstimateRequest, CloneObject, calculateEstimate)"] PACE_DB["ePS Pace PostgreSQL Read Replica / Views
(Estimate, Job, JobCost, InventoryItem, PurchaseOrder)"] PACE_CON["PaceConnect Inbound / Outbound Triggers"] PFLOW["PACE Scheduling (JobPlan) /
PrintFlow 4D APS & Auto-Count 4D DMI"] end T1 & T2 --> S_RAD T2 --> P_GATE T3 -.->|"Inventory & Reorder Signals"| S_RAD S_RFX --> BR_REQ --> P_GATE P_PLAN -->|"Draft Estimate (Pending Estimator Review)"| PACE_API PACE_DB -->|"Read-Only Historical & Inventory Context"| P_HIST & P_SCHED & S_RAD & S_BRF PACE_CON -->|"Live Milestone Events"| P_SCHED & S_OUT P_SCHED <-->|"Capacity & Rush Simulation"| PFLOW P_SCHED & PACE_API --> BR_RES --> S_RFX & S_OUT

2. Technical & Operational Discovery Questionnaire for Lowe-Martin

Before finalizing the integration adapters or starting a 90-day pilot, this targeted discovery checklist establishes the exact technical and operational baseline across Sales, Estimating, Production Planning, and IT.

Section A: ePS Pace Core Environment & API Footprint (For IT / PACE Admin)

  1. PACE Version & Hosting:
  • What exact version and point release of ePS Pace is currently running in production (e.g., Pace 34.x / 35.x / 36.x)?
  • Is PACE hosted on-premise inside Lowe-Martin's network (Ottawa/Mississauga data centers) or in ePS's managed cloud environment?
  1. Multi-Plant Configuration (Ottawa vs. Mississauga):
  • Are the Ottawa and Mississauga plants configured as separate Company/Plant entities inside a single PACE database, or separate PACE instances?
  1. API & PaceConnect Licensing:
  • Is the PACE Web Services API (ReadObject, CreateObject, UpdateObject, FindObjects, CloneObject, InvokeAction) enabled and licensed?
  • Is PaceConnect licensed for inbound/outbound XML/JSON integrations, and what existing integrations currently use it (e.g., OmniConnex, accounting/GL, shipping carriers, prepress workflow like Kodak Prinergy / Esko)?
  1. Database Read Access:
  • Does Lowe-Martin maintain a read-only PostgreSQL reporting replica or ODBC/JDBC views for BI/reporting (e.g., Power BI, SSRS)?
  1. Customizations & UDFs:
  • What critical User Defined Fields (UDFs), custom XPath calculated fields, or custom objects have been added to Estimate, Job, Customer, or JobPart?

Section B: Estimating & Product Engineering (For Head of Estimating)

  1. Product Templates & EasyQuote:
  • Does Lowe-Martin actively use EasyQuote or configured JobProductType / EstimateRequest templates for standard commercial print, direct mail, or wide-format items?
  • Is the optional Price List Quoting module used for enterprise/contract accounts (e.g., OECM or LMX contract rate cards)?
  1. Complex Multi-Part & LMX Kitting Estimates:
  • How are multi-component jobs (e.g., folding carton + commercial booklet + variable-data card + LMX hand-kitting/fulfillment) structured inside PACE today—as a single multi-part Estimate (EstimatePart 1..N), linked combo estimates, or separate PACE + WMS quotes?
  1. Intake & Revision Pain Points:
  • Roughly how many estimate requests arrive per week, and what percentage require going back to sales/customer for missing specifications?
  • What is the average turnaround time today for: (a) a standard commercial quote, (b) a custom packaging/kitting quote, and (c) a multi-lot institutional RFP?

Section C: Scheduling & Shop-Floor Data Collection (For Production Planning / Ops)

  1. PACE Scheduling vs. PrintFlow 4D:
  • Does Lowe-Martin use native PACE Scheduling (JobPlan electronic board), PrintFlow 4D (dynamic constraint-based APS), or another scheduling tool across Ottawa and Mississauga?
  • Are all departments scheduled in the system (Prepress, Offset Press, Digital Press, Wide Format, Die-Cutting/Gluing, Bindery, Lettershop, LMX Hand-Kitting), or only press and major bindery?
  1. Shop-Floor Actuals (JobCost & Auto-Count):
  • How are actual run times, makeready hours, and spoilage captured on the floor—via Auto-Count 4D (DMI) machine counters, terminal barcode scans (PACE Data Collection), or manual timecards?
  • How reliably can we compare Estimate vs. actual JobCost across completed jobs?
  1. Promise-Date Commitments:
  • What is the current workflow when a sales rep or CSR needs a committed delivery date for a quote or rush order?

Section D: Sales, CRM, OmniConnex & Bid Desk (For Sebastián Gonzalez / Sales Ops)

  1. Current CRM & Pipeline Tooling:
  • What CRM (if any) do Account Executives currently use, and is it connected to PACE (Customer, Contact, Estimate, Job, Invoice) or maintained manually?
  1. Account & Opportunity Assignment:
  • How are new inbound inquiries, public tenders, and multi-division accounts currently assigned across Account Executives and LMX / Packaging / Direct Mail specialists?
  1. RFI / RFP / RFQ Bid Process:
  • How many formal RFIs/RFPs/RFQs does Lowe-Martin respond to per quarter (across OECM, CanadaBuys, Merx, enterprise retail, pharma, financial services)?
  • Where do boilerplate corporate responses (FSC/Bullfrog sustainability, security, equipment lists, SLAs) currently live?
  1. **OmniConnex & LMX WMS Boundary:**
  • How do OmniConnex storefront orders and LMX warehouse management (WMS) interact with PACE today?

3. Three Commercial & Rollout Options

We have structured the architecture so Lowe-Martin can adopt the capabilities in the sequence that delivers the fastest operational and commercial return:

Rollout TrackScopeBest When...Time to First Value
Track 1: Modular Dual-Track (Recommended)Deploy Offering 2 (Sandy CRM + Opportunity Radar + RFx Engine) for a pilot Sales pod simultaneously with Offering 1 (PACE Planning & Scheduling Assistant) for a pilot Estimating/Planning pod, connected via the PACE × Sandy Bridge.Sebastián wants immediate front-end revenue acceleration (tenders, cross-sell briefs, RFP turnaround) and faster PACE estimating/scheduling velocity.Weeks 3–4 (Read-only PACE context + RFx intake live); Weeks 6–8 (PACE draft creation & schedule checks live).
Track 2: Commercial & RFx First (Offering 2 Lead)Launch Sandy Account Strategy Briefs, External/Internal Opportunity Radar, and the RFI/RFP/RFQ Bid System first, seeded with a scheduled read-only export from PACE. Add deep SOAP/PrintFlow write-back in Phase 2.Sales & Marketing wants to move immediately with near-zero IT dependency on live PACE production APIs in Month 1.Weeks 2–3
Track 3: PACE Planning & Scheduling First (Offering 1 Lead)Launch the PACE Agent Assistant for spec validation, missing-spec triage, historical look-alikes, PACE estimate draft generation, and live schedule/PO risk alerts.Estimating and Production Planning capacity is the primary bottleneck throttling sales growth.Weeks 4–6

4. 90-Day Evidence-Gated Pilot Plan

Following Cogneris's evidence-gated methodology (established in Project Sandy), the 90-day pilot is designed with explicit gates, human-in-the-loop safety guardrails, and honest baseline-vs-pilot measurement:

flowchart LR G0["Weeks 1–2: Gate G0
Technical Discovery &
Baseline Audit"] --> G1["Weeks 3–5: Gate G1
Read-Only PACE Context,
Sandy Briefs & RFx Parser"] G1 --> G2["Weeks 6–8: Gate G2
PACE Estimate Drafts &
Schedule Feasibility Live"] G2 --> G3["Weeks 9–12: Gate G3
Controlled Operational Pilot
& Outcome Evaluation"]

Phase-by-Phase Deliverables

  1. Weeks 1–2 (Gate G0 — Discovery, Schema Audit & Baseline Freeze):
  • Complete the Technical Discovery Questionnaire with IT, Estimating, and Sales Ops.
  • Verify PACE WSDL / EstimateRequest objects, PostgreSQL read views, and PACE Scheduling / PrintFlow 4D schema in a staging/test environment.
  • Freeze historical baseline metrics (trailing 90-day RFQ-to-estimate cycle time, spec-rework frequency, RFP preparation hours, quote-to-win conversion, and multi-division attach rate).
  1. Weeks 3–5 (Gate G1 — Sandy Account Briefs, Opportunity Radar & RFx Intake Live):
  • Connect read-only PACE historical data (5 years of Estimate, Job, JobCost, Customer) to Sandy.
  • Activate 6-Part Account Strategy Briefs, Internal PACE Reorder/Whitespace Mining, and External Tender Radar (CanadaBuys, OECM, Merx) for the pilot sales cohort.
  • Activate the RFI / RFP / RFQ Parser & Missing-Spec Gate on live incoming inquiries.
  1. Weeks 6–8 (Gate G2 — PACE Draft Estimate Engine & Schedule Co-Pilot Live):
  • Enable automated PACE Estimate Draft generation (Draft — Pending Estimator Review) paired with Historical Look-Alike & Actual-vs-Estimate variance cards.
  • Enable Pre-Quote Schedule Feasibility & 72-Hour Material/Proof Readiness Alerts across Ottawa and Mississauga.
  1. Weeks 9–12 (Gate G3 — Measured Pilot Run & Executive ROI Review):
  • Run full closed-loop operations across the pilot sales and estimating cohort.
  • Evaluate pilot cohort outcomes against the frozen G0 baseline and present the Gate G3 Executive Review to Sebastián Gonzalez and Lowe-Martin leadership to authorize full rollout.

5. Safety, Security & Data Governance Guardrails

  1. Zero Autonomous Quotes or Schedule Overwrites:
  • The PACE Agent Assistant never sends pricing directly to a client and never overwrites active PrintFlow / PACE Scheduling boards. Estimators approve every PACE estimate; planners approve every schedule change.
  1. Sovereign Canadian Data & Confidentiality:
  • All Lowe-Martin customer data, PACE pricing tables, margin formulas, and high-security / government RFP documents remain isolated within Lowe-Martin's dedicated tenant boundary with Canadian data residency and full audit logging.
  1. Claim & Compliance Verification:
  • In both Sandy Account Briefs and RFP narrative drafts, any commitment involving SLAs, certifications (FSC, security clearances), or pricing terms is visually flagged for explicit human confirmation before external release.