system architecture v3.0

System Architecture DocumentProject: Blue Bird

Ver 3.0

PREPARED BY REVIEWED BY APPROVED BY

NAME Jon Fortman

1. John Broom2. Richard Moseley3. Lynese Sanders4. Rogena Baston5. Joe Mendoza6. Donny Faries7. Bobby Crabb

Donny Faries

ROLE Tech Lead

1. Tech Lead Mentor2. Developer3. Analyst4. Analyst5. Developer6. Application Architect7. Project Manager

Application Architect

SIGNATURE

DATE 21 February 2005 21 April 2005 6 May 2005

Approved and Issued by: Project OfficeTemplate Version: 1.2

Template Revised: August 20, 2003

Blue Bird System Architecture Document

TABLE OF CONTENTS1. KEY INDIVIDUALS INVOLVED....................................................................................................................... 4

BUSINESS PROJECT SPONSOR................................................................................................................................ 4

RSTS PROJECT SPONSOR..................................................................................................................................... 4

PROJECT MANAGER............................................................................................................................................... 4

2. CURRENT SYSTEM........................................................................................................................................ 5CURRENT HARDWARE DIAGRAMS AND MODELS.......................................................................................................5

CURRENT TECHNICAL ENVIRONMENT NOTES...........................................................................................................5

Technical Component: All.................................................................................................................... 5

3. FUTURE SYSTEM......................................................................................................................................... 10FUTURE HARDWARE DIAGRAMS AND MODELS........................................................................................................10

FUTURE TECHNICAL ENVIRONMENT NOTES............................................................................................................11

Technical Component: All..................................................................................................................14

8. GENERAL...................................................................................................................................................... 18ASSUMPTIONS...................................................................................................................................................... 18

CONCERNS.......................................................................................................................................................... 19

CONSTRAINTS...................................................................................................................................................... 19

NOTES................................................................................................................................................................. 19

9. CHANGE LOG............................................................................................................................................... 19

1. Key Individuals Involved

Business Project SponsorJulie Buckley, Director New Business Development

Susie Moore, Manager Service Plans

RSTS Project SponsorSam Whitling - Sr. Director EDM, RSTS

Project ManagerBobby Crabb – Project Manager

of 21 Last Update Date: 10/23/2015 3:19:00 PM

/tt/file_convert/58a500d41a28abce778b62af/document.docxLast Saved By: Forest Willis


2. Current System

Current Hardware Diagrams and Models

Current Technical Environment Notes

Technical Components




Process To Hardware Relationships (Current System):




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.

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.

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

RSSP Lookup, Update, Phone Logs: CICS based system that allows display and update of 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




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.

Monthly Claims Xmit(batch): Batch job that FTPs claims against RSSPs to Assurant(Federal Warranty). Change to satisfy 4.2-5 Weekly Claims Xmit, Re-Xmit

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. 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 transactions not done by the field (RSS). Includes RSSP giveaways, franchise sales and refunds, phone-in RSSP sales and refunds. Change to accommodate dealer net cost

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. Change to display svp sku id, svp catg id, dealer net cost

RSSP Lookup, Update, Phone Logs: CICS based system that allows display and update of RSSPs. Viewable and updateable by all RSSP management. 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:

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. Decommission Mainframe MIPS Reduction: Small. App is networked based but talks to DB2. Only executes 4 to 5 times a month.

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. Decommission Mainframe MIPS Reduction: Small. App is web-based based but talks to DB2.

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. Decommission Mainframe MIPS Reduction: Medium. CPU - 03:13.7 (3 MINS 13.7 SECS)

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. 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. DecommissionMainframe 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):




Description:

New ProcessChange To ProcessNo Change To ProcessDecommission

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). Change to accommodate dealer net cost

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. 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.

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. Decommission

GLOROCP1 (Unix)

Monthly Claims Xmit(batch): Batch job that FTPs claims against RSSPs to Assurant(Federal Warranty). Change to satisfy 4.2-5 Weekly Claims Xmit, Re-Xmit

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. Change to satisfy 4.1-3, 5.6-1 Daily Sales/Refunds/Cancels Xmit

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. 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)

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. 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

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. Change to accommodate dealer net cost

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

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. Change to display svp sku id, svp catg id, dealer net cost

RSSP Management

RSSP Lookup, Update, Phone Logs: CICS based system that allows display and update of RSSPs. Viewable and updateable by all RSSP management. Change to display svp sku id, svp catg id, dealer net cost




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

NotesNumbers 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

10 4-22-05




Daily Report

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

Documents