Creating a Smart Manufacturing or Digital Manufacturing portfolio for a consulting company is one of those things that sounds simple on paper but is anything but in real life. Over the past two decades, I’ve built and led practices from scratch — first in the Americas, then in the U.S., and more recently, I’ve been on the “industry side” designing architectures for a global manufacturing company. Here’s what I’ve truly learned about building a portfolio that works, what actually matters, and a few things I wish I’d done differently.
Why Build a Portfolio? (And What Does That Even Mean?)
A portfolio isn’t just a fancy PowerPoint with a bunch of logos and buzzwords. It’s the set of services, solutions, and capabilities you can repeatedly deliver, that actually solve real manufacturing problems. In my experience, the best portfolios are living toolkits — not static lists. They’re built from what you know how to deliver, the accelerators and templates that make you faster and more reliable, and the stories you can tell from real projects.
When I started out, the “portfolio” was just me and a couple of colleagues figuring out how to connect SCADA to SAP and get some OEE numbers on a dashboard. Over time, that grew into a full set of offerings: plant connectivity, MES rollouts, analytics, mobile apps, AR/VR pilots, and more. But the core was always the same — connect machines, data, and people, and make it simpler for the plant to run better.
The Building Blocks: What Actually Goes Into a Good Portfolio
Repeatable Solutions and Accelerators
The biggest leap in practice maturity came when we stopped treating every project as a blank slate. Instead, we created reusable templates and accelerators for things like OEE, machine integration, downtime tracking, and MES-to-ERP connectors. For example, we built a standard MES template that could be rolled out to multiple sites, cutting delivery time by 30–40% and making support much easier. This wasn’t just about code — it included documentation, test scripts, training decks, and even project plans. If you want to scale, you need this foundation.
Service Offerings That Solve Real Problems
Every portfolio I’ve built had to answer a few basic questions: What problems do manufacturers actually have? Can we solve them quickly and reliably? For us, the core offerings became things like:
- Plant Connectivity (edge-to-cloud, historian integration, real-time data streaming)
- MES Implementation and Rollouts
- Analytics and Visualization (dashboards, KPI tracking, advanced analytics)
- Digital Worker Enablement (mobile, AR/VR, wearables)
- Compliance and Data Integrity (GxP, audit trails, secure architectures)
- We packaged these as end-to-end services, not just technical projects. That meant including business case development, change management, and post-go-live support.
Templates, Methodologies, and Governance
Repeatability comes from more than just code. We standardized delivery through templates (for requirements, architecture, testing), clear methodologies (Agile, Waterfall, or a hybrid), and strong governance. This helped us keep quality high, even as we grew and onboarded new team members. For example, we had a standard “plant connectivity” reference architecture and playbook that could be adapted for each site, but the core was always the same.
The Hard Parts: Challenges and Lessons Learned
Scaling Across Sites and Regions
Rolling out solutions globally is a different beast. Every plant thinks it’s unique (and to some extent, they’re right). Standardizing data models, integration patterns, and governance across dozens of sites was a massive challenge. The only way we made it work was by building strong local teams, investing in enablement, and being honest about what could be standardized and what needed to stay flexible. Sometimes, we had to fight for data access from equipment suppliers or work around legacy systems that were older than some team members.
Talent and Team Building
The consulting business is all about people. The best templates in the world don’t matter if you can’t recruit, train, and keep good engineers, architects, and project managers. I found that cross-functional teams (mixing IT, OT, quality, and business folks) worked best. We made a point to do hands-on training, shadowing, and knowledge transfer — not just “throwing it over the wall.” I also learned to look for people with curiosity and grit, not just the right certifications.
Competing with the Big Guys
We were often up against much larger system integrators. What helped us win was our focus on speed, flexibility, and deep domain knowledge. We could move faster, adapt to client needs, and show real results — not just slideware. Having a set of real project stories, references, and a track record of successful deployments (with numbers to back it up) made a huge difference.
Pricing and Structuring Offerings
We tried different models: fixed price for pilots, milestone-based billing for larger rollouts, and time-and-materials for ongoing support. The key was to be transparent about what was included, what was extra, and how risk would be managed. For big multi-site programs, we balanced onshore, nearshore, and offshore resources — starting heavy onshore for kickoff and design, then optimizing as the program matured.
What I’d Do Differently (If I Could Go Back)
If I had to do it all again, I’d double down on three things:
- Invest Even More in Accelerators and Templates: The more you can standardize, the easier it is to scale and the more value you deliver to clients. Don’t wait for the “perfect” template — get something out there, use it, and improve it with every project.
- Build a Stronger Community of Practice: Sharing lessons, code, and stories across teams and regions is the only way to keep learning and stay ahead. I wish I’d formalized this sooner — things like regular knowledge shares, playbooks, and open feedback loops.
- Be Ruthless About Value: It’s easy to get caught up in technology for its own sake. The only thing that matters is whether you’re solving a real problem for the plant. If you can’t explain the value in plain English, it’s probably not worth doing.
One Honest Opinion
Here’s something that might not be popular: Most consulting portfolios are too complicated. Clients don’t care about your “offerings matrix” or how many frameworks you have. They care about results — faster rollouts, fewer headaches, and measurable improvements in quality, downtime, or compliance. The simpler and more focused your portfolio, the better.
Final Thoughts
Building a Smart Manufacturing portfolio is about more than just technology. It’s about people, process, and a relentless focus on real-world value. The best portfolios are built on hard-won lessons, real project scars, and a willingness to keep learning. If you’re starting out, keep it simple, stay close to the plant floor, and never stop improving your toolkit. And don’t forget to celebrate the wins — even the small ones.
Leave a Comment