DATA CONVERSION:
For those clients that have existing content avaialble in another type of database, we are either able to make direct use of existing content, or through darta maniulation techniques, convert the data into acceptable forms for our needs. This approach will substantially reduce requirements for data entry.
SOFTWARE TOOLS:
The tools we utilize will vary from simpleExcel Spreadsheets through subantial custom designed database tools, depending upon the number of fields needed for the project at hand.
In most cases, we use FileMaker Pro as our desktop database tool to gather, collate and manipulate comtent into desired formats. The ease of use combined with extensive capabilities make FileMaker an attractive tool. We have utilized FileMaker softwares to gather and maintain comntent for bopth factories and distributors with grteate succes and minimal costs.
DATA ENTRY PROCESS:
As a manufacturer or distributor of products, you may have multiple product categories with varying levels of data required for proper presentation on your site.. For demonstration purposes, we will use three "documentation" levels with no limitatiojn on product categories. The docmuentation levels we will use are:
- Flagship Products - need as much content as possible too market your products effectiovely on the web and educate potential buyers as to the applications, features, benefits and specifications of your product. The mmore content we have, the better in terms of making the sale and generating page ramnking on all the serach engines
- Secondary Products - These products are important, but need not be dopcumented to the same extent as flagship productsd as they are either complimentary top the Flagship Producrts or will never be a primary source for profits for the company.
- Ancillary Products - shuld be listed but wvery little content, at least in html format, available on the web. This assumes that Search Engine Optimizatuon for these products will never be required.
Our first task would be to work with your Product Marketing Managers to deteremine product categories and the documenation level we should pursue for each family of products. With this input, we can now create a simple database tool to facilitate data entry processes.
As am example, we'll use the product category of power supplies in comnimnation with the three documentation levels listed above. the database fileds required to be completed could vary as follows:
Flagship Products:
|
Description:
|
Input Specs Input Voktage Frequency Inrush Current Input Current Leakage Current Input Protection Harrmonics |
Output Specs | ||
Input Specs: Output Specs Protection Miscellaneous
Input Voltage Setpoint Accuracy Over Current Status & Control
Frequency Adjustnent Range Over Voltage Safety Standards
Inrush Curent Line Regulation Short Circuit Emissions
Input Current Load Regulation Over Temperature
Leakage Current Ripple / Noise Reverse Polarity
Reflected Ripple Transient Response
Harmonics Recovery
Turn-On Tim
Overshoot / Undershoot
Model Numbers and their related Output Voltage / Current Ratings
SECONDARY PRODUCTS:
Features
Dimensions
Input Voltage
Output Adj Range
Regulation (Line / Load / Temp)
Safety Standards
Emission Standards
Model Numbers and related Output Voltage / Current Ratings
ANCILLARY PRODUCTS:
Generic Description
Model Numbers and related Output Voltage / Current Ratings
We create the database and enetry all the product family names with their matching documentation level, allowing us to utilize low-cost data entry resources anywhere arund the globe. Additionally, we can pre-write or provide drop down selection for a large majority of text found in the fields to reduce keystrokes, as an example, we could provid the following options for Flaghsip Power Supplies / Input Voltage:
* Universal AC Input Range (85-264 VAC)
* Universal AC Input Range (90-264 VAC)
* Universal AC Input Range (110/230 VAC)
* Auto Ranging AC Input (90-132 / 180-264 VAC)
The user could select the appropriate value from a drop down list in one click, saving dozens of keystrokes. Multiply this by the number of fields and this approach will save massive amounts of keystrokes while reducing errors and improving consistency of data.
