SIN CHUEN OOI

• Built inbound SAP proxy for MPDL (Source) through BOOMI, which is a Boeing specific middleware tool in addition to PI/PO; with Forward Error Handling (FEH) capabilities to reprocess failed transactions through SXMB_MONI or /SAPPO/PPO2
• Built a more user friendly custom transaction, Quotation Review and Approval Process compared to using standard SAP transaction: ME4N, ME47, ME48, ME45 using screen painter
• Built outbound SAP proxy for Boeing International Business System (BIBS) with process inventory data including operational difference between the customers to facilitate the international financial recording of CSP part transactions e.g. part sales, discards, scraps, lost parts, loans, serviceable and non-serviceable returns, part number corrections etc
• This BIBS process is designed with configuration dashboard, that can detect configurations, analyze the material documents' movement type and indicate if configuration is missing or wrongly assigned that caused it not to be detected as a BIBS transaction.

• FREW team to resolve the GSEP/ITSM Incidents, Service Requests and PCR (Change Request), ServiceNow
• Liaised with customers, and functional team to analyze issues or requirements and propose and deliver resolution while keeping to Boeing's stringent transport processes
• Supports ECC, CRM, MDG, SCM/APO for BCA, DE ERP/MDG (S4) with BDUK security clearance, RMAS, Flight System
• Primary developer working closely with the basis team to upgrade Flight System (FSP) Solman Upgrade SP17
• Highly involved in resolving Priority 1 issues e.g. VIM AP payment, Dassian, Payment transactions - F110, Vertex
• Bank Payment instructions for specific Country/Bank

Background:

Tenneco had a failed implementation by another vendor to migrate from legacy to SAP system. This project was to identify, salvage and help Tenneco refocus on the area that needed attention to bring the project to a successful go-live

Responsibilities:

• Took on functional role
• In charge of 15 Change Request across Warehouse Management and Production Planning
• Work closely with business to get the specific requirements, produce Financial Specifications, guide developers, prepare the test data and test all scenarios
• Update management on progress and potential issues and escalation
• Built functionality for their return process, rework by engineers to salvage parts, RFUI scanning of parts for material staging and production lines
• Decipher Tenneco's custom code programs, customize some functionality so that they can extend usage by different plant
• Knowledge transfer to developers
• Completing FS, FUT, and handover to Business for UAT sign-offs

Background:

Power NS EAM Locomotive introduces the next generation technology, enhancing locomotive maintenance processes and operations

• SP&E - Shop Planning & Execution application provides a comprehensive near real time view of locomotives before and during shop event, their status in progressing through the shop, compliance to 4C criteria, and closure of work. SP&E helps shop leaders quickly identify and remedy work exceptions so they can release reliable locomotives in a timely and efficient manner
• LMT - Locomotive Maintenance Toolbox or LMT is a new PowerNS mobile application, accessible from an NS issued iPad. LMT serves craft personnel maintaining and repairing locomotives with a mobile, user-friendly interface for accessing work information and resources while documenting progress and materials used during the shop event. This application is currently in development with the initial release planned for 2023 to our pilot locations in Birmingham and Chattanooga
• Data integration – with LMIS, Logic Springs, TEP.
• Move of scheduled maintenance system of record from LMIS to EAM (SAP) with LMIS integration

Responsibilities:

• Set up core OOPS factory classes that streamlines and simplify coding E.g. Characteristics, Notifications, Work Orders, Maintenance Plans, Planned Orders, Defect Label Barcode
• Set up BRF + for material, notifications, work orders etc
• Work on the critical interfaces and program that creates/maintain Notifications from Troubles (LMIS), packing of open notifications into Revisions, closure of Work Order and Notifications.
• Developed workflow that automatically sets status of the Functional Location to automatically set Arrived status 30 mins after Yarding status is set.
• Worked on the Odata for SP&E and LMT to parse data from and to UI Mobile team.
• Developed Document Retrieval for material from HP or Sharepoint repository URL
• Developed deep structured Odata
• Developed on the Defect Label Barcode using Adobe Form (SFP)
• Responsible for understanding functional specs, producing the technical specs, development, involved in testing cycles, signing off on the work completed, and status reporting for the team.
• Highly involved in N+1 to N environment for R1 and upgrade of support pack for iMRO
• Retrofit codes from N into N+1 environment manually
• Execute the SPDD and SPAU transactions during the upgrade that compares the before and after upgrade at code level
• Created custom tcode that can be linked to a specific SQVI report that was created/owned by authorized finance personnel.
• Worked on enhancements of virtual plant L999 to MDCA and MDCL for iMRO
• Developed program that would run periodically to changed the planned order based on Object dependencies, and days + 7 rules as SAP standard doesn't have any BAPI to update the planned order components when the plant or start date changes.
• Involved in the Hypercare of PowerNS
• Correspond with SAP on defects on products or issues pertaining standard SAP iMRO
• Perform performance tracings and performance tuning

Background:

Boeing OneSAP (Feb 2016 – Oct 2017)

• Commercial Aviation Services OneSAP Implementation Program Boeing Commercial Aviation Services OneSAP Program execution, deliverables and integration of all 10 business workstreams. Integrating over 2,000 business requirements and 300 business process into SAP configurations, enhancements and integrations across 8 SAP modules (ECC, SCM, CRM, PCE, GTS, SRM, MDG, BI/HANA)

Boeing eCommerce/Hybris (Mar 2017 – Oct 2017)

• Launch of Boeing Part Page eCommerce Channel

Boeing OneSAP Hypercare (Oct 2017 – May 2019)

Boeing Upgrade Projects (May 2019 – Mar 2020)

• Vendor Invoice Management (VIM Upgrade)
• SAP NetWeaver 7.5 ERP, S/4HANA 1511, 1610, 1709, 1809, SAP PI 7.5 SOLMAN 7.2, ECC, SRM, CRM, MDG, BI, GTS, and all RMAS systems
• S/4HANA & NetWeaver ABAP/JAVA based SAP System upgrades/Migrations

Boeing Zippy's Material Master Workbench (Mar 2020 – Mar 2021)

Responsibilities:

• Pre-prepping the development environment with SCI, streamlining the procedures, and the introduction of global macro to make development effort easy
• Dev Lead of the following work streams concurrently OTC, CRM, and PCE, e-Com (Hybris)
• Responsible for understanding Functional specs, producing all the technical specs, assigning work to offshore Malaysia and India team, code inspections for quality assurance, involved in testing cycles, signing off on the work completed, and status reporting for the team
• Heavily involved in coding the several highly complex pieces of work

For example: As Lean Order (LORD) was used in CRM and e-Com/Hybris, CRM LORD has limitation when a part number of a 18 characters is used instead of 40 chars.

• E-Com was later handed over to me as the third party contractors were at risk to deliver the solution.
• As e-Com was a critical and very complex solution that requires certain statuses to be displayed to customers based on various combinations of values coming from an order, delivery, billing, and global trade service.
• Proposed and built a configurable solution from scratch on that could enable the super user to configure any combinations of values that would derive the correct status to be displayed to customers on Part Page.
• This solution came with its own analysis report that allows users to know how the final status was derived. Various batch programs were also provided that can be reinitiate to recalculate statuses for certain documents.
• This very same solution was also replicated to auto close Service Requests in CRM
• Involved in the Hypercare of Boeing OneSAP and took over the ownership of mass updates to master data in Production systems.
• Make sure that the upgrade functionality works and did not break anything
• Retrofit all the codes from the old into the new upgrade environment
• The main person to execute the SPDD and SPAU transactions during the upgrade that compares the before and after upgrade at code level
• Coordinate with the Basis on the timing of all the transport requests imported into the system across all systems
• Correspond with SAP on defects on products or issues pertaining standard SAP
• Perform performance tracings and performance tuning
• Provide daily status updates

Background:

HECO is upgrading from:

• ECC 6.0 EHP 4 to ECC 6.0 EHP 7
• CRM 7.0 to CRM 7.0 EHP 3

Responsibilities:

• Responsible for analyzing all the results from Upgrade Smart Tools that compares the before and after products and impacts of all the SAP standard and customized codes
• Plan out all the steps to mitigate and remediate all the custom codes that may be impacted during upgrade
• Integrate plan into the overall project upgrade approach, timeline, and resourcing plans
• Create risk documents that may impact the upgrade projects
• Manage offshore development team
• Coordinate with other project teams (e.g. AMI/OBF/IVR/GEMS projects) and draft out approach and procedures to handle any code changes
• Keep track of all the codes changes that needs to be retrofit to the new system
• The biggest workload is to work with the CS lead to convert all the old ICWC screens to new ICWC screens while making sure that all the customized logic still works e.g. Split screen, Premise overview, Contract Account Tree display, BuAg and BP confirmation and Interaction record etc.
• Make sure that the upgrade functionality works and did not break anything
• Retrofit all the codes from the old into the new upgrade environment
• The main person to execute the SPDD and SPAU transactions during the upgrade that compares the before and after upgrade at code level
• Coordinate with the Basis on the timing of all the transport requests imported into the system
• Correspond with SAP on defects on products or issues pertaining standard SAP
• Perform performance tracings and performance tuning
• Provide daily status updates

Background:

• HECO's current CIS, “ACCESS”, has been in place at the Companies since 1991
• While ACCESS has consistently performed many of the basic functions required at the time it was implemented, customer and user demands (approximately 450,000) are exceeding its capabilities

Responsibilities:

• Is roped in to be the technical team lead to manage a team of developers from Puerto Rico, Malaysia, and onsite developers
• Assigned with Herculean task to bring the client's young and new team up to speed on best practice, enhancements techniques, introduction of new technologies, and provide sufficient training and support for the team
• Pre-prepping the development environment with SCI, streamlining the procedures, and the introduction of global macro to make development effort a breeze was amazingly introduced by in this project
• On top of that, he's core responsibility is to manage the development and Interface team and also provide technical assistance or advice to the technical, functional and business team
• Responsible to ensure good codes are delivered in timely manner and ensure milestones are achieved
• Developed few of the most complex programs like transformer load program, PDF retrieval on ICWC from Stream Serve, masking of SSN and Bank details and mass maintenance of functional locations
• The project has passed through 3 rounds of ITC and number of defects has made its way to the development team was surprisingly low compared to other projects
• To train team members and clients to deliver to a level that they can effectively produce quality work
• Performance tuning on programs, quality control and issue fixing
• Knowledge transfer of developments to the support team

Background:

• DPSG has recently bought the Snapple brand (MSSI) and in need to upgrade from 4.6 to ECC6 and merge their system into the Core business

Responsibilities:

• Put in place to help DPSG and HCL manage a team of developers that would help in absorbing MSSI (Snapple) into the core business
• The technical team spreads over US, Puerto Rico, India and Malaysia
• Core responsibility is to manage the Interface team and also provide technical assistance or advice to the technical, functional and business team. He also work closely with the EDI team mainly JCAPS and GXS to ensure all the mapping between SAP and the external party is done correctly
• Is responsible to ensure good codes are delivered in timely manner and ensure milestones are achieved
• Heavily involved in the blue print phase to help the functional and business formulate the functional specifications, delivery, QA over the span of 5 cycles of User Testing phase

Background:

Jet Aviation is suppose to go live with their iMRO implementation but they have not managed to change all the forms and contracts that is supposed to be for their customers and the engineering department

Responsibilities:

• Help Jet Aviation to revamp all their forms and contracts delivered to the customers and the engineering departments.
• Adapt the forms from previous non-iMRO projects to iMRO supported projects
• Trace all the major and critical problems and issues of iMRO and fix it
• The first project on iMRO was a Cessna C560 with a ground time of 5 days and departure on 19 March 2010. The iMRO solutions – which have been developed has very well been received by the users and have successfully proceeded the entire cycle from Task List Database – Notifications – Orders – MEB – EWI – to the Documentation in the new solution. The next aircraft project on iMRO is planned for end March 2010 and JetAviation will continue the stepwise roll-out to all aircraft groups and sites