The Ten Things You Need to Know Before You Start a PSIM Project
- Published: Tuesday, 23 October 2018 08:48
- Written by Adlan Hussain
1. Business Case
Proof Statement: PSIM consolidates and automates a businesses’ Operating Procedures across an organizations security framework. A holistic PSIM implementation meeting the ambitions of the business will be achieved when participating department heads contribute to the business case.
2. Well Defined Objectives
Proof Statement: When defining PSIM objectives you need to ensure there are;
• Quantitative: The PSIM objectives should be easily, measured, monitored and reported,
• Time-frame specific: Time frames should be specified in all of your PSIM objectives,
• Flexible: PSIM technology is extremely powerful; it will redefine the way you work. It is important to revisit your objectives regularly to ensure they reflect these changes,
• Understandable: The PSIM objectives should be created in an understandable way that can be easily communicated without having to decipher jargon,
• Realistic: It is important that the PSIM objectives are realistic, or you may end up disappointing your stake holders and yourself.
Risk: Your PSIM solution will only meet your objectives if they are clear and understood by all key stakeholders.
3. Risk Management
Risk: Without suitable risk management a PSIM deployment could be jeopardized.
4. Scalability & Flexibility
Proof Statement: Ensuring you choose a PSIM solution that allows you an easy and cost effective path to scale up or down to meet your needs will reduce the risk of needing to change systems a few years down the line.
Risk: Choosing a PSIM solution that does not scale or allow you to easily change in-line with your evolving process will mean you need to upgrade your PSIM system prematurely.
5. Fail to Plan, Plan to Fail
Proof Statement: Employing an experienced full time Technical Project Manager (PM) will help to ensure all of the moving parts of a PSIM deployment are as expected and on schedule. Selecting a PM who has experience in deploying large IT systems will further reduce the risk of missing deadlines.
Risk: A PSIM deployment without a PM can take longer than expected, resulting in a deployment that falls behind the expectations of stakeholders.
6. Ensure all Requirements are Identified
Proof Statement: It is therefore essential to develop an Operational Requirements Document (ORD), which will help ensure a 360 degree audit to ensure a complete list of requirements is gathered. This will go through each of the systems and identify input & output requirements such as external interface requirements and functional requirements, as well as defining system-wide and technology requirements such as performance and usability requirements.
Risk: An incomplete Operations Requirements Document could lead to unhappy stakeholders and could add time delays to achieving a system that is approved by all.
7. Establish Change Management Rules
Proof Statement: Establishing rules on how to manage requests for change outside of the scope of works needs to be documented prior to a deployment. Establishing clear roles within the organization and approval processes for such changes will support this activity.
Risk: Without documented change management rules the complexity of features and requirements can quickly change resulting in a system that does not meet the original objectives.
8. Establish Partnership with Key Stakeholders
Risk: Without support from all key stakeholders a PSIM deployment will take longer to achieve and will create conflicts leading to timelines slipping.
9. Plan for Change, “Things Will Not Go As Planned”
Proof Statement: Ensuring there is flexibility and contingency in your plans will help to ensure deadlines and expectations are met. Working closely with your PSIM vendor and using the wealth of experience they have in these types of deployments will help guide you to creating a plan that factors in some contingency for the unknown.
Risk: Without flexibility and contingency in the PSIM deployment plan you are risking missing deadlines set.
10. Select the Right Integrator
Proof Statement: Ensuring your PSIM integrator has the relevant IT systems engineering, project management and physical security experience will help to ensure smooth deliver of your PSIM deployment. Pay particular attention to the integrators certification by the PSIM vendor, which is something all reputable PSIM vendors should be actively providing their integration partners with.
Risk: Without suitable certification and proven experience, an integrator can add considerable risk to a PSIM project.