Livestock Data Automation & Excel Dashboard

Job ID: 39841934

Budget: $250 – $750 AUD

Project: Livestock Data Automation + Excel Dashboard
Overview
We are building a data pipeline and reporting solution. Some work will happen in my tenant (our infrastructure, APIs, OCR, Power Automate Premium) and some in client’s tenant (email flow, document storage, draft email).
________________________________________
Milestones & Task Breakdown
Milestone 1 — MLA API Integration (my tenant)
• In my tenant, develop an Azure Function or API wrapper to consume MLA public data (price grids, benchmarks, etc.).
• Include data filtering, schema mapping, caching, error handling, and retry logic.
• Deliver sample endpoint calls and documentation.
Milestone 2 — Email Intake & Document Routing for Kill Sheets and Feedback sheets (mix my tenant, client tenant)
M2 - My tenant
• In my tenant, build a Power Automate flow triggered on inbound email that matches defined sender / subject.
• Use identifiers (ABN, PIC, fuzzy name matching) against client master data (SharePoint list) to identify which client the email belongs to.
• Save kill sheet attachment into a client-specific folder in my tenant SharePoint.
• Compose an email to my client with the original document + MLA insights (retrieved by calling the MLA API) and customer code.
M2 - Clients tenant – Solution to be imported
• In clients tenant, build a Power Automate flow triggered on inbound email from me. Use identifiers (Customer code) against client master data (SharePoint list) to identify which client the email belongs to. Retrieve client email address.
• Save kill sheet attachment into a client-specific folder in client’s SharePoint.
• Forwards the email (inc attachments) to the clients email address leave it in Drafts (do not auto-send for human in the loop vetting).
Milestone 3 — Data Extraction & Table Creation (my tenant)
M3 - My tenant
• Use the same email trigger flow from Milestone 2 as input for parsing.
• In my tenant, process the attached kill sheet via OCR / Document Intelligence PAYG Azure, extract structured data (weights, grades, dates, etc.).
• Normalize fields using lookup tables (client master, species converter, abattoir list) stored in my tenant. This will be difficult as no two processors supply the information in the same format or industry language. Model will need to be trained to read the 8 different processor templates accurately.
• Append to list in my tenant Include data filtering, schema mapping, caching, error handling, and retry logic.
• Flag or mark the original inbound email in my tenant as processed/completed if flow worked correctly. If not add a planner task due today to look into this.
• Use that same detail to create a table to email to client (aim to append to list in his database.)
M3 - Clients tenant – Solution to be imported
• Receive email above
• Append table to Sharepoint list
• Flag or mark the original inbound email as processed/completed if flow worked correctly
Milestone 4 – Buying Grids Intake and Broadcast
M4 – My tenant
• In my tenant, build a Power Automate flow triggered on inbound email for buying grids that matches defined sender / subject. This will be from an email forwarded from my client.
• Extract grid data using OCR Azure PAYG
• Compose a document using the information extracted on a branded pdf.
• Draft an email attaching the above document and Add in Market insights from API integration and customGPT to obtain localised industry data.
• Save kill sheet attachment into a client-specific folder in my tenant SharePoint.
• Flag or mark the original inbound email as processed/completed if flow worked correctly. If not add a planner task due today to look into this.
M4 - Clients tenant – Solution to be imported
• In clients tenant, build a Power Automate flow triggered on inbound email from me. Use identifiers (processor info) against processor master data (SharePoint list) to identify which processor the email belongs to.
• Save kill sheet attachment into a processor specific folder in client’s SharePoint.
• Creates an email draft (inc attachments) to the clients email address from the Client list BCC for privacy. Leave it in Drafts (do not auto-send for human in the loop vetting).
• Flag or mark the original forwarded email that started the flow as processed/completed if flow worked correctly.
Milestone 5 — Excel Dashboard & Secure Client Reporting (my tenant → client shared)
• In my tenant, build an Excel workbook using Power Query + Power Pivot that ingests the data table produced from Milestone 3.
• Create PivotTables, charts, slicers, filters to allow dynamic data exploration.
• Develop a refresh/update workflow (manual, semi-automated, or script) in my tenant so the workbook can be updated when new data arrives.
• For each client, prepare a version or filtered view and export/share via secure “specific people” links from OneDrive / SharePoint that clients can open their workbook without needing extra licences.
• Provide instructions and optional automation (Power Automate Desktop, script) for refreshing and republishing it securely.
________________________________________
Different Tenants
I can provide access to only my tenant for the major build and copies of the tables.
My client will need these as an exported solution.
________________________________________
Deliverables & Acceptance Criteria
• MLA API wrapper + documentation (my tenant)
• Power Automate flow in client’s tenant for email intake, routing, draft generation
• Data extraction logic in my tenant producing clean table from the same email flow
• Excel dashboard workbook(s) built in my tenant and securely shared to client
• Secure distribution mechanism so client sees only their data (via client’s tenant share links)
• Deliverable in as soon as possible but not exceeding 1 week
• Quote needed for the project, not per hour
• Sample documents can be provided after NDA and IP Agreement signed and bid provisionally accepted. Quote will be confirmed and deposit paid after Freelancer has viewed the documents and confirmed scope and quote.
• Won't accept a requote after the job is accepted unless the scope changes.