Вы находитесь на странице: 1из 6

Business/Technical

Design Document
Department Maintenance
Nathan Christopher/TM
/18/2014

MFC SUMMARY INFORMATION

Change Requestor

EURC number

Jason Amos

23012978

Delivery manager

Planned date for deployment

Craig Palmer

TBC

Business area affected

IT service affected

CCM

Department Maintenance

MFC PRIORITY

Emergency

High

Medium

Low

MFC DETAILS

Business Justification
As part of a standard agent migration the linkage between Depot and client must be updated during the
weekend to ensure that the old agent is replaced with the new agent. The update must happen over
the weekend as operations need to issue deliveries from the old, at close of market and then issue
receives to the new. Trade messages are created using the depot and client linkages. The changes
are currently performed by a manual SQL but due to the future projected use and the attempt to
remove the request being performed by Production Support a systemic solution is required.
Incident and/or problem report (PR) numbers
that relate to this MFC (if applicable)

Service levels affected by this change

None
Impact assessment
Additional function required in order to request the bulk update
Who will validate change in UAT
Jason Amos Paul Danvers
AUTHORIZATION

Authorized by

Date

Steve Poole

19/06/2014

Date Created:

18/07/201418/07/14

Date Revised:
Last Saved By:

21/07/14
abhijit chavanpatil

2011 JPMorgan Chase & Co. All Rights Reserved.


Confidential And Proprietary
For Internal Use Only - Do Not Duplicate

Version: 0.2
Page 1 of 6

Worldwide Securities Services


Maintenance

- Department

Combined Business/Technical Design document Jason Amos Paul Danvers

BACKGROUND/SUMMARY

OF THE

PROBLEM

Reference

Priori
ty

Problem Summary

Business
Impact

CCMSMFC725
EURC
23012978

High

Currently, Production Support run sqls during a


migration weekend allowing Operations to bulk update
depot maintenance. The running of sqls by Production
Support is considered to be an activity that introduces
risk and as such an activity that should be removed from
their remit.
Additional Collateral Operations would like to increase
the capability of the bulk updates and as such the action
needs to be enhanced.
Creating a function to apply these updates will ensure
the process is owned by the correct department, reduce
risk of incorrect application and introduce control to the
process.

Med

REQUIREMENTS

Requirement

Create bulk linkages between client and depots on H02.


MFC725_BR01

Id
Description

The existing SQLs need to be considered for a standard Agent migration


(Full market and all clients) i.e. a find and replace of old and new depot
data.
As part of the CSD project a full Agent migration is NOT occurring, only
Collateral clients are being migrated and not all clients are to be migrated.
Due to the partial migration Operations need the ability to request replacing
of old depot with a new depot on a client (or borrower) specific update
basis.
The current sqls also update other department maintenance configuration.
Again, as Partial migration can occur the configuration is not a find and
replace it needs to be a find, copy and add with the new depot details.
As part of the process for partial agent migrations it is assumed:
Operations will be adding the additional linkages for clients that are
remaining.
Operations will be supply the data to be changed in the agreed format and
agreed location.
Existing process followed

Migration SQLs basic


process.docx

Date Created:

18/07/201418/07/14

Date Revised:
Last Saved By:

21/07/14
abhijit chavanpatil

2012 JPMorgan Chase & Co. All Rights Reserved.


Confidential And Proprietary
For Internal Use Only - Do Not Duplicate

Version: 0.1
Page 2 of 6

Worldwide Securities Services


Maintenance

- Department

Combined Business/Technical Design document Jason Amos Paul Danvers

Where the Bulk linkage function is selected and successfully complete the
user will be informed. The file applied will be moved to an archive folder.
Where the Bulk linkage function is selected and a file is not in the expected
location the user will be informed.
Where a new depot is not supplied, data not supplied in the correct format
or file named incorrectly the user will be informed that the upload has failed
due to formatting of the data.

Business Rules

Where an Old Depot and New Depot (no client / borrower) are supplied in
the data the function will find and replace all data in the 6 files linkage
and configuration.
Where an old depot, new depot and client (or borrower) are supplied in the
data the linkages will be replaced where the old and client (or borrower)
match IIPDA2, IIPDA3, IIPDA4
Where an old depot, new depot and client (or borrower) is supplied in the
data, the configurations will be found (using the old depot only), copied and
added with the new depot - IIPDDA, IIPXBI and IIPMSO.
Default (*) client (or borrower) must be considered.
Assumptions
Where a data match is NOT found no action will be performed.
Any clean up of additions in the configurations will be performed by
Operations.
Operations will provide Master depots, where required, in the data.
From Agent to Agent in the same market the configurations are the same.

Acceptance
Criteria

Bulk upload function available in H02.


The user will be required to select the initiation and confirmation that the
upload should take place.
Folders created in the IFS for data file to saved and requested from.
Archive folder created in the IFS for data file to be moved to following bulk
upload attempt.
Where the bulk upload is successful the user is informed Bulk
Department Maintenance update successful.
Where there is no file to apply for the bulk update the user is informed No
file in location <>.
Where the data is not in the expected format the user is informed Data in
the file is not as expected.
Where an Old Depot and New Depot are supplied in the data the function
will find and replace all data in IIPDA2, IIPDA3, IIPDA4, IIPDDA, IIPXBI and
IIPMSO where evident.
Where an old depot, new depot and client (or borrower) are supplied in the
data the linkages will be replaced where the old and client (or borrower)
match IIPDA2, IIPDA3, IIPDA4 i.e. the old depot will be replaced with the
new depot.
Where an old depot, new depot and client (or borrower) is supplied in the

Date Created:

18/07/201418/07/14

Date Revised:
Last Saved By:

21/07/14
abhijit chavanpatil

2012 JPMorgan Chase & Co. All Rights Reserved.


Confidential And Proprietary
For Internal Use Only - Do Not Duplicate

Version: 0.1
Page 3 of 6

Worldwide Securities Services


Maintenance

- Department

Combined Business/Technical Design document Jason Amos Paul Danvers

data the configurations will be found (using the old depot only), copied
and added with the new depot - IIPDDA, IIPXBI and IIPMSO.

Testing
Considerations

Defaults (*) should be considered in the scenarios.


For configuration addition, where an old depot, new depot and client (or
borrower) is supplied, the current data that includes accounts must be
considered in the scenarios.
File supplied can be mixture of including and not including the client (or
borrower)

Date Created:

18/07/201418/07/14

Date Revised:
Last Saved By:

21/07/14
abhijit chavanpatil

2012 JPMorgan Chase & Co. All Rights Reserved.


Confidential And Proprietary
For Internal Use Only - Do Not Duplicate

Version: 0.1
Page 4 of 6

Worldwide Securities Services


Maintenance

- Department

Combined Business/Technical Design document Jason Amos Paul Danvers

3
3.1.1

PROPOSED SOLUTION

1.1

PROCESSES
Current Process:

1.1 CURRENT PROCESSING


Proposed Processing:

1.2 DATABASE CHANGES

Retired Database

Amended Database

New Database

1.3 PROGRAMS / PROCESS CHANGES


1.3.1

Retired Programs/Processes

1.3.2

Amended Programs/Processes
Followings are processes/Programs are being Added for this requirements

1.2
AFFECTED OBJECT LIST
Name
Description

Type

Action

1.3
TURNOVER WORKLISTS
The following worklist(s) will be used for this development:
Application
CCS

Worklist
MFC 725

Description
MFC-725 : AutoFAX Purging Process Change

POST IMPLEMENTATION
1.4
SUPPORT DOCUMENTS
Reference Document
Location
Gateway Support Tracking Log

http://intraspectkm.jpmorganchase.com/gm/document1.9.2437537

Environment Manager Manual

http://intraspectkm.jpmorganchase.com/gm/document1.9.1966542

Date Created:

18/07/201418/07/14

Date Revised:
Last Saved By:

21/07/14
abhijit chavanpatil

2012 JPMorgan Chase & Co. All Rights Reserved.


Confidential And Proprietary
For Internal Use Only - Do Not Duplicate

Version: 0.1
Page 5 of 6

Worldwide Securities Services


Maintenance

- Department

Combined Business/Technical Design document Jason Amos Paul Danvers

REFERENCE DOCUMENTS

None.

DOCUMENT CONTROL
1.5
APPROVAL
The following groups and individuals have approved this document:
Name
Jason Amos
Paul Danvers
Jo Damen
Steve Poole
Craig Palmer
Abhijit Chavanpatil
Sabarish Ganapathi

Title
UAT Analyst
Client Processing Manager
Transaction Processing Manager
Application Development Manager
Applications Developer
Consultant
Concultant

1.6
DOCUMENT HISTORY
Versio Name
n
0.1
Nathan Christopher

Approver?
No
Yes
Yes
No
No
No
No

Date

Description

21/07/2014

Initial document of Business summary and


Business requirements plus proposed
technical solution

1.7
DOCUMENT STORAGE
{Add in a hyperlink to location of document in Sharepoint}

Date Created:

18/07/201418/07/14

Date Revised:
Last Saved By:

21/07/14
abhijit chavanpatil

2012 JPMorgan Chase & Co. All Rights Reserved.


Confidential And Proprietary
For Internal Use Only - Do Not Duplicate

Version: 0.1
Page 6 of 6