This chapter contains information about the systems assurance process.
The system assurance process is the exchange of information among team members to ensure that no aspects of the sale, order, installation and implementation for the Oracle Key Manager are overlooked. This process promotes an error-free installation and contributes to the overall customer satisfaction.
The system assurance team members (customer and Oracle/StorageTek representatives) ensure that all aspects of the process are planned carefully and performed efficiently. This process begins when the customer accepts the sales proposal. At this time, a representative schedules the system assurance planning meetings.
The purpose of the system assurance planning meetings is to:
Introduce the customer to Oracle's encryption products
Explain the system assurance process and establish the team
Identify and define the customer requirements
Identify any additional items needed (such as cables, tokens, and switches)
Prepare for the installation and implementation
Schedule and track the entire process
Table 2-1 System Assurance Task Checklist
Task | Completed? |
---|---|
Introduce the team members to the customer. Complete the Team Member Contact sheets. Make copies as necessary. |
Yes__ No__ |
Explain the encryption solutions to the customer. See Chapter 1, "Introduction" for topics and information. |
Yes__ No__ |
Use Chapter 2, "Systems Assurance" to help define the customer requirements. |
Yes__ No__ |
Complete the Team Member Contact sheets. |
Yes__ No__ |
Review and complete Chapter 3, "Site Preparation". Comments: |
Yes__ No__ |
Review and identify "User Roles Work Sheet". Comments: |
Yes__ No__ |
Review Chapter 4, "Components". Comments: |
Yes__ No__ |
Review "Supported Configurations". Comments: |
Yes__ No__ |
Determine the installation schedule: Date: Time: |
Yes__ No__ |
Download and provide the customer with a copy of the Administration Guide PN E41579-01. Virtual Operator Panel—Customer PN: 96179 http://download.oracle.com/docs/cd/E24472_01/index.html |
Yes__ No__ |
Complete the following information for the customer team members:
Name: | |
Title: | |
Telephone Number: | |
FAX Number: | |
Cell Phone / Pager: | |
E-mail Address: |
Name: | |
Title: | |
Telephone Number: | |
FAX Number: | |
Cell Phone / Pager: | |
E-mail Address: |
Name: | |
Title: | |
Telephone Number: | |
FAX Number: | |
Cell Phone / Pager: | |
E-mail Address: |
Name: | |
Title: | |
Telephone Number: | |
FAX Number: | |
Cell Phone / Pager: | |
E-mail Address: |
Note: Customer representatives may include: security officers, finance managers, IT managers, network administrators, systems administrators, site planning managers, and anyone else involved in installations. |
Complete the following information for the Oracle team members:
Name: | |
Title: | |
Telephone Number: | |
FAX Number: | |
Cell Phone / Pager: | |
E-mail Address: |
Name: | |
Title: | |
Telephone Number: | |
FAX Number: | |
Cell Phone / Pager: | |
E-mail Address: |
Name: | |
Title: | |
Telephone Number: | |
FAX Number: | |
Cell Phone / Pager: | |
E-mail Address: |
Name: | |
Title: | |
Telephone Number: | |
FAX Number: | |
Cell Phone / Pager: | |
E-mail Address: |
Note: Representatives may include: marketing, sales, and account representative, systems engineers (SEs), Professional Services (PS), installation coordinators, and trained services personnel. |
Complete the following checklist and make a conceptual drawing to help with the installation. Provide this information and drawing to the installers.
Use this checklist for each Key Manager the customer is considering. This checklist is geared towards planning a single Oracle Key Manager system, with up to 20 OKMs.
Table 2-2 Solution Planning Checklist
Question | Selection / Comments | Quantity |
---|---|---|
What type of configuration does the customer want? Notes: The maximum number of sites with KMAs is 20. It is possible to have sites without KMAs connected across a customer supplied wide area network. Also, the 20 site limit is within a single cluster. The customer may choose to have multiple clusters; however, KMAs in one clusters are unaware of KMAs in other clusters. |
__Single site __Multiple sites __Disaster recovery site |
How many:
|
How many appliances (KMAs) are needed? The maximum number of KMAs is 20. The minimum OKM size is 2*. The recommendation is at least 2 (assuming sites are geographically dispersed) * The exception to this standard configuration (single-node site) must be made with the approval of Encryption Engineering, Professional Services, and Support Services. |
How many: |
|
What type of encryption hardware kits are needed? How many encryption hardware kits are needed? |
__SL8500 __SL3000 __SL500 __SL150 __9310/9741E __L-Series __Rackmount |
How many:
|
How many and of what type of encryption-capable tape drives are needed? |
__T10000A __T10000B __T10000C __T10000D __T9840D __HP LTO 4, 5, or 6 __IBM LTO 4 or 5 |
How many:
|
Are external (standalone) Racks required? Type? |
__Yes __No |
How many: |
Identify customer requirements and expectations. |
The following pages provide space to help sketch a drawing of the configuration.