TO:
`
`Stuart Goodniok
`
`FAX:
`PHONE:
`
`Compumotor
`(707) 584-8015
`(800) 358-9068
`
`FROM:
`
`Dave Brown
`
`PHONE:
`
`ROY-G-BIV Corporation
`(206) 820-1245
`
`DATE:
`
`1/18/94
`
`PAGES:
`
`3 including this one.
`
`NOTES:
`
`Hi Stuart,
`
`Here is brief description of the model we are working with, the benefits, and the
`process that we are following. If you have any problems with this transmission,
`please let me know.
`I look forward to talking to you tomorrow.
`
`Best Regards,
`
`Dave Brown
`
`ROY-G-BIV Corporation,
`
`ABB Inc.
`
`EXHIBIT 1007
`
`
`
`ROY-G-BIV
`
`Well-engineered software for a spectrum of ideas
`
`ROY-G-BIV Corporation
`12434 82nd Avenue NE
`
`Kirkland, WA 98034
`(206) 820-1245
`
`
`
`Page 1 of 3
`
`RGBOOO52984
`
`Page 1 of 3
`
`

`

`
`
`Standardizlng Motion Control Windows Open Service Architecture
`
`. Windows Open Service Architecture
`
`Windows Open Service Architecture provides an insulation layer between the application developer and the
`device drivers created by service providers.
`Insulating the application
`
`developer from the device driver implementation details of the service
`allows them to work more efficiently. A manager layer supporting the
`Application Programming Interface (API) handles all high level driver
`OJ
`.,
`functionality. Some functionality examples included in this layer are
`213..
`A308“
`support for an OLE 2.0 interface, OLE 2.0 Automation, error
`rec/gtqu . 855 ..
`management, data normalization, and any other high level, motion
`
`control functionality. All device driver called by the manager layerfl,» '9," '
`<
`'
`support the Service Provider Interface‘?’z
`e functionality provided bbl
`,r/ i
`the device driver layer is specific to the hardware used. The next
`section describes some of the advantages of using the WOSA model
`
`for both service provider and application deve10per.
`’
`'
`
`if
`
`Advantages of using WOSA
`
`Provides hardware independent interface which increases marketability of higher level software
`applications.
`Simplifies device driver development - All interface details and common functionality are handled by
`the API layer.
`OLE 2.0 interface prepares applications for Windows 4.0 (Chicago) and Windows NT.
`Provides easy integration into higher‘fp’i‘ogramming languages through OLE 2.0 Automation.
`0 Visual Basic
`'
`0
`Excel
`
`Follows client/server model.
`
`Future OLE 2.0 will provide remote server capability.
`
`0
`
`0
`
`O 0
`
`0
`
`0
`
`Standardization Process
`
`How can we put WOSA to work? To make the model useful to all users, we need to standardize both the
`Service Provider Interface and Application Programming Interface. At ROY-G-BIV we are pulling
`together several industry leaders in the motion control hardware and software markets into a forum to do
`just that. Within the forum, we will work with all vendors by fielding their input into the specification.
`Updated specifications and pre-release software supporting the API specification are made available to all
`participating vendors allowing them to integrate the soflware into their applications before the final public
`release.
`In addition to hardware vendors, we are planning to work with software application developers to
`help specify and promote the Application Programming Interface.
`
`.
`
` 1
`
`ROY-G-BIV Corporation
`
`‘
`
`1/18/94
`
`
`
`Page 2 of 3
`
`RGBOOO52985
`
`Page 2 of 3
`
`

`

`
`
`Standardlzlng Motlon Control Wlndows Open Service Architecture
`
`Our Role
`
`We are in the process of establishing a standard motion control interface in the motion control market for
`Windows and Windows NT. Currently, we are creating a consortium of hardware vendors interested in
`enhancing their market share within the software portion of the motion control market. Our role includes
`the following:
`
`1.
`
`2.
`
`0 at 3.
`
`Coordinate specification evolution.
`a) Manage input from participants.
`i)
`CompuServe
`ii) Direct Mail
`iii) Phone
`iv) Meetings
`b) Maintain current specification.
`c)
`Distribute current specification.
`d)
`Enlist new participating companies.
`i)
`Hardware vendors.
`ii)
`Software vendors.
`Develop manager layer supporting the AP].
`a)
`Target Windows NT
`b)
`Target Windows 4.0 (Chicago)
`0)
`Target Windows 3.1 WIN325
`Develop device driver supporting the SP1 for one vendor.
`a)
`Target Windows 4.0 (Chicago)
`b)
`Target Windows NT
`
`Participant’s Role
`
`The role of the participant is to have input on the specification, support the SP1 layer in developed device
`drivers, and market the API/SPI software. Below is a detailed description of their role.
`(a) 9&1.
`Participate in specification evolution.
`:..r;,‘\ex\,
`WM \7‘3 lo) Sh)
`a)
`Active input.
`0&5"
`«
`(7
`Develop device drivers supporting the SP1.
`a)
`Target Windows 4.0
`b)
`Target Windows NT
`3 *3. Market the API/SPI WOSA model.
`
`2.
`
`7t? 4.
`
`Sell manager or API layer and SP1 supporting device driver with hardware.
`
`fl
`
`'46“)
`«- W
`W
`(011/
`" M. 0M W / fl
`/ OW Exciucjt/ llfi ’
`
`a“
`'
`
`__________________——————————
`
`ROY-G-BIV Corporation
`
`2
`
`1I18I94 .
`
`Page 3 of 3
` RGBOOO52986
`
`Page 3 of 3
`
`