Skip Headers

Oracle® Collaboration Suite On Demand Reference Guide
Release 2.0
Part No. B12301-01
  Go To Table Of Contents
Contents

Previous
Previous
Next
Next
 

C Production Assessment

To confirm that the Customer implementation is ready for transition to production, Oracle On Demand will take the Customer's environment through a Production Assessment (PA) testing methodology. The PA consists of a series of functional, configuration, supportability, and performance tests. Through this testing, Oracle may identify and fix key issues that may have a negative impact on the system during transition to production or on performance once in production. During the production assessment, a number of required actions and recommended actions may be identified. Oracle requires the completion of the Production Assessment, and the completion of all required actions that have been identified before a system may become production.

The primary purpose of production assessments is to confirm that Customers' systems environments are compliant with Oracle On Demand standards prior to commencing production operations (or Ògoing liveÓ). Standards compliance is the foundation of the Oracle operations strategy for delivering consistent service levels to On Demand Customers. Consequently, the production assessment process is rigorously enforced for all On Demand Customers.

The Production Assessments (PA) process begins at the On Demand Kickoff meeting organized shortly after the signing of the On Demand services contract. The importance of a successful PA is emphasized and an outline of the PA process is presented to the Customer at this time. The PA process consists of the Customer's agreement that production operations should only commence after On Demand designates the Customer's project to be Production Ready (PR). The Service Delivery Manager (SDM) will communicate Production Ready (PR) status to the Customer in writing through the Production Assessment Status Report. If the Customer commences production operations prior to having a PR status, then On Demand service levels may not be achievable. This message is reinforced during Systems Engineering Management Plan (SEMP) Milestone meetings by the SDM as the Customer's systems environment progressively passes a number of assessments to achieve ÒProduction ReadyÓ status.

Production Assessments consist of a number of tests designed to validate standards compliance in the areas of systems configuration, functionality, performance, and supportability. Each compliance area is covered by one or more tests. Each test consists of a number of test items. Common tests that apply to all Customers are grouped together and referred to as a basic package of PA tests. Specialized tests that apply to only certain Customers or Customer profiles are collectively referred to as the enhanced package of PA tests.

This appendix covers the following topics:

Production Assessment Process Outline

  1. Production Assessment occurs throughout the LifeCycle of each Customer project. It is important that the Customer and Implementor are apprised of their roles and responsibilities for Production Assessment testing.

    • Review Production Assessment checklist with an overview of roles and responsibilities for each checklist with the Customer and Implementor.

    • Production Assessment checklists that require Implementor actions:

      • Network Connectivity Tool

      • UAT

      • Operations Implementation (SDM will coordinate environment downtime to complete the checklist)

      • Business Continuity

  2. Maintain data that will be required for the Production Assessment process to be executed:

    • Service Offering(s) purchased

    • At least one project should be created for each Service Offering. If multi-phased, a separate project will apply to each phase.

    • Go-live date for each project must be maintained and accurate at all times.

    • Implemented products for each project

    • Environment details for each project

  3. Production Assessment checklists will be scheduled automatically based upon the Customer implementation type, modules implemented, Service Offering, and the anticipated Go-live date. Customers are initially given a Not Production Ready (NPR) status when the entry is created.

  4. Three weeks before the Go-live, Customer and Implementor should complete and freeze all code changes to allow final Production Assessment testing to begin. The Customer and Implementor should have all required documents submitted to the Production Assessment team via their SDM. The required documents are:

    • User Acceptance Test (UAT): This is a test and verification of the Customer's Critical Business Functions (CBF). The Customer and Implementor will test CBF and provide test results with their plan to fix any problems that are discovered.

      • A UAT Example is available from the Customer's SDM as a reference for what Oracle expects from the Customer or Implementor for UAT. The required data for a UAT consists of the following:

        - What is tested?

        - Who tested it? (First and last name)

        - When was it tested?

        - What were the results? If the results failed, how were they resolved?

        - Logical sequence of tests-tests follow a logical order.

        - Network Connectivity Tool output file

        - OSA 10 and OSA90 Forms

        - Business Continuity

Tests

The current list of PA tests is provided in Table C-1. Test items are changed on an on-going basis. Entirely new tests may be added or current tests removed from the list. Change management is implemented by assigning a test package version number for the PA tests in effect. Details on any test package version are available from the Customer's Service Deliver Manager (SDM).

Table C-1 Production Assessments Tests

Test Group Objective Representative Tests
Configuration and Supportability Basic: Validate key configuration parameters in the operating system, technology stack, support infrastructure and network against predefined values. Server and storage, network implementation, RAC, Stabilization Business Continuity
Functionality Basic: Verify basic functionality of the major system components (for example, network) through tests and test plan reviews Network Connectivity Tool

Enhanced: Validate functionality of major system components using methods which may require Customer/implementor interaction. UAT review
Performance Basic: Quantify baseline system performance with no user induced load. System monitoring

The PA testing status of a Customer project with respect to production readiness is always one of the following:

A Customer's project's PA status normally progresses from NPR to PR. The Production Assessment team maintains an active PA status report outlining the status of a Customer's PA tests. Customers may request this report from their SDM at any time. "Production Assessment Status Report" contains an example of the status report.

Test Results

Testing status will be one of the following in the PA status report:

Indicated actions will be assigned to Oracle On Demand or the Customer/Implementor or both, as appropriate. The assigned representative is responsible for taking action on all required and recommended actions. Test results are collected, aggregated, and reported. The Production Assessment team tracks the resolutions.

Corrective Actions

There are two types of error resolution:

Table C-2 shows the groups responsible for tracking the resolution and the required resolution times.

Table C-2 Resolution Responsibilities

Action Type Implementor / Customer Interaction Required? Tracking Responsibility Resolution Objective
Required Actions from Checklists (UAT, Network Connectivity Tool, Business Continuity) Yes SDM All actions must be resolved before Go-live
Required actions from checklists (Networking, Server and Storage, Implementation, RAC, Stabilization) No SDM All actions must be resolved before Go-live
Recommended actions from checklists (Networking, Server and Storage, Implementation, RAC, Stabilization) No SDM All actions should be resolved before Go-live. Unresolved items will be addressed via the PMP process.

Documents

Table C-3 lists the required documentation for Collaboration Suite On Demand Production Assessment test. Each environment requires one set of Production Assessment test documents.

Table C-3 Required Production Assessment Test Documentation

Deliverables Collaboration Suite On Demand
OSA10 and OSA90 Forms Yes
UAT (Details, results, who did it, when it was done, who owns the responsibility for the outcomes) Yes
Network Connectivity Worksheet Yes
Business Continuity Yes

Contact the Customer's SDM for copies of these documents.

Pre-Production Backups

All requests for baseline backups prior to the Go-live date should be established at this time. The Customer should decide what needs to be backed up in case a restore is needed. This will provide the Customer with a stable system before the Go-live date.

Support Training and Post Go-Live Requirements

Within the first 30 days of the Go-live date, or first month-end close, the Customer's environment will be tracked for any critical issues such as severity 1 service requests and bugs.

The Implementor is required to be available throughout this time, and should be a reference contact for Oracle On Demand Support. The Implementor confirms that the Customer has adequate knowledge and training to work with Oracle On Demand. In particular, the Implementor confirms that the Customer has complete knowledge and information on:

Service Models

Production Assessment will apply to the Oracle Collaboration Suite On Demand service offerings for the @Oracle and @Customer service models.

Figure C-1 is an example of a Production Assessment Customer status report.

Figure C-1 Production Assessment Status Report

A customer project’s project readiness status normally progresses from NPR to PPR, then to PR. The Production Assessment team issues a Production Assessment Status Report approximately one week before Go-live outlining the status of a customer’s PA tests.