Chapter 86 – The Shut Down

As noted in many preceding  chapters, our IT managers withholding of our programs caused us to shut down. It cost us dearly. It cost our employees, some 175 of whom had to be laid off for part of a week just before thanksgiving.

The evidence we produced on this is immense. I and two other executives testified as to the shutdown, its cost in terms of revenue and replacements costs to generate the software. I testified as to our inability to find the programs and where we looked for them. I testified and produced emails to M asking him to help after the shutdown, with the identification of the software location on the computer he returned to us and on our servers. Then Jamie Gedye, the consultant we hired, testified that he flew out from Chicago and looked for the software, the code, the programs, etc. and could not find them even with the help of Chris (our assistant manager). Jamie testified that they looked for the programs on M’s former computer, the windows servers, the dialer servers, other IT computers and the archived files. The files could not be found. Jaime testified that Chris could not find the files nor did Chris know how to generate the reports. Jaime testified that he regenerated the programming so that we could generate the reports daily and testified that the programs could not be generated daily to produce the reports. One of my clients testified that we were unable to do any work for them for over a week because of our inability to write the client reports. In addition we had forensic reports from two forensic experts concluding that the database programs were not on M’s computer nor on any of the other computer I previously identified. All in all seven witnesses, forensics reports, Foxpro experts, etc. None of the computers were destroyed.

M testified that there were no programs, that he was not responsible for the shutdown. Chris Cox however has confirmed that this is judt not true.

The surprise witness was Chris Cox, our former assistant manager, who testified that we did not shut down. That we did not shutdown! He further testified however that there were Foxpro programs that the IT department regularly accessed, a contradiction to Max’s testimony. Testifying that there was no shutdown in spite of the massive amount of evidence to the contrary, including emails to and from Chris while we were shutdown, was a challenge to our position that M destroyed the software. I don’t think an IT assistant manager forgets that we shutdown, that it could have led to his demotion and did lead to his ultimate departure.  So now they have one witnesses questioning whether there was a shutdown, but offering conflicting testimony about the existence of our programs. M did not dispute, in his testimony, that we shut down. Chris Cox’s tesimony is here.11-5-10

Whether Chris lied about the shut down is for you to decide. It would have been more consistent for him to say that he did not remember. He also referred to programming, executable files he claimed we had on the servers noting that he had used those files many time. And yet they were gone. The overwhelming record shows the files were not there. Did he forget that too? His admission that we had at one time these programs to move data around, create tables and extract reports was valuable but on balance I think Marshall and M convinced him to lie. He could not remember the names of the people who worked there but knew they had. He didn’t remember Gedye at all and he worked with him for a week. It would  be a hard thing for an IT professional to admit to lying to cover up the damage that M caused, but that is the logical truth.

The arbitrator ultimately concluded that the shutdown may not have been caused by M, that Chris testified that programs existed and should have been found by Jaime Gedye. Chris also testified that he regularly used these programs. What was not disputed by the arbitrator was that there was a shutdown. Instead he concluded that we destroyed evidence when we continued to use the servers and other computers, presumably also the $200,000 dialer, after the shutdown. One of the more bias conclusions by the arbitrator was that we had deteriorated the forensic results on missing Foxpro programs because we continued to use the computers, in spite of the fact that we had forensics work done, forensic images taken  and expert reports issued the first week after M destroyed the software. But he did not by contrast hold M to the same conclusion when M simply destroyed his emails, destroyed his computers and reformateed a hard drive owned by us (a hard drive containing Foxpro programs). M’s attorney issued the litigation hold. M’s fiancee was an attorney at the time.

I believe the arbitrator had the mental acuity to understand the foensics and had to overcome the shutdown attribution to M in order to otherwise find in his favor, a stretch of illogic on unsupported facts. We were fearful that the arbitrator’s compromised independence would lead him to set the facts aside, but calculated that once his lack of independence was raised he would not do anything as blatant as to suggest that M was not responsible for the shutdown. We were shutdown because we could not generate reports for our clients. We could not because our programs were simply not findable. Whether this was a unilateral act by M or one in collusion with Chris is beside the point. M, even as a conspirator, is liable.

I don’t think this was confusion by the arbitrator. I think it was anger for calling him out. The reasoning was weak but calculated. The perjury by M and C were easily determinable.

I have often wondered why we did not file a summary judgment motion on the shut down. That should have eliminated M’s claims and solidified ours. It would have eliminated years of work and hundreds of hours of forensics.

We will have to ask Jeff Edelson and Scott Cliff that question. I remember Scott believing that the lack of communication between me and M after his termination in October was disconcerting. That however was not something I was called to explain nor do I believe it the least bit credible to give something that subjective merit in light of the evidence we had.

We had evidence. Why wasn’t it considered? Arbitrator Bill, why wasn’t it weighed? Why wasn’t our evidence comprised of emails, forensics, the testimony of 6 independent witnesses, the testimony of 3 witnesses working for us, all taken together more compelling than the sole testimony of the defendant who destroyed his computers, his emails, our software and our hard ware?

Jaime Gedye’s testimony is here. Gedye

Chris Cox testimony is here. Chris Cox

Justin McAnn on the existence of Foxpro programs on the hard drive Max reformatted can be found here.MCann

McAnn’s Linkedin address is here. You will note that his website urls do not work and he has provided no other contact information. Much Like Max, they are ghosts.

The Foxpro programs on the hard drive Max reformatted follow. These same programs were not on the active hard drive he returned on 11/13/03. There is no record of them on the active, 60 gig hard drive, per McAnn testimony and our forensic reports.

mail_split_incoming.prg prg GEM Executable Code\Executable
incoming.prg prg GEM Executable Code\Executable
mail_split_incoming.prg prg GEM Executable Code\Executable
memb_no.PRG PRG GEM Executable Code\Executable
report.PRG PRG GEM Executable Code\Executable
comb.prg prg GEM Executable Code\Executable
temp.PRG PRG GEM Executable Code\Executable
trans.PRG PRG GEM Executable Code\Executable
adispfix.prg prg GEM Executable Code\Executable
t.PRG PRG GEM Executable Code\Executable
mail_split.prg prg GEM Executable Code\Executable
fixwiz.PRG PRG GEM Executable Code\Executable
AppBldr.prg prg GEM Executable Code\Executable
comb.PRG PRG GEM Executable Code\Executable
appwiz.prg prg GEM Executable Code\Executable
secs.PRG PRG GEM Executable Code\Executable
wt_convert.PRG PRG GEM Executable Code\Executable
mytrnsfm.prg prg GEM Executable Code\Executable
transfrm.prg prg GEM Executable Code\Executable
phonefix.PRG PRG GEM Executable Code\Executable
phone_fix.PRG PRG GEM Executable Code\Executable
mail_split.prg prg GEM Executable Code\Executable
incoming.PRG PRG GEM Executable Code\Executable
dispfix.PRG PRG GEM Executable Code\Executable
amcdmra.PRG PRG GEM Executable Code\Executable
all_report.prg prg GEM Executable Code\Executable
server.prg prg GEM Executable Code\Executable
start.prg prg GEM Executable Code\Executable
hexedit.prg prg GEM Executable Code\Executable
gendbc.prg prg GEM Executable Code\Executable
odebug.prg prg GEM Executable Code\Executable
cpzero.prg prg GEM Executable Code\Executable
conprocs.prg prg GEM Executable Code\Executable
convert.prg prg GEM Executable Code\Executable
generic.prg prg GEM Executable Code\Executable
foreign.prg prg GEM Executable Code\Executable
migdb4.prg prg GEM Executable Code\Executable
transprt.prg prg GEM Executable Code\Executable
analyzer.prg prg GEM Executable Code\Executable
utility.prg prg GEM Executable Code\Executable
main.prg prg GEM Executable Code\Executable
datepick.prg prg GEM Executable Code\Executable
anim.prg prg GEM Executable Code\Executable
cgraph.prg prg GEM Executable Code\Executable
fdproc.prg prg GEM Executable Code\Executable
pgraph.prg prg GEM Executable Code\Executable
main.prg prg GEM Executable Code\Executable
jobmgr.prg prg GEM Executable Code\Executable
dummy.prg prg GEM Executable Code\Executable
poolmgr.prg prg GEM Executable Code\Executable
srchdata.prg prg GEM Executable Code\Executable
odebug.prg prg GEM Executable Code\Executable
foxweb.prg prg GEM Executable Code\Executable
t1.prg prg GEM Executable Code\Executable
main.prg prg GEM Executable Code\Executable
insubq.prg prg GEM Executable Code\Executable
bizrules.prg prg GEM Executable Code\Executable
csmain.prg prg GEM Executable Code\Executable
csprocs.prg prg GEM Executable Code\Executable
cust.prg prg GEM Executable Code\Executable
msmqmsg.prg prg GEM Executable Code\Executable
prod.prg prg GEM Executable Code\Executable
order.prg prg GEM Executable Code\Executable
book_TCE.prg prg GEM Executable Code\Executable
book_sub1.prg prg GEM Executable Code\Executable
book_pub.prg prg GEM Executable Code\Executable
registry.prg prg GEM Executable Code\Executable
runcode.PRG PRG GEM Executable Code\Executable
setobjrf.prg prg GEM Executable Code\Executable
_base.prg prg GEM Executable Code\Executable
genmenu.prg prg GEM Executable Code\Executable
genhtml.prg prg GEM Executable Code\Executable
scctext.prg prg GEM Executable Code\Executable
RUNACTD.PRG PRG GEM Executable Code\Executable
hlp2fox.prg prg GEM Executable Code\Executable
vfpxtab.prg prg GEM Executable Code\Executable
_command.prg prg GEM Executable Code\Executable
ERR_REPORT.PRG PRG GEM Executable Code\Executable
test1.PRG PRG GEM Executable Code\Executable
amcsale.PRG PRG GEM Executable Code\Executable
crmcomp.prg prg GEM Executable Code\Executable
crmclient.prg prg GEM Executable Code\Executable
crmworker.prg prg GEM Executable Code\Executable
testqc.prg prg GEM Executable Code\Executable
foxqc.prg prg GEM Executable Code\Executable
main.prg prg GEM Executable Code\Executable
report.PRG PRG GEM Executable Code\Executable
t.PRG PRG GEM Executable Code\Executable
q.PRG PRG GEM Executable Code\Executable
tw.PRG PRG GEM Executable Code\Executable
report_pm_nodate.prg prg GEM Executable Code\Executable
dailyver.PRG PRG GEM Executable Code\Executable
T.PRG PRG GEM Executable Code\Executable
report_am.PRG PRG GEM Executable Code\Executable
report_pm.PRG PRG GEM Executable Code\Executable
daily_rpt.prg prg GEM Executable Code\Executable
scrub.PRG PRG GEM Executable Code\Executable
incoming.PRG PRG GEM Executable Code\Executable
report_am_nodate.prg prg GEM Executable Code\Executable
De135.PRG PRG GEM Executable Code\Executable
report_all.prg prg GEM Executable Code\Executable
De154.PRG PRG GEM Executable Code\Executable
De145.PRG PRG GEM Executable Code\Executable
De138.PRG PRG GEM Executable Code\Executable
De89.PRG PRG GEM Executable Code\Executable
De102.PRG PRG GEM Executable Code\Executable
De94.PRG PRG GEM Executable Code\Executable
report_all.prg prg GEM Executable Code\Executable
daily_rpt_ampm.prg prg GEM Executable Code\Executable
make_scrub.PRG PRG GEM Executable Code\Executable
make_rr.PRG PRG GEM Executable Code\Executable
incoming.PRG PRG GEM Executable Code\Executable
pe_sales.PRG PRG GEM Executable Code\Executable
pe_sales_resend.prg prg GEM Executable Code\Executable
report.PRG PRG GEM Executable Code\Executable
pe_nsr.PRG PRG GEM Executable Code\Executable
comb.prg prg GEM Executable Code\Executable
pol_send.PRG PRG GEM Executable Code\Executable
amcsale.PRG PRG GEM Executable Code\Executable
psplit.PRG PRG GEM Executable Code\Executable
hours2.PRG PRG GEM Executable Code\Executable
pe.PRG PRG GEM Executable Code\Executable
hours.PRG PRG GEM Executable Code\Executable
fone.PRG PRG GEM Executable Code\Executable
dnc2.PRG PRG GEM Executable Code\Executable
main.prg prg GEM Executable Code\Executable

All of the above, but a few, were dated in May 2003 when the hard drive allegedly crashed. The others were dated 11/12/03, the day before he turned over the files on his last day.

Our forensic report on recovered files from the active hard drive Max returned are here. 60 GB Hard Drive Recovered Files Relevant Dates. Not one Foxpro program.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s