Key facts
| Organisation | Inciper (now Kerv) |
|---|---|
| Role | Data and Analytics Consultant |
| End client | Marston Holdings (Marston Recovery), court order enforcement and debt recovery for more than 280 local authorities and central government departments, around 250,000 liability orders a year. |
| Dates | January 2018 to July 2018 (7 months) |
| Type | Contract; 2 renewals |
| Significance | First engagement with a Dynamics 365 source system, the start of the D365 data specialism, and the first of three Inciper engagements. |
| Status | To confirm — old CV dates Dec 2017 to Aug 2018; LinkedIn Jan to Jul 2018. |
| Knowledge base | Personal\CV\kb\employment\2018-01-inciper.yaml |
Summary
An Azure enterprise data warehouse and reporting platform with a Dynamics 365 source system, built for Marston Holdings, the court order enforcement and debt recovery business. Included a case study presented to the Microsoft Data Platform team.
Achievements
- Consultant on a project building an Azure enterprise data warehouse and reporting platform with a Dynamics 365 source system.
- Presented a case study to 10 members of the Microsoft Data Platform team.
- Renewed twice during a seven month engagement.
- Designed and implemented an enterprise data warehouse following Kimball methodology.
- Implemented an extract, load and transform process using Azure Data Factory, Azure Blob Storage, Azure Automation, Polybase, SQL Database and SQL Data Warehouse.
- Developed Azure Analysis Services models.
- Developed DAX calculated columns and measures.
- Developed Power BI reports using live connection to Azure Analysis Services.
- Followed agile methodology with month long sprints incorporating daily scrums, sprint planning, refinement, reviews and retrospectives.
Technologies
Azure Data Factory, Azure SQL Data Warehouse, Azure Analysis Services, Azure Automation, Polybase, Power BI, Dynamics 365.
Open questions
- Date discrepancy with the old CV (Dec 2017 to Aug 2018) stays flagged on the master table.
Sources
The old CV (CV-MD-02.docx) and the LinkedIn experience capture of 5 October 2026. Relevance ratings agreed with Matthew, 8 October 2026.