*****************************
COMMENT ON CODE AND CO DETECTORS FROM OCTOBER 27, 2015 ARTICLE
****************************
Ken
    Bravo, Bart [see Bart's comments in the Oct 27 2015 email].  As much as we wish for a level playing field in this industry, some players foolishly chew up the turf for the rest of us, keeping LAHJs and dispatch authorities antagonized and alienated by unprofessional  carelessness. Not to mention the knowledge spectrum amongst LAJHs. 
    To drill down into this, did the LAHJ perhaps mandate notification if a tamper came in, as well as for an actual CO alarm? Was this caused by learned distrust of installers? Overzealous LAHJs are not too common,  but misplaced zealotry, bred by unprofessional carelessness on the part of our peers definitely is. 
    Every  completion inspection, indeed every plan review should be used as an opportunity to get on the same page with the LAHJ. It is always wise to iron out interpretation and response questions up front.  
    Get to know the chief code interpreter at the state fire marshal's office. Respectfully use him/her as the higher authority, when necessary. Then fulfill expectations, with rare, or no failures. This respectful and competent approach will promote confidence in us and our industry. Inspections will actually get easier.
     The LAHJ Always gets what he/she wants. Why not provide it from the start? 
My two cents.
Jim d'Entremont 
Asheville Security Systems 
***********************************
ANOTHER PERSPECTIVE ON ASAP TO PSAP
***********************************
Ken
    …. another observation about “ASAP to PSAP”.
    We hear lots of good things from industry leadership about the ASAP to PSAP program, but very little is written or said by leadership about the risks. Although this forum recently highlighted some of the hidden financial and technology issues, presented by persons outside the leadership circle.
    Another perspective to consider:   
    We understand there will not be a “national standard”.  PSAPs are local. Technology might be standardized nationally, but the PSAP will be following local ordinance and policy.  For example, in Salt Lake City, the ASAP/PSAP program could make it easier to enforce local VR/Verified Response programs.  And in Seattle it could be easier to enforce the local SR/Subsidy ordinance that requires all monitoring firms to pay the fees for unnecessary calls for help. And in Las Vegas, it could make it easier for local PSAPs to lower response priority to “broadcast & file”.  And in other communities, like Los Angeles it could make it easier for local PSAPs to separate alarm calls from the general public for greater control for slow or no response. 
    You get the story…. expansion of the ASAP to PSAP program could make it easier to destroy the existing local relationships for the critical public private partnership, especially for the smaller and the responsible security providers. 
    All of this discussion is motivation for industry leadership to solve the false alarm issues internally, not hide them within ASAP to PSAP.  
    Careful what you ask for….
Lee Jones
Support Services Group
***********************
COMMENT ON IDEAS TO WRECK YOUR BUSINESS FROM NOV 2 105
************************
Ken
I must say that I took great pleasure when I read in the Nov 2 2015 morning email, Mitch Reitman’s comment about using a competitor’s contract, “borrowed” and modified to fit your business, and it possibly fouling up an acquisition.  I had an employee do exactly that several years ago, and to this day, uses a very old contract I purchased from you, with his company name photocopied over ours.  Maybe that will be the karma factor when the day comes that he is ready to sell…
anon