Interface between a CMMS and its external providers
Around a CMMS (Hexagone) revolve many external providers who want to use and process its data. My role: act as the intermediary, giving each of them read and write services suited to their needs. Other processes are scheduled shell scripts (cron) that run at precise frequencies, produce CSV files and drop them into a directory on the target server. This interface layer decouples the core system from its users: each provider gets what it needs, in the form that suits it (API or file). I maintain and evolve these 4 production applications (third-party application maintenance), with full autonomy over analysis, code and quality, and I take part in the team's daily meetings.
