Case study · Orion Industrial

Fractional Salesforce Architect for an Orion Industrial Service Cloud Rescue

Engagement summary

ForceFolks supplied a fractional Salesforce solution architect to Orion Industrial for a stalled Service Cloud and Field Service programme. The architect worked three days per week from 15 January to 28 June 2024. Orion’s engineers implemented the work and its CIO retained release authority. Orion’s Copado logs show failed production deployments dropping from 40% to 5% across the reported periods.

Client and Engagement Facts

Orion Industrial: Client and Engagement Facts
FieldEngagement detail
ClientOrion Industrial
Industry and client locationIndustrial equipment and aftermarket service in Düsseldorf, Germany
Salesforce scope and toolsService Cloud, Field Service and Experience Cloud. Azure DevOps, Copado and Jira.
Staffing and datesOne solution architect for three days per week, 60% allocation, from 15 January to 28 June 2024
Delivery arrangementNearshore delivery with six shared hours each working day with the Düsseldorf team
Client ownershipOrion’s engineering manager owned the remediation backlog. Orion’s engineers implemented the changes, and the CIO retained release authority.

Why the Client Added Capacity

Orion’s Service Cloud programme had missed two go-live dates. The internal team still needed decisions on sharing, data modelling and Experience Cloud boundaries. Orion brought in a fractional architect to resolve those decisions so its engineering team could resume work through its existing Copado release process.

Client corroboration

“The ForceFolks architect wrote the records, our engineers built to them, and our deployment failure rate collapsed. The checklist he left behind is still how we release.”

Dr. Lukas Brandt, CIO, Orion Industrial

Role Contributions and Acceptance

Orion Industrial: Role Contributions and Acceptance
ForceFolks roleWork and outputsClient review or acceptance
Salesforce solution architectProduced seven architecture decision records covering sharing, the Service Cloud to Field Service data handoff and Experience Cloud roles. Created a dependency register, prioritised the remediation backlog in Jira and documented the release-readiness checks Orion adopted.Orion’s engineering manager and platform lead reviewed the work. Orion’s engineers built to the accepted decisions, and its CIO approved each release gate.

Outcomes and Evidence

Orion Industrial: Outcomes and Evidence
MeasureBaselineResultWindowSource
Failed production deployments40%5%October–December 2023 vs April–June 2024Orion Copado production deployment logs
Architecture decision records accepted07January–June 2024Orion decision record repository
Open dependency blockers23415 January vs 28 June 2024Orion Jira dependency board
Production releases0 in the preceding 9 months4February–June 2024Orion release calendar
First stable release—Accepted 16 February 2024February 2024Orion release acceptance record

Discuss the work your team needs

Share the Salesforce work, roles and client review responsibilities. ForceFolks will assess the staffing requirement against that scope.

Discuss your staffing requirement