Description -

WAHH is an ultimate software solution for general public to (Capture, Predict & Report) the Accumulated Waste or Dead Animal usually encountered on a frequent basis.

The mobile app allows the user to capture the photo of waste, the AI logic behind runs prediction on the photo and displays various (objects, object specific diseases & disease details like summary, symptoms, causes, prevention & treatment) available in the garbage. There's a 'Report' button on screen, clicking which will immediately send the detailed report to nearest municipality.

However, the Web platform is a beautiful dashboard provided for the registered action takers (Govt./Municipalities) to see various reports submitted with Geo Location, an integrated Map helps the Municipality to easily locate the reported area. The detailed report communicates about the impact of the waste. This will help the Govt. to understand the seriousness of health hazards due to waste and to take immediate action.

In future, the plan is to introduce Drone (IoT) for capturing and reporting along with app. Improvise the Web platform for assignment and status management. And a better analyzing & reporting system for Govt. / Municipality (Action Taker) based on Geo Indexing functionality etc.

Responsibilities –

• Requirement Gathering, Project Planning, Architecture Design & Documentation.
• Involved in complete front-end & back-end development using Python & Cloudant Db.
• Involved completely in understanding & using IBM Watson Visual Recognition, Cloud Object Storage & Cloudant Services.
• Involved completely in integrating Paytm payment gateway etc.
• Involved in writing various API’s as required.

Skills / Language -

• Python, IBM Watson Services.
• Cloudant DB, Cloud Object Storage, API Development.
• Bootstrap, HTML5, CSS3, jQuery, JavaScript, Google Map API, Location services etc.

SchoolTonic is designed to facilitate paperless administration of schools. The software has the ability to host modules which allows a user to maintain the academic history of students, staffs, inventories, various records, etc. which ultimately helps the staff, teachers and school authorities to work in accord. The tool brings many different functions/departments in one system and provides all the relevant data in one place.

StudentTonic, a unique e-learning platform created for multiple devices to digitalize the education system. The purpose of StudentTonic is to digitalize the school’s curriculum without doing enough transformation on the classical approach like (Daily Attendance, Regular Classes, Precise Topics, Activity Based Exams, Progress Tracking & Suggestions for Improvements etc.)

A Vendor Management Software, tailor-made to fit the requirements, process & environment of any vendor. There were multiple roles & levels of access in Work Nexus like Program Administrator, Requestor, Delegate, Request Approver, Customer Internal, Supplier, Contractor etc.

Workflow: A brief on the workflow is as follows, the Administrator was responsible for creating different Suppliers, Requesting Managers, News bulletins etc. in the system. The were various modules involved in like Candidate Recruiting Request, Payroll Request, Timesheet/Expense Report Process, Performance Reporting etc. with their own workflow and functionalities.

My role in this project was to make required changes in the existing template as per new vendors requirement or to add any new modules/functionalities if asked for.

On the other hand, Reimagine is a XPages migration of the same application in which, I was actively involved as one of the members in development team.

A Vendor Management Software, tailor-made to fit the requirements, process & environment of any vendor. There were multiple roles & levels of access in Work Nexus like Program Administrator, Requestor, Delegate, Request Approver, Customer Internal, Supplier, Contractor etc. Workflow: A brief on the workflow is as follows, the Administrator was responsible for creating different Suppliers, Requesting Managers, News bulletins etc. in the system. The were various modules involved in like Candidate Recruiting Request, Payroll Request, Timesheet/Expense Report Process, Performance Reporting etc. with their own workflow and functionalities. My role in this project was to make required changes in the existing template as per new vendors requirement or to add any new modules/functionalities if asked for. On the other hand, Reimagine is a XPages migration of the same application in which, I was actively involved as one of the members in development team.

The SOI Database is an XPages application which is designed with a purpose of properly monitoring & tracking safety related issues & to reinforce the benefits of Safety observation standards & procedures. The flow of this application works as, user creates a Safety Observation Report by filling all the required fields where the observation hours gets calculated from the difference of date fields & people involved. Before submitting it to the next level users creates the Observation points which were child documents of the main reports and finally submits the main report form to the Zone Owners which were configured. On submission based on the different values of child documents an Unsafe Action & Unsafe Condition matrix gets generated which gets linked with a pop-up dialog box. A notification goes to the Zone Owner with document link who accesses the document and assigns all the Observation points (child documents) to the respective assignees the Zone Owner himself selects the next level Verifier of the document while assigning. On assigning all the points the parent document status gets updated to Assigned. All the individual child link goes to the respective Assignees who can access & completes their activities. On completion the child link goes to the respective Verifier who can verify or reject the documents. On completing all the points, the parent document status gets updated to Completed. Before completion the Zone Owner gets an option to change the Target Date, Assignees or Verifier if required. After completion the Verifier receives the child link and verifies the document. He can also reject the document which goes back to the previous stage and assignee completes it back. On verification of all the points the parent document status gets updated to Closed and thats the closure of the complete process. Apart from the flow different additional features are provided with the database like: Calendar View control for SOI meeting scheduling. Different Chart generation. Search & Export functionality. User based Workbench. Configurable mail templates. Different reminder agents with MIME design etc.

The Incident Investigation Database is developed to outline the process for reporting, recording and investigating an incident, recommending corrective and preventive actions and to communicate the lessons learned to prevent recurrence of similar incidents. The intent is to ensure that there is no ambiguity while reporting, classifying incidents, and injuries, illnesses, providing immediate response, medical assistance and investigation. It covers roles and responsibilities of all personnel associated with Incident Investigation as well as the methodology required to investigate effectively. This database consists of two modules First Information Report (FIR) & Detailed Investigation Report (IR). The flow starts with composing FIR with the basic mandatory fields like Title, Unit, SBU, Date & Time of Incident, Zone, Exact Location of Incident, Description of Incident, Injury Details etc. While composing users fills a PFE Sheet which contains preset configured queries and divided into three different categories i.e. Process, Fire & Environment. Each question is assigned some marks and the total marks decides the category of the incident as (A, B, C). Once FIR is submitted it goes to the Investigation Team who investigates it and confirms back to the composer. On confirmation the composer creates a detailed IR Report. Based on the category of the Incident the IR detail appears to be filled. While composing IR a link for creating the CAPA points appears to the composer. Composer can create as many CAPA points which is linked with a separate form and submits the IR Form. On submitting the IR the CAPA link goes to the respective Assignees, Assignees completes their task and submits it to the Verifier for verification. Verifiers can either verify or reject the task. On rejection the CAPA goes back to the Assignee to recomplete and on Verification it gets closed. Once all points are verified the IR status finally gets converted to Closed. Apart from the flow different additional features are provided with the database like: Different Chart generation. Search & Export functionality. User based Workbench. Configurable mail templates. Different reminder agents with MIME design etc.

The Documentation Cell system acts as a central repository which stores the specification requests and provides access to Controlled and Uncontrolled documents. The flow of this application works as, different types of specification documents are created by Doc Cell members (users with DocCell role) where they can store either Controlled or Uncontrolled documents as an attachment. In order to view the attachment, the users have to undergo through an approval process. User creates Access Request forms for a particular specification and submits it to the next level of approver i.e. L1 Approver who can either approve or reject the request. Approving the request sent a notification to the 2nd level of approver i.e. QA Approver and finally it goes to 3rd level of approver i.e. DC Approver which is the final level of approval for the Request. Once the request is approved by the DC Approver the user can see the attachment tab and print button and clicking the print button will directly prints the attached document. At each and every level of approval or rejection notification is sent to the respective people. And on rejection user can resubmit the same request once again.

In this database a Business Card Request has been created by the requestors which has been filled and submitted to the Business Card Reviewer, during request creation he/she can previews the Business Card View, once completed he/she can submit the request which gives a final preview of the card and clicking the OK button will send a notification to the Reviewer. A mail goes to the Business Card Reviewer with the doc-link of the request. The Reviewer reviews and modifies the request if required, and sends completion mail to the Requestor. The Requestor receives the completion mail with the final preview of the Business Card. This application is developed for both Client and Web uses.

Conflict Check System (CCS) is a Web based application internally used by the client for managing the external & internal conflicts. My role was to handle the Maintenance & Change Releases on time to time basis and to provide production support as required. I was involved in starting from preparing the Design & Estimate document, Development Activity, QA Release document, Test Scripts, Deployment document and handling the complete deployment activity on QA Release.

SHE Infosite is completely a Web based application which is a combination of 5 to 6 databases which is broadly used by the customer. All the databases are linked at once page called, SHE Infosite which presents different modules to the user for raising and monitoring different kind of requests. As maintenance task involved in many issue handling & enhancement activities for these applications.

An internal application designed for OpenNTF competition. This application is designed to provide a single screen support for managing ACL of multiple databases. The charm of this application is its completely designed in Web using XPage. Now, you can have a single XPage to manage your ACL settings for multiple databases on a server. Project Scope: The scope of this application are as follows: It is designed to run on current server so, you need to create a copy of the application on the server you want to use it. It covers almost every features of ACL except the Copy button under Log tab and Administration Server section under Advanced tab. The application is tested on IBM R9 platform and is expected to work well on previous versions R8 or R8.5. Any reported bug on previous platforms will not be a part of this release. The application is thoroughly tested on Firefox 40.0.3 and is expected to work well on other browsers like IE 11.0 & Chrome 45.0. Any reported bug on previous platforms will not be a part of this release.