Finding Proof of Concept Scoping Guides for ROCK

Summary:

The document outlines updates and provides scoping guides for various products such as Express PoC, Logger, and a Connector for RepSM Model Import. It includes five scoping guides available in ZIP files attached to Steven Maxwell's blog post dated October 19, 2010. These guides are specific to HP_ArcSight, including forms for both Express PoC and Logger, as well as a document on Evaluating RepSM. Updates include adding RepSM to ESM scoping guides and updating supported platforms based on new product releases. In May 2012, updates were made to AppSM and the Connector Appliance, expanding content on the public web site and modifying success criteria for AppSM. Additionally, there was a scoping guide titled "IV_ScopingChecklist.doc" for IdentityView v1.1, providing instructions on customizing the document for different customer use cases.

Details:

The provided text discusses finding proof of concept (PoC) scoping guides for various products such as Express PoC, Logger, and a Connector for RepSM Model Import. It mentions that there are five scoping guides available in ZIP files attached to Steven Maxwell's blog post dated October 19, 2010. These guides include "HP_ArcSight_PoC_Request_Form_Express.docx" (for Express PoC including Logger) and "HP_ArcSight_PoC_Request_Form_Logger.docx" (specific to Logger). Additionally, a document on Evaluating RepSM is available through HP Connections for downloading software and requesting an evaluation license for the RepSM Model Import Connector. Updates include adding RepSM to ESM scoping guides and updating "Supported Platforms" based on new product releases. In this document, various updates were made in May 2012 related to the AppSM and software Connector Appliance. The content was expanded on the public web site with the latest graphics, and changes were also implemented to the "Success Criteria" of AppSM. Additionally, there were updates in April 2012 based on feedback from Brian Wolff, including updated appliance specifications, supported platforms, a simple networking requirements table, and an appendix containing the latest "Ports and Protocols" PDF. A note is made about an additional scoping call with questions regarding secure wipe of the appliance and other related topics. The document titled "IV_ScopingChecklist.doc" is a scoping guide from Professional Services, specifically for IdentityView v1.1. It provides instructions on how to customize and prepare the document for different customer use cases, including preparing properties, editing client information, and scheduling a scoping call. The guide also includes details about the requirements for using the Model Import Connector, such as needing a 64-bit Operating System and potentially having Domain Administrative privileges. For sample Telco use cases to be added or replaced in this document, users can find these under "For sample Telco use cases" heading. Additionally, customers often inquire about protocols and ports needed for a proof of concept, which can also be found within the guide. Some key steps outlined in the document include: 1. Selecting "Prepare," then navigating to "Properties" and editing the "Client" field by replacing "CUSTOMER" with the actual customer name. 2. In the "General Information" section, selecting the model of appliance if applicable. 3. Editing the "Sales Representative" and "Pre-Sales Consultant" sections as needed. 4. Forwarding the completed document to the customer for review and scheduling a scoping call. 5. Ensuring that the Model Import Connector runs on a 64-bit Operating System, not a 32-bit one. 6. Providing information on how to update fields in headers and footers by right-clicking on the "CUSTOMER" field and selecting "Update Field." 7. Attaching files such as PoC_Request_Forms.zip for easy access during the scoping process. The text provided seems to be a mix of various entries, likely from different contexts such as software downloads, documentation links, and profile references. Here's a breakdown and summary of each entry: 1. **IdentityView v2.0 SP1**: This appears to be the version name of some software or document related to identity management or user identification tools. The abbreviation "SP1" might indicate that this is an updated release with added features or fixes, but without more context, its specific function and application are unclear. 2. **Where can I download software such as the latest Connector?**: This seems like a query about where to find additional software components or tools similar to a "Connector." However, since no further details are provided (e.g., what kind of connector is being referred to), it's not possible to provide specific guidance without more context about the software in question. 3. **5 Steps to Take to Win a POV Before You Start**: This entry seems to be related to winning a proof of concept (POV) project or proposal, suggesting there might be a guide or checklist available that outlines five steps to follow. The focus here is on preparing and strategizing before starting the process. 4. **CloudShare Documentation**: This refers to documentation about CloudShare, presumably an IT management tool or cloud service platform. It asks where one can find information regarding this product’s appliance configurations, implying a need for setup guides or technical specifications related to how it works in practice. 5. **View Steven Maxwell's profile**: A request to view the professional profile of someone named Steven Maxwell, likely on a platform that supports profiles like LinkedIn or a corporate intranet where staff members can be listed with their roles and achievements visible to others. 6. **i.R.O.C.K. powered by Jive SBS® 4.0.11 community software**: This is an instance of proprietary software from Jive, possibly related to enterprise collaboration tools. The version number "4.0.11" suggests a specific release or iteration, and "community software" implies it might be available in different editions catering to various user needs. 7. **Jive Software Version: 113816**: This is an annotation indicating the version of Jive Software being used, with a unique version number that appears to be internal or custom. In summary, these entries are from varied contexts including software versions, documentation requests, strategic guides for project success, and professional profiles. More context would be needed to provide more precise information about each item.

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.