throbber
1 of 4
`
` CROSSROADS EXHIBIT 2350
`Oracle Corp., et al v. Crossroads Systems, Inc.
` IPR2014-01207 and IPR2014-1209
`
`

`
`I, John Middleton, state and declare as follows:
`
`1.
`
`I was an employee of Crossroads Systems, Inc. from 1997 until 2001.
`
`I started at Crossroads in February of 1997. For most of my tenure at Crossroads I
`
`was a Vice—president of engineering.
`
`2.
`
`During 1997, I worked on the “Verrazano” project, which ultimately
`
`became Crossroad’s first storage bridge product. During this time period, I worked
`
`with both Geoffrey Hoese and Jeffrey Russell on the Verrazano project. My role
`
`on Verrazano was hardware engineering manager.
`
`3.
`
`During my employment at Crossroads, including my work on the
`
`Verrazano project, I became familiar with Crossroads’ recordkeeping practices.
`
`Specifically, I became familiar with Crossroads’ practices regarding the creation,
`
`modification, and keeping of documents. Documents related to the Verrazano
`
`project, such as presentations, drawings, product specifications, product
`
`instructions, reports, and the like, were created by Crossroads employees during
`
`the regular course of business.
`
`4.
`
`Both during and after the Verrazano project, it was the regular
`
`practice of Crossroads’ employees to create such records at or near the time the
`
`recorded act, event, condition, or opinion occurred. For example, if a particular
`
`drawing were updated or changed, the change was generally noted by inclusion of
`
`1
`
`2 of 4
`20f4
`
`

`
`a revision date and a description of the reason for the change. If a document was
`
`revised, generally this would be reflected by a new revision number and the date of
`
`the revision. It was the general practice of Crossroads’ personnel to date such
`
`documents as of the date the record was created or modified. I do not recall any
`
`instance in which documents related to the Verrazano project were dated in the
`
`future or the past, and doing so would have been inconsistent with Crossroads’
`
`normal practice.
`
`5.
`
`It was Crossroads’ normal practice that documents and records could
`
`only be made or revised by someone with knowledge or based on information
`
`transmitted by someone with knowledge. Documents and records like those
`
`mentioned in paragraph 3 were regularly made and kept in the course of
`
`Crossroads’ regularly conducted business activity—specif1cally, the design and
`
`creation of new products.
`
`6.
`
`The above practices were in place at Crossroads in 1997, and
`
`afterwards. During the time I was at Crossroads, Crossroads practices regarding the
`
`creation, modification, and keeping of documents and records, as previously stated,
`
`did not change.
`
`7.
`
`I was at Crossroads when it sued Chaparral Network Storage. I recall
`
`gathering documents related to the lawsuit and providing them for Crossroads’
`
`2
`
`3 of 4
`30f4
`
`

`
`attorneys. When doing so, I made available only true and correct copies of
`
`Crossroads’ documents, without any changes. I am unaware of anyone making any
`
`changes to any documents that were provided to Crossroads’ attorneys.
`
`I declare under penalty of perjury under the laws of the United States of America
`
`that the foregoing is true and correct.
`
`Executed on: June __§, 2015
`
`
`
`4 of 4
`40f4

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket