AVOTIGERTOUCH2
AVOLITES
discontinued

Tiger Touch II

ORDER CODE: AVOTIGERTOUCH2

Now boasting a 100% brighter screen, increased processing power, and faster graphics engine, the Tiger Touch II is the most specified Titan console.
The Avolites Tiger Touch II represents the perfect combination of power and portability. This third-generation console is packed with enough power for complex shows, yet small and light enough to fly in standard hold luggage. The console features SMPTE timecode support and a redesigned button layout to match the entire Titan range.
In order to update the console to version 12 of the Titan, it will be necessary to purchase and install a USB dongle called AVOKEY.
Serial 02006 - 03065
You need to order:
- AVOKEYINT 
- 1x5 way to USB-A Cable (spare part code 8000-6102)
Once you've received your AVOKEYINT and 1x5 way to USB-A Cable, you will be required to connect the USB-A Cable to the motherboard. This cable will provide an additional USB port for the AvoKey.
Click here to view the installation guide: https://www.avolites.com/Portals/0/Downloads/Manuals/AvoKey/8000-6102 TT2-2-3K AVOKEY upgrade with 1808-0028.pdf
 
Serial 03066 - 4020

You need to order only AVOKEYINT
Once you've received your AVOKEYINT, you will be required to connect this directly to the available (Blue) USB port inside the console (on the motherboard).
Click here to view the installation guide: https://www.avolites.com/Portals/0/Downloads/Manuals/AvoKey/8000-6101 TT2 AVOKEY no cable.pdf
 
Serial 04021 - 05001
You need to order only AVOKEYINT
Once you've received your AVOKEYINT, you will be required to connect this directly to the available (Red) USB port inside the console (on the motherboard).
 
Serial 5001 and above include a factory fitted AvoKey.
Therefore, you do not need to purchase an AvoKey.

Main features:

  • 10 pageable playbacks, 60 pages.
  • 10 static playbacks - perfect for instant access.
  • 100% brighter 15.6" screen.
  • Three metal shaft optical encoders offering luxurious precision.
  • MIDI support for MIDI Notes and MIDI Timecode.
  • Built in UPS.
  • 4 physical DMX outputs, up to 16 over ArtNet or sACN - 8192 channels.
  • Supports Titan Network Processors for DMX expansion up to 64 universes.
  • Trigger inputs.
  • Dual Ethernet port.
  • Expand your control surface through wings, DMX In or MIDI.
  • Dedicated cue stack control.
  • Support for external touch screen.
  • 10 programmable executor buttons.
  • Conveniently accessible front loading USB.
  • Dimensions (WxHxP): 675x435x147 mm (console only); 750x620x300 mm (console in flight case).
  • Weight: 15.2 kg (console only); 29.40 kg (console in flight case); 31.70 kg (console packed in flight case).

PHOTO GALLERY

Technical specifications

Versions

Accessories & Related Products

AVOKEYINT
AVOKEYINT
(Optional)
AvoKey internal (red)
AVOTT2FC
AVOTT2FC
(Optional)
Avolites TigerTouch II Case

DOWNLOAD

Data sheet & specs

File name File size Download
Letter datasheetAvotigertouch2_A4_DATASHEET.pdf(28/05/2021)454KB

User manual

File name File size Download

DMX chart & personalities

File name File size Download

Photometrics

File name File size Download

CAD symbols & drawings

File name File size Download

Tech docs

File name File size Download

Software

File name File size Download

Firmware

Info Request

Maturity Level Assurance May 2026

The practical necessity of MLA becomes starkly evident in high-stakes industries. Consider the automotive sector, where a single software glitch in an electronic control unit can lead to fatal recalls. Automotive SPICE (ASPICE) mandates specific maturity levels for different processes. An OEM does not simply ask a supplier, "Do you have a coding standard?" Instead, they demand MLA evidence that the supplier’s requirements management process operates at Maturity Level 3 (well-defined and deployed across projects). This assurance allows the OEM to reduce their own testing burden, manage supply chain risk, and achieve faster time-to-market. Similarly, in aerospace, the FAA’s reliance on Delegated Organization Authorization (DOA) is underpinned by the manufacturer’s ability to demonstrate process maturity—proving that safety is designed in, not just inspected at the end.

The architecture of MLA typically rests on four key pillars. First is , where best practices are codified into repeatable workflows. Without a standard, there can be no maturity. Second is Objective Evaluation , where trained assessors use formal methods (e.g., CMMI appraisals or ISO 15504 assessments) to score process attributes against a maturity ladder—usually from Level 1 (Initial/Chaotic) to Level 5 (Optimizing). Third is Capability Verification , which involves rigorous testing of process outputs against statistical controls. For instance, in high-reliability industries, MLA may require demonstrating a manufacturing process’s "CpK" (process capability index) to prove it consistently stays within specification limits. Fourth, and most importantly, is Continuous Feedback and Remediation , where assurance findings directly trigger corrective actions and process improvements, closing the loop between evaluation and execution. maturity level assurance

In the modern landscape of engineering and manufacturing, the phrase "trust but verify" is no longer sufficient. As products become more complex and supply chains more distributed, organizations face a critical question: How can a buyer trust that a supplier’s processes will consistently deliver quality results? The answer lies not just in inspecting the final product, but in assuring the maturity of the processes that create it. This is the domain of Maturity Level Assurance (MLA) —a systematic, data-driven approach to evaluating, verifying, and improving an organization’s process capability. MLA transcends traditional quality control; it is the strategic discipline that transforms process models from theoretical frameworks into operational guarantees. The practical necessity of MLA becomes starkly evident

However, implementing MLA is not without challenges. A common pitfall is "certification theater"—where organizations focus on passing an appraisal (e.g., achieving a CMMI Level 3 rating) without embedding the behavioral and cultural changes necessary for true maturity. In such cases, MLA becomes a bureaucratic burden, generating paperwork that masks rather than reveals risk. Effective MLA avoids this by decoupling assurance from episodic audits. Instead, it integrates lightweight, frequent checks into the daily workflow—automated process mining, peer reviews, and real-time dashboards of process metrics. The gold standard is when assurance is so seamless that it feels less like an inspection and more like a navigation system for the organization. An OEM does not simply ask a supplier,

Looking forward, the evolution of Maturity Level Assurance is being shaped by artificial intelligence and predictive analytics. Next-generation MLA systems will not merely report that a process is at Level 3; they will predict that, given current trends, a specific requirement traceability activity is likely to degrade to Level 2 within the next sprint. By analyzing patterns in deviation, AI can recommend targeted micro-improvements, accelerating the journey toward Level 5. This shifts the role of the quality professional from a retroactive gatekeeper to a proactive architect of resilience.

In conclusion, Maturity Level Assurance is far more than a sophisticated audit. It is the operational backbone of organizational reliability in a complex world. By providing objective, continuous evidence that processes are not just documented but demonstrably capable, MLA builds the bridge between process models and real-world performance. For organizations seeking to move beyond mere survival toward sustainable excellence, maturity level assurance is not an option—it is an imperative. It transforms the promise of quality from a vague aspiration into a measurable, manageable, and trustworthy reality.

At its core, Maturity Level Assurance is the practice of providing objective evidence that an organization’s processes operate at a defined, repeatable, and increasingly optimized level of capability. It is intimately linked with capability maturity models (CMMs), such as the Capability Maturity Model Integration (CMMI) or Automotive SPICE (Software Process Improvement and Capability Determination). While a standard audit confirms compliance (whether you are following a checklist), MLA confirms effectiveness (whether the process reliably achieves its intended outcomes). The "assurance" component is critical: it implies continuous monitoring, independent verification, and a forward-looking stance that anticipates failures before they occur, rather than merely documenting them after the fact.


Subscribe to our Newsletter

Loading...