How Do I Run a Proof of Concept?

Summary:

This document outlines a structured approach to conducting a proof of concept (POC) for introducing new products or solutions in the United States and Canada. The process involves several steps including scoping, setup, preparation, and delivery models such as cloud sharing, laptops, workshops, appliances, paid pilots, and license keys. Key points include initiating a conference call with the customer to complete a proof of concept scoping guide, focusing on practical solutions within constraints, setting up a POC for minimal complexity, and following specific steps like reviewing documentation, preparing a scoping guide, assessing network access requirements, obtaining necessary approvals, and ensuring all preparations are completed before the POC. Additionally, it emphasizes security measures such as SSH access, configuring McAfee Host Intrusion Prevention settings, using secure deletion tools like Eraser, and adhering to company standards during the POC execution. The document also addresses limitations on scope duration, differentiation strategies, resource allocation, scoping guides, key differentiators, standards of business conduct, checklists, and protection of brand image through tools like IdentityView and Reputation Security Monitor.

Details:

A "proof of concept" (POC) is a demonstration used to prove the feasibility of an idea or method. It may be small and incomplete but serves as evidence that a concept could potentially be applied in practice. The POC process involves several steps including scoping, setup, preparation, and delivery models such as cloud sharing, laptops, workshops, appliances, paid pilots, and license keys. Expiration typically occurs at the end of the last day or Friday of the POC period. In preparing for a POC in the United States and Canada, initiate a conference call with the customer to complete a proof of concept scoping guide. Ensure you are familiar with relevant products and solutions before the call. During this call, go through each section of the scoping guide while considering use cases that showcase unique capabilities like Active Lists, Session Lists, Dashboards, and Variables. Highlight competitive advantages over rivals by showcasing difficulties competitors face with IdentityView, Reputation Security Monitor, and Threat Detector. Avoid overly complex designs or excessive scope; instead, focus on practical solutions within the constraints of available tools such as Logger if necessary. The task involves setting up a proof of concept for a new product or solution with minimal complexity and following specific steps: 1. Reviewing the "Objections" and "Best Practices" sections in provided documentation. 2. Preparing a scoping guide that will be sent to both the customer and manager, seeking their confirmation after the call. 3. Communicating with the customer regarding receipt of the scoping guide. 4. Assessing network access requirements for setup using laptop or company systems, as well as discussing appliance security measures such as secure wiping options if needed. 5. Determining whether the appliances need to be rack mounted and noting any specific attire guidelines for onsite visits. 6. Ensuring all necessary approvals or clearances are obtained before visiting the customer's site. These steps require a thorough understanding of the product, effective communication skills with both internal team members and external customers, and coordination across different departments to ensure timely completion of each phase. The task involves scheduling and confirming a proof of concept (POC), verifying customer details such as address and business hours, discussing power and networking requirements with the customer, ensuring compatibility with their server setup, checking for network restrictions, preparing by downloading necessary software and documentation, and finalizing preparations like SmartConnectors. The document outlines steps for preparing for a proof of concept (PoC) involving SmartConnectors for devices and applications. To avoid scope creep where customers may request additional SmartConnectors not initially scoped for the PoC, it is recommended to keep the SmartConnector software confidential. Additionally, it advises downloading any necessary solutions software or documentation for deployment during the PoC, including IT Governance, PCI, SOX, FISMA, HIPAA, JSOX, NERC, IdentityView, ThreatDetector, and Reputation Security Monitor solutions. Ensure that all content and context updates are downloaded to a USB drive. Save Express/ESM/Logger custom content relevant to the customer use cases documented in the scoping guide on the same USB drive. Verify importability of this custom content into the specific version being used during the PoC. Test on "vanilla" virtual machines to ensure compatibility with the intended PoC appliances, as these more closely resemble the actual appliances. If a FlexConnector is part of the scope, obtain sample logs and create it beforehand; assistance can be sought from the PreSales Global Field Support team if needed. Lastly, make sure all consoles used in the PoC are ready for deployment. This document outlines a set of guidelines and requirements for working with specific products and tools during a proof of concept, emphasizing security measures and proper handling of licenses and software. The main points include: 1. **Interfaces**: Ensure that the consoles for installed products are verified to connect with virtual machines. Also, verify connectivity with web browsers to access any product interfaces such as Logger, Connector Appliance, Express, or ESM. 2. **Licenses**: Retrieve all licenses from email and save them on a USB drive, ensuring they are specifically intended for the proof of concept and not internal keys. 3. **SSH Access**: By default, SSH access to the appliance is disabled. After enabling it, respond to the challenge string displayed by entering a specific response. Contact the PreSales Global Field Support team if assistance is needed with this string. 4. **Tools**: Have all necessary software tools installed on the laptop and downloaded on a USB drive, including PuTTY, WinSCP, Cygwin, and FileZilla. 5. **McAfee Host Intrusion Prevention**: The laptops have McAfee Host Intrusion Prevention which blocks inbound connections by default. If needed, configure it to allow minimal ports for specific tasks and ensure not to expose the laptop to potential infections or harm in a customer's environment. Perform regular antivirus/anti-spyware scans before and after onsite work. 6. **Eraser**: Mentioned as an optional tool for securely deleting data from hard drives, supported under Windows XP SP3, Windows Server 2003 SP2, and potentially other versions not specified. This document is crucial for ensuring a secure and compliant environment during the proof of concept phase, especially regarding security protocols and handling sensitive information. This document outlines essential details for a proof of concept (POC), including software requirements and hardware recommendations. It covers secure deletion tools like Eraser, which should be used to wipe virtual machines at the end of the POC. Network connectivity is facilitated through HPVR and WebEx accounts for remote team members, while physical cables include straight-through and crossover Ethernet cables along with a small Ethernet hub/switch. A USB drive preloaded with necessary software is also recommended. Additionally, it emphasizes the importance of adhering to company standards during POC execution and suggests not having sales personnel present during sensitive phases like the proof of concept or presentation of results to maintain professionalism and focus on technical aspects. The document highlights that Sales should be involved in kickoff meetings and for presentations but should avoid being present during these more analytical stages. It also stresses the importance of using latest release SmartConnectors and following best practices such as not going first, considering alternatives, and utilizing company appliances rather than customer-provided ones. The summarized content outlines a structured approach to managing and limiting the scope of a proof of concept for r hardware. Key elements include: 1. **Limit the duration**: To ensure efficiency, set specific timeframes for each stage of the proof of concept. 2. **Limit the scope**: Define clear boundaries for what will be included in the project to avoid overambition and maintain focus. 3. **Differentiate**: Highlight unique features or benefits that distinguish this r hardware product from competitors, which could include:

• Differentiation based on SmartConnectors and FlexConnectors usage limits.

4. **Schedule** management involves planning and organizing tasks to meet deadlines effectively. 5. **Resources** allocation is crucial for managing personnel, materials, and finances efficiently within the constraints of the proof of concept. 6. **Scoping Guides** provide a framework for decision-making regarding project scope and objectives at various stages. 7. **Key Differentiators**: Identify aspects that set this product apart from others in the market, such as adherence to specific standards or unique functionalities. 8. **Standards of Business Conduct**: Establish guidelines for ethical behavior within the company, including management practices like Equipment Management & Remarketing (United States) and iServe (Canada). 9. **Checklists** help ensure that all necessary tasks are completed in a timely manner throughout the proof of concept phase. 10. **IdentityView**, **Reputation Security Monitor**: These tools monitor and protect the company's brand image and online reputation, critical for managing business conduct and ensuring market security during the proof of concept.

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.