Resolve SCADA Batch ID Errors
Budget: ₹12,500 – ₹37,500 INR
I’m running a live rubber-plant production system where SCADA writes every batch into SQL Server 2008. Actual weights and totals are perfect, yet the batch IDs that feed our SSRS reports appear twice at times or vanish altogether. These anomalies happen randomly; they are not linked to shift changes or load spikes.
The job is a surgical fix. I do not want an audit or a redesign and there will be no PLC modifications or on-site work. All that is needed is to correct the existing SCADA script–to–SQL transaction logic so that one batch generated upstream produces one and only one row in the database, and every consecutive number is present.
You’ll be working remotely on:
• SCADA scripting (our environment supports WinCC, Wonderware, Ignition or Citect; bring whichever expertise matches what you discover in the code)
• Microsoft SQL Server 2008 objects involved in the insert logic
• Any Report Builder / SSRS query that may be compounding records through JOINs or retry logic
Deliverables
1. Updated SCADA script or stored procedure that guarantees idempotent inserts.
2. Adjusted SSRS query (if necessary) so the report aligns 1:1 with live data.
3. A short hand-off note summarising the exact change and how it prevents future duplicates or skips.
Acceptance will be based on a live demonstration period in which the production system runs continuously and each new batch ID is written exactly once with no gaps unless a batch is deliberately cancelled.
If you have proven experience handling SCADA-to-SQL transactions and can step straight into a running plant without disrupting production, I’d like to hear how you would approach the fix and a realistic turnaround time.
The job is a surgical fix. I do not want an audit or a redesign and there will be no PLC modifications or on-site work. All that is needed is to correct the existing SCADA script–to–SQL transaction logic so that one batch generated upstream produces one and only one row in the database, and every consecutive number is present.
You’ll be working remotely on:
• SCADA scripting (our environment supports WinCC, Wonderware, Ignition or Citect; bring whichever expertise matches what you discover in the code)
• Microsoft SQL Server 2008 objects involved in the insert logic
• Any Report Builder / SSRS query that may be compounding records through JOINs or retry logic
Deliverables
1. Updated SCADA script or stored procedure that guarantees idempotent inserts.
2. Adjusted SSRS query (if necessary) so the report aligns 1:1 with live data.
3. A short hand-off note summarising the exact change and how it prevents future duplicates or skips.
Acceptance will be based on a live demonstration period in which the production system runs continuously and each new batch ID is written exactly once with no gaps unless a batch is deliberately cancelled.
If you have proven experience handling SCADA-to-SQL transactions and can step straight into a running plant without disrupting production, I’d like to hear how you would approach the fix and a realistic turnaround time.