Seeing as I am writing the Service/Repair module right now, I guess I can answer you.
   
  The new Service/Repair module will be part of the standard ISTECH updates, not an Add-on. It will start off by looking very much like SOA does now. You can enter a S/R order, have notes enter items/ kits/ F&O etc.. We also allow for a new Inventory type "S" Service/Repair type. This would be used for servicing/repairing part numbers that are not yours..
i.e. set up a part "SR100" type "S" description "Cleaning"
When a SR order saves a "S" type line it will prompt the user for Make, Model, and Serial Number(s).   All S/R orders will be kept at a new/seperate location for inventory values.
 
 Once a SR is created then it can be processed/converted to a WO much like a SO can convert to a WO.  Then upon completion of the WO, it will generate an Invoice at whatever price is needed.
 
 This is a quick overview of what is being done, so if users have any suggestions, now is the time..
 

Quote from NovaZyg   on 06/30/05 at 07:13:27:

 
Having an SO type C for "CONSIGNMENT" Would be awsome. We have consignment inventory all over the country. Having a separate order type and inventory account would be great. That way you would not see it on the open order list. We started using inventory locations for awhile. You don't want to see my lisy of locations.
 
Thanks,
 
John

"Then upon completion of the WO, it will generate an Invoice at whatever price is needed. "
 
Just some basic questions:
 
Can the S/R Orders also be released through SO-E and invoiced and shipped as normal?  
 
Are the part type "S" items similar to part type "N" in that they are not stocked?  Or more like "A"? "N"-style might be more useful.  Can they have a BOM?  For instance SR100 Cleaning might have 15 minutes of labor and 15 minutes of overhead and MEK solvent.  Allowing it to have a BOM would properly allocate costs.
 
It seems also like the S/R module would be a great fit with the RMA module, and returns in general.  We are very excited about it here.

Can the S/R Orders also be released through SO-E and invoiced and shipped as normal?  
 
No, we will be developing a new S/R program that will do the enter finished production, Assign a price (could be labor and parts, could be parts only or labor only, could be $0.00 due to warrenty, cold be a % of the selling price etc...)and Invoice/Post.
 
Our thinking is that "S" type parts will be like "F" type parts,  they can have BOMs. and Qty's but those Qty's will not be mixed with Real Inventory. That is why "S" parts will only be allowed in the S/R location and this location will not be part of the regular inventory. So it will not be part of the inventory valuation, but can be tracked seperatly for insurance purposes.
 

 Where I work, we don't do repairs without issuing a  quote.  I've had instances in the past where the customer had a coniption(?) fit over the estimate and junked the unit.  Also, many of my customers won't issue a PO without a written estimate first.  One thing to add is that we reserve the right to charge a minimum labor fee to look at the equipment.  
  I am still a little puzzled about the value of having the S type parts.  When we repair stuff, we pull parts out of our inventory.  We assign prices to parts that are used for repairs (adding as needed).  
  I would thing that some sort of data file to keep track of what equipment was in house for repair, and its status would be handy.  Also maybe a archival log so that you could get a service/repair history of a unit or customer.
  Ya need a beta-tester?

Lynn,
 
  I undertand better about the S type parts.  We use F&O for our finished goods... I see problems with this.   I guess we could also use S type part numbers for items that we used to make, but don't have the finished goods part numbers in the system anymore.
 

I can also see how for companies that use Advanced Manufacturing where they may want to keep track of labor and resources that are being committed for repairs rather than normal production.  In some company's, your repair section is pretty self-contained, in others, some repair has to be sent out to the factory floor (for example, replacement of a surface-mount IC may be done at the one station that has the equipment, which may not be in the repair section), or to an outside vendor.  
I would think that you would want to be able to differentiate between warranty and customer-paid for service or repair.
My main experience with repair is from my time in the military, where I was in maintenance units.  One thing that might also be useful would be to assign some sort of status code to a repair (either the S/O or W/O).  If your company does a lot of repairs, or this is its primary business, then you would want to run reports that tell you what's up with an item.  For example,  an item may go from w/shop, to w/customer authorization for repair, to w/parts (if required) to in shop, to Q/C, and finally to shipping.
Of course, all this could turn a really good, simple module in to a pretty complicated mess.