SourceCode AV
@SourceCodeAV
Pittsburgh based Audiovisual User Group discussing trends, sharing ideas, and shaping the future of AV.
Anda mungkin suka
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 Tren
- 1. No Kings 591K posts
- 2. Semaj Morgan N/A
- 3. Dork Cult Protest Day 19.2K posts
- 4. Araujo 575K posts
- 5. Vandy 3,596 posts
- 6. Jelly Roll 1,148 posts
- 7. Gameday 31.8K posts
- 8. Gil Manzano 19.5K posts
- 9. Haaland 42.7K posts
- 10. Bournemouth 19.5K posts
- 11. Girona 38.9K posts
- 12. Mateta 9,941 posts
- 13. Diego Pavia N/A
- 14. #GoBlue 1,224 posts
- 15. Saban 7,565 posts
- 16. Ange 81.8K posts
- 17. Massie 52.1K posts
- 18. Georgia Tech 2,756 posts
- 19. Vanderbilt 3,879 posts
- 20. Flick 47.8K posts
Anda mungkin suka
Something went wrong.
Something went wrong.