Building a global HRM solution on the Microsoft Azure platform. It is a multi-tenant PAAS application As a lead architect responsible for workflow, business rules, extensible domain entities and integration services. Working with development teams in Madrid and India to implement this. We design and build our software using reactive architecture. Azure provides good support for building microservices. Some details on the technologies used in the areas I am responsible for:The key technologies we use are Azure webapp, webjobs, Azure service bus queues and topics for building the reactive architecture. The hard of the workflow engine is based on Microsoft Workflow Foundation. The business rule engine is based on ANTLR parser technology.

Next to being the architect of OpenText Cloud Service Brokerage, now also being part of the Entity Modeling team working on the next generation of the BPM development tools.

Design and implementation of OpenText Cloud Service Brokerage. This is the next generation of CCP and adds the capability to describe product structures using a declarative specification language that defines many different relationship types and state controlled actions. Through a product catalog and a product offering system, users can create, modify and delete product structures and invoking the appropriate actions.We are in the process of applying for a patent on "System and method for product fulfillment in a cloud-based multi-tenancy system"

Working on design and implementation of Cordys Cloud Provisioning (CCP), a product for onboarding of Cordys applications, of tenant and users and subscribing tenants to applications and assigning users to the applications in a given role. The product is used for the by Cordys operated cloud and for service providers that wanted to operate their own cloud. CCP allowed for deploying applications, tenant and users to multiple computer clusters on different locations in the world from a central hub.Had the role of Scrum Master for some years

IB-Groep Pilot 1a (role: designer, developer, coach)In this project for IB-Group we are replacing the IBM MQSI message broker with Cordys technology. This was partly already done during the PoC but now, the full functionality will be built and the IB-Groep developers themselves will be trained on the job to complete the work. I also support Pilot 3 to help the business people how to construct flows.ING Proof of Concept (role: scrum master / designer / team lead)n this project for ING/NN the abilities of the new Cordys C2 version are demonstrated using a Mortgage Quotation process as a business case. The business functionality serves as a framework for demonstrating the capabilities of the platform. This project is closed successfully after the demonstration of the functionality and underlying technical solution and Cordys technology.Etam Infrastructure (role: Architect)Part of a task force to scope and estimate a project for connecting all Etam backend systems to the Cordys ESB and replacing the current point to point solutions.Etam Plateau 1 (role: Architect)Designed the blueprint for the next cycle of projects to deliver a merchandize flow dashboard and processing the Point of Sales information. Reviewed all designs made by Etam.Also created a scope definition and estimate for the Merchandise Flow Dashboard.Informatie Beheer Groep (role: Scrum Master / developer)Proof of Concept for the IB-Groep to show that Cordys Technology could connect to IBM iSeries and zSeries using the MQ connectivity infrastructure using own connectors or the connectors of Seagull.Proof of Concept for the Amersfoortse (role: developer)Worked on a mortgage application with backend integration to mainframe teaming up with Software-AGEtam Plateau 0 (role: Architect)Designing the architectural blueprints for the Etam Retail Services company. Governance on the designs and implementation.

Developing a RosettaNet-based extension on top of SSA Baan Iv and SSA Baan ERP. RosettaNet is a standard describingThis extension consist of two parts:- A toolkit for exposing the internal business processes of Baan IV / Baan ERP. With this toolkit, third party process integration tools can interface with the internal Baan business processes and internal business processes could trigger and control external integration processes.- A ready to use RosettaNet solution based on the toolkit and IBM Websphere Business Integration (consisting of: process engine, mapping tools, internet gateway).The total team size for this project was 6 persons.

In de new organization, starting January 2003, all product owners (being the consultants and architects) of the business unit ‘Enterprise Enabling Technology’ were merged in one team. The goal of this merge was to increase the cooperation between product owners and to achieve a better integration of the products. The team was divided across four locations: (Barneveld) Netherlands, Hyderabad (India), Mumbai (India), Iceland. Total team size: 12 persons. The product domains of this team consisted of integration technology, business intelligent, B2B and workflow and business process technology.

After the restructuring of Baan (June – July ) the management decided to change direction and abandon the Microsoft technology in favor of J2EE. To provide a basis for the next generation of internet products, basic services were needed (Common Services).

After the management decided that the Baan Suite should be open to the Internet, a dedicated team of 4 persons was formed to start this initiative.Over time, the team grows in the Netherlands to 30 persons and in India to 80 persons. Initially the technology was based on the Microsoft Java environment but this technology proved to be immature and was abandon for the more stable and commercial more attractive Microsoft SiteServer / ASP architecture

In January 1995, Baan started a research group for building the next generation platform for the ERP suite. This group consisted of a number of teams, each team dealing with one of the basic technologies needed (repositories, development tools, languages, databases, common services, user interfaces)

The Baan Technology Team was responsible for maintaining the technology on which the Baan applications ware build. This technology was referred to as ‘the Bshell’, although many other tools were also developed and supported. Qua concept, the Bshell is comparable with the Java virtual machine.

At the start of this project two applications existed for making estimations for construction activities. One application for road construction (based on the RAW standard) and one for the buildings (based on the Stabu standard).