Diagnostic Baselining

1 . A method, comprising:

at a device, receiving device-under-service (DUS)-related data for a DUS;

at the device, determining that the DUS-related data is to be aggregated into aggregated data based on a classification of the DUS-related data;

at the device, generating an aggregated-data comparison of the DUS-related data and the aggregated data;

at the device, generating a DUS report based on the aggregated-data comparison, the DUS report comprising one or more sub-strategies, wherein at least one of the one or more sub-strategies comprises a sub-strategy-success estimate; and

sending the DUS report from the device.

2 . The method of claim 1 , wherein the DUS-related data comprises DUS-test data obtained from a first DUS test performed on the DUS.

3 . The method of claim 2 , wherein determining the DUS-related data is to be aggregated comprises:

determining one or more DUS attributes from the DUS-related data;

selecting baseline data from the aggregated data based on the one or more DUS attributes;

generating a baseline comparison between the DUS-test data and baseline data;

determining the classification for the DUS-related data based on the baseline comparison; and

aggregating the DUS-related data into the aggregated data based on the classification.

4 . The method of claim 2 , further comprising:

at the device, generating a diagnostic request based on the aggregated-data comparison, the diagnostic request for requesting data related to a second DUS test performed at the DUS.

5 . The method of claim 4 , wherein the diagnostic request comprises instructions for performing the second DUS test.

6 . The method of claim 1 , wherein the DUS-related data comprises complaint data, and wherein generating the DUS report comprises generating the DUS report based on the complaint data.

7 . The method of claim 6 , wherein generating the DUS report comprises:

determining at least one complaint based on the complaint data;

generating a query based on the at least one complaint;

querying a rules engine of the device using the query; and

in response to the query, receiving the one or more sub-strategies.

8 . The method of claim 7 , wherein the compliant data comprises complaint text, and wherein determining the at least one complaint comprises:

generating a textual analysis of the complaint text; and

determining the at least one complaint based on the textual analysis.

9 . The method of claim 7 , wherein the DUS-related data comprises DUS-test data obtained from a first test performed on the DUS,

wherein generating the aggregated-data comparison comprises performing a statistical analysis of the DUS-test data and the aggregated data, and

wherein generating the DUS report comprises generating the query based on the statistical analysis and the at least one complaint.

10 . The method of claim 9 , wherein the DUS-related data and the aggregated data each comprise data for a plurality of variables, and wherein the performing the statistical analysis comprises performing a multi-variable analysis of the data for at least two variables of the plurality of variables.

11 . The method of claim 1 , further comprising:

at the device, receiving success-related data on a first sub-strategy of the one or more sub-strategies; and

at the device, adjusting the sub-strategy-success estimate of at least the first sub-strategy based on the success-related data.

12 . The method of claim 1 , wherein generating the aggregated-data comparison of the DUS-related data and the aggregated data comprises:

determining a basis of one or more vectors representing at least part of the aggregated data;

determining a baseline-data vector of the baseline data, the baseline-data vector utilizing the basis;

determining a DUS-data vector of the DUS-related data, the DUS-data vector utilizing the basis; and

determining a vector difference between the baseline-data vector and the DUS-data vectors.

13 . The method of claim 12 , wherein generating the DUS report based on the aggregated-data comparison comprises determining at least one of the one or more sub-strategies based on the vector difference.

14 . The method of claim 1 , wherein the DUS-related data comprises complaint data, and wherein generating the aggregated-data comparison of the DUS-related data and the aggregated data comprises:

determining a reduced data set of the aggregated data based on the complaint data;

determining a set of basis vectors based on the reduced dataset; and

identifying one or more principle parameter components for a complaint in the complaint data based on a projection of the basis vectors onto the DUS-related data; and wherein generating the DUS report based on the aggregated-data comparison comprises:

applying one or more rules about the principle parameter components; and

determining a sub-strategy based on the applied one or more rules.

15 . The method of claim 1 , wherein generating the aggregated-data comparison of the DUS-related data and the aggregated data comprises generating a pattern correlation between at least some of the DUS-related data and at least some of the aggregated data.

16 . A client device, comprising:

memory;

a processor; and

instructions stored in the memory that, in response to execution by the processor, cause the client device to perform functions comprising:

receiving a diagnostic request for a device under service (DUS),

sending, to the DUS, a DUS-test request to perform a test related to the diagnostic request,

receiving, from the DUS, DUS-related data based on the test,

sending the DUS-related data,

receiving a DUS report based on the DUS-related data, and

generating a DUS-report display of the DUS report.

17 . The client device of claim 16 , wherein the client device further comprises a network-communication interface, wherein sending the DUS-related data comprises sending the DUS-related data via the network-communication interface, and wherein receiving the DUS report comprises receiving the DUS report via the network-communication interface.

18 . The client device of claim 16 , wherein the client device further comprises a user interface, and wherein the functions further comprise:

displaying the DUS-report display via the user interface.

19 . A method, comprising:

receiving a diagnostic request to diagnose a device under service (DUS) at a device;

determining, at the device, a test based on the diagnostic request, the test related to at least a first operating state of the DUS;

requesting, by the device, performance of the test at the first operating state of the DUS;

at the device, receiving first-operating-state data for the DUS based on the test;

verifying, at the device, that the first-operating-state data is related or is not related to the first operating state; and

in response to verifying that the first-operating-state data is related to the first operating state:

generating a differential analysis by the device based on the first-operating-state data,

generating a DUS-report display by the device based on the differential analysis, and

sending the DUS-report display from the device.

20 . The method of claim 19 , wherein the first-operating-state data comprises data from at least two sensors associated with the DUS.

21 . The method of claim 19 , wherein the test comprises a plurality of tests for the DUS.

22 . The method of claim 19 , wherein verifying that the first-operating-state data is related to the first operating state comprises:

determining a first grid cell for the first-operating-state data;

determining an operating state related to the first grid cell; and

determining that the operating state related to the first grid cell is the first operating state.

23 . The method of claim 22 , wherein generating the differential analysis by the device based on the first-operating-state data comprises:

determining first aggregated data for the first grid cell; and

generating a first differential-analysis list for the first operating state based on a comparison of the first-operating-state data and the first aggregated data.

24 . The method of claim 19 , further comprising:

in response to verifying that the first-operating-state data is not related to the first operating state:

requesting, by the device, another performance of the test at the first operating state of the DUS;

at the device, receiving second-operating-state data for the DUS based on the test.