This is a sample of the deployment plan on how to carry out the cut over activities for the migration from an old interface to web service interface with service providers.
Cybersecurity Awareness Training Presentation v2024.03
Deployment Plan for B2B Integrations
1. Now until Day 0
Task Details Begin Time End Time Owner Status
Soft Launch 1-Mar-09 Customer Dev Team
Load Dbacklog Orders
- Order Confirmed Date - 1/Nov/2008
- Backlog order
1-Mar-09 Customer Dev Team
DRAGONfx 2.0 Change Ticket Change Ticket
Preparation - Master CT
- MQ CT
- Control-M CT
- DB CT
Submit the CT - refer to CT & Contact tab 1-Mar-09 Customer Dev Team
Upstream/Downstream Change Ticket
Preparation
Review Deployment Plan 1-Mar-09 Customer
Review the Deployment Plan
- Webservice Project Team / Business (Upstream/downstream)
- Upstream/Downstream Systems Teams, IT
- LSPs
Day 1
Task Details Begin Time End Time Owner Status
Change Ticket Review 2-Mar-09 Customer
Change Ticket Review for Webservice Change Ticket and
Upstream/Downtream systems Change Ticket (Upstream/downstream)
Teams, IT
Day 2
Task Details Begin Time End Time Owner Status
Verify Webservice Connectivities LSP able to connect to Webservice thru https 9:00 AM 4:00 PM Customer IT, Vendor IT
Copy/Verify OMI Master Data 9:00 AM 4:00 PM Customer Bussiness Support
- Copy the OMI Master data from UAT
- Verify the OMI Master data
Pull/Verify DRAGON 1.0 Users Accounts 9:00 AM 4:00 PM Customer Logistics Business IT need to pull out now
- Pull out the old applicaton 1.0 user accounts
- Create the user accounts in application 2.0
Verify Master Data 9:00 AM 4:00 PM Customer Logistics / COM /
- Review all the master data (especially on Part, Vendor Pull all the master data
Part, etc) COC business, Logistics in xls file to the team.
Business,
Procurement, Customer IT
Day 2
Task Details Begin Time End Time Owner Status
Create User Accounts in Application 2.0 - Create the user accounts 9:00 AM 4:00 PM Customer Logistics
Load/Verify Application 1.0 Final Orders 9:00 AM 10:00 PM Customer Procurement
- Orders loaded up to that day same as Application 1.0
- Clear all the message fallout
- Keep deployment day feed in webservice transaction
table (example, SO / SOC / MN / etc) in case LSP
required
9:00 AM 1:00 PM Vendor Business / IT
Deploy LSP application ( no data interface - Deploy the changes in LSP system and point to Inventory quantity can
to within lsp and Dell) Application 2.0 webservices send to us on Day 0 if
- Physical inventory count for LSP (DMI / VMI) hub operation is stop
Stop Application 2.0 - Stop the application 2.0 weblogic 9:30 AM 10:00 AM Customer IT
2. 10:00 AM 12:00 PM Customer IT
Change Order Management batch jobs - Change the Order Management data feed to application
and LSP Feed-in folder 1.0 and application 2.0
- Change the LSP feed-in folder to another new folder
name
Adjust Inventory 10:00 AM 11:30 AM Customer Logistics/Customer Inventory quantity can
- Get the latest inventory info from Hub
send to us on Day 0 if
- Update/Adjust the Inventory table IT
hub operation is stop
Final turn application 2.0 orders - set the email account for application 2.0 email 10:00 AM 12:00 PM Customer IT
notification
- delete ETA_TMP table
- - Keep deployment day feed in webservice transaction
table (example, SO / SOC / MN / etc) in case LSP needed
Change vendor currency conversion setting 9:00 AM 12:00 PM Customer Logistics
Change vendor currency conversion
setting
Implement freight system changes Point to new application 2.0 DB view 9:00 AM 12:00 PM Customer IT
Deploy the application 2.0 build scripts Run the deployment build scripts with all the jobs enable 10:00 AM 12:00 PM Customer IT
11:00 AM 1:00 PM Customer Logistics / COM /
Confirm the master data and orders - Final verify all the master data and make sure non-
COC business, Logistics
intergrity. backlog orders set properly
- Make sure no records in webservice_transaction table Business,
Procurement, Customer IT
Start the Weblogic for Backend/Frontend services 12:00 PM 1:00 PM Customer IT
Turn on Application 2.0 application
services
Verify/Test order management Feed Files - Make sure application 1.0 and application 2.0 able to 12:00 PM 1:00 PM Customer IT
load/process the orders and master data
4:00 PM Customer IT, Vendor IT
Testing with LSP - Test with LSP on the webservices 1:00 PM
Day 3
Verify/Test freight system changes Able to pull the existing application 2.0 orders thru DB 9:00 AM 4:00 PM Customer IT
Implement Online Webfarm changes Point to new application 2.0 webservice 9:00 AM 4:00 PM Dell IT
Verify/Test Online Webfarm 9:00 AM 4:00 PM Customer IT
Able to pull the existing application 2.0 orders thru
webservice
Point to new application 2.0 DB 9:00 AM 4:00 PM Customer IT
Implement Customer Care system
changes
Implement Datamart changes Point to new application 2.0 share folder 9:00 AM 4:00 PM Customer IT
Implement Ebilling changes Point to new application 2.0 webservice 9:00 AM 4:00 PM Customer IT
Monitor Application logs Monitor application logs 9:00 AM 4:00 PM Customer IT
Verify/Test Customer Care system Able to pull the existing application 2.0 orders thru DB 9:00 AM 4:00 PM Customer IT
Verify TNT status Make sure the in-factory/ex-factory status is correct 9:00 AM 4:00 PM Customer Logistics
Verify OMI status Monitor the OMI calculated data and email status 9:00 AM 4:00 PM Customer Logistics / COM /
COC business, Logistics
Business,
Procurement, Customer IT
Verify Inventory Movement Able to perform Inventory movement from LSP 9:00 AM 4:00 PM Customer Logistics / COM /
COC business, Logistics
Business,
Procurement, Customer IT
3. Verify Reports Verify Fulfillment, TNT, Inventory, OMI reports 9:00 AM 4:00 PM Customer Logistics / COM /
COC business, Logistics
Business,
Procurement, Customer IT
Verify other downstream/upstream Able to pull the existing application 2.0 orders 9:00 AM 4:00 PM Customer Logistics / COM /
systems COC business, Logistics
Business,
Procurement, Customer IT
Final verification Final verify all the testing results before Go/No-Go 4:00 PM 4:30 PM Customer Logistics / COM /
COC business, Logistics
Business,
Procurement, Customer
IT/Vendor Business, Vendor IT
GO/NO-GO Meeting GO/NO-GO Meeting 4:30 PM 5:00 PM Customer Logistics / COM /
COC business, Logistics
Business,
Procurement, Customer
IT/Vendor Business, Vendor IT
Day 4 onward
Task Details Begin Time End Time Owner Status
Close the Change Ticket Update and close the Change Ticket 9:00 AM 4:00 PM Customer IT
Stabilization Start Monitor Trouble Ticket and route to project team 1-May-09 Customer Logistics/Customer
IT
4. Day 3
Task Details Begin Time End Time Owner Status
Stop application 2.0 6:30 PM 7:00 PM Customer IT
Stop the application 2.0 application and change back to soft launch
setting
7:00 PM 10:00 PM Customer IT
Copy upstream/downstream feed files back to Copy the upstream/downstream feed files from application 2.0
application 1.0 back to application 1.0
Copy the TNT status from application 2.0 tables to application 1.0 7:00 PM 10:00 PM Customer IT
Copy the TNT status / servicetag records from
application 2.0 DB to application 1.0 DB
Set the merge order in application 1.0 7:00 PM 10:00 PM Customer IT
Base on the application 2.0 merge order and set the application 1.0
fulfillment table
Adjust the Inventory 7:00 PM 10:00 PM Customer Logistics Business
Base on the application 2.0 inventory and adjust back on
application 1.0
Rollback MQ changes Change back to original MQ servers 7:00 PM 10:00 PM Customer IT
Rollback upstream/downstream/LSP changes Rollback to their original application settings 7:00 PM 10:00 PM Customer Change Owner
Verify back out result Verify back out result 10:00 PM 11:00 PM Customer Logistics/Customer IT
Day 4
Task Details Begin Time End Time Owner Status
Close the Change Ticket Update and close the Change Ticket 9:00 AM 4:00 PM Customer CT Implementer