X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C79DC8.82EAED42@onstor-exch02.onstor.net>; Wed, 23 May 2007 22:58:11 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C79DC8.82EAED42"
Content-class: urn:content-classes:message
Subject: RE: Minutes from 5/22 Cougar Phase 2 Exit Review
Date: Wed, 23 May 2007 22:57:07 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E023B3E70@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/AAAHdtRAAAbHk0AAMfH+8
References: <BB375AF679D4A34E9CA8DFA650E2B04E03D9108B@onstor-exch02.onstor.net>
From: "Paul Hammer" <paul.hammer@onstor.com>
To: "Mary Li" <mary.li@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Andrew LeFebvre" <andrew.lefebvre@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C79DC8.82EAED42
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We have to discuss :
=20
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.
27)     Need to work out a plan for including an internal Beta test as =
part of the project.=20
28)     Need to close on finding a QA resource to work with DEV on =
testing of Linux on Bobcat.=20

________________________________

From: Mary Li
Sent: Wed 5/23/2007 5:00 PM
To: Tim Gardner; Andrew LeFebvre; dl-Cougar
Subject: RE: Minutes from 5/22 Cougar Phase 2 Exit Review



Sounds good.=20

_____________________________________________
From: Tim Gardner
Sent: Wednesday, May 23, 2007 4:13 PM
To: Mary Li; Andrew LeFebvre; dl-Cougar
Subject: RE: Minutes from 5/22 Cougar Phase 2 Exit Review

Is the plan still to update the integrated schedule with the QA schedule =
so that we can create dependencies

between QA and SW tasks? Once this has been done I will work with you to =
create those dependencies.

Vikas said he was going to do this once he finished the first pass of =
the QA schedule.

_____________________________________________
From: Mary Li
Sent: Wednesday, May 23, 2007 3:27 PM
To: Andrew LeFebvre; dl-Cougar
Subject: RE: Minutes from 5/22 Cougar Phase 2 Exit Review


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 =
<file://mightydog/Program%20Management/Cougar/QE/QESchedule/Cougar-QE-Sch=
edule_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
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.=20
22)     Share what are the biggest component costs in COGS as a =
percentage of the total.=20
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.=20
28)     Need to close on finding a QA resource to work with DEV on =
testing of Linux on Bobcat.=20
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.=20
33)     COGS number used in build plan are about 20% too low.  Ops to =
provide numbers to use for each phase.=20
34)     Andy to update build plan (for COGS and requirements from QA and =
Mktg) and send to Frank for review.=20
35)     Ops to provide tooling costs and NRE by phase to Frank for =
review.=20
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_01C79DC8.82EAED42
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: Minutes from 5/22 Cougar Phase 2 Exit =
Review</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3059" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText34741 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>We have to =
discuss :</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>17)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>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 keepi</FONT><FONT face=3DArial size=3D2>ng Cougar =
completely out of the Zonda code line would delay the Cougar FCS by a =
month.&nbsp; Decision made to resolve this in a separate =
meeting.</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3Den-us><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>18)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>In a similar way to how QA documented the entrance criteria for =
SW, they need to document their maturity/config</FONT><FONT face=3DArial =
size=3D2>uration requirements for HW.</FONT></SPAN></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>27)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Need to work out a plan for including an internal Beta test as =
part of the project.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT =
face=3DArial size=3D2>28)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT =
face=3DArial size=3D2>Need to close on finding a QA resource to work =
with DEV on testing of Linux on Bobcat.</FONT></SPAN> </DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Mary Li<BR><B>Sent:</B> Wed =
5/23/2007 5:00 PM<BR><B>To:</B> Tim Gardner; Andrew LeFebvre; =
dl-Cougar<BR><B>Subject:</B> RE: Minutes from 5/22 Cougar Phase 2 Exit =
Review<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial color=3D#0000ff =
size=3D2>Sounds good.</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us> </SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DTahoma =
size=3D2>_____________________________________________<BR></FONT></SPAN><=
SPAN lang=3Den-us><B></B></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><B><SPAN lang=3Den-us><FONT face=3DTahoma =
size=3D2>From:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3DTahoma size=3D2> Tim =
Gardner<BR></FONT></SPAN><SPAN lang=3Den-us><B></B></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><B><SPAN lang=3Den-us><FONT face=3DTahoma =
size=3D2>Sent:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3DTahoma =
size=3D2></FONT> <FONT face=3DTahoma size=3D2>Wednesday, May 23, 2007 =
4:13 PM<BR></FONT></SPAN><SPAN lang=3Den-us><B></B></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><B><SPAN lang=3Den-us><FONT face=3DTahoma =
size=3D2>To:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3DTahoma size=3D2> =
Mary Li; Andrew LeFebvre; dl-Cougar<BR></FONT></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><SPAN lang=3Den-us><B></B></SPAN><B><SPAN =
lang=3Den-us><FONT face=3DTahoma =
size=3D2>Subject:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3DTahoma size=3D2> RE: =
Minutes from 5/22 Cougar Phase 2 Exit Review</FONT></SPAN><SPAN =
lang=3Den-us></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial color=3D#000080 =
size=3D2>Is the plan still to update the integrated schedule with the QA =
schedule so that we can create dependencies</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial color=3D#000080 =
size=3D2>between QA and SW tasks? Once this</FONT><FONT face=3DArial =
color=3D#000080 size=3D2> has been done I will work with you to create =
those dependencies.</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial color=3D#000080 =
size=3D2>Vikas said he was going to do this once he finished the first =
pass of the QA schedule.</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT =
size=3D2>_____________________________________________<BR></FONT></SPAN><=
SPAN lang=3Den-us><B></B></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><B><SPAN lang=3Den-us><FONT =
size=3D2>From:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT size=3D2> Mary =
Li<BR></FONT></SPAN><SPAN lang=3Den-us><B></B></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><B><SPAN lang=3Den-us><FONT =
size=3D2>Sent:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT size=3D2> Wednesday, May =
23, 2007 3:27 PM<BR></FONT></SPAN><SPAN lang=3Den-us><B></B></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><B><SPAN lang=3Den-us><FONT =
size=3D2>To:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT size=3D2> Andrew LeFebvre; =
dl-Cougar<BR></FONT></SPAN><SPAN lang=3Den-us><B></B></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><B><SPAN lang=3Den-us><FONT =
size=3D2>Subject:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT size=3D2> RE: Minutes from =
5/22 Cougar Phase 2 Exit Review</FONT></SPAN><SPAN =
lang=3Den-us></SPAN></P><BR>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>14)&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3DArial size=3D2>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 s</FONT><FONT face=3DArial size=3D2>hip REV3 to =
customers by the 1/18 FCS/GA.&nbsp; This change needs to be incorporated =
into the integrated schedule as well.</FONT></SPAN></P>=0A=
<UL>=0A=
<UL>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial color=3D#0000ff =
size=3D2>[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</FONT><FONT face=3DArial color=3D#0000ff size=3D2> test plan to =
reflect this .</FONT></SPAN></P></UL></UL>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>15)&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3DArial size=3D2>QA =
needs to update their detailed schedule for the Phase 2 [60K ops] =
portion of the project.&nbsp; Right now they are not aligning with the =
mid-June FCS.</FONT></SPAN></P>=0A=
<UL>=0A=
<UL>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial color=3D#0000ff =
size=3D2>[Mary] Just updated the detailed schedule which is available =
at</FONT></SPAN><SPAN lang=3Den-us> </SPAN><A =
href=3D"file://mightydog/Program%20Management/Cougar/QE/QESchedule/Cougar=
-QE-Schedule_v3.mpp"><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us><U><FONT face=3DArial color=3D#0000ff =
size=3D2>\\</FONT><FONT face=3DArial color=3D#0000ff =
size=3D2>mightydog\Program =
Management\Cougar\QE\QESchedule\Cougar-QE-Schedule_v3.mpp</FONT></U></SPA=
N><SPAN lang=3Den-us></SPAN></A><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us><FONT face=3DArial color=3D#0000ff size=3D2>.&nbsp; I =
assume starting date is 04/01/07 for phase2 which may not be true.&nbsp; =
I couldn</FONT><FONT face=3DArial color=3D#0000ff =
size=3D2>&#8217;</FONT><FONT face=3DArial color=3D#0000ff size=3D2>t =
fin</FONT><FONT face=3DArial color=3D#0000ff size=3D2>d definite SW =
deliverable date for QE from Integrated =
schedule.</FONT></SPAN></P><BR></UL></UL>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DTahoma =
size=3D2>_____________________________________________<BR></FONT></SPAN><=
SPAN lang=3Den-us><B></B></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><B><SPAN lang=3Den-us><FONT face=3DTahoma =
size=3D2>From:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3DTahoma size=3D2> =
Andrew LeFebvre<BR></FONT></SPAN><SPAN lang=3Den-us><B></B></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><B><SPAN lang=3Den-us><FONT face=3DTahoma =
size=3D2>Sent:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3DTahoma size=3D2> =
Wednesday, May 23, 2007 11:40 AM<BR></FONT></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><SPAN lang=3Den-us><B></B></SPAN><B><SPAN =
lang=3Den-us><FONT face=3DTahoma size=3D2>To:</FONT></SPAN></B><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT =
face=3DTahoma size=3D2> dl-Executive; dl-eng-ops-staff; dl-Cougar Core =
Team; Kevin Matthews<BR></FONT></SPAN><SPAN =
lang=3Den-us><B></B></SPAN><SPAN lang=3Den-us><B></B></SPAN><B><SPAN =
lang=3Den-us><FONT face=3DTahoma =
size=3D2>Subject:</FONT></SPAN></B><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3DTahoma size=3D2> =
M</FONT><FONT face=3DTahoma size=3D2>inutes from 5/22 Cougar Phase 2 =
Exit Review</FONT></SPAN><SPAN lang=3Den-us></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>All,</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Thanks to =
everyone who participated in yesterday</FONT><FONT face=3DArial =
size=3D2>&#8217;</FONT><FONT face=3DArial size=3D2>s Cougar Planning =
Review (Phase 2 Exit).&nbsp; Unfortunately, the consensus was =
altho</FONT><FONT face=3DArial size=3D2>ugh the team has made good =
progress, we are not quite ready to proceed into the Phase 3A =
(Prototype) stage.</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2></FONT></SPAN>&nbsp;</P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial size=3D2>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>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>16)&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3DArial size=3D2>Tom =
requested there should b</FONT><FONT face=3DArial size=3D2>e a =
&#8220;max memory&#8221; Cougar configuration targeted for customers who =
are willing to pay for very high performance.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>17)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>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 keepi</FONT><FONT face=3DArial size=3D2>ng Cougar =
completely out of the Zonda code line would delay the Cougar FCS by a =
month.&nbsp; Decision made to resolve this in a separate =
meeting.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>18)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>In a similar way to how QA documented the entrance criteria for =
SW, they need to document their maturity/config</FONT><FONT face=3DArial =
size=3D2>uration requirements for HW.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>19)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>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.&nbsp; This allows the entire team to be engaged on =
Cougar, which is needed to</FONT> <FONT face=3DArial size=3D2>meet the =
mid-January Phase 1 [45K ops] FCS/GA.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>20)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Questions were raised about the build plan yield =
assumptions.&nbsp; Brian needs to justify numbers that seem overly =
optimistic.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>21)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Need to understand what prototype parts have gone through DFM =
and what still n</FONT><FONT face=3DArial size=3D2>eeds to be =
completed.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>22)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Share what are the biggest component costs in COGS as a =
percentage of the total.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT =
face=3DArial size=3D2>23)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT =
face=3DArial size=3D2>Discussion about FRU mechanical tolerance =
stackup.&nbsp; Brian believes we are protected by the way the tolerances =
and critical dimensions are called</FONT> <FONT face=3DArial =
size=3D2>out on the drawings.&nbsp; 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.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>24)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Brian commented that in the cluster-in-box conf</FONT><FONT =
face=3DArial size=3D2>iguration the DIMM</FONT><FONT face=3DArial =
size=3D2>&#8217;</FONT><FONT face=3DArial size=3D2>s on the two boards =
will be very close together.&nbsp; Tom had experience in the past of =
DIMM</FONT><FONT face=3DArial size=3D2>&#8217;</FONT><FONT face=3DArial =
size=3D2>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</FONT> <FONT face=3DArial size=3D2>t</FONT><FONT =
face=3DArial size=3D2>his problem.&nbsp; Ops to provide schedule for =
these tests.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>25)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Marketing</FONT><FONT face=3DArial size=3D2>&#8217;</FONT><FONT =
face=3DArial size=3D2>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>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>26)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Caeli asked that DEV be responsible for Beta install and =
customer s</FONT><FONT face=3DArial size=3D2>upport rather than the SE =
and CS assistance documented in the Beta plan.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>27)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Need to work out a plan for including an internal Beta test as =
part of the project.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT =
face=3DArial size=3D2>28)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT =
face=3DArial size=3D2>Need to close on finding a QA resource to work =
with DEV on testing of Linux on Bobcat.</FONT></SPAN> <BR><SPAN =
lang=3Den-us><FONT face=3DArial =
size=3D2>29)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>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.&nbsp; This change needs to be incorporated into the =
in</FONT><FONT face=3DArial size=3D2>t</FONT><FONT face=3DArial =
size=3D2>egrated schedule as well.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>30)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>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>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>31)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>QA needs to update their detailed schedule for the Phase 2 [60K =
ops] portion of the project.&nbsp; Right no</FONT><FONT face=3DArial =
size=3D2>w they are not aligning with the mid-June FCS.</FONT></SPAN></P>=0A=
<P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>32)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Need to explain why the Phase 2 SW DEV work is taking 130 days =
to complete.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>33)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>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=3Den-us><FONT face=3DArial =
size=3D2>34)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Andy to update build</FONT><FONT face=3DArial size=3D2> plan =
(for COGS and requirements from QA and Mktg) and send to Frank for =
review.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>35)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Ops to provide tooling costs and NRE by phase to Frank for =
review.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>36)&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT face=3DArial =
size=3D2>Tom made suggestion to come up with a summary of costs and =
minimizing risk that could be shared with</FONT><FONT face=3DArial =
size=3D2> Bob</FONT><FONT face=3DArial size=3D2>&#8217;</FONT><FONT =
face=3DArial size=3D2>s staff.</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2></FONT></SPAN>&nbsp;</P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>We</FONT><FONT face=3DArial size=3D2>&#8217;</FONT><FONT =
face=3DArial size=3D2>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>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Regards,</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Andy</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN></P></DIV></BODY></HTML>
------_=_NextPart_001_01C79DC8.82EAED42--
