Solutions · Utilities
Integration controls for co-ops and public power.
Retire the Scribe jobs that feed Dynamics GP and WAMS. Then run outage, meter-exception, work-order and permit flows through the same gates, with the same audit trail.
Why now
TIBCO ended maintenance for Scribe Insight on 30 November 2022, and extended support for eligible customers on 30 November 2023.1 Perpetual licences keep running, so most Scribe jobs are still running: unpatched, unsupported, and understood by one person if anyone.
Microsoft will end product support and updates for Dynamics GP on 31 December 2029. Security patches continue until 30 April 2031.2 Every job you run on either product is a job you will rebuild at least once. Rebuild it once, behind a gate, with a shadow run to prove it, and the next move is a configuration change.
Job shapes
The jobs, as a utility runs them.
Each shape is a job template plus a rule pack. The source, the gate and the destination are configuration. The control is the same in every one.
PM voucher batch
AP export from your CIS or AP system to a Dynamics GP Payables batch. Held over an amount threshold; two-person approval over a higher one. Lands unposted, so the accountant still posts.
PA timesheet batch
Timekeeping export to a GP Project Accounting timesheet batch. Hours exceptions held for a supervisor. Per-line results back to the source.
PA miscellaneous log
Equipment and material logs to GP Project Accounting. Cost-code checks before posting, with a hold for anything that does not match the project.
Capital sales order
Capital jobs from the CIS to a GP sales order. Approver named by amount. Posted once, with the idempotency record to prove it.
Meter-exception routing
AMI or MDM exceptions routed by type: some to a WAMS work order, some held for a reviewer, all on one board with the age of each.
Outage escalation
OMS events escalated to Teams or email when nobody acknowledges them within the window you set. Each escalation is an audit line.
Work-order dispatch
Work orders from the CIS or OMS into WAMS, with a hold when the crew, the asset or the cost code is missing.
Permits and inspections
Permit requests and inspection results between the portal, WAMS and GP. A person clears what the rules cannot.
"In pilot" means the shape is running for our founding customer. "Reference" means it runs in our utility test bed and has not yet gone live at a utility.
Method
How a Scribe retirement runs.
Inventory
Every job on one sheet: name, source and target systems, money moved, cadence, owner, failure history. Rank by risk, not by convenience.
Rebuild one job as configuration
A job template, a rule pack and a manifest. The GP adapter and the file readers already exist; what changes per job is data.
Shadow run
The Scribe job keeps posting. Redflow runs the same input and compares the result line by line. You see the diff every day.
Cut over when the diff is zero
Turn the gate on, turn the Scribe job off. If something is wrong, turn it back. The idempotency record means nothing posts twice during the swap.
Next job
Same engine, same gate types, same board. The second job is faster than the first and the eighth is a configuration review.
What stays where
The GP adapter runs inside your network and pulls from the cleared stream. There is no inbound connection into GP, WAMS or your CIS from outside. Approvers get a notice by email or Teams and approve in Redflow or by reply. See Deployment andSecurity.
Sources
- TIBCO, "Support Policy: Retirement Notice for TIBCO Scribe Insight" (KB0107020) and "TIBCO Scribe Insight Retirement Frequently Asked Questions" (KB0072675):retirement notice,FAQ.↩
- Microsoft, "Announcing End of Support for Dynamics GP", Dynamics 365 Blog, 25 September 2024, updated 15 January 2025:blog post; Microsoft Lifecycle,Dynamics GP.↩
Bring the Scribe job you trust least.
We will show the inventory sheet, the shadow diff and the gate for that one job.