X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C79D89.7DD8233B@onstor-exch02.onstor.net>; Wed, 23 May 2007 15:27:05 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C79D89.7DD8233B"
Content-class: urn:content-classes:message
Subject: RE: Minutes from 5/22 Cougar Phase 2 Exit Review
Date: Wed, 23 May 2007 15:27:04 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03D90FD0@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03D90E08@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Minutes from 5/22 Cougar Phase 2 Exit Review
Thread-Index: AcedabP5WakerZ0TSYeZrBq4glcp2wAHnf/A
From: "Mary Li" <mary.li@onstor.com>
To: "Andrew LeFebvre" <andrew.lefebvre@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C79D89.7DD8233B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


14)	QA plan needs to distinguish between what tests can be done with
REV2 HW (available 10/31) and what must be done with REV3 (available
12/7) in order to be able to ship REV3 to customers by the 1/18 FCS/GA.
This change needs to be incorporated into the integrated schedule as
well.
		[Mary] Final regression is for test on Rev3. This is
already in schedule, I just added note for this task in schedule. I also
just updated test plan to reflect this .

15)	QA needs to update their detailed schedule for the Phase 2 [60K
ops] portion of the project.  Right now they are not aligning with the
mid-June FCS.
		[Mary] Just updated the detailed schedule which is
available at \\mightydog\Program
Management\Cougar\QE\QESchedule\Cougar-QE-Schedule_v3.mpp.  I assume
starting date is 04/01/07 for phase2 which may not be true.  I couldn't
find definite SW deliverable date for QE from Integrated schedule.


_____________________________________________
From: Andrew LeFebvre=20
Sent: Wednesday, May 23, 2007 11:40 AM
To: dl-Executive; dl-eng-ops-staff; dl-Cougar Core Team; Kevin Matthews
Subject: Minutes from 5/22 Cougar Phase 2 Exit Review

All,

Thanks to everyone who participated in yesterday's Cougar Planning
Review (Phase 2 Exit).  Unfortunately, the consensus was although the
team has made good progress, we are not quite ready to proceed into the
Phase 3A (Prototype) stage.
=20
Here is a list of actions/comments I wrote down.  Please respond to all
on this e-mail if you have any additions.
16)	Tom requested there should be a "max memory" Cougar
configuration targeted for customers who are willing to pay for very
high performance.
17)	There was general concern about the Cougar code being part of
Zonda, and the affects it might have on that release.  DEV commented
that keeping Cougar completely out of the Zonda code line would delay
the Cougar FCS by a month.  Decision made to resolve this in a separate
meeting.
18)	In a similar way to how QA documented the entrance criteria for
SW, they need to document their maturity/configuration requirements for
HW.
19)	QA schedule is based on the assumption that all QA resources
will be freed up from Zonda by the middle to end of October, so they can
move to Cougar.  This allows the entire team to be engaged on Cougar,
which is needed to meet the mid-January Phase 1 [45K ops] FCS/GA.
20)	Questions were raised about the build plan yield assumptions.
Brian needs to justify numbers that seem overly optimistic.
21)	Need to understand what prototype parts have gone through DFM
and what still needs to be completed.
22)	Share what are the biggest component costs in COGS as a
percentage of the total.
23)	Discussion about FRU mechanical tolerance stackup.  Brian
believes we are protected by the way the tolerances and critical
dimensions are called out on the drawings.  Ops to provide ACT incoming
inspection plans (which components, which dimensions, what frequency)
since we are counting on them to make sure the parts are delivered to
specification.
24)	Brian commented that in the cluster-in-box configuration the
DIMM's on the two boards will be very close together.  Tom had
experience in the past of DIMM's coming loose during shipment.  Mark
mentioned that Cougar will be going through a complete set of packaging
tests to verify we will not run into this problem.  Ops to provide
schedule for these tests.
25)	Marketing's Beta needs are for 3 cluster-in-box systems.  Build
plan showed this as 3 single head, so it needs to be updated.
26)	Caeli asked that DEV be responsible for Beta install and
customer support rather than the SE and CS assistance documented in the
Beta plan.
27)	Need to work out a plan for including an internal Beta test as
part of the project.
28)	Need to close on finding a QA resource to work with DEV on
testing of Linux on Bobcat.
29)	QA plan needs to distinguish between what tests can be done with
REV2 HW (available 10/31) and what must be done with REV3 (available
12/7) in order to be able to ship REV3 to customers by the 1/18 FCS/GA.
This change needs to be incorporated into the integrated schedule as
well.
30)	Build plan currently has all of the QA test systems coming out
of REV2 HW.  QA to redefine their HW needs by REV level.
31)	QA needs to update their detailed schedule for the Phase 2 [60K
ops] portion of the project.  Right now they are not aligning with the
mid-June FCS.
32)	Need to explain why the Phase 2 SW DEV work is taking 130 days
to complete.
33)	COGS number used in build plan are about 20% too low.  Ops to
provide numbers to use for each phase.
34)	Andy to update build plan (for COGS and requirements from QA and
Mktg) and send to Frank for review.
35)	Ops to provide tooling costs and NRE by phase to Frank for
review.
36)	Tom made suggestion to come up with a summary of costs and
minimizing risk that could be shared with Bob's staff.
=20
We'll use the team meeting next week to discuss which of these items
need to be closed before we can try again to exit Phase 2.

Regards,

Andy

------_=_NextPart_001_01C79D89.7DD8233B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Minutes from 5/22 Cougar Phase 2 Exit Review</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">14)&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Arial">QA plan needs t</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">o distinguish between what tests can be done with REV2 HW =
(available 10/31) and what must be done with REV3 (available 12/7) in =
order to be able to ship REV3 to customers by the 1/18 FCS/GA.&nbsp; =
This change needs to be incorporated into the integrated =
schedu</FONT><FONT SIZE=3D2 FACE=3D"Arial">l</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">e as well</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
<UL><UL>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[Mary]</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">Final regression is for test on Rev3.</FONT> <FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">This is already in =
schedule</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">, I just =
added note for this task in schedule</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">.</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">I also just updated test plan to reflect =
this</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>
</UL></UL>
<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">15)&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">QA needs to update their detailed schedule for the Phase =
2 [60K ops] portion of the project.&nbsp; Right now they are =
no</FONT><FONT SIZE=3D2 FACE=3D"Arial">t aligning with the mid-June =
FCS</FONT><FONT SIZE=3D2 FACE=3D"Arial">.</FONT></SPAN></P>
<UL><UL>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[Mary]</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Just =
updated the detailed schedule which is available at</FONT></SPAN><SPAN =
LANG=3D"en-us"> </SPAN><A HREF=3D"file://\\mightydog\Program =
Management\Cougar\QE\QESchedule\Cougar-QE-Schedule_v3.mpp"><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">\\</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">mightydog\Program =
Management\Cougar\QE\QESchedule</FONT></U></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">\</FONT></U></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U></U><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">Cougar-QE-Schedule_v3.mpp</FONT></U></SPAN><SPAN =
LANG=3D"en-us"></SPAN></A><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial"></FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">I</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial"></FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">assume</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial"> starting date</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial"> is</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial"> 04/01/0</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">7</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> for =
phase2</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> =
which</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">may not be =
true.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial"></FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I =
couldn</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">&#8217;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">t find =
definite SW deliverable dat</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">e for QE</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">from</FONT> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">Integrated schedule</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
<BR>
</UL></UL>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Andrew LeFebvre<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Wednesday, May 23, 2007</FONT> <FONT SIZE=3D2 =
FACE=3D"Tahoma">11:40 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Executive; dl-eng-ops-staff; dl-Cougar Core Team; =
Kevin Matthews<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></SPAN></B><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Minutes from 5/22 Cougar =
Phase 2 Exit Review</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">All,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Thanks to everyone who participated in =
yesterday</FONT><FONT SIZE=3D2 FACE=3D"Arial">&#8217;</FONT><FONT =
SIZE=3D2 FACE=3D"Arial">s Cougar Planning Review (Phase 2 Exit).&nbsp; =
Unfortunately, the consensus was although the team has made good =
progress, we are</FONT> <FONT SIZE=3D2 FACE=3D"Arial">not quite ready to =
proceed into the Phase 3A (Prototype) stage.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Here =
is a list of actions/comments I wrote down.&nbsp; Please respond to all =
on this e-mail if you have any additions.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">16)&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">Tom requested there should be a &#8220;max memory&#8221; =
Cougar configuration target</FONT><FONT SIZE=3D2 FACE=3D"Arial">ed for =
customers who are willing to pay for very high =
performance.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">17)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">There was general concern about the Cougar code being =
part of Zonda, and the affects it might have on that release.&nbsp; DEV =
commented that keeping Cougar completely out of the Zonda code =
l</FONT><FONT SIZE=3D2 FACE=3D"Arial">ine would delay the Cougar FCS by =
a month.&nbsp; Decision made to resolve this in a separate =
meeting.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">18)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">In a similar way to how QA documented the entrance =
criteria for SW, they need to document their maturity/configuration =
requirements for HW.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">19)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">QA schedule</FONT><FONT SIZE=3D2 FACE=3D"Arial"> is based =
on the assumption that all QA resources will be freed up from Zonda by =
the middle to end of October, so they can move to Cougar.&nbsp; This =
allows the entire team to be engaged on Cougar, which is needed to meet =
the mid-January Phase 1 [45K ops] FCS/</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">G</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">A.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">20)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Questions were raised about the build plan yield =
assumptions.&nbsp; Brian needs to justify numbers that seem overly =
optimistic.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">21)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Need to understand what prototype parts have gone through =
DFM and what still needs to be completed.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">22)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Share what are the</FONT><FONT SIZE=3D2 FACE=3D"Arial"> =
biggest component costs in COGS as a percentage of the =
total.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">23)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Discussion about FRU mechanical tolerance stackup.&nbsp; =
Brian believes we are protected by the way the tolerances and critical =
dimensions are called out on the drawings.&nbsp; Ops to provide ACT =
inc</FONT><FONT SIZE=3D2 FACE=3D"Arial">oming inspection plans (which =
components, which dimensions, what frequency) since we are counting on =
them to make sure the parts are delivered to =
specification.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">24)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Brian commented that in the cluster-in-box configuration =
the DIMM</FONT><FONT SIZE=3D2 FACE=3D"Arial">&#8217;</FONT><FONT =
SIZE=3D2 FACE=3D"Arial">s</FONT><FONT SIZE=3D2 FACE=3D"Arial"> on the =
two boards will be very close together.&nbsp; Tom had experience in the =
past of DIMM</FONT><FONT SIZE=3D2 FACE=3D"Arial">&#8217;</FONT><FONT =
SIZE=3D2 FACE=3D"Arial">s coming loose during shipment.&nbsp; Mark =
mentioned that Cougar will be going through a complete set of packaging =
tests to verify we will not run into this problem.&nbsp; Ops =
t</FONT><FONT SIZE=3D2 FACE=3D"Arial">o</FONT><FONT SIZE=3D2 =
FACE=3D"Arial"> provide schedule for these tests.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">25)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Marketing</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">&#8217;</FONT><FONT SIZE=3D2 FACE=3D"Arial">s Beta needs =
are for 3 cluster-in-box systems.&nbsp; Build plan showed this as 3 =
single head, so it needs to be updated.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">26)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Caeli asked that DEV be responsible for Beta install and =
customer support rather than</FONT><FONT SIZE=3D2 FACE=3D"Arial"> the SE =
and CS assistance documented in the Beta plan.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">27)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Need to work out a plan for including an internal Beta =
test as part of the project.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">28)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Need to close on finding a QA resource to work with DEV =
on testing of Linux on Bobcat.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">29)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">QA plan needs t</FONT><FONT SIZE=3D2 FACE=3D"Arial">o =
distinguish between what tests can be done with REV2 HW (available =
10/31) and what must be done with REV3 (available 12/7) in order to be =
able to ship REV3 to customers by the 1/18 FCS/GA.&nbsp; This change =
needs to be incorporated into the integrated schedu</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">l</FONT><FONT SIZE=3D2 FACE=3D"Arial">e as =
well.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">30)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Build plan currently has all of the QA test systems =
coming out of REV2 HW.&nbsp; QA to redefine their HW needs by REV =
level.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">31)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">QA needs to update their detailed schedule for the Phase =
2 [60K ops] portion of the project.&nbsp; Right now they are =
no</FONT><FONT SIZE=3D2 FACE=3D"Arial">t aligning with the mid-June =
FCS.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">32)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Need to explain why the Phase 2 SW DEV work is taking 130 =
days to complete.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">33)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">COGS number used in build plan are about 20% too =
low.&nbsp; Ops to provide numbers to use for each phase.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">34)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Andy to update build plan (for</FONT><FONT SIZE=3D2 =
FACE=3D"Arial"> COGS and requirements from QA and Mktg) and send to =
Frank for review.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">35)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Ops to provide tooling costs and NRE by phase to Frank =
for review.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">36)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">Tom made suggestion to come up with a summary of costs =
and minimizing risk that could be shared with Bob</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">&#8217;</FONT><FONT SIZE=3D2 FACE=3D"Arial">s =
staff.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">We</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">&#8217;</FONT><FONT SIZE=3D2 FACE=3D"Arial">ll use the =
team meeting next week to discuss which of these items need to be closed =
before we can try again to exit Phase 2.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Andy</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C79D89.7DD8233B--
