Day 1: Tuesday September 12, 1999: Convened at 9:10 AM

1 Attendees are shown in Enclosure 5.

1.0 Co-Chair John Sheppard called the meeting to order.

1.1 The 99D agenda was reviewed and approved with minor modifications.

1.2 Chair's Report

Automatic archiving of e-mail messages over the reflector is now working.

The 1232.1 was elevated to full use in September of 1999.

• The minutes from the last meeting were approved.

1.5 IEC WG7/TC93 Liaison Report:

John Sheppard reported that Randy Simpson is no longer part of working group 7 of IEC as Liaison to SCC20.

The liaison position is currently open.

John Sheppard reported the following Regarding the ITC workshop.

ITC held the 3rd workshop on System Test and Diagnosis on 9/30/99 in Atlantic City. The workshop was well attended.

John Sheppard gave a presentation on AI-ESTATE.

IBM a participate in the Distributed Management Task Force (DMTF) gave a presentation on the diagnostic component of the Common Information Model (CIM, a UML model).

1.7.1 Reviewed CEM in terms of the unified standard.

Changes to CEM:

Model element is tied to hierarchical element rather than individual subtype elements

Repair entity has been added to parallel the test entity.

Tied repair item to function.

Tied resource to cost

Made action a hierarchical element.

Made all attributes of diagnosis optional.

Tied order operator back to model.

The relationships between failure modes, faults and failures.

 

Example:

A transistor junction is open (failure mode) causing a stuck at 0 at the device edge (fault) causing a screen to go blank on a display (functional failure)

No Changes

Changes: EDIM => DIM

Deleted pos_neg

Permit conjuncts or disjuncts, but not both.

Limit standard values such that USERDEFINED not allowed. (Applies to test_outcome and diagnosis.outcome).

Deleted model.diagnosis from the diagnostic entity.

No changes to date.  Changes will occur to maintain consistency with the CEM.

2.1 Reviewed PCWG recommended changes

2.1.1 Changes to D&MC Operations Manual

• It was noted that there is insufficient documentation regarding the length of term regarding CoChair positions. A discussion followed. A recommendation will be made to PCWG to address this issue.
• The issue of consensus was discussed. The heading of 3.3 was eliminated and the text modified to reflect Robert's Rules of Order.


Motion by Tim Wilmering and seconded by Jack Taylor to approve the changes as recommended by D&MC. The motion was unanimously approved.

1232  Requirements document with PCWG recommendations, unanimously approved.

1522 Requirements document with PCWG recommendations, unanimously approved.

Revised PAR 1232 document with PCWG recommendations, unanimously approved.

2.2.1 Amanda Giarla asked the committee how a "provider" might introduce a new service not listed in the atomic, higher-order or utility services. The committee recommended that provider generated services, designed and or built by a provider, be submitted to the committee as a proposal for consideration to be included in the standard.

2.2.2 Draft Outine of Services

W Atomic
X Higher-Order Services
Y Utility Services

2.2.3 Preliminary review of versions of the specifications going back to draft 2.1 for higher order services that were previously considered important but subsequently deleted. Tim Wilmering will merge these previously considered services for review on day 3 of meeting 99D.  (action 99D-1)

2.3  With regard to open issue 98D-1 the subcommittee agreed that an additional conformance item will be to permit outputting session trace as specified by the DCM and its associated Interchange format.

2.4 With regard to open issue 99C-1, ISO10303 Part12 (EXPRESS-I) versus Part-21 (Step Physical File Format) a discussion resulted and lasted until the end of the day.

Day 3: Thursday September 13, 1999: Convened at 9:00 AM

3.1 With regard to open issue 99C-1, ISO10303 Part12, "Express-I Language Reference Manual" versus Part-21 "Clear Text Encoding of the Exchange Structure" (sometimes referred to as Step Physical File Format) a short discussion commenced with a resulting motion.

Motion by Tim Wilmering to change in the interchange format in the next version of the standard ISO 10303 Part-12 by Part-21. Seconded by Les Orlidge.  Approved by consensus. Mark Kaufman assigned to make replacement. (action 99D-2)

W Atomic ("primitive")

W.1 Create
W.2 Delete
W.3 Get
W.4 Put

X Higher-Order Services

X.1 Control Services

Initialize Session
Setup
Process Setup
Start Session
Suspend Session
Resume Session
Kill Process
backtrack (n), where n is number of steps
Do my test
Change - Optimize
select_test (Already defined standard)
select_test based on hypothesis

X.2 Analysis Services

Estimated time to complete
Time Left to Test
Resources needed to complete
Analyze Hypothesis - Analyze the user identified hypothesis for feasibility
Historical Things
Similar
Likely
Unlikely

X.3 Explain Services

X.3 Show Inference Trace
X.3 Show Session Trace

X.4 Inference Services

X.4 Process Test Outcome
X.4 Process Test Batch
X.4 get_most_likely_diagnoses - Count or likelihood

X.5 Learning Services

X.5.1 update_test_cost_time
X.5.2 update_test_cost_currency
X.5.3 update_resource_cost_time
X.5.4 update_resource_cost_currency
X.5.5 update_action_cost_time
X.5.6 update_action_cost_currency

Y Utility Services

Y.1 Counting Services
Y.2 Existence Services
Y.3 Indexing Services

3.2.2 Tim Wilmering's merged list of previously considered services was reviewed and logged as item #303. An action item was given to Tim to analyze the list for services that already exist, services to be implemented in the next version of the standard and services to be deferred.  The resultant list will be placed on the reflector for discussion. (action 99D-4)

3.3 Randy Simpson's proposals for action items 99A-10 and 99C-16 were introduced and logged as log item #301 and log item #302.

3.3.1 Randy Simpson's proposed Testability and Diagnosability Characteristics and Metrics (P1522) for Draft Section 4.3, log item #302 was reviewed.

3.3.2 D&MC Committee Recommended 1522 Changes

Intro

• Change third bullet to “Errors in Diagnosis”
• Change first sentence of following paragraph to read: “ The last item will include …”

4.3.1

• Fault Detection – The process of identifying and reporting one or more faults within a repair item (as defined in 1232.1)

4.3.2

• Fault Isolation – The process of identifying and locating one or more faults to a level consistent with a specific requirement or goal

4.3.3

• False Alarm -  A fault indication where no fault exists.

 I. Alarm – A fault indication

2. False Alarm -  A fault indication where no fault exists.

a. Can Not Duplicate – A false alarm that triggers a maintenance action
b. “Nuisance Alarm” – A false alarm that does not trigger a maintenance action

3. True Alarm – A fault indication where a fault exists

a. Can Duplicate – An alarm that triggers a maintenance action
b. “Ignored Alarm” – An alarm that does not trigger  a maintenance action

4. False Assurance – A lack of fault indication where a fault exists, that leads to an unscheduled outage, mission abort, or other loss of service when service was expected.

3.4 The committee adjourned at 4:30.

3.5 After adjournment John Sheppard gave a demonstration of the EDMVisual Express Tool to SCC20 attendees.
 

Action Item 98C-13: Greg Bowman will contact Lisa Fowbles (DoD Config Mgmt) about exploring opportunities to marry AI-ESTATE to NATO CALS model.
Status: ONGOING.  Greg Bowman exploring establishment of a formal relationship.
Now closed Greg gave up.

Action Item 99A-10: Randy to create a proposal for false alarm metric(s) for the Testability standard.
Status: CLOSED

Action Item 99A-11:  Greg accepted an action to explore the possibility of creating a demonstration of AI-ESTATE as part of V-22 (HeloPlane), to test capability to provide partial/reconfigurable TPS test functionality.
Status: ONGOING.  Marketing idea that AI-ESTATE models can be helpful in the development of TPSs

Action Item 99B-7: Dave Kleinman to provide a proposal based on Qualtech's approach to computing metrics under multi-outcome assumptions, for the purpose of assisting in defining model-based metrics for P1522.
Status: OPEN

Action Item 99B-8: Eric Gould to provide a proposal based on DSI's approach to computing metrics under multi-outcome assumptions, for the purpose of assisting in defining model-based metrics for P1522.
Status: OPEN.  Mark Kaufman will inform Eric of the assigned action.

Action Item 99C-1: Tim Bearse to provide an editable electronic copy of the 2165 Mil-Handbook to John Sheppard for subcommittee use (FTP area).
Status: OPEN

Action Item 99C-2: John Sheppard and Greg Bowman will work to get logged items onto the website.
Status: OPEN

Action Item 99C-3: John Sheppard will update the models, incorporating comments from the meeting.
Status CLOSED.

Action Item 99C-4: Tim Bearse will write up a strategy for creation of bindings for the unified standard.
Status: OPEN

Action Item 99C-5: Tim Wilmering will develop a naming convention for specifying the accessor services of 1232. This will be used to facilitate the generation of binding strategies.  Exam current services to see if convention already exists.
Status: OPEN

Action Item 99C-6: Mark Kaufman will convene an electronic meeting to address higher order services.
Status CLOSED.

Action Item 99C-7: Mark Kaufman will compile the new 1232 document, affectionately known as "Little Shamu".
Status: OPEN

Action Item 99C-8: Mark Kaufman will solicit identification of services from Detex Systems, Inc.
Status: OPEN

Action Item 99C-9: Dave Kleinman will solicit identification of services from Qualtech Systems, Inc.
Status: OPEN

Action Item 99C-10: Greg Bowman will post the paper "Formal data Models for SGML and HyTime" regarding the harmonization of SGML and STEP on the web page.
Status: OPEN

Action Item 99C-11: Mark Kaufman will provide the 1232 PAR and copies of P1232 and P1522 "requirements documents" to PCWG.
Status: CLOSED

Action Item 99C-12: Mark Kaufman will rewrite the Introduction to P1522.
Status: OPEN

Action Item 99C-13: John Sheppard will author section 1 (all) and section 4.1.3 of P1522.
Status: OPEN

Action Item 99C-14: Amanda G. will author sections 4.1.1 and 4.1.2 of P1522.
Status: OPEN

Action Item 99C-15: Greg Bowman will author section 4.1.4, and all of section 4.4 of P1522.
Status: OPEN

Action Item 99C-16: Randy Simpson will author section 4.3 of P1522.
Status: Closed

Action Item 99C-17, John Sheppard will set up public web site for working development of P1522 section 4.
Status: OPEN

Action Item 99C-18: Mark Kaufman will reform the P1522 and re-send.
Status: OPEN

Action Item 99C-19: Hugh Pritchett will brainstorm on the metric primitives listed in minute's item 2.5.8
Status: OPEN

Action Item 99C-20: John Sheppard will put RMS Partnership URL on DMC web site.
Status: OPEN

Action Item 99C-21: Greg Bowman will create new banner for DMC web page.
Status: OPEN

Action Item 99C-22: Greg Bowman will provide descriptions of the candidate higher order services based on previous documentation.
Status: OPEN

Action Item 99C-23: John Sheppard will make the agreed upon changes to the Operations Manual.
Status: Closed

Action Item 99C-24: Greg Bowman will distribute TC-184 (PLCS) (log item 294) to members-only reflector.
Status: OPEN

Action Item 99C-25: Mark Kaufman will be sending a letter of concern to the SCC20 regarding the costs and time.
Status: closed

Action Item 99C-26: Mark Kaufman and or John Sheppard will forward the full use recommendation to Steering and will write the letter that the SCC20 Chair will forward to the IEEE.
Status: closed

Action Item 99C-27:  John Sheppard will take the action to request approval from Steering.
Status: closed

Action Item 99C-28: Amanda Giarla will acquire the 99C model changes from the web and enter then as logged items.
Status: OPEN

 New Action Items

Action Item 99D-1: Tim will merge the higher order service definitions collected from the review of P1232.2 drafts 2.1-3.2.
Status: CLOSED

Action Item 99D-2: Mark Kaufman will change part-12 to part-21 in the exchange format portion of the unified standard.
Status: Open

Action Item 99D-3: Tim Bearse will write the specifications for Utility Services, counting, existence, and indexing.
Status: Open

Action Item 99D-4: Tim Wilmering will analyze the list of previously considered services for services that already exist, services to be implemented in the next release, and services to be deferred.  The resultant list will be placed on the reflector for discussion.
Status: Open

Action Item 99D-5: Mark Kaufman will take current proposals from Randy Simpson (#301 & #302) and fold them into the 1522 draft.
Status: Open

#285  99A AI-ESTATE Meeting Minutes, February 1999, Monterey, CA (4/27/99)

#286  TDC Trip Report (4/27/99)

#287  Draft Unified Common Element Model  (4/27/99)

#288  GKS Model for Counting/Existence Services (4/27/99)

#289  'Setup' Entity and Array Passing: Counting/Existence Services (4/27/99)

#290  Rev'ing Up AI-ESTATE: Counting/Existence/Test Availability Services (4/27/99)

#291  STRIPS Model Proposal (4/27/99)

#292  FFD Testability Metric (4/28/99)

#293 99B AI-ESTATE Meeting Minutes, April 1999, Alexandria, VA (7/27/99)

#294 ISO/TC184/SC4 Product Life Cycle Support document

#295 IEEE 1232 PAR, IEEE 1232 Requirements Document Version 6,  IEEE 1522 Requirements Document Version 2

#296 P1522 Straw Man (Mark's file name P1522-SM).

#297 The updated 1232 information model, 7/28/99.

Items logged at 99D.

#298 1232 Requirements document, version 6 dated 10/13/99  (10/14/99)

#299 1522 Requirements document, version 2 dated 10/13/99  (10/14/99)

#300 Current AI-ESTATE Models as of 10/14/99

#301 Proposal for Testability and Diagnosability Characteristics and Metrics, False Alarms (P1522) as required by action item 99A-10 (10/14/99)

#302 Proposal for Testability and Diagnosability Characteristics and Metrics, Section 4.3 (P1522) as required by 99C-16 (10/14/99)

#303 Initial merged list of previously considered services from previous drafts going back to 2.1.
 

Issue 98C-5 (From the 1232.2 Recirculation comments)  Section 7 is also loosely worded and ambiguous. It allows implementations claiming to be standards compliant to have stubs that return the "Service_not_available" status code, while insisting subset compliance is not permitted. As stated in the original response, "We appreciate the concern as regards a baseline expected behavior. We hope to address this concern, perhaps in the development of one or more AI-ESTATE Recommended Practices in the future." Concerning the suggestion for a state diagram, an early version of 1232.2 had such a diagram and found all services allowable in all cases (at least for now). Concerning clause 7, we felt that requiring implementation of all services beyond stubs was potentially too demanding; however, we did not want to open the door to sub setting until we knew which subsets made sense.  This is an issue we expect to resolve when moving to full use.
Status: OPEN  Review 'Service not Available' status codes after next draft of document is available.

Issue 97B-3: (Unification) High order reasoning services, what are they and where do they belong? Should they be part of Application Executive or part of the diagnostic reasoner or should they stand alone. Additional higher order functions, including 'revert' and 'choose test' are examples. An earlier draft of 1232.2 should be reviewed to identify many of the higher order services.
Status: CLOSED - Low Priority (High priority for 99-D meeting)

Issue 98B-8: Should a standard or recommended practice be generated to represent a baseline expected behavior?
Status: OPEN - Low Priority

Issue 99C-1: The standard could allow the implementer a choice of either ISO10303 Part-21 or ISO10303 Part-22.  This allows more freedom in implementation, but causes a potential need to translate between the two formats.
Status: Closed, selected part21 to replace part 12 part 22 deferred.

Issue 98D-1: Is an interchange format needed for the Dynamic Context Model, perhaps to deal with TMIMS-related issues and/or case based reasoning?
Status: CLOSED -Low Priority(High priority for 99-D meeting)
Yes this is needed.

New Issues

Issue 99D-1: Defer addressing the following higher-oder services: Explain Choice of Test, Explain Hypothesis and Learn.
Status:OPEN
 

I. Call To Order

II. Approval of Agenda

III. Reports

A. Chair
B. Secretary
C. Liaison

None

A. High Order Services
B. Draft Review
C. Proposals
D. Model Review
E. Open Issues
F. Section Work

A. Draft Review
B. Proposals
C. Model Issues
D. Open Issues
E. Metrics Issues
F. Section Work

VIII. Time and Location of 00-A

IX. Set Agenda for 00-A

X. Adjourn

I. Call To Order

II. Approval of Agenda

III.Reports

A. Chair
B. Secretary
C. Liaison

None

A. High Order Services
B. Draft Review
C. Proposals
D. Model Review
E. Open Issues
F. Section Work

A. Draft Review
B. Proposals
C. Model Issues
D. Open Issues
E. Metrics Issues
F. Section Work

VIII. Time and Location of 00-B

IX. Set Agenda for 00-B

X. Adjourn