<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Model Overview on API Documentation</title>
    <link>https://docs.icepack.ai/model-overview/</link>
    <description>Recent content in Model Overview on API Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 05 Mar 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://docs.icepack.ai/model-overview/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The problem envelope</title>
      <link>https://docs.icepack.ai/model-overview/problem_envelope/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/model-overview/problem_envelope/</guid>
      <description>The problem envelope is a common structure to all modelling API calls. Models are placed inside the envelope container and shipped as a single payload to the API. The advantage to this is that there are fewer end-points that you need to work with and the specification of what you want done actually moves into the envelope itself.&#xA;Workflow: sending a model The submitting of models to the API follows a common process.</description>
    </item>
    <item>
      <title>Routing models</title>
      <link>https://docs.icepack.ai/model-overview/routing-models/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/model-overview/routing-models/</guid>
      <description>Routing models involve determining the sequence in which things should be done by different resources. The simplest case of a routing model is the TSP, where a single resource (the travelling salesman) has to visit all locations provided in the cheapest possible way. This is the key focus of routing models, finding good sequences of activities which minimise the cost. Routing models grow more complicated and involve many side constraints.</description>
    </item>
    <item>
      <title>Periodic models</title>
      <link>https://docs.icepack.ai/model-overview/periodic-problems/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/model-overview/periodic-problems/</guid>
      <description>Periodic models are a specific class of tactical (or strategic) routing problems. In industry, these are often referred to as Nominated Visit Day (NVD) or Nominated Delivery Day (NDD) problems. NVD is a term used to describe periodic problems when scheduling salesforce visits (non-capacitated). NDD is used to describe periodic deliveries for vehicles (capacitated).&#xA;The big differentiator between routing models and periodic routing models is that decisions that require consistency over the planning period are often being made.</description>
    </item>
    <item>
      <title>Sourcing models</title>
      <link>https://docs.icepack.ai/model-overview/sourcing-models/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/model-overview/sourcing-models/</guid>
      <description>Sourcing models are quite different to routing models in that sourcing models are strategic, while routing models fall into the tactical/operational modelling tier. This means that sourcing models attempt to answer questions that are posed at a higher level than routing models. Modelling individual sequences of activities (like routing models) is not considered in sourcing models. Rather, the focus shifts to modelling aggregate transactions and the options around how they are performed.</description>
    </item>
  </channel>
</rss>
