05. PACE API Integration Summary  •  PACE API SPEC
CLIENT & FULFILLMENT ENTERPRISE
LOWE-MARTIN GROUP • EST. 1908
•
LMX SOLUTIONS FULFILLMENT • OMNICONNEX
×
COMMERCIAL CREATIVE & AGENTIC AI PARTNERS
BRILLIANTZ COMMERCIAL & BRAND SYSTEMS
•
Cogneris. CORE CRM & PACE AI

ePS Pace API Integration Architecture & Method Summary for Lowe-Martin

Classification: CONFIDENTIAL — Cogneris Engineering & Integration Reference

Client Target: The Lowe-Martin Group / LMX Solutions (Ottawa & Mississauga)

Date: 2026-11-19

Version: 1.0


1. Executive Summary: How We Incorporate the ePS Pace API

To integrate safely and performantly with ePS Pace (formerly EFI Pace) across Lowe-Martin's Ottawa and Mississauga operations, our architecture uses a Hybrid 4-Channel Integration Pattern.

Why a hybrid pattern instead of only SOAP API calls?

  1. PACE's Costing Engine Must Never Be Bypassed: You cannot use an external LLM or spreadsheet formula to guess commercial print imposition, press run speeds, spoilage curves, or bindery setups and insert raw cost numbers into PACE. Every write operation must go through PACE's SOAP Web Services (EstimateRequest, CloneObject, InvokeAction: calculateEstimate) so PACE's own internal calculation rules compute the estimate.
  2. SOAP Alone Is Too Slow for Multi-Year AI Context: Chaining hundreds of SOAP FindObjects and ReadObject requests to search 5 years of historical jobs, compare estimated vs. actual shop-floor JobCost, or mine 1,000 customer reorder cycles adds latency and application-server load. Because PACE runs on PostgreSQL, we pair SOAP writes with a Read-Only PostgreSQL Analytics View Layer for sub-second AI context with zero production locks.
  3. Scheduling Requires Respecting the PrintFlow 4D Boundary: If Lowe-Martin uses PrintFlow 4D alongside or instead of native PACE Scheduling (JobPlan), external software must never overwrite JobPlan rows directly in PACE behind PrintFlow's back.
flowchart TB subgraph Apps["The 5 LMX-NewOps Applications"] A1["App 01: PACE EstiGate™
(Intake, Missing-Spec Gate & Drafts)"] A2["App 02: PACE PlanFlow™
(Cross-Plant Schedule & 72-Hr PO Watchdog)"] A3["App 03: CORE CRM Studio™
(Buyer→Rep→Approach→Outcome & 6-Div Matrix)"] A4["App 04: CORE Opportunity Radar™
(Tenders & 45-Day PACE Reorder Miner)"] A5["App 05: CORE RFx Bid Studio™
(Multi-Lot RFP Parser & PACE Bridge)"] end subgraph Bridge["Service 01: The PACE × CORE CRM Integration Bridge"] C1["Channel 1: SOAP Web Services & InvokeAction
(Governed Draft Writes & Native Cost Calculation)"] C2["Channel 2: PaceConnect Event Webhooks
(Real-Time Outbound XML/JSON Milestone Triggers)"] C3["Channel 3: Read-Only PostgreSQL Views
(Sub-Second Historical Estimates, JobCost Actuals, Inventory & POs)"] C4["Channel 4: Scheduling & DMI Read-Safe Sync
(PACE JobPlan / PrintFlow 4D Load & Auto-Count 4D Actuals)"] end subgraph PaceCore["Lowe-Martin ePS Pace & Plant Backbone"] P_SDK["ePS Pace Application Server
(WSDL SOAP SDK & Costing Engine)"] P_DB["ePS Pace PostgreSQL Database
(epace Schema / Reporting Replica)"] P_PF["PACE Scheduling / PrintFlow 4D APS
& Auto-Count 4D Shop-Floor DMI"] end A1 & A5 --> C1 --> P_SDK P_SDK --> C2 --> A2 & A3 & A5 P_DB --> C3 --> A1 & A2 & A3 & A4 P_PF <--> C4 <--> A1 & A2

2. The 4 PACE Integration Channels & Exact API Methods Used

Channel 1: ePS Pace SOAP Web Services API (Governed Writes & Native Costing)

PACE exposes strongly-typed SOAP WSDL services over HTTPS (ReadObject, CreateObject, UpdateObject, DeleteObject, FindObjects, CloneObject, InvokeAction, InvokePaceConnect). We use these specific services and actions:

PACE SOAP Service / MethodTarget PACE ObjectsHow We Use It in LMX-NewOpsSafety & Governance Guardrail
CreateObject + InvokeAction (createEstimateFromRequest / calculateEstimate)EstimateRequest, Estimate, EstimatePart, EstimateQuantityPathway A (Template-Driven Quotes): For products mapped to a PACE JobProductType template (the same engine used by EasyQuote—e.g., booklets, brochures, postcards, wide-format signage, standard cartons), App 01 (PACE EstiGate™) populates an EstimateRequest and invokes PACE's native calculation action.PACE computes 100% of imposition, press sheets, spoilage, makeready, and markups. Tagged DRAFT_PENDING_ESTIMATOR_REVIEW.
CloneObject + UpdateObject + InvokeAction (calculateEstimate)Estimate, EstimatePart, EstimatePaper, EstimatePress, EstimateActivityPathway B (Complex Multi-Part & LMX Kitting Quotes): When a custom multi-component job arrives (e.g., folding carton + 24pp bilingual booklet + VDP cards + LMX hand-kitting) that closely matches a proven historical PACE estimate, App 01 calls CloneObject on the baseline estimate, updates the delta fields (quantities, stock weight, kitting hours), and calls InvokeAction: calculateEstimate.Preserves all validated sub-operations and routing dependencies from the proven baseline estimate; requires human estimator review before release.
ReadObject & FindObjectsEstimate, EstimateStatus, Job, Customer, Contact, JobProductType, PriceListLive lookup of active estimate status, customer-specific contract rate cards (where Price List Quoting is enabled), and product template schemas for the Missing-Spec Gate.Scoped API service account with role-based permissions; rate-limited to protect interactive PACE users.
UpdateObject (Notes & Custom UDFs)EstimateNote, JobNote, User Defined Fields (u_*)Attaches the AI Assumption Sheet, Historical Look-Alike Variance Summary, and Schedule Feasibility badge (Green / Amber / Red) directly onto the PACE Estimate record for the estimator to inspect.Writes only to designated draft/note fields; never alters posted financial or active job-ticket fields.
InvokeAction (convertToJob)Estimate → JobConverts an accepted quotation into a live production job.100% Human-Triggered Only: The agent never calls convertToJob autonomously; it is executed only after human estimator/CSR approval.

Illustrative SOAP Workflow for App 01 (PACE EstiGate™) & App 05 (CORE RFx Bid Studio™)

<!-- Step 1: Create or Clone EstimateRequest / Estimate with extracted RFQ specs -->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
                  xmlns:urn="urn:pace.pace2020.com">
  <soapenv:Body>
    <urn:createObject>
      <urn:EstimateRequest>
        <urn:customer>APEX-BIO-CA</urn:customer>
        <urn:jobProductType>LMX_PHARMA_KIT_4P</urn:jobProductType>
        <urn:description>[AI_DRAFT_PENDING_REVIEW] Apex 2027 Bilingual Patient Kit (15k / 30k)</urn:description>
        <urn:quantity1>15000</urn:quantity1>
        <urn:quantity2>30000</urn:quantity2>
        <urn:u_cognerisSourceRfxId>RFX-2026-118</urn:u_cognerisSourceRfxId>
      </urn:EstimateRequest>
    </urn:createObject>
  </soapenv:Body>
</soapenv:Envelope>

<!-- Step 2: Trigger PACE's internal calculation engine via InvokeAction -->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
                  xmlns:urn="urn:pace.pace2020.com">
  <soapenv:Body>
    <urn:invokeAction>
      <urn:actionName>calculateEstimate</urn:actionName>
      <urn:primaryKey>EST-90412</urn:primaryKey>
    </urn:invokeAction>
  </soapenv:Body>
</soapenv:Envelope>

Channel 2: PaceConnect Inbound & Outbound Event Webhooks

Instead of polling the SOAP API every 30 seconds to ask "Did the estimator approve the quote yet?" or "Did the paper PO arrive?", we configure PaceConnect outbound XML/JSON triggers on four key lifecycle events:

  1. Estimate Status Change (Draft → Approved / Quoted / Won / Lost):
  • Immediately notifies App 05 (CORE RFx Bid Studio™) to pull the estimator-approved unit prices, run-on rates, and plant lead time into the RFP pricing schedule.
  1. PurchaseOrder Receipt / ASN Update (PurchaseOrderLine):
  • Immediately updates App 02 (PACE PlanFlow™) 72-Hour Readiness Watchdog when mill paper/board arrives (or slips) at the Ottawa or Mississauga receiving dock.
  1. Prepress Proof Approval (JobStatus / Prepress Milestone):
  • Clears the prepress readiness gate on the App 02 schedule watchdog.
  1. Job Close & Final Costing (Job Closed / JobCost Posted):
  • Triggers App 03 (CORE CRM Account Studio™) to reconcile quoted margin vs. realized shop-floor margin and update the account's 6-Part Strategy Brief.

Channel 3: Read-Only PostgreSQL Analytics View Layer (epace Schema)

Because ePS Pace runs on PostgreSQL, we establish a strictly read-only JDBC / reporting-replica connection exposing five pre-joined SQL views. This gives the AI agents sub-second retrieval across years of Lowe-Martin history without touching transactional locks:

Read-Only ViewUnderlying PACE TablesWhich App Uses It & Why
v_lmx_historical_estimatesestimate, estimatepart, estimatequantity, estimatepaper, estimatepress, estimateactivityApp 01 (PACE EstiGate™): Finds the top 5 historical look-alike estimates by product type, dimensions, stock caliper, ink coverage, and finishing sequence.
v_lmx_jobcost_actualsjob, jobpart, jobcost, activitycode, costcenter (populated by Auto-Count 4D / Data Collection)App 01 (PACE EstiGate™): Compares estimated hours/waste against actual floor makeready, run speed, spoilage, and LMX hand-kitting seconds to flag margin leaks before quoting.
v_lmx_inventory_and_posinventoryitem, inventoryline, purchaseorder, purchaseorderline, paperweightApp 01 & App 02 (PACE PlanFlow™): Checks whether required paper/board is physically on the floor in Ottawa or Mississauga, or when an open mill PO is scheduled to arrive.
v_lmx_account_6div_matrixcustomer, invoice, invoiceline, job, estimate, salesperson, jobproducttypeApp 03 (CORE CRM Account Studio™): Computes trailing 36-month revenue, quote-to-win ratios, realized gross margin, and untouched whitespace across Lowe-Martin's 6 divisions.
v_lmx_reorder_cadencecustomer, job, estimate, u_omniconnex_skuApp 04 (CORE Opportunity Radar™): Detects recurring seasonal/annual print & mail campaigns 45 days before historical order dates and flags quote-heavy/low-win accounts.

Channel 4: Scheduling Boundary (PACE Scheduling vs. PrintFlow 4D)

In our initial technical discovery call (Gate G0), we verify whether Lowe-Martin runs native PACE Scheduling, PrintFlow 4D, or a combination across Ottawa and Mississauga:

Scheduling EnvironmentHow We Integrate Read / Feasibility ChecksHow We Handle Rush Simulations & Schedule Changes
Native PACE Scheduling (JobPlan)Read scheduled operation start/end times, department queues, and machine shift calendars from JobPlan and CostCenter tables.Simulate operation insertion in memory inside App 02 (PACE PlanFlow™); write proposed schedule notes to JobNote for master scheduler approval.
PrintFlow 4D (Dynamic Constraint APS)Read synchronized machine load, queue durations, dependency networks, and job due-date slack from the PACE-to-PrintFlow sync tables / XML export.Never mutate JobPlan rows directly in PACE (which PrintFlow would overwrite on its next sync cycle). Instead, run non-destructive ripple simulations in App 02 and pass approved rush priority / promise-date attributes through the sanctioned PACE-to-PrintFlow job header fields.

3. Application-by-Application PACE API Mapping

This summary table shows at a glance how each of the 5 Applications interacts with ePS Pace:

ApplicationReads from PACEWrites to PACEHuman Approval Gate
App 01: PACE EstiGate™
/apps/estigate.html
• JobProductType required spec schemas
• Top 5 look-alike Estimate & JobCost actuals
• Floor paper InventoryItem availability
• Creates EstimateRequest or clones baseline Estimate (CloneObject)
• Calls InvokeAction: calculateEstimate
• Writes AI assumption & variance note to EstimateNote
Senior Estimator reviews and approves every draft in PACE before pricing is released.
App 02: PACE PlanFlow™
/apps/planflow.html
• JobPlan / PrintFlow 4D machine queues across Ottawa & Mississauga
• Open paper PurchaseOrder ETAs
• Prepress proof status & die inventory
• Attaches feasibility badge (Green / Amber / Red) and schedule reservation request to EstimateNote / JobNoteMaster Scheduler / Planner approves any rush slotting or cross-plant rerouting.
App 03: CORE CRM Studio™
/apps/core-crm.html
• 36-month customer Invoice, Job, and Estimate win/loss history across all 6 divisions
• Rep & specialist historical delivery records
• Read-only against PACE production tables (stores 6-Part Strategy Briefs and assignment evidence in the CORE CRM database)Sales Manager & Account Exec control all assignment overrides and brief edits.
App 04: CORE Opportunity Radar™
/apps/opportunity-radar.html
• 5-year historical job cadence (Job.dateSetup)
• Quote-to-win ratios by customer
• OmniConnex / LMX warehoused SKU burn rates
• Read-only against PACE until a rep clicks "Initiate Proactive Re-Quote", which routes a pre-populated request to App 01 (EstiGate™)Account Executive reviews and triggers proactive outreach or re-quote requests.
App 05: CORE RFx Bid Studio™
/apps/rfx-studio.html
• Receives estimator-approved unit prices, run-on rates, and validated lead times back from App 01 & App 02 via PaceConnect / SOAP ReadObject• Pushes normalized multi-lot technical specs across the bridge to App 01 (PACE EstiGate™) to generate the linked PACE estimate draftsEstimator approves all PACE costs; Bid Lead / Exec confirms all flagged SLA/compliance claims.

4. Five Gate G0 Verification Items Before Writing Our First Line of Adapter Code

To move from this blueprint into Gate G0 implementation with Lowe-Martin's IT and Estimating team, we verify five concrete items in a 45-minute technical call:

  1. WSDL & SDK Endpoint Check: Confirm the PACE version (e.g., 34.x / 35.x / 36.x) and verify access to the SOAP WSDL endpoints (/epace/services/ReadObject, CreateObject, UpdateObject, CloneObject, FindObjects, InvokeAction) in a staging/test environment.
  2. Product Template (JobProductType) Inventory: List which commercial print, direct mail, wide-format, packaging, and LMX kitting product types already have configured JobProductType / EasyQuote templates vs. which rely on custom EstimatePart assembly or cloning.
  3. Ottawa vs. Mississauga Entity Structure: Confirm how the Ottawa and Mississauga plants are separated in PACE (multi-company, multi-plant, or cost-center prefix) for cross-plant routing comparisons.
  4. Scheduling & DMI Footprint: Confirm whether Ottawa and Mississauga use native PACE Scheduling (JobPlan) or PrintFlow 4D, and how Auto-Count 4D / Data Collection posts actuals to JobCost.
  5. PostgreSQL Reporting Replica / View Access: Confirm the read-only PostgreSQL connection path for the five analytics views (v_lmx_*).