Integrated TDA tab (integrated workflow with IMPACT Pre-sale TDA package for supported products)
|
Notes:
▪If you open the Integrated TDA tab before configuring a COS system, you see only the Cover Sheet and COS Requirements options.
▪When you access this tab, you see the Cover Sheet sub-tab . In a IBM COS project, you also see a sub-tab.
▪You can click any of the following links to learn about the other tabs in this view:
|
The Integrated TDA tab integrates seamlessly with IMPACT. The data entered into this section is stored in the IMPACT database. IMPACT compares the customer requirements in this section to
your technical design and determines whether you are meeting your customer’s requirements. This view opens to the Cover Sheet tab. The first time that you enter this view, a Terms and
Conditions page is displayed for you to read and agree to.
Cover Sheet for a project
Only IBM COS systems include a Cover Sheet in Storage Modeller.
The Cover Sheet tab allows you to provide general information about the customer opportunity for your project. Your project design can continue even if initially you must give tentative
answers to cover-sheet questions.
When you enter this section for the first time, you must agree to the terms and conditions.
Figure 62
shows the Cover Sheet for the
CapacityCalc project.
Figure 62 Cover Sheet expandable fields
The following three sections present a total of ten questions to guide your collaborators in the review and approval process:
▪General:
– 1. Customer Name (mandatory field, marked with a red asterisk)
– 2. Customer Opportunity Name (mandatory field, marked with a red asterisk)
– 3. Sales Connect Opportunity ID (mandatory field, marked with a red asterisk)
– 4. Describe your Data Type: (drop-down menu)
• Object Only (default)
• Object and File (NFS/SMB)
• File Only
▪Data:
– 5. Is immutability required (Write Once Read Many/NENR)? (Yes or
No)
▪Requirements:
– 6. High Level Business Requirements
• Description (100 characters minimum)
• Budget, radio buttons for
Yes, Opportunity has Funding
or No Funding.
• Solution Budget (a value between 0 to 100000000000)
• Currency code (ISO 4217)
– 7. High Level Technical Requirements
• Description (100 characters minimum)
• Use radio buttons to specify three Yes/No answers:
i. Yes, Opportunity requires future feature functionality. (In other
words, the opportunity requires new, unannounced features from IBM.) OR
No future feature functionality.
ii. Yes, Opportunity requires future capacity expansion. OR
No future capacity expansion.
iii. Yes, Opportunity requires inclusion of rack hardware in Bill of Materials (BOM). OR
No rack hardware required.
(In other words, the customer provides racking.)
– 8. Assumptions
• Description (100 characters minimum)
Instructions: Describe and cite documentation that is not
directly requested in other FOS Engine fields. When referencing documentation, be sure to use official customer facing or Product Offering Management sources.
– 9. What is the primary use for Cloud Object Storage?
– 10. What are the regulatory compliance requirements?
– 11 (Overall question):
This question reveals the priorities for four dimensions of system design:
11.
Assign weight from 1 to 4, with 4 being the most important and 1 being least important.
(You use a slider control to specify weights for these 4 dimensions: Performance;
Expandability; Reliability / Disaster Recovery / Durability; and Price per TB.)
COS requirements
For an IBM COS system, a
COS Requirements sub-tab is in the Requirements tab of the List tab. The COS Requirements sub-tab contains
technical questions about the COS.
When you enter this section for the first time, you must agree to the terms and conditions.
The COS Requirements tab contains two sections:
▪Requirements. Define requirements for the following aspects:
– Number of data centers
– Mirror requirements
– Weighting Performance, Expandability, and Reliability
– Capacity Requirements
– Storage Growth Rates
– Performance Requirements
– Reliability Factors
▪Attachments:
Allows you to upload customer-supplied design requirements to the IMPACT database.
Figure 63
displays a partial view of the Requirements and Attachments sections.
Figure 63 COS Requirements section