Viper Controls

image03

The Viper is the primary space fighter of the Colonial Fleet.  It comes in several varieties, from the Mark II (shown above), to the Mark VII (the latest version).  Each is made for a single pilot, and the controls allow the pilot to navigate short distances in space to dogfight with enemy fighters.

image09

Mark II Viper Cockpit

The Mark II Viper is an analog machine with a very simple Dradis, physical gauges, and paper flight plans.  It is a very old system.  The Dradis sits in the center console with the largest screen real-estate.  A smaller needle gauge under the Dradis shows fuel levels, and a standard joystick/foot pedal system provides control over the Viper’s flight systems.

image06

Mark VII Viper Cockpit

The Viper Mk VII is a mostly digital cockpit with a similar Dradis console in the middle (but with a larger screen and more screen-based controls and information).  All other displays are digital screens.  A few physical buttons are scattered around the top and bottom of the interface.  Some controls are pushed down, but none are readable.  Groups of buttons are titled with text like “COMMS CIPHER” and “MASTER SYS A”.

Eight buttons around the Dradis console are labeled with complex icons instead of text.

image07 image08

When the Mk VII Vipers encounter Cylons for the first time, the Cylons use a back-door computer virus to completely shut down the Viper’s systems.  The screens fuzz out in the same manner as when Apollo gets caught in an EMP burst.

The Viper Mk VII is then completely uncontrollable, and the pilot’s’ joystick-based controls cease to function.

Overall, the Viper Mk II is set up similarly to a WWII P-52 Mustang or early production F-15 Eagle, while the Viper Mk VII is similar to a modern-day F-16 Falcon or F-22 Raptor .

 

Usability Concerns

The Viper is a single seat starfighter, and appears to excel in that role.  The pilots focus on their ship, and the Raptor pilots following them focus on the big picture.  But other items, including color choice, font choice, and location are an issue.

Otherwise, Items appear a little small, and it requires a lot of training to know what to look for on the dashboards. Also, the black lines radiating from the large grouper labels appear to go nowhere and provide no extra context or grouping.  Additionally, the controls (outside of the throttle and joystick) require quite a bit of reach from the seat.

Given that the pilots are accelerating at 9+ gs, reaching a critical control in the middle of a fight could be difficult.  Hopefully, the designers of the Vipers made sure that ‘fighting’ controls are all within arms reach of the seat, and that the controls requiring more effort are secondary tasks.

Similarly, all-caps text is the hardest to read at a glance, and should be avoided for interfaces like the Viper that require quick targeting and actions in the middle of combat.  The other text is very small, and it would be worth doing a deeper evaluation in the cockpit itself to determine if the font size is too small to read from the seat.

If anyone reading this blog has an accurate Viper cockpit prop, we’d be happy to review it! 

Fighter pilots in the Battlestar Galactica universe have quick reflexes, excellent vision, and stellar training.  They should be allowed to use all of those abilities for besting Cylons in a dogfight, instead of being forced to spend time deciphering their Viper’s interface.

Explorer Surveillance

The Control Room of Jurassic Park has a basic video/audio feed to the Tour Explorers that a controller (or, in this case, John Hammond) can use to talk to the tour participants.  He is able to switch to different cameras using the number keys on the keyboard attached to the monitor. The cameras themselves appear to be fixed in place.

JurassicPark_FordSurveillance01

We never see the cameras themselves in the Explorers, but we do see Malcolm tap on one of the cameras during the tour while Hammond is watching it’s feed, so they are visible to the riders.

Hammond occasionally speaks through his audio link, and can hear a constant audio feed from the Explorers. He has some kind of mute button (he says a couple disparaging comments that the other characters don’t appear to hear), but the feed from the Explorers is real-time. It isn’t obvious how he switches between the different Explorers’ audio feeds, or whether he hears both Explorers simultaneously. Continue reading

Ford Explorer Status

image00

One computer in the control room is dedicated to showing the status of the Jeeps out on tour, and where they currently are on the island.

Next to the vehicle outline, we see the words “Vehicle Type: Ford Explorer” (thank you, product placement) along with “EXP” 4–7.  EXP 4 & 5 look unselected, but have green dots next to them, while EXP 6 & 7 look selected with red dots next to them.  No characters interact with this screen. Mr. Arnold does tap on it with a pen (to make a point though, not to interact with it).

On the right hand side of the screen also see a top-down view of the car with the electric track shown underneath, and little red arrows pointing forward.  Below the graphic are the words “13 mph”.  The most visible and obvious indicator on the screen is the headlights.  A large “Headlights On” indicator is at the top of the screen, with highlighted cones coming out of the Jeep where the headlights are on the car. Continue reading

Weather Monitor

Jurassic Park’s weather prediction software sits on a dedicated computer. It pulls updates from some large government weather forecast (likely NOAA).  The screen is split into three sections (clockwise from top left):

  1. 3D representation of the island and surrounding ocean with cloud layers shown
  2. plan view of the island showing cloud cover
  3. A standard climate metrics along the bottom with data like wind direction (labeled Horizontal Direction), barometric pressure, etc.

We also see a section labeled “Sectors”, with “Island 1” currently selected (other options include “USA” and “Island 2”…which is suitably mysterious).

JurassicPark_weather01

Using the software, they are able to pan the views to the area of ocean with an incoming tropical storm.  The map does not show rainfall, wind direction, wind speed, or distance; but the control room seems to have another source of information for that.  They discuss the projected path of the storm while looking at the map.

JurassicPark_weather03

Missing Information

The park staff relies on the data from weather services of America and Costa Rica, but doesn’t trust their conclusions (Muldoon asks if this storm will swing out of the way at the last second despite projections, “like the last one”).  But the team at Jurassic Park doesn’t have any information on what’s actually happening with the storm.

Unlike local weather stations here in the U.S., or sites like NOAA weather maps, there is in this interface a lack of basic forecasting information like, say, precipitation amount, precipitation type, individual wind speeds inside the storm, direction, etc… Given the deadly, deadly risks inherent in the park, this seems like a significant oversight.

The software has spent a great deal of time rendering a realistic-ish cloud (which, we should note looks foreshadowingly like a human skull), but neglects to give information that is taken for granted by common weather information systems.

Prediction

When the park meteorologist isn’t on duty, or isn’t awake, or has his attention on the Utahraptor trying to smash its way into the control room, the software should provide some basic information to everyone on staff:

  • What does the weather forecast look like over the next few hours and days?

When the weather is likely to be severe, there’s more information, and it needs to urgently get the attention of the park staff.

  • What’s the prediction?
  • Which parts of the park will be hit hardest?
  • Which tours and staff are in the most dangerous areas?
  • How long will the storm be over the island?

If this information tied into mobile apps or Jurassic Park’s wider systems, it could provide alerts to individual staff, tourists, and tours about where they could take shelter.

JurassicPark_weather02

Make the Information Usable

Reorienting information that is stuck on the bottom bar and shifting it into the 3d visual would lower the cognitive load required to understand everything that’s going on.  Adding in visuals for other weather data (taken for granted in weather systems now) would bring it at least up to standard.

Finally, putting it up on the big monitor either on demand or when it is urgent would make it available to everyone in the control room, instead of just whoever happened to be at the weather monitor. Modern systems would push the information information out to staff and visitors on their mobile devices as well.

With those changes, everyone could see weather in real time to adjust their behavior appropriately (like, say, delaying the tour when there’s a tropical storm an hour south), the programmer could check the systems and paddocks that are going to get hit, and the inactive consoles could do whatever they needed to do.

Sleep Pod—Wake Up Countdown

On each of the sleep pods in which the Odyssey crew sleep, there is a display for monitoring the health of the sleeper. It includes some biometric charts, measurements, a body location indicator, and a countdown timer. This post focuses on that timer.

To show the remaining time of until waking Julia, the pod’s display prompts a countdown that shows hours, minutes and seconds. It shows in red the final seconds while also beeping for every second. It pops-up over the monitoring interface.

image03

Julia’s timer reaches 0:00:01.

The thing with pop-ups

We all know how it goes with pop-ups—pop-ups are bad and you should feel bad for using them. Well, in this case it could actually be not that bad.

The viewer

Although the sleep pod display’s main function is to show biometric data of the sleeper, the system prompts a popup to show the remaining time until the sleeper wakes up. And while the display has some degree of redundancy to show the data—i.e. heart rate in graphics and numbers— the design of the countdown brings two downsides for the viewer.

  1. Position: it’s placed right in the middle of the screen.
  2. Size: it’s roughly a quarter of the whole size of the display

Between the two, it partially covers both the pulse graphics and the numbers, which can be vital, i.e. life threatening—information of use to the viewer. Continue reading

Contact!

image04

Jack lands in a ruined stadium to do some repairs on a fallen drone. After he’s done, the drone takes a while to reboot, so while he waits, Jack’s mind drifts to the stadium and the memories he has of it.

Present information as it might be shared

Vika was in comms with Jack when she notices the alarm signal from the desktop interface. Her screen displays an all-caps red overlay reading ALERT, and a diamond overlaying the unidentified object careening toward him. She yells, “Contact! Left contact!” at Jack.

image02

As Jack hears Vika’s warning, he turns to look drawing his pistol reflexively as he crouches. While the weapon is loading he notices that the cause of the warning was just a small, not-so-hostile dog. Continue reading

Red Phone

After the gravitic distortion is discovered, Barcalow flips a toggle switch upwards with his thumb. As Ibanez confirms that “Gravity is 225 and rising,” the light on the bridge turns red, and Barcalow turns to a monitor.

The monitor (seen above) features a video window in the top center. Along the left side of the screen 11 random numbers report the COMM STATS INTERSHIP. Along the right side of the screen 11 other random numbers report the COMM STATS INTRASHIP. Beneath the video some purple bars slide in and out from a central column of red rectangles. One of these rectangles is bright yellow. Beneath that a section reports SCANNING FREQUENCIES as 21 three-character strings, some of which are highlighted as red. At the bottom of the screen blue and yellow-green smears race back and forth across a rectangle. Everything is in Starship Troopers‘ signature saturated colors and a block font like Microgramma or Eurostile.

These details are almost immediately obscured, as Deladier looks up from her laptop (looking presciently like a modern Macbook Air with its aluminum casing) to look at the video monitor to demand a “Report,” and the video grows larger to fill the screen.

StarshipTroopers-RedPhone 04

StarshipTroopers-RedPhone 07

Here the snarky description must pause for some analysis.

Analysis

The red alert mechanism is actually pretty good. Both the placement of its switch at shoulder level and the fact that it must be flipped up help prevent against accidental activation. The fact that it’s a toggle switch means it can be undone with ease if necessary. The red light immediately provides feedback to everyone on the bridge (and throughout the ship?) that the system has gone into a red alert. No other action is necessary to alert the person who needs to be informed, i.e. the Captain. The only other improvement might be a klaxon warning to alert others who are sleeping, but it’s entirely possible that very thing is happening elsewhere on the ship, and the bridge is spared that distraction. So full marks.

The user interface on the monitor seems pretty crappy though. If someone is meant to monitor COMM STATS—intership or intraship—I cannot imagine how a column of undifferentiated numbers helps. A waveform would be more useful to track activity across a spectrum. Something. Anything other than a stack of numbers that are hard to read and interpret.

The SCANNING FREQUENCIES is similarly useless. Sure, it’s clear that the ship’s systems are scanning those frequencies, but the three-character strings require crew to memorize what those mean. If those frequencies are defined—as you imagine they must be to be at all useful as static variables—then you can remove the cognitive weight of having to memorize the differences between JL5 and LQ7 by giving them actual names, and only displaying the ones that have activity on them, and what that activity means. Does someone need to listen in? Shouldn’t that task be apparent? And why would that need to be shown generally to the bridge, rather than to a communications officer? And I’m not sure what those purple squiggles mean. It’s nice that they’re animated I guess, but if they’re meant to help the user monitor some variable, they’re too limited. Like the sickbay display on the original Star Trek, knowing the current state is likely not as useful as knowing how the information is trending over time. (See page 261 for more details on this.) So trendlines would be better here. The little sweeping candy colored smears are actually okay, though, presuming that it’s showing that the system is successfully sweeping all frequencies for additional signal. Perhaps a bit distracting, but easy to habituate.

It’s nice that the video screen fills the screen to match the needs of the communicators. But as with so many other sci-fi video calls, no effort is made to explain where the camera is on this thing. Somehow they can just look at the eyes of the other person on the monitor, and it works. This feels natural to the actors, looks natural to the audience, and would be natural in real life, but until we can figure out how to embed a camera within a screen, this can’t work this way, and we’re stuck with the gaze monitoring problem raised in the Volumetric Projection chapter of the book with the Darth Vader example.

So, all in all, this interface is mostly terrible until it becomes just a videophone. And even then there are questions.

Snarky description continues

Picking up the description where I left off, after the Captain demands a report, Barcalow tells her quickly “Captain, we’re in the path of an unidentified object heading toward us at high speed.” Ibanez then looks down at her monitor at the gravity well animation, to remark that the “Profile suggests an asteroid, ma’am.” You know, just before looking out the window.

STARSHIP_TROOPERS_asteroid

Honestly, that’s one of the funniest two-second sequences in the whole movie.

Otto’s Manual Control

WallE-Otto02

WallE-Otto06

When it refused to give up authority, the Captain wrested control of the Axiom from the artificial intelligence autopilot, Otto. Otto’s body is the helm wheel of the ship and fights back against the Captain. Otto wants to fulfil BNL’s orders to keep the ship in space. As they fight, the Captain dislodges a cover panel for Otto’s off-switch. When the captain sees the switch, he immediately realizes that he can regain control of the ship by deactivating Otto. After fighting his way to the switch and flipping it, Otto deactivates and reverts to a manual control interface for the ship.

The panel of buttons showing Otto’s current status next to the on/off switch deactivates half its lights when the Captain switches over to manual. The dimmed icons are indicating which systems are now offline. Effortlessly, the captain then returns the ship to its proper flight path with a quick turn of the controls.

One interesting note is the similarity between Otto’s stalk control keypad, and the keypad on the Eve Pod. Both have the circular button in the middle, with blue buttons in a semi-radial pattern around it. Given the Eve Pod’s interface, this should also be a series of start-up buttons or option commands. The main difference here is that they are all lit, where the Eve Pod’s buttons were dim until hit. Since every other interface on the Axiom glows when in use, it looks like all of Otto’s commands and autopilot options are active when the Captain deactivates him.

A hint of practicality…

The panel is in a place that is accessible and would be easily located by service crew or trained operators. Given that the Axiom is a spaceship, the systems on board are probably heavily regulated and redundant. However, the panel isn’t easily visible thanks to specific decisions by BNL. This system makes sense for a company that doesn’t think people need or want to deal with this kind of thing on their own.

Once the panel is open, the operator has a clear view of which systems are on, and which are off. The major downside to this keypad (like the Eve Pod) is that the coding of the information is obscure. These cryptic buttons would only be understandable for a highly trained operator/programmer/setup technician for the system. Given the current state of the Axiom, unless the crew were to check the autopilot manual, it is likely that no one on board the ship knows what those buttons mean anymore.

WallE-Otto03

Thankfully, the most important button is in clear English. We know English is important to BNL because it is the language of the ship and the language seen being taught to the new children on board. Anyone who had an issue with the autopilot system and could locate the button, would know which button press would turn Otto off (as we then see the Captain immediately do).

Considering that Buy-N-Large’s mission is to create robots to fill humans’ every need, saving them from every tedious or unenjoyable job (garbage collecting, long-distance transportation, complex integrated systems, sports), it was both interesting and reassuring to see that there are manual over-rides on their mission-critical equipment.

…But hidden

The opposite situation could get a little tricky though. If the ship was in manual mode, with the door closed, and no qualified or trained personnel on the bridge, it would be incredibly difficult for them to figure out how to physically turn the ship back to auto-pilot. A hidden emergency control is useless in an emergency.

Hopefully, considering the heavy use of voice recognition on the ship, there is a way for the ship to recognize an emergency situation and quickly take control. We know this is possible because we see the ship completely take over and run through a Code Green procedure to analyze whether Eve had actually returned a plant from Earth. In that instance, the ship only required a short, confused grunt from the Captain to initiate a very complex procedure.

Security isn’t an issue here because we already know that the Axiom screens visitors to the bridge (the Gatekeeper). By tracking who is entering the bridge using the Axiom’s current systems, the ship would know who is and isn’t allowed to activate certain commands. The Gatekeeper would either already have this information coded in, or be able to activate it when he allowed people into the bridge.

For very critical emergencies, a system that could recognize a spoken ‘off’ command from senior staff or trained technicians on the Axiom would be ideal.

Anti-interaction as Standard Operating Procedure

WallE-Otto05

The hidden door, and the obscure hard-wired off button continue the mission of Buy-N-Large: to encourage citizens to give up control for comfort, and make it difficult to undo that decision. Seeing as how the citizens are more than happy to give up that control at first, it looks like profitable assumption for Buy-N-Large, at least in the short term. In the long term we can take comfort that the human spirit–aided by an adorable little robot–will prevail.

So for BNL’s goals, this interface is fairly well designed. But for the real world, you would want some sort of graceful degradation that would enable qualified people to easily take control in an emergency. Even the most highly trained technicians appreciate clearly labeled controls and overrides so that they can deal directly with the problem at hand rather than fighting with the interface.

The Gatekeeper

WallE-Gatekeeper04

After the security ‘bot brings Eve across the ship (with Wall-e in tow), he arrives at the gatekeeper to the bridge. The Gatekeeper has the job of entering information about ‘bots, or activating and deactivating systems (labeled with “1”s and “0”s) into a pedestal keyboard with two small manipulator arms. It’s mounted on a large, suspended shaft, and once it sees the security ‘bot and confirms his clearance, it lets the ‘bot and the pallet through by clicking another, specific button on the keyboard.

The Gatekeeper is large. Larger than most of the other robots we see on the Axiom. It’s casing is a white shell around an inner hardware. This casing looks like it’s meant to protect or shield the internal components from light impacts or basic problems like dust. From the looks of the inner housing, the Gatekeeper should be able to move its ‘head’ up and down to point its eye in different directions, but while Wall-e and the security ‘bot are in the room, we only ever see it rotating around its suspension pole and using the glowing pinpoint in its red eye to track the objects its paying attention to.

When it lets the sled through, it sees Wall-e on the back of the sled, who waves to the Gatekeeper. In response, the Gatekeeper waves back with its jointed manipulator arm. After waving, the Gatekeeper looks at its arm. It looks surprised at the arm movement, as if it hadn’t considered the ability to use those actuators before. There is a pause that gives the distinct impression that the Gatekeeper is thinking hard about this new ability, then we see it waving the arm a couple more times to itself to confirm its new abilities.

WallE-Gatekeeper01

The Gatekeeper seems to exist solely to enter information into that pedestal. From what we can see, it doesn’t move and likely (considering the rest of the ship) has been there since the Axiom’s construction. We don’t see any other actions from the pedestal keys, but considering that one of them opens a door temporarily, it’s possible that the other buttons have some other, more permanent functions like deactivating the door security completely, or allowing a non-authorized ‘bot (or even a human) into the space.

An unutilized sentience

The robot is a sentient being, with a tedious and repetitive job, who doesn’t even know he can wave his arm until Wall-e introduces the Gatekeeper to the concept. This fits with the other technology on board the Axiom, with intelligence lacking any correlation to the robot’s function. Thankfully for the robot, he (she?) doesn’t realize their lack of a larger world until that moment.

So what’s the pedestal for?

It still leaves open the question of what the pedestal controls actually do. If they’re all connected to security doors throughout the ship, then the Gatekeeper would have to be tied into the ship’s systems somehow to see who was entering or leaving each secure area.

The pedestal itself acts as a two-stage authentication system. The Gatekeeper has a powerful sentience, and must decide if the people or robots in front of it are allowed to enter the room or rooms it guards. Then, after that decision, it must make a physical action to unlock the door to enter the secure area. This implies a high level of security, which feels appropriate given that the elevator accesses the bridge of the Axiom.

Since we’ve seen the robots have different vision modes, and improvements based on their function, it’s likely that the Gatekeeper can see more into the pedestal interface than the audience can, possibly including which doors each key links to. If not, then as a computer it would have perfect recall on what each button was for. This does not afford a human presence stepping in to take control in case the Gatekeeper has issues (like the robots seen soon after this in the ‘medbay’). But, considering Buy-N-Large’s desire to leave humans out of the loop at each possible point, this seems like a reasonable design direction for the company to take if they wanted to continue that trend.

It’s possible that the pedestal was intended for a human security guard that was replaced after the first generation of spacefarers retired. Another possibility is that Buy-N-Large wanted an obvious sign of security to comfort passengers.

What’s missing?

We learn after this scene that the security ‘bot is Otto’s ‘muscle’ and affords some protection. Given that the Security ‘bot and others might be needed at random times, it feels like he would want a way to gain access to the bridge in an emergency. Something like an integrated biometric scanner on the door that could be manually activated (eye scanner, palm scanner, RFID tags, etc.), or even a physical key device on the door that only someone like the Captain or trusted security officers would be given. Though that assumes there is more than one entrance to the bridge.

This is a great showcase system for tours and commercials of an all-access luxury hotel and lifeboat. It looks impressive, and the Gatekeeper would be an effective way to make sure only people who are really supposed to get into the bridge are allowed past the barriers. But, Buy-N-Large seems to have gone too far in their quest for intelligent robots and has created something that could be easily replaced by a simpler, hard-wired security system.

WallE-Gatekeeper05

Alien Stasis Chambers

The alien stasis chambers have recessed, backlit touch controls. The shape of each looks like a letterform. (Perhaps in Proto-Indo-European language that David was studying at the start of the film?) David is able to run his fingers along and tap these character shapes in particular sequences to awaken the alien sleeping within.

vlcsnap-00003

The writing/controls take up quite a bit of room, on both the left and right sides of the chamber near the occupant’s head. It might seem a strange decision to have controls placed this way, since a single user might have to walk around the chamber to perform tasks. But a comparison of the left and right side shows that the controls are identical, and so are actually purposefully redundant. This way it doesn’t matter which side of the chamber a caretaker was on, he could still operate the controls. Two caretakers might have challenges “walking over” each other’s commands, especially with the missing feedback (see below).

Prometheus-295

Having the writing/controls spread over such a large area does seem error prone. In fact in the image above, you can see that David’s left hand is resting with two fingers “accidentally” in the controls. (His other hand was doing the button pressing.) Of course this could be written off as “the technology is not made for us, it’s made for an alien race,” but the movie insists these aliens and humans share matching DNA, so apart from being larger in stature, they’re not all that different.

Two things seem missing in the interface. The first is simple feedback. When David touches the buttons, they do not provide any signal that his touch has been received. If he didn’t apply enough pressure to register his touch, he wouldn’t have any feedback to know that until an error occurred. The touch walls had this feedback, so it seems oddly missing here.

The second thing missing is some status indicator for the occupant. Unless that information is available on wearable displays, having it hidden forces a caretaker to go elsewhere for the information or rely solely on observation, which seems far beneath the technological capabilities seen so far in the complex. See the Monitoring section in Chapter 12 of Make it So for other examples of medical monitoring.