Home Contact Info Client Login
Juncture Optimization

Evolution of Supply Chain Systems: A Functional Perspective

To better understand juncture optimization take a look at how supply chain systems have evolved and where juncture optimization fits.

* Juncture Optimization supports WMS, TMS, OMS, CMS, SCP, SCE, ERP, etc.
 

Juncture Optimization Examples

One of the key differentiators behind our solutions is the toolkit of mathematical techniques we employ. Coupled with decades of domain experience, our development team has customized these specialized mathematical techniques to match our optimization goals. The resultant optimization modules reside at the core of, and uniquely power our optimization engines. A sampling of applications of our customized, optimization engines are highlighted below.

  • Maximize cross-docking opportunities by examining yard management or dock scheduling problems, while meeting with capacity constraints and delivery promises
  • Minimize selection cost by applying advanced math to the pick line while ensuring that product is provided to retail in a way that minimizes restocking costs.
  • Minimize total selection costs using the latest generation of the genetic algorithm toolkit, combinatorial searching tools, and a customized version of the Ejection Chain generalized assignment problem solver to perform optimal slotting assignments. This optimization engine takes into account both sequencing and assignment goals, which can be weighted by the user.
  • Minimize total distribution costs while co-mingling pickups and deliveries while meeting triumvirate requirements and constraints for customer service, transportation and the distribution center.
  • Minimize selection costs by integrating (in real time) the order pool with selector actions all while continuously reassigning work tasks.
 

Integration Into Customer's Existing Infrastructure

To integrate our optimization engines we utilize alternative systematic approaches to unobtrusively fit into a customer's existing infrastructure. Options to consider include:
  • A server application that receives data and sends results using industry standard integration queues (such as IBM MQ Series) that have interfaces to the Java Message Service (JMS). To build this solution for a customer, we would do custom data definitions and parsers/generators so that existing systems would not require any customization. All of the data translation work would be done by our application using "custom, connection code" built on a customer-by-customer basis. This approach provides "easy to fit" solutions that would require little work by customer's existing staff.
  • A web-service that sends and receives data via the popular XML web-service interfaces. A big advantage to this approach is that the application is "disconnected" from the existing systems and does not require that the existing systems be configured to send and receive data.
  • A stand-alone PC program that imports and exports data in a clean way. Options still provide for automatic integration using one or both of the methods above, but it is not required. The program can range anywhere from a true stand-alone application where customers import and export files to a fully integrated tool, but with a user interface.