1.01	LIGHTING CONSOLE AND ACCESSORIES
A.	General
1.	The lighting control console shall be a microprocessor-based system specifically designed to provide complete control of stage, studio, and entertainment lighting systems. The console shall be the Ion Xe as manufactured by Electronic Theatre Controls, Inc., or equal.
2.	The system shall provide control of either 2,048 or 12,288 outputs on a maximum of 32,768 control channels, which may be any number from 1 to 99,999. Systems that require external co-processing to control 12,288 outputs shall not be acceptable. Output shall be distributed over a 10/100 MB Ethernet network using Net3/ACN, ETCNet2, Avab and/or Artnet (multi-cast) protocols. The user shall be able to control the application of protocols at an individual address level. 
3.	The system shall support full bi-directional RDM communication with compatible devices via Net3 DMX/RDM Gateways. RDM communication shall adhere to ANSII standard E1.20-2006 Entertainment Technology – RDM – Remote Device Management Over DMX512 Networks. Supported RDM features shall include:
a.	Discovery and Identification of RDM capable devices
b.	Setting of start addresses, operating modes and additional settings as exposed by connected devices and controllable via RDM
c.	Viewing of Sensor data as provided by connected devices
d.	Error reporting as provided by connected device 
4.	A maximum of 10,000 cues, 1000 groups, 1000 presets, 4 x 1000 palettes (Intensity, Focus, Color and Beam), 99,999 macros, 1000 effects, 1000 curves, 1000 Color Paths and 1000 snapshots may be contained in non-volatile electronic memory and stored to an onboard solid-state hard drive or to any USB storage device. 
5.	Recorded cue lists may be played back simultaneously on a maximum of 200 faders. Channels shall respond to cue information by last instruction with discrete rate control provided for all cues. The console may be placed in Tracking or Cue Only mode by the user as a system default and overridden on individual record actions as required. HTP/LTP intensity flags, assert, proportional, intensity master or manual master fade control. Priority and Background Priority may be placed on each cue list. It shall also be possible for a cue list to contribute to playback background states or to withhold such contributions.
6.	A Master Playback fader pair shall be provided. The fader pair may execute crossfades or all-fades, with IFCB cue level timing, 
7.	Fader wings (standard or motorized) provide additional playback faders (up to 200), additive or inhibitive submasters (up to 999), and grand master control. Presets and IFCB palettes may be loaded to faders for playback control, either individually or in user-defined lists. Virtual fader control is also provided. 
8.	A high-resolution level wheel shall be provided to control intensity for selected channels and scrolling within selected displays. Four pageable encoders shall be provided for control of non-intensity parameters. Non-intensity encoders toggle between coarse and fine control. The expand function for frame table devices shall provide a graphic representation of all images and colors in the associated device for instant selection. A graphic shutter representation shall provide additional control of shutter parameters. The display shall also provide an indication of the current value for the associated parameter, based on channel selection. A high-resolution rate wheel, which may also be used for fader paging shall be provided.
9.	Control surface buttons shall be backlit. This backlighting provides indication of functional states. Backlight intensity shall be user controllable, and shall automatically dim after a defined period of inactivity.
10.	Control and programming features for automated fixtures shall also include: a standard library of fixture profiles, the ability to copy and edit existing profiles and create new profiles, patch displays including channel and output addressing, 16-bit fade resolution, color characterization allowing color in up to six different color spaces.
11.	System information, including playback status, live output and blind values for all record targets shall be displayed on a maximum of two external high resolution monitors, which may also be multi-touch touch-screens. Every display shall support three user-definable workspaces. Each of these workspaces shall provide individually configured frames, with size/scaling controls. Any Windows 7 compatible display may be used.
12.	A context sensitive on-line Help feature shall explain and provide an example of the operation of each feature of the system. This help system shall be integrated into the on-board user manual via hyperlinks.
13.	A fully integrated Virtual Media Server feature shall allow user to map images and animations to a rig array. 40 such maps may be created, each with 12 layers. System that rely on external hardware or software for this functionality shall not be acceptable.
14.	User-definable, interactive displays may be created. These displays, which can be used in live and blind operating modes, allow graphical layout of channels, desk buttons and programming tools. Standard symbols are provided, and the user may import their own symbols or graphics. Each symbol may be individually defined with data feedback characteristics. Non-interactive status information, such as a mirror of other user’s command lines, may also be included in the display. A graphical browser is provided for fast selection of these views. Multiple zoom factors and placements may be stored and recalled for each display. 
15.	A detachable alphanumeric keyboard shall be provided. The keyboard shall allow labeling of all show content. An integrated virtual alphanumeric keyboard shall also be provided.
16.	Console software upgrades shall be made by the user via flash drive. It shall be possible to install software updates in all consoles, processor units and remotes from one device over the network.
17.	The console operating software shall be loaded into program execution memory from the internal hard drive when the console is powered. In the event of an uncontrolled shutdown, the console shall return to its last output state when power is restored. Devices requiring a UPS to provide such protections shall not be acceptable.
18.	Integrated dimmer monitoring features shall be provided to allow indication of dimming system status, error states and dimmer load monitoring. Adjustment of dimmer configuration from the console shall also be supported. Communications with the dimming system shall utilize ANSI E1.17 2006 - Entertainment Technology - Architecture for Control Networks.
19.	Integrated RDM device features shall be provided. The console shall discover and patch RDM devices. The console shall monitor RDM devices to allow indication of RDM device online/offline status error states. The console shall be capable of changing settings of RDM devices such as the DMX start address. Communications with the RDM devices shall utilize ANSI E1.20 2006 – Remote Device Management.
20.	Network configuration tools shall be provided from within the desk.
21.	Show data may be created and modified on a personal computer, using either Windows 7 or higher or a Macintosh platform running OS 10.11 or later via a free offline editing application. The program shall run natively on Apple operating systems. Applications requiring PC emulation programs shall not be acceptable.
22.	A PC, using either Windows 7 (or higher), or a Macintosh running OS 10.11 (or later) using the offline software application shall be able to connect to a control system via the network and view or modify current show data in an independent display environment, using an ETCnomad key. When connected without the key, the computer shall operate in Mirror Mode, with the device to be mirrored selectable by the user.
23.	Synchronized backup shall be provided via another full console on the network, an ETCnomad/Puck, or by use of a remote processor unit. The backup console/RPU shall maintain synchronized playback with the master and shall take over control of the lighting system upon loss of communication with the master. Use of two RPUs to service and backup system output is also supported.
24.	A maximum of 99 users may access and interact with show data simultaneously. Each user shall have an individual workspace. User identification may be assigned to more than one control device, allowing users to work in tandem, or allowing a designer/ALD to mirror the current display format, mode and command line of the associated programmer. Partitioned control allows discrete control of channel/parameter groupings by user. Partitioned control may be easily enabled and disabled with no need to merge show data from multiple users.
25.	The system shall support up to 32 individual simultaneous Time Code inputs or Event lists using Show Control Gateways.
26.	Systems that do not provide the above capabilities shall not be acceptable.
B.	Controls and Playback
1.	Manual Control and Programming Section
a.	The console keyboard shall be grouped by function. Major groupings shall be record target functions, numeric keys, level assignment functions, display navigation functions and controls, as well as non-intensity parameter controls. 
b.	The command keypad shall be fully interactive with direct selects and other virtual controls, which provide “one touch” selection of channels, groups, palettes, presets, effects, snapshots and macros.
c.	Non-intensity parameters may be set numerically via an extensible keypad. This control shall be fully interactive with the moving light encoder controls and the virtual controls. The controls shall also access available modes for each parameter type, min and max values for each parameter as applicable, as well as home position on a parameter basis. Each encoder shall support shift functions for fine control. The range of motion of coarse control may be set by the user. Tactile feedback shall indicate full and half frame positioning of certain controls.
d.	Only those parameters available for control in the active lighting system shall be displayed for control. Displays shall condense or lowlight parameters not available to selected channels. Alternatively, the encoders may be placed in a state allowing parameters not applicable to the current selection to be suppressed.
e.	Lamp controls provide direct access to luminaire functions such as striking and dousing arc lamps and calibrating entire fixtures or individual mechanisms of fixtures, as provided by the luminaire manufacturer. User access to these features is normalized across all manufacturers for ease of use. Use of a “control channel” for accessing these functions shall not be required and systems requiring use of control channels for these functions shall not be acceptable. 
f.	Fan functions shall be provided both via command line operation and through encoder controls.
g.	Highlight shall be supported, with user definable highlight values. Lowlight conditions may be defined for selected, but not specified channels. Rem Dim commands, at specific levels by channel, may be optionally and automatically called with the highlight command.
h.	Advanced color control functions provide color mixing in any of six different color spaces. Gel matches are provided via gel picker or by command line control. Tinting tools allow adjusting the color mix irrespective of the native mixing system. Spectrum tools support adjusting the output of additive color systems with more than three emitter types, allowing the X/Y coordinate to be held while adjusting the recipe that achieves that mix. Color Path tools allow the user to control the live fade of fixtures through the color space. 
i.	The Virtual Media Server function shall allow the user to create layouts of devices, identified as pixel maps. Media content (images, movies, text and procedurally generated effects) may then be applied, manipulated and stored. Stock content is provided and the user may import his own imagery and animations. 
j.	Macros may be set to run as default. Default macros called manually hall post to the command line, but executed via cue lists shall run in the background. The user may override this behavior by defining the macro to always execute in the foreground or background, regardless of the recall method. Startup, Shutdown and Disconnect macros may also be defined.
2.	Playback Section
a.	The playback faders shall consist of a 100mm Master Fader pair with three control buttons.
b.	Additional playbacks may be defined via external wings and/or virtual fader controls. Faders may be grouped for playback with user definable controls.
c.	It shall be possible to instantaneously halt an active cue, back to the previous cue, manually override the intensity fade or manually override the entire fade. 
d.	It shall be possible for a cue list to contribute to the background state or for the contents of each cue list to be withheld from such. Priority and background priority states may be established.
e.	Playback faders shall have the following associated controls: 
1)	Freeze, which halts the output of the fader
2)	Stop Effect, which stops the action of an effect
3)	Filter, to assign filter states to a fader
4)	Go To Cue 0, to reset a cue list
5)	Off, to turn off the contents of a playback, releasing control to the background state or to set to null.
6)	Assert, to replay an active cue
7)	Release, to release control to the background and reset the cue list.
8)	Timing disable, channel filters, parameter filters, priority and background priority status may also be defined. 
9)	The potentiometer shall be configurable as a proportional master, an intensity master, or manual master. Support for rate, effect rate, effect size and Master Only controls is also provided. Filtered manual timing masters and effects masters may be configured.
10)	Rate override and fader paging are supported with a wheel encoder and associated controls.
3.	Submasters
a.	Up to 999 proportional, fully overlapping additive or inhibitive submasters may be defined. Submasters shall have colored LEDs to indicate submaster status. Each submaster may have fade up, dwell and down fade times. Submasters may be set to priority and background priority status. 
b.	Submasters may be set to HTP or LTP intensity. Non-intensity parameters on submasters shall be LTP only.
c.	Exclusive mode for a submaster shall prohibit the live contribution of that submaster from storing to cues or other submasters. Shield mode prohibits access of associated channels from any other playback or manual control operations.
d.	A submaster potentiometer may be defined as proportional, master only or intensity master. When set as an intensity master, a mark and unmark feature is supplied.
e.	The submaster blind buffer shall be linked directly to live playback.
f.	It shall be possible to set submaster values directly from the command line.
g.	Submasters may be set to fade to background or to minimum value when the fader is returned toward zero.
h.	Submaster values may contribute to the background state or withheld from such.
4.	Grand Master Faders
a.	The location of the Grand Master shall be user definable. The grand master shall have associated blackout and blackout enable buttons. 
b.	Blackout shall send all associated intensity outputs to zero. Non-intensity outputs shall not be affected.
C.	Display Controls
1.	Format shall change the view of selected displays.
2.	It shall be possible for the user to choose which parameter categories or parameters (s)he wishes to display.
3.	Flexichannel modes shall change which channels are viewed in selected displays, as follows:
a.	No modes
b.	Masters only/cells only
c.	Use Partitions
4.	Flexichannel states shall change which channels are viewed in selected displays, modified by the modes, as follows:
a.	All channels
b.	Patched channels
c.	Show channels
d.	Active/Moved channels
e.	Selected channels
f.	Manual Channels
g.	View channels (user identified list)
h.	Channels with discrete timing
5.	Expand shall extend the selected view sequentially across connected displays, vertically or horizontally.
6.	[Time] depressed shall display discrete timing data. [Data] suppressed shall display absolute values of referenced data. These functions may be latched.
7.	Displays may also be toggled to show stored data currently manually overridden, the source of the current parameter data, output level, patch assignment, part structure and referenced marking data. 
8.	Playback status displays are provided with a variety of different formats. Indications are provided per cue for live moves (lights fading from zero and also moving non-intensity parameters) and dark moves (inactive lights which have stored non-intensity parameter moves).
9.	Display content including which of the workspaces is in focus on any of the three monitors and what views are docked in those workspaces may be instantly recalled using snapshots.
D.	Operating Modes
1.	Live Mode
a.	Channel lists may be constructed using the +, -, and Thru keys as well as the direct selects. Channel selection and deselection is fully interactive, regardless of the method used.
b.	Levels may also be set with the keypad, level wheel and non-intensity encoders. “Selected” channels shall be those last addressed and under keypad control. Controls are provided for single button access to the last selected channel list, all channels with manual levels and all active channels. 
c.	Channels may be set at a user defined default level using the Level key. +% and -% keys adjust channels quickly by user definable values.
d.	Channels and/or channel parameters may be captured. Capture mode shall allow the user to selectively capture channel data at specific levels. Captured data shall be indicated on the Live display.
e.	Sneak shall be used to restore specified channels to background states, default values, or to send them to specified values, in user specified times. 
f.	Selected channels may be set at a level or held to current values while all other channels are set to zero using Rem Dim. Toggling Rem Dim shall restore all unselected channels to original levels. The Rem Dim level shall be user definable via the command line or with a default setup value.
g.	Channels may be recorded into groups for fast recall of commonly used channels. 1000 groups shall be available. Groups shall store selection order. The Offset function supports rapid creation of ordered groups, including reverse and random order.
h.	Parameter settings may be stored to Intensity, Focus, Color and Beam Palettes and to Presets. All referenced data may be stored to whole numbers or to up to 99 decimal places between each whole number. 
i.	The following conditions may be placed on a channel or channel parameter to be included with a cue record action.
1)	Discrete fade time and/or delay 
2)	Block flag
3)	Assert flag
4)	IFCB Filters, which may be set at a parameter level.
5)	and Restore
j.	999 cue lists may be stored. Cues may be recorded in any order. Up to 99 decimal cues may be inserted between any two whole number cues. Each cue may contain a maximum of twenty parts. 
k.	It shall be possible to record cues and cue parts with the following information:
1)	Any collection of channel data, as determined by the use of “Record”, “Record Only” or selective store commands, combined with parameter filters.
2)	Cue Level timing and delays for Intensity Up, Intensity Down, Focus, Color and Beam.
3)	Follow or hang time
4)	Link instruction
5)	Loop value
6)	Block, Assert, Preheat, and/or Mark Flag 
7)	Curve
8)	Allfade
9)	Label and note
10)	Execute list to trigger other activity
l.	Non-intensity channel parameters may be marked (preset), in two ways. Automark presets any parameters transitions in the cue just prior to intensity becoming active. Automark may be disabled on a cue or cue part basis, enabling a “live” move. Alternatively, non-intensity parameters may be marked to a specific cue with a single command instruction. It shall not be necessary to store these parameters directly into the cue in which the movement is to occur. 
m.	Any channel parameter may be stored with an effect instruction. These effects may contain relative offsets from current value, or absolute instructions. Effects may be progressive action or on/off states. Entry and exit behaviors shall modify the channel parameters activity when beginning and ending the effect.
n.	Update may be used to selectively add modified parameter data quickly to that parameter’s current source. Update may be specified to modify referenced data content or break the link to that content. A dialogue informs the user of the content that will be updated. A trace command may be used to modify the data to the original source of its move instruction. It shall be possible to update inactive record targets.
o.	Recall From quickly pulls specified data from record targets or other channels into the current view.
p.	Copy To quickly copies selected data to specified channels or other record targets.
q.	Address and channel check functions shall be provided. 
r.	Channel parameters may be “parked” at levels. Those levels are not added to any live record operations, nor may they be changed until the parked element is “unparked”. Scaled park provides real time proportional adjustment of stored intensity values. Address Park shall also be provided.
s.	About shall provide detailed status of selected channels or specified record targets. This shall include current source, current value, discrete timing, parked value, marked to and for indications. Background levels and current DMX output are also displayed. Channel usage indicates submaster and cue information and also provide a "dark moves" report on a per channel basis. 
t.	1000 snapshots may be stored which instantly recall specified front panel and display configurations.
u.	Live data may be displayed in a summary view or detailed table orientation.
v.	Query shall allow selection of channels by their current or possible state. Keywords and fixture types shall allow quick access to fixtures.
w.	User definable home positions, on a per channel basis, may be defined.
x.	Channel level offset commands provide channel ordering and sub-grouping functions.
y.	Undo shall be used to sequentially step back through manual operations or to undo record and delete actions. It shall be possible to undo multiple commands in one action.
2.	Blind
a.	The Blind display allows viewing and modification of all record targets without affecting stage levels.
b.	Record target data may be displayed in a summary view, a detailed table orientation or a spreadsheet view, which allows quick data comparisons, move and replace functions.
c.	Changes to blind data shall be automatically stored. Range selection of both record targets and channels shall be supported.
3.	Patch Display
a.	Patch shall be used to display and modify the system control channels with their associated library data.
b.	Each channel may be provided with a proportional patch level, curve, label, swap and invert functions, as well as keywords to service Query.
c.	Offset functions in patch shall allow selection of channel ranges and shall allow the user to establish a “custom” footprint for any device output.
d.	Custom color wheels, color scrolls and gobo wheels shall be defined in patch. These devices shall be created with a simple table and graphical user interface supported by images of major manufacturers.
e.	RDM discovery and device monitoring shall be supported.
f.	Copy to and Move functions shall be supported in patch.
4.	Setup/Browser
a.	Setup shall access system, user and device configurations.
b.	It shall be possible to partially import Eos show files. Users shall be able to select as much or as little of the show file as required, with renumber tools.
c.	It shall be possible to import ASCII and Lightwright data files. It shall be possible to export as ASCII or .csv.
d.	Setup shall also access show data storage, import, export, print to .pdf and clear functions, as well as show data utilities.
e.	The system shall support programming and playback of real time clock events, including cue, submaster and macro execution at specific times of specified days or at a time based on astronomical events. 
f.	A control screen shall be provided for network configuration, selecting date/time, software update controls, selecting functional language and/or keyboard for labeling option, as well as other system level tools.
g.	Available languages for prompts, advisories and help messages shall include English, Bulgarian, German, Spanish, French, Italian, Japanese, Korean, Russian, Chinese, simplified and Chinese, traditional.
h.	Supported keyboards shall include American, United Kingdom, French, German, Italian, Korean, Norwegian, Russian, Slovakian, Turkish, Swiss, Swedish, Finnish and Bulgarian.
E.	Dimmer Monitoring and Configuration
1.	The lighting control system shall provide communication with an ETC Sensor+, Sensor3 or FDX dimming system for remote monitoring and configuration of show specific functions from within the software application.
2.	Circuit level configuration and monitoring functions shall include but not be limited to:
a.	Control mode (dimmable, switched, latch-lock, always on, off or fluorescent).
b.	Curves
c.	Control threshold
d.	Min and Max Scale Voltage
e.	Preheat
f.	Scale load
3.	Rack status messages shall include but not be limited to:
a.	State of UL924 panic closure
b.	DMX port error/failure
c.	Network error/failure
d.	A, B, C Phase below 90 or above 139 volts and headroom warning
e.	Ambient temperatures out of range
4.	Circuit status shall include but not be limited to:
a.	Module type and location
b.	Output level
c.	Control Source
d.	Overtemp
5.	Advanced circuit feedback shall include but not be limited to:
a.	Load higher or lower than recorded value
b.	DC detected on output
c.	SCR failed on/off
d.	Breaker trip
e.	Module has been removed
f.	Load failure
g.	Shutdown due to Overtemp
F.	Interface Options
1.	The console shall support a variety of local interfaces. 
a.	AC input
b.	USB (five ports for items such as alpha-numeric keyboard, mouse, touch screens, USB Flash drive)
c.	Ethernet (two ports)
d.	Two Display Port output connectors, supporting Windows 7 compliant monitors as 1280x1024 resolution minimum. Touchscreen/multi-touch support of any/all of these monitors is provided. 
e.	Contact Closure trigger via D-Sub connector
f.	4 DMX/RDM ports
g.	Alternative Contact Closure trigger through Gateway
h.	OSC Transmit/Receive
i.	MIDI In/Out, MSC and MIDI Notes through Gateway
a.	SMPTE Timecode through Gateway		
G.	Accessories 
1.	ETCPad (ETC Portable Access Device)
2.	iRFR and iRFR Preview (applications for iPhone, iPod Touch and iPad units)
3.	aRFR (application for Android devices)
4.	Net3 Remote Video Interface
5.	20 Fader or 40 Fader non-motorized fader wings
6.	10 Fader or 20 Fader motorized fader wings
7.	Gateways
a.	Net3/ETCNet 2 to DMX/RDM Gateways (one to four ports)
b.	MIDI/SMPTE Gateway
c.	I/O Gateway with 12 analog inputs, 12 SPDT contact outputs, RS-232 interface
H.	Synchronized Backup 
1.	An optional Backup system shall consist of one of the following combinations of devices: 
a.	Two networked Consoles.
b.	One (or more) Console with one Remote Processor Unit (RPU)
c.	One (or more) Consoles with two Remote Processor Units (RPUs) 
d.	ETCnomad/Puck
I.	Physical
1.	All operator controls and console electronics for a standard system shall be housed in a single desktop console, not to exceed 20” wide, 15” deep, 4.5” high, weighing 12.7 pounds. Console power shall be 90 – 240V AC at 50 or 60Hz, supplied via a detachable locking power cord.