{"id":56,"date":"2017-12-23T11:18:26","date_gmt":"2017-12-23T11:18:26","guid":{"rendered":"http:\/\/www.mineoptek.com.au\/?page_id=56"},"modified":"2018-03-01T13:29:20","modified_gmt":"2018-03-01T13:29:20","slug":"white-paper","status":"publish","type":"page","link":"https:\/\/www.mineoptek.com.au\/?page_id=56","title":{"rendered":"White Paper"},"content":{"rendered":"
\n\t\t\t\t\t
\n\t\t\t\t\t\t

Background<\/h2>\n

Mine scheduling software predominantly services a single mine or a small complex containing a few mines which service a single processing plant. The assumptions within that environment are:<\/span><\/p>\n

    \n
  1. Data sizes reasonable for a small cluster of mines<\/li>\n
  2. Single point of data entry and data management for the scheduling project<\/li>\n
  3. Data provided by a small handful of site-based engineers at regular intervals to meet typical reporting timetables<\/li>\n<\/ol>\n

    While these assumptions are problems where they aren\u2019t met, they also cause problems for smaller mines:<\/span><\/p>\n

      \n
    1. There is typically no change management or change logging, so the system is prone to data entry errors and personnel making adjustments to key numbers and then forgetting which ones they changed<\/li>\n
    2. When new data arrives, the single-all-in-one project-file structure means a choice has to be made as to which of the many what-if cases that were run over the previous months should be used as the basis to go forward and take the new data<\/li>\n<\/ol>\n<\/div>