SCC20 TII WG Meeting Minutes
Feb 2011
Orlando
Participants
Skip Yarnall
Steve Sharp
Larry Hill
Dexter Kennedy
Ron Taylor
Steve Wagener
Kent Shoemaker
Larry Adams
David Sharone
Ion Neag
Anand Jain
Teresa Lopes
Chris Gorringe
George Gathers
Mike Rutridge
Chuck Renolds
Hugh Pritchard
J Schmalenberger
Dave Droste
Dave Ptacek
Tuesday 8th Feb 2011
09:00-09:20 Short Plenary (All)
The meeting was called to order at 09:00. The IEEE Patent slides, entitled “pat-sideset.ppt” and dated “25 March 2008” where presented to the meeting by the acting chairman Chris Gorringe
09:30 – 15:00 TII & HI Joint Discussion
P1505.1.1
The team leader was unable to make the meeting due to adverse weather and had requested that the meeting postpone any discussion until the next face to face meeting in April; the meeting agreed.
Intrinsic Path Characteristics WG report
1671.5(Test adapter)/.6(Test Station) to support "Intrinsic Path Characteristics"
Discussed where to hold info. See IntrinsicPathCharacteristics_2-8-11.docx. Also brought up weather this would be part of existing ATML ‘dot’ schemas or a new ".7" and COMMON.
Chris insisted that we create a large set of "Use Cases". Could be draft XML or "built up by hand". Hugh Pritchett brought up that this info hasn’t existed or been available. This has created a problem with TPSs working correctly. Therefore, we have no history to create use cases. Chris & Ron would create a prototype ATML schema that covered the topics identified in the Intrinsic Path Characteristics document items so show how such information would fit with the ATML framework
AI#1 - Formally make report output of working group.
AI#2 - Start an implementation.
AI#3 - Where are the use cases that come in. Does this satisfy users?
Actions by April 11th, the week of the next SCC20 meeting in Piscataway, NJ.
Wednesday 9th Feb 2011
The Agenda for the day was
09:00 1671.1 Test Description Anand Jain
10:00ish ATML Results Next door
13:00-17:00 ‘’dot’ Standard Issues
· 1671.1 Test Description Anand Jain
· 1671.2 Instrument Description Chris Gorringe
· 1671.3 UUT Description Ion Neag
· 1671.4 Test Configuration Mike Seavey
· 1671.5,6 Test Adapter & Test Station Ron Taylor
The current ATML Issues document ATMLDemo2010Rev6.xls was reviewed and updated to revision 7
· #2 - TestDescription Differences - Change 1671.1 examples and schemas to reference 1641-2010 schemas
· #4 - Use of hc:Path in Test Adaptor - "Reconsider as part of Test Adaptor review Use IntrinsicPath Characteristics to show how this would be used"
· #5 - Use of Test results Indictments - The Demo used this claification, to both generate test results with Indictments and read test results with failures and add indictments based on the Test Description diagnostic path Send email to Tony Aldwart of details
· #6 - Use of namespace prefix - Update ATML 1671 Examples to use prefered namespace prefixes
· #7 - Use of namespace prefix in hc:Path - Update ATML 1671 Examples to use prefered namespace prefixes
· #11 - Test Description Interface Requirements - Create action to clarify Test Description to include this as part of standard
· #12 - Use of xsi:type uut:HardwareUUT - Add uut:Component to cover the R4 resistor as hardware Item
· #14 - Sub component connectors - brilliant idea, just as it should be probaly need to write words to indicate that it proper to refer to an internal component via its component and ports and not required to create an arbitary connector examples would be use of Instruments iand resources in other ATML documents
· #15 - Storing ATS Signals in ATML - as part of new PARS do we want to make this more explicit We need to distiquish 'files' from exchange format; A good solution if for a system to create an AllocatedCapabilities file whose contents uses the TestAdaptor exchange format to described the allocated ATML capabilities
· #19 - Capture wirelength etc - Part of Intrinsic Path Characteristics
· #20 - Ambiguity Groups - Add extra attribute to outcome that allows us to match test outcomes to failures ambiguity
· #21 - Mapping Tests results to test Description (instance to Description) - cross reference to tests has been added to test results
· #23 - Describing Shielded paths - Part of Intrinsic Path Characteristics
· #26 - How to indict a component e.g. R4 - Fault and failur ID to be added toTest Results
· #31 - Where a element requires both ID and name can they be the same, in which case why force both - Need to review each example in the 'dot' standards on a case by case status
· #32 - How to relate UUT Errors with TD Failures and Faults - 1) Add TD's Faults and Faulures klist in UUT description and then 'refrence' these from TD rather than duplicate them 2) HardwareItemDescription/Errors and UUtDescription Status (bit codes) need tp be explained. A distiction is that errors refer to 'messages' returned when the hardware is working e.g. Instrument error messages, where as UUT Status are bit codes for test & diagnosis
· #35 - UUT Description and Test Description have different UUT documents - move into UUT description
· #36 Power requirement specification do not match – Use common approach across documents
· #37 - Failures, Faults and Errors - copy to UUT description and reference in Test Description
· #38 - Outcome qualifiers - need to review how to map outcomes (at the test /Action level) to the comparison or limit that creates that outcome how does an executive know which outcome comes from what measured value, i.e. which limit failed
· #39 - How to Passing Test Results up the call chain - Provide example to Anand
ATML ‘dot’ schedule
The following schedule was confirmed
/ .2, .3, .4 / .1, .5, .6 /Collect Comments from ATML Demo 3weeeks / 10/14/2010 / 10/14/2010
Create issues list from comments for each ‘dot’ standard / 12/2010 / 12/2010
Get Master documents for IEEE into new IEEE Template / 1/14/2011 / 1/14/2011
All input received user inputs / 1/14/2011 / 1/14/2011
Review confirm all issues – plus suggested solution / 1/14/2011 / 1/14/2011
Final task group input (confirm time scales with task group) / 1/16/2011 / 1/16/2011
Initial Update schemas to include comments / 4/2011
5/2011(3) / 9/2011
Update support files to match schemas / 7/2011 / 4/2012
Draft Documents need to be updated to current Schema (depends on Altova) / 9/2011 / 9/2012
Thursday
TII Website (User Guide)
· WebSite review
1. User Information
2. ATML Demos
· History
At present we have access to …
a) IEEE TII WebSite / ATML Website and ATML Demonstration all housed on the IEEE area
b) Groove (3.1 to Office 2010)
c) Box.Net (http://www.box.net) (http://www.box.net/files#/files/0/f/44406548/ATML_Demo_2010)
d) ATML Wiki Entry (http://en.wikipedia.org/wiki/ATML)
e) MSN Groups, “ATML Focus Group”
f) Google Groups
a. http://groups.google.com/group/atml-forum
b. http://groups.google.com/group/atml-FocusWG
g) Google Sites
a. https://sites.google.com/site/atmlguide/
b. https://sites.google.com/site/atmlfocusgroup/
h) Google Docs
i) ListServer (email threads and topics) (http://grouper.ieee.org/groups/scc20/tii/email/thread.html)
j) Hosted Discussion Forum
Some of these are really viable alternatives e.g. the ATML Wiki entry is something we have and will need to monitor, but any registered Wiki user can edit the page so its more for us to ‘plug’ ATML.
Our requirements are quite varied
a) we need some parts to be ‘Open Access’ anyone can read them, any known/registered user can post
b) Some are members only with login controlled/invited by us
c) Generally unrestricted access (i.e. not blocked by company or IT filters)
Attached is a spread sheet matrix with various ‘requirements’ features.
To be honest I’d be happy with Groove for development stuff and IEEE Website and TII Listserver as place for casual users to read and post questions. Failing that Google Suite is probably my next favourite.
Outcome
1) Transfer Google site content to TII website
2) Reference the IEEE download as the primary schema location
3) Request permission from IEEE to publish ATML papers (from ATC)
4) user guide may require forum, wait and see
5) Anand to see if we can reuse their content
6) Easier to find links to actual standard support a one job page for both schema download and standard purchase
7) need to take content already dispersed and update TII we as User orientated loosing development stuff
8) Update Wiki
9) Remove WiP schemas to private area
TII & TAD Management
WG ATML User Guide PAR initial preparation (for April’s meeting)
PAR details where written and approved by the WG to be submitted to SCC20 Admin and then steering see PAR1671_1.doc
Roster membership
TII roster membership was reviewed
2010/2011 TII Report
The TII yearly IEEE Report was revised and updated wee TII Report2011.doc