Data Architect
Resource Logistics
- Jersey City, NJ
- Contract
- Full-time
Jersey City, NJ
Contract(Remote work)Detailed JD
· Determine the scope of Data migration.· Document the data migration strategy.· Document Data Migration Protocol to go along with the data migration strategy.· Produce the Data Migration Summary report based on the data migration strategy and protocol documents.· Participate in finalizing the code migration strategy in conjunction to the data migration strategy.· Co-ordinate moving of various transports from a ,S perspective.· Support Mapping and Construction of Data from Legacy Systems· Establish and Support Pre-Load and Post-Load Business Signoff· Support Internal and External Quality Control and Audit Processes· Lead Data Defect Triage and Re,tion· Scope/Identify/guide any re,tion of incomplete/incorrect Data in Legacy Systems.· Validation of all the data once its moved across the environments (DEVàPQAàQAàProd)· Cutover planning and Mock cut-over coordination and fall over and fall out reconciliation working closely with Systems and Performance teams. Some of the points to be considered for cutover are:o Inclusion of reversion back to PROD original state post mock cutover exercises for first siteo Plan for mock cutover for 2nd site as FDC will already be in PROD· POST go-live monitoring of all data related activities and the whole cutover plan.· Some of the other specific responsibilities will also involve the following:1. Verification of Data Integrity between platforms - ERP, ,S, Serialization2. Coordination of delivery/ creation of BY Test data in each environment - DEV, PQA, QA and Prod3. Oversight of all things data migration environment to environment strategy - configuration, master and transactions as applicablea. Reconciliation of accelerator tool result for uplifts across platformsb. RCA for fill-out and follow-on corrective actionsc. Updated approach review to not repeat history for each Component load to higher environments.4. Data Conversion Strategy from lower to higher environments including BY configuration preservation where applicable and legacy MClient data conversion.a. LPN's with serialized hierClienthiesb. Inventory (LPN) by locationc. Orders by statusi. Inboundii. Outboundd. Orders not only by status including progress quantity details at header and at line item levele. Inventory by Location with LPN details regarding status, committed (all of the sub-tabs)f. Inventory reconciliation with ERP and Serializationg. Serialization Datah. Clinical Data