Systems Facilities and Operations Readiness Mapping System

Establishment of a new System or a Facility brings numerous challenges along with it which in turn can lead to critical risk elements. These risk elements can become a major hindrance in the successful implementation of the project, which if not addressed systematically can lead to complete failure or shut down of the project. Also, it can lead to financial losses or comparatively less Return on Investment from the project than what was actually estimated while the project was approved. To avoid such unpleasant outcomes for an ambitious project, it is essential to check the overall readiness of the project area with respect to Systems, Facilities, Operational Functions within the new proposed project.

SFOR is a system that derives this readiness for these Systems, Facilities and Operational Functions.  SFOR enables foreseeing the outputs of a particular project from an overall functional perspective. It presents information of how different assets created by the project touch down within the overall organization in creating a useful function. It enables the company to see from a distinct angle at a project where they are able to see things that the traditional project design and construction teams cannot anticipate. This way the company is able to point out missing links between a legacy system and a new system. This is one of the most fundamental principles of SFOR.

SFOR is a system which provides a knowledge base of all the verticals in which the Birdi Group works. There can be different projects like an airport project or a seaport project or a hospital, rail and transit project or a school project. Each of these verticals have their own standard way of conducting the project activities or processes. From one airport to another some of these standard processes slightly change, but typically they have their core processes that don’t change. A few of the processes in an airport project are Terminal Operations, Land Side operations, Air Side operations, Gate Operations, Ticket Operations, etc. The SFOR Systems needs to have the capabilities to establish a knowledge base for all of these verticals.

The knowledge base is developed by setting up SFOR guidelines for a particular type of project, which include Business Processes information and their SOPS to be followed considering various regulations and standards, Stake Holder functions, SFOR or ConOps Elements which express the desired outputs, Systems and Facilities which are to be used for the processes in the project.

A Requirement Traceability Matrix is used to break down the newly proposed project into discrete and granular Project Scope Packages. Each of the granular processes within the Project Scope Packages are then mapped with SFOR or Concept of Operations Elements along with the respective Stake Holders, Systems, Facilities linked with the processes within the project scope packages. Subsequently the potential gaps as well as risks associated with the processes are revealed which are analyzed and appropriate solutions are provided or steps and corrective measures are taken for closing those gaps and mitigating these risks.