SourceCode AV
@SourceCodeAV
Pittsburgh based Audiovisual User Group discussing trends, sharing ideas, and shaping the future of AV.
Potrebbero piacerti
We're back & ready for our first session of 2016! Join us 3/16 for Trends in the #Corporate Market! tinyurl.com/zbflwt7 #avtweeps
That's a wrap! Thank you for all 30+ of you who attended! Have ideas for the next meeting? Tag us at #SourceCodeAV
Pennsylvania school code 10.24 effective today #SourceCodeAV
Future - taking out the word "recommendation" in reference to emergency notification in the fire code and base it on occupancy #SourceCodeAV
80%-90% of colleges and universities purchase their systems via grants #SourceCodeAV
There are multiple grants available for end-users to purchase or upgrade their emergency notification system through ex.DHS #SourceCodeAV
A huge thank you to our panel @eatoncorp, @visix_inc, and @Biamp. The information you shared was fantastic! #SourceCodeAV
There is a distinction in liability between design and integration #SourceCodeAV
Liability and E&O insurance. Look at specification of designs and make sure it was installed to these specifications. #SourceCodeAV
There is no special insurance at this time. There are no specific codes. Integrators are giving recommendations on what to do. #SourceCodeAV
Document tremendously, including any incident reports, any issues with the system and fixes, etc. #SourceCodeAV
Documentation and procedure. A set of criteria that the company needs to follow, which is a plan & backup plan. #SourceCodeAV
Worst Case Scenario: if mass notification fails, is there liability & criminal responsibilities on the integrator and owner? #SourceCodeAV
Going further than that adds vulnerability to the system #SourceCodeAV
Put in a data aggregate custom to that environment to tell you if there is an issue and at what level of urgency #SourceCodeAV
What type of reporting and/or remote monitoring can we do to ensure our systems are online and functioning at all times? #SourceCodeAV
Backup servers, having multiple paths for messages (IP, networking), layers of messages (personal, building) #SourceCodeAV
How can we implement redundancy into these systems? #SourceCodeAV
With a CAP system, the message is consistent. You don't have multiple people inputting conflicting message to multiple sources #SourceCodeAV
Using dynamic media, incorporate audio from source, don't rely on end user to create, different look than typical info #SourceCodeAV
United States Tendenze
- 1. No Kings 1.12M posts
- 2. Ole Miss 11.3K posts
- 3. #UFCVancouver 10.3K posts
- 4. Georgia 63K posts
- 5. Carnell Tate 5,933 posts
- 6. Brian Kelly 7,873 posts
- 7. Vandy 13K posts
- 8. Shapen N/A
- 9. Lane Kiffin 5,732 posts
- 10. Clemson 5,061 posts
- 11. Constitutional Republic 21.2K posts
- 12. Schumann 1,338 posts
- 13. Vanderbilt 10.8K posts
- 14. Barlow 3,212 posts
- 15. UNLV 2,197 posts
- 16. Cash Jones N/A
- 17. Hammond 2,284 posts
- 18. Beamer 3,693 posts
- 19. Julian Sayin 1,867 posts
- 20. Lagway N/A
Potrebbero piacerti
Something went wrong.
Something went wrong.