Projects
1. Lending-Risk
Working in a micro-services environment with around a dozen projects.
Innovating Digital Lending Solutions.
Driving Performance and Scalability.
Leadership and Mentorship.
2. Digital Distribution Platform
Building a Python Scripting Project from scratch. The e-Delivery application is divided into 3 broad categories:
Back Office: managing software content i.e., payloads and pushing to a Content Manager.
Content Manager: handling the content management, i.e., S/W ISOs, meta-data containing additional information about payload type and dependencies.
Site or Hospital: network maintaining connectivity with the Content Manager via an internal interfacing app.
Major tasks performed:
Built an Installer Framework: Single handedly designed and developed a fully functioning Installer Framework which supports multiple Installers for Healthcare Devices by using Design Patterns.
Playing the role of an Architect: Designing an Uninstaller/Roll-back Framework which takes care of all types of Packages (Hot-fix, Patch, Upgradable, Load From Cold (LFC), and more).
3. ULTRIA CLM (Contract Lifecycle Management)
ULTRIA CLM is a software suite comprising of 3 different projects namely:
Tenant Management System (TMS) - This is a project which handles the data of different Clients, their products, users, scopes, roles, and activities.
It also handles the authentication and authorisation of the users who try to login into any of their products.
Contract Lifecycle Management (CLM) - This is the main project in the entire suite.
As the name suggests, this project handles the entire life cycle of a contract.
It contains various modules namely:
a. Request Portal - This is the module for non-legal people, helping them create a simple outline of a contract based on existing internal templates, or user-uploaded external templates.
b. Authoring Module - This is the module where a legal person, such as a contract author, can create a contract from scratch.
There are different stages a contract can go through, such as Authoring, Negotiate, and Signing.
Once all the above stages are complete, the contract is then ready to be moved to the next module, i.e. Repository Module.
c. Repository Module - This is the module where the application stores the completed contracts.
The user has an option to directly upload a contract document in Repository for storage, or else the author of a contract in the Authoring Module can add a completed contract to Repository Module.
Workflow - This is a project which handles the review process of any contract.
There are various rules and patterns a client can create or modify for the review of any/every type of contract.
The above three projects work in tandem to provide businesses close control over myriad contracts and their execution.