While waiting to get in touch with the people I need, I've been looking into what literature exist already...
I've noticed a couple major problems scenes of live music:
ONE: FROM MOSH PITS TO STAGE-DIVERS:
People sometimes do "stupid" stuff because it's "fun." People in charge don't want to limit "fun" too much because otherwise nobody would come and they wouldn't make $.
However, they don't want anyone to die other... so there are security folks. They catch crowdsurfers before they get on stage, and pull out the people up front that are getting smushed to death because they didn't know what they were getting themselves into.
TWO: CLUB SHOOTINGS
It happens; Famous incidents (Shyne/Puffy/Lopez) and locally.
Interestingly, at least in the Seattle scene recently, there's been quite a few. Most notable, those "club nights" that are 18+ and not only 21+. Why are these events the ones that are problematic? Gangs. By drawing 16+ or 18+, they are also drawing in a gang related crowd. We've seen this happen at Vera too. That's why we're not doing any dance events until we do a comprehensive re-evaluation of our capabilities and understand fully the scope of the problem we're dealing with.
article
FOR ME: Couldn't yet find any work published on the type of scene I'm leaning more towards, so this could be a very interesting space to produce some work on.
Sunday, February 28, 2010
Tsunami problems
No progress due to tsunami in Hawaii. Yes really. That somebody I need to talk to about my project but couldn't talk to til Tuesday... well the tsunami is keeping him over in hawaii for a bit longer, so until then...
Monday, February 22, 2010
Abstract
It's looking pretty short, so if anybody has some feedback on it, it'd be greatly appreciated.
Security is ubiquitous in events and functions. Live music, is no exception. With a significant proportion of live music happening in venues prohibited to the underage crowd (most places that serve alcohol, such as bars and clubs) there becomes a clear difference between all-ages, predominately youth, events and non-all-ages/youth events. Despite the differences in the characteristics of all-ages, predominately youth crowds, the approach to security does not consider these differences. This research identifies several key aspects in which all-ages/youth events differ from non-all-ages/youth events, and the implications on security policy. This work can be used to inform future security policy regarding all-ages, predominately youth events.
Security is ubiquitous in events and functions. Live music, is no exception. With a significant proportion of live music happening in venues prohibited to the underage crowd (most places that serve alcohol, such as bars and clubs) there becomes a clear difference between all-ages, predominately youth, events and non-all-ages/youth events. Despite the differences in the characteristics of all-ages, predominately youth crowds, the approach to security does not consider these differences. This research identifies several key aspects in which all-ages/youth events differ from non-all-ages/youth events, and the implications on security policy. This work can be used to inform future security policy regarding all-ages, predominately youth events.
Sunday, February 21, 2010
Design + Business
I think I've always been struggling with trying to combine design & business into something I want to do.
I've already decided against being in-house designer. Then I've decided against traditional "doing" design. I thought about PM in ad agencies. I thought about brand strategy.
Now I'm thinking about consulting.
During my interview with Accenture, I was explaining how awesome design studies is, and talking about problem-solving vs. problem-finding, and how complicated questions have simple answers. The Sr. Manager said, "like 42?"
Yes. Exactly. Perfect analogy. Consultants get it too.
So there you have it, consultants are like DSers tackling business problems.
I've already decided against being in-house designer. Then I've decided against traditional "doing" design. I thought about PM in ad agencies. I thought about brand strategy.
Now I'm thinking about consulting.
During my interview with Accenture, I was explaining how awesome design studies is, and talking about problem-solving vs. problem-finding, and how complicated questions have simple answers. The Sr. Manager said, "like 42?"
Yes. Exactly. Perfect analogy. Consultants get it too.
So there you have it, consultants are like DSers tackling business problems.
Narrowing down
1. type of event/crowd
Different age groups act differently.
4. intoxicated patrons
Drunk adults at least can legally be drunk, but what do you do with drunks under 21?
why not consider drug use too? if it's illegal, its illegal for both the over-21 and under-21 crowd-- no differences to be explored.
6. handling of physical disturbances
Ideally, issues would be handled before the become violent.
Protocol versus human morals:
teen getting beat up while 3 security men watch
Different age groups act differently.
4. intoxicated patrons
Drunk adults at least can legally be drunk, but what do you do with drunks under 21?
why not consider drug use too? if it's illegal, its illegal for both the over-21 and under-21 crowd-- no differences to be explored.
6. handling of physical disturbances
Ideally, issues would be handled before the become violent.
Protocol versus human morals:
teen getting beat up while 3 security men watch
Tuesday, February 16, 2010
Things to consider in security policy
Not (yet) a comprehensive list, but it's a start:
1. type of event/crowd
2. number/positions of security personnel
3. unruly patrons
4. intoxicated patrons
5. when to involve police
6. handling of physical disturbances
7. prohibited items (and what isn't allow but can be check at front desk)
8. evacuation plan
9. Documentation/incident reports
1. type of event/crowd
2. number/positions of security personnel
3. unruly patrons
4. intoxicated patrons
5. when to involve police
6. handling of physical disturbances
7. prohibited items (and what isn't allow but can be check at front desk)
8. evacuation plan
9. Documentation/incident reports
Sunday, February 14, 2010
realization of limitations
So the estimated timeline on the security policy development of Vera with 206 Zulu is looking a bit out of scope for my project. It's expected to take about a year, and that doesn't even count the educational componets to be developed afterward.
TO DO:
talk to Josh some more about what and if there is something I can do for my capstone that would lend itself well into the larger picture....
TO DO:
talk to Josh some more about what and if there is something I can do for my capstone that would lend itself well into the larger picture....
Subscribe to:
Posts (Atom)