We shall start our tutorial with creating a scenario, one of the principal elements of anyLogistix. Further on during this tutorial we will populate it with complete information on shipping and related operations, as well as all the data on vehicles, warehouses, etc. This information will be used for running experiments and building reports.
Let us begin.
The numbered lists in tutorials are actually checklists. Click the numbers to save your progress!
Create a scenario
Click the New Scenario button in the project tree.
The New Scenario dialog box will open.
As you can see, the Scenario type option is already set to GFA since we are creating this scenario in the GFA experiment tab (it is highlighted in the toolbar):
Type My Supply Chain in the Scenario name field and leave all the rest fields as they are.
Click OK. The new scenario will appear in the GFA tab, since the Scenario type option was set to Greenfield Analysis (GFA) in the New Scenario dialog box.
Once the new scenario is created, you will see the default anyLogistix interface, which consists of the following areas:
- The title of the current project, and the menu bar.
- The Project tree — allows you to work with the scenarios and execute experiments.
- GIS map — shows geographical structure of the scenario.
- The list of tables and table editor, defining the supply chain you are
creating. The tables are listed in the alphabetical order. The list differs for each scenario type.
The number next to the table name indicates the number of records the table contains.
The categories above the list of tables allow you to filter the tables:
- Basic — lists the tables required to launch the experiment.
- All — lists all the tables applicable to the current scenario type.
- In use — lists the tables that contain at least one record with the current scenario's data. The number next to the tab name shows the number of tables that contain data.
When in experiment mode this area may contain either a dashboard menu (in case of simulation based experiments, available in the SIM tab) or a list of results (in case of Network optimization experiment).
- Validation section — shows data inconsistency, if any.
- Structure view — shows logical structure of the scenario.
Having created a new scenario we can start populating its tables with data.
As you might have noticed, the Products and Periods tables already contain records, this is automatically done by anyLogistix in the tables that are required to run the experiment. These records can be edited later.
Let us start with adding customers to our model. Each customer is located in a certain city on the territory of the United States of America. The following cities will be considered in our supply chain: Washington DC, Dallas, Philadelphia, Jacksonville, San Diego, Chicago, New York, San Antonio, Los Angeles, San Jose, Phoenix, Orlando, Denver, Nashville, Detroit, Boston, Atlanta, Seattle, Kansas City, Salt Lake City.
You can either follow our scenario and use the same list of customers or you can use your own set of customers. In either way, make sure that you follow this tutorial steps as we design our supply chain.
Add a customer via GIS map
Use the GIS map to navigate to the USA and zoom in close enough to be able to see the city names. Let us locate our first customer in Washington, DC. You can see it on the screenshot below.
Click the Create Customer icon in the GIS map toolbar.
- Double-click the Washington, DC city marker on the map to place the customer. A new customer will be created.
- When done, click the Panning mode icon to the left of the Create Customer icon to exit the editing mode.
Now that we have created a new customer, we must give it a meaningful name. Below the GIS map you will see the automatically opened Customers table containing the record with the previously created Customer customer.
Rename a customer
- Click the Customer cell in the Name column to activate the editing mode.
- Type Washington DC and press Enter to exit the editing mode.
The customer will now have a meaningful name referring to its actual location. The customer's location name in the
Location column will be automatically updated.
The mentioned location is automatically set based on the GIS map spot that we clicked to create this customer. All the available locations are stored in the Locations table. If you navigate to this table, you will be able to manually define the location of the customer.
Navigate to the Locations table
- Click the All table tab to browse through the list of all the GFA related tables.
- Scroll down the list and click Locations. You will be taken to the Locations table.
Now we will edit location. There are two alternative ways to manually define the location of the customer. You can do either of the following:
- Specify the location's Latitude and Longitude coordinates
(the Fill coordinates automatically toggle button is disabled by default).
- Edit the Name of the city (or type the city name in the City column),
specify the name of the Country (e.g. Washington DC,
USA), and enable Fill coordinates automatically.
anyLogistix will connect to Maptiler GIS search to get the exact coordinates, and place the customer at
Washington DC (the Latitude and
Longitude columns will be automatically filled with the received data).
- Specify the location's Latitude and Longitude coordinates (the Fill coordinates automatically toggle button is disabled by default).
Use the second method if you want locations of your customers to have actual geographic names to which you can refer from the other tables.
Now that we have created our first customer, we can proceed to add all other customers in the very same way.
To save some time and eliminate possible customer locating issues we provide you with the exported scenario MS Excel data sheet containing all our customers and their locations. Use it to Import the data into the existing scenario.
The importing data does not contain the previously created Washington DC customer.
Import customers to this scenario
- Click the Import button in the bottom of the project tree to open the Import Scenario dialog box.
- Select the MS Excel file with the scenario data by clicking the Browse button to the right of the field and navigating to the existing file.
- Click Advanced options to open the section and modify the import parameters.
- Click the Tables to import drop-down list and check Customers and Locations. This means we will import only the tables containing customers and their locations.
- Disable the Create new scenario toggle button to prevent creation of new scenario and specify the My Supply Chain scenario in the Scenario name option. In this way, we will import the data of the selected MS Excel file into the existing scenario.
- Uncheck the Import experiments, Import initial states, and Import external tables options.
- Click OK to import the data.
When done, you will see all the customers on the map.
Once you have added all the customers, you can move on to the next step to specify the product your supply chain will be providing the customers with.
How can we improve this article?