IVI 2010 June Meeting Summary Final · Web viewPatent Call Please be aware that this meeting is...

IVI Foundation

Meeting SummariesFeb. 7 - 9, 2011

Boston, MA

Table of ContentsCHAPTER 1 MEETING ATTENDEES....................................................................................................................2

CHAPTER 2 IVI DATA CONVERSION WORKING GROUP – MEETING MINUTES..................................3

CHAPTER 3 VISA WORKING GROUP..................................................................................................................9

CHAPTER 4 IVI MARKETING COMMITTEE MEETING MINUTES IVI GSG VIDEO WORKING MEETING...................................................................................................................................................................14

CHAPTER 5 IVI MARKETING COMMITTEE MEETING MINUTES............................................................23

CHAPTER 6 TECHNICAL COMMITTEE............................................................................................................31

CHAPTER 7 IVI BOD MEETING FEB 9, 2011.....................................................................................................41

CHAPTER 8 ANNUAL MEMBERSHIP MEETING.............................................................................................47

IVI Foundation Meeting Minutes Oct. 2010

Chapter 1 Meeting Attendees

Name Company Email

Arun Veeramani National Instruments [email protected]

Bob Helsel IVI Foundation [email protected]

David Rohacek National Instruments [email protected]

Don Essner DRS-SSI [email protected]

Evan Cone National Instruments [email protected]

Howard Haugstad Rockwell Automation [email protected]

Jason Schares Rockwell Collins [email protected]

Jochen Wolle Rohde & Schwarz [email protected]

Joe Mueller Agilent Technologies [email protected]

Johannes Ganzert Rohde & Schwarz [email protected]

John Harvey Agilent Technologies [email protected]

John Ryland Keithley Instruments [email protected]

Jon Bellin National Instruments [email protected]

Kirk Fertitta Pacific Mindworks [email protected]

Rob Purser The Mathworks [email protected]

Santanu Pradhan Tektronix [email protected]

Scott Rust National Instruments [email protected]

Tom Fay Agilent Technologies [email protected]

Tom Sarfi VTI Technologies [email protected]

Yves Maumary Agilent Technologies [email protected]


`

Chapter 2 IVI Data Conversion Working Group – Meeting Minutes

General Meeting Info:Date of Meeting: February 8th, 2011

Location: LasVegas

Chairperson: Yves Maumary

Minutes Prepared By: Yves Maumary

Meeting Attendees:Name Company Phone Email

Yves Maumary Agilent Technologies +41 22 884 3221 [email protected]

Evan Cone National Instruments [email protected]

Vesna Jadric National Instruments [email protected]


Patent CallPlease be aware that this meeting is being held under the Intellectual Property Rights policy adopted by IVI Foundation. If you do not have a copy of this policy, please see me during this meeting. You may also view and download a copy of that policy at the Membership IVI Legal Documents section of the Consortium website.

At this time, I would ask that anyone in attendance inform me if they are personally aware of any claims under any patent applications or issued patents that would be likely to be infringed by an implementation of the specification or other work product which is the subject of this meeting. You


mailto:[email protected]




need not be the inventor of such patent or patent application in order to inform us of its existence, nor will you be held responsible for expressing a belief that turns out to be inaccurate.

Nothing new.

Last Meeting MinutesThe minutes from the previous meeting (January 19th) are approved – thanks Evan.

Topics To Be Discussed1. Approve last meeting minutes2. Review action items3. Review IviFgen rev. 5.0 draft specification:

a. Editorial corrections from the feedback since last draft distributionb. Corrections to the Marker extensions (static rep caps)c. Review of Appendicesd. Addition of State Diagram for triggers

4. Break5. Discuss schedule and plan: final draft, submission of final draft for 45 days review period inside

IVI, voting.

Review Action Items from Previous Meeting

Note: all the resolved Action Items until the Boston meeting in October 2010 were cleared. Please refer to the previous minutes if needed.

Owner Action Item Status

Yves What happens when the user loads wf of different sizes onto the different channels? Error? Or truncate to shorter size? (Evan’s comment from Oct 18th)

(22/12/10) On the Agilent Arb, this is permitted by the driver but strongly discouraged because produces unpredictable output (?!)Given the proposal of single call for all channels, require explicitly same length in the text. Also, for C/COM, waveforms are end-to-end, not (data-) interleaved.

Evan Was the intention of channel specific trigger in the original spec to allow multiple timebases in a single instrument? (i.e. channels generating ‘asynchronously’)

(22/12/10) Consensus that it was a mistake in the first place for the trigger interface. 2 possibilities: keep it as for the original trigger interface,



or remove the channel parameter in the new extensions.Decision: keep the channel parameter.

Yves Editorial changes (from Evan’s email 22/10/2010) should be applied to draft after .NET review completed:# Value definitions for new attributes (IVI_CLASS_PUBLIC_ATTR_BASE + ??)# Allowed values of attributes# Allowed values of function parameters# Section 24.3.1 Add Data Marker, the description of parameter: BitPosition need to be revised. "... The driver uses this value to set the Source Channel attribute. Refer to the attribute ..." It should be Bit Position attribute

(22/12/10) John Harvey currently owns the draft wait until .NET review completed.

(29/1/11) Done by Yves.

Yves Editorial change: Trigger Source (str) in Attr Values: “LAN6” has a blank.Sample Clock Source C values have wrong font.Sample Clock Source missing from C Attr ID definition list.

(22/12/10) John Harvey currently owns the draft wait until .NET review completed.


Yves Question from IVI.NET WG: Sparse Marker Waveform Handle, how to deal with the different types of the Waveform objects?

(22/12/10) The WG believes we should keep using handles for the waveforms, so this will no longer be an issue.

Yves Correction: trigger source property/attribute applies to Channel (not N/A).


Yves New attribute of type int64 MAX_WAVEFORM_SIZE_64 (needs to be brought to TC).

(07/2/11) Following discussion with Kirk and Jon, decided to have a new extension group IviFgenArbWfmSize64, with 2 new attributes, wfm size min64 and max64, and the corresponding query QueryArbWfmCapabilities with the 4 params (maxNumWfms, wfmQuantum, min64 and max64).

It is also agreed that this no longer needs to be brought to the TC.

Yves Multi-channel waveform creation: single call for the multiple channels. For .NET, use an array of

(30/1/11) Done by Yves. For .NET, the waveforms should be



Waveform objects. Require all waveforms to be of same length.

concatenated into a single Waveform object, similarly to IVI-C and IVI-COM.

Yves Terminal Configuration attribute: add a channelName parameter to the .NET Set/Get methods and the COM property, and make the attribute apply to Channel.


Yves Keep using waveform/sequence handles in .NET. (30/1/11) Done by Yves.

Yves For the Create Channel Arbitrary Waveform function, in the case of multi-channel waveforms the user must pass concatenated waveforms for C and COM. What is the proper .NET type? Should we introduce IWaveformCollection<type> objects? Or simply concatenate the waveforms like for C/COM?

(8/2/11) Agree to keep same method parameter type as for single waveform creation.

Yves Add new read-only attribute Sample Bit Resolution in IviFgenArbWfmBinary extension group to be able to query how many bits are significant. Together with the binary alignment, this will allow the user to know the range and resolution of the integers in the waveform.


Yves & Evan Find/create a state diagram to explain the triggers behavior.

(8/2/11) Evan did not find such a diagram.Not sure we want to further delay this specification, textual descriptions seem sufficient.

Yves Implement comments from Jan 19th in spec by January 31st.

(8/2/11) Done.

Record of Discussions:

Report from the IVI.NET meeting in Las Vegas about the IviFgen specification We do not want to modify the existing extension groups to avoid breaking the compliance of

existing drivers. However, given the number of modifications to the specification, we shall not hesitate to rev the (COM) interfaces.

Note that the default interface of an IVI-COM driver will be IviFgen (for backward compatibility with existing applications). The user will need to explicitly cast to IviFgen2.

CreateChannelWaveform has the waveform size set via an Int64. We need a 64-bit version of that attribute. We will therefore add 2 new attributes: WaveformSizeMax64 and WaveformSizeMin64 (in C: MAX_WAVEFORM_SIZE64 and MIN_WAVEFORM_SIZE64).


Because they are used either by the CreateChannelWaveform function or its binary versions, these new attributes should not be placed into either of those new extensions groups. They are best placed in their own new extension group IviFgenArbWfmSize64This new extension group shall also include the (IVI-C only) corresponding query function.For .NET, we shall use the attributes from the IviFgenArbWfm extension group (the ‘original’ extension group).

The specification draft will be ready by end-of-day Tuesday 8th.

Review IviFgen rev. 5.0 draft specificationReview and edits following feedback from Evan:

Copy/paste error on page 252. The added "COM Prototype" should be ".NET prototype" done. SparseMarker Configure function, the parameters that are .NET specific say (.NET) after them,

but we don't do that for the parameters in the DataMarker Configure function. not applicable anymore.

In the .NET Hierarchy, why are some properties just presented as properties (like OutputMode) and others written as Set & Get (like OperationMode)? Because parametrized properties (e.g. channel specific) are not supported by .NET.

As per the discussion on Dec 8, 2010, I thought we were modifying the data markers and sparse markers to be pre-populated. I believe that means changing the name of the Add functions to Configure. Remove/RemoveAll may also need to be renamed to clear or reset or something. done. Remove was removed(!), and RemoveAll replaced by Clear (.NET) or DisableAll (C/COM).

Other comments:

Given that .NET will not include the CreateWaveform method without the channel parameter, the question is asked whether we need to explicitly specify that this method can also be used for single channel arbs, and/or allow an empty string for the channel parameter. No, other specifications do not support empty strings for the channel parameter.

Marker extensions: the marker extensions were edited to replace ‘Add’ by ‘Configure’. Given that Configure would do an implicit enable, we discussed whether we should add an ‘Enabled’ attribute. After some checks with other specifications, it appears that the destination attribute can be specified as None, which is equivalent to a disable. The destination attribute will serve as the ‘Enabled’ attribute (None = disabled). We decide also to keep a function DisableAll to set all destination attributes to None.

Indices vs indexes: for simplicity and consistency, it is decided to use indexes everywhere (seems to be the more “modern” spelling).

Review of Appendices:

All sections of the appendices seem to remain valid and not require modifications.

Schedule:

NI wants to do another iteration of prototyping. Given that it will be an iteration of an existing prototype, 2 IVI Foundation Meeting Minutes Oct. 2010

to 4 weeks should be enough.

Currently there are no plans for IVI-COM and IVI.NET prototypes. This will be brought up at the TC.

Action Items Created:


Evan Check chapters 29, 30, 31.

Next MeetingThe next meeting is scheduled for February 16, 4:30 pm (Central European Time). Yves will send out a reminder message at the beginning of that week.


Chapter 3 VISA Working Group

General Meeting Info:Date of Meeting: February 7, 2011

Location: Las Vegas, NV

Chairperson: Dan Mondrik

Minutes Prepared By: Jim Piotrowski

Meeting Attendees:

Name Company Email

Dan Mondrik National Instruments [email protected]

Jim Piotrowski National Instruments [email protected]

John Harvey Agilent Technologies [email protected]

John Ryland Keithley [email protected]

Vinod Cherian The Mathworks [email protected]

Joe Mueller Agilent Technologies [email protected]

Bob Helsel Bode Enterprises [email protected] Foundation Meeting Minutes Oct. 2010


Jason Schares Rockwell Collins

Topics to be discussed:

VXI 4.0 extensions, see attached document from Tom Sarfi (VPP 4.3, 4.3.2)

PXI extensions for inclusion of BACKPLANE resource; 64-bit BAR info for INSTR (VPP 4.3, 4.3.2)

PXI multi-vendor interoperability initiative; discuss user-kernel API or some other approach (new specification)

Opportunity to request other VISA spec extensions

Create draft to send to Technical Committee meeting to officially open and/or create the necessary specs

Decide on timing and frequency of conference calls to make forward progress

All of the discussion topics were accompanied by slides. The slides are posted here.

VXI 4.0 extensions, see attached document from Tom Sarfi

The document from Tom is posted here.

Joe: Are future VISA implementations compliant w/o new VXI extension support?

Dan: VISA spec is generally quiet about support requirements, especially for hardware specific things

Vinod: Is there a way to query a device for latest version supported?


http://www.ivifoundation.org/membership/committees/VISA/Documents/Software%20Requirements%20for%20VXI-1%204.0%20V3.doc

http://www.ivifoundation.org/membership/committees/VISA/Documents/VISA_working_group_Feb_2011.pptx

Dan: There should be an attribute to get what hardware spec is a given device is compliant with (i.e. we should add that attribute)

Explanation of new VXI star triggers (triggers are present in new P3 slots only)

Joe mentioned that i2c is used for system health for AXIe, but not used for instrument communication during discussion of i2c VXI support.

Sangram might be a good contact from VTI for VXI extension functionality and purpose.

Contact info from Bob later.

John Harvey: Could raw Get/Set attribute in COM be used to support new attribute to avoid new interface.

Question of what getAttribute returns...answer is a VARIANTARG

Send slides to Bob.

Also, will need VTI to implement the interface since nobody else will...

John H: Can we create an enumeration so that attribute IDs are present in type library

PXI extensions for inclusion of BACKPLANE resource; 64-bit BAR info for INSTR

ViAssertTrigger doesn't actually assert, just assumes that triggering happens between RESERVE and UNRESERVE

Joe: What happens if I call viAssertTrigger to reserve a line? Does the behavior change if it's already been mapped?


Dan: Depends on mapping order and whether the call was on the source or the destination

Joe: PXI stuff in parallel with .NET effort?

Dan: Should define it in C before .NET; NI documentation is scattered/non-existent

Joe: Would like it in .NET if possible

Joe: INSTR and backplane assert trigger differences?

Dan: Implementations exactly the same for NI. Explained that it existed on both just to satisfy different use cases.

Joe: Want to ensure that both will call same new underlying component

Dan: .Net will probably have 64-bit attributes for BARs

General consensus on PXI INSTR spec additions.

PXI multi-vendor interoperability initiative; discuss user-kernel API or some other approach (new specification)

Agreement from Agilent (Joe) about common user/kernel interface approach, only worry is some exotic need for the device to have a special interface

Dan: Could use IOCtls for that, define standard "vendor-reserved" IOCtl range

John H: IRegister64 has the interface issue. MoveIn<byte size>Ex and MoveOut<byte size>Ex

Would require with a new GUID due to interface change

Opportunity to request other VISA spec extensions


Jochen: Are any spec additions necessary for IPv6 support? Do we want to require IPv6 support to comply with a specific VISA version?

Dan: INSTR should be supported in the specs after HiSLIP support changes. SOCKET may require spec updates. VISA specification has historically been relatively lenient regarding requiring protocol support to be compliant.

Motion to refer to Technical Committee:

The VISA working group moves that the IVI Foundation VISA Working group update VPP 4.3, VPP 4.3.2, and VPP 4.3.4, and create a new IVI 6.3 specification, to extend the VISA definition to include:o Extensions to control VXI-1 4.0 compliant controllers. Specifically the ability to:o Support new address modifiers for 2eVME/2eSSTo Control the additional star trigger lineso Assert new SYNC100 utility bus signalo Extensions to control PXI devices including:o A PXI BACKPLANE resource class for mapping/unmapping triggers and reserving triggerso Support 64-bit base address registerso A common user-kernel driver interface for PXI

Conference Call Schedule and Other Action Items: VISA will take over the HiSLIP 9:00-10:00 AM CST time slot starting Thursday, March 3

o Dan will work on getting the phone conferencing set up Other Action Items

o Bob: Email Dan with Sangram’s contact infoo Dan: Post slides presented at meetingo Jochen: Investigate VISA TCPIP Socket implementation for IPv6 compatibility issueso John Harvey: Provide NI with fixed VISA COM interface


Chapter 4 IVI Marketing Committee Meeting MinutesIVI GSG VIDEO WORKING MEETINGGeneral Meeting Info:

Date of Meeting: February 8, 2011


Chairperson: Jared Aho

Minutes Prepared By: Jared Aho

Meeting Attendees:Name Company Attended

Jared Aho National Instruments Y

Kirk Fertitta Pacific MindWorks N


Bob Helsel IVI Foundation Y

Jochen Wolle Rohde & Schwarz Y

Rob Purser The Mathworks N

Mike Wadzita Tektronix Y

Joe Mueller Agilent Y

Jason Schares Rockwell Collins Y

Eric Wetjen The MathWorks N

Vesna Jadric National Instruments Y

Deoborah Homan Agilent N


Discussion Topics:

This is a working marketing committee meeting to focus solely on the IVI GSG Videos (aka Camtasia Videos). The current open and due action items of the marketing committee are not accurately reflected in these notes. Refer to the IVI Marketing Committee Meeting Notes from February 9, 2011 for a comprehensive update on marketing committee activities.

Owner Action Item Deadline Status

Camtasia Video Owners

Get raw footage ready for editing and production Feb 7 2011 Open


Record of Discussions:

NI shared the first draft of the Getting Started with IVI for LabVIEW and Getting Started with IVI for LabWindows/CVI videos.

Notes from the LabVIEW and LabWindows/CVI video review

Bob – consistent theme across videos should be “easy”

o Website – actually show the user where to go for this tutorial, even go as far as opening the GSG for this environment

o Written script of what they’re saying so the user can follow along

Does Camtasia have way to include script along with audio/video?

o Present an outline of steps up-front to help the user follow along; and summarize at the end

A way to help with the flow is to keep the outline within view and reference back to it; could this be done in post-processing?

o Good use of example at the end, and to relay about extensibility of these drivers

o Need to make sure that the hosting on the website is solid, don’t want users to have bad experience trying to access/watch videos.

o Possibly host an example along with the GSG pdf and video

Consider changing the resource page to create a hosting page for each of the development environments

o Slow and steady pace

Jochen – each video should point out the simulation feature of IVI

o For this example, we’re going to use a simulated instrument. Simulated instruments is a built-in feature of all IVI drivers, <benefit statement>


o Who is the target audience? Are they familiar with the ADEs?

We expect them to be familiar with the ADEs, but not necessarily how to use IVI within the ADE

As an example, showing how to get to the LabVIEW Context Help portion could be cut.

o Set expectations that it’s more than just a driver being installed (i.e. shared components). Use consistent terminology as GSG guide

Jason – should we call out config store

o Might not be relevant enough for “getting started” content

o Microsoft video examples reference what version of the software they’re using. It’s good information to detail up front to set user expectations

Joe – the beginning of the video showed how to get the driver; the LV and CVI examples showed how to actually get the drivers

o When we went down this path for the written guides, we decided not to because it was too varied. We intentionally cut it out of the written guides to keep things generic and independent

o Vesna – GSG guides do have a generic section which refers to accessing the driver; this could be a part of the opening instead of a part of the individual videos

o The videos seemed to focus more on the environments than it did the function calls themselves. We should flip this. Focus more on the driver and the calls than the environment.

Jared – use the printed GSG as a guide. If it’s not included in the GSG guide, vendor should bring this up during the marketing calls so member committees can discuss

Jochen – can save some time by having the pre-build example loaded in the background


Bob – finding the balance between just showing how to do it and including the benefits of the technology to the user

o Include some framing statements up front or throughout that touch on benefits; could include in the beginning

Mike – what is critical knowledge for someone getting started

o The installation process is very important

o Talk about the driver specifics and the function calls. Make it clear what you should do, and what you should not do. The user is interested in really understanding how to use the driver

Joe – at the end of the videos when talking about closing resources, make it clear this is a main topic that can go wrong. It’s more than just getting memory back, it’s closing resources to your I/O.

o Mike – this is the exact type of information that should be called out

o Jared – consider putting how to write loops appropriately in the end of the presentation; put open/config/close outside the loop; could go in generic closing to videos

Jochen – include more details at the end on how to get more information

o Last chapter of getting started guide which talks about advanced features

o How to use the IVI config store

o How to prepare your program how to exchange instruments

Guidelines and Consensus Points for All Videos

Length: 10 minutes maximum (including open, body, close)o Opening: 1 minuteo Body: 7-8:30 minuteso Closing: 15-30 seconds


Formato Jared A to propose based on lessons learned of creating the LabVIEW and

LabWindows/CVI videos

Openingo Set basic expectations – what’s the point of the video, and then the outline to followo Benefit statemento Accessing and installing the driverso The IVI webpage – Resources page and all that’s included

Bodyo Use the Getting Started Guide as the GUIDE; model the body after what’s already

included and use consistent terminologyo Focus on the driver and how to use the driver in the environment, but not the

environmento Follow the outline that’s in the GSG (this outline will be introduced during the Opening)

Closingo Additional information on installing driverso Additional information on advanced content

General Points of Discussiono It takes about 2 days to record 8 minutes of quality contento Smooth, slow, tone of voice; speak precisely and avoid slang; avoid humoro Use a script, it will likely be reusedo No slides in the bodyo GSG Videos will not be created for environments that do not have GSG PDF document o Owners: your GSG PDF document must be updated, sent to Bob, and posted along with

the videoso The same example you create or reference in the video should be made available to be

posted online along with the PDF and video

Things to Look Into Furthero Convenient ways of including the verbal script along with the video/audioo Include an example or code snippet along with GSG document and video


IVI GSG Video Project Plan

Status or Due Date

Using IVI with… Owner GSG PDF Update

GSG Video v1

GSG Video v2

GSG Video Release Candidate

GSG Video Final (including opening / closing)

Opening and Closing Segments

Bob H May 2011

March 2011

April 2011 Included w/ others

Visual C++ Joe M May 2011

May 2011

June 2011 August 2011

C# and VB. NET Kirk F May 2011

May 2011


VB .NET Kirk F May 2011

May 2011


LabVIEW Jared A Done Done March 2011

April 2011 May 2011

LabWindows/CVI Jared A Done Done March 2011

April 2011 May 2011

MATLAB Rob P May 2011

May 2011


Measure Foundry Kristen S May 2011

May 2011


PAWS REMOVE

Visual Basic 6.0 May 2011

May 2011


VEE Pro Deborah H May 2011

May 2011


Deliverables Send to Bob, Bob to post

Review with IVI MC

Review with IVI MC

Review with IVI MC, Send to Bob

Bob final production, Review with IVI MC, post to web, Press


release for Autotestcon in September

Summary of New Action Items:


Jared AReview NI’s IVI GSG Video v2 at March conf call March 2011 Open

Bob HReview Opening and Closing segments at March conf call March 2011 Open

Jared A/Bob H

Review Opening/Closing segmens, and LabVIEW and LabWindows/CVI release candidates

April 2011 Open

Jared A/Bob H

Complete LabVIEW and LabWindows/CVI IVI GSG Videos by May meeting May 2011 Open

IVI GSG Content Owners

Send updated IVI GSG PDF documents to Bob May 2011 Open

Bob H Post completed IVI GSG chapters to the web May 2011 Open


All IVI GSG Videos v1/v2 to be reviewed during May meeting May 2011 Open

IVI GSG Content

All IVI GSG Videos release candidates to be June 2011 Open



Owners reviewed


Send release candidate footage to Bob for final production June 2011 Open

Bob HFinish final production of videos and send for review August 2011 Open

Jared A Press release on availability of IVI GSG Videos August 2011 Open

Bob H

Complete IVI GSG Video project by posting content and sending press release during Autotestcon

September 2011

Open


Chapter 5 IVI Marketing Committee Meeting MinutesGeneral Meeting Info:

Date of Meeting: February 9, 2011


Chairperson: Jared Aho

Minutes Prepared By: Jared Aho

Meeting Attendees:

Name Company Attended

Jared Aho National Instruments Y

Kirk Fertitta Pacific MindWorks Y

Bob Helsel IVI Foundation Y

Jochen Wolle Rohde & Schwarz Y

Rob Purser The Mathworks Y

Mike Wadzita Tektronix Y

Joe Mueller Agilent Y

John Harvey Agilent N

John Ryland Keithley Y

Jason Schares Rockwell Collins Y

Santanu Kumara Tektronix N

Eric Lord Pacific Power Source N

Kevin Lam Ametek Programmable Power N

Eric Wetjen The MathWorks Y

Tom Fay Agilent N

Yves Maumary Agilent Y

Evan Cone National Instruments Y


Jon Bellin National Instruments Y

Jim Piotrowski National Instruments Y

Vesna Jadric National Instruments Y

David Rohacek National Instruments N

Deborah Homan Agilent N

Anshul Arora Tektronix Y

Don Essner DRS Y

Vinod Cherian The Mathworks Y

Mike Woodring Pacific Mindworks Y


Discussion Topics: Roll Call Review of action items from previous meeting New Business Summary of New Action Items Proposed Next Meeting: March 22, 2011, Conference Call


Bob HCreate a “letterhead”/masthead for white papers written on behalf of IVI Foundation Feb 9 2011 Open

Kirk F Send updated IVI white paper to Bob Feb 9 2011 Done

Bob H Post the IVI White paper on the website Feb 9 2011Pending letterhead

Bob H Post updated GSG chapters Feb 9 2011Moved to May

Camtasia Video Owners

Get raw footage ready for editing and production Feb 9 2011 Open

Jared A Press release on availability of camtasia videos March 31 2011

Open

Bob H Press release on HiSLIP Q1 2011 Open

John H Draft of IVI.NET press release Feb 7 2011 Open

John H Press release on .NET support Q2 2011 Open

Arun V/Jared A

Marketing plan for IVI.NET Feb 7 2011 Open


Record of Discussions: IVI letter-header graphic

o The colorful design might look poorly if printed; suggested to use a basic letterhead which includes graphic and dividing line; use colors consistent with existing IVI content, but minimally

o Bob H – get with Joe to get previous header graphic; the graphic should be a replica of the IVI logo on the webpage, but without the busy-colors

IVI white papero Kirk finishing opening; to send to Bob, Bob to attach leader head, and send to marketing

committee by next marketing meetingo Kirk finished the white paper during the marketing committee meeting and sent outo IVI white paper pending letterhead before it can be publishedo Bob H – attach letterhead after marketing committee approves, and then post to

Resources page

Marketing section of IVI websiteo Bob H get Jared A access; Jared A to post IVI MC meeting notes to page

IVI GSG Videoso For detailed notes, refer to the “IVI Marketing Meeting_Camtasia_110208.docx” documento Reviewed the Guidelines and Consensus Points and the IVI GSG Video Project Plan, both

documented in the 110208 meeting minuteso Follow the GSG chapter and it provides you the template, form, driver, etc. to use for the

videoo Bob to send Kristen S contact info to Jared; Jared to communicate video ownershipo Do we do a separate video for VB. NET?

May might be difficult to hit for PMW, but yes, we need two separate videos for C# and VB .NET

o Should VB 6 be created? Rob proposes that VB 6 is more commonly used than we’d think At risk of being delayed or deferred. Pending volunteer

o Reuse – do we recommend reusing IVI GSG content on vendor webpages? Jared recommend promotion, but pointing to IVI page. Easier maintainability,

teaches them where to go for additional information Sounds like The Mathworks has the GSG MATLAB chapter hosted on their webpage This should be discussed at future meeting and marketing committee should

propose policieso All updates on GSG chapters submitted and posted by Mayo IVI GSG video press release pushed to August 2011


HiSLIP press releaseo Content expert for this release is Joe Mo Marketing owner for this release is Bob Ho We want to announce the availability of products, and as of now no known products

shippingo Expected to be 3-6 months until products availableo Review HiSlip press release during May meeting; Bob H to circulate prior to meeting

IVI .NET press releaseo Content expert for this release is John Ho Marketing owner for this release is John Ho We want to announce after the availability of drivers, and as of now not releasedo Review IVI .NET press release during May meeting; John H to circulate prior to meeting

IVI .NET marketing plano Review IVI .NET marketing plan during May meeting

Driver Registry webpageo Krk completed the updates to the driver registry for IVI .NET; the final cost was $0

AC Power press releaseo We want to announce the release of a new specificationo Content expert is Ray Martino Marketing owner is Eric Lordo Review in AC Power pres release during May meeting; Eric L to circulate prior to

meeting

2011 Marketing Activitieso 2011 conference calls will heavily be used for IVI GSG Video status updates and to make

progresso During the in-person meetings, we require a 3 hour IVI GSG Video working sessiono Jared A - During the May meeting, we need to get status updates on currently proposed

press releases and suggest schedule for release, budget availability, consideration to consolidate releases HiSLIP, IVI .NET, AC Power, IVI GSG Videos

IVI Plaques


o Joe M to bring IVI plaque to May meeting for signatures, and to send to Scott as a thank you

o Need to come up with plan for plaques; current home under Joe’s desk is running short on space

o Other consortiums seem to be getting the same benefit by using a basic colored-framed plaque as IVI is with heavier, machined plaque

o Joe M to lead discussion at May meeting on what to do with plaques One proposal is take them to Autotestcon 2011, and let companies take them home

with them Another proposal is find a new home for them; NI and Mathworks volunteered

housing them


Summary of New Action Items:


IVI GSG 2011 Marketing Initiative – Autotestcon September 2011 target release

IVI GSG Owners

Refer to IVI GSG Table for complete list of action items. Action items for next two marketing committee meetings to be included in this table.

Ongoing Open

Jared AReview NI’s IVI GSG Video v2 at March conf call March 2011 Open

Bob HReview Opening and Closing segments at March conf call March 2011 Open

Jared A/Bob H

Review Opening/Closing segmens, and LabVIEW and LabWindows/CVI release candidates

April 2011 Open

Bob HUpdate the “letterhead” to be consistent with feedback March 2011 Open

Bob HPost the IVI white paper on the IVI Resources website March 2011 Open

Jared APost the marketing committee notes to the member section of the IVI website March 2011 Open

Bob H/ Jared A

Communicate to IVI GSG Owners not in attendance so they are aware of action items, dates, and deliverables

March 2011 Open

Joe M

Bring a plaque to May meeting to sign and send to Scott; lead discussion on plan for plaques

May 2011 Open

Bob H/ Joe MCirculate HiSLIP pres release draft in time for review during in-person meeting May 2011 Open

John H Circulate IVI .NET press release draft in time May 2011 Open



for review during in-person meeting

Eric L/ Ray MCirculate AC Power press release draft in time for review during in-person meeting May 2011 Open

Jared A Review schedule of press releases for 2011 May 2011 Open

Jared A Review IVI .NET marketing plan May 2011 Open


Chapter 6 Technical Committee

General Meeting Info:Date of Meeting: February 09, 2011

Location: Las Vegas

Chairperson: Jon Bellin

Minutes Prepared By: Vesna Jadric

Topics To Be Discussed:

Review Agenda Review Voting Members In Attendance Patent Call Approve minutes from the June 2010 Technical Committee Meeting Approve minutes from the October 2010 Technical Committee Meeting Review outcome of recent eVotes, IPR Declarations, Editorial Changes, and Reviews Review Action Items from Previous Meeting Review Spec Status Document Working Group Topics

VISA: Discuss requested changes for VXI and PXI – Jim Piotrowski IviFgen: IVI.NET Driver Prototyping – Yves Maumary IviACPwr: Issues with the cross-references in the .doc file – Vesna Jadric HiSLIP Review – Joe Mueller

New Business Document management discussion – Kirk Fertitta

Discuss Upcoming Meetings New Action Items

Voting Members In Attendance

Present Organization Name Name

Aeroflex Corporation Mark Meldrum


Present Organization Name Name

X Agilent Technologies Joe Mueller

Ametek Programmable Power Kevin Lam

BAE Systems Wade Lowdermilk

X DRS-SSI Don Essner

X Keithley Instruments John Ryland

X National Instruments Jon Bellin

Nokia Torben Christensen

X Pacific MindWorks, Inc. Kirk Fertitta

Pacific Power Source, Inc. Eric J. Lord

X Rohde & Schwarz Jochen Wolle

X Rockwell Collins Jason Schares

X Tektronix Anshul Arora

Teradyne, Inc. Teresa Lopes

X MathWorks, Inc. Rob Purser

TYX/EADS Chris Gorringe

X VTI Instruments Tom Sarfi

There are 10 voting members in attendance, which satisfies the requirements for a quorum of 5 of Voting Members. (Quorum is 25% of Voting Members. There are currently 17 Voting Members.)

Patent CallPlease be aware that this meeting is being held under the Intellectual Property Rights policy adopted by IVI Foundation. If you do not have a copy of this policy, please see me during this meeting. You may also view and download a copy of that policy at the Organization>>Legal Documents section of the Consortium website.


At this time, I would ask that anyone in attendance inform me if they are personally aware of any claims under any patent applications or issued patents that would be likely to be infringed by an implementation of the specification or other work product which is the subject of this meeting. You need not be the inventor of such patent or patent application in order to inform us of its existence, nor will you be held responsible for expressing a belief that turns out to be inaccurate.

Approve minutes from the June 2010 Technical Committee MeetingsThe minutes from the June 2010 Technical Committee Meetings are posted on the IVI Foundation web site.

No issues were brought up with the minutes. The minutes are accepted.

Approve minutes from the October 2010 Technical Committee MeetingsThe minutes from the October 2010 Technical Committee Meetings are posted on the IVI Foundation web site.

No issues were brought up with the minutes. The minutes are accepted.

Review outcome of recent IPR Declarations, eVotes, and Reviews

IviDigitizer Editorial Changes

On October 15th, Yves Maumary announced IviDigitizer editorial changes via the email below

From: <[email protected]>

To: [email protected]

Date: 10/15/2010 06:46 PM

Subject: Review Period Starting for the IviDigitizer Specification with Editorial Changes

Hello, The IVI Data Conversion Working Group has identified a set of editorial changes to the IVI-4.15


IviDigitizer specification. The updated draft is available at the following URL: http://www.ivifoundation.org/membership/committees/Data%20Conversion/Draft%20Spec/IVI-4.15_Digitizer_.NET_Review_Draft_2010-10-13.doc You will find attached to this message a change document showing the changes. The review period for this document starts October 15, 2010, and runs through October 22, 2010. Please send comments to Yves Maumary by the end of the day on October 22, 2010. Best regards, Yves Yves Maumary Agilent Technologies SA Phone +41 (0)22 884 3221

There was no review feedback regarding the proposed changes. The Editorial Changes are accepted.

Action Item: Yves to post updated spec on the IVI Foundation web site.

IVI-3.1 Editorial Changes

On October 22nd, Vesna Jadric announced IVI-3.1 editorial changes via the email below

From: Vesna Jadric/AUS/NIC


Date: 10/22/2010 11:07 AM

Subject: Editorial Review: IVI-3.1 Spec Changes (6-day review)

Greetings:

During the October IVI Foundation meeting in Boston, National Instruments was tasked with updating IVI-3.1 specification to remove the bitness of the DLL in the Section 5.17.12.

The change document is now posted to the IVI-3.1 web site.

IVI-3.1 Proposed Change - Remove the DLL bitness IVI-3.1: Driver Architecture Specification

The review period for this editorial change is October 22 - November 2, 2010.


http://www.ivifoundation.org/membership/committees/IviDriverArchitecturev3_1/IVI-3.1_Architecture_2010-10-22.doc

http://www.ivifoundation.org/membership/committees/IviDriverArchitecturev3_1/IVI%203.1%20Proposed%20Change%20-%20Remove%20DLL%20bitness.docx

http://www.ivifoundation.org/membership/committees/IviDriverArchitecturev3_1/Default.aspx

Please contact me with feedback.

Thanks,

Vesna JadricSoftware Group Manager | Instrument Drivers/IVI | National Instruments | 512-683-5360


VPP-6 Editorial Changes

On January 11th, Vesna Jadric announced VPP-6 editorial changes via the email below



Date: 01/11/2011 01:56 PM

Subject: Editorial Review: VPP-6 Spec Changes (6-day review)

Greetings:

During the October IVI Foundation meeting in Boston, National Instruments was tasked with updating VPP-6: Installation and Packaging specification to match current practice for G-Based drivers in the Sections 5 and 7.

The change document and the updated spec are now posted to the VXI plug&play Working Group web site.

The review period for this editorial change is January 11 - January 20, 2011.


Thanks,

Vesna JadricInstrument Drivers/IVI | National Instruments | 512-683-5360


IviACPwr Editorial Changes

On January 31st, Vesna Jadric announced IviACPwr editorial changes via the email belowIVI Foundation Meeting Minutes Oct. 2010



Date: 01/31/2011 10:12 AM

Subject: Editorial Review: IVI-4.5: IviACPwr Spec Changes (6-day review)

Greetings:

National Instruments proposed to make several editorial changes in the IviACPwr spec. The change document and the updated spec can be found on the IviACPwr working group web site.

The review period for this editorial change is January 31 – February 8, 2011.


Thanks,

Vesna JadricInstrument Drivers/IVI | National Instruments | 512-683-5360


Review Action Items from October 2010 MeetingOwner Action Item Status

Scott Rust Scott Rust approve the June 2010 Technical Committee Meeting minutes at the February 2011 Technical Committee meeting

[02/09/2011] Complete.

Yves Maumary Correct IviDigitizer specification and run editorial review process

[10/22/2010] Complete.

The updated spec not on the web site.

Scott Rust Scott to sign NI’s IPR declaration for VisaNS, scan the documents, and send to John Harvey and Bob H.

[11/19/10] Complete.

Bob Helsel Bob H to consolidate IPR declarations and other legal scanned documents in the Legal Working Group portion of the IVI Members Only area.

[11/11/2010] Complete.

John Harvey John Harvey put links to previous version of the .NET specs in the Member Only areas.

[02/09/2011] Identified and moved the previous versions of the specs to the Member Only areas. Need to verify some



issues with Bob and Vesna.

Jon Bellin Jon Bellin to run Editorial change process for IVI-3.1 regarding DLL bitness

[11/09/2010] Complete.

Jon Bellin Jon Bellin to run Editorial change process to update Section 5 of VPP-6: Installation and Packaging Specification to match current practice for G-Based Drivers.

[01/20/2011] Complete.

Kirk Fertitta Kirk to run the review and release process for the IVI Shared Components to incorporate the AC Power Source type libraries.

[01/18/2011] Installer created and sent to Kirk for review.

Dan Mondrik Dan Mondrik to lead VISA working to review the changes requested by the VXI 4.0 Technical Working group, to consider additions for PXI interoperability, and then make recommendations/motions to the IVI Technical Committee on what work to start in the IVI Foundation.

[02/09/2011] Complete.

Review Spec Status DocumentThe group reviewed and edited the Spec Status Document.

Working Group Topics

Requested changes to VISA specification for VXI and PXIThe VISA Working Group made the following motion:

Resolution (2011-02-09:#01): The VISA working group moves that the IVI Foundation VISA Working group update VPP 4.3, VPP 4.3.2, and VPP 4.3.4, and create a new IVI 6.3 specification, to extend the VISA definition to include:


– Extensions to control VXI-1 4.0 compliant controllers. Specifically the ability to:• Support new address modifiers for 2eVME/2eSST• Control the additional star trigger lines• Assert new SYNC100 utility bus signal

– Extensions to control PXI devices including:• A PXI BACKPLANE resource class for mapping/unmapping triggers and reserving

triggers• Support 64-bit base address registers

– A common user-kernel driver interface for PXI

The vote was 9-0-0.

IviFgen specification: IVI.NET Driver PrototypingCompleted the revision of the draft based on the prototype. The latest version is available on the WG web site.

NI and PMW will update their IviFgen headers and make them available for prototyping purposes. PMW will work with John H to port the existing IDL into Nimbus and then add new features. PMW will create .NET assembly for IviFgen. When these are available, the prototyping can start.

NI will prototype two IVI-C drivers. PMW will prototype IVI.NET drivers. PMW will prototype IVI-COM drivers after the May meeting.

IviACPwr class spec: Issues with the cross-references in the .doc fileNI gave a brief overview of the issues with the document.

The PDF created from the word document was corrupted. It appears to be problem with the cross-references in the doc file.

Action Item: Vesna Jadric to work with a Tech Writer to fix the document and create a PDF file.

HiSLIP ReviewJoe Mueller gave HiSLIP status update.

Joe outlined proposed changes to the HiSLIP spec to make the prose Lock, Close, and default port number more liberal. Joe moved that we incorporate these changes as a minor change to IVI-6.1.


Seconded by Jochen Wolle. The vote was 9-0-0.

Action item: Vesna to add this motion to the Life Cycle document.

New BusinessKirk proposed that we use a document management service (SharePoint) to make it easier to manage WG web pages. It requires an inexpensive license per user.

Kirk moved that we create a subcommittee to investigate problems in the management on the WG areas and propose a solution.

Seconded by Rob Purser. The vote was 9-0-0. Interested parties include John H, Bob H, Vesna, and Kirk.

Discuss Upcoming MeetingsThe next meeting will be May 18th – 20th in San Diego or Denver. Bob Helsel will make recommendation by the end of February.

Working Group Time

IVI.NET (including interop) ½ day

Technical Committee Meeting and BoD ½ day

Marketing Committee General 1 hr for the combined group

Marketing Committee IVI Getting Started Working Session ½ day in track 2 working session

Shared Components Management 1 hr

VISA 1/2 day

VISA.NET 1 day

Data Conversion - FGen 1/2 day

VISA.NET should not conflict with VISA or IVI.NET. Shared Components Management should not conflict with VISA.NET, IVI.NET. VISA can partially conflict with IVI.NET. Marketing Committee IVI Getting Started Working Session should not conflict with VISA.NET or IVI.NET.IVI Foundation Meeting Minutes Oct. 2010

Criteria for IVI meeting locations (from Feb 2010 TC meeting minutes):

For US meetings:

Major airport hub that allows most members a non-stop flight (examples: Denver, Dallas, Orlando, Las Vegas, Chicago, St Louis, Los Angeles, Atlanta)

Hotel journey is 20 minutes on Google maps. Sleeping room price should target $100 but not exceed $130. Willing to go higher on sleeping

room price if it is walking distance to restaurants and avoids rental car. Internet bundled into the cost.

The meeting after the May 2011 meeting is tentatively scheduled for October 3rd – 5th in Austin, TX. If Austin doesn’t get selected, the group will select Chicago, Denver, Orlando, or Dallas as an alternate location.

Tentative cities for 2012:

Feb 2012 – Atlanta or Los Angeles

May 2012 – Boston

October 2012 – Munich

Summary of Action Items Created at the February 2011 Technical Committee Meeting


Jon Bellin Jon Bellin to approve the February 2010 Technical Committee Meeting minutes at the May 2011 Technical Committee meeting

Yves Maumary Yves to post the latest IviDigitizer spec version on the IVI Foundation web site

Vesna Jadric Fix the IviACPwr spec and create a PDF file

Kirk Fertitta Kirk to run the review and release process for the IVI Shared Components 2.2



John Harvey John Harvey to put links to previous version of the .NET specs in the Member Only areas

Vesna Jadric Follow up with John H about 4 different items in the Life Cycle document

Vesna Jadric Fix the name of the IviACPwr spec on the web

Vesna Jadric Vesna to add HiSLIP minor change to the Life Cycle document

[02/10/2011] Complete.

Adjourn

Meeting Adjourned.

Chapter 7 IVI BoD Meeting Feb 9, 2011

Called to order at: 13:35

Directors in attendance

Present Director Company

X Don Essner DRS Sustainment Systems, inc

X Rob Purser MathWorks

X Kirk Fertitta Pacific MindWorks, Inc.

X Jason Schares Rockwell Collins

X John Ryland Keithley

X Joe Mueller Agilent Technologies

X Jon Bellin National Instruments

X Jochen Wolle Rohde & Schwarz


Quorum is a majority of directors. 8/8 satisfies the requirement.

Agenda Review

IVI BOD MEETING FEB 9, 2011

1. DIRECTORS IN ATTENDANCE

2. AGENDA REVIEW

3. REMINDER OF THE IP POLICY, ANTI-TRUST, AND DUTY OF TRUST OF DIRECTORS

4. RESOLUTIONS PASSED BY ELECTRONIC MEANS SINCE LAST MEETING

5. INPUTS REGARDING MINUTES OF PREVIOUS MEETING

5.1 ACTION ITEMS FROM PREVIOUS MEETING

6. ELECTION OF OFFICERS

7. BOD SUB COMMITTEES

8. FINANCIAL REPORT

9. REPORT FROM MARKETING COMMITTEE

10. SHARED COMPONENT WORKING GROUP – SOURCE CODE CONTROL NEED

11. MEMBER USE OF FOUNDATION OWNED DOCUMENTATION INCLUDING PROSE AND FIGURES

12. VXI TEAM ASSISTANCE IN NEW VISA WORK

13. OTHER NEW BUSINESS

Reminder of the IP Policy, Anti-trust, and Duty of Trust of Directors

The IVI Foundation has an IP policy that could require that some of your corporations’ IP be licensed to the IVI Foundation and its members at no cost. Every participant in the IVI meetings should be familiar with the obligations that participation in the standard incurs on your company.

Every member of the consortium is encouraged to familiarize themselves with legal requirements regarding anti-trust violations. Members need to be cautious and refrain from discussing markets and pricing.


Directors have a duty to the IVI Foundation. They are legally and ethically obligated to do the “right thing” for the IVI Foundation since they serve as a principal of that organization, if this conflicts with other responsibilities such as their duty to their employer, they need to take appropriate actions to resolve the conflict of interest.

Resolutions passed by electronic means since last meeting

No motions were passed by the Board of Directors since the last face-face meeting:

Inputs Regarding Minutes of Previous MeetingNone expressed

Action Items from Previous Meeting

ITEM OWNER UPDATE

Discuss work needed on driver registration page to Tango (need to add IVI .NET). Arun to approve (or not) work.

Kirk Fertitta Done – work is complete at no expense.

Incorporate something in IVI 3.1 on member use of IVI owned prose (IP)

Jon Bellin Done – updates to 3.1 completed as editorial updates to 3.1

Bob Helsel move the AC Power spec from the working group area to the main spec download area

Bob Helsel Done

Election of officersOffice Serving in 2010 Nominees for 2011

President Joe Mueller Joe Mueller

Treasurer Scott Rust Jon Bellin

Secretary Jochen Wolle Jochen Wolle

Chair Technical Committee Scott Rust Jon BellinIVI Foundation Meeting Minutes Oct. 2010

Chair Marketing Committee Arun Veeramani Jared Aho

Kirk Fertitta moved that these nominees be elected. Rob Purser seconded.

Motion passed unanimously.

BoD Sub Committees

Sub Committees of BoD Serving in 2010 Nominated for 2011

Legal Committee

Marketing Committee Arun Veeramani (chair) Jared Aho

Rob Purser Rob Purser

Jochen Wolle Jochen Wolle

Kirk Fertitta Kirk Fertitta

Deb Homan Deb Homan

Joe Mueller

Bob Helsel Bob Helsel

Operating Procedures


Operating procedures and Legal committee will be formed if and when needed. In their absence, relevant issues will be handled by the board of directors.

Jared should use this list as the nominal members of the marketing committee.

Financial Report

The following summarizes the financial status of the consortium:

Shared Component Working Group – Source Code Control Need

Motion from Shared Component Working Group that we put all source code in a 3rd party managed source code control system, grant every voting member company the right to a single license, permit any member company additional licenses at cost (full year licensing only, to be paid in advance, when requested).

Discussion:

- We anticipate needing about $1200/year to cover this (because we only anticipate about 5 active users).

- Could attempt to limit the number of users, or put the right to gain access at the discretion of the Shared Component Working Group.

- We WOULD require that the official representative of the company request access for a company to gain access.


Motion Second and Carried: 7:0:0

Initially: Agilent,NI, R&S,Pacific MindWorks

Group would also like the BoD to consider moving the FogBugz billing to a similar model.

Currently have 3 users (NI, PMW, Agilent). Based on this would have a $900 annual expense.

Rob Purser moves that we adopt a similar model for FogBugz billing as we just agreed to for source code control system access. Here membership will be subject to Shared Component Chairman approval.

Kirk Fertitta seconded.

MSC, passed unanimously.

Member use of Foundation owned documentation including prose and figuresThe new text is in section 5.21.1 of IVI 3.1. This permits users to pull material from specs to use in documentation. With notice, to be in place by 2016.

VXI Team Assistance in new VISA workProbably VTI and EADS, which are members, can represent the VXI needs for VISA updates. No action needed.

Other New businessBob Helsel to draft a letter of appreciation to Scott Rust for his years of service to IVI. IVI Foundation Meeting Minutes Oct. 2010

IVI Plaques

Marketing committee will decide what to do, people generally like the plaques. Will definitely send one with appropriate insert to Scott Rust.

Adjourned 2011-02-09

Chapter 8 Annual Membership MeetingFeb 09, 2011

Called to order: 13:21

Review voting members in attendance, introductions

Voting Members in Attendance (establish quorum and voting representatives in attendance):

Company Representative Present


Aeroflex Corporation Marv Rozner

BAE Systems Wade Lowdermilk (Ron Drees)

DRS Sustainment Systems, inc Don Essner X

Keithley Instruments John Ryland X

MathWorks Rob Purser X


Pacific MindWorks, Inc. Kirk Fertitta X

Pacific Power Source, Inc Eric Lord

Rockwell Collins Jason Schares X

Tektronix Anshul Arora X

Teradyne Teresa Lopes

EADS/TYX Corp Chris Gorringe

VTI Instruments Sangram Gaikwad (Tom Sarfi) X

Company Representative Present

Agilent Technologies Spon Joe Mueller X

National Instruments Spon Jon Bellin X

Rohde & Schwarz Spon Jochen Wolle X

Note: Quorum is 25% of voting membership or 2, whichever is greater (By-Laws section 3.6). Based on 16 voting members, a quorum is 4.

_10__ Present 2011-02-09 satisfies quorum.


Review Agenda

ANNUAL MEMBERSHIP MEETING_____________________________________________________1

1. REVIEW VOTING MEMBERS IN ATTENDANCE, INTRODUCTIONS__________________1

2. REVIEW AGENDA________________________________________________________________1

3. REVIEW MINUTES OF PREVIOUS MEETING_______________________________________2

4. CIRCULATE MEMBERSHIP ROSTER TO BE CORRECTED BY MEMBERS____________2

5. CREATE SLATE OF GENERAL DIRECTORS REPRESENTING GENERAL MEMBERSHIP..........2

6. IDENTIFY SPONSOR DIRECTORS AS ELECTED BY SPONSOR MEMBERS____________3

7. NEW BUSINESS__________________________________________________________________3

Review minutes of previous meetingNo concerns expressed

Circulate membership roster to be corrected by membersWritten copy of membership record circulated.

Create slate of general directors representing general membershipThere are 15 General-level members in the IVI Foundation, Inc., of whom, 6 are in attendance. Being more than 25% of the total membership that class, this constitutes a quorum.

NOTE FROM BY-LAWS 4.3c: “… Notwithstanding anything in these By-laws to the contrary, at the discretion of the Board, no Member shall be eligible to nominate or elect a Director if such Member’s representative to the Board of Directors failed to attend a majority of the meetings of the Board in the previous year….”

Company Representative Able To Serve


Aeroflex Corporation Marv Rozner

BAE Systems Wade Lowdermilk (Ron Drees)

DRS Sustainment Systems, inc Don Essner X

Keithley Instruments John Ryland X

MathWorks Rob Purser X


Pacific MindWorks, Inc. Kirk Fertitta X

Pacific Power Source, Inc Eric Lord

Rockwell Collins Jason Schares X

Tektronix Anshul Arora

Teradyne Teresa Lopes

EADS/TYX Corp Chris Gorringe

VTI Instruments Sangram Gaikwad (Tom Sarfi)

15 total general members. As a class, General Members are permitted to nominate 5 directors.

Kirk Fertitta moved that each of the 5 available directors be elected as the general membership directors. Rob Purser seconded.

Resolution passes: 6:0:0


Identify Sponsor Directors as elected by Sponsor Members

The following directors were elected by their representative companies.

Company Representative

Agilent Technologies Joe Mueller

National Instruments Jon Bellin

Rohde & Schwarz Jochen Wolle

New BusinessNone

Adjourned 13:34

Meeting adjourned:


IVI 2010 June Meeting Summary Final · Web viewPatent Call Please be aware that this meeting is...

Documents

Transcript of IVI 2010 June Meeting Summary Final · Web viewPatent Call Please be aware that this meeting is...