DIAGNOSTIC AND MAINTENANCE CONTROL SUBCOMMITTEE
09-A MEETING
Orland, FL
January 13-15, 2009

09-A Agenda

• Call to Order

• Approval of Agenda

• Reports

  • Chair's report

  • Secretary's report

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

  • Brief presentations---D. Droste, Electronics Prognostics PAR

• Pxxxx AI-ESTATE Users Guide

  • Review Requirements Document (priority 1)

  • Review PAR (priority 2)

• Finalize AI-ESTATE

  • Document review

  • Prepare for ballot

• MAI

  • Ballot Status

  • Ballot Resolution

• SIMICA

  • Operational Context Discussions

  • User Guide Discussions

• Final Discussions on All Topics

• Review Old Action Items

• Review New Action Items

• Set Time and Location of 09-B Meeting

• Set Agenda for 09-B Meeting

• Adjourn

Tuesday, January 13, 2009

The meeting was called to order by Mark Kaufman at 9:57 am.

Agenda was reviewed and approved by committee vote.

Chair’s Report

P1636 is in the final throes of the approval process. The scope in the standard mentions a draft of P1232 but the PAR mentions the approved 2002 standard. This needs to be resolved. Otherwise, everything seems to be resolved.

P1636.2 ballot finished and passed. There are over 600 comments to resolve.

P1232 needs to get into ballot ASAP since its PAR expires in December 2009 and the full use period ended in 2007.

Secretary’s Report

Minutes of 08-D meeting were reviewed and approved.

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

Liaison Reports

CS liaison had nothing to report.

I&M liaison had nothing to report.

AES liaison had nothing to report.

Presentations

Dave Droste will be giving a presentation on Wednesday.

P1232 Discussion

The P1232 document was reviewed to ensure all sections were present.

The P1232 document was then updated, filling in several missing sections. These sections included the Model Service Management tables, the Part 21 annex, the introductory paragraph on semantics, and several other small edits. The document was returned to the working group to resolve some additional deficiencies in preparation for the session Wednesday.

Wednesday, January 14, 2009

Presentation

Dave Droste started the day with a presentation on a proposed new task group for Electronics Prognostics. Based on the discussion, a joint meeting at the Bath SCC20 will be set up for further discussion.

Following the presentation, the MAI BRC broke out. The rest of the committee continued with P1232.

P1232 Discussion

Alicia provided another updated version of the document. The document underwent an additional review with a few changes being made, mostly in the Extensibility and Services sections. The only remaining component to be included is a paragraph referencing and locating external files:

• EXPRESS long form schemata

• Part 28 XSDs

• WSDL specifications

The DMC broke for lunch and reconvened following a brief Steering Committee meeting.

Following Steering, two motions were handled.

Motion: John S. moved that P1636 be modified to make the Scope consistent with the current PAR and that modified standard be recirculated to the balloting constituency. Seconded by Michelle H. The motion passed without objection.

Motion: Michelle H. moved that P1232 be submitted for ballot contingent upon completion of the table of contents and web site reference. Alicia H. seconded. The motion passed without objection.

AI-ESTATE Users Guide

Mark kicked off the discussion on the AI-ESTATE Users Guide by mentioning that the Users Guide Requirements document will be needed. Users Guide has been talked about for years. Mark asked the group if anyone would be interested in working on the Users Guide. The copy Mark has is an old one, which might be pretty generic. Michelle mentioned that she would be interested, however, she is unable to commit at this time. Mark agreed.

Since the group did not have the needed information to adequately discuss the Users Guide, Mark suggested that the group ask the following: 1) what should be in the Users Guide and 2) how much of it should be covered. What is the Users Guide trying to do? Michelle suggestions were: 1) how do you read it, 2) how do you use it. One of the nice things about user guides is that they are informative not normative.

Michelle recommended that whoever works on the users guide should be someone who has worked on 1232.

The Users Guide Requirements document was reviewed in support of the development of the Users Guide. The scope and purpose were looked at first. Mark recommended that the scope should be expanded, Michelle agreed. One of the questions is, when it says implement IEEE 1232, what is meant by it. Michelle said it should provide a background and how to interpret your models and entities. It is supposed to explain what was essentially explained in the standard. Simon suggested that the Users Guide should be a stand alone document and should introduce the concept. Mark also mentioned that examples would be good to include since they are not usually included in the standards. Within the users guide, should it be more fine detail, assuming that background is already known.

Michelle asked what the intent of having an IEEE 1232 Conformance requirement section was. Mark suggested that this section was to give more information.

Michelle recommended adding additional appendices to cover Part 28, Part 21, and WSDL. Requirements document was updated to include Appendix C for Part 28 and Appendix D for Part 21 and Appendix E for WSDL. Further discussed was adding the appendix for WSDL. Michelle thought that most of the WSDL information is available in the internet and adding it to the users guide might not be necessary. For the time being it is added to the Section 2 Requirements.

Simon asked if there are other standards that have users guide which can be used as a guide to develop the 1232 Users Guide. Might be redundant to have a users guide as many people might use the standard alone. Mark reiterated that the standard lacks examples and might be good to have a document which gives you access to these examples. The users guide should only be used for information to help implement 1232.

Simon asked that once we verify if the requirements are adequate would that be sufficient for the PAR. If it’s the committees decision to go ahead with the PAR then Mark would process. This will be further discussed when the entire team reconvenes Thursday, 15 Jan.

It’s more than background information and details. It should include a description of interrelationships between the AI-ESTATE standards. Simon suggested the use of the door bell example used during the demo at AUTOTESTCON. Some of the examples are not useful if they are merely in text. Mark suggested that they should also include downloadable material from the website. Simon asked if the users guide would also be at the same level of review as the standards. Mark indicated that it would, however the review would not be as rigorous. Simon asked Mark if there were any templates or guidelines for developing users guide on the website that he was aware of.

Alicia asked if the overview of EXPRESS is needed. The 1232 standard includes an Annex on EXPRESS so it might be redundant to include in the users guide. Mark asked if there was anything needed to be added for that in the users guide. It might be sufficient to direct to the standard for detailed information.

The purpose and scope were updated. Also updated was the list of Relevant ATML and SIMICA documents to include IEEE 1671 for ATML and IEEE 1636, IEEE 1636.1 and IEEE 1636.2 for SIMICA. Changes made to the Users Guide Requirements document will be used in the development of the Users Guide.

Alicia emailed the revised version of the Users Guide Requirements document to John S.

Mark asked if someone knew who the great champion of the Users Guide was. Tim responded that there is none. Tim asked Michelle if she and Alicia had any lessons learned. Michelle said that lessons learned will be available. Tim also asked Simon about lessons learned.

John S. asked Tim if he remembered what had been the outcome of the Steering meeting in regards to dropping the requirements from the SSC20 requirements document. The outcome was that before dropping the requirements there has to be a revision to the operations manual.

On the agenda Thursday:

• Comments on the Users Guide Requirements document from John S.

• Administrivia

• 1626: SIMICA contents discussion and SIMICA Users Guide Requirements document discussion

• Per Tim, there is nothing to talk about regarding these two items

• Trying to get public information regarding flight data

Thursday, January 15, 2009

Administrivia

The action items were reviewed again.

The proposed agenda for the next meeting was updated.

The roadmap was reviewed and updated.

The next meeting is planned for Bath, UK during the third week of April.

The meeting adjourned at 8:24 am.

The meeting was reconvened by T. Wilmering at 11:13 to consider a wrinkle from the IEEE.

Issue: The IEEE raised an issue that putting “-2002” in the scope of the standard would tie it to an out-dated version. Specifically SIMICA refers to entities in the model that either do not exist or have been changed over the -2002 version. Therefore, we cannot simply revert and recirculate.

Motion: Mark K. moved to modify the P1636 PAR to remove “-2002” from 1232 from the Scope and leave 1232 undated. In addition, the Scope of the P1636 document to remove “/D4” from 1232 and leave 1232 undated. Then to proceed to have the PAR approved by NEWCOM and document recirculated. John S. seconded. Approved without objection.

The meeting adjourned again at 11:19.

Attendees

Action Item Summary

Old Action Items

• 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. Tim W. will take an action to attempt to acquire a publicly available DFDAU and FOQA data frame specification.

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

  Status: CLOSED, Draft provided for 08-D meeting. Final draft pending results of that meeting.

• 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: CLOSED

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

  Status: OPEN (Pending completion of final draft.)

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

  Status: CLOSED (OBE)

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

  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: CLOSED

• 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 08D-02: Alicia H. to incorporate results of open service discussion into the P1232 draft.

  Status: CLOSED

• Action Item 08D-03: Alicia H. or Michelle H. to add a model management service table to the P1232 draft.

  Status: CLOSED

• Action Item 08D-04: Oscar F. to complete the WSDL service specification for incorporation into the P1232 draft.

  Status: CLOSED

• Action Item 08D-05: John S. to complete the model updates for incorporation into the P1232 draft.

  Status: CLOSED

• Action Item 08D-06: John S. or Steve B. to generate the XML schemata based on the P1232 information models for incorporation into the P1232 draft.

  Status: CLOSED

• Action Item 08D-07: Extensibility section to be completed and incorporated into P1232 draft, depending on outcome of Darryl B. proposal. Darryl B. to be responsible for any updates.

  Status: CLOSED

• Action Item 08D-08: Michelle H. to update and incorporate P11 annex into P1232 draft.

  Status: CLOSED

• Action Item 08D-09: Darryl B. to prepare P21 annex for incorporation into P1232 draft.

  Status: CLOSED

• Action Item 08D-10: Darryl B. to prepare P28 annex for incorporation into P1232 draft.

  Status: CLOSED

• Action Item 08D-11: Tim W. to update conformance section, especially focusing on P21/P28 conformance for incorporation into the P1232 draft.

  Status: CLOSED x 3

• Action Item 08D-12: Michelle H. to review and revise Bibliography and Normative References for the P1232 draft.

  Status: CLOSED

• Action Item 08D-13: Michelle H. to prepare a final P1232 draft.

  Status: CLOSED

• Action Item 08D-14: John S. to prepare commentary for the Bayesian model specifying how to order the test/diagnosis outcomes for the probability tables to ensure the values align. The proposal is for this language to use a “radix-counting” approach.

  Status: CLOSED

• Action Item 08D-16: John S. to fix the constraints in the Bayesian model focusing on checking sums-to-one. The indexing is a bit messed up.

  Status: CLOSED

• Action Item 08D-17: John S. to examine the OASIS DEX on Aviation Maintenance as it relates to SIMICA (including operational context?).

  Status: OPEN

• Action Item 08D-18: Tim W., Michelle H., Pat K., and Mike S. to inquire with their companies, seeking out potential subject matter experts for operational context.

  Status: OPEN

• Action Item 08D-19: Mark K. to send an appeal to the DMC listserv for members to provide comments on Test Results to the SA Secretary. That appeal should include the location in the document where the address can be found.

  Status: CLOSED

• Action Item 08D-20: Michelle H. to set up a conference call with Michelle, Tim, John, Darryl, and any other interested parties to resolve the extensibility issue.

  Status: CLOSED (OBE)

New Action Items

• Action Item 09A-01: Mark K. to serve as ballot designee and to initiate the ballot process for P1232.

  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 Low 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 High Priority (AI-ESTATE User's Guide is now being worked.)

• Issue 08A-1: Craig M of NAVAIR suggested 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 Low Priority

• Issue 08D-1: 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 Low Priority

• Issue 08D-02: 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 High Priority (John S. and Steve B. part done. Erol E. and Pat K. have become Simon J.)

Items Logged at 09-A Meeting

• #484 Electronics Prognostics Presentation (D. Droste, 1/14/09)

Standards Development Roadmap

Proposed 09-B Agenda

• Call to Order

• Approval of Agenda

• Reports

  • Chair's report

  • Secretary's report

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

• Brief presentations---Impact, ISO 13372/13374 Diagnostics Parts

• Brief presentations---J. Sheppard, AI-ESTATE Demonstrations

• Brief presentations---J. Stanco, MAI Demonstrations

• Pxxxx AI-ESTATE Users Guide

• Finalized Requirements Document (priority 1)

• Finalize PAR (priority 2)

• AI-ESTATE Ballot Resolution

• SIMICA

  • Operational Context Discussions

  • User Guide Discussions

• Joint HI-DMC Meeting on Electronics Prognostics

• Final Discussions on All Topics

• Review Old Action Items

• Review New Action Items

• Set Time and Location of 09-C Meeting

• Set Agenda for 09-C Meeting

• Adjourn