Updated: Jul 26
When it comes to testing, every organization has its own distinct processes, workflows, and requirements. One-size-fits-all solutions often fall short of meeting these needs.
That's where TITAN Test Life Cycle Management shines.
Your process is your competitive advantage. TITAN offers unparalleled flexibility and configuration options, allowing you to adapt the software to your process instead of conforming to rigid out-of-the-box settings.
Each of the following features within Titan can be tailored to suit your business:
Workflows: Titan develops and manages multiple sets of workflows and approval processes within an organization. Workflows are customized to align with processes as they currently exist; no need to alter a workflow to conform to an application. An infinite number of workflows can be developed -- one for every team within the organization.
Forms: Test requests and other forms can also be customized for each team. Certain teams may require a separate set of fields or may even require shared fields to be mandatory or not mandatory. User input can be controlled using drop-down options.
Nomenclature/terminologies: One team in the organization may refer to items as "samples" while a different team may use the term "material" for the same items. Titan can be customized to reflect the organization's specific work vocabulary at an organizational or team level.
Role-based permission: Different teams require different sets of user access. Team A, for example, may allow engineers to schedule technicians. Team B has a Technician Manager who reviews tests and schedules resources accordingly. Titan can accommodate an infinite variety of permissions and roles based on each team's process and structure.
Portal and Instance
The portal and the instance concepts are key to Titan's flexibility. The portal contains its own workflow, form types, terms, and access; each portal is designed to support a single work team and each portal is infinitely customizable. Capabilities are provided within the Titan application so that trained users can define their own workflows, forms, etc. (The organization can optionally defer these tasks to 12th Wonder).
Multiple portals fit inside a single instance. An instance provides the convenience of sharing resources associated with all teams. For example, company projects, equipment, and test vehicles can be shared by all the portals. Also, tasks like user administration can be accomplished easily; an administrator can manage users for several portals from a universal view.
The diagram below shows the relationship between portal and instance.
A large automaker in North America uses Titan to create and manage test requests. The automaker has multiple engineering teams, each with its own set of processes and rules. Each team is assigned a portal; several portals occupy a single instance. Testing resources – like vehicles and equipment – are shared among the teams within the instance.
There are three engineering teams within the instance. The first team designs and tests materials, the second team is responsible for electrical systems, and the third team performs crash testing. Each testing process is radically different from the others, but the procedure of requesting a test is the same: a form is completed, approved, and forwarded to a technical team for execution.
The Titan team worked with each group, documenting the unique processes, workflow, and terms. Titan then created and deployed approval processes and forms for each team. Vehicle project codes, shared by all teams, were added manually via the Projects feature. Test vehicles, a resource that all teams also shared, were bulk uploaded from an Excel file, and the teams collaborated on appropriate terminology. Titan also developed roles for each team with permissions designed to enable each unique workflow.
Even though the forms and workflows are strikingly different for each team, all three portals are managed conveniently in a single instance, and one administrator manages the users for all three portals within a special portal within the instance.