DIAGNOSTIC AND MAINTENANCE CONTROL SUBCOMMITTEE
08-C MEETING
Baltimore, MD
July 15-17, 2008

08-C Agenda

· Call to Order

· Approval of Agenda

· Reports

o Chair's report

o Secretary's report

o Liaison Reports (CS, I&M, AES)

o Brief presentations

·         Finalize AI-ESTATE

o Issues from AI-ESTATE demonstration

o Services discussion

o Document review

o Prepare for ballot

· SIMICA Ballot Resolution

· MAI Discussions

o Information model review

o Document review

o Prepare for ballot

· Pxxxx AI-ESTATE User's Recommended Practice

o Requirements Document (priority 1)

o Draft PAR (priority 2)

· Final Discussions on All Topics

· Review Old Action Items

· Review New Action Items

· Set Time and Location of 08-D Meeting

· Set Agenda for 08-D Meeting

· Adjourn

Tuesday, July 15, 2008

The meet was called to order by Mark Kaufman at 8:10 am.

Agenda was reviewed, modified and approved by committee vote.

Chair’s Report

The chair reported that P1636 passed by 75% exactly.

In April, IEEE Std 1522 was approved for withdrawal. It was thought that a full sponsor ballot would be required. Since then, the Standards Board met and decided that withdrawal will require a sponsor vote rather than a sponsor ballot. Therefore, SCC20 Steering will have to vote again in September.

The call for patents was also presented.

Secretary’s Report

Minutes of 08-B meeting were reviewed and approved.

Action Items and Open issues were reviewed and modified as appropriate.

Liaison Reports

CS Liaison: A report was sent out following the April meeting.

AES Liaison: Nothing to report.

I&M Liaison: Nothing to report.

Presentations

No presentations.

The DMC broke into two groups: standard working group and P1636 ballot resolution.

Standards working group:

Reviewed the 6.2 services introductory text and service order table from the services working group (Log 476 - IEEE_P1232_ReasonerManipulationServices v4.doc). Made minor editorial changes and decided to table the review of the service descriptions until later in the week to allow Alicia, Michelle, and Darryl time to update service order table with service descriptions.

Discussion occurred regarding the XML format for the models. Erol shared what Impact Technologies has been developing for XML documents of the D-Matrix and Bayesian Models as well as a reasoner XML output format for recommended actions. The D-Matrix (Log 477 – Dmatrix AI-ESTATE.xml) and Output (Log 478 Dmatrix Test_Output.xml) example were reviewed. The D-matrix example was based off the earlier Part28 XML that Darryl put forth at the last meeting. Erol brought up the DiagnosisOutcome attribute of Good or Candidate and whether we should consider something like a Grey Scale Health value (between 0 & 1) to indicate the level of health beyond just Good or Candidate.

Stepped through the previous version of the standard. Discussion took place on section 4.7, Service Order Dependence. It was agreed that the state diagram would be removed to be replaced with the new Service Order Table put forth by the Services Working Group.

Began review of the services descriptions (Log 479 - 6 2 Services Formatted 2008-07-15.doc). Reviewed the recommended services for Enhanced/Optional services. The group agreed with the recommendations, but tabled final decision until John and Tim could review.

Darryl joined the group via telecom. Did a quick review of the latest additions/changes to the services. The documents that have been updated by Darryl and Lockheed will be merged and final service descriptions completed for review before the end of the meeting. Looked at the introductory text and service order dependence table. Discussion ensued regarding whether the description should be part of section 4.7 or be in the services clause 6. The group thought that moving to clause 6 would be best, but tabled for future discussion with Tim/John. Reviewed the conformance section that was presented in April. The section allows for conformance to 6.1 or 6.2 services with “or” meaning “and/or”. An application is conformant with 6.2 services if it supports all non-optional (enhanced) services. Telecom ended with Darryl.

Tim joined the group, so open discussion items were brought up.

- Services WG recommended removing requestHypothesisConfidence as the value can be retrieved via the getDiagnosticResults. Tim agreed. Three services were recommended for Enhanced or Optional services. (Group decided Optional would be best description.) The services are: estimatedCostToStage, estimatedResourcesToStage, and getTestOutcomesFromDiagnosis. Agreement was made for the first two. The getTestOutcomesFromDiagnosis was discussed to be needed for model maturation. However, after further discussion, it was questioned that perhaps this service was for the CEM. Model maturation would be looking to use the DCM and actual values. Discussion will continue with John.

- Reviewed the Service Order Dependency table. Tim liked the format and content of the table. Table will be updated to provide section number with each service function. It was decided that the Example of the Order to call services in a diagnostic session, be moved to an annex or made part of the user’s guide that is to be developed in the future.

- Reviewed section 4.7 – Service Order Dependence. It was agreed that table 4 for model management services (6.1) would be updated to same format as the 6.2 services. The state diagram will be updated for newly defined states and show only transistions without labels on the arrows.

- Looked at contents of Clause 4.  It was decided to reorganize the standard. Recommendation is for the following.

O Make 4.1 (AI-ESTATE architecture) and 4.3 (Binding Strategy) part of Clause 4. Both of these sections are good information, but don’t really tell “How” or “What” the standard shall do.

o Move 4.2 (Interchange Format), 4.7 (Service Order Dependency), 4.5 (Status Codes), 4.4 (Extensibility), and 4.6 (Conformance) will be moved to Clause 5 in the order listed here. These sections all define the “How” part of implementing the standard.

o Make Clause 5 (Models) Clause 6 and make Clause 6 (Services) Clause 7. These clauses both define the “What” part of the Standard.

Wednesday, July 16, 2008

Meeting was called to order by Mark Kaufman at 8:00.  There was no plenary held. The committee adjourned to the conference room to review MAI questions/comments. Tim had numerous comments that were discussed and given to Joe and Mukund for incorporation. Completed comment review and committee broke into two groups: standards working group and BRC.

Erol presented the Impact Bayesian Output XML (Log 480 – aiestate_Bayes_Output.xml) and some discussion took place clarifying the standard intent for interchange of data.

Reviewed the MAI schema to ensure the request Lockheed had for tracing maintenance actions to specific test failures. It wasn’t clear to Joe or Alicia that updated schema supports the request. This will be discussed in a telecom with John Ralph after lunch. Joe will generate an instance document to represent use case.

Discussed the MAI document readiness for ballot. The plan is to have a document ready for quality review by 15-August.

Alicia brought up the need to discuss asserting DiagnosticOutcomes and the issues/concerns in doing so. Will discuss at a later point with Tim, John, and Darryl.

Started discussion of what’s needed for the User’s Guide/Best Practices. Began looking at the Purpose statement for the requirements document. Assigned action for numerous committee members to document concerns/issues.

Discussion with John Ralph took place. John agrees with Joe that the request by Lockheed is supported. Joe will put together the example to verify.

Clause 3 definitions were reviewed. Definitions that were identical to IEEE 100 were removed from the 1232 standard unless multiple definitions were found in 100. In this case, the definition appropriate for 1232 was left in the standard. Reviewed any remaining definitions not in 100 and updated to group consensus.

Roadmap

The roadmap was reviewed and updated.

IEEE SCC20 Diagnostic and Maintenance Control Subcommittee Roadmap

Created and reviewed the agenda for the 08-D meeting.

Reviewed Old and New action items.

Alicia presented the outcome for the 06C-03 action item (Log 481 - Action Item 06C-3_071608.doc). There are some similar entity types.  Needs further discussion with Tim/John to determine what to do with it.

Thursday, July 17, 2008

Reviewed the roadmap and agenda for the next meeting with the full committee.

Continued discussion on the User’s Guide. Idea was brought up to consider having a DMC User’s Guide vs. just a 1232 User’s Guide.  It was agreed that it would be a 1232 User’s guide to include DMC standards structure, purpose, and vision model of how the standards are related and intended to work together.

Steve Butcher joined the meeting to present the part 28 schemas he has been working.  The committee liked the format of the fault tree model that was shown and agreed the XML instance document was easy to read and understand. Consensus was to move forward with this approach for the XML schemas in the standard.

Meetings was adjourned at 12:15 pm

Attendees

Action Item Summary

Old Action Items

· Action Item 06C-3: Alicia Helton will examine the 1232 models for elements that may be related or duplicated in a P1636.x schema. Such identification will enable use to ensure consistency between the schemata and provide a mapping as necessary.

Status: CLOSED

· Action Item 06C-4: Pat Kalgren to use his AUTOTESTCON 2006 paper to start developing a prognostics annex for 1232. This paper will provide a set of definitions as a starting point.

Status: OPEN Pat is going to examine the paper and other sources for a possible annex. The gray scale health may serve as an example in the annex.

· Action Item 07A-3: Darryl B. to obtain a description of the operational/environmental information from recording devices for a commercial platform relevant to diagnostics.

Status: OPEN This action item is in support of possible new 1636.x Operational Context standard.

· Action Item 07A-13: P1232 working group co-chairs to prepare final draft of P1232 for April meeting.

Status: OPEN, Modified to be due electronically by August 15, 2008.

· Action Item 07B-6: Michelle H. to add text to the P1232 standard expressing that the focus of the models is to define semantics and to facilitate information exchange. As a result, it is possible, if not likely, that an instantiation of the model will not be optimized for computational purposes (wordsmithed for clarity).

Status: OPEN (may need help from John S. and Tim W.)

· Action Item 07C-6: Brit Frank to complete a QA review of the P1232 draft prior to submission to MEC.

Status: OPEN

· Action Item 07D-4: Darryl B. to write an introduction to ISO 10303-21 as an informative annex to P1232.

Status: OPEN

· Action Item 07D-6: Darryl B. to add relevant services to support “ActualUsage.”

Status: CLOSED

· Action Item 07D-7: Alicia H. and Darryl B. to develop a service for asserting outcomes.

Status: OPEN

· Action Item 08A-02: Darryl to review Clause 4.4 to see if it needs modification and ensure it supports model exchange in both EXPRESS and XML.

Status: OPEN

· Action Item 08B-02: Joe S. to make changes to MAI schema resulting from schema review. Those changes affecting the EXPRESS will be be provided to John S. to make the associated changes in the information model.

Status: CLOSED

· Action Item 08B-03: John S. to check on whether there is a need for a Letter of Consent to use the EXPRESS-G figures generated by EDMVisualExpress.

Status: CLOSED

· Action Item 08B-04: Joe S. to update the MAI draft standard to incorporate the editorial changes recommended by the subcommittee.

Status: CLOSED

· Action Item 08B-05: All members of the subcommittee to provide a detailed review of the draft P1636.2 standard by May 23, 2008. Comments should be sent to Joe Stanco.

Status: OPEN Revised due date: August 1, 2008.

· Action Item 08B-06: Oscar F. to examine the modified information models to determine impact on regenerating the WSDL for both 6.1 and 6.2 services. If impact is small, he will generate the WSDL. If it is large, impact on schedule will determine whether or not the WSDL will be generated and included in the standard.

Status: CLOSED

· Action Item 08B-07: John S. to update the definitions of the various outcome constants to tighten the semantics. The specific definitions to use are those provided by the April 2 email from Darry B. (titled, “suggested changes for GOOD/BAD/CANDIDATE and for hierachical consistancy”).

Status: OPEN

· Action Item 08B-08: Darryl B. and John S. to reword the extension mechanism from the 2002 AI-ESTATE for the P1232 standard. The rewording will focuses clarity, consistency, and intent of maintaining semantic integrity combined with appropriate flexibility.

Status: OPEN (in process)

New Action Items

· Action Item 08C-01: John S. to create the final MAI information model based on final modifications to the XML Schema.

Status: OPEN

· Action Item 08C-02: Oscar F. to generate WSDL specification based on updated services for P1232.

Status: OPEN

· Action Item 08C-03: Joe S. to generate a MAI Instance document showing how it can relate specific maintenance action to a specific test failure(s).

Status: OPEN

· Action Item 08C-04: Carry S., Erol, Alicia, Darryl, Tony A., John S., and Steve B. to document problems, issues, concerns, and/or difficulties in using the AI-ESTATE standard.  Information will be used in the development of the User’s Guide document.

Status: OPEN

· Action Item 08C-05: Mark to develop draft requirements document and PAR for the 1232 User’s Guide.

Status: OPEN

Open Issues

· Issue 07B-1: The current order constraint in 1232-2002 is difficult to understand and, therefore, difficult to use. The DMC decided to “minimalize” the order constraint to focus only on preconditions and added actions to the model. It is recognized that this minimalist construct is at best suboptimal and possibly “broken.” Unfortunately, timing prevents a new construct being included in the model, and the DMC felt something needed to be there to address ordering. For the next revision, a more expressive and usable order constraint facility needs to be incorporated into the model, replacing the current minimalist construct. One proposal on hand is Log #451.

Status: OPEN Medium Priority

· Issue 07C-1: Need to perform a trade study to determine what new services are actually required. This is essential for establishing a usable scope for the service specification. The focus here is for the next revision of the standard.

Status: OPEN Low Priority

· Issue 07D-1: These standards (especially AI-ESTATE) are difficult to understand due to the large number of options available to an implementer. It is really important to provide some kind of guidance to the implementer. The hope is that a User's Guide can be put together once the revision has cleared its next ballot.

Status: OPEN Medium Priority

· Issue 08A-1: Craig M of NAVAIR suggest several additions to the SIMICA model at the 08-A meeting. One of those suggestions was to add a subtype of Design Model: Obsolescence Model. The question is whether the Obsolescence Model can be used a basis for triggering a maturation event and thereby affecting the Diagnostics Model. John S. has the use case (Asset Specific Diagnostics).

Status: OPEN Medium Priority

· Issue 08A-2: John S. and Darryl B. raised the issue of Part 28 for XML schemas to support validation of instance models against the information model. The general issue of validating XML instance documents against EXPRESS information models needs to be explored, whether using a schema derived from Part 28 or an XML schema geared toward XSLT translation to Part 21.

Status: CLOSED

Items Logged at 08-C Meeting

· #476 IEEE_P1232_ReasonerManipulationServices v3 (D. Busch)

· #477 Dmatrix aiestate (E. Esen)

· #478 Dmatrix test_output (E. Esen)

· #479 6 2 Services Formatted 2008-07-15 (A. Helton)

· #480 aiestate_bayes_output (E. Esen)

· #481 Action Item 06C-3_071608 (A. Helton)

Proposed 08-D Agenda

· Call to Order

· Approval of Agenda

· Reports

o Chair's report

o Secretary's report

o Liaison Reports (CS, I&M, AES)

o Brief presentations

· Pxxxx AI-ESTATE User's Guide

o Review Requirements Document (priority 1)

o Review PAR (priority 2)

· Finalize AI-ESTATE

o Document review

o Prepare for ballot

· Finalize MAI

o Prepare for ballot

· SIMICA

o Next Projects

· Final Discussions on All Topics

· Review Old Action Items

· Review New Action Items

· Set Time and Location of 09-A Meeting

· Set Agenda for 09-A Meeting

· Adjourn