ABB · posted · checked
Master Thesis Work – Industrializing e-SBOM Traceability across DevOps, Windchill and Product Lifecycle Systems
AzurePythonOn-site · Malmo
Who can apply
On-site · Malmo
Location: Malmo, Skane County, Sweden
At ABB, we help industries outrun - leaner and cleaner. Here, progress is an expectation - for you, your team, and the world. As a global market leader, we’ll give you what you need to make it happen. It won’t always be easy, growing takes grit. But at ABB, you’ll never run alone. Run what runs the world.
This Position reports to:
R&D Global Unit Lead
Your role and responsibilities
Execution of this Thesis work will be done within ABB Automation PCP, a unit within ABB’s business area Process Automation. Automation PCP develops automation products - hardware and software - for monitoring, process control and optimization. We have automation products for all kind of industries.
Within Automation PCP, we would like to continue the previous master's thesis on extended Software Bills of Materials (e-SBOMs) by moving from a successful proof of concept toward an industrially usable, governed, and maintainable solution. The work should investigate how artifact-centric e-SBOM information can be generated, exchanged, aggregated, baselined, and traced across the software lifecycle and across ABB engineering systems.
Details:
Period: TBD
Number of credits: 30 ECTS
Number of students for this thesis work: 1 or 2
Location: Mostly on site - Malmo, Sweden
The thesis will investigate an architecture in which development environments and CI/CD pipelines generate controlled e-SBOM metadata for exact artifact versions, while product-lifecycle, release, and vulnerability-management systems consume appropriate views of that information. The study should use ABB System 800xA as the main case, but the proposed principles and interfaces should be generic enough for reuse by other ABB products and customer systems.
The work should explicitly address integration and governance boundaries among systems such as Azure DevOps, Windchill, Dependency-Track, source repositories, artifact repositories, and approved release-documentation or archive locations. A key topic is how to avoid uncontrolled duplication while preserving authoritative ownership, immutable release evidence, product-level traceability, and continuously updated vulnerability information.
A proof-of-concept implementation is expected. It should use e.g. scripts and REST APIs to demonstrate a representative flow from a controlled build artifact to an e-SBOM, aggregation or transformation, validation, and publication or registration in a downstream system. The proof of concept should include automated checks and readable output for both tools and human reviewers.