ArcSight RepSM Evaluation Process

Summary:

The HP ArcSight Reputation Security Monitor (RepSM) evaluation license process is detailed, requiring approval from the regional SW GRRO team for external customers over 90 days and directing internal inquiries to a specific HP Connections page. External requests must go through their sales representative for a license key. Key information required includes use case, product number, and contact details. For extension license requests, details of the initial evaluation are necessary. The document also outlines using Sales Force.com ID exclusively for external customer requests, with strict guidelines for licensing fulfillment team handling split or transfer orders to avoid multiple quantities in single order entries. Allowed characters include alphanumeric values only, excluding special characters like underscores.

Details:

The document outlines a process for evaluating the HP ArcSight Reputation Security Monitor (RepSM) product, intended for both internal and external use. It specifies that the software should only be used on an evaluation basis and downloaded from specific sources based on whether the customer is internal or external to HP. External customers must contact their sales representative to request a license key, while internal inquiries are directed to a particular HP Connections page. For external customers requesting an evaluation license for more than 90 days, approval from the regional SW GRRO team (Global Revenue Recognition Organization) is required before submitting the request to licensing support. The document also lists essential information needed when making such requests, including specifying use case, product number, and contact details. For extension license requests specifically for external customers, additional details about the initial evaluation license are necessary. The document outlines specific instructions for handling external customer requests and managing sales force processes on the platform called "Sales Force.com." Here's a summary of key points: 1. **Use of ID**: There is a unique identifier known as Sales Force.com ID, which should be used exclusively for submitting external customer requests. This helps in tracking and organizing such requests efficiently. 2. **Special Note for Licensing Fulfillment Ops Team**: The team responsible for handling licensing fulfillment must follow strict guidelines when creating split or transfer orders from master EONs:

• Each order transferred should contain only one product quantity per order. This ensures clarity in the transaction and prevents any confusion with multiple quantities of a single product being bundled together.

3. **Creation of EON**: When setting up an EON (which seems to be a part of this system), only alphanumeric values are allowed; special characters like underscores ("_") should not be used. This rule ensures that the identifiers in the system remain clean and consistent, which is crucial for accurate data management within the platform. 4. **Revision History**: The document mentions revision history, implying that these instructions might have been updated recently or are subject to changes. Users must refer to the latest version of this guide when performing tasks related to external customer requests on Sales Force.com. In summary, the document is a procedural guideline for how to handle and interact with specific features within the platform for external customers and internal operations teams regarding licensing fulfillment and order management. It emphasizes simplicity in data entry through clear instructions about which characters are allowed when creating unique identifiers or entering orders.

Disclaimer:

The content in this post is for informational and educational purposes only. It may reference technologies, configurations, or products that are outdated or no longer supported. If there are any comments or feedback, kindly leave a message and will be responded.