Comparison of "old" Crop (menu Production cycles, Tasks) and "new" Crop (Work order)
Introduction
1 Comparison of Production cycles with Work orders
Converting process rules:
a) Data recorded within PRODUCTION CYCLES are converted into WORK ORDERS form. Individual work order represents individual crop area which was recorded within Production cycle as Crop area and meanwhile recorded within Farming task.
b) Number of created work orders is equal to the number of previous assigned crop areas within Production cycles for which was reported realization. If the crop area was planned in Production cycle, but no work was reported on it through Farming task menus, no work order is created.
Picture 3: Product Winter barley as production cycle Winter barley 2015 with assigned crop area Subdivision 541779_1 (above, old CROP) converted into work order Winter barley on Crop area Subdivision 541779_1 (below, new CROP)
Picture 4: Two Crop areas, assigned to product Wheat within production cycle Wheat 2013 (above, old CROP) converted into two work orders for Wheat, with related Crop Area (below, new CROP)
1.2 PRODUCTION CYCLE: GENERAL DATA
Picture 4a: General data ( product, unit, status, expert model-if applied) from production cycle (above, old CROP) are displayed in work orders` header (below, new CROP)
1.2 PRODUCTION CYCLE: PLANNED DATA
Converting process rules:
a) Total plan QTY recorded within production cycle is calculated according to assigned Crop area size. Additional data about planned yield /ha is calculated automatically.
Example: 105 tonnes recorded as planned for Crop area 1706802_5: 23,75 ha and Crop area 541779_5: 1 ha with SUM: 24,75 ha results in 100,75 tonnes for 1706802_5:23,75 ha and 4,24 tonnes for 541779_5: 1 ha.
b) Planned start&end date from production cycles are not converted in any data in new crop: each work order Planned start date reflects first recorded realization task and meanwhile each work order Planned end date reflects last recorded realization task
Picture 4b: Planned yield data from production cycle (above, old CROP) are displayed and calculated in work orders` header as plan total (below, new CROP)
1.3 PRODUCTION CYCLE: REALIZATION DATA
Converting process rules:
a) As Realization part within Production cycles was not developed to the end no data from realization part are transformed to work orders header.
Picture 4c: Realized yield data from production cycle (above, old CROP) are not displayed in work orders within new CROP as work orders posses only data about individual crop area
1.4 PRODUCTION CYCLE: OTHERS
Picture 4d: Work order created for production cycle type 600 (above, old CROP) is converted and changed inot a new work order ID as a doc. type 60C ( below, new CROP)
1.5 PRODUCTION CYCLE:SEED
Picture 4e: For Seed calculations tab (above, old CROP) no linked/converted data within work orders is presented - in further development a seed QTY as part of expert model
1.6 PRODUCTION CYCLE: HISTORY
Picture 4f: History data within production cycles (above, old CROP) are displayed within individual work order as a task positions (below, new CROP)
2 Comparison of Farming task with Work order
Converting process rules:
a) Form Farming task is replaced by tree main entry forms:
- Right-click entry on individual work order´s position within Work order
- Task input and Planned task input within CROP&VEGs menu
- Input Daily work within Tools/Daily plan
b) Data recorded within Farming task are displayed within individual Work orders - all data recorded for individual crop area within tab Sowing/fertilization/Protection/Care and Cultivation/PRM Care and Cultivation/ PRM Mechanical tasks/ Other tasks/Moving/Grazing/ Product/ are displayed within individual work order as a position of work order.
2.1 TASK
Picture 5: Record for realized work: SOWING at 20.3.2013 for within production cycle Wheat 2013 for two Crop areas (above, old CROP) converted into position SOWING with Start date 20.3.2013 on two work orders, related to Product Wheat (below, new CROP).
2.2 WORKER
Converting process rules:
a) Hours total reported for production cycle are calculated according to Crop area size:
Example: 10 hours reported for John Sample for Crop area 1706802_5: 23,75 ha and Crop area 541779_5: 1 ha with SUM: 24,75 ha results in 9,6 hours for 1706802_5:23,75 ha and 0,40 hours for 541779_5: 1 ha.
Picture 6: Record for Workers, reported od task within production cycle Wheat 2013 (above, old CROP) converted within two work orders at Resource hierarchy at tab WORKERS with calculation of Task duration regards Crop area Size (below, new CROP).
2.3 USED CROP AREA
Picture 7: Data for used Crop area, recorded as %, within Farming task (above, old CROP) converted into data Plan Area (ha) and Done Area (ha) within Resource hierarchy for individual positions within work orders (below, new CROP).
2.4 MATERIAL WITH WAREHOUSES
Converting process rules:
a) Material Quantities recorded within Farming tasks are calculated regards Crop area size:
Example: recorded material Seed Lennox at range 4500 kg for two crop areas: 1706802_5: 23,75 ha and 541779_5: 1 ha with SUM 24,75 ha results in 181,82 kg for 541779_5: 1 ha and 4.318,18 kg for 1706802_5: 23,75 ha.
b) for each material data Plan/ha is calculated according to Crop area size
Example: recorded total material 4.318,18 kg for 23,75 ha results in 181,82 kg of Lennox seed per ha.
Picture 8: Data for type & quantities of material recorded within Farming tasks (above, old CROP) converted into data Plan QTY and Done QTY within Resource hierarchy, tab Material for individual positions within work orders (below, new CROP).
Picture 9: Data about material´s issuing warehouse recorded within Farming tasks by Used material (above, old CROP) converted into data within work orders/tab Documents/Issue/Materials (below, new CROP).
2.5 MACHINERY (SELF-PROPELLED&IMPLEMENTS)
Converting process rules:
a) within Farming tasks/ Tools Self-propelled and implements were assigned to individual task: in case more self-propelleds& implements were assigned in old crop no information about links among self-propelled&implements&worker is available therefore Self-propelled&Implemenst are displayed in Resource hierarchy tabs Self-propelled and Implements.
b) where Self-propelled &Implements was recorded for more crop areas, data about done time qty for individual self-propelled is calculated regards crop area size.
Example: assigned Tractor old and Seed drill recorded for at range 20 hours for two crop areas: 1706802_5: 23,75 ha and 541779_5: 1 ha with SUM 24,75 ha results in 0,81 hours for 541779_5: 1 ha and 19,19 hours for 1706802_5: 23,75 ha.
Picture 10: Data about assigned self-propelled&implements by individual task (above, old CROP) converted into data within Resource hierarchy as tab Self-.propelled &Implements (below, new CROP).
2.6 WORK ORDERS DOCUMENTS
Converting process rules:
a) All documents type 640 WO-Relieve for material and 660 WO-Relieve for service created within work order 600 in old crop are displayed within individual work order as doc. type 60C through tab Documents. Data are calculated according to Crop area size.
Example: QTY of Wheat Lennox seed recorded at range 4.500 kg within 13-600-00001 through linked document is display within individual work order 13-60C-000001 and 13-60C-000002 through tab Documents/ Issue.
Picture 11: Documents, created and linked through work order as a doc. type 600 (above, old CROP) are displayed within individual work order through tab documents/Issue (below, new CROP).
2.7 HARVESTED YIELD
Converting process rules:
a) Harvested yield data within Farming tasks are displayed within individual work order and calculated according to assigned crop area size.
Example: QTY of Yield Wheat at range 90 tonnes recorded for two crop areas 1706802_5: 23,75 ha and 541779_5: 1 ha with SUM 24,75 ha results in 3,64 tonnes hours for 541779_5: 1 ha and 86,36 tonnes for 1706802_5: 23,75 ha.
Picture 12: Harvested yield QTY & warehouse reported within farming tasks (above, old CROP) are displayed within individual work order through tab documents/ Receiving Documents (below, new CROP).