System Architecture v3.0

Approved and Issued by: Project Office
Template Version: 1.2
Template Revised: August 20, 2003
System Architecture Document
Project: Blue Bird
Ver 3.0
PREPARED BY REVIEWED BY APPROVED BY
NAME Jon Fortman
1. John Broom
2. Richard Moseley
3. Lynese Sanders
4. Rogena Baston
5. Joe Mendoza
6. Donny Faries
7. Bobby Crabb
Donny Faries
ROLE Tech Lead
1. Tech Lead Mentor
2. Developer
3. Analyst
4. Analyst
5. Developer
6. Application Architect
7. Project Manager
Application
Architect
SIGNATURE
DATE 21 February 2005 21 April 2005 6 May 2005

Blue Bird System Architecture Document
Page 2 of 21 Last Update Date: 10/23/2015 3:19:00 PM
Z:tempwindows20151023151937_6c88cb31fd9a74c177e84389c72d4c56be197fb0542ed302-b5e9-4e01-9f17-48d63e81bafb-
151023151935-lva1-app6891.docx Last Saved By: Jon
TABLE OF CONTENTS
1. KEY INDIVIDUALS INVOLVED...............................................................................................................3
BUSINESS PROJECT SPONSOR........................................................................................................................3
RSTS PROJECT SPONSOR.............................................................................................................................3
PROJECT MANAGER......................................................................................................................................3
2. CURRENT SYSTEM...............................................................................................................................4
CURRENT HARDWARE DIAGRAMS AND MODELS .................................................................................................4
CURRENT TECHNICAL ENVIRONMENT NOTES.....................................................................................................4
Technical Component: All............................................................................................................4
3. FUTURE SYSTEM .................................................................................................................................9
FUTURE HARDWARE DIAGRAMS AND MODELS ...................................................................................................9
FUTURE TECHNICAL ENVIRONMENT NOTES ..................................................................................................... 11
Technical Component: All..........................................................................................................14
8. GENERAL ........................................................................................................................................... 18
ASSUMPTIONS ............................................................................................................................................ 19
CONCERNS ................................................................................................................................................ 19
CONSTRAINTS ............................................................................................................................................ 19
NOTES ...................................................................................................................................................... 19
9. CHANGE LOG ..................................................................................................................................... 19

1. Key Individuals Involved
Business Project Sponsor
Julie Buckley, Director New Business Development
Susie Moore, Manager Service Plans
RSTS Project Sponsor
Sam Whitling - Sr. Director EDM, RSTS
Project Manager
Bobby Crabb – Project Manager

2. Current System
Current Hardware Diagrams and Models
Current Technical Environment Notes
Technical Components
RadioShack
Food Mart
Company Store
RadioShack
Network Server
(Visual Basic, Access DB, ANSO)
Tandem (COMM system)
Call Center Units
010118, 010119
Service Center
IBM
PYTHON (Unix)
IBM
GLOROCP1
(Unix)
Food Mart
Franchise Store
RadioShack
Mainframe - IBM OS/390
(COBOL, CICS, Assembly, VSAM, DB2)
Assurant
Statement
Systems
Fax
RSSP Management

Process To Hardware Relationships (Current System):
RadioShack
Food Mart
Company Store
RadioShack
Network Server
Tandem
Call Center Units
010118, 010119
Service Center
PYTHON (Unix)
GLOROCP1
(Unix)
Food Mart
Franchise Store
RadioShack
Assurant
Statement
Systems
Franchise
RSSP Price
Maintenance
IBM
Monthly Sales
Xmit (batch) -
RS Admin
Monthly
Claims Xmit
(batch)
Confirmation
Letters
GLOROCP1
(Unix)
RSSP Retail Price
Control VB App
CSV1000 (online)
Monthly Sales & Claims
Xmit VB App
CSV5000(online)
ANSO generated
replacements
Sales Entry System Admin
Unit 010118 DR (sales,
refunds)
Sales Entry System Admin
Unit 010119 DR
(replacements)
RSSP Management
RSSP Lookup,
Update, Phone
Logs
RSSP Legacy
Price
Control(online)
RSSP Lookup, Update,
Phone Logs
Contract Services Batch
Processes
Amortization
ICRT System
Srv Ctr Onsite
Cust Xmit
RSSP Legacy
Price Control
(batch)
Tandem
Active
Contracts
Reporting
Begin And End
Date Daily
Validation
Daily Sales
Reporting
Refund
Matching
Status Code
Updating
Daily EDI Sales
Xmit (batch) -
Fed Warr Admin
Value Added Network
(GXS - Global
eXchange Services)
New Business
and Renewals
Telemarketing
Srv Ctr Daily
Report (sales,
refunds, ICRTs)
Tandem
Store Daily
Report (sales,
refunds)
Tandem
RSSP Retail
Price
Control(batch)
IBM
IBM
Fax
Franchise
RSSP Sales &
Refunds

Description (general synopsis of technical components):
Fax
Franchise RSSP Sales & Refunds: These must be faxed to admin unit 010118 due to the fact
that franchise stores operate on a different POS system than retail stores or service centers.
PYTHON (Unix)
Franchise RSSP Price Maintenance: Comes from RSSP Legacy price control once per month.
Full base file goes out 3 times per year (every four months).
Network Server
Monthly Sales & Claims Xmit VB App CSV5000: Online initiation via Visual Basic program,
CSV5000, of jobs that support the Monthly Sales and Claims Xmit to Assurant. The process
chain begins with data found on a MS-Access database.
RSSP Retail Price Control VB App CSV1000: RSSP pricing for retail stores only are controlled
through this Visual Basic program.
ANSO Generated Replacements: Retail stores have the ability to perform replacements for
equipment covered under an RSSP by going into the appropriate section of ANSO. These
replacements are harvested nightly from a DB2 pooling table and routed into nightly processing
for the 010119 daily report.
GLOROCP1 (Unix)
Monthly Claims Xmit(batch): Batch job that FTPs claims against RSSPs to Assurant(Federal
Warranty).
Monthly Sales Xmit(batch) – RS Admin: Batch job that FTPs RSSP sales and refunds to
Assurant (Federal Warranty) for those contracts written on products that are administered by
RSSP.
Confirmation Letters: These are harvested every two weeks from DB2 to send to customers to
confirm their RSSP purchase. A copy of the terms and conditions is included in the mailing done
by Statement Systems.
Value Added Network (GSX – Global eXchange Services)
Daily EDI Sales Xmit (batch) – Fed Warr Admin: RSSP sales and refunds for those contracts
carrying products administered by Assurant are FTPed daily via EDI format to GSX who then
xmits them to Federal Warranty.
Mainframe – IBM OS/390
All Contract Services Batch Processes run on this machine.

The following entities and their respective subsystems are dependent upon both online and batch
processes on this machine:
Call Center Units 010118, 010119
Sales Entry System Admin Unit 010118 Daily Report: Specialty daily report that processes
transactions not done by the field (RSS). Includes RSSP giveaways, franchise sales and
refunds, phone-in RSSP sales and refunds.
both phone-in replacement transactions (for equipment covered under an RSSP) and
replacements performed directly by the field via ANSO. The ANSO replacements are
harvested nightly during batch processing of the 010119 daily report and merged with the
replacements done via CICS by 010119 personnel.
RSSP Lookup, Update, Phone Logs: CICS based system that allows display and update of
RSSPs. Viewable by all 010118 and 010119 personnel. Most have update access.
RSSP Management
RSSPs. Viewable and updateable by all RSSP management.
Begin and End Date Daily Validation: For newly sold contracts, this batch process
1) supplies missing begin and end dates for contracts based on the contract length
2) validates equipment information and RSSP pricing
RSSP Legacy Price Control (online): CICS based system that allows qualified RSSP
personnel to add, change and delete RSSP pricing for those selling points and subsystems
that use this pricing system. Maintenance applied to this system is supposed to kept in
sync with the retail pricing system as well.
Daily Sales Reporting: Batch reporting of all RSSP sales and refunds from all sale points
including unit 010118 (franchise also), retail stores and service centers. Transactions are
harvested from DB2.
Amortization: Monthly batch reporting that harvests sales and refunds from DB2 in order to
provide journaling reports for all sales and refunds and amortization reports for the states of
NM, ND and MA. The sales and refunds file from this process feeds the Monthly Sales
Xmit(batch) – RS Admin to Assurant subsystem.
Refund Matching: daily batch process that attempts to match RSSP refund transactions to
the original RSSP ticket. If matched, a refund match flag is set on the original ticket and
the control/drop id is set on the refund transaction to that of the original ticket.
ICRT System: Monthly harvest of repairs done for products covered under an RSSP from
repair DB2 tables. Files from this subsystem feed subsystem Monthly Claims Xmit(batch)
to Assurant for the repairs portion.
Status Code Updating: Monthly batch process that sets the status code of contracts
according to whether the end date is greater than or less than/equal to the current date.
Active Contracts Reporting: Monthly process that does reporting on all active contracts
within DB2.

New Business and Renewals, Telemarketing: Monthly processes that produce
telemarketing reports used for RSSP new business and renewal solicitations. Mail
solicitation records are produced but are not currently sent to the third party contracted
printer.
Tandem
Service Center Onsite Customer Xmit: weekly process that harvests all active onsite RSSP
customers from DB2 that have been assigned to a service center and xmits their contract
information to the assigned service center. Also figures out add, change and delete maintenance
for all customers.
RSSP Legacy Price Control (batch): daily process that figures add, change and delete
maintenance for RSSP pricing that is used by the service centers.
RSSP Retail Price Control (batch): daily process that figures add, change and delete
maintenance for RSSP pricing that is used by the retail stores.
Service Center Daily Report (sales, refunds, ICRTs): Xmit of service center RSSP sales, refunds
and ICRTs on their daily report.
Store Daily Report (sales, refunds): Xmit of retail store RSSP sales and refunds on their daily
report.

3. Future System
Future Hardware Diagrams and Models
RadioShack
Food Mart
Company Store
RadioShack
Network Server
Tandem (COMM system)
Service Center
IBM
PYTHON (Unix)
IBM
GLOROCP1
(Unix)
Food Mart
Franchise Store
RadioShack
Assurant
RSSP Management
Tandem
IBM
?
IBM
?
SVS

Future Technical Environment Notes
Hardware Acquisitions: There will be no additional hardware needed for this project.
Mainframe MIPS Reduction: Some reduction can be seen in the process synopsis below but there
will also be new processes created. As a result, it is not expected that the project will either increase
or reduce mainframe MIPS significantly. Furthermore, as some processes will be converted from
monthly to daily, the MIPS will not be reduced but, rather, redistributed.
Process Summary:
Changing Processes:
2.0 Franchise RSSP Price Maintenance: Comes from RSSP Legacy price control once per
month. Full base file goes out 3 times per year (every four months).
 Change to accommodate dealer net cost
3.4.4 Franchise RSSP Sales & Refunds: Will leverage the current process until the automation of
this piece can be done in a separate project.
 Change to handle dealer net cost
2.0 RSSP Retail Price Control VB App CSV1000: RSSP pricing for retail stores only are
controlled through this Visual Basic program.
 Change to handle display, update, add of dealer net cost.
Warranty).
 Change to satisfy 4.2-5 Weekly Claims Xmit, Re-Xmit
RSSP.
 Change to satisfy 4.1-3, 5.6-1 Daily Sales/Refunds/Cancels Xmit
5.2.1-17 Repair Status/Event: Batch process that sends repair status updates to retail stores.
 Change needed so that the current process maps current statuses being sent to the statuses
needed by Assurant.
5.4 Sales Entry System Admin Unit 010118 Daily Report: Specialty daily report that processes
 Change to display svp sku id, svp catg id, dealer net cost
4.4 Amortization: Monthly batch reporting that harvests sales and refunds from DB2 in order to
provide journaling reports for all sales and refunds and amortization reports for the states of NM,

ND and MA. The sales and refunds file from this process feeds the Monthly Sales Xmit(batch) –
RS Admin to Assurant subsystem.
 Change to handle requirements section 4.4
ICRT System: Monthly harvest of repairs done for products covered under an RSSP from repair
DB2 tables. Files from this subsystem feed subsystem Monthly Claims Xmit(batch) to Assurant
for the repairs portion.
 Change to daily process
3.4.1 Store Daily Report (sales, refunds): Xmit of retail store RSSP sales and refunds on their
daily report.
 Change to handle in-store (partial) replacements
3.4.2 Service Center Daily Report (sales, refunds, ICRTs): Xmit of service center RSSP sales,
refunds and ICRTs on their daily report.
 Change so that Auth# is xmitted because the repair status refresh requires auth# on the F3
file.
New Processes:
4.2-8 Xmit Summary Report: Statistics report of all data transmitted from RadioShack to
Assurant
 New
4.1-8 MPOS: Missed POS. File of sales on merchandise that was eligible for a service plan at
the time of sale but for which no service plan was sold.
 New
4.1-7 Sales Load Errors: File of sales/refunds that Assurant kicked out of their database loads.
 New
4.1-15 MPOS/Renewals: File of MPOS and renewals generated by Assurant. IS THIS
NEEDED????
 New
5.2.2-5 Gift Cards: Full replacement file for PRP from Assurant to SVS.
 New
5.2.2-6 Gift Cards: Full replacement file for PRP from SVS to RS.
 New
4.2-7 Weekly Invoice Status Report: Approved claims from Assurant
 New
5.6-7 Refunds & Cancels: Refunds and cancellations from Assurant
 New
4.3-3 MPOS, Renewals Commissions: Payment for missed point of sale and renewals that were
done by Assurant.
 New
5.4-1 Assurant Website: Customer entitlement for claims
 New
5.2.1-16 Claims Incident#s, Auth#s

 New
Planned Process Decommissions:
 Decommission
Mainframe MIPS Reduction: Small. App is networked based but talks to DB2. Only executes 4
to 5 times a month.
 Decommission
Mainframe MIPS Reduction: Small. App is web-based based but talks to DB2.
 Decommission
Mainframe MIPS Reduction: Medium. CPU - 03:13.7 (3 MINS 13.7 SECS)
 Decommission
Mainframe MIPS Reduction: Medium. CPU - 40.2 SECS
Sales Entry System Admin Unit 010119 Daily Report: Specialty daily report that processes both
phone-in replacement transactions (for equipment covered under an RSSP) and replacements
performed directly by the field via ANSO. The ANSO replacements are harvested nightly during
batch processing of the 010119 daily report and merged with the replacements done via CICS by
010119 personnel.
 Decommission
Mainframe MIPS Reduction: Small. CICS transactions are 800 to 1000 per day. Nightly
processing is light. Approximately 24 SECS CPU could be seen in reduction for nightly
processing. CICS CPU reduction would be approximately 40 SECS per day.
New Business and Renewals, Telemarketing: Monthly processes that produce telemarketing
reports used for RSSP new business and renewal solicitations. Mail solicitation records are
produced but are not currently sent to the third party contracted printer.
 Decommission
Mainframe MIPS Reduction: Medium. CPU - 02:24.9 (2 MINS 24.9 SECS)

Technical Components:
Process to Hardware Relationships (Future System):
RadioShack
Food Mart
Company Store
RadioShack
Network Server
(Visual Basic)
Service Center
PYTHON (Unix)
GLOROCP1
(Unix)
Food Mart
Franchise Store
RadioShack
Assurant
2.0 Franchise RSSP
Price Maintenance
(legacy)
IBM
4.1-3, 5.6-1 Daily Sales/Refunds/
Cancels Xmit
4.2-5 Weekly Claims Xmit, Re-
Xmit2.0 RSSP Retail Price
Control VB App
CSV1000(online)
RSSP Management
RSSP Lookup,
Update, Phone
Logs
2.0 RSSP
Legacy Price
Control(online)
Contract Services Batch
Processes
4.4
Amortization
ICRT System
Tandem
Active
Contracts
Reporting
Begin And End
Date Daily
Validation
Daily Sales
Reporting
Refund
Matching
Status Code
Updating
3.4.2 Srv Ctr Daily
Report (sales,
refunds, ICRTs)
Tandem
3.4.1 Store Daily
Report (sales,
refunds, in-store repl)
Tandem
2.0 RSSP
Retail Price
Control(batch)
IBM
3.4.4 Franchise
RSSP Sales &
Refunds
Parsing
Validation
Journaling
DB2 Load
IBM
?
5.2.1-27 Srv Ctr
Onsite Cust Xmit
2.0 RSSP Legacy
Price Control
(batch)
Tandem
Franchise Opt-
In and Price
Validate
Tandem
GLOROCP1
(Unix)
IBM
5.2.1-17 Repair Status/Event
4.1-15 MPOS/Renewals
???
4.1-7 Sales Load Errors
5.6-7 Refunds & Cancels
4.2-7
Wkly Invc
Stat Rpt
4.2-8 Xmit Summary Rpt
4.3-3 MPOS, Renewals
Commissions
IBM
?
5.4-1 Assurant
Website
IBM
5.2.1-16 Claims
Incident#s, Auth#s
4.1-8 MPOS
?
SVS
5.2.2-5 Gift Cards
IBM
5.2.2-6 Gift Cards
IBM
?
?
5.4 SES 010118 DR
Parsing
Validation
Journaling
DB2 Load
Mainframe
Mainframe
5.4 SES 010118 DR
Mainframe
IBM
?
Mainframe
Franchise Opt-
In and Price
Validate Load
New Process Change Process No Change To Process Unconfirmed Process or Hardware
Tandem
Fax
Franchise Admin

Description:
New Process
Change To Process
No Change To Process
Decommission
Fax
3.4.4 Franchise RSSP Sales & Refunds: Will leverage the current process until the automation of
this piece can be done in a separate project.
 Change to handle dealer net cost
PYTHON (Unix)
2.0 Franchise RSSP Price Maintenance (legacy): Comes from RSSP Legacy price control once
per month. Full base file goes out 3 times per year (every four months).
Network Server
 Decommission
2.0 RSSP Retail Price Control VB App CSV1000: RSSP pricing for retail stores only are
controlled through this Visual Basic program.
 Change to handle display, update, add of dealer net cost.
 Decommission
GLOROCP1 (Unix)
Warranty).
 Change to satisfy 4.2-5 Weekly Claims Xmit, Re-Xmit
RSSP.
 Change to satisfy 4.1-3, 5.6-1 Daily Sales/Refunds/Cancels Xmit
 Decommission
5.2.1-17 Repair Status/Event: Batch process that sends repair status updates to retail stores.

 Change needed so that the current process maps current statuses being sent to the statuses
needed by Assurant.
4.2-8 Xmit Summary Report: Statistics report of all data transmitted from RadioShack to
Assurant
 New
4.1-8 MPOS: Missed POS. File of sales on merchandise that was eligible for a service plan at
the time of sale but for which no service plan was sold.
 New
4.1-7 Sales Load Errors: File of sales/refunds that Assurant kicked out of their database loads.
 New
4.1-15 MPOS/Renewals: File of MPOS and renewals generated by Assurant. IS THIS
NEEDED????
 New
Value Added Network (GSX – Global eXchange Services)
 Decommission
Mainframe – IBM OS/390
All Contract Services Batch Processes run on this machine.
The following entities and their respective subsystems are dependent upon both online and batch
processes on this machine:
Call Center Units 010118, 010119
both phone-in replacement transactions (for equipment covered under an RSSP) and
replacements performed directly by the field via ANSO. The ANSO replacements are
harvested nightly during batch processing of the 010119 daily report and merged with the
replacements done via CICS by 010119 personnel.
 Decommission
RSSP Management

Begin and End Date Daily Validation: For newly sold contracts, this batch process
1) supplies missing begin and end dates for contracts based on the contract length
2) validates equipment information and RSSP pricing
2.0 RSSP Legacy Price Control (online): CICS based system that allows qualified RSSP
personnel to add, change and delete RSSP pricing for those selling points and subsystems
that use this pricing system. Maintenance applied to this system is supposed to kept in
sync with the retail pricing system as well.
Daily Sales Reporting: Batch reporting of all RSSP sales and refunds from all sale points
including unit 010118 (franchise also), retail stores and service centers. Transactions are
harvested from DB2.
4.4 Amortization: Monthly batch reporting that harvests sales and refunds from DB2 in
order to provide journaling reports for all sales and refunds and amortization reports for the
states of NM, ND and MA. The sales and refunds file from this process feeds the Monthly
Sales Xmit(batch) – RS Admin to Assurant subsystem.
 Change to handle requirements section 4.4
Refund Matching: daily batch process that attempts to match RSSP refund transactions to
the original RSSP ticket. If matched, a refund match flag is set on the original ticket and
the control/drop id is set on the refund transaction to that of the original ticket.
ICRT System: Monthly harvest of repairs done for products covered under an RSSP from
repair DB2 tables. Files from this subsystem feed subsystem Monthly Claims Xmit(batch)
to Assurant for the repairs portion.
 Change to daily process
Status Code Updating: Monthly batch process that sets the status code of contracts
according to whether the end date is greater than or less than/equal to the current date.
Active Contracts Reporting: Monthly process that does reporting on all active contracts
within DB2.
New Business and Renewals, Telemarketing: Monthly processes that produce
telemarketing reports used for RSSP new business and renewal solicitations. Mail
solicitation records are produced but are not currently sent to the third party contracted
printer.
 Decommission
Parsing, Validation, Journaling, DB2 Load (as applied to 3.4.4 Franchise RSSP Sales &
Refunds): Processes necessary for placing daily reports into the corporate database.
 Change to handle dealer net cost.
Tandem
Franchise Opt-In and Price Validate Load: Data load to validate RSSP pricing and opt-in status.
 New
Franchise Opt-In and Price Validate: Franchise POS lookup to validate RSSP pricing and opt-in
status.
 New
5.2.1-27 Service Center Onsite Customer Xmit: weekly process that harvests all active onsite
RSSP customers from DB2 that have been assigned to a service center and xmits their contract

information to the assigned service center. Also figures out add, change and delete maintenance
for all customers.
2.0 RSSP Legacy Price Control (batch): daily process that figures add, change and delete
maintenance for RSSP pricing that is used by the service centers.
2.0 RSSP Retail Price Control (batch): daily process that figures add, change and delete
maintenance for RSSP pricing that is used by the retail stores.
3.4.2 Service Center Daily Report (sales, refunds, ICRTs): Xmit of service center RSSP sales,
refunds and ICRTs on their daily report.
3.4.1 Store Daily Report (sales, refunds): Xmit of retail store RSSP sales and refunds on their
daily report.
 Change to handle in-store (partial) replacements
Unconfirmed Hardware/Platforms
5.2.2-5 Gift Cards: Full replacement file for PRP from Assurant to SVS.
 New
5.2.2-6 Gift Cards: Full replacement file for PRP from SVS to RS.
 New
4.2-7 Weekly Invoice Status Report: Approved claims from Assurant
 New
5.6-7 Refunds & Cancels: Refunds and cancellations from Assurant
 New
4.3-3 MPOS, Renewals Commissions: Payment for missed point of sale and renewals that were
done by Assurant.
 New
5.4-1 Assurant Website: Customer entitlement for claims
 New
5.2.1-16 Claims Incident#s, Auth#s
 New
1. General

Assumptions
3.4.4 Franchise RSSP Sales & Refunds: We will leverage existing methods for handling this function
including having the franchise stores fax or email their sales into corporate where they will be input
into admin unit 010118 by corporate staffing (as is being done now). We will apply changes only to
allow for dealer net costing. These dealer net cost changes are considered within scope for Bluebird.
Automating franchise RSSP sales and refunds is considered out of scope and will be handled in a
separate project.
Concerns
Constraints
Notes
Numbers that precede a process description refer to the requirements document and are intended to
map processes to requirements.
The following pertain to the disposition of processes found on illustrated hardware.
1. 5.2.2-6 Gift Cards: it is not known how SVS will xmit this information to Fort Worth.
2. 4.2-7 Wkly Invc Stat Rpt: undetermined as to format or xmit platform
3. The MS-Access database utilized by Wyatt Reece would no longer be utilized for sales and
claims xmit.
4. In-store replacements would no longer be done through ANSO.
5. Servicing of onsite customers will be handled by Assurant.
6. Srv Ctr Onsite Cust Xmit will remain in place as per requirement# 5.2.1-27.
RadioShack Electronic Communications Group: For all processes that post to Unix servers (i.e.
GLOROCP1) for FTP transmissions both to Assurant from RadioShack and from Assurant to
RadioShack, the RadioShack Electronic Communications group will handle both retrieval and posting
of files on Assurant servers. RS Ecom will also handle data encryption for all files traveling to
Assurant from RadioShack and unencryption for all files traveling to RadioShack from Assurant.
Hardware Specifications: No machine specifications will be listed since there will be no hardware
acquisitions or decommissions within the project.
7. Change Log

New
Version #
Changes Effected
Page # Effective
Date Remarks
2.0 Reformatted the paragraph
describing Begin and End Date
Daily Validation so that a stray
line would not be confusing as
to context.
7,15 4-15-05
2.0 Added SVS to the Future
Hardware diagram
9 4-15-05
2.0 Added flow line from
RadioShack Company Store to
Assurant server
9 4-15-05 This indicates Company
Stores will be accessing
Assurant’s website but that
detail is on the subsequent
diagram.
2.0 Added 3.4.4 Franchise RSSP
Sales & Refunds to the
Assumptions section
17 4-15-05
2.0 Standardized Tandem
hardware icons
13 4-15-05
2.0 Changed PYTHON (Unix) icon
to Fax for 3.4.4 Franchise
RSSP Sales and Refunds
13 4-15-05
2.0 Standardized all hardware
icons such that the description
is found below the icon
13 4-15-05
2.0 Changed colorcoding of
uncofirmed processes to light
red from gray.
13 4-15-05
2.0 Changed “Unconfirmed
Process” to “Unconfirmed
Process or Hardware”
13 4-15-05
2.0 Added “Hardware Acquisitions”
and “Mainframe MIPS
Reduction” information
10 4-15-05
2.0 Added flow line from service
center to Assurant website
13 4-15-05
3.0 Changed Franchise RSSP
Price Maintenance to 2.0
Franchise RSSP Price
Maintenance
10 4-22-05
3.0 Changed Amortization to 4.4
Amortization
10 4-22-05
3.0 Changed RSSP Retail Price
Control VB App CSV1000 to
2.0 RSSP Retail Price Control
VB App CSV1000
10 4-22-05

3.0 Changed Sales Entry System
Admin Unit 010118 Daily
Report to 5.4 Sales Entry
System Admin Unit 010118
Daily Report
10 4-22-05
3.0 Changed Store Daily Report
(sales, refunds) to 3.4.1 Store
Daily Report (sales, refunds)
11 4-22-05
3.0 Marked 3.4.2 Srv Ctr Daily
Report (sales, refunds, ICRTs)
as a change process since this
DR will have to xmit auth#
because status refresh requires
auth# on the F3 file.
13 4-26-05
3.0 Added CPU stats onto the
subsystems marked for
decommission
12 4-26-05
3.0 Relocated 2.0 Current System
to the following page.
3 4-29-05
3.0 Added notes pertaining to file
handling with respect to the
RadioShack Electronic
Communications group
18 4-29-05
3.0 Added notes pertaining to
hardware specifications
18 4-29-05
3.0 Changed the “Parsing,
Validation, Journaling, DB2
Load” process box from “No
Change To Process” color
scheme to “Change Process”
color scheme to reflect that
changes will be needed to
handle in-store replacements
from the POS DR.
13 4-29-05

System Architecture v3.0

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (19)

Similar to System Architecture v3.0

Similar to System Architecture v3.0 (20)

More from Jon Fortman

More from Jon Fortman (8)

System Architecture v3.0