dbo.Sites
Field | Data Type | Description |
BaseScenario* | Text | Base scenario name |
Site* | Text | Site name, e.g. "DCE_USA_GA_Atlanta" |
SiteDescription | Text | Site description, often name or description from site master |
City | Text | City |
State | Text | State or Province abbreviated, e.g. "GA" |
Country | Text | Country |
PostalCode | Integer | Postal code |
Latitude | Float | Latitude |
Longitude | Float | Longitude |
GeocodeMethod | Text | When using Geocode in Architect, this field will auto-populate with the sole Geocode method that Gains uses, “AzureMaps" |
Prefix | Text | Site prefix. It is used for convenience in filtering and/or reporting. E.g. “DCE” for the example site “DCE_USA_GA_Atlanta” |
StockingLocation | Text | Not used in COG models. Used when creating a multi-period NEO model. If turned on, it will allow sites to build up inventory between periods ['Yes', 'No']. |
FixedCost | Float | Fixed cost incurred if this site is used |
FixedCostModel | Text | Fixed cost model associated with this site |
StockingLocation | Text [Yes, No] | Not used in COG models. Used when creating a multi-period NEO model. If turned on, it will allow sites to build up inventory between periods |
Prefix | Text | Site prefix. It is used for convenience in filtering and/or reporting. E.g. “DCE” for the example site “DCE_USA_GA_Atlanta” |
Notes | Text | Freeform notes |
SolverInclude* | Text [Yes, No, FRC] | Indicates whether this record is active |
If the address fields are filled out but the latitude and longitudes coordinates are not, use the architect geocoding tool to populate these two fields.
We need to do this because the COG Solver picks the best new location(s) based on the lat/long coordinates of existing sites.
If the latitude and longitude coordinates are filled out but the address fields are not, this approach will work. However, we recommend using the reverse geocoder to populate the address fields.
This method will display the address in the output, which users are generally more familiar with.