TECHNOLOGIES:

Programming Languages: BizTalk 2016/BizTalk 2013 R 2/2010/2009/2006 , C#, XSLT, ASP.NET, Visual Studio 2012/2010/2008/2005 and other programming languages under .NET environment. Also exposed in the following programming Cold Fusion Markup Language (CFML), ANSI C, Turbo C, C++, VBScript, JavaScript and Turbo Pascal.

Enterprise Application Integration Tool: BizTalk Server 2016, 2013, 2013 R2, 2010, 2009, ESB Toolkit 2.1, 2006, 2006 R2, BizTalk Server 2004, UDDI Services, SQL Server BI Tools such as SSIS.

Mapping Tools: BizTalk Server 2016, 2013 R 2/2010/2009/2006 /R2 maps, XSLT

Development Patterns and Practices: Enterprise Library 4.1 and up, ES toolkit 2.1/2.0 (implementation of custom resolvers)

EDI Standards: ANSI X12, HIPAA - 5010 (834, 835, 837, 997)

Databases: SQL Server 2016/2014/2012/2008 R 2/2008/2005/2000 back-end database (Analysis Services, SSIS, stored procedures, triggers, views, functions), ORACLE 8i back-end database, PL/SQL and SQL*Plus environment

PROFESSIONAL EXPERIENCE:

Confidential, Rockford, IL

Sr. BizTalk Lead/Developer/Integration Support | EDI Analyst

Responsibilities:

• Re-designed and modified existing HL7 interfaces for optimized performance operations such as envelop de-batching and lookup caching.
• Created a framework to convert HL7 messages into standardized canonical message eliminating tightly-coupled HL7 version schema references inside orchestration messages restricting the capability of integrating different HL7 versions for other partners without code changes in the orchestrations.
• Created a pipeline framework to dynamically change the SQL Server address in the send port configured as static WCF-SQL to have flexibility of avoiding dynamic send port calls inside orchestrations.
• Developed a custom behavior plugin merge request details and the response messages to instead of using orchestrations just for merging the request and response message.
• Worked with business analysis team to define the company’s first fully functional companion guide definition for EDI 837. Since the company is communicating for clearing house for processing EDI-HIPAA related transaction, they don’t have a fully functional companion guide for 837 transaction.
• Converted the legacy 837 processing interfaces into a BizTalk integration platform utilizing different artifacts such as EDI schemas, mappings, orchestrations and BRE.

Confidential, Redwood City, California

Sr. BizTalk Developer/Integration Support | Enterprise Application Integration Analyst

Responsibilities:

• Rejoined the integration for additional business requirements needed for currently implemented ESB integration platform in compliance with Liquid Biopsy products or Confidential .
• Supported and maintained monitoring to the currently running GHI.OSM/ESB BizTalk application in Production environment.
• Re-designed and modified Distributable Results interface for the classification of Confidential information from source CRM/Salesforce into StarLims data translations.
• Modified the maps and orchestrations applying interrogations of the message data from CRM/Salesforce to categorize of the Order in Confidential or non- Confidential .
• Modified MaterialReturn and LabCrmExchange interfaces for changes in the processing behavior of Acks/Nacks sent back from CRM/Salesforce, ShipService and StarLims.
• Worked with optimizing Salesforce-StarLims data transfers due to issues of max-out transactions per user account by utilizing multiple accounts usage distribution through data entity types.

Confidential, Wisconsin

Sr. BizTalk Developer/Administrator

Responsibilities:

• Worked on trading partner for setup and configurations on BizTalk and Microsoft AX (CRM) for new and existing trading partners.
• Coordinated with different trading partners and vendors on exchanging information needed for BizTalk application configurations such as certificates, EDI and AS2 configurations.
• Analyzed and modified mapping bug fixes on currently existing Nexus BizTalk applications.
• Provides production support on different BizTalk applications on a day to day basis to ensure data are flowing between CRM application to different trading partners.

Confidential, Chicago, Illinois

Sr. Integration Developer / Sr. BizTalk Developer

Responsibilities:

• Worked with Master Data Management (MDM) product called MultiVue used as master data source for the entire Confidential International systems within North American region (both US and Canada).
• Fine tune BizTalk configurations and include BizTalk Server to be part of the SCOM monitoring tools.
• Also, administers BizTalk Server and its applications used for real-time interface between MDM-MultiVue and other systems.
• Analyzed and designed integration interfaces between MultiVue with different systems used by Confidential such as Microsoft CRM Dynamics, EPIC and Benefit Point (BP).
• Created new SSIS packages for bulk initial loads from source systems (CRM, EPIC and BP) into MDM-MultiVue. Also modifies existing SSIS integration packages for additional business requirements and data processing changes.

Confidential, Novi, Michigan

Sr. BizTalk Developer

Responsibilities:

• Worked with different integration teams for connecting enterprise-wide logistics systems of on-premise and external systems integration for Ryder.
• Designed and proposed integration process flow based on service-oriented architectural principle of BizTalk Server.
• Supported other non-BizTalk integration team on defining and creating schemas that are in compliance with BizTalk artifact requirements.
• Worked with different BizTalk interfaces connecting internal services (web UIs, LMS, Logging), web APIs (WCF services and RESTful services etc.), database back-end (SQL Server) and external systems (CouchBase, FourKites, MacroPoint).
• Defined and created xml schemas, maps, custom pipelines, custom pipeline components, orchestrations for the following interfaces:
• GeoFenceResponse processing
• GetGeoLocation lookups
• RequestTruckInformation transaction processing
• Sending and Receiving Truck Loads
• TripLateNotification processing
• TripStopEvent processing
• Freights information transactions
• Truck Capacity processing
• Created deployment packages for BizTalk interface applications and documentation for installation guide and interface use cases.
• Provided some training and knowledge-transfer assistance for other team that are non-BizTalk to help them understand the architectural design of BizTalk Server processes.

Confidential, Redwood City, California

Sr. BizTalk Developer / Enterprise Application Integration Analyst

Responsibilities:

• Designed Enumeration Translation Framework (cross referencing definition for different sources) that will be used for enumeration translation definition from one LOB to another (such as Salesforce which is CRM by LOB into StarLims which Lab by LOB category).
• Introduced the caching-approach of the enumeration translations to avoid numerous SQL connections and transaction when performing enumeration translation lookup on the database.
• Created several BizTalk interfaces with the CRM and LAB lines of business.
• Introduced the use of BizTalk CAT Instrumentation as the standard tracing and instrumentation tool for all BizTalk based applications.
• Created Material Return interfaces which required debatching/rebatching of queries from StarLims to SalesForce, from StarLims to Shipping Service then to SalesForce with asynchronous RESTful services calls.
• Created DistributableResults interface connecting the could-base Salesforce (CRM) distribution processes into different stages of operations in Confidential ESB (enterprise service bus) services (i.e. RRS, RAS, RSS, Fax Services etc.) in which some of the process requires debatching/rebatching as per some of the invoked services requires.
• Leveraged the capability of calling/invoking RESTful request-response services in asynchronous process.

Confidential, Neenah, Wisconsin

Sr. BizTalk Developer / Enterprise Application Integration Analyst

Responsibilities:

• Designed integration framework and patterns using BizTalk as enterprise application integration tool utilizing ESB Toolkit 2.1 as BizTalk design pattern.
• Created interfaces as part of the Confidential Integration System (BIS) that serves as middleware and data repository to be used for application integration and instrumentation.
• Implemented instrumentation tools to be used by BizTalk integration applications for validations of data processing such as data imports and export from one system to another (e.g. SAP to BMS, BMS to Flat file, EDI to SAP, SAP to external supplier such as Ariba (cloud based), SAP to Confidential internal system etc.).
• Developed integration applications using BizTalk for the following BMS processes: Handling Unit, Order Events, Operation Setup, Operation Output, Scrap Transaction and Work Centers coming from BMS legacy system into Operation Data Store (ODS) and Enterprise Data Warehouse (EDW).
• Created business rules that performed a complex SAP process
• Created different custom pipeline components such as message archiving process mechanism and transaction properties promotions and other custom processes per requirements of the interfaces.
• Developed integration applications using BizTalk for the following SAP Process: Production Orders, Purchase Orders and Sales Orders coming from SAP into different systems such DATA3, Shuttle and Mills.
• Created canonical schemas used for integration solutions, flat file schemas, SAP IDOC schemas and SQL table schemas.
• Created composite schemas for different SQL tables. Also developed custom pipelines associating flat file schemas and custom pipeline components.
• Published schemas as WCF service used for cross-referencing and lookup processing in BIS.
• Created/Developed maps used for different integration applications requirements such as: (1) SAP IDoc to canonical schema; (2) SAP IDoc to WCF service cross-reference; (3) multipart messages (SAP IDoc, WCF response, flat file schemas) to canonical schema; (4) Canonical schema to either flat file, SAP IDoc or composite operation schemas.
• Developed orchestrations used in different integration applications designed to be used as an itinerary service that can be called and used inside BizTalk ESB itinerary.
• Created/Developed custom .NET Helper components used inside orchestrations, mappings and business rules and instrumentation process.

Environment: Windows Server 2008 Enterprise, BizTalk Server 2013, Visual Studio, BizTalk Server 2010, Visual Studio 2010 Team Edition, TFS, C#, MS SQL Server 2012/2008 R2/2012, XSLT, XPath, Business Rule Engine, Enterprise Service Bus (ESB) Toolkit 2.1, WCF, Web Services, SAP, DTD, Gentran.

Confidential, San Francisco, California

Sr. BizTalk Developer / EDI Analyst

Responsibilities:

• Created custom .NET Windows Service application using C# that serves as a pre-processor before EDI reach BizTalk application’s EDI disassembler process. This pre-processor application is used to handle large inbound EDI files more 100MB size by splitting into multiple transaction sets within the file with 5000 INS segments each transaction so that BizTalk will not go into message throttling errors.
• Analyzed and created mapping comparison of companion guides between trading partner companion guides and SFHP companion guide.
• Created canonical schema used for mapping between 834 EDI HIPAA transactions and SFHP internal systems such as QNXT application.
• Developed custom pipeline component that grouped multiple 834 EDI eligibility files based on trading partner and consolidate them into one 834 EDI file with 10,000 INS segments per transaction.
• Created different SQL stored procedures that insert data from mapped EDI 834 eligibility file into SQL Server databases.

Environment: Windows Server 2008 Enterprise, BizTalk Server 2009, Visual Studio 2008 Team Edition, TFS, C#, MS SQL Server 2008 R2, XSLT, XPath, EDI HIPAA Transaction (834).

Confidential, Aliso Viejo, California

Sr. BizTalk Developer

Responsibilities:

• Created different interfaces for legacy system migration from eGate mapping tool to SAP and other external clients of Confidential .
• Developed the following interfaces from different clients into SAP: A052 United Way Deduction to SAP, A309 ESS Clock Time to SAP, A271 Timberline Payroll to SAP. Interfaces involve conversion and mapping of flat files into SAP IDoc format.
• Developed A244 Telecard Billing Information and A286 Gross Payment Australia that utilized the concept of convoys in which it requires both pair of files - Master Information data and Detail data in order to process the complete the mapping consolidation process.

Environment: Windows Server 2008 Enterprise, BizTalk Server 2010, Visual Studio 2010 Team Edition, TFS, C#, MS SQL Server 2008 R2, WCF services, eGate Legacy mapping tool, XSLT, XPath.

Confidential, Minneapolis, Minnesota

Sr. BizTalk Developer

Responsibilities:

• Created Tax File Extract BizTalk application for generating Tax (Periodic and Quarterly) files in high performance database polling resulting into a very short period of time in generation process in comparison to the legacy application which took 30 hours to generate the quarterly files of all Confidential small and medium companies into 8 hours or less in the newly develop BizTalk Tax file Extract system.
• Designed and developed interface application in BizTalk that would import different deduction types from different clients to be uploaded to Confidential Payroll System.
• Architected and developed the Client-To- Confidential Import Interface application using ESB concepts for enterprise application integration. Implemented and used ESB Toolkit 2.0 as primary tool for EAI.
• Redesigned and converted Confidential Data Export Services, a Windows service legacy system into BizTalk platform integrated with Business Activity Monitoring (BAM), acknowledgment handling and log event tracking mechanisms.
• Developed numerous custom pipeline components used for decoding/formatting flat files, XML and Excel spreadsheets used in receive and send ports.
• Exposed xml schemas and orchestrations as WCF services with the use of ESB itineraries as operational steps for manipulating different messaging operations.
• Created/Developed complex data access layers comprising stored procedures, custom .Net components written in C# using Enterprise Library 4.1 as its design patterns.
• Created event logging mechanism tool component that monitors and stored the event processes and operations of a BizTalk custom interface application from start to finish.

Environment: Windows Server 2008 Enterprise, BizTalk Server 2009/2010, Visual Studio 2008 Team Edition, C#, MS SQL Server 2008, BizTalk ESB Toolkit 2.0/2.1, UDDI Registry Server, IIS, WCF services, Legacy Payroll system.