TS. Extension Source

Overview and Visibility

The Extension Source step may be used to load scripts to change the reserves database, stockpile inventories, equipment performance, processing plant performance, and reporting fields. 

Open

Extension Source step overview

Site Specific Extensions

Site specific extensions come in the form of a  "SiteSpecificExtension.sln" file and a "SiteSpecificExtensions" folder. These two items must be kept together in a parent folder (for example, "SiteName_LOM_001") and kept in the same working area as the "project.tsch" and "project.hinf" files. 

• Since your project specific scripts come from a C# project, they are coded separately from the application. Press a folder icon to select a path to import extensions, so those scripts can be used in the Tactical Scheduler project.

Open

Press the folder icon to initially upload set of scripts made for your model

• Once those scripts are loaded, then you don’t need to keep a separate copy of these extension files. The scripts are now available for save from the APS project via the export button.

• Tactical Scheduler project files will continue to work if they are separated from the scripts folder, but any changes to the script require it to be re-imported from the source. As such, always make sure the scripts accompany the project files in any handover.

If the Alastri support team need to edit your scripts, zip up the whole folder and upload to Alastri Files Upload Space.