Corporate Finance Mainframe-4

OLSI – Online Sales Inquiry (Saks)

Document of Understanding v0.3

HBC Confidential
Authors
Name Location Phone Email

Mayank Bangalore kumar.mayank5@tcs.com

Manjunath Bangalore manjunath.bhadrakali@tcs.com

Revision History
Date Author Description

01/07/16 Mayank Functional overview of OLSI – Online Sales Inquiry

(Saks) by SARAH on 24/06/16 v0.1

07/07/16 Manjunath B Updated Functional Overview v0.2

07/07/16 Manjunath B Technical overview of OLSI – Online Sales Inquiry
(Saks) by SARAH on 30/06/16 v0.3

HBC Confidential
 Contents

1. Application Name......................................................................................................5
2. Purpose of the Application........................................................................................5

3. Business Process flow diagrams................................................……….5

4. Sub application details / Key business transaction...............................................6
5. Application User Information Yet to receive..........................................................6

6. Application usage pattern and seasonality and special processes 7

7. Support and Coverage requirements.......................................................................7

8. Overview of Functionality and brief descriptions of key process. .7

9. Online – Screen Inventory (for custom built)...........................................................8

10.Special data handling or security requirements (where

applicable).........................................................................................................8
11. Computations...........................................................................................................8
12. Dependencies...........................................................................................................8
13. History Related With the application....................................................................8
14. Languages supported (If Multilingual).................................................................8

B – Technical Overview...................................................................................8
15. Technology Stack.....................................................................................................8
16. License Requirements...........................................................................................10
17. Technology Variances...........................................................................................10
18. System architecture diagram...............................................................................10
19. Database Architecture...........................................................................................10
A) Physical data model and Logical data model............................................................11
B) List the key tables and their mapping to the transactions.......................................11
20. Backup, Recovery and Archival............................................................................11
21. Infrastructure Architecture Diagram for all Environments...............................11
22. Number of Instances.............................................................................................11
23. Performance and Availability...............................................................................12
24. Scheduled Upgrades.............................................................................................12
25. Setup Procedures...................................................................................................12

HBC Confidential
 26. Interfaces................................................................................................................12
27. Critical Jobs / Integration needs / Schedules Yet to receive...........................13
28. Technical data sheets............................................................................................13
29. Detail the Do’s and Don’ts and specific test scenarios....................................14
30. Ticketing System....................................................................................................14
Yet to receive......................................................................................................................14
A) Tools................................................................................................................................14
B) Reports............................................................................................................................14
31. Quantitative Assessment of Ticket data.............................................................14
Yet to receive......................................................................................................................14
A) Analyze Application Incident data..............................................................................14
B) Trend Analysis................................................................................................................14
32. Operating Procedures Yet to receive.........................................................15
A) Incident Management (all types) until Ticket closure...............................................15
B) Incident Reporting and Recording Mechanism.........................................................15
C) Planned Activity Resolution Process...........................................................................15
D) Unplanned activity Resolution Process......................................................................15
E) Disaster Recovery process............................................................................................15
F) Change Management Process......................................................................................15
G) Deployment Process.....................................................................................................15
H) Log Locations / Enabling / Debugging Process........................................................15
I) Release management frequency and process............................................................15
J) Installation Process.........................................................................................................15
K) Rollback Management..................................................................................................15
L) Third party Support including Helpdesk.....................................................................15
M) After hours support procedure..................................................................................15
33. Configuration Management. Yet to receive.............................................15
A) Configuration Management Process..........................................................................15
B) Configuration Mgmt (People, Hardware, Software, other assets)..........................15
34. Communication Process. Yet to receive...................................................15
A) Communication within the Team and Client.............................................................15
B) Escalation Process and Touch Points..........................................................................15

HBC Confidential
 C) Customer Communication Framework for Jobs, Monitoring..................................15
35. Verification and Validation process. Yet to receive..............................16
A) Application Functionality Verification.........................................................................16
B) Performance Testing.....................................................................................................16
C) System Integration Testing Process............................................................................16
36. Process templates Yet to receive.............................................................16

D – Known Issues, Bugs, Knowledgebase, Dependencies....................16

A – FUNCTIONAL OVERVIEW
1. Application Name
OLSI – Online Sales Inquiry (Saks)

2. Purpose of the Application

To provide near-real-time sales results by store or store/department or
department level for brick and mortar locations as they trickle up from the store to
the mainframe. It can also report on presells that were rung on a previous day and
are dropping on the current day. It does not include .com, Locator, or restaurant
sales.

3. Business Process flow diagrams

Fig 1- Purpose of Online Sales View

HBC Confidential
 T-Log Translation system saves transaction details into DB2 table on Mainframe
from POS system so that users can inquiry on the transaction details through green
screen and look at all the transaction details as to total transaction amount for the
day at store level or department level or store/department level. All store and
department details will be fetched from Company structure on real time basis. OLSI
reads the Mainframe DB2 table to generate output COGNOS reports.

4. Sub application details / Key business transaction

Yet to receive

5. Application User Information: Yet to receive

Department/ Key IT Site Contact

Number of Users
User Group area/functionali Person (if needed)
ty of the
application Tot Concurre
used al nt*

Application Support Owner (IT):

VP DVP/Director Development Mgr. Support Mgr.
Fred Muse Lex Davis Nona Ware Sarah Shaw

Application Owner (Business/BSM):

VP DVP/Director Manager
Alison Woodcock Kate Hansen Kirsten Grimaldi
Ed Stagman Andrea Robins

Banner (HB, HO, LT, Saks, Outlets, and CORP): Saks US and Canada, Find@ (POS)

Software Vendor:
Vendor Systematic Software Solutions
Contact name Steve Trischetta
Email stevet@syssoftware.com
Phone 732-297-8989

Skills Required to Support System (COBOL, ASP, and Java):

HBC Confidential
CICS, COBOL, VSAM, DB2

User/Business Group:
User Business Group
Store Management Stores
Kirsten Grimaldi and team BSM
Andrea Robins and team? Customer Relations

IT SME (Subject matter expert):

DVP/Director Manager Development SME Support SME
Lex Davis Sarah Shaw Steve Trischetta Sarah Shaw

Business SME (Subject matter expert):

DVP/Director Manager Development SME Support SME
Kirsten Grimaldi Kirsten Grimaldi Kirsten Grimaldi

User Training Documentation (Link below): Yet to receive

6. Application usage pattern and seasonality and special processes

Yet to receive

7. Support and Coverage requirements

SLA (Time application is available to users):

Day Application available Application unavailable
Monday-Thurs, Saturday 5 a.m.-11 p.m. Central 11 p.m.-5 a.m. Central
Region is PICICTF1 In reality it is only being
updated when the stores
are open and ISRS and
TLTS are running.
Friday 2:30 a.m.-11 p.m. Central 11 p.m.-2:30 a.m. Central
Sunday 8:30 a.m.-8:30 p.m. 8:30 p.m.-8:30 a.m. Central
Central

8. Overview of Functionality and brief descriptions of key process

Service Center Documentation (Link below):

HBC Confidential
Context Diagram (Link below):

R: TCS Application Support/Finance/OLSI

Requirements/Design Documents (System overview - Link below):

9. Online – Screen Inventory (for custom built)

10. Special data handling or security requirements (where applicable)

Yet to receive

11. Computations
Yet to receive

12. Dependencies
Yet to receive

13. History Related With the application

Yet to receive

14. Languages supported (If Multilingual)

Yet to receive

B – Technical Overview
15. Technology Stack

[Detail:
- Application type: Mainframe
- Application Stage: Production
o Application is released to Production
- Detail the Hardware ( if required )
o N/A

HBC Confidential
 - Detail the Operating system
o z/OS
- Detail the Software / Language
o IBM Mainframe
 Cobol & DYL-280
o Unix Server
 Unix Shell Script
- Detail the tools and any Integration technologies used
o File-Aid
 File manipulation tool
o Panvalet
 Member manipulation tool
- Detail all major and minor technologies / frameworks the application is
built with. the latest versions.
- Detail the data store
- Detail the version control tool
- In case of products establish the market name of the product, version &
vendor details.
- Establish if vendor AMC for third party product / support is required ; and
is available or not through Customer’s
- Cover Database, Administration / Security , Front-end GUI , Application
server , Language , API’s , Encryption , Monitoring tools , Development
tools , Reporting tools, Integration tools, Workflow , Rules engine etc ]

Platform (Mainframe, .Net, etc.):

Platform Application
Mainframe

Data Source (Database Name/File Qualifier):

Data Source Name Data Type Origin Application Platform
POS TLOG VSAM POS/TLTS Saks Mainframe
Data extracted VSAM Company Structure Saks Mainframe
from Company
Structure (for
department and
store information)
PIIC.SA.OLSIDEPT
PIIC.SA.OLSISTOR
Internal DB2 tables DB2 OLSI Saks Mainframe
TSA003STR_FLASH
TSA004STRDPT_FL
ASH

HBC Confidential
Security Permissions (List groups): Yet to receive
RACF AD Other
RACF

Security Regulations:
PCI PII Capital One Port
No No No
A. How do you grant access?

RACF

B. What data is being used?

Sales and returns at a summary level by store, store/dept, and dept/store.

C. How is data protected?

RACF/Mainframe

D. How is data transmitted (encrypted/Tokenized)?

Data resides on the mainframe.

16. License Requirements

Yet to receive

17. Technology Variances

Yet to receive

18. System architecture diagram

Yet to receive

HBC Confidential
 19. Database Architecture

Yet to receive

A) Physical data model and Logical data model

[Example power designer models]

B) List the key tables and their mapping to the transactions.

Yet to receive

20. Backup, Recovery and Archival

Yet to receive

21. Infrastructure Architecture Diagram for all Environments

Yet to receive

List Environments/Server names (Ex: Production, development, test, and

training):
Environment MF/Server Source Code Location
Production Mainframe Librarian
(PI.OPER.SOURCE)
Development Mainframe Librarian
(TI.PGMR.SOURCE)
Test
Training

HBC Confidential
 22. Number of Instances

Yet to receive
Instanc Instance type Instance Synchronizatio Accessibilit Remarks /
e ( Eg : Location n with y Centralized /
No Production , [ If Production Details Decentralize
Development hosted Instance , ( URL , IP d
, Testing ) outside State Yes / Address
Custome No etc )
r’s
Network
]

Detail the ALL access URL and links for different components such as

- Local databases
- Version control tools
- Application URL
- Reports etc

23. Performance and Availability

Yet to receive

24. Scheduled Upgrades

Yet to receive

25. Setup Procedures

Yet to receive

HBC Confidential
 26. Interfaces
Yet to receive

27. Critical Jobs / Integration needs / Schedules Yet to receive

Critical Job Information – (if application has critical jobs that will be monitored list
details in this table)
Critical Job Server or Site Schedu Scheduled Impacts if not Notifications Needed
le Completion completed on time late
Name (Due out
time))

Scheduling Dependencies High Level:

System Name Escalation Process
Predecessor for PISADOSL PKSADTL1 Programmer On-Call will
(This is the only batch job be notified and will reach
in the process. It prepares out to their/other teams if
store/dept information for necessary.
the next day and deletes
older data from the
proprietary DB2 tables.)

Impact to business if application is offline/running late/missing data (who,

what):
Who What
Store Mgt Real time data is not available
Cognos trickle sales reports will not be
accurate

Job Flow Diagram (Link below): Yet to receive

System Monitoring (List monitoring tool. Ex. TMON for MF/New Relic for Open
Systems):

HBC Confidential
 28. Technical data sheets
Yet to receive

29. Detail the Do’s and Don’ts and specific test scenarios

Yet to receive

C – Operational Overview

30. Ticketing System

Yet to receive

A) Tools

B) Reports

31. Quantitative Assessment of Ticket data.

Yet to receive

A) Analyze Application Incident data.

B) Trend Analysis

HBC Confidential
 32. Operating Procedures Yet to receive

A) Incident Management (all types) until Ticket closure.

B) Incident Reporting and Recording Mechanism.

C) Planned Activity Resolution Process.

D) Unplanned activity Resolution Process.

E) Disaster Recovery process

F) Change Management Process.

G) Deployment Process

H) Log Locations / Enabling / Debugging Process

I) Release management frequency and process

J) Installation Process.

K) Rollback Management.

L) Third party Support including Helpdesk

M) After hours support procedure

33. Configuration Management. Yet to receive

A) Configuration Management Process.

B) Configuration Mgmt (People, Hardware, Software, other assets).

34. Communication Process. Yet to receive

A) Communication within the Team and Client.

B) Escalation Process and Touch Points.

C) Customer Communication Framework for Jobs, Monitoring.

HBC Confidential
 35. Verification and Validation process. Yet to receive

A) Application Functionality Verification.

B) Performance Testing.

C) System Integration Testing Process.

36. Process templates Yet to receive

D – Known Issues, Bugs, Knowledgebase, Dependencies

Yet to receive

HBC Confidential