Monthly Archives: March 2011

How Many BC Staff? Part 2

I have to admit that I find the idea of running separate BC tables with separate staffs within the same hall completely bewildering—I cannot imagine how it could be supposed to improve the running of national fencing tournaments.

Even assuming we had enough BC volunteers to double up the staffing and were willing to pay extra for a second stage, additional computers, and a second microphone, I can’t see how it would work. We couldn’t simply split the hall evenly in half. Throughout any given day, the number of strips required to run a single event can vary from 40 or more for the pool round down to a single pod of 4 strips—and then the finals strip. As the 3 to 10 events of differing sizes we’d run each day progressed, we’d constantly need to shift the allocation of strips between each BC table—either that, or we’d need to split events themselves into smaller pieces, which would be even more confusing.

And then there’s that second microphone. We usually have two for Summer Nationals, so that the BC staff running team events can call their captains directly from the team table. In such close proximity, it’s pretty easy to see and hear when someone is already talking over the PA system. But with widely separated BC stages, announcements in a venue with a less-than-ideal sound system (as in Detroit this month) would be completely incomprehensible (instead of just mostly incomprehensible).

But there are already circumstances where we run, in effect, satellite BC tables. Take teams, for instance. At NACs, it’s less apparent, because team events are relatively small, but we usually run team events relatively independently from the individual events, from a dedicated floor-level team table. We set up a team computer with a single computer operator plus table staff for each team event, though at NACs, there are seldom multiple team events running at the same time. We run team events on Fencing Time, a huge improvement over when I started, when they were run entirely by hand. (I wrote in detail about running a team event in my BC Diary: Day 7, so check that out if you’re interested in more details—just scroll down past the Congress Meeting description.)

At Summer Nationals, where there is often more than one team event going on at once, we usually allocate a block of strips to the team table, to be used by all the team events as needed. There’s a bit of shifting strips back and forth throughout the day as needed, but with the team table staff there within easy reach of the BC chair, it’s easy to manage (as long as there are enough strips in the room for the total we need, which for SN is not always true—but that’s a different issue).

In the past, when we’ve used convention centers or hotels with split venues, we’ve created satellite BCs to work the second room, along with an armorer and trainer to handle problems as they occur. At the JOs at the Broadmoor in Colorado Springs a few years back, most of the saber events were isolated in a ballroom across the lake from the main part of the venue. And I still laugh at how John Carollo, bored serving as the lone trainer in a small, column-cluttered second room at a Reno NAC one March, insisted on acting as “personal executive assistant” to me and Gerrie Baumgart, posting sheets for us, and directing fencers to the proper places from which to address us.

If we had unlimited personnel, both BC staff and volunteers, we could set up a satellite table near the pods used for an event’s DEs, so that fencers wouldn’t need to walk all the way to the BC table and back each time they won a bout. It wouldn’t make much difference in the running of the tournament or in the overall length of the day, but it might be nicer for the fencers (though that’s one of my favorite parts of running tournaments—I’d miss talking with fencers through the whole DE tableau). We’d just need the one or two people to run the tableau, some visible place for them to sit out by the pods, and volunteers to run the bout slips back to the computer operators at the main BC table every so often.

In a way, this is what we do now when we assign DEs by pod; we just designate one referee as pod chief or pod captain to run a small section of the tableau out there, except that we don’t make the pod captains keep track of the completed bout slips. But if we had enough BC staff to run sections of the tableaux out near the strips where the bouts occur, that would free up referees from administration to work more bouts as referees. (Though I’m not sure I can imagine an épée event without Mr. Alperstein and his famous Alperstein System demonstrating the proper way to run a DE quadrant.)


1 Comment

Filed under Fencing

How Many BC Staff Does It Take To Run a National Fencing Tournament?

I realized from some of the comments on after my Playing With Numbers post that there are still a lot of misconceptions about how the bout committee works. One comment suggested that a more useful statistic than the ones I’d come up with would be the number of bout committee staff per total fencers—that more BC staff would make tournaments easier to run. Another suggested that splitting the hall in half and having two separate BC tables and staffs would ease tournament operations.

Neither is true.

(Don’t think for a minute, though, that we don’t need more BC staff. However, what we need is a larger pool of qualified staff to hire from, not more people up on the platform at any given time. We need more staff so we have time to train current staff to handle jobs like lead computer and BC chair, and time to train new people at the entry level. With more regional tournaments, we need that larger pool to help those organizers staff their events—we ought to have (and are already planning) a BC staff list like the referee list the FOC has on FRED.)

For a typical NAC, we hire a BC chair, a computer lead, three computer operators, and three table staff. If the NAC is very large, as the November and January NACs were this season, we’ll add another table person. If there are many events—say, more than 18 over 4 days, as in March this season, with all those Vet age-levels—we’ll also add a fourth table person. If there are team events, as at JOs or the March NAC, we’ll hire both a fourth table person and a fourth computer operator, because teams are run on a separate computer at a dedicated floor-level team table.

During the week or two before the tournament, the BC chair and computer lead use the strip management spreadsheet (which gives us the number of pools, DE bouts, and estimated times for each round of each event, among other useful information), to plan the staff schedule, which is sent out to all staff a few days before the tournament. Usually, computer staff each day work one computer with all the events in a single weapon. Table staff assignments vary a bit more—one person might work a single huge event, or one morning and one afternoon event, or one morning and several simultaneous small afternoon events.

The BC chair and computer lead normally fly in late Wednesday or early Thursday to be able to work on set-up day at the venue, usually along with a couple of other BC staff whose flights are early enough, unpacking the big black BC crate (just like the ones strips are shipped in). The computers are unpacked and the network set up: there is a master computer and three laptops set up as slaves; if there are team events, another laptop is set up as a team computer for when it will be needed.

(On tournament days, you’ll usually see quite a few more computers up on the platform. Tanya has one with access to Railstation, so she can check (and correct) entries and fencer profiles. The BC chair and computer lead usually bring their own laptops—I use mine to run the strip management spreadsheet for planning throughout the tournament. The head referees often bring their own machines, too. This proliferation of electronics got so bad, what with all the referees who want to charge phones or other devices, too, that this season we seriously upgraded our power strips; the tournament computers are always on a separate circuit from everything else.)

Here’s how an event typically runs:

Before the event closes, the table staff person (we’ve never figured out a good title for this position—event manager? competition coordinator? generic BC person?) retrieves the event sign and bio forms from the event folder, picks a marker color for the event, and stakes out a place at the BC table to hang the sign and set up the table side of the event. At close, she (usually a she, though by no means always) receives the printout of the no-shows from the registration desk and calls them over the PA system. Once that’s done, the list is given to that weapon’s computer operator to withdraw the no-shows, update the seeding list, and create the format sheet.

When the final seeding and format sheet are printed, the operator gives them to the table staff for copying and posting; once it’s posted, she announces that it’s up. Meanwhile, the computer operator sets the pools, checking for unresolved conflicts and that the larger pools are the higher-seeded pools. If solutions to the unresolved conflicts can be found within about 20 minutes, that is done; otherwise, they are left standing as unresolvable. (This process can be far more complicated than it first looks, requiring frequent reference to the seeding list and multiple cascading swaps.) Then a seeded copy of the pools is printed and given to the referee assigner, and a randomized copy of the pools and an alphabetical pool list are given to the table staff. The BC chair, by this point, has informed the table person of the strips her event is assigned to, and those are penciled onto the pool assignment sheet before it is copied and posted. (We prefer to post the seeding and pools separately, especially for point events, in order to allow a bit of time for fencers to verify their final seeding; unfortunately, few take advantage of the opportunity.)

Once the pool and strip assignments are posted and announced, the table person adds the strip numbers to the pool sheets, which she’s already marked with the event color to distinguish from the other events running that day. We usually try to spread any pools of 6 around among the 7s, to allow double-stripping the 7s more easily once the 6s are done. Then, all that’s needed are the referee assignments; some assigners (most, so far this season) are fairly quick at this, while others can take 30–40 minutes to allocate 50 or 60 referees to 30 or 40 pools. On occasion, the referees have not yet finished their morning meeting by the time the BC has events ready to go; some head referees make a point of getting to the platform in plenty of time, while others are not so conscious of the passage of time and therefore get calls from the BC chair asking if they are on their way yet.

When the assigner provides the referee list, the table person adds the referee names to the pool sheets; for a big event, we often split the list, and two or even three people will copy the referee names. Then the referees are called to pick up their sheets, and for the next 5 or 10 minutes, they’ll come in person or call to ask for second calls on fencers who’ve not yet shown up. Once the fencing is underway, the BC staff—both computer and table sides—for this event are free for most of the next 90–150 minutes, depending on the weapon.

What do we do with the free time? Read email and web-surf for those with connected devices, play computer games, read books, knit or cross-stitch, make group coffee runs if there’s a Starbucks or Peet’s in the convention center, shop at the vendors in the hall, work on other fencing matters (check seeding for the next day’s events, create training materials, other projects). Sometimes we even go watch fencing.

Ideally, about halfway through the pools, the table staff will tour the pools to see how many bouts are left on most strips and whether any have fallen significantly behind the rest, in which case, the assigner is informed and extra referees might be sent out to take bouts, if there is an extra strip available. Some assigners—but not all—keep a close watch on their events and handle this themselves. Sometimes, though, head referees get pulled into what we fondly refer to as “Things” (as in, “Sharon got called out to a strip for a Thing”)—requests to observe a particular referee or mediate a rules dispute or see that a black card is handled properly, so it never hurts for the BC to keep an eye on progress, too.

Once the pools start coming in, the table person checks them off on her master sheet and hands them to the computer operator for entry. Once all are entered, the operator prints out the round results, on which the table person draws a line between the ups and outs if there is a cut, and gets it copied, posted, and announced. While that is done, the operator prints the DE tableaux, once with divisions for the assigner and one without for posting. The assigner and the chair have usually already decided on the number of strips to be used for the DEs and how they will be grouped (in pods, in pairs or (preferably not) as singles), so the table person writes the strip assignments on the table and gets it copied, posted, and announced, too.

Meanwhile, back at the computer, the operator prints out the bout slips (at 4 per page, a full 256 table would be 32 pages for the first round alone), marks the sheets with the event color, and slices and sorts the bout slips in stacks for each bracket of the table, the process we refer to as “slicing and dicing.” When the assigner gives her the tableau with the referee assignments, the table person makes two copies and returns the original to the assigner. One set will be used at the table for recording bouts as they come in; the other is split up and given to the assigned referees with the bout slips for that section of the table.

After the slips have been sent out with the referees, the table person organizes her tableau. Most of us lay the pages out vertically in pairs—a table of 128 prints out in four pages, so pages 1 and 2 would be on the left and pages 3 and 4 to the right. The table person then numbers the bouts on the tableau (XSeed puts bout numbers on the bout slips but not on the tableau, so if we want to match them up, we need to do our own numbering) and then sorts the slips for each round into quadrants (or octants, in the case of an 8-page table of 256) so that there’s a stack for each page.

As bouts come in, the table person verifies that the winner is actually the fencer the slip says it is (you’d be amazed at how many fencers sign slips that say their opponent won), records the winner and the score on the paper tableau, writes up the next bout slip if there is one, and stacks the returned bout slips for the computer operator, who usually comes to pick them up more often than the table person gets a chance to take them over to the operator.

Why do we even run the paper tableaux? Why don’t we just enter results directly into the computer? When there are four or five events at once in the same weapon on a single computer, there’s less waiting for the fencers if there are separate lines to turn in bout slips for each event. It’s easier for the computer operator to enter the data accurately if she’s insulated from dealing directly with several hundred fencers. And with all the paper we produce, even marked with its distinguishing colors, it’s easy for bout slips to be misplaced, and the paper tableau gives us an additional record of each bout in such cases, rare though they are.

A table of 128 (or fewer) can be run easily by a single person; using two for an event that size is overkill. Only if we’ve got a BC trainee will we split a 128 table, so they can see how the event is done without it being overwhelming. For a table of 256, it’s nice to have two people for at least the early rounds of the DEs—8 pages of tableau is a bit of a stretch for one person to cover, though it’s nowhere near impossible. Sometimes, if there aren’t too many other things going on, we’ll have a computer operator or a volunteer act as a concierge of sorts, to check fencers’ bout slips as they arrive and direct them to the proper half of the tableau. (For a table of 512, which the BC has done once and hopes never to do again, we’d need at least 3 people—preferably 4—to run the 16 pages of tableau, and a concierge would be a necessity rather than a luxury.)

But those extra bodies are only useful for the first few rounds. From time to time, I’ve run a 256 saber table alone, and it’s always a rather breathless experience getting through the the first few rounds, because the bouts just keep coming and coming. (But it’s fun, too!) Big tableaux in foil and epee are easier to keep up with, because in those, the fencers tend to come in small waves—the bouts are longer and more of them go to time. But by the time any event fences down to the 64, one person is plenty for running the table. Getting the strips and referees assigned for the round of 8 is a snap (though less so than it used to be for events using replay these days); once the fencing is completed, all the table person needs to do is arrange and mark the bio forms according to placement for the medal presentation and then make sure the bio forms are returned to the computer operator for the event folder.

For tournaments with many smaller events (in Detroit we held 44 events), it’s common for a table person to run two or three events simultaneously. When events are only two or three pools, if that, and the DEs fit on a single page, it’s easy to run multiple events as long as each has its own color, and it’s far less stressful than adding extra people to the crowd already on the BC platform.

But what about that idea of having two separate BCs in the same hall? Wouldn’t that solve the crowding problem? I’ll talk about that next time, along with running teams and a few other ideas.


Filed under Fencing

Playing With Numbers

In the course of avoiding working on my taxes this morning, I had fun playing around with this season’s national tournament numbers. I’d been struck since I got home from Detroit by the number of comments on Facebook and Fencing.Net about how well run the Detroit NAC was and got to wondering whether most people really understand the reason for the difference between a “well-run” NAC like Detroit and one with jammed-up days and late nights like Milwaukee last November.

So I put together a little spreadsheet with the number of strips, events, days, and individual and team entries for every event so far this season. Then I started looking at the averages (means, that is) to see what I could see.

I looked at “events per day,” which range from 2 individual and 1 team for the December NAC to 10.5 for the October Div. I/Vet in Cincinnati. “Individual fencers per day” is also interesting—the extremes are 217 at the December NAC and 585 for November’s Junior/Cadet/Youth 14 in Milwaukee. While I was at it, I also worked up “fencers per strip” and “fencers per strip per day,” along with the analogous stats for teams.

Neither the number of fencers per day nor the number of events per day correlate well with what I’ll call “perceived difficulty of tournament.” Some NACs, like JOs, are large but have relatively few events, so they aren’t too difficult to run. Other tournaments have both large numbers and a lot of events, so they are far more complicated and stressful.

Looking back at this season so far, the easiest events to run were the December NAC, of course, with only 6 individual events and 3 team events, and this month’s Div 2/3/Vet NAC in Detroit. Neither had painfully tight schedules, and competition ended early enough each day at both that officials (and fencers) could get real meals in restaurants each evening. The most difficult tournaments were the November and January NACs—both lots of large events with large entry numbers, both with very late nights throughout.

“Individual fencers per strip” turned out to correlate perfectly with my “perceived difficulty of tournament”:

  • December NAC: 19.7
  • March NAC: 34.63
  • JOs: 40.1
  • October NAC: 44.8
  • January NAC: 45.47
  • November NAC: 51.98

Once I saw this, of course, I had to run the projected numbers for the April NAC in Portland and for SN in Reno to see what their “fencers per strip” would look like.

Portland, with a schedule similar (fewer but somewhat larger individual events, more teams) to the Detroit NAC, comes up in the same range, 36.02.

And SN? Brace yourself—it’s an impressive 108.84. (And that doesn’t even include teams.)

So then I got to wondering—if we wanted to run SN so that its atmosphere and “perceived level of difficulty” were equivalent to that of the most difficult NAC this season (November, with a “fencers per strip” of 51.98), how many strips would we need instead of the 60–65 we’ll have? 128.

If we wanted a downright comfortable SN, with evenings running no later than 8:00 or 8:30, like Detroit this month, say a “fencers per strip” of 35? That would take 190 strips. I can just imagine the look on Sharon Everson’s face if she were told she needed to hire referees for a 190-strip SN.

Sometimes all you can do is laugh. (And it definitely beats doing taxes.)

1 Comment

Filed under Fencing

Detroit, Part 2

Sure, the LOC for the Detroit NAC was great. Patrick Webster and his sister, Amy Webster (who also worked as a BC trainee for the NAC), did a fabulous job creating an LOC who did everything we could have wished for to help us run the tournament smoothly.

But what really set this Detroit LOC apart was their outreach. They weren’t just helping us out—they were selling fencing to their community. It wasn’t just the usual newspaper articles and TV stories, either, though there were those. There was also this:

This exhibition was set up in a room right next door to the venue, and every so often, the energetic Bobby Smith (En Garde! Detroit, PWF and Wayne State alumnus) would come through the venue, leading a school group or a group of parents and kids, explaining the sport as they toured the room. He often ended the tours right in front of the bout committee, drafting one of us to explain a bit about what we do at tournaments. Then he’d ask everybody if they were interested in learning more about fencing to take a look at the club card they’d been given (which were also in our goody bags):

“Take a look on the back and see whether there’s a club in your area. If you’re interested in learning more, I can find someone here today who can talk to you about their programs.”

Which is, I suppose, one of the virtues of having a huge crew of LOC volunteers—at any given time, the odds of finding someone from a specific club in the division were pretty good. It was really nice to see a USFA division that understands that when more people are interested in fencing and find a way to learn more about the sport, all of the division’s clubs benefit.

Leave a comment

Filed under Fencing