e-com2 Program ---Additional comments V2

Morning UWE-

I received this document from Peter d-Entremont whom you met last week.  I asked him to review with Bill Buholtz (Sales person on the account} the program as it was described to Peter and I last week.  Below please review their findings!

These 2 changes in red comes from bill buholtz.  They are in RED

Tim,

I had a long discussion with Bill today, and we developed a list of questions for Transim:

1. Can they please develop budgetary pricing with estimates of the three modules we discussed as well as an estimate for only modules a and b or c


   a. populating a rack with various switches, panels, etc.
   b. laying out several racks in a room
   c. laying out cable trays on top of the rack in room drawing

2. What can we expect maintenance costs to be? 

   a. what is their routine maintenance contract costs (%)
   b. can they make a management portal that allows someone skilled in working with web-sites to add and remove parts from the system? Note this is not intended for a novice and can include some amount of skill. Assume that someone like Bill Buholtz or Gorden Mack is doing this maintenance.


3. What would they expect the server requirements to be, assuming the following estimated usage:
   a. As many as 10,000 total users with data stored on the system
   b. As many as 200 simultaneous users configuring systems at any one point in time


4. Can they point us to a web-site that shows us something they have done that is in use that is similar to what we are discussing?
   a. Especially any tools that have drag & drop capability of adding components to a design


5. We have assumed they would deliver us code that can be placed on our own server, is this correct?

6.We have assumed that e-com2 would provide the look & feel to the system - we will make our own "skin" and they will provide the hooks for us to do this, is this a good assumption?


7.  Have they ever done a software escrow to ensure we will have access to the code if anything ever happens to their ability to support us in the future?

8. Note we expect at launch to have on the order of 1,000 parts that will need to in the system, most likely in 10 to 20 different categories. 

I would use 2000 parts and there may be as many as 12 attributes associated with each  part.

genie program

I was of the opinion that Nana Flynn and
Elenor as members of the noonan clan at the cronin clan blog!

The electronic components industry must

Economic Issues

• Price of fuel – The traditional Outside Sales person has to alter their sales strategy---More in-house sales tools, with fewer visits to the customer
• Recession – The cost of doing business the Traditional way will be 29to39% less cost effective ( see link to

Outsource their Virtual e-Catalog

• Global Marketplace – “The World is Flat.
• 4^th Sales Channel – the internet – The % B2B sales using the Internet is increasing as a share-of-sales yach year by 11%...Therefore, lower cost of sales, and 10% bottom line profit
• Sell franchised products to Global Customers “Internet Savvy”
• “Software as a Solution” will allow the customer to stick to their Core Competency, which is selling components and have fetch Solutions to provide the

   "We are excited about this first order and it underscores what we've

been hearing from our customers around the world -- the Geared Turbofan

engine brings the game-changing improvements in fuel burn, engine noise,

environmental emissions and operating costs that airlines are demanding,"

said Todd Kallman, president, Pratt & Whitney Commercial Engines. "Customer

reaction has been extremely positive. We currently have several proposals

out with various airlines and we are confident that there will be

additional orders throughout this year."

Midmarket high-tech manufacturers face intense competition globally - and that means it is critical to maximize offshoring and outsourcing tactics to cut costs, increase efficiency, and maintain competitive advantage.

Component Databases

http://www.datasheetcatalog.com/other_manufacturer.html