Developing A Standardized Project Deliverables Package - What Do You Include Or Recommend?

How big are your projects? Small is relative. For us, we are in the 10-40 camera arena most of the time.

We currently provide nothing. Not a single sheet of paper, just an email with an invoice... horrible

We already have some folders designed, and business cards printed with our support info. The plan is to put a summary of what we installed, cameras, intrusion, fire, access control etc, any relevant info, and support instructions in the folder. I did not think about a binder. A binder may be overkill as we would only have a few sheets of paper in it.

A map may be helpful, and we thought about keeping one in the head end, still undecided. All the IP's and configs would mean nothing to our clients as they usually have no real IT support.

We keep passwords, configs etc inside Connectwise. It's still a work in progress getting it all in there and we are slowly working on that goal.

Thanks for your honest reply :-).  Our typical project is the same as yours... SMB type stuff.  Some charter schools as well.

How do you like Connectwise?

Have at look at ITglue.  You can load all your system info, secure passwords, documentation and more then give your customer access to their info if you want by setting up account and giving them access. It also intergrated with Connectwise.

Hi Michael - thanks for your feedback.  Does it help to create the documentation or just a bucket to hold it as so to speak?   I will watch some videos and check it out.  What would you say are the main things you use it for?  

The customer needs to understand items that are not expensed on the final bill your team pays for with their time. Don't sell yourself short, in the very least if the system documentation is minimal you can sell at a break even cost to deliver basic system parameters. A smart PM can work with an office admin on working out simple project closing documentation templates.

As for me, I personally put in my own time to have my own project record, photos, emails and changes from the original scope. This is  usually a digital project folder with some simple filters to pack it all away. It's mine (I cannot remember everything and need to file my work somewhere), it feels more like a journal/blog.

If the project is large, plenty of wiggle room to build in system documentation and charge for it as part of your standards. In regards to passwords, it comes down to theirs or yours. Never leave the defaults login enabled, change it to a higher level and then have them manage it from there, even on isolated hardware. If they want nothing to do with it then preventive maintenance is your friend. Firmware, SSA updates, Password Lists, Backups, Syslogs make them pay. If they really want U: admin P: admin then circle back with them in an email describing the risks and see if they still want to own it. Do not let your technicians run amuck with passwords and logins, the engineer, pm or integrator owner should be able to provide a path to follow.

Good Luck.

Thank you undisclosed 3.  Good information.

Large enterprise end user here...

This is what I expect to see on every project. This is loosely based on my written standards that are provided to vendor's bidding on projects. You may find some of this useful for smaller jobs as well.

Pre-requisites to design:

• Threat level and risk assessment (CPTED review)

Pre-requisites to tender:

• Acknowledgement of internal installation standards
• System design
• Shop drawings
• Scope of work
• Storage calculations
• Vendor/Technician certifications
• Itemized proposal
  • Equipment
  • Software
  • Licensing
  • Labor
  • Rentals
  • Training
    
    
• Service/Maintenance/Inspection proposal
• Maintenance/inspection scope of work
• Warranty start date
• Warranty duration
• Warranty details on equipment & software
• Warranty service hours
• After hours service hours & rates with minimum callout charges
• Guaranteed response plan to system troubles and outages
• Annual testing schedule
• Software/firmware update plan
  

Upon project completion:

• Documentation
  • As-built drawings
  • Testing & Acceptance results
  • System deficiencies
  • Known risks
  • Explanation of any deviations from specifications or scope of work
  • Device Host Names
  • Device I.P. Addresses
  • User permissions report
  • Manuals
  • End user training

Excellent - very well thought out.  I appreciate you offering it up.  I think elements of it fit perfectly for my use case.

It is hard trying to dial in what is not enough vs was it too much...

Thanks.