Can we add a template or something for Network topology? Along with a spreadsheet of the camera names, IP addresses, ports, etc. That way we have pre and post-sales covered
I am more than willing to assist!
Project Documentation Forms & Work Order Guide
Published Jan 16, 2024 15:15 PM
This form may be one of the most important tools integrators can have when doing install and service work.
Inside, we provide a sample template form and explain which key details installers should include. We examine these crucial points:
- Why Project Documentation Is Needed For Security
- Which Information To Include In Documentation Notes
- Examples Of Good Information
- Why Sketches And Drawings Are So Useful
- Why As-Built Drawings Are Still Needed, But Make Powerful Adds To Project Documentation
Note: This tutorial was initially published in 2019 but was significantly updated in 2024.
Download *** *** ***** ********
********:
*********: ** ********* **** ****** *** this ** ********* * ************* **** for ***** *** ***** / **********. There ** ** '*** **** **** all' ****, *** **** ******* ** meant ** ***** ** * ******** point ** **** ** ****** *** quicker ** ***** **** ***.
Project ************* *******
** *******, ***** ********* *** ** the ********** ** ******* ****** *** explain *** **** **** ** ******* equipment, *** ********, ** ********* ****** security ******* ** ******* *****.
*** ******* ************* ***** ****** *** a ****** ********** ** *********, *********, and *** ******* ********** *********** ***** performing *** ****.
*** ********'* ******* ****** *** ***** invoicing ** *** ******** *** **** performed *** **** ******** ********* ***** for *** ****** **** **** *** the ******** ** ** *** ******, especially ** ***** ** ********* ***********.
The ******** ***** ** **** *************
*** **** ***********, ************* ***** *** basis ** ************* ***** ******** *********** and ***********. *** ****** ******** ************* for **** ********** ********* ***** ******* in ********* ** *********** ** ********* future ***************. ****** ***** ********** *** work ** *** **** ***** ** they ******** **** *** ***** ** done ** * ******** ** *** time ** ***** ** ** **** later *** '******* ********' **** ********* or ******* ****.
*** ******* ************* / **** ***** Form ********* ******** **** ******* **** a ***** ******** *****, **** ** the ***** ** ********* ***** **** as ** ******* ** *********.
Information ** *******
** ***** ** **** ******* ** include ** ******** ******* *************, ****** mandatory *********** ********:
- ******** ******* ****** *** **** **** Started
- *****/******* ** ******** ***********/********** ********** *** Job
- *** ***** ** ****/******** *** *** As *********
- *** ********* ***** **** *** *********
- ***** ****** ** ********* *** *** Many **** ****, ********* *****, *******, MAC, *** ** *********
- ******* ***** ********** *** *** *** Was *********
- ***** ** *******/ ********** ***** ** the ********
- *** ********* **** ** ****** / Component ********, ** **********
- ******** ********* *********/********* **** *********
******** *** ****** ********* ** ***** documents ******* ******** ******* *** *** job, ********** ** *** ******* ************* form ** * ****** '***** *****,' 'Work *****,' ** '*******' *** ******** pays ** *** ******** *******.
Typical ******** ************ ***********
******** ** ******* *** ******** ************ or *********** ********:
- ************ *** ************* ******* ** ************** camera *****
- ****** ********* *** *********-**-**** ***** ******** of *********** ******-****
- *** ********** ****** ** ******/**** **** specific ********* ** *********
- ***** ********* ********* *** ******* ** the ******* ** *** ******** *******
- *** ** *** ******* *****-**-******* ** AHJ *** * ********** ********?
- ********* ******* **** **** ****** *****, IP ******* *******, *** ***** **** locations
- **** ********** **** ******* **** *****, additional ********** ********* *****, ** ******* cabinet *********
- ******** *********** ** ************ ** *********** terms **** **-**** ** ** ******* drawings
*** ****** *** ** *********** ******** typically ******* ** *** **** ** security ********* ********* *** *** ******** the ****** *** ** ******** ** operational ******** ** '******' *******.
Include ******** & ********
*** **** *******, ****** ******** ******* pin-out ********, ******** ******, *** **** pictures ***** ** *** ***** *** useful **** ******** ** *** ** project *****.
**** * ****** **** ******* *** do * **** ******* *** ** explaining *** ******** ********* *** ********* or ********, *.*.:
*****, **** ******** ****** ******** *** depicting '******* *************' ******* ** **** future ******** **** ************ *** *** when ******* ****** ******** **** *********.
'As-Built' ******** ***** ******
*** ********* ****** ** **** ****** Project ************* ***** ** *** ******* the ********** *** ******* **'**-*****' ********.
********* ** *** ******** ********* ** Architects (***), ******* ******** ****** ******* at ***** *** *** ** ******** handed *** ** *** ***** **** show "** *** ***, **-**** ******* to *** ******** ************ *********." *******, these ******* *** **** ** **** but *** ** **** ** *** systems ** ********. ***** ******** ****** locations *** ********** **** ******* ********* that ***** **** **** ***** ** convey *** ***** ** ********* ** attempted.
** ****, **-***** ******** *** ***** useful ********* ********* ** ******* ******** forms, *** ** **** ******** *** filed *** ****** *********, **** ***** form * '**** ****' ******** *** future ******* ****.
*** **** ** *** *******, *** our:'**-*****' ******** ********.
Comments (5)
UM
Undisclosed Manufacturer #1
Jan 07, 2019TM
Ty Mullen
Jan 08, 2019No question documenting projects and follow up service is a good thing.
Follow up service calls are easier to document because there isn't as many changes, but still have to be done. Conversely projects can be very heavily documented. I have found that different projects require different documentation.
Projects that have architect, general contractors, and sub contractors will have a minimal amount of documentation listed in the specifications of the project that have to be completed. And it doesn't matter how little or large your scope of the project is you will have to complete that list of requirements. So make sure that you account for that time when your quoting the job. I have had projects where the documentation was as long or longer to complete then the work being performed. It will save you time if you create templates for those items as well.
Another important thing is how the information is to be stored and accessed. It's so nice if all of the information can be stored in a single resource/application. And save you so much time and headache if that resource can be accessed while onsite with great ease.
Fabian Muyawa
Jan 09, 2019The Project documentation are cardinal inorder to harmonize communication between the client and the service company. The docs formerlises the whole project process and lives most of the clients satisfied.
Without any docs client tend to be unsatisfied and sometimes even become difficult to pay for the service.
Therefore, such docs like the above template are very important to avoid disputes with clients.
Will Doherty
Jan 09, 2019I agree with the premise of good documentation. The document above combines the invoice with work order confirmation which might work for some businesses. In my experience asking the technician to know the tax rate and sell prices is not efficient use of their time. I recommend getting a signature for the scope of work performed, list parts/materials used and time onsite then have the office staff generate an invoice within 24 hours. If you cannot get a signature then a quick email follow up with this information works as well. Sometimes tacking down the POC onsite at the end of the work can be a waste of time.
Here are some of the fields we added on our work order:
We added person who authorized the work to be performed as well as point of contact onsite. These can be different and can cause confusion for the field tech and admin staff.
We added a field for follow up needed/parts on order/call complete. This let the end user know the status as well as what we needed to do behind the scenes to complete the work.
You also might want to check with your local insurance requirements however we used Onsite time/offsite time so we knew when the field technician was physically at a client's site. This was recommended by our insurance agent.
UI
Undisclosed Integrator #2
Jan 17, 2024Reflecting on years of experience in building and managing integration projects, one recurring challenge stands out – the constant demand for documentation. Whether it's a minor detail or a major process, the need for organized documentation has become a daily refrain.
In my view, organizations of every size should consider establishing a dedicated department focused on documentation standards, meticulous filing, and effective communication of document etiquette. This proactive approach ensures smoother operations and sets the foundation for streamlined project management.
For those contemplating the shift to MSP software, it's essential to strike a balance. The potential downside of "too much documentation" can be as challenging as the initial problem. We've transitioned from a model where one person held all project information to a decentralized structure, involving every individual who contributed, collaborated, or managed various aspects of a project.
Navigating through countless revisions, purchase orders, and intricate details presents its own set of challenges. The signal-to-noise ratio becomes a pertinent concern – drowning in a sea of information while craving meaningful knowledge.
In this dynamic landscape, I'm curious to learn about your strategies for login documentation. How do you ensure accuracy and efficiency in managing critical information, especially as projects evolve over time?