From PICLIST@MITVMA.MIT.EDU Thu Nov 14 02:56:13 2002 Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-7.13) id A14DEBA0080; Thu, 14 Nov 2002 02:56:13 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <10.007D3B58@cherry.ease.lsoft.com>; Thu, 14 Nov 2002 5:42:22 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 1161 for PICLIST@MITVMA.MIT.EDU; Thu, 14 Nov 2002 05:20:27 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 3773; Thu, 14 Nov 2002 05:20:00 -0500 Received: from mailout6-0.nyroc.rr.com [24.92.226.125] by mitvma.mit.edu (IBM VM SMTP Level 320) via TCP with ESMTP ; Thu, 14 Nov 2002 05:19:59 EST X-Comment: mitvma.mit.edu: Mail was sent by mailout6-0.nyroc.rr.com Received: from scientifx6ajal (roc-66-24-96-28.rochester.rr.com [66.24.96.28]) by mailout6-0.nyroc.rr.com (8.11.6/RoadRunner 1.20) with SMTP id gAEAK0k01061 for ; Thu, 14 Nov 2002 05:20:00 -0500 (EST) References: <3DD33141.52D59C2A@3mtmp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: <00a801c28bc8$0689cf10$6400a8c0@scientifx6ajal> Date: Thu, 14 Nov 2002 05:24:32 -0500 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Rich Subject: Re: Standard contract for work? To: PICLIST@MITVMA.MIT.EDU X-RCPT-TO: Status: R X-UIDL: 277600430 X-Evolution-Source: pop://mailinglist%40farcite.net@mail.farcite.net/ X-Evolution: 00000697-0000 Josh: Usually, a document called a Bid Specification Proposal is generated by the client. But if the client does not write a Bid Spec, you must in order to protect yourself. The Bid Spec must contain such things as: 1. The environment in which the device will operate properly, i.e., dust, humidity, temperature range, vibration, light, radiation, etc. 2 The interface requirements, the stability (including short term and long term drift), accuracy with respect to full scale or measured value, repeatability, switching speed, etc. 3. The terms and conditions of the Agreement, i.e., price, delivery, milestones, debugging, warranty, payment schedule, and so on. Usually, you write a standardized document that is sometimes referred to as the "Boiler Plate" and you attach those things that are unique to the project under consideration. I hope this helps you, Rich ----- Original Message ----- From: "Josh Koffman" To: Sent: Thursday, November 14, 2002 12:14 AM Subject: [OT]: Standard contract for work? > So, here am I faced with the prospect of coming up with some sort of > contract for some work I will be doing. Does anyone here have a standard > type of contract they are willing to share? Or, at least some sort of > outline of things that should be covered? > > Any discussion would be appreciated. I figure this may also be something > good to have on piclist.com or at least in the archives (there is some > discussion, but no templates or lists) for the begining contracter. > > Thanks, > Josh > -- > A common mistake that people make when trying to design something > completely foolproof is to underestimate the ingenuity of complete > fools. > -Douglas Adams > > -- > http://www.piclist.com hint: PICList Posts must start with ONE topic: > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads > > -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics