16.05.2014 Views

Patent It Yourself - PDF Archive

Patent It Yourself - PDF Archive

Patent It Yourself - PDF Archive

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

440 | <strong>Patent</strong> it YOURSELF<br />

the employer’s business, without paying the employee) on<br />

inventions made using company time, facilities, or materials.<br />

If you have an EA, it will almost certainly require that<br />

you assign (legally transfer) to your employer all inventions,<br />

that are:<br />

1. made during the term of employment (note that<br />

Form 16A asks you to list all inventions you owned<br />

prior to employment—those are excluded from the<br />

agreement)<br />

2. related to the employer’s existing or contemplated<br />

business<br />

3. made by using the employer’s time (that is, the time<br />

for which the employee is paid), facilities, or materials,<br />

or<br />

4. made as a result of activity within the scope of the<br />

employee’s duties.<br />

Note that under items 1, 2, and 4, even if an employee<br />

makes an invention at home, on the employee’s own time,<br />

the employer still can be entitled to ownership.<br />

Also, you’ll usually be bound to disclose all inventions<br />

to the employer (so the employer can determine if they’re<br />

assignable). Lastly, most EAs will require you to keep your<br />

employer’s trade secrets confidential during and after your<br />

employment. Some states, such as California, have enacted<br />

statutes (Calif. Labor Code, Sections 2870 et seq. and 2860)<br />

prohibiting the employer from requiring the employee to sign<br />

any EA that is broader than the foregoing. For example,<br />

under such statutes the employee can’t be made to turn<br />

over all inventions, no matter where and when made, to the<br />

employer. Similarly, the employer is prohibited from providing<br />

an EA that states that everything an employee acquires from<br />

the employer (except salary) belongs to the employer.<br />

EXAMPLE: Griselda is an engineer employed by Silicon<br />

Valley Chips (SVC) to design integrated circuits. Griselda’s<br />

EA requires her to disclose to SVC all inventions<br />

made during the term of her employment at SVC<br />

and to assign to SVC all inventions which relate to<br />

integrated circuits or SVC’s business, or which she<br />

makes using SVC’s time, facilities, or materials. While<br />

employed, Griselda invents a new toilet valve at home<br />

in her workshop. The toilet valve is clearly outside<br />

the scope of SVC’s business and therefore, Griselda<br />

owns it totally. However, she should disclose the valve<br />

to SVC (regardless of whose time it was invented on).<br />

Later, Griselda, while still employed but on vacation, is<br />

cogitating about an integrated circuit design problem<br />

she had last week at work. She comes up with a valuable,<br />

less-expensive integrated circuit passivation technique.<br />

Since this invention relates to SVC’s business, SVC<br />

owns it and Griselda must disclose it to SVC and sign<br />

any patent application and assignment on it that SVC<br />

requests.<br />

If the invention is clearly within the scope of the EA, or<br />

is in a gray area, I still recommend first disclosing it to the<br />

employer. If the employer isn’t interested in the invention<br />

after reviewing it, the employee can apply for a release, a<br />

document under which the employer reassigns or returns<br />

the invention to the employee. (The employer may retain a<br />

“shop right” under the release—that is, a nontransferable<br />

right to use the invention for its own purposes and business<br />

only.)<br />

If the invention is in the gray area and the employer<br />

wants to exploit the invention, the employee can then try<br />

to negotiate some rights, such as a small royalty, or offer to<br />

have the matter decided by arbitration. Failing this, a lawsuit<br />

may be necessary, but I favor employees disclosing “grayarea”<br />

inventions so that a cloud of ownership uncertainty<br />

will not engulf their invention.<br />

Most EAs also require the invention-assigning employee<br />

to keep good records of inventions made and to cooperate<br />

in signing patent applications, giving testimony when needed,<br />

even after termination of employment. Most companies<br />

give the employee a small cash bonus, usually from one to<br />

several thousand dollars or more, when the employee signs<br />

a company patent application. This bonus is not in payment<br />

for the signing (the employee’s wages are supposed to cover<br />

that) but to encourage employees to invent and turn in<br />

invention disclosures on their inventions. Some employers,<br />

such as Lockheed, give their inventor-employees a generous<br />

cut of the royalties from their invention, and some will even<br />

set up a subsidiary entity (partly owned by the employeeinventor)<br />

to exploit the invention. Most, however, prefer to<br />

reward highly creative employees via the salary route.<br />

Legislation has been proposed and engineering organizations<br />

have sought to expand the rights of the employed<br />

inventor. One of these proposals is to change the U.S. to<br />

the German system, where employees own their inventions<br />

but usually assign them to their employers in return for a<br />

generous cut, such as 20% of the profits or royalties.<br />

E. Assignment of Invention<br />

and <strong>Patent</strong> Rights<br />

Suppose you’re an employed inventor and you make an<br />

invention on your employer’s time and your employer wants<br />

to file a patent application on it. Under the law, every<br />

patent application must be filed in the name(s) of the true<br />

inventor(s). This raises a problem. If it’s filed in your name,<br />

how will the employer get ownership? Since inventions,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!