Analysis
Neither proposal is straightforwardly good or bad. Both have genuine strengths. Both have serious concerns. A PDM-trained practitioner should be able to articulate those concerns clearly - and use them to structure the negotiation before a contract is signed.
Logia
Strength: Target system knowledge. As a VAR for the selected ERP, Logia genuinely knows the target data model. This matters for the mapping work - someone who has implemented the target system dozens of times will identify structural constraints and mandatory fields that a generalist supplier might miss. This is a real differentiator.
Red flag: Collapsing GAM and MDE into a single phase. PDM separates Gap Analysis and Mapping from Migration Design and Execution for a reason. GAM is primarily a business activity - it establishes what the data means, who owns it, and what transformation rules apply. MDE is primarily a technical activity - it builds and executes the routines that apply those rules. Running them in parallel creates a situation where ETL is being designed before the business rules are agreed. The inevitable result is rework, or worse, ETL that is built to assumptions that later prove wrong.
Logia’s proposal to combine them is commercially rational - it is faster and cheaper to deliver. But the risk of that speed falls on the client, not on Logia. Probe this hard in any follow-up discussion.
Red flag: Under-resourced Landscape Analysis. 2 FTE for LA across a 10-system landscape is thin. LA is where you discover the scope, identify data quality issues, and establish the baseline for everything that follows. Under-investing in LA means those discoveries happen later - during mapping, or during execution, where they are far more expensive to resolve.
Red flag: LD excluded. Logia has excluded Legacy Decommissioning from scope entirely. This is not unusual for a VAR - they have no commercial interest in retiring the old system. But it is a risk that DHGS must consciously accept and plan for. Who will do it? When? At what cost? These questions need answers before contract signature.
HAL
Strength: Appropriate LA resourcing. 5 FTE for Landscape Analysis across 10+ systems is credible. For a migration of this breadth - spanning physical assets, vehicles, finance, HR, customers, and departmental systems - thorough LA is the single most important investment in the programme. HAL has understood this.
Strength: Early data profiling. HAL’s plan to begin data profiling during High Level Design, enabled by early delivery of the HLD, is methodologically sound. Surfacing quality issues early - when there is still time to address them - is central to PDM. The alternative is discovering them during execution, at which point the programme is under pressure and the options are limited.
Strength: Correct phase separation. HAL maintains the separation between GAM (High Level Design) and MDE (Detailed Design). This is the right approach and reflects an understanding of why the phases are distinct.
Red flag: Cannot document their own methodology. This is serious. HAL claims to have a proprietary methodology and specialised tooling, but was unable to provide formal documentation of either during the tender. If a supplier cannot describe their methodology, you cannot hold them to it. You cannot assess whether it is appropriate for your context. You cannot write acceptance criteria against it. This is not a minor concern - it is a governance exposure. Before any contract is signed, HAL must produce written documentation of their methodology, with enough detail to form the basis of milestone and acceptance criteria.
Red flag: Proprietary tooling during LA. HAL plans to use their own toolset for source data profiling during Landscape Analysis. The concern here is data continuity: the output of LA - the LDS, the data profiles, the quality baselines - needs to be owned by DHGS, not by HAL’s tool. If the engagement ends or changes, DHGS must retain access to everything that was produced. Contractual clarity on data ownership and tool output portability is essential.
Red flag: LD excluded. Same as Logia. Both proposals exclude Legacy Decommissioning. This is a gap that DHGS must address in the programme plan before either contract is signed.
The Missing Piece: Legacy Decommissioning
Both suppliers have excluded LD. This deserves its own section because it is not a minor contractual technicality - it is a programme risk.
Legacy Decommissioning is the final phase of PDM. It involves retiring the source systems in a controlled way, archiving data that must be retained for regulatory or business reasons, and confirming that the target system has received and validated everything it needs. Done badly, or not done at all, it leaves the organisation with live legacy systems running alongside the new ERP, with all the confusion, cost, and data integrity risk that entails.
The question DHGS needs to answer before selecting either supplier is: who is responsible for Legacy Decommissioning, and is that person or team available and funded? If the answer is “we’ll figure it out later,” that is a risk that should be formally logged and owned.
Recommendation
There is no objectively correct answer here - the right choice depends on information not available in the proposals alone (pricing, references, contract terms). But based on the proposals as presented, HAL is the stronger starting point, for two reasons:
- Their LA resourcing is more credible for the scope of this programme.
- Their phase structure is methodologically correct.
However, HAL should not be selected without resolving the methodology documentation issue. That is a non-negotiable pre-condition. If HAL cannot produce written methodology documentation, the engagement will be difficult to govern.
If Logia is selected, the GAM/MDE phase structure must be renegotiated before contract signature. Accepting the combined phase as proposed transfers significant execution risk to DHGS.
In either case, Legacy Decommissioning must be explicitly scoped, resourced, and funded - by someone.
Key Takeaways
- A VAR’s target system knowledge is a genuine asset but does not substitute for methodological rigour in the source analysis and mapping phases
- Collapsing GAM and MDE into a single phase is a commercial decision by the supplier that transfers risk to the client - always probe the rationale
- LA resourcing should be proportional to the number and complexity of source systems; under-investment in LA is one of the most common causes of late-stage programme problems
- Suppliers who cannot document their own methodology cannot be governed against milestones - documentation is a pre-condition of engagement, not a post-contract nice-to-have
- Legacy Decommissioning being excluded from both proposals is a programme gap that must be resolved before any contract is signed