SR3R Project Forum

Discussion and debate for the SR3R Project
It is currently Wed Dec 11, 2019 4:33 pm

All times are UTC - 5 hours




Post new topic Reply to topic  [ 3 posts ] 
Author Message
PostPosted: Wed Jul 11, 2012 8:53 am 
Offline
Site Admin

Joined: Tue Jul 17, 2007 11:39 am
Posts: 875
Location: Boston
Bringing this back over from Dumpshock, where I posted it along with some motivation.

For this discussion I'm going to consider Seattle only—the security rating system should to some extent allow application to different cities and countries, but I don't want to spend the time thinking about where that might break down right now.

Canon rules for security response do exist (New Seattle p111), but they're complete garbage—the issue of no minute-scale timekeeping was "addressed" by making security capable of teleportation, with two patrol vehicles carrying two security officers each arriving on scene in a B-rated zone no more than 63 seconds after the start of a fight. Even worse, whoever wrote this section decided to base response on initiative passes—so the speed of the arriving security depends on the Initiative of the participants of the combat. If a brawl between a bunch of unaugmented average individuals (no more than 4+1d6 initiative) is going on, a wired speedsam at 14+4d6 initiative jumping into the fray will triple the speed of the responding security. (If you're tempted to say "of course, it's a more serious threat now", note that the unaugmented crew could easily be using rocket launchers, flamethrowers, and mortars.)

So we can dispense with the numbers in New Seattle, at least. Looking at the details of the response levels, it's clear that the rules assume that the fight is more or less taking place in public (in the city, rather than in a facility), with the response being from Lone Star or the appropriate local security contractor. I'm going to start by considering what I believe to be the more common case: security response inside a building or facility.

Some terminology for convenience:
    Unit (or Security Unit): one or more security assets which are dispatched collectively and which travel and operate in a closely coordinated fashion (so two security officers and a drone traveling in a group are one unit; if the drone is making use of its different mobility characteristics to arrive ahead of the officers, or by a substantially different route without deliberate effort to arrive at the same time, it's a separate unit. For simplicity the "synchronized travel" requirement is assumed to come into effect when the security assets are "sufficiently close" to the destination—glossing over little details like starting from different places but making rendezvous before it could actually matter)
  • Response: the deployment of one or more units resulting from fulfillment of a specific set of conditions (including the passage of time). In the New Seattle rules, each different stage on the template except for "Aware of Problem" is a response. Unless otherwise specified, a response involves deployment to the location of the incident causing initial fulfillment of conditions. A response begins when the unit commences travel from its initial location to the response point (see below).
  • Response point: the location to which a response is deployed.
  • Response order: an instruction to conduct a response.
  • Response delay: time between a response order and the resulting response. In general a measure of how long it takes the unit involved to get ready.
  • Response time: time between a response and arrival at the response point. Travel time.
  • Total response time: response time plus response delay.
  • Facility: a contiguous region to which responses may be directed with impunity (usually one or more buildings all on a single lot under single control; may also be specific floors of a multi-occupancy building, etc.) which is "relatively compact" (response times from on-site resources are substantially more similar to each other than to response times from off-site resources—the Renraku Arcology, notably, is not a single facility under this definition).

Also, to start out I'm going to make a simplifying assumption that I think can be removed later: that fog of war is minimal. Responses are to a specific known response point, a unit is considered to have arrived on-scene when it arrives at the response point, there are no chain-of-command issues or similar that cause responses to not occur when they otherwise might.

Different parts of the potential response can be characterized in a reasonable-seeming fashion as follows:

  • Deployed security: ready at a moment's notice, give or take. For physical non-Rigger security assets, probably on patrol or stationed on guard somewhere. Essentially no response delay, response time can vary widely based on deployed location relative to response point.
  • On-duty security: in a state of "active waiting", probably in a ready room or similar. Response delay on the order of tens of seconds, response time dependent on placement of ready room—locations usually laid out deliberately for roughly equidistant coverage of facility.
  • On-site reserves: present on-site but in no particular state of readiness. Response delay on the order of minutes.
  • Local rapid response: active waiting, but somewhere else. Response delay on the order of tens of seconds, but response time on the order of ten minutes.
  • Local security: response delay on the order of minutes, response time on the order of ten minutes, figure total response time on the order of twenty minutes.
  • Regional rapid response: active waiting, but somewhere really else. Total response time on the order of tens of minutes (exact distribution may vary; personnel deploying by van may have response delay of tens of seconds but response time of tens of minutes, while deploying aircraft may have response delay of ten minutes or more but response time of ten minutes or less)

~J

_________________
Failure: when your best just isn't good enough.


Top
 Profile  
 
PostPosted: Sun Sep 16, 2012 11:34 am 
Offline
Forum Admin

Joined: Tue Jul 17, 2007 11:50 am
Posts: 827
Location: DeeCee
Since you posted this at dumpshock and people responded there, I trust you'll be curating that thread and post the summary or conclusion back here when it's done?


Top
 Profile  
 
PostPosted: Sun Sep 16, 2012 4:12 pm 
Offline
Site Admin

Joined: Tue Jul 17, 2007 11:39 am
Posts: 875
Location: Boston
Yep, that's the plan.

~J

_________________
Failure: when your best just isn't good enough.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC - 5 hours


Who is online

Users browsing this forum: No registered users and 0 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group