CONCEPT of OPERATION (CONOPS)
The process of implementing a security-oriented project presents an extensive range of challenges. Such challenges, which need to be specified, are driven for the actual operational requirements of the system’ users, out of which a complete and thrall Concept of Operational (CONOPS) is defined. The Concept of Operations is an essential and necessary step in the systems engineering process and the main component leading to the solution development based on user’s requirements and system design.
The CONOPS is set by highly experienced operational experts, with extensive field experience in every aspect of the project.
Our engineers take the following essential steps in forming a professional CONOPS:
- Set meeting with each of the Stakeholders and learn of the operational requirements.
- Visit the POI (point of interest) in which the customer would like to operas ate it service and learn of the set by the customer, and learn the landscape, the current infrastructure, the weakens and challenges or each POI (point of interest).
- Based on all the information gathered, we shall form a CONOPS document describing the project from the operational point of view.
The CONOPS outcome is a formal document that recommends to the customer operational means of how to address each of the operational challenges in the project.
The CONOPS document includes a high-level description of the project capabilities, how the system shall operate, taking into account physical limitation, technical gaps, federal regulation, the roles and responsibilities for the different users, typical operational scenarios and Stakeholders interests.
A mandatory process that is usually performed right after, and based on the CONOPS, with the primary aim of verifying and obtaining detailed information of the landscape, topographical and infrastructure challenges presented in each of the POI (point of interest) in the project. The Site Survey includes (among others) contractors’ survey and coordination meetings.
The information gathered from the Site Survey, together with operational customer requirements as set in the CONOPS are acting as the grounds for preparing the conceptual solution design, and further on the detailed technical solution.
The Site Survey shall include our field engineers visits to the sites, aerial photography, official updated city/country map, and so far.
The CONOPS outcome is translated into conceptual design, set by dedicated engineers who have experience in taking each of the concepts of operation conclusion per challenge and turn it into a technical solution.
The conceptual design shall advise on-site use and enhancements, selection of materials, building systems and equipment, as well as provide a recommendation on construction feasibility (if required), availability of materials and labor, estimated time requirements for project realization and factors related to project projected cost.
Our experts takes into consideration the following guiding principles when forming the conceptual design :
- Scalability – the system design and general architecture should support scalability to provide continuous growth to meet the growing demand of system users. There must not be any system-imposed restrictions on the upward scalability in the number of field devices. E.g., the use of a single vendor or proprietary solutions shall be carefully examined.
- Availability – our experts peruse the motive of “no single point of failure”, hence the architecture components should provide means to ensure that are no single point of failures in critical project’s elements, and insure continuous availability.
Based on the CONOPS, and incorporating the findings and information of site survey process, we shall provide the customer with a detailed system architecture of the overall solution, our recommendation for the technology to be used in order to fulfill the CONOPS, and all the components of the technical system architecture (which should be industry best standard).
When defining the technical design and the specific vendors to be used, we do our best to fit the technology per POI to the conclusion set in the conceptual model. Hence, we are not bound to a specific or single vendor, we define the technology according to the CONOPS, and not trying to set the CONOPS according to the technology
The outcome of this stage is a full and detailed system technical design, with our recommendation for the technology/vendor to be used, including BOM and (if applicable) commercial aspects of the BOM (bill of materials).
The technical design may also include the definition of the labor work to be performed to achieve the required project target in each POI. Pending on the magnitude of the labor and infrastructure work, this may be presented in a different document.