Minutes - Security Industry Association

More documents

Recommendations

Info

d. DSC Fibro Protocol Publication – There has been talk about SIA Standards publishing and distributing the DSC Fibro protocol, this will be discussed e. CP-01 Status – A review of the CP-01 happenings since it’s release in 2010 f. Glossary Project Status – Glossary update 5. DC-09 Project Review a. Review Project Proposal (Attachment B) Mr. Nesse went over the highlights of the project proposal. The group had no questions about the proposal. The proposal will be forwarded to the SIA Standards Committee on November 2 nd for approval. Mr Nesse asked for a motion to forward the project proposal to the SIA Standards Committee for approval. R. Hinkson/L. Dischert Motion Passes with Unanimous Consent b. Review Contribution from Amstein & Walthert (Attachment C) Mr. Nesse summarized the contribution to the standard from Amstein & Walthert: as follows, and gave his own thoughts on whether the contribution would be beneficial to be included. 2.1b Additional Parameters • MAC - matches existing, OK • alarm text: OK • site name: OK • building name: OK • location: OK • room: OK • trigger: OK, may conflict with or duplicate the data message, but seems a useful extension • X, Y, Z: OK • an extension of ASCII to allow accented characters should be considered (how is this extension defined?)
Is the intent to send multiple messages to send more information to describe an event, or to define a delimiter? It seems multiple messages are more likely to be acceptable due to limitations on the overall message length. 1.2 Sequential Retransmission The proposed sequence appears reasonable and effective. Perhaps this can be added as annex material. 2.2 Examples The UML sequence diagrams appear effective and would be a good addition to the document. 1.3 Monitoring of the Connection This information seems to go beyond the scope of the protocol standard. If included at all, it would be annex material. 1.3a Transmission Parameter This too is beyond the protocol spec, but seems to be useful annex material once the details are defined. 1.3b Redundancy This information seems to go beyond the scope of the protocol standard. If included at all, it would be annex material. 1.4, 2.4 Messages for Reverse Commands It may not be feasible to document these requirements, and polling intervals are generally too long to allow reasonable response times for commands. Also, it generally doesn't make sense to administer this through the receivers- in most systems where it started in the receivers it has been moved to a separate PC application. 1 NAK The transmitter should process the NAK message to set its internal time reference to that of the receiver so that the next message can be accepted. This seems clear in the document: "in order to allow the transmitter to adjust its internal clock". Generally, the transmitter would maintain a time base independently of the user-viewable time base, as even with mandated GMT time usage, it is common that the time used by the central station and the time used by the user are not the same.
Page 1: SIA Standards Kickoff Meeting - Int
Page 5 and 6: c. Next steps Schedule a meeting of
Page 7 and 8: Mr. Nesse entertained a motion to a

Minutes - Security Industry Association

Create successful ePaper yourself

Delete template?

Save as template?