Testing Event Workflow Options

Option 1: Important Dates with VDI (Vendor Data Input) integration

👍Recommended Workflow

In this option, Important Date events are created and managed by an integrated third-party vendor such as Tanknology or Crompco. The vendor uses Titan Cloud's API to update Important Dates for individual tests (LD, Line, ATG, etc.) with all the relevant details. In addition to the raw data sent as an XML file, the third-party vendor imports PDF files for the completed tests that are automatically saved to the facility's Electronic File Cabinet (E-Files).

Pros: Users don't need to manually create, update, or close Important Dates records. The interface in Titan Cloud Edge can simply be used to monitor upcoming and past-due events or review completed results.

Cons: This workflow requires complex technical setup, and may require ongoing attention to ensure incoming data is correctly mapped in Titan Cloud Edge. 

Option 2: Automatically generate new records when Important Dates are closed

👍Recommended Workflow

When marking an Important Date event record as complete, fill in the required fields such as completed date, result, and frequency to prompt the system to automatically generate a follow-up event. 

Pros: The user never has to worry about manually creating follow-up events, and all historical completed events are accurately documented.

Cons: Remembering which fields are required to automatically generate a recurring Important Dates record can be tricky, as it can differ based on Important Dates Configuration. But don't worry, our product and engineering teams are working on improving this!

Option 3: Keep records open

Testing Event Organization Options

Option 1: Break out each testing event into its own record

By default, a VDI integrated workflow will separate each testing event into its own record. Customers that do not use a VDI integration may also choose to track each testing event individually.

Pros: Tracking and documenting each testing event individually provides accurate and detailed historical records and makes it easy to track individual costs. 

Cons: Each testing event must be updated individually, which can be time consuming if you are not using a VDI integration.

Option 2: Bundle testing events into a single event record

Group testing events by type or frequency and track them together as a single event record.

Pros: Bundled testing records are easy to maintain, with less manual creating and updating of event records. This option is ideal if you are using a different system outside of Titan Cloud Edge to track individual testing events and results. 

Cons: Individual results, dates, documents, and costs for each test may not be tracked this way.