Case study / 01
FAID Quantum
Analytical implementation, product architecture and integration
Two fatigue-analysis algorithms delivered through a native library, a browser application and a managed web API. Developed at InterDynamics, the products support direct schedule analysis and integration into third-party rostering and workforce systems.
FAID and FAID Quantum analytical capability is available through three integration surfaces: the Angular and .NET FAID Quantum web application, a managed developer API using Azure API Management and .NET Azure Functions, and the native FAID Quantum Shared Object Library embedded in third-party software. The developer API uses separate controls for API subscription access and product entitlement, with entitlement validated by the InterDynamics Licensing Platform.
01 / Analytical implementation
From analytical models to production calculations
My work began with the existing FAID implementation in the desktop product. I translated the calculations into C++ and packaged them as a DLL, making the algorithm available to external applications while improving calculation performance within our own software.
The second algorithm, FAID Quantum, required implementation directly from academic research papers covered by InterDynamics’ exclusive commercial licences. Results were checked against a calculation spreadsheet supplied by the researchers.
The established DLL subsequently provided raw reference outputs for checking later implementations. Comparisons with the desktop product also covered the graphical presentation of results, including outputs requiring interpolation and interpretation.
02 / Integration architecture
Two algorithms, three delivery models
The native library allows customers to calculate fatigue predictions from roster data within their own software. Customers control how the results are analysed and presented, fitting fatigue analysis into their existing product workflows.
My responsibility included the integration interfaces, examples in multiple programming languages, API documentation, licensing and expiry controls, and error reporting for invalid inputs.
The managed web API followed requests from customers who preferred remote calculation to installing a native component. Azure API Management and .NET Azure Functions provide the integration surface, with subscription access and product entitlement handled as separate controls.
Both algorithms are available through the native library, web application and web API.
03 / Product workflow
From exchanged files to retained assessments
The desktop product used a file-based workflow: users loaded roster data, ran an analysis and exchanged input files when sharing work. For the web application, I introduced named assessments that retain inputs and calculated outputs together, with access governed by group permissions.
Corporate customers needed to collect individual submissions for manager-led analysis. In this workflow, ordinary users manage their own records; authorised managers can review and consolidate submissions into a separate group assessment. Shared assessments remain available for collaborative work.
The distinction keeps individual users focused on their own data and prevents them from changing another person’s submissions, while giving managers the visibility needed for group analysis.

04 / Application and cloud architecture
Delivery across the application and platform
I owned the web product’s design and implementation across the Angular frontend, C# backend, database structure, cloud architecture, deployment and CI pipelines. Auth0 establishes user identity, while backend services enforce organisation context and access to assessment data. Calculations remain behind the application layer.
The browser application extended access beyond the Windows desktop product and introduced persistent, permission-controlled workflows across users and groups. Colleagues contributed testing, QA and product feedback.
Alongside engineering delivery, I led early internal presentations and customer demonstrations. Ongoing work includes technical support and helping customers integrate the products into their software and operational workflows.
05 / Outcomes
Established products and corporate adoption
The DLL became one of InterDynamics’ strongest-selling products over many years.
The web application gained corporate customers, including organisations seeking individual data collection with manager-led consolidation and analysis. The web API attracted several corporate users within its first year of operation.