I-35 North-South Freight Systems: Twin Cities, North Iowa, Des Moines and Kansas City

Planning scope and geographic boundary

The I-35 north-south spine is a useful reference for connecting Twin Cities work with north-central Iowa, Des Moines and Kansas City demand. This paper treats Forest City, Iowa as the program's planning origin, not as a claimed Strong Tower office or a guarantee of field response time. Mason City is part of the regional operating catchment rather than a claim that every named facility sits directly on the interstate. Actual terminal access, restrictions and travel conditions must be checked for the proposed movement.

The architectural problem is a sequence of commitments with different owners. A shipper releases an order, a carrier reserves resources, a facility confirms an appointment, and accounting later requires evidence that the work matches an agreement. The interstate creates a useful geographic frame, but the system should not confuse a corridor label with a fixed executable route. Preserve the route proposal separately from the commercial lane and update the former without silently changing the latter.

Use current state transportation information for planning context and live authoritative sources before execution. Iowa's freight plan is a planning reference, not a real-time dispatch feed. Iowa DOT freight planning.

Define the lane as a versioned operating object

A lane record should identify the commercial origin and destination scope, equipment requirements, service conditions and effective period. It can relate to several facilities and several acceptable route proposals. A price selected for a customer lane must remain linked to the applicable agreement even when a dispatcher chooses a different approved stop sequence. Otherwise, a routing correction can inadvertently change the commercial basis of the load.

For this spine, distinguish an interstate leg from the first and last local connectors. A planning estimate that includes only the long interstate segment can overlook facility service time, yard access or a required intermediate stop. Store the distance authority and the meaning of the mileage used in rating, driver compensation and planning. These quantities may legitimately differ, but their labels should not be interchangeable.

Test a revised delivery facility within an agreed customer zone. The application should identify whether the commercial agreement still applies, whether the appointment needs review and whether the resource reservation remains feasible. A one-field destination edit is not an adequate representation of all three decisions.

Capture appointments as commitments with provenance

An appointment record needs a facility identity, intended local time, confirmation source, version and current disposition. A requested time is not a confirmed time. Preserve the request and response history so dispatch can explain why a planned arrival changed. If the source supplies an ambiguous time or no confirmation, show the missing condition instead of treating an optimistic estimate as accepted service.

A north-south movement can involve several operating teams even when the civil time display looks familiar. Preserve actual offsets and time-zone context rather than relying on a user's browser location. Event time, receipt time and planning time remain separate. A driver update received after a connectivity interruption may describe an earlier stop, while a new customer instruction may require immediate review.

The acceptance case should include an appointment changed after a tractor was reserved. Verify that the system updates the proposed work, alerts the responsible role and preserves the earlier confirmation. A notification being queued does not prove the dispatcher or driver received the change.

Separate resources, reservations and assignments

A tractor, trailer and driver form a proposed operating combination, but they do not share one availability clock. A trailer may be at a customer while the tractor is available for another task. A driver may have uncertain duty information. Model these conditions separately and create a reservation boundary before the proposed combination becomes a committed assignment.

Concurrent planning deserves explicit tests. Two dispatchers may identify the same apparently attractive tractor for different northbound loads. A recommendation engine should not allow both to become final merely because each calculation was valid when it started. Use an atomic reservation or equivalent conflict check and show the losing request a clear next action without erasing its entered work.

Preserve the reason for a human override. A carrier may prioritize a customer's critical appointment, a planned equipment return or a driver's agreed work pattern over the lowest modeled empty mileage. The system should record that decision without pretending the model had captured every relevant commercial condition. Overrides become useful feedback for later rule improvements.

Rate the commercial movement deterministically

A corridor tariff should select among the relevant customer, equipment, origin zone, destination zone, quantity and effective-date conditions. State precedence before optimizing the lookup. A specific contracted lane and a broader regional fallback can overlap legitimately only when their order of application is documented. A tie that depends on database row order is not a supportable commercial rule.

The calculation receipt should retain quantities, tariff version, selected rule, fuel-index reference, accessorial candidates and rounding policy. The carrier can then reproduce an invoice after the current tariff has changed. Do not recalculate historical work merely because an operator opens the record. Repricing is a distinct action with authority and an explanation.

A realistic acceptance workload includes the shared corridor with different customers and equipment categories, a contract boundary at the relevant effective instant and an unknown facility mapping. The expected result is not always a price. Sometimes the correct output is an explicit ambiguity or missing-reference condition that prevents an unsupported quote from appearing authoritative.

Keep fuel, empty miles and driver pay distinct

Long corridor movements make mileage and fuel assumptions visible, but the same numerical input should not be copied into every financial calculation without an agreement. A customer fuel schedule may use eligible loaded miles, while compensation uses another mileage authority and equipment repositioning remains an operating expense. Preserve those meanings even if a dashboard displays their totals together.

An illustrative continuous surcharge uses eligible miles multiplied by the positive difference between an index and a contract base, divided by an agreed efficiency value. Production terms may use brackets or another schedule. Store the actual source publication and rounding stage. A recently published index must not silently replace the value used in an approved historical invoice.

For a Forest City planning scenario, test an additional customer stop, a changed empty repositioning leg and a driver reassignment. Verify that each affects only the rules whose scope includes it. Matching the final net amount is not enough if offsetting errors have moved money between customer revenue, carrier cost and compensation.

Use exception evidence for facility delay

Facility dwell should be represented as an evidence case rather than as a guaranteed accessorial. Arrival observations, gate events, appointment compliance and documents may support an interval, but contract eligibility remains a separate rule. Preserve where an inferred interval begins, which observations support it and where missing data limits the conclusion.

A GPS sample inside a polygon does not establish continuous physical presence until the next sample regardless of gap length. The reference auditor should accumulate only intervals supported by its declared model and flag longer gaps for review. Overlapping geofences also require an ownership policy so one stop does not create several unrelated charge candidates for the same commercial event.

Assign the unresolved case to a role with access to the relevant facility and customer records. The dispatcher may explain physical events, while accounting decides whether the evidence supports a billing action under the agreement. Keep the approved charge, rejected candidate and supplier dispute as distinguishable outcomes rather than reducing all of them to a generic completed status.

Plan disruption as an information-state change

Weather, access restrictions and customer changes can invalidate a route proposal without changing the underlying shipment identity. The system should identify which plan assumptions are stale and request review. A stored map is not a current road advisory, and a planning publication is not a live source of permission to operate.

Model an alternate proposal as a new version with its distance, time and commercial consequences visible. Preserve the previous plan and the reason it was replaced. The approval boundary should recheck equipment availability, appointments and applicable operating constraints rather than allowing a new route line to inherit every prior decision automatically.

For testing, introduce a disruption after acceptance but before the first pickup. The application should preserve the customer obligation while preparing a revised operating plan. Then repeat the case after a pickup has occurred. The latter scenario may require additional custody, customer communication and financial treatment; it should not be handled by deleting the movement and starting an unrelated shipment.

Preserve customer communication as a tracked obligation

A customer status message should identify its shipment, event meaning, source timing and intended recipient context. A successful API response may confirm durable receipt without confirming that a person saw the update. Separate message delivery, business acknowledgement and any required human follow-up in the ledger.

The carrier should be able to answer what the customer was told when a plan changed. Retain the approved statement and its source event rather than regenerating a historical message from the shipment's current display. This matters when a delayed observation arrives after an earlier estimate was communicated in good faith.

Test a status transmission that times out after remote acceptance. Retry should use the agreed idempotency or reconciliation contract and avoid creating conflicting updates. A dispatcher-visible state should explain whether the communication is pending, uncertain or confirmed at the relevant boundary. Silence in a technical queue is not evidence that the customer has an accurate operating picture.

Close the corridor movement in accounting

Financial closure should require the relevant operating and document evidence, not only a delivered display state. A controller needs to trace charge components, adjustments, approvals and external posting references. Missing proof of delivery or an unresolved accessorial can create a deliberate hold while the physical shipment remains correctly recorded as delivered.

The accounting integration should preserve prepared, validated, accepted and reconciled states. A request timeout can leave the outcome uncertain even when the remote system created an invoice. The next action is reconciliation using a stable reference, not automatic creation of another document. Test credits and corrections as well as the first posting.

Use a multi-customer corridor fixture where several loads share a rate basis but have different accessorials and settlement components. Compare detailed obligations as well as totals. A matching batch total can hide a charge posted to the wrong customer, which is an operating error even if the grand total balances.

Adopt the design through a bounded service slice

Begin with a defined customer and equipment population whose normal and exception paths can be observed. The slice should include tender receipt, resource reservation, physical execution, documentation, billing and recovery. Implementing only the dispatch screen postpones the questions most likely to produce manual reconciliation after rollout.

Assign owners for mappings, contracts, calendars, customer communications and financial release. Preserve a change record that links each software or configuration update to the requirement and acceptance case it affects. The carrier should know who can publish a tariff correction and which historical calculations must remain unchanged.

Expansion should follow evidence: unresolved case age, duplicate prevention, reconciliation completeness and operator understanding. Do not infer readiness for every I-35 movement from a successful demonstration on one ideal load. A documented limitation can define a safe operating envelope while the team addresses the next case; an unacknowledged limitation cannot support an accountable release decision.

Acceptance pack and research boundary

The acceptance pack should contain lane and facility identities, tariff examples, appointment history, reservation conflicts, observed-event fixtures, failed communications and accounting reconciliation. Include a completed load with a late update and an incomplete load with a source gap. Both must remain understandable without altering history to make the dashboard look clean.

Record the benchmark environment and distinguish synthetic test records from customer operations. Measure correctness, latency distribution and recovery behavior under the selected workload rather than publishing an unsupported universal performance claim. A live operating release also needs current route information and the carrier's approved compliance process, which this regional reference does not replace.

Strong Tower Consulting, LLC is the Minnesota architecture firm founded in 2008 by Scott Elliott. The method here applies that identity to a specific operating problem without claiming a local terminal, unnamed customer or exclusive corridor expertise. Its useful output is a carrier-controlled system whose commitments, observations, financial consequences and recovery actions can be inspected together.

Worked review: one revised northbound load

Consider a hypothetical northbound order whose delivery appointment changes after acceptance. Preserve the original order and confirmation, create the revision, and identify affected resource reservations. Re-evaluate the route proposal and the relevant commercial conditions without changing the shipment identity. If a later device event describes the earlier plan, retain it with its actual event time rather than forcing it into the latest schedule.

The review passes only when dispatch can identify the authorized plan, the customer ledger shows the intended communication, and accounting can explain any changed charge. This is a synthetic acceptance scenario, not a client success story or evidence of an actual corridor deployment.

Interface contract for a shared corridor desk

A shared desk needs an interface contract that distinguishes an operator command from an observation. A command might request that a specific driver and tractor be reserved for a work order. An observation might report where a trailer was scanned. Store the caller's authority context, the target operating entity and the expected current version with the command. Reject a conflicting version without treating the rejection as a new physical event.

The response should identify durable acceptance or a specific reason why the action was not applied. For an asynchronous instruction, return an operation reference that can be queried after a browser disconnects. The operator should not need to submit the same action repeatedly to discover whether the first request succeeded. The service must preserve enough context to reconcile uncertain outcomes.

A test can open two desk sessions against one unassigned load, reserve the same equipment through each, and introduce a delayed observation between them. Exactly one compatible reservation should become authoritative under the stated policy. The unsuccessful request should retain its proposed values and explain the conflict. The observation remains part of the evidence history regardless of which command was accepted. This establishes business behavior at the interface boundary rather than merely checking that both screens remain responsive.

Rehearse a day-end interruption and restore

A practical recovery exercise should stop the relevant processing component while accepted loads, outbound messages and prepared invoices exist. Preserve the transaction boundary at which the component stopped, then restore it in an isolated environment with outbound effects disabled. The exercise should determine which records are present, which obligations are pending and which remote outcomes are uncertain.

For the I-35 operating slice, include a load already picked up, a reserved but unstarted movement and a delivered shipment waiting on documentation. Each has a different recovery consequence. Recreating every record as received would erase operational meaning; marking every queued message delivered would invent external confirmation. Restore the actual state and use the reconciliation procedure for the boundaries that cannot be proved locally.

The final review should compare expected business records with the restored system and document every manual intervention. Have dispatch confirm the next executable action and accounting confirm that posting will not duplicate an obligation. Record elapsed restoration time with its environment and scope. This measured exercise can support a recovery claim for that configuration; it does not establish a universal zero-loss or zero-downtime result for every carrier system or future release.

Technical method appendix: Describe throughput with a workload model

This appendix reproduces a selected company-authored method from The Strong Tower Architectural Standard. It is attributed reference material, not an additional regional fact, customer case or claim of a new experiment.

A workload model connects technical sizing to the carrier's operating rhythm. Count tender arrivals, dispatch updates, mobile events, rating requests, document uploads and accounting exports separately. They place different demands on compute, storage and human review. A thousand small status messages are not equivalent to a thousand scanned document packets, even if an activity dashboard counts each as one event.

For each flow, record typical and peak arrival rates, payload sizes, acceptable delay, retention and concurrency. Include bursts after a partner outage, a shift change or a connectivity restoration. Backlogs often become most dangerous during recovery, when normal traffic continues while old work is replayed. Capacity planning must account for both populations sharing the same downstream services.

Use a simple queue balance to make the question concrete: backlog growth equals arrival rate minus sustainable completion rate over the same interval. When arrivals exceed completions, the system needs either more capacity, controlled admission or an explicit delay policy. Adding worker processes cannot solve a bottleneck in a partner API that allows only a limited request rate.

An acceptance workload should be reproducible. Preserve the mix of transactions, the size distribution and the order in which updates arrive. Remove confidential business values while keeping realistic relationships among records. The carrier can then compare candidate systems on the same operating problem instead of comparing vendor demonstrations prepared under unrelated conditions.