Common use of System Development Clause in Contracts

System Development. As an outcome from the General Discovery phase and GECF-A Discovery, First Data will identify general system differences, which will require systems development on the First Data System. First Data will identify final specific differences for RCSI’s approval within each Wave that may require systems development on the First Data System. With respect to differences that require systems development, First Data will: • Write programming requests for all First Data System changes identified during GECF-A Discovery and outlined in the Resolution Agreements. • Design First Data System enhancements and write detailed documents describing the specific First Data System changes. • Quality inspects designs by the requester as well as members of the Systems and Programming organization. • Provide detail designs to RCSI for review and approval. • Code and construct the First Data System changes, including individual unit and system testing of the programs that are changed. • Merge the new code with production code into an integration testing environment, which is executed by First Data development and testing staff to identify specific coding errors. • Move all applicable programs into the Client Acceptance Test environment where the new functionality can be tested in a production-like system by RCSI and First Data. • Install completed programs into production according to the standard release schedule. First Data will: • Receive and analyze the RCSI system masterfiles. • Prepare a mapping specifications document, which details how fields are mapped from the RCSI masterfiles to First Data masterfiles. • Review mapping specifications with the RCSI. Table of Contents • Code the Conversion programs from the mapping specifications. The Conversion programs create new First Data System masterfiles. • Test the Conversion programs using a series of “Mock” Conversions. First Data will receive the production masterfiles from RCSI and run them through the Conversion programs to create output reports showing each masterfile field and value. First Data will verify the information against the mapping specifications. • Execute the Conversion programs on conversion weekend and merge the new masterfiles into production. First Data or RCSI, in accordance with the Discovery Plan, will: • Establish RCSI defined parameters on the Product Control File and fully document deviations from the RCSI standard template for each portfolio. • Create Account Level Processing/Transaction Level Processing strategies. • Build Portfolio Allocation and Cardholder Allocation tables to drive pricing strategies. • Create statement forms and envelopes. • Order plastics, card carrier forms, inserts and envelopes. • Set reporting parameters and fully document deviations from the RCSI standard template for each portfolio. • Build cardholder letters. • Establish Behavior Score/Adaptive Control parameter tables. First Data or RCSI, in accordance with the Discovery Plan, will: • Analyze current terminal and network configuration. • Design telecommunication network for terminals, point of sale devices and interfaces. • Order and install data lines and communication equipment. • Complete programming to route data files to/from First Data System. • Establish procedures for mailed tape media. Table of Contents The Conversion training plan consists of four (4) phases that First Data or RCSI, in accordance with the Discovery Plan, will perform as part of each Conversion Wave: needs assessment, train the trainer, staff level training, and follow up as described in Schedule A, Section 16. In order for the training portion of the Conversion to be successful, the following must occur: • The Parties’ commitment and support. • Dedicated resources from First Data and RCSI • Appropriate time for planning and execution • Open communication between the Parties to facilitate a positive experience • Time allocated for employee training and follow-up • Instill the business Partnership between First Data and RCSI • Timely escalation of issues Testing consists of First Data’s planning and coordination of all software development, Conversion programs, interfaces and product control file parameters. First Data will perform software development testing, including having new software to pass through three (3) phases of internal testing before the software is turned over to RCSI for user acceptance testing. First Data Systems and Programming (“S&P”) is responsible for testing in first three (3) phases. It is in the user acceptance testing phase that RCSI will have the opportunity to use the First Data System and become involved in the various testing scenarios. RCSI may at its discretion participate in the scripting and execution of any phase of testing. First Data will perform the three (3) testing phases, and facilitate client/user acceptance testing described below. Unit Testing-This phase of testing is conducted by First Data’s S&P staff. The testing is done at the most basic level. The unit test ensures that all modified or new logic paths in the affected applications modules work correctly and reflect the final design requirements. The test includes known inputs, test case scripts, and expected results. System Test-This phase of testing is also conducted by the First Data S&P staff. The testing is now expanded to include all modules that have been modified for a given project (usually a sub-system). The modules are tested together to validate that code changes meet design requirements and that the various components of the altered system function together properly. The system test consists of both acceptance and regression testing. Modules that send, receive, and share data with the modified modules are used to test changes and to regression test the legacy functionality. First Data will share the results with RCSI. Table of Contents Integration Test-The integration test conducted by the First Data S&P staff incorporates all software and database modifications from a specific software release into one (1) testing environment. Multiple daily cycles will be executed as well as weekly and monthly cycles. The testing ensures that projects execute as intended and do not introduce any unanticipated problems. Changes are tested across and between applications as well. Client/User Acceptance Testing- (M Cycle) Upon the completion of the three (3) internal First Data test phases described above, the software release is installed in the user acceptance test cycle. The M cycle is a daily production cycle which is run by First Data’s production control department. Performance and stress tests are performed by extrapolating results from this Client/User Acceptance Test. RCSI Testing – RCSI will prepare timelines and test plans for all internal and external requirements, including any data or resource requirements from First Data. M cycle is available for RCSI to test a production cycle against RCSI converted data, input and output along with any system development relating to the Initial Conversions. In addition, specific requests for testing will be addressed as received from RCSI which may require Team 9P involvement. RCSI will need to identify a champion to coordinate testing required by RCSI. RCSI will have on-line access to the M cycle and have the ability to send inputs to and receive outputs from the M cycle. RCSI will prepare and execute test scripts to ensure that custom program requests function as intended. Conversion Testing-First Data will prepare specifications for each file which will be Converted. First Data will review the specifications with RCSI and schedule several First Data internal mocks and several RCSI mocks. During mock testing, First Data will review with RCSI old and new dumps of the files to ensure information has mapped properly. First Data will run balance reports and any additional verification reports requested by RCSI during the mocks. For the mock testing it will be important that RCSI representatives be onsite in Omaha. That way, they will have access to First Data experts and have the ability to review reruns and reports timely. Product Control File- (PCS/ALP/TLP/TLR) First Data will build tables in production and M cycles. First data will train and assist RCSI in building its PCF tables. First Data and RCSI will verify each field before and after it is built. In addition, First Data will hold PCF/TLP/TLR reviews to ensure parameters are set correctly. After verification, First Data will build parameters in M cycle as well as production. RCSI will be able to test all inputs and output, screens, etc., using the parameters which will be in place at conversion. Using M cycle and the 9P environment, First Data and RCSI will verify that all parameters are mirrored correctly from M to production. Conversion weekend is the culmination of all the previous phases. First Data will adequately prepare RCSI using the mock Conversions RCSI for file verification on conversion weekend. The process starts with RCSI delivering masterfiles to First Data. This can be accommodated via transmission or delivering of physical tapes. First Data will run these files through the Conversion programs and product audit reports for approval. Both RCSI and First Data will verify the results. First Data will balance the total number of accounts and current outstandings to the ▇▇▇▇▇. First Data will review all exception reports. Once the Conversion results are signed off by RCSI, the First Data will merge the RCSI masterfile records into the masterfile records of the First Data System. Table of Contents First Data will establish procedures for lost/stolen account processing during the Conversion weekend, for RCSI’s approval. At the end of the implementation phase, RCSI should feel confident that masterfile integrity remained the same from the last day of processing on the RCSI system to the first day of processing on the First Data System. RCSI will need to have staff on-site in Omaha the weekend of each Conversion Wave. It will also need to put together their own plan identifying the new processes, sequence of events, command center personnel, etc.