Industry specific cover image

Connecting the Dots – Supply Chain and Grower Management

Joel Schipper, Principal Solutions Architect

The Challenge

• To booking a sale• Against WIP and

harvests in progress

• Linking the plant forecast• Single stage crops• Multi-stage plants

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?

• 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

• 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

Operations Sales Key Customers

Demand Points

Enterprise Forecast

Forecast Reconciliation based upon accuracy

89% 93% 68%Product

Location

Cha

nnel

Product

Location

Cha

nnel

Product

Location

Cha

nnel

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 dataFlexibility with navigation through multiple user defined hierarchies

and various units of measure

Comparison view of various stakeholder

forecast

Demand Consensus

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

Product

LocationC

hann

el

Define Demand Points

• Hierarchy

• Units

• Horizon

• Time Buckets

• Aggregation Levels

Database Model

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

• 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

Legacy, detailed plant level planning process.

Done once or twice a year between Sales and Production.

Ideal to link to a “Demand Consensus” process.

Caculate Plant Supply from Forecast

Standard “BOM”.

Easily imported into EnterpriseOne.

Define “BOM” of Consumables

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

Define Crop Operations

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

“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.

Multi-Stage Crop Relationships

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 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

• 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 Message

Review

Soil Message ReleaseUse New Item and MessageType to recognize “plants” and to release “Grower Harvests”

Consumables for a Plant

Explosion also creates demand for Plant “BOM” items

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 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

• 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

• Weigh Tag Receipt• Plan receiving activity• Record quality results

against receipt• Over-receive• Receive product variants,

alternate SKU’s

MRP Message Release “adds”

a Harvest record

Operations from Legacy

Plant Planning system

Track Details such as Spraying

Track Labor, Consumables, Equipment

Perform Many Other Activities

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 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

• 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

Standard S&D Inquiry

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 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 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

“WIP” Plants in normal F41021

Detail Availability

“WIP” Plants in normal inventory detail

WIP Detailed Inventory ReportEnhancement

• Similar to Lot/Location inquiry• Location comments stored as attachments

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

• 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

Know More. Do More. Spend Less.