PIR Part 1 - Version 2.0

Allstate Project Initiation Form- Part 1

Project Name: / Transaction Systems Intertest ver 7.0 Installation
Requested by: / Phyllis Shao
PMO Contact (Submitted by) / Gregg Davison
Department: / ESI/Transaction Systems
Funding Business Unit:
Project Sponsor / Owner / Conway Norwood
Technical Planner / Marco Chou
Desired Start Date: / October 10, 2005
Desired Completion Date: / November 4, 2005
Estimated Project Cost (CRE only, if only your area is known, please indicate)

Project Permit Type:

Permit to PlanPermit to Build

Project Information

Project Description

Concept / Narrative:

Describe the business need or business issue that initiated the need for this request

(Free Form Text Field) z/OS ver. 1.6 will be implemented Enterprise wide on the mainframe by the EMSM team. Transaction Systems owns Intertest software(Applications CICS testing and debugging tool) support, and per the vendor CA, the current version installed at Allstate ver. 6.3 is not compatibile with z/OS 1.6. Version 7.0 of Intertest is required for compatibility with z/OS 1.6.

Objective:

Provide a comprehensive definition of the work to be done and your business unit’s strategic initiative this request aligns to

(Free Form Text Field) The following areas along with TransactionSystems will be involved in the planning and rollout:
EMSM
Application Area testing
ETS, symbolic file support
Client Managers
DCO (Possibility)
Detail work effort will include SMPE deployment, and application testing/communication.

Scope:

Describe what is included within the project objective, including location, number of users or organization impacted

(Free Form Text Field) The project will encompass all areas of Allstate. Purpose is to effectively rollout Intertest ver. 7.0 to Allstate Enterprise. Intertest exist in all of the datacenters, Hudson, Dallas, Northbrook and Oakbrook.

Deliverables:

Describe or list the major deliverables, which the project will produce

(Free Form Text Field) Deliverables from the project will be the successful implementation of Intertest ver 7.0 to all Test and Production CICS Regions. Total number of known CICS regions is approximatley 375.
Transaction Systems Intertest Implementation Strategy:
- Install in Sandbox Cics Online (CICSMA0H) and test
- Install in 1 Test MSYS CICS Online and test (Control versioning by concatenation)
- Rollout to remaining Test MSYS Onlines and test
- Rollout to remaining Test systems and test (ESYS, ASYS, BSYS, JSYS)
-Rollout to Pre-Pro and test
- Rollout to Production

Project Impact Analysis

Economic:

Summarize the economic impact the project will have including benefits (tangible or intangible) of completion or impact if request is not implemented

(Free Form Text Field) As part of our SLA to our customers we always rollout the latest version of Intertest in a timely manner. Also, we assure compatibility with other software products. Additionally, there are some needed bug fixes that are also a part of this version.

Organization:

Summarize the impact the project will have on the Organization. Include factors, which affect organizational structure, performance or customer satisfaction

(Free Form Text Field) Allstate Enterprise CICS Applications stabilitywill increase with the ability to test applications with the enhancements of the rollout of this version of Intertest. This release includes enhancements and bug fixes. Also this implementation is a pro-active approach to ensure compatibility with the z/OS 1.6 upgrade.

Process Change:

Summarize the impact the project will have on the current process

(Free Form Text Field) This Project will not impact the Transaction Systems Intertest installation process and will be transparent to end users.

Assumptions:

Additional Assumptions and Prerequisites:

Describe additional considerations, which have an effect on the project, including sponsor/client and team expectations. The expectations should address but not be limited to scope related matters, quality related matters, timeframe matters, resource related matters, organization and communication matters, economic and financial matters, risk-related matters, and business arrangements and contract matters.

(Free Form Text Field) The implementation of Intertest ver 7.0 is a pro-active approach to ensure compatibility with the z/OS 1.6 upgrade. The implementation is also a prerequisite for the z/OS 1.6 upgrade.

Identify Risks and Dependencies

State the risks (or potential risks) that are identified with providing a solution of this type, and describe the critical dependencies that are required for successful execution of the project (The identification of these risks and critical dependencies will also be crucial for post-pilot implementation of an Allstate initiative.)

(Free Form Text Field) Risks include the following:
1) Not rolling out Intertest ver. 7.0will cause incompatibility with the installation of z/OS 1.6 and provide exposure to code defects in Interest ver 6.3.

Resource Requirements (if known or predetermined)

Skill set dependency – special requirement, contractor, vendor, or SME dependence

Specific technology requirement – (Hardware or Software)

(Free Form Text Field) Transaction Systems - 2 resources,
ETS - symbolic file support
Application Areas - Application communication and testing
Client Managers
Potentially:
Assistance from Datacenter staff ( DCO).

Security Requirements:

Security – Will this application and/or business process use information that would be considered restricted, confidential or public? Please explain below.

(Free Form Text Field) Intertest has a component that allows access to read/update/delete Application file data.To mitigatethis risk Intertest is installed in the production environment in a dormant state and the transaction that enables "File" access is secured via AIS. Additionally, there is a process that was initiated a couple of releases back that requires the DCO to enable Intertest for users and monitor and track their usage. This process is audited by the Auditors..

Security – Will this information be accessed or stored outside the Allstate network? Please explain below.

(Free Form Text Field) N/A

Security - Is this application/business process considered critical to Allstate’s core business. Please indicate High, Medium or Low and briefly explain below.

(Free Form Text Field) The Intertest application is not commonly used in the Production environment and because of the aforementioned process in Security Requirements #1 it is rated Low.

Completion Criteria

Deliverables

What needs to be done? How will it be measured in the most objective terms? How will we know when we’re finished? The objective is to eliminate subjective analysis after the completion of the project

(Free Form Text Field) Measurement of success will be the completion of implementing Intertest ver. 7.0 to approximately 375 CICS regions.Implementation will be defect free and have no negative impact on the end user.

Version 2.0 Page 1 of 5