connecting the dots supply chain and grower management n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Connecting the Dots – Supply Chain and Grower Management PowerPoint Presentation
Download Presentation
Connecting the Dots – Supply Chain and Grower Management

Loading in 2 Seconds...

play fullscreen
1 / 46

Connecting the Dots – Supply Chain and Grower Management - PowerPoint PPT Presentation


  • 115 Views
  • Uploaded on

Industry specific cover image. Connecting the Dots – Supply Chain and Grower Management. Joel Schipper, Principal Solutions Architect. To booking a sale Against WIP and harvests in progress. Linking the plant forecast Single stage crops Multi-stage plants . The Challenge.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Connecting the Dots – Supply Chain and Grower Management' - lucius


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
the challenge
To booking a sale

Against WIP and harvests in progress

Linking the plant forecast

Single stage crops

Multi-stage plants

The Challenge
added complexity
Added Complexity
  • Multi-Stage Crops
    • Seedling
    • Initial plant stage, e.g., 3” pot or initial growth
    • Secondary plant stages, e.g.,
      • 1 gallon can
      • 5 gallon can
    • Final plant to be sold
  • One “harvest” per stage
    • New “harvest” cycle for each subsequent stage
    • Must carry history and cost through all stages
what s needed
Forecasting the Demand

Planning the required Crop Planting

Defining a “harvest” process (“BOM and Router”)

Defining multi-stage Plant Relationships

Starting a “harvest” in EnterpriseOne

Providing “harvest” visibility to Sales

Maintaining plant “WIP” visibility

Managing plant transformations for multi-stage plants and crops

What’s Needed?
what s needed1
What’s Needed?
  • Forecasting Demand
  • Planning the required Crop Planting
    • Defining a “harvest” process (“BOM and Router”)
    • Defining multi-stage Plant Relationships
  • Starting a “harvest” in EnterpriseOne
  • Providing “harvest” visibility to Sales
  • Maintaining plant “WIP” visibility
  • Managing plant transformations for multi-stage plants and crops
demand consensus
Demand Consensus
  • Statistical Forecasts from JDEdward Sales History
    • Some items monthly; others weekly (perennials)
  • Forecast input from other stakeholders, such as Sales, Production, Customers
  • Web and Excel review and input
  • Forecast Hierarchies
    • Key to executive acceptance of forecasts
managing stakeholder input

Location

Location

Location

Channel

Channel

Channel

Product

Product

Product

Managing Stakeholder Input

Key Customers

Sales

Operations

Demand Points

89%

93%

68%

Forecast Reconciliation based upon accuracy

Enterprise Forecast

slide8

Demand Consensus

Graphical representation of sales history, stakeholder forecast history, and stakeholder forecast.

Internal and external stakeholders can add value and increase forecast accuracy by forecast collaboration via the web, spreadsheets and any other time series of data

Flexibility with navigation through multiple user defined hierarchies and various units of measure

slide9

Demand Consensus

Comparison view of various stakeholder forecast

slide10

Demand Consensus

Demand Consensus Excel front end enables users to download various forecast versions, make changes locally, and upload changes, which are then immediately visible to all other stakeholders.

gaining consensus at any level

Define Demand Points

Database Model

  • Hierarchy
  • Units
  • Horizon
  • Time Buckets
  • Aggregation Levels

Location

Channel

Product

Gaining Consensus at any Level
what s needed2
What’s Needed?
  • Forecasting Demand
  • Planning the required Crop Planting
    • Defining a “harvest” process (“BOM and Router”)
    • Defining multi-stage Plant Relationships
  • Starting a “harvest” in EnterpriseOne
  • Providing “harvest” visibility to Sales
  • Maintaining plant “WIP” visibility
  • Managing plant transformations for multi-stage plants and crops
legacy plant planning systems
Legacy Plant Planning Systems
  • Need Demand forecast from EnterpriseOne
  • May know “BOM” or required consumables
  • May know Operations
    • Operation sequence (plant, fertilize, spray, prune)
    • Timing between operations
    • Calendar timing of key operations
      • E.g., can only prune in March/April
  • Would know sequence of multi-stage crops
    • Able to “back schedule” to earlier stages
slide14

Caculate Plant Supply from Forecast

Legacy, detailed plant level planning process.

Done once or twice a year between Sales and Production.

Ideal to link to a “Demand Consensus” process.

slide15

Define “BOM” of Consumables

Standard “BOM”.

Easily imported into EnterpriseOne.

slide16

Define Crop Operations

The Router for making a 6462 in a 1 gal can (item 6462M).

Notice multi-year calendar.

Could have plant spacing, environmental info as well

legacy systems to enterpriseone
Legacy Systems to EnterpriseOne
  • Master Data to be mapped and integrated
    • Periodically updated for changes
    • Item Master of Plants
    • Product Structures (Plant BOM’s)
    • Plant Routers
    • Attribute and other codes such as work centers in these 3 files
slide18

Multi-Stage Crop Relationships

“Item tree” relationship that links the items that lead to the creation of the #2 can from a 3” pot that came from a root cutting.

Each step is an SKU with a router.

legacy systems to enterpriseone1
Legacy Systems to EnterpriseOne
  • Dynamic Data
    • Pushed to E1 after the planning process: once/twice annually
    • Planned Order Extraction: the master schedule file
      • Plant Starts to E1 MRP message workbench
      • Includes all starts related for an multi-stage plant
      • Planned order changes due to forecast changes
      • Revises any previous messages that were not firmed in E1
what s needed3
What’s Needed?
  • Forecasting Demand
  • Planning the required Crop Planting
    • Defining a “harvest” process (“BOM and Router”)
    • Defining multi-stage Plant Relationships
  • Starting a “harvest” in EnterpriseOne
  • Providing “harvest” visibility to Sales
  • Maintaining plant “WIP” visibility
  • Managing plant transformations for multi-stage plants and crops
enterpriseone mrp
EnterpriseOne MRP
  • Legacy Plant Planning system loads top level plant starts into the MRP message table
    • Example: 46902 Gold Coast Juniper #2 Gallon
  • Lower level plant items are consolidated
    • Legacy plant planning system consolidates and loads these requirements for earlier stage plants
    • Example: 46903P 3” potted GC Juniper
  • New MRP message type for Grower Harvests
    • Driven by new JDE item type
    • Allows demand to flow down to related “kit” of soils, fertilizers, containers, stakes, etc.
mrp grower harvest message release
MRP “Grower Harvest” Message Release
  • MRP Message Release
    • Opens Grower Harvest record
    • Brings in expected quantity and ending date
    • Harvest defaults remaining fields from Block information
      • Block definition is identical with plant item/size
  • Initiates Workflow to track next steps in a business process
    • Review Harvest record
    • Attach and release harvest work order
  • Note: MRP ST/OT Transfer Messages
    • Still generated for location transfers of finished goods for sales
      • Grown in one location; sold in another
grower management background information
Grower Management(Background Information)
  • Grower Management tracks the progress of the crop from planning through harvest, regardless of type of crop.
    • What and how much will be grown?
    • Where is the crop being grown?
    • When will it be ready for harvest?
    • What cultivation activities such as fertilizing or irrigation need to be done and when?
    • How much will be harvested?
    • What is the quality of the harvested crop?
  • One or more crops (harvests) per year
    • Or a multi-year crop (e.g., forestry)
grower management handles the farm and field
Grower Management Handles the Farm and Field
  • Defines and assign specific origins (blocks, lots, fields) to crops
  • Tracks progress of cultivation and crops, whether internally or externally owned
  • Records the use of any chemicals
  • Understands the costs of growing the crop
  • Updates and sees entire anticipated harvests to verify consistent supply
  • Receives a single crop as different SKUs using Product Variants
  • Creates a history so that good years can be repeated
grower management features
Harvest Management

Track many block and harvest attributes

Develop crop estimates for supply planning

Manage intended use

Mass updating capabilities reduce administration

Farming Activities

Plan growing activities

Track actual growing activities performed

Track operational cost

Record chemical usage

Grower Management Features
  • Weigh Tag Receipt
    • Plan receiving activity
    • Record quality results against receipt
    • Over-receive
    • Receive product variants, alternate SKU’s
slide30

Operations from Legacy

Plant Planning system

enterpriseone back to legacy plant planning systems
EnterpriseOne back to Legacy Plant Planning Systems
  • From Grower Management
    • Grower Harvests started
      • Related Work Order number, quantity, date
    • Grower Harvest completions
      • Quantity and date received
    • “Left over” end of season inventory
what s needed4
What’s Needed?
  • Forecasting Demand
  • Planning the required Crop Planting
    • Defining a “harvest” process (“BOM and Router”)
    • Defining multi-stage Plant Relationships
  • Starting a “harvest” in EnterpriseOne
  • Providing “harvest” visibility to Sales
  • Maintaining plant “WIP” visibility
  • Managing plant transformations for multi-stage plants and crops
connecting growing and sales
Connecting Growing and Sales
  • Sales needs visibility into plants that are growing and will be sold in the current season
    • Make the connection from Grower Mgt to Sales through an inbound “PO”
      • Grower Harvests are already taken against an on-the-fly PO
    • Sales can now see the harvest on standard Supply & Demand Inquiry as a “PO”
sales sees incoming harvest
Sales sees Incoming Harvest

Standard S&D Inquiry

proposed enterpriseone grower enhancements
Proposed EnterpriseOne Grower Enhancements
  • New MRP “Grower Harvest” message release
    • Creates Grower Harvest and related PO line
      • Informs Sales of current expected harvest quantity and date
      • PO line is received at weigh tag operation
what s needed5
What’s Needed?
  • Forecasting Demand
  • Planning the required Crop Planting
    • Defining a “harvest” process (“BOM and Router”)
    • Defining multi-stage Plant Relationships
  • Starting a “harvest” in EnterpriseOne
  • Providing “harvest” visibility to Sales
  • Maintaining plant “WIP” visibility
  • Managing plant transformations for multi-stage plants and crops
proposed enterpriseone grower enhancements1
Proposed EnterpriseOne Grower Enhancements
  • PO line sets up “traditional inventory” lot/location record with zero cost
    • Allows for WIP inventory and cycle counting
    • PO receipt “closes out” the traditional inventory quantity
  • In Grower, do an Operational close by date range over all active work orders in grower harvests
inventory availability
Inventory Availability

“WIP” Plants in normal F41021

detail availability
Detail Availability

“WIP” Plants in normal inventory detail

wip detailed inventory report enhancement
WIP Detailed Inventory ReportEnhancement
  • Similar to Lot/Location inquiry
  • Location comments stored as attachments
what s needed6
What’s Needed?
  • Forecasting Demand
  • Planning the required Crop Planting
    • Defining a “harvest” process (“BOM and Router”)
    • Defining multi-stage Plant Relationships
  • Starting a “harvest” in EnterpriseOne
  • Providing “harvest” visibility to Sales
  • Maintaining plant “WIP” visibility
  • Managing plant transformations for multi-stage plants and crops
transform operation
Transform Operation
  • New Base “Transform” Operation to consume a previously grown plant
    • Carries forward accumulated attributes, costs, and operational history of the consumed plant to support lifetime track/trace history
    • Could be last or first WO step
    • Another use case is doing more work (pruning) to saleable stock