IEEE SCC20 AI-ESTATE Meeting 99C Minutes
ARINC - Annapolis, MD

Day 1: Tuesday July 27, 1999: Convened at 8:30 AM

1 Attendees are shown in Enclosure 5.

1.0 Co-Chair Mark Kaufman called the meeting to order.

1.1 The agenda was reviewed and approved with modifications.

1.2 Chair's Report

1.2.1  John Sheppard talked about the email discussion on restructuring 1232.

1.2.2  John identified that ARINC has procured an EXPRESS tool set.  A presentation will be made tomorrow

1.3 Secretary's Report

1.3.1 Minutes from the 99-B meeting were approved without modification, as reflected in AI-ESTATE Log #293.

1.3.2 Action items were reviewed and updated, as shown in Enclosure 1.

1.4  Liaison Reports:

1.4.1 IEC Liaison WG7/TC93: John reported that the committee of action met last month and the AI-ESTATE documents were all approved for fast track.  They will go to ballot as soon as IEEE copyright release is given.

1.5 Discussion began on the restructuring of the AI-ESTATE standards.

1.5.1  Issues were identified as follows:

1.5.1.1  On the status of trial vs. full use, the subcommittee traded thoughts on existing requirements for the AI-ESTATE standard solution, and the weight of 'full use' of the standard to propel its use.

1.5.1.1.1  The subcommittee reviewed all open issues identified during the 1232.1 balloting process, to evaluate feasibility of reaffirming the trail use standard for full use.

1.5.1.1.2 R. Simpson moved that the 1232.1 be affirmed for full use.  A point was raised that, for this trial use standard, comments will be accepted for 18 months from date of publication.  The motion carried with 7 affirmative, 0 negative, and 3 abstentions.  Two actions will be taken: forwarding the recommendation to Steering for approval and writing the letter for SCC20 Chair to forward to IEEE.  John Sheppard will take the action to request approval from Steering (actions 99C-26 & 99C-27).

1.5.1.2  On the complexity and size of the document, John identified several activities which he believes can develop a usable set of services within 6 months and an approved unification standard in 18 months.

1.5.1.2.1  John identified the following action steps to reduce the size and complexity of the unified document:

1.5.1.2.2  An open issue was generated (Issue 99C-1), and it remains to be determined whether the standard will reference ISO10303 Part 21, Part 22, or allow the implementer to use either format.

1.5.1.3  As for the schedule for completion of the unified standard, actions were assigned to finish the models, identify and name services, write a binding creation strategy, and remove bindings, etc.

1.6  The group discussed the PAR for 1232, the Unified standard (AI-ESTATE Log #295).  A motion passed unanimously to accept the PAR.

1.7  The group reviewed the requirements document for IEEE 1232.  "Portability" was modified to change "implementations" to "information" in the phrase "...promote portability of implementations between conformant implementations."

1.8  The models for the unified standard were discussed next.  John presented the model, as modified from the previous meeting, written using a new application which outputs in EXPRESS.

1.8.1  Changes were made to the model, in the areas of context and how 'level' is affected.

1.9  The semantics of test and diagnostic outcome model elements was discussed.

1.10 Issue 98C-5 was addressed and the subcommittee discussed levels of service and related return codes.


Day 2: Wednesday July 28, 1999: Convened at  8:30 AM

2.0 Attendees are shown in Enclosure 5.

2.1 Review of model changes from July 27.  Added new changes to model.

2.2 Greg Bowman gave presentation on harmonization of STEP and SGML. There is an associated paper that Greg will distribute. (action 99C-10)

2.3 Modeling, John led a discussion on defining the entity "Purpose"

2.4 Reviewed 1522 "Requirements Documents".

2.4.1 Changed Prepared by "The AI-ESTATE Subcommittee" to "Diagnostic and Maintenance Control Subcommittee."

2.4.2 Motion (Randy Simpson) to approve P1522 requirements document with single change, passed unanimously.

2.4.3 Mark Kaufman will provide a 1232 PAR and a copy of P1232 and P1522 "Requirements Documents" to PCWG. (Action Item 99C-11)

2.5 Reviewed the P1522 Straw Man document.

2.5.1 It was noted that Mark is keeper of 1522 document and its "red lines."

2.5.2 Mark's P1522 Straw Man logged as item 296.

2.5.3 It ws determined that the introduction need to be rewritten. Mark Kaufman, will rewrite the Introduction to P1522.  (Action Item 99C-12)

In the following section list the assigned authors are embolden and link to an action item.

2.5.4 Continued discussion focused on clause 1, Overview

1 Overview (John Sheppard, action 99C-13)
1.1 Scope
1.2 Purpose
1.3 Conventions
2.5.5 Focused on clause 4, Description
4 Testability and Diagnosability
4.1 Background (Amanda Giarla, action 99C-14)
4.1.1 Testability (Amanda Giarla)
4.1.2 Diagnosability (Amanda Giarla)
4.1.3 Relationship to AI-ESTATE (John Sheppard, action 99C-13)
4.1.4 Product Life Cycle (Greg Bowman, action 99C-15)

4.2 Assumptions (use current draft)

4.3 Classes of Metric and Characteristics (Randy Simpson,action 99C-16)
4.3.1 Detection
4.3.2 Isolation
4.3.3 Alarms

4.4 Applications in Product Life Cycle (Greg Bowman, action 99C-15 )
4.4.1 Prediction
4.4.2 Measurement

2.5.6 John Sheppard, will set up public web site for working development of P1522 section 4 (action 99C-17).

2.5.7 It was decide that P1522 needed to be reformed and re-sent (action 99C-18).

2.5.8 Continued discussion focused on clause 5, Metrics. The supporting text for the following candidate metrics is removed. The headings will be left in for now. If proposals for the metrics are offered they will be considered otherwise they will be removed before balloting.

Candidate Metrics
Accessibility
Controllability
Observability
Reminder

In the context of P1522, the whole purpose of the information model is to provide a basis for a formal unambiguous definition of the metrics.

Methodology for development of purposeful metrics.

(1) Identify (Prediction) model elements or primitives
(Measurements) field elements or primitives


(2) Identify Area of Metrics

Detect
Isolate
Alarm
 
(3) Synthesize Metrics To answer item 2 above or section 4 of P1522, Testability and Diagnosability.
 
(4) Classify Metrics Prediction
Field Measurable
Qualitative
Primitives


Overlay: Level
Measurements

Count of maintenance actions
Maintenance cycle per item
Time a system is operational
Time from start event to end event
Diagnosis
Operational
Non-operational
Perform test
Repair Verify
Dollar Cost of
Resources (eg. people, materials)
Count of Initial Symptoms
Count of repaired/replaced items per maintenance action
Count of tests used
Count of total tests


Overlay: Level
Prediction

Count of total tests
Count of diagnoses
Etc for each entity
Time cost of entities
Non-time costs of entities
Hugh Pritchett will brainstorm on the metric primitives listed in minute's item 2.5.8 (action 99C-19).

2.6 John gave a synopsis of the D&MC (99B) visit to "RMS Partnership" meeting and other discussions.

2.6.1 Web issues were discussed at this time. It was suggested that John put the RMS Partnership URL on DMC web site (action 99C-20). It was also suggested that Greg create a new banner for the DMC web page (action 99C-21).

2.7 Modeling Issues

2.7.1 John led a discussion regarding the model entity "Session."
 


Day 3: Thursday, April 29, 1999 convened at  9 AM

3.0 Attendees for this day are shown in Enclosure 5.

3.1 Over the evening break John produced (using EDM Visual EXPRESS) a well formed and annotated document of the latest models.  John reviewed model changes from day 2 along with a new "Diagnostic Inference Model."  The documents will be entered as logged items, (action 99C-28). 

3.2 Randy raised the issue of the section 4 outline. Section 4.3 was amended as follows.

4.3 Classes of Metric and Characteristics, (Randy Simpson)
4.3.1 Detection
4.3.2 Isolation
4.3.3 Alarms
4.3.3 Errors in Diagnosis
3.3 Discussion focused on issues of "Recommended Practices." The question was raised is there adequate committee time and resources to pursue the development of a recommended practices. The committee decided not to pursue the issue at this time.

3.4 Discussion focused on "Higher Order Services" (Diagnostic) with an open discussion on candidate services.

3.4.1 Definition of Higher Order Services: Services that can be done by a set of lower order services and some computation. The accessor services are the lowest order services.

3.4.2 Resulting candidate list.

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

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

EXPLAIN SERVICES:
Show Inference Trace
Show Session Trace

INFERENCE SERVICES:
Process Test Outcome
Process Test Batch
get_most_likely_diagnoses - Count or likelihood

BOTTOM DWELLERS:
Explain - Choice of Test
Explain Hypothesis
Learn
update_test_cost_time
update_test_cost_currency
update_resource_cost_time
update_resource_cost_currency
update_action_cost_time
update_action_cost_currency

3.4.3 Amanda Giarla asked the question is there a need to standardize services the Diagnostic Reasoner might require. The committee stated that such services are outside the scope of the standard.

3.4.4 It was noted that higher order services were an item of discussion in the past.  Greg Bowman will provide descriptions of the candidate higher order services based on previous documentation (action 99C-22).

3.5 It was noted parenthetically that at the 99C meeting Greg Bowman is the outgoing secretary of DMC and that Amanda Jane Giarla is the incoming secretary of DMC as of meeting 99C.

3.6 Operations Manual

3.6.1 John led a discussion focused on reviewing and making changes to the Operations Manual. Randy moved to approve as modified, unanimous approval. John Sheppard will make the agreed upon changes to the Operations Manual (action 99C-23).

3.7 The list of Action Items were reviewed.

3.8 Log Items were reviewed

3.9 Mark Kaufman set the next agenda

3.9.1 Discussion focused on Time and Place of next meeting. The committee discussed their concern over the time and costs of attending the full length of the SCC20 meetings.  Mark Kaufman will be sending a letter of concern to the SCC20 regarding the costs and time (action 99C-25)


Enclosure 1 Action Item Summary

Action Item 98C-10: Greg Bowman to arrange for AI-ESTATE members to be added to the STEP/SGML NIST exploder.
Status: CLOSED

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.

Action Item 98C-15: Tim Wilmering will contact Charles Amaral about obtaining a copy of AP-208 (Life Cycle Mgmt for Process Plants).
Status: CLOSED see action item 99C-24.

Action Item 99A-1: A. Giarla has an action to explore the status and future of IEC liaison by determining the pros and cons of possible options.
Status: CLOSED

Action Item 99A-6: Randy Simpson to send the AUTOTESTCON reference (Keiner 1980) for the testability definition to Mark Kaufman.
Status: CLOSED

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

Action Item 99A-11:  Greg accepted an action to explore the possibility of creating a demonstration of AI-ESTATE as part of V-22 RTCASS transportability, to test capability to provide partial/reconfigurable TPS test functionality.
Status: ONGOING.  Proposal for implementation is the next step.

Action Item 99A-12: Bill Rodriguez will explore the USMC position on AI-ESTATE capability in NxTest.
Status: CLOSED  The USMC currently is committed to NxTest and AI-ESTATE

Action Item 99A-13: Tim Bearse will explore role of AI-ESTATE in TDC initiatives.
Status: CLOSED.  TDC is now soliciting membership.  Mark Kaufman accepted position as liaison to TDC.

Action Item 99B-1: Amanda Giarla will provide the AI-ESTATE Secretary with an electronic copy of Log Item #288.
Status: CLOSED.

Action Item 99B-2:  John will flesh out the STRIPS proposal, integrating it into the draft Unified CEM.
Status: CLOSED.

Action Item 99B-3: Mark Kaufman has an action to send the latest draft of 1522 to the AI-ESTATE members only reflector (keep it under 1MB).
Status: CLOSED. No changes to document.

Action Item 99B-4: Tim Bearse determine who has custody of 2165 Mil Handbook and explore interest in modifying and releasing its programmatic content as a Recommended Practice.
Status: CLOSED. NAWC Lakehurst prepared the mil handbook, which is approved and has unlimited release.

Action Item 99B-5: Jack Taylor to determine who has custody of DEF Standard 0013 and explore interest in modifying and releasing its programmatic content as an IEEE DMC Recommended Practice.
Status: CLOSED OBE

Action Item 99B-6: John Sheppard accepted an action to incorporate redlines from the 99-B minutes into the Requirements document for 1522.
Status: CLOSED.

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 99B-9: Greg Bowman will ensure members only reflector list is current.
Status: CLOSED.  This action is considered a regular duty of the Secretary.

Action Item 99B-10: John Sheppard accepted action to revise the PAR and Requirements document for the Diagnostic and Maintenance Control Information Base (D&MCIB) Requirements document.  This will be presented at the 99C meeting for subcommittee approval.
Status: CLOSED.

Action Item 99B-11: John or Mark will initiate discussions for open issues #98C-5and #99B-1.
Status: CLOSED.

 New Action Items

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.
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: OPEN

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

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

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

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

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

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


Enclosure 2 Recent Log Items

#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.
 


Enclosure 3 Open Issues

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.

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: OPEN -Low Priority(High priority for 99-D meeting)

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: OPEN - Low Priority (High priority for 99-D meeting)

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

99B-1: The current definition of test_outcome, and the new definition of diagnostic_outcome have weak semantics. This means it is difficult to determine whether a fault is actually detected by examining the outcomes since we can no longer tell which correspond to "pass" or "good" in all cases. We may need to address this in the update to the model.
Status: CLOSED.

New Issues

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: OPEN -  Unassigned priority
 


Enclosure 4
AI-ESTATE 99-C Meeting Agenda
 ARINC  Annapolis, MD

I. Call To Order

II. Approval of Agenda

III. Reports
        A. Chair
        B. Secretary
        C. Liaison

IV. 15 Minute Presentations
        A. TeRM (Lee Shombert)
        B. STEP/SGML Harmonization (Greg Bowman)

V. P1232 Unification Issues
        A.  1232 Restructure/Reaffirmation
        B. Approval of PAR/Requirements Document
        C. Proposals
            i. STRIPS Model
            ii. Semantics for test and diagnostic outcome
        D. Model Review
        E. Open Issues

VI. P1522 Testability/Diagnosibility
        A. Approval of Requirements Document
        B. Results of Draft Review
        C. Proposals
            i. False Alarm Metric
            ii. Multi-Outcome Metrics
            iii. FFI/FIR Metrics
        D. Model Issues
        E. Author Assignment and Schedule
        F. Recommended Practice
            i. DEF Std 0013
            ii. Mil Hdbk 2165

VII. DMC Subcommittee Operations Manual Review

VIII. New Action Items Review

IX. Set Time and Location for 99-D

X. Set Agenda for 99-D

XI. Adjourn


Enclosure 5
AI-ESTATE 99-C Meeting Attendees List

Name / Affiliation
Voice Phone (V) / Fax (F) / Email
T
W
Th
Greg Bowman 
The Boeing Company 
P.O. Box 16858 M/C P23-34 
Philadelphia, PA 19142-0858 
V(610) 591-6684 
F(610) 591-9850 
gregory.p.bowman@boeing.com
X
X
X
 Bill Rodriguez 
Marine Corps Logistics Bases 
814 Radford Blvd. 
Albany, GA  31704-1128
V(912) 439-6307 
F(912) 439-6172 
rodriguezwc@matcom.usmc.mil
X
X
 
Larry Carpenter ARINC 
2551 Riva Rd. Annapolis, MD 21401
 
X
   
Tony Bartolini 
V(510) 887-3387 
F(510) 783-9438 
anthonyb@etec.com
X
X
 X
Hugh Pritchett

 
V(912) 988-2626 
F(912) 988-2626 
prhugh@cstel.net
X
X
 X
Les Orlidge 
Allied Signal 
Teterboro, NJ  07608-1173
 V (201) 393-3849 
F (201) 393-6804 
X
   
Timothy Bearse, 
Naval Undersea Warfare Center 
Code 8313, Bldg 112/16 
1176 Howell Street 
 Newport, RI 02841-1708
V(401) 832-8982 
F(401) 832-7878 
bearsetm@code831.npt.nuwc.navy.mil
X
X
 X
Amanda Jane Giarla 
Hamilton Software, Inc 
2270 North Point Parkway 
Santa Rosa, CA 95407
V (707) 542-2700 x157 
F (707) 542-3443 
amanda@hamsoft.com
X
X
 X
John Sheppard 
ARINC 
2551 Riva Rd. 
Annapolis, MD 21401 
V(410) 266-2099 
F(410) 573-3170 
jsheppar@arinc.com
X
X
 X
Tim Wilmering 
The Boeing Company 
PO Box 516, M/C S034-1240 
St. Louis, MO 63166-0516 
V(314) 234-6781 
F(314) 232-2242 
timothy.j.wilmering@boeing.com
X
X
 X
          Mark Kaufman 
  NWAS 
PO Box 5000 
Corona, CA 91718-5000
V(909) 273-5725 
F(909) 273-4599 
kaufman.mark@corona.navy.mil
X
X
 X
William R. Simpson 
IDA 
1801 N. Beauregard St. 
Alexandria, VA 22311-1772 
V(703) 845-6637 
F(703) 845-6788 
rsimpson@ida.org
X
X
X
Kjell Bengtsson 
EPM Technology
V 47-23171717 
F 47-23171700 
kjell.bengtsson@epmtech.jotne.com
 
X
 
Roger Goldberg ARINC 
2551 Riva Rd. Annapolis, MD 21401
 
X
   


Enclosure 6
AI-ESTATE 99-D Meeting Agenda
 Oct 12-14, Piscataway, NJ

I. Call To Order

II. Approval of Agenda

III.Reports

A. Chair
B. Secretary
C. Liaison
IV. 15 Minute Presentations
A. Web Based Diagnostics (Qualtech)
V. P1232 Unification Issues
A. High Order Services
B. Draft Review
C. Proposals
D. Model Review
E. Open Issues
VI. P1522 Testability/Diagnosability
A. Draft Review
B. Proposals
C. Model Issues
D. Open Issues
E. Metrics Issues
VII. New Action Item Review

VIII. Time and Location of 00-A

IX. Set Agenda for 00-A

X. Adjourn