Clairvoyance User’s Manual...Clairvoyance User’s Manual 2012 3 | Page Table of Contents Overview .....5 Introduction .....5

CLAIRVOYANCE USER’S MANUAL JANUARY 2013

2 | P a g e A g i l e n t T e c h n o l o g i e s

ORIGINAL AUTHOR: ANDRE RANDALL

REVISIONS BY: DENNIS COOK

REVISION: 1.1

DATE: JANUARY 14, 2013

AGILENT TECHNOLOGIES, INC.

Clairvoyance User’s Manual 2012

3 | P a g e

Table of Contents Overview ....................................................................................................................................................... 5

Introduction .............................................................................................................................................. 5

Predictive Modeling .................................................................................................................................. 6

Setup ............................................................................................................................................................. 7

Login/Access ............................................................................................................................................. 7

Assigning Resources .................................................................................................................................. 8

Organizing the District ................................................................................................................................ 12

Weekly Meetings .................................................................................................................................... 12

Open SR’s ................................................................................................................................................ 15

Root Cause Analysis and Historical Review................................................................................................. 17

Assigning Failure Modes ......................................................................................................................... 17

Response Time Analysis .......................................................................................................................... 21

Search .......................................................................................................................................................... 23

Leveraging SR Search Capabilities ........................................................................................................... 23

Leveraging the Tool ..................................................................................................................................... 24

Driving Response Time Excellence .......................................................................................................... 24

Appendix ..................................................................................................................................................... 26

Data Model ............................................................................................................................................. 26

Known Data Dependencies/Issues .......................................................................................................... 26

Technique to Platform Grouping Table .................................................................................................. 27


Table of Tables Table 1 Failure Modes ................................................................................................................................. 19 Table 2 Data Dependencies and Issues ....................................................................................................... 26 Table 3 Technique to Platform Grouping .................................................................................................... 27

Table of Figures Figure 1 Setup New User .............................................................................................................................. 7 Figure 2 Add New Resource .......................................................................................................................... 8 Figure 3 Setup Resource Info ........................................................................................................................ 8 Figure 4 Add Resource Availability ................................................................................................................ 9 Figure 5 Add Resource Availability Detail ..................................................................................................... 9 Figure 6 Modify Resource Availability and Add Time Off ........................................................................... 10 Figure 7 Add Time off Detail ....................................................................................................................... 10 Figure 8 Resource Summary ....................................................................................................................... 11 Figure 9 Resource Modifications and History ............................................................................................. 11 Figure 10 Weekly Meetings View................................................................................................................ 12 Figure 11 Closed Loop Yield Analysis Example (IM) .................................................................................... 14 Figure 12 Open SR Installs Greater than 30 Days Details ........................................................................... 16 Figure 13 Unassigned Failure Mode Selection ............................................................................................ 17 Figure 14 Assigning a Failure Mode Screen ................................................................................................ 18 Figure 15 Response Time Analysis .............................................................................................................. 21 Figure 16 Response Time Trend Analysis .................................................................................................... 22 Figure 17 SR Search View ............................................................................................................................ 23 Figure 18 DM-WLA Meetings ...................................................................................................................... 24 Figure 19 Weekly WLA Meeting Agenda .................................................................................................... 24 Figure 20 Closed Loop Resource Planning .................................................................................................. 25


5 | P a g e

Overview

Introduction Clairvoyance is a tool that that provides forward looking capacity planning. Historically services have managed serious investment decisions like training and hiring based on historical performance data. The previous strategy relied on leveraging historical utilization, skills gap analysis and response time data to predict future performance.

Clairvoyance leverages historical data analyzing it for expected delivery effort per model. Using that information it predicts the effort needed to complete open SR’s in the coming week localized to the district level. With this District Managers can leverage Clairvoyance to critically analyze upcoming skill gaps and capacity issues.

If a district is struggling with meeting business response time metrics, the tool provides a statistical modeling function that will allow its leaders, through root cause analysis, to fundamentally fix problems and drive improved performance.

Response time performance can be ‘rolled up’ to the territory and business unit to examine trends and drive improved performance.


The primary functions of Clairvoyance are:

• A past, current and future week view of customer demand aggregated into technique groupings. • A past, current and future week view of total headcount and full time equivalent headcount,

aggregated into supply hours • FSE resource tracking, including Field-On-Loan tracking and its impact on district capacity. • Open and Aging SR reviews • Historical Failure Mode Trend analysis data to enable Root Cause Analysis and drive Corrective

and Preventive Actions (CAPA’s) for response time metric improvements • Export of SR History based on Accounts, Platform/Techniques, Billing Type, SR Type and other

attributes. This data can be exported and used for account reviews, District Performance Analysis and other business needs.

• Year to Date, Weekly and Monthly views of Response time performance • Response Time Yield curves for Installs, PM’s, OQ’s and Repairs

Predictive Modeling Clairvoyance provides several levels of predictive modeling:

1. Estimate demand in hours by analyzing data based on the following criteria: a. Estimate hours needed to complete a job based on historical patterns of delivery effort

for each Agilent Model. b. Aggregate hours into ‘Technique’ tables for simple analysis of skills required for delivery c. Separate delivery effort of installations, PMs, OQs and repair into separate buckets d. Analyze delivery effort based on how work performed in step (a/c) is done uniquely for

each district e. If a model has never been delivered in your district, use information from your territory.

If a model has not been delivered in your territory, use information from your region, etc.

f. Forecast the work necessary to deliver an open SR based on Agilent Model, Activity Type and District leveraging steps a,b,c and d and present it to the District Manager.

2. Estimate repairs not currently registered in Siebel but certain to appear in the current week by analyzing historical repair trends based on platform and technique. Present those as ‘predictive repairs’ to the District Manager to help drive capacity planning.

3. Analyze PM’s due in the current month, linearly spread those over the remaining weeks of the month, estimate the effort to complete them, and present them to the District Manager to help drive capacity planning.


7 | P a g e

Setup

Login/Access Clairvoyance can be found at the following address: http://agilent.clv.bluefinui.com

You can request access from Dennis Cook, or 302 (T) 636 8290. Please be prepared to provide the following information:

First, Last Name

Agilent Email Address

Your desired login name

Your desired password (can be reset later)

Your Agilent Employee Number

Your Organization (District Name)

Once this data is provided a login account will be created for you and access will be provided. Please allow a few days turn-around time for this request.

Figure 1 Setup New User

http://agilent.clv.bluefinui.com/


Assigning Resources Once a login is provided the first task required to use Clairvoyance is to add your Field Engineers to the tool. This will allow you to create a capacity model. Click on ‘Resources’ on the menu bar (see arrow (A)):

Figure 2 Add New Resource

To add resources click on “New” as shown in “B” above. Once you click on “New” the following Screen will be presented:

Figure 3 Setup Resource Info

Add the First and Last name. Select the resource type based on whether the resource is in your district and managed by you “Owned” or a non-Agilent resource you leverage to deliver services “ASP”. Then select the home area of the resource, which should be your district. Once that is done click on ‘Save’ (Arrow C above).

B

A

B

C


9 | P a g e

Once this is done you will get the following screen:

Figure 4 Add Resource Availability

On this screen you can add the normal working hours of the Field Engineer and adjust those working hours by adding scheduled time off. To add working hours click on ‘Add Availability’ (arrow D above). The following popup will be presented:

Figure 5 Add Resource Availability Detail

Add hours to the work week and the start date for the resource. If the resource is a full time employee with no expected end date leave ‘Ending’ blank. If the employee is expected to end his employment with Agilent add that date to ‘Ending’. You can also add notes like “New employee” or “GCMS Resource” or anything else that helps you identify your resource. These notes are not used anywhere else in Clairvoyance however. When done click ‘Add’ in the popup and the tool will create the availability profile for the resource.

B D

B E


The following example added ‘New FSE’ to the current district, starting on 11/01/2011 with no end date working 8 hours a day for 5 days a week.

Figure 6 Modify Resource Availability and Add Time Off

If you make a mistake you can click on the pencil (arrow F) which will bring up the popup to allow changes.

To adjust for resources availability based on training and time off, click on ‘Add Time Off’ (arrow G) and get the following popup:

Figure 7 Add Time off Detail

Select the ‘Type’ of time off (Vacation or Training), Select a start and end date (both required) and add optional notes (LC Training, Personal Holiday, etc.). Once done click ‘Add’.

F

B G

B H


11 | P a g e

The following example added a training class for a resource named “New FSE” starting on 11/26/2012, ending on 11/30/2012 with the note “ICP-OES Refresher Course”:

Figure 8 Resource Summary

Once you are satisfied with your resource, click ‘Save’ (arrow J).

Repeat arrow’s B through J for each resource you need to add to Clairvoyance.

If you need to delete a resource first delete all availability records by clicking on the x at arrow K and time off records by clicking on the x at arrow L. Once this is done you can then delete the resource by clicking on ‘Delete’ at arrow M.

Figure 9 Resource Modifications and History

The tool also ‘hides’ scheduled time off that has happened in the past to keep from cluttering up your screen. To see historical time off click on “Show History” shown in arrow N.

J

K

L

M

N


Organizing the District

Weekly Meetings The Weekly Meetings view is the primary purpose of Clairvoyance. By leveraging this view a DM can drive his organizations capacity planning decisions in alignment with his WLA, management team and training organization. It provides information on current and future (up to 4 weeks) gaps that, if not carefully planned for, can cause significant skills based resource gaps.

The Weekly Meetings view provides the DM with an overall view of the demand, supply and potential gaps in her business in the current week. Using the information provided you can leverage Clairvoyance to analyze your historical work load, your current open SR’s due in this week, and your future PM’s, the net impact of training/vacations on your capacity and ultimately understand the net impact of each of these factors on your ability to meet current demand.

Figure 10 Weekly Meetings View

This view provides the following information:

1. What historical run rate have you had in your district for Installs, Repairs, OQ’s and PM’s? Leveraging that data, compare it against the current week to see if this week provides an uptick in demand that is abnormal and should be addressed.

1

2

3

4

5

6

7

8

9

10

11


13 | P a g e

2. What PM’s and OQ’s are due this month? How many are complete? Given the time left in the month, how many do you need to do this week to meet this month’s commitments? What are the number of repairs that might come in this week and the effort to deliver them?

3. What is the aggregate supply of Agilent and non-Agilent resources that you have in the district? 4. How of the resources in the district are truly available to work this week, excluding vacations

and training? 5. Given the number of SR’s that are currently open and are due this week, do you have adequate

capacity to deliver them? 6. Given all of your demand, including PM’s that may not have a commit date this week and repairs

that might occur but have not shown up yet in the system; do you have adequate capacity to deliver?

7. What skills are needed to deliver the current demand (GC, LM, etc.)? 8. How many hours does your district typically use to do installs, repairs, OQs and PM’s for each

skill areas and what is the total amount of time needed to meet the week’s customer demand based on that historical trend?

9. What is the net impact of vacations and training on your capacity model and who will not be available this week?

10. What is the net ASP pool available to the District 11. What’s the probability of a ‘Bad’ week in the district, measured by the inability to meet current

demand with the resourcing/skilling/staffing strategy currently documented?

District Managers must critically analyze gaps and associated resourcing tradeoffs to insure long term gaps are filled. In coordination with WLA’s Observations, Actions and Adjustments can be documented and then revisited to see if plans have caused a positive impact. By leveraging the Weekly Meetings view and the information gained from the RT Analysis view a DM can leverage simple CAPA (Corrective and Preventative Analysis) techniques to improve organizational capability.

Skills based resourcing provides a simple example. If, after analyzing information on the ‘Weekly View’ screen suppose a DM finds significant uptick in ICP/MS repairs (Percent of Total for IM = 10%, Historical % IM = 3%). A DM has several analytical options:

1. Examine the resource pool to see if the IM resource will be on vacation/Training 2. Explore the history of IM delivery using the SR Search view to see if there are district issues with

IM delivery (SR Search Screen, Platform = IM, RT Met = No and then explore Failure Modes and Comments to understand why RT was not met). See if there is a failure mode trend and explore historical comments to understand why.

3. Check to see if repair capacity is being hindered by an uptick in PM demand because the district is failing to spread out PM’s across the month and bunching them into the current week (use the Detailed Jobs table on Weekly View Screen, explore the PM column vs. the Repair/OQ/Install/Other columns. Drill in by clicking on the number in the IM row and PM column to see the details and understand the commit dates)?


4. Should you add ASP’s or resources outside the district to meet the demand uptick (FOL model in resources tab)?

Each DM should meet weekly with their WLA to discuss capacity issues documented on the Weekly View screen. DM’s should capture strategies and tactics in the observations, actions, and adjustments text boxes, and then go back and explore if those changes have made a difference in the business. To understand whether those adjustments have actually made positive difference, a DM can look at the “Response Time Yield” view of the “RT Analysis” tab and see if the response curves in the areas of focus have gotten better. For example, changes in strategies and tactics on “IM” platforms would show a positive ‘bend’ in the IM curve below:

Figure 11 Closed Loop Yield Analysis Example (IM)


15 | P a g e

Open SR’s

District Managers can use the Open SR screen to explore SR’s that are open and with a bit of work might be closed. This table provides:

1. SR’s broken up into Install, OQ, PM, Repair and Other 2. SR’s with commit Dates that are older than 30 days 3. SR’s with commit dates that are between 0 and 30 days 4. SR’s with commit dates due in the current week 5. SR’s with commit dates that are due in the future 6. A subtotal of all SR’s included in 2 through 5 above 7. Aged SR’s where readiness is uncertain (SR’s with commit dates set to 12/31/2020) 8. The total number of all SR’s

1

2

3

4

5

6

7

8

9


Each number in the above table can be examined by clicking on it to see the details. The following is an example that shows the details for installs that are more than 30 days old:

Figure 12 Open SR Installs Greater than 30 Days Details

The list provided includes the SR’s, company, platform, model number, SR Open date and SR Commit Date. The list can be exported by clicking on the XLS button. An exported list can then be provided to the WLA to work independently on to clean up.

1


17 | P a g e

Root Cause Analysis and Historical Review Clairvoyance provides tools for fundamentally understanding why response time metrics are not being met in your district. This is done by critically analyzing how SR’s fail, assigning failure modes over a period of time, and then using the statistical information gathered to determine root cause. Root cause data can be used to change training strategies, challenge parts delivery and/or inventories, train WLA’s on Seibel usage etc.

Once response time metrics improve failure mode assignment, along with root cause analysis, might not be needed. A DM can recommit to it again when significant changes occur.

Assigning Failure Modes With Clairvoyance you can analyze why your district is not meeting its response time business metrics. Response time metrics are computed using the following logic:

SL Response Response Time Met = YES

1, 2, 3, 4, …. Days [Activity Start Date]-[SR Opened Date] <= SL Response (i)

Scheduled [Activity Start Date]=< [SR Committed Date]

(i) Working days (Mon-Fri), public holidays not accounted

When response time is missed it is listed in Clairvoyance in the left window for each activity that missed. By assigning failure modes to an activity a District Manager can look for trends over time that indicate which significant, sustained problem has been negatively impacting response time performance.

When you first log into Clairvoyance you are presented with the “Unassigned Failure Mode” screen:

Figure 13 Unassigned Failure Mode Selection

B A


Click on any of the Customers listed in the table on the left of the screen (arrow A) and the following screen will appear:

Figure 14 Assigning a Failure Mode Screen

This screen provides a summary of the SR/Activity including the commit date, open date, activity start date, platform, account, etc. shown in arrows B, D and E.

B B

B C

D

E

F


19 | P a g e

Failure modes are in the drop down called “Failure Mode” (arrow C). Failure modes are defined by the following:

Table 1 Failure Modes

Failure Code Meaning 2nd Activity There are SR’s in Siebel that have multiple activities

attached to them. It is possible that one of the activities started on or before the commit date and the 2nd activity started after the commit date. When this happens you can set the failure mode to ‘2nd Activity’ and set ‘RT Met’ to “Yes”

ASP Missed Non-Agilent delivery resources failed to meet response time

BO Parts (Back Ordered Parts) Response time was missed because parts could not arrive at the customer site prior to commit date

Coding This is a general bucket to catch coding errors like no commit date set, failure to change the commit date when the customer told you it was ok, etc.

Escalation SR is in escalation and response time was missed waiting for Agilent overall responsiveness (formal escalation must be open)

FSE Owned The FSE failed to get to the job even when there was ample time to do so.

Other This is a catch bucket for errors that don’t fit any of the above or is used to assign historical SR's to a common bucket prior to your district starting to use Clairvoyance.

RCE Owned The Remote Customer Engineer failed to follow up and Agilent missed the response time commitment

SDD Same Day Dispatch-> Agilent’s metric is to get the call to the WLA in the same day that the customer submits a request to our website or calls our 800 number. This measures whether the front end is working correctly including entitlement, parts predict, call routing, etc.

WLA Owned The WLA dropped the ball in assigning resources, escalating to the DM when needed, properly working with the FSE’s to align their calendars, contacting the customers, etc.

Wrong RT Calculation

Clairvoyance miss-computed the response time and it should have passed.


Customer Customer Reschedules call due to customer reasons after initial scheduling.

Holiday Country Holiday delays response time.

District Managers can determine which failure mode to assign by highlighting the SR, copying it, pasting it into Siebel, and exploring why the SR missed response time. A DM can look at SR notes, audit trails, activity notes and any other Siebel field to understand root cause. Once root cause is determined you can go back to Clairvoyance select the failure mode using the drop down box at arrow C, add notes and resolution suggestions and click “Save” (arrow F). Clairvoyance with then begin to collect failure mode data and allow you to build a trending data.

Once you hit save on the current SR, select another SR in the column on the left (arrow A) and complete the failure mode assignment effort. Do this for all activities listed on the left. Every week you will get a new list of failed SR’s that will need updating. The next step is to then understand your failure modes and use that data to adjust your plans needed to improve District response time.


21 | P a g e

Response Time Analysis Clairvoyance allows you to analyze historical data and by capturing failure modes you can focus on the top issues in your district and have a quicker impact on reversing negative response time trends. Selecting RT Analysis (Response Time Analysis) provides:

Figure 15 Response Time Analysis

The above view provides failure mode data, sorted by Installs, Repairs, PMs and OQs, and sorted by failure mode for each activity type. In this view last fiscal year Northern New England did the following

• 496 Installations • 439 installation were delivered by commit date • 57 missed customer commitments

o 24 were missed because of coding issues o 14 were missed because the FSE did not get there on the commit date o 9 were missed because the district failed to have an appropriate trained resource by

the commit date to deliver the installation o 2 were problems with the WLA not managing the installations correctly o 1 installation was missed because the ASP did not get there by the commit date o 1 was missed because the installation required a part that was not in the shipment

and was backordered

A district manager can leverage this information to drive changes to the operational model of the district. For instance, with such a large number of coding errors, the District Manager can focus on training for the WLA’s, Field Engineers and other critical resources on how to setup and manage installation SR’s in Siebel.


The large number of FSE Owned SR’s might imply specific training is needed with the Field Engineers. Many times our customers ask Agilent to change the installation date (site is not ready, gasses are not ready, old equipment has not been removed, etc.). A call could go out to the Field Engineer, but the engineer doesn’t bother to call the WLA to inform them the commit date has changed. Simple training can address this.

Trending data can also show how changes to your business have impacted response time. Select “Response Time Yield” (arrow A) on the left of the chart and you will see:

Figure 16 Response Time Trend Analysis

Using the drop downs you can filter on platforms and date ranges (arrow B) and using the check boxes (arrow C) you can add or remove activity types (PM, OQ, Repair and Install).

This chart shows a positive trend in repair response time that began in June 2012. Leveraging root cause analysis information derived from this section and changes made to the delivery model, you can monitor its impact on response time performance using these charts.

B A

B

C


23 | P a g e

Search

Leveraging SR Search Capabilities Clairvoyance provides a SR Search capability that allows you do explore issues with your business. An example is:

Figure 17 SR Search View

This search tells me that in

• Northern New England District there are quite are • 108 instances where response time was missed in the time frame from • 11/01/2011 to 10/31/2012 in the • LC platform which were caused by capacity problems.

SR search is a powerful tool that can provide rich information on your business. All data can be exported to excel using the xls button. More detailed analysis can be done in Excel.


Leveraging the Tool

Driving Response Time Excellence

Figure 18 DM-WLA Meetings

Figure 19 Weekly WLA Meeting Agenda


25 | P a g e

Clairvoyance is designed to allow the District Manager to drive process excellence in her organization. By examining historical data, and looking at current and future week demand, a DM will be able to adjust the direction of his capacity management decisions to avoid skill gaps that cause response time issues.

A simple model of this is:

Figure 20 Closed Loop Resource Planning

Each week a District Manager should meet with her WLA to review skill gaps. In the short term (2 weeks to 3 months), the DM can leverage field on loan (FOL) or ASP’s to fill capacity gaps. Over the mid-term (2 months to 6 months) she can then use the tool to understand sustained gaps and put FSE’s into targeted training. If a skill gap is expected to be sustained over a longer period (6 – 12 months) she can open up a requisition and hire new FSE’s.

Review 1-12 week Gaps

FOL and ASP for short Term

capacity management

Training to meet mid-term

technology gaps

Adjust ASP Capacity/Focus

Examine Utilization and

Financials for HC affordability

Hire for sustained gaps

Incremental training and HC adds to supply reducing your

Monday ‘Blues’


Appendix

Data Model The Clairvoyance tool loads all closed and open SR data from Siebel on a regular basis (currently weekly). All SR’s are assigned to a district based on the zip code of the customer where the work was completed. It follows exactly the zip code model used in Diver and with Services financial analysis.

Closed SR data is extracted and supplemented to provide information on response time performance per activity (was the activity delivered in the contractually committed timeframe). When an activity misses its response time performance target, it is presented to the District Manager to analyze and assign an associated failure mode. The collection of these failure modes allows the District Manager to see trending information and do root cause analysis in her district.

Known Data Dependencies/Issues Table 2 Data Dependencies and Issues

Issue Detail The Clairvoyance tool is driven by Commit Dates

All decisions in the tools rely on Seibel commit dates.

Clairvoyance provides Activity vs. SR based analysis

The tool provides all activities of a single SR.

Data is updated once a week Clairvoyance data is not real time. It is updated every Monday morning by 9am Eastern Standard Time

SR’s are assigned based on ZIP code tables

All SR’s are assigned by associated the zip code of the customer where the work is done to the district that owns that zip code

Warranty and Installation SR’s on Agilent equipment fall into the district where the Agilent Site is located

If a demo or other Agilent instrument is loaned out to a customer it still belongs to the zip code where the instrument was originally shipped from.

Trade and Gratis SR’s impact historical workload computations but do not impact Response time computations

Trade and Gratis SR’s do not show up on the ‘Unassigned Failure Mode’ or the RT Analysis screens. They are however added to the CLV tool to compute historical efforts to deliver.


27 | P a g e

Technique to Platform Grouping Table Table 3 Technique to Platform Grouping

Technique Grouping PLATFORM Platform Description Atomic Spectroscopy AA Atomic Absorption Atomic Spectroscopy V-AA Atomic Absorption Atomic Spectroscopy IM ICP-MS (Inductively Coupled Plasma-Mass Spectroscopy) Atomic Spectroscopy V-IO ICP-OES (Inductively Coupled Plasma-Optical Emission

Spectroscopy ) Atomic Spectroscopy V-MP Microwave Plasma Atomic Emission Spec (MP-AES) CrossLab NON-AGILENT 3rd party support CrossLab MV-DI Multi Vendor DIs CrossLab MV-GC Multi Vendor GCs CrossLab MV-GM Multi Vendor GMs CrossLab MV-IM Multi Vendor IMs CrossLab MV-GC Multi Vendor LCs CrossLab MV-GM Multi Vendor LCs CrossLab MV-LC Multi Vendor LCs CrossLab MV-LM Multi Vendor LMs CrossLab MV-MS Multi Vendor MSs CrossLab MV-OTHER Multi Vendor Other CrossLab MV-RP Multi Vendor RPs CrossLab MV-SP Multi Vendor SPs CrossLab V-BK Varian (Bruker) GCs GC GC Gas Chromatography GC V-GC Varian GC not divested to Bruker GCMS AGILENT Archon Purge & Trap Auto Sampler GCMS GM Gas Chromatography/Mass Spec GCMS V-GM Varian GCMS not divested to Bruker Genomics BI Bioanalyzer Genomics CE Capillary Electrophoresis Genomics AP Lab on a chip Genomics SN Scanners Genomics SR Stratagene Genomics L9 TapeStation LC V-DI Dissolution LC V-FC Flash Chromatography LC GP Gel Permeation LC V-GP Gel Permeation LC LC Liquid Chromatography


LC V-LC Varian Liquid Chromatography LCMS BC Biocius Rapidfire MS LCMS LM Liquid Chromatography/Mass Spec LCMS V-LM Varian Liquid Chromatography/Mass Spec Molecular Spectroscopy

A2 A2 Acquisition (Molec Spec)

Molecular Spectroscopy

IR Cary


V-FL Cary Fluorescence


V-UV Cary UV


V-IR FTIR (Fourier transform infrared spectroscopy)


UV UV-Vis Spectroscopy

Other COMPUTER "PCs, Monitors, & Printers" Other CONSUMABLE

S Consumables

Other Z-OTHER Other Other 9H PL9H vaccum products (svc not thru PL74) Other SW Software Other V11 Velocity 11 Automation Research Products V-NM Magnetic Resonance Research Products V-XR X-ray Crystallography

Documents

Clairvoyance User’s Manual...Clairvoyance User’s Manual 2012 3 | Page Table of Contents Overview .....5 Introduction .....5