26 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHDeposit Date?
Leading reported evidence
Fill later than later orders
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
Dealer also talked about how many early orders were filled later than later orders.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
The code that follows CMPPRD is PRDLST (factory last check point) and then IMPINV (complete and invoice) this is when the dealer probably wants to get things really moving, finally after that we will see ONVESL!
Leading evidence: 'Fill later than later orders' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check point)' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
The code that follows CMPPRD is PRDLST (factory last check point) and then IMPINV (complete and invoice) this is when the dealer probably wants to get things really moving, finally after that we will see ONVESL!
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Check point)
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
The code that follows CMPPRD is PRDLST (factory last check point) and then IMPINV (complete and invoice) this is when the dealer probably wants to get things really moving, finally after that we will see ONVESL!
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
26 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Planet-9: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T150451Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Not sure if this has been posted before, but just wanted to see when everyone placed their deposit. I placed mine the first week of January and was second on the list at my dealership. I tried to make the deposit in November but the dealership said the wouldnt be taking deposits for it yet, since the car had not been officially anounced.
Don't laugh........9/09/2004 is when my dealer tookmy deposit. Tried even before then but they wouldn't take it. Deposit receipt still says 'Boxster Coupe'.......LOL, little did I know.
9/9/04 is going to be tough to beat. Im surprised the dealership let you place it that early since the dealerships, at least here in Houston, told me they wouldnt take them yet.
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt">The mysteries of time of order vs. construction. I wonder if changing the order delays it any. I did and still have no VIN.[/quote]
My first attempt was 05/2004......they wouldn't take it then. Kept asking each month. I think my salesman finally took the deposit to get rid of me for a while. At that time I really didn't know what the demand was going to be, but one thing for sure I wanted to be one of the first.
Last update I got was that mine was in production and should be done any day now. I had a Nov. build date, but I think mine got pushed back a bit due to me changing and adding some interior pieces painted exterior color. It should appear right around launch date if all goes as planned.....fine by me.
Yeah, I'm not sure if I should feel slighted or not. There are people at my dealer who ordered after me that are getting their cars before me. mmmm...
In any case, I have good news for those people. I was told they won't hold the cars, so I think a few of us in So. Cal will have them for Christmas.
Chris,
Atlas says his got pushed back from a Nov. build to Dec. Mine got pushed ahead from a Dec. build to a November completion. Don't know why, and not complaining.
Russ
Deposit? My dealer didn't require a deposit from me. I could have taken a November build slot but wanted a December build for other reasons so 2 people at my dealer will get a car before me, actually 1 will, the other just backed out, that's the black car I need to get specs on for everyone.
Deposit date was 6/18/05.
Dealer told me today that the last vessel to depart for US was Nov. 30. Since my completion date was on Nov.30, I just missed the boat, and now have to wait for the next boat. Status today shows still waiting in Europe. Dealer had no information on when the next vessel would sail for US, but is optimistic that car will arrive in time for 1/14 release date.
Dealer also talked about how many early orders were filled later than later orders. He is as much in the dark as to how this turned out as the rest of us. Only left with speculation to go on.
Edited by - kmns on 12/12/2005 4:39:26 PM
Russ,
He told me that my code was still CMPPRD also. There is one code between this one and the on the vessel code, but he said that there is only one day delay between those Codes once the car is ready to board. Lets hope one of the ships gets back over there soon and loads up.
kmns,
The code that follows CMPPRD is PRDLST (factory last check point) and then IMPINV (complete and invoice) this is when the dealer probably wants to get things really moving, finally after that we will see ONVESL!
Russ
Russ
Even though I am frustrated that we just missed the last boat, I am remaining optimistic for delivery by the official release date of Jan.14. The way I see it, if the cars get on a vessel within the next 10 days, and it would seem reasonable that a boat would be back to get more by then, there would be sufficient time for the cars to travel to their destinations over a 3 week period, even with the Holidays.
kmns,
Yes I will remain optimistic as well! And while I am doing so I will be bugging my dealer daily to find out if that code has changed to the next level.
Aloha Russ
If you want to drive yourself nuts (or more so than now) you can check out the companies web sites that transport Porsches. With a bit of web searching you can probably come up with the vessel schedules.
Santa Fe,
Yes, sign me up as somone that wants to drive themselves nuts. Any further information on tracking down the companies web sites that transport Porsches will be appreciated. Be assured, there are no limits to my obsession./fckeditor/editor/images/smiley/MWPX/help.gif
Hi tokz,
You will not get a VIN until the car is actually built or completed, so that would be most likely in January sometime. I had a November build date and mine was completed Dec.1st. That same day my dealer called me with my VIN.
Aloha Russ
This is a source reference. Confirm exact model applicability in the original material.
