RPM | REQUIREMENTS AND POLICIES MANUAL

Viewable by the world

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Unknown macro: {dojo-tabs}
Unknown macro: {dojo-tab}

Title:

Nondisclosure Agreements

Publication date:

1/2/2012

Effective date:

9/20/1996

BRIEF

Policy Summary

A written Nondisclosure Agreement (NDA) must be approved and signed by Technology Transfer before proprietary information (outgoing or incoming) is shared, in any form, with non-Berkeley Lab employees. Information disclosed by Laboratory employees under an NDA must be identified as "proprietary" or "confidential." Laboratory employees are not allowed to sign Nondisclosure Agreements from outside entities without the approval of Technology Transfer.

Who Should Read This Policy

  • All employees
  • All affiliates

To Read the Full Policy, Go To:

Contact Information

Licensing Manager
Technology Transfer
[email protected]

Unknown macro: {dojo-tab}

Title:

Nondisclosure Agreements

Publication date:

1/2/2012

Effective date:

9/20/1996

POLICY

Details of this policy have not yet been converted to the new format.
Please go to these pages to find the details:

Contact Information

Licensing Manager
Technology Transfer
[email protected]

Revision History

Date

Revision

By whom

Revision Description

Section(s) affected

Change Type

1/2/2012

0

H. Clark

Re-write for wiki

All

Minor

Unknown macro: {dojo-tab}

DOCUMENT INFORMATION

Title:

Nondisclosure Agreements

Document number

10.04.006.000

Revision number

0

Publication date:

1/2/2012

Effective date:

9/20/1996

Next review date:

1/2/2013

Policy Area:

Intellectual Property

RPM Section (home)

Info Management

RPM Section (cross-reference)

5.06(C)(1) and 5.06(F)

Functional Division

Tech Transfer

Prior reference information (optional)

RPM Sections 5.06(C)(1) and 5.06(F)

Source Requirements Documents

Contract 31, Clause I.92 – DEAR 970.5227-3, Technology Transfer Mission (Deviation JUL 2006)

Implementing Documents

None

  • No labels