Magnet.me - Het slimme netwerk waarop hbo‑ en wo‑studenten hun baan of stage vinden.
Het slimme netwerk waarop hbo‑ en wo‑studenten hun baan of stage vinden.
Je carrière begint op Magnet.me
Maak een profiel aan en ontvang slimme aanbevelingen op basis van je gelikete vacatures.
Background BowTie Suite Team
The BowTie Suite team at Wolters Kluwer- Enablon develops risk management software with Bowtie diagrams being the at the core of the product range. Because these diagrams are relatively easy to understand, the bow-tie diagrams are used to communicate the risk to higher management as well as the people on the work floor, thus making the risk management process understandable for all stakeholders.
BowTie finds its roots in the chemical industry course notes for a lecture on hazard analysis given at the University of Queensland in 1979. The exact origin is unclear but the mainstream use started in the aftermath of the Piper Alpha disaster with Royal Dutch/Shell adopting the methodology as the company standard for analyzing and managing risk. It is widely regarded as a suitable visual tool to keep an overview of risk management practices.
The BowTie Suite products we develop currentlty are
What are your responsibilities?
Mobile application development:
*Basic knowledge of mobile application development, C# is required
Managing application artifacts:
The final artifacts (.exe, dlls, .zip) of our applications are currently published manually, we would like to automate the process of publishing the artifacts to our internal Jfrog Artifactory repositories
BowTieXP desktop: Remove dependency on Internet Explorer component (spike)
To integrate with BowTieXP Enterprise Server application the BowTieXP Client desktop application currently makes use internally of the C# Internet Explorer component, that we have customized.
Nobody uses internet explorer anymore! for many reasons. So this old component would need to be replaced with another browser component (like the modern WebView).
However it might also be a good opportunity to take a look at another login mechanism entirely, using an OpenId connect flow for instance. What would be the best option? Would it be compatible with the solution we have now? Could this be implemented quickly?
*Requires knowledge about http web requests, http redirection, cookie handling, logon mechanisms
What do we offer you at Wolters Kluwer’s Enablon?
Wolters Kluwer is a global leader in information services and solutions for professionals in the health, tax and accounting, risk and compliance, finance and legal sectors. We help our customers make critical decisions every day by providing expert solutions that combine deep domain knowledge with specialized technology and services.
Change language to: English
Deze pagina is geoptimaliseerd voor mensen uit Nederland. Bekijk de versie geoptimaliseerd voor mensen uit het Verenigd Koninkrijk.