How To PoC (Proof of Concept)
A Proof of Concept (POC) is a critical tool in successfully deploying new technologies and implementing policies. A properly executed POC will allow you to not only evaluate the viability of a technology, but also how to properly deploy it and what policies to build around it for long term use.
Identify the parameters of the operational business case for which the POC is being conducted. The POC should always be measured against these parameters.
Establish what data is needed to create the right business case. It is important to capture technical as well as operational data to measure the technology’s effectiveness as well as user experience.
Set up the POC in your environment mimicking the production setup in a test bed. Same technology will behave differently in different configurations. Therefore, it is critical to create the right environment and then measure results against it.
Observe everything and not just the core technology. Focus on all aspects that the POC impacts: infrastructure, administration, staffing, architecture, aesthetics, branding, maintenance and support.
Document the POC form beginning to end, from defined business case criteria to data points to lessons learned. Leverage that documentation into business cases, lessons learned, bases of design and SOW RFIs.
Plan for immediate, midterm and long-term deployment including soft costs such as staffing, SLAs, administrative time, supplies.
And lastly, circle back to the original parameters and establish a risk tolerance and acceptance model for a fully informed business case to leadership.
POC Execution Checklist
- Identify the parameters of the operational business case
- Establish what data is needed to create the right business case
- Setup the POC in your environment mimicking the production setup in a test bed
- Observe everything and not just the core technology
- Document the POC from defined business case criteria to data points
- Plan for immediate, midterm and long-term deployment
- Circle back to the original parameters and establish a risk tolerance
About Atriade
Key Takeaway: Atriade is an independent, MBE/SBE certified physical and electronic security consulting firm with more than 30 years of experience, serving as owner’s representative on 500+ projects across 60+ industries in 30+ countries.
Atriade is an independent physical and electronic security consulting firm with more than 30 years of experience. We act as the owner’s representative and trusted advisor from assessment through execution. We are not a product reseller or a systems integrator, so recommendations are based on what the organization needs rather than what a vendor sells.
Our work covers security assessments and risk analysis, program strategy and master planning, system design for access control, video surveillance, perimeter protection and visitor management, implementation oversight and project management, and lifecycle support.
To date we have completed 500+ projects across 60+ industries in 30+ countries, including work for Fortune 50 companies, Ivy League universities and leading technology firms in Silicon Valley. Atriade is a certified Minority Business Enterprise (MBE) and Small Business Enterprise (SBE).
Visit us online at Atriade.com
Connect with us on LinkedIn
Subscribe to our LinkedIn newsletter, Take A Risk
Keep the existing hyperlinks on all three closing lines exactly as they are set on the current posts.
Frequently Asked Questions
How do you start a proof of concept for physical security?
A Proof of Concept starts by identifying the parameters of the operational business case for which the POC is being conducted. The POC should always be measured against these parameters. The next step is to establish what data is needed to create the right business case, including both technical data and operational data to measure the technology’s effectiveness and user experience.
Why should a physical security proof of concept mimic the production environment?
A Proof of Concept should be set up in your environment while mimicking the production setup in a test bed. The text states that the same technology will behave differently in different configurations. Because of that, it is critical to create the right environment and then measure results against it. This helps ensure the POC reflects how the technology performs in the intended setup.
What should be observed during a physical security proof of concept?
A Proof of Concept should observe everything and not just the core technology. The text says to focus on all aspects that the POC impacts, including infrastructure, administration, staffing, architecture, aesthetics, branding, maintenance, and support. Looking beyond the core technology helps the organization understand the broader effect of the POC across the environment where it will be used.
What should be documented and planned during a physical security proof of concept?
A Proof of Concept should be documented from beginning to end, from defined business case criteria to data points to lessons learned. That documentation should be leveraged into business cases, lessons learned, bases of design, and SOW RFIs. The process should also include planning for immediate, midterm, and long-term deployment, including soft costs such as staffing, SLAs, administrative time, and supplies.