MC Systems · the solar division of MC Consulting — an engineering practice since 1984

How much of your project capacity goes to tasks that don't require a project manager?

It might be the front end — bids nobody had the hours to answer. It might be the back — an asset built and not earning while the closeout package is finished. We do not assume we know which. Two days on site tells us where the capacity actually goes, and we say plainly what is worth automating and what is not.

Four times the audit fee, or there is no invoice.If the audit does not surface at least four times what the audit itself costs, in recoverable annual cost, you are not billed for it. You keep the written finding either way. The guarantee covers the audit — anything we build afterwards is quoted and agreed separately.
Which End

Most people who call you already know what they are going to sell you.

We do not. Sometimes the pipeline is the constraint and the delivery side is fine. Sometimes the pipeline is healthy and the work is stuck behind paperwork nobody has time to finish. We have seen both, and we have been wrong guessing from the outside.

So the audit covers the whole run — marketing, sales, estimating, contracts, permitting, engineering, procurement, project management, field, commissioning, closeout, O&M, finance. Fifteen departments. Two days. Then we tell you where the hours actually go, what would be worth changing, and what we would leave alone.

Roughly one audit in three concludes the highest-value workflow is not worth automating yet.Usually because there is no verifiable source of truth to build on. Saying so is part of what you are paying for — the sequencing advice is worth the fee on its own.
Cost of Delay

One reason the back end is worth measuring: in your sector the clock has a price.

In most industries late paperwork costs time. In renewable it costs money per day, and the amount is calculable rather than abstract. That does not mean it is where your problem is — only that if it is, the number is knowable. These are the three places it tends to hide.

Unbilled revenue

An asset that is built but not energized earns nothing. Every day between mechanical completion and commercial operation is revenue the project financed for and did not collect.

Ask yourself
What was the gap between mechanical completion and COD on your last project — and what was a day worth?

Statutory deadlines

Tax credit qualification runs on dates that do not move. A closeout package that slips past a deadline does not cost you a week — it changes the economics of the project.

Ask yourself
Has documentation timing ever put a credit deadline at risk on one of your projects?

Interconnection position

Queue positions carry real option value and real re-study risk. Documentation that holds up an interconnection milestone puts something far more expensive than engineering hours at risk.

Ask yourself
Who owns interconnection paperwork — and what else is that person supposed to be doing?
The Two Engines

One system, two engines — pipeline in, projects out.

The usual answer is a separate tool for each, bought at different times for different reasons. We build a single system that automates the repetitive work at both ends of the business, and leaves every consequential judgment with your people. Which engine you need first — or whether you need both — is what the audit establishes.

Engine 01 · Pipeline in

Growth

Winning more of the work you already see.
  • RFP and proposal throughput — the reusable portion drafted, so the estimator spends the time on price and scope.
  • Identify and target the right prospects — developers, EPCs and asset owners that match the work you actually want.
  • Personalised outreach at scale — relevant and specific, never templated blasts.
  • Follow-up that does not get dropped — the sequence runs whether or not anyone remembers.
  • A pipeline you can see — what is in it, what stage, and what it is worth.
The judgment about who to pursue and what to say stays with your people. The list-building and the copy-paste does not have to.
Engine 02 · Projects out

Delivery

Faster closeout, so finished assets start earning.
  • Commissioning documentation and closeout — test records, punch lists, as-builts and turnover packages generated per asset from the commissioning record.
  • Compliance and performance reporting — offtaker, lender, utility and regulator reports drafted from the source of record.
  • Submittals and equipment packages — verified against the specification, not against the last project.
  • Legacy integration knowledge — captured and searchable, so schedules stop depending on who is on site.
  • Every figure traceable — checked against a primary source before it ships.
Built on fifty-two years of commissioning discipline. The engineer keeps the judgment; the paperwork does not need one.
Which end is the constraint?Sometimes it is the front. Sometimes the pipeline is fine and the work is stuck behind paperwork. Sometimes neither, and the honest answer is that nothing here is worth building yet. We measure both before recommending either.
What We Remove

Six places the hours usually go. None of them require the expertise.

These are the six we find most often across renewable contractors — three at the front of the business, three at the back. Every one is drafting, assembling, chasing or reformatting — work that consumes commissioning engineers and project managers without requiring their judgment. Whether any of them are true in your operation is the part only you can answer, and it is worth answering before anyone talks about tools.

01
Commissioning documentation & closeout
Test records, punch lists, as-builts, O&M manuals and turnover packages assembled from the same source data over and over, per block, per inverter, per site. Structured once, generated per asset, verified against the commissioning record rather than retyped from it.
Ask yourself
How many people touch a turnover package before it ships, and how much of that is retyping?
02
Compliance & performance reporting
Recurring reports to offtakers, lenders, interconnecting utilities and regulators — same shape every period, assembled by hand from SCADA exports and spreadsheets. Drafted automatically from the source of record, with every figure traceable to where it came from.
Ask yourself
Who assembles your monthly offtaker and lender reports, and how many hours does it take?
03
Submittals, RFQs & equipment packages
Vendor datasheets, cut sheets, certifications and equipment submittals compiled per project, most of it substantially identical to the last one. Retrieved, cross-referenced against the specification, and assembled — with part numbers verified against the manufacturer's published record rather than against the last project.
Ask yourself
When you decline an RFP, is it because it was a bad fit — or because nobody had the hours?
04
Legacy control integration knowledge
The tribal knowledge of how the older assets are wired, addressed and integrated — usually held by two or three people, undocumented, and a schedule risk every time one of them is unavailable. Captured, structured and made searchable in plain language.
Ask yourself
If your two most experienced integration people were unavailable next month, what would slip?
05
Proposal and bid assembly
Qualifications, exclusions, safety record, insurance, references and resumes rebuilt for each submission, with compliance matrices answered line by line. The reusable portion drafted from a maintained library so the estimator spends the time on price and scope.
Ask yourself
Open two recent proposals side by side. How much of the second one already existed in the first?
06
Opportunity capture and follow-up
Opportunities arriving across portals, inboxes and phone calls, tracked in whatever each person uses. Captured into one log with the reason a bid was declined recorded alongside it — which is the number almost nobody has.
Ask yourself
Of the work you turned down last year, how much was a bad fit and how much was a calendar problem?
Why Us

Commissioning discipline does not care what generates the electricity.

MC Systems is the solar division of MC Consulting, an engineering practice since 1984. The reason this transfers is that the underlying discipline was never about reactors. It was about proving a system does what the specification says before anyone signs for it — and documenting it well enough that someone else can verify the claim years later.

Palo Verde · Arizona Public Service
Computer systems startup across all three units

Balance-of-plant monitoring, control rod systems, radiation monitoring, security and water treatment — then trained the utility's own personnel to run them.

Vogtle Units 1 & 2 · Georgia Power
Startup work package controls

Two and a half years authoring procedures and controlling the startup work package process through commissioning of both units.

Savannah River · DOE · Top Secret
$4M cost overrun averted

Design team and onsite startup engineer for the site-wide electronic safeguards system. A fiber modem circuit redesign prevented forced replacement of every dual-link fault-tolerant modem on site.

ECOS Systems · multi-site portfolios
Energy control across 30 locations

Turnkey energy evaluations with 24/7 monitoring; automated energy-control systems reducing electricity and gas consumption across a multi-site portfolio.

Five power stations, one DOE weapons facility, and 350 miles of fiber. After the first assignment, never as plant staff — always the outside specialist brought in to bring systems up, verify them against specification, and hand the discipline to the client's own people. That is the same engagement a renewable developer needs at closeout.
Contact

Twenty minutes. No pitch deck. Mostly you talking.

I will ask how the work actually moves through your company — where it starts, who touches it, what happens between winning a job and closing it out. At the end I will tell you whether I think there is something worth measuring properly, or whether there is not. Both are real answers, and you will get one either way.

PracticeMC Systems — solar division of MC Consulting, Inc.
Practising since1984 · Arden, North Carolina
First call20 minutes · no charge · no deck
AuditTwo to three days on site · quoted after the first call · four times the audit fee in recoverable cost, or no invoice
ServingCommercial and utility-scale EPCs, developers, O&M and subcontractors