How to Estimate an IT Project
Always starts with data when estimating an IT project. Your approach will depend on your IT project. To choose the best method(s), the preparer needs to be informed on your project’s needs and assess it using IT heuristics.
IT project management requires unique skills, as technical projects are highly complex and constantly changing.
​
Our estimator will answer the following questions at the start of your IT project:
-
What is the purpose of this project?
-
What are the deliverables?
-
What type of project is this (new, addition, repair, or something else)?
-
How complicated will this project be to deliver?
-
What are the high-level requirements?
-
What information do I need to gather?
-
How will I collate the data?
-
Who needs to be involved, and at which stages?
​
In addition to the historical data you use as a foundation for your estimate, the document you present to management may include the following, depending on your IT project and method(s) you select:
-
Basic Information: List the project title, project manager, and company name.
-
Cost Estimates: Include the baseline, minimum, and maximum project estimates, as well as the risk contingency.
-
Phases: Include the estimate and space to later record the actual hours for business requirements, functional specifications, detailed design, code and unit testing, system testing, user acceptance testing, project manager, project control office, and project management office (PMO).
-
Phase Activity: Here, break down the standardized work effort metric, phase team size, computed work effort hours, the average hourly cost of each resource, and the estimated cost of each phase.
-
Roles: List the required participants, including their hourly rate and the resource count allocation per project phase.
-
Schedule: Include the estimated start and end dates, length of each work day, and project duration in weeks.
​
We will designate a team member to cross-check the accuracy and depth of the document, with special attention to the following often-overlooked areas:
-
Documented Requirements: Ensure that the project manager has documented all project requirements.
-
A requirements document specifies the technical and design details. It includes any resource requirements and connects the project with business goals. A separate IT requirements document helps support the cost estimate.
-
A business analysis requirements document summarizes interface and functional requirements.
-
Meetings: Aligning your team requires regular meetings. Account for this time when determining the schedule.
-
Nonfunctional Project Requirements: Set any terms for these potential requirements, such as automatic scaling, before the project's start.
-
Project Management: This category often accounts for approximately 10 - 15 percent of the budget.
-
Testing: Unit testing ensures the deliverable quality. Make a plan to test throughout the project.
-
Additional Costs: Consider less obvious costs, such as the time it takes to perform project analysis or set up a new team environment.
How to succeed in CCTV projects in 7 steps!
​​
During consulting, we always hear the questions:
"How many cameras will be used in the project?
Can I access footage from anywhere?
Is it best to use wired or wireless?
Why do we need to use containment?
Is it expensive?
Can you give an estimate of the project cost now?"
The answers may vary from "I do not know, it depends, it's a high possibility, or maybe ...." many professionals take into account only the cost of the cameras, but forget all the other elements that make up a system of a closed circuit television IP. This article shows in seven steps what it takes to design and implement a system.This article shows in seven steps what it takes to design and implement a system.
​
1. Objective of the project
Before going out and determine the position of the cameras, determine what the objective of the project is, the perimeter monitoring, process control, asset protection, among others. This is one of the most important steps (and must be written), as it establishes all points of the project; on 80% of the projects the following target is heard: "I want a 100% coverage!" "I want to have HD on all cameras" "I want to see everything!".
Here are some examples of goals unassigned, we will have greater chances that the project does not materialize (due to high cost) or does not comply with the desire of the customer after installation (dark targets).
Important: The target must be familiar to all, especially to those who sponsor the project and operate the system.
​
2. Cameras locations
With the set goal, go to field for research and check the best location for the cameras, also check possible interference that can adversely affect the images at the end of the project. Note that this check can only be done while in Site, projects implemented through maps, charts or even Google Maps cannot give the same result.
At the time, observe the lighting, if necessary indicate the use of projectors (LED, infrared), choosing the right model for every application and document management BOM with brand and model and lens of every camera along with the ground floor of the place, position each camera and enter the field of vision of the same.
​
3. Infrastructure
The IP CCTV system requires an Ethernet network already in place at the site. If you have a network in place that will be shared with the cameras, make sure that the network has conditions to maintain all systems in operation. The network administrator should be involved in this step.
​
-
Are there any free ports on the switch for the new cameras?
-
Does the Switch support this new traffic?
-
Is it PoE?
-
Do you have the ability to feed the cameras?
If there is an established network, create a new project and complement the above documents (bill of materials and ground floor).
Important: The surge suppressors and grounding system must not be forgotten.
​
-
Selecting the Right Network Cabling Solution
-
The success of your CCTV system hinges on the quality of network cabling chosen. Opt for high-performance, durable cables that can withstand environmental factors and ensure reliable data transmission. Consider factors such as cable type (e.g., Cat5e, Cat6), length requirements, and compatibility with Power over Ethernet (PoE) technology for streamlined installation.
-
Evaluate the specific requirements of your CCTV system, such as the number of cameras, distance between cameras and the central recording device (DVR/NVR), and anticipated data traffic. Choose cabling solutions that can accommodate these requirements while providing ample bandwidth and signal integrity.
​
-
Selecting the Right Containment Solution
-
Evaluate the containment/conduit requirements of your CCTV system, such as the number of conduits, size of the conduit based on the number of cameras, junction boxes, pull points, conduit connectors, and adapters, trunking for specific areas, the distance between cameras and the central recording device (DVR/NVR), internet service provider modem, or clients Network closet and provisions for any internal runs.
​
4. Administration
When the objective of the project is finalized, the administration of the system should be assigned, which influences the choice of platform or monitoring software.
​
-
Will the system be in a single local access or a remote access?
-
Is there only one Site or will they have multiple locations with centralized management?
-
Do we have contingency recording images?
-
Are there professional operating the system?
​
Today there are several manufacturers of CCTV software with similar functions, but they may have different ways of licensing, for example, while a manufacturer only charges the amount of cameras that are being managed and provide all other characteristics ( for example, remote access, the number of customers, cell phone access, etc.) others may charge by the characteristics through additional licenses.
After choosing, complement the list of materials document.
​
5. Monitoring Center
Here is the heart of the system, and like all heart must be protected and must be working well. Some of the points to be observed:
-
Use servers: These devices are designed to operate 24 hours a day, as your security system, and should be dedicated for this use, i.e. should never be shared with another application.
-
Refrigerated environment: The server must be conditioned on racks and refrigerated environments should never be installed in lodges, or under tables or cupboards. High temperatures are the main causes of defects in the systems.
-
On break: In addition to the cameras monitoring center, it should work in a power outage situation, adjust the no-break system to keep all equipment in operation during faults.
-
Technical Furniture: The hubs will not last if used office furniture, the right thing is the use of technical furniture that has the durability to ensure the functionality for long periods.
​
6. The skilled labor
If you have the best project, buy the best equipment market and do not hire specialized companies for installation, it can go wrong. Always ensure that the professionals have training and technical certification to install, set up and train on products.
​
7. Warranty
Remember, all equipment is worn out mainly by time, to minimize the effects, you only need a preventive and regular maintenance. It is cheaper a preventive maintenance cost than the cost of replacing equipment with corrective maintenance.
​
Another point are the spare parts, if their work is fundamental and cannot suffer outages, even if faulty, it is best to keep some equipment in stock for replacement.
​
Following these steps you will succeed at the end of implementation. Of course, there are works and projects with various complexities, but errors are minimized and with practice are eliminated. Often we hear "It's ... cheap is expensive ...." but we assure you that with a well-done design, goes even cheaper! Therefore, always consult your engineer!