Create build improvements with automation: CIT environment is about 90% automated; Other environments will be automated as they upgrade to Sterling 9.4.Collaborated with WebEng and UNIX team for fully automated build and deployment, with JVM cluster restart.Coordinate Sterling build and deployments in DTQ environments, approximately 10 to 16 per week.Served as Deployment/Implementation lead for Sterling OMS upgrade from version 8.5 to 9.4.Coordinate code merge activities among development teams every time a new Production release goes live.Work with Deployment Team to develop and execute plan for Sterling deployments into Production.Update Sterling Deployment Plan (per release) with any updates to support the Production solution.Support Sterling Go-Live activities.Plan/implement/troubleshoot Sterling 9.4 in all DTQ environments.Manage RTC code streams for Development and Build teams.Troubleshoot to fix DTQ environmental issues and report findings to Environments Team. Wins/Achievements in process improvement:Organized build request chaos by creating Build Dashboard in JAZZ RTC which served as central location for all software code builds. -Each environment owned a TAB in the dashboard and build team member would promote code tagged in daily requestUpdated Build script .xmls to be parameter driven rather than hard-coded values. This eliminated the technical debt the team had been carrying for yearsTook task descriptions in the Sterling Imlementation Plan and created script files for HCL WebEng to execute rather than providing description and having them execute. -Greatly increased the success of task completion as well as reduced the time to execute entire plan.Implemented a project that provided scripts to be executed in Jenkins for Sterling agent restarts. -This reduces the dependency of our team while testing is ongoing.Created Build Wiki which shares environment information. -Reduced dependency when developer had an en

Engaged in defining solution requirements with client from BRD discussions.Created high-level architectural specifications on Sterling OMS 9.2, ensuring feasibility, functionality, and integration with existing systems/platforms.Contributed in requirement review sessions with client business analystInstructed team to conduct proof of concept scenarios to extend OMS product to handle intended solutionProvided technical support to offshore team Updated build scripts and assisted deployment into testing environmentsPerformed testing and bug-fixing in post-developmentParticipated in Detailed Design sessions for several Business ReleasesUpdated and maintained development build scripts and environments on Sterling OMS 8.5Performed testing and bug-fixing in post-developmentArchitected a local printing solution to be used on centrally hosted applicationWorked as co-lead on all integration work involving over 100 interfacesParticipated in Detailed Design sessions for first and second Business ReleasesResponsible for installation of release updates as well as documenting these proceduresHosted sessions with client to review enhancementsWrote test scripts for client to use in User Acceptance TestingInvolved in the analysis of client’s business requirement and converting them to technical designs by defining the mapping (out-of-the-box/configurable) and extensionsDesigned the back-end API extensions and the interface to the external system for Label PrintingCoordinated the unit tests, string tests with the team

With the environment in mind, this service was created to stop the unwanted newspapers that pile up when on vacation, go unread, retain water and become a waste and most importantly created to save trees. The local journal puts out 1.2 million papers a week - thats a big environmental footprint.