1. Filling the sub-supplier update request
1.1. Display supply chain view of sub-suppliers?
2. Reviewing the sub-supplier update request
2.1. Activate / Deactivate
2.1.1. Activating per supply chain
2.1.1.1. Requirements are always per supply chain. If a sub-supplier is de-activated by a supplier :
2.1.1.1.1. Suspend requirements of this supplier / sub-supplier combi
2.1.1.1.2. Suspend and hide requirements of this supplier/sub-supplier combi
2.1.1.2. Deactivate = Archive Activate = de-archive
2.1.1.2.1. Removes all requirements
2.1.1.2.2. Hides all documents
2.1.1.2.3. Hides sub-supplier
2.1.1.2.4. Archive per supplier?
3. A leading, stand-alone seasonal intake. No auto request to subs.
3.1. Based on this seasonal intake, All provided subs are added, nothing removed
3.1.1. By default NO request to subs, just to directs.
3.2. Fewer request
3.2.1. Not per se organisation clutter reduction
3.3. Label/Note when sub-supplier was last submitted in seasonal intake
3.3.1. Allows you to filter/note which subs are active
3.3.1.1. Where do you want to see / track
3.4. :question: Which sub suppliers are send during a growerlist/tracebility sheet? All, or specific for this buyer.
3.5. :question: Is it relevant to display the existing base? Does that help the supplier? We assume this only helps when you know it by heart / head?
3.6. :question: Technical feasibility question: Based on seasonal supplier updates, can we immediately fetch information from Global GAP based on GGN?
3.6.1. :question: If so, can we use this organisation input to show requirements on the spot? I.e. social high risk or low risk?
3.7. :question: How feasible is this sub-supplier intake? Will suppliers do this?
3.7.1. Is this worth it for our users? I.e. 100 certificates, judge and match based on GGN (including creating organisations). This depends on our solution / UX.
3.7.1.1. Can we simplify this, for example by automatching documents to organisations based on filename [hackathon idea!].
3.7.2. Or is it enough to just indicate what they have / how they are certified?
3.8. :warning: Regardless of how smart we can request documents during seasonal intake - there will always be order based documentation (lab reports for example)
3.8.1. :question: What will be the trigger to fetch those?
4. Share up to date suppliers
4.1. Upload excel
4.2. Upload excel & compare to currently known list
4.3. Manually, based on currently known list
5. (Effect on) automatic requests
5.1. Requests are always off for sub-suppliers. The seasonal intake replaces this dynamic, to still get in the right documentation but prevent from spamming.
5.2. The seasonal intake determines active/inactive for each sub-supplier (during the set timeframe for the corresponding season).
6. How/when to gather documentation
6.1. During seasonal intake. Is this feasible on the supplier end? And desirable on the user end?
6.2. In a request after the seasonal intake (when new suppliers are checked against requirements)
6.3. Only when they've actually supplied product, i.e. after order
6.4. During seasonal intake one only shares what documentation/certification is available. The actual document is shared after order.
7. Trigger seasonal intake
7.1. Manually
7.2. Manually + remember for next year (send automatically or nudge)
7.3. Based on rules (product on organisation level needed)
8. Problem: Dev capacity
8.1. A.
8.1.1. Focussed on season and product
8.1.1.1. Value
8.1.1.1.1. We can comfortably de-activate subs for a particular product. Saves user effort in managing subs.
8.1.1.2. Effort
8.1.1.2.1. Higher
8.1.1.3. Risk
8.1.1.3.1. Too advanced?
8.1.1.3.2. Requires more data on sub-suppliers
8.1.1.4. Fit with Strategy
8.1.1.4.1. Good - supply chain oriented.
8.1.2. Details
8.1.2.1. Products per organisation required
8.1.2.2. Activate and de-activate per product
8.2. B.
8.2.1. Focussed on collecting organisations
8.2.1.1. Value
8.2.1.1.1. no declutter, but more automatic update of the supplier base.
8.2.1.2. Effort
8.2.1.2.1. Less
8.2.1.3. Risks
8.2.1.3.1. Seasons overlap: Deactivating organisations that should be active for other seasons.
8.2.1.3.2. Auto request are off for subs, but can we collect documents pre-order? Or do we rely on manual-post order request?
8.2.1.4. Fit with Strategy
8.2.1.4.1. Limited
8.2.2. Details
8.2.2.1. Do not decide which to remove
8.2.2.2. Manual
8.2.2.3. Add all new
8.2.2.4. In bulk
8.2.2.5. Simple.
9. What information is required
9.1. Pre-season
9.1.1. Proposed pesticide list
9.1.1.1. PER Producer a excel template must be filled with a bunch of data.
9.1.2. Preferred supplier information sheet / Proposed producer list / Grower overview (Interestingly requested from type **producer)**
9.1.2.1. Per product
9.1.2.1.1. Each packhouse used
9.1.2.2. Per grower
9.1.2.2.1. Grower name
9.1.2.2.2. Grower identifier
9.1.2.2.3. Plot code
9.1.2.2.4. Production season start & finish
9.1.2.2.5. Area size HA which is present on the GLOBALG.A.P.
9.1.2.2.6. Estimated production volume ton/ha
9.1.2.2.7. CSR program / scheme / accreditations (No document)
9.1.2.2.8. Variety
9.1.2.2.9. Area m2
9.1.2.2.10. Planting date
9.1.2.3. Per packhouse (Not always)
9.1.2.4. All different formats supplied by suppliers
9.1.3. Transparency sheet / Update on which growers
9.2. Post-order
9.2.1. Packing list of growers
9.2.2. Lab analysis
9.2.2.1. Residue
9.2.2.1.1. Per plot
9.2.2.2. Mircobio
9.2.3. Certificates
9.2.3.1. Food Safety
9.2.3.2. Social
9.2.4. Audit reports
9.2.5. Spray list/ Spray report
10. initiating the sub-supplier update request
10.1. Seasonal intake
10.1.1. No pre-listed sub-suppliers
10.1.1.1. Manually
10.1.1.1.1. Ask for a whole new set
10.1.1.1.2. Display complete current sub-supplier chain. for supplier to select from.
10.1.1.2. Automatically
10.1.2. Pre-listed set of subsuppliers
10.1.2.1. Manually
10.1.2.1.1. Offer users a filter and selecting page to compose list.
10.1.2.1.2. Still need to add information to sub-supplier to filter on like product, then why not automate it?
10.1.2.2. Automatically
10.1.2.2.1. How do we get product on sub-suppliers initially?
10.1.2.2.2. Based on the product and country of sub-suppliers we compose a list of sub-suppliers per season.
10.2. Order intake
10.3. Bijkoop intake
11. Requesting documents about sub-suppliers
11.1. Possible to Display requirements about active sub-supplier to supplier directly?
11.1.1. Documents not yet available?
11.1.1.1. How long before a season does requesting start?
11.1.2. helene.vandendries@agriplace.com
11.2. After new sub-suppliers are created, system will automatically match requirements and send out automatic request.
11.2.1. Again a request
11.2.2. If a sub-supplier that was already existing in another supply chain this other provider will also receive the request.
12. Who needs to manage subs (pre-purchase)
12.1. Roveg - Preferred suppliers extensive information required
12.2. Keelings (Not in requirements, self uploaded grower overviews)
12.3. Euro Berry (Proposed pesticides list ?)
12.4. Nosibe (Growerl overview)
12.5. N&K (Grower overview)
13. The Network
13.1. Chain
13.1.1. Basic accounts
13.1.2. Data requirements
13.1.2.1. CO2 Footprint
13.1.2.2. Pesticide
13.1.2.3. Sustainable measures taken?
13.2. Farm
13.2.1. Farmers
13.2.1.1. Profile
14. Product
14.1. The customer ALDI (ALDI Nord, ALDI SOUTH Germany, HOFER Austria) demands SPRING as mandatory add-on for selected fruit and vegetables originating from water risk regions (apples, avocados, bananas, blueberries, carrots, cucumbers, grapes, lemons, lettuce, limes, mushrooms, oranges, peppers, potatoes, strawberries and tomatoes).
14.2. From January 1st, 2023, the customer Lidl will only trade Rainforest Alliance-certified goods for the products mango and avocado. Therefore, we require a current Rainforest Alliance certificate from all avocado and mango producers who deliver to the customer Lidl.
14.3. Dry matter statement (Mango / Avocado
14.4. Currently added as tags to organisations and to document metadata
14.5. Requesting product specific documents: Rule only with product tag. Tag management is now easier too. Why is that not enough?
14.5.1. More details required in product suitability