|
|
|
Dynaprice Venues Subsystems for separate business units or functions |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Dynaprice data services are based on networking together separate business units or functions. Each business unit or function receives a dedicated set of computer programs and database access configured and customized to its particular needs. These programs are implemented in a controlled-access website called its "operating venue" -- where it does its business.  Each venue can be given selected capabilities to manage listings (inventories and public postings of wanteds and offers), people (staff, customers and sales prospects), and a "haggling" style of dealmaking between identified people with regard to specific listings. This all rests on top of administrative functions for business operations, including such things as reporting and archiving.Individual venues can be configured and linked for data sharing with great flexibility to meet the needs of any organization. The descriptions of Dynaprice Products include sample illustrations of linkages among venues configured in the ways shown below. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Venue Configurations |
|
Operating Characteristics | |||||||||||||||||||||||
| |||||||||||||||||||||||
|
Access Control Options for controlling who can access a venue |
|
Every venue has a public web page visible, but not necessarily publicized, on the web. The content of that page is fully custom to the owner of the venue. Access to information and user facilities behind the public home page is controlled by software on the Dynaprice server. There are three ways access to a venue is controlled:
|
||||||||||||||||||||
| class="notebb">top | |||||||||||||||||||||||
| |||||||||||||||||||||||
| |||||||||||||||||||||||
|
Source of Listings Defines the venue(s) from which listings are displayed |
|
Each venue displays a controlled set of offer and wanted listings. Each venue will display listings posted within itself, and may post listings from other venues. There are three ways of specifying where the displayed listings come from:
|
||||||||||||||||||||
| class="notebb">top | |||||||||||||||||||||||
| |||||||||||||||||||||||
| |||||||||||||||||||||||
|
Visibility Level Controls which venues can display which items and, for those items, what descriptive data |
|
There are ten "levels" of visibility provided for in Dynaprice data services, ranging from 0 (fully private) to 9 (fully public). Each listing item, data field, and venue is assigned a visibility level. An item itself is visible only in venues assigned a visibility level UP TO the level of the item. The same holds true for individual descriptive data fields assigned to a product class or a company inventory record. The ten levels are:
These levels offer those entering inventory items the flexibility to choose where each item is seen or to set up time-phased expansion of item visibility up a corporate hierarchy, to membership groups it subscribes to, and to the public at large. A Corporate example: Several divisions each have several departments and wish to seek redeployment of unused assets first within the department, then within the division, then company-wide, and finally as an open sale to the public. A Dynaprice company client may specify inventory venues for each department and build a hierarchy of department, division and company-wide redeployment venues (with access control only to company employees). That company can implement rules that items unclaimed for internal redeployment at a lower level after (say) 28 days are then released to the next higher level of visibility. A Trade Association example: Members post listings in their Inventory Venues, then select a release date for each item on which it becomes visible to all other members at an Association "Group" venue. Group venues can be ranked 1-3 for differentiation among levels of visibility among them, or Group Level 1 may be reserved to display certain "Item Data" to Group Administrators that is not shown to Group Members at Levels 2 and 3. |
||||||||||||||||||||
| class="notebb">top | |||||||||||||||||||||||
| |||||||||||||||||||||||
| |||||||||||||||||||||||
|
Public Posting Privileges Settings that determine whether and what kind of listings may be posted |
|
Listings may be offers to sell or wanteds for purchase (or, where used, auctions). Clients using Dynaprice for their inventory management generally want the ability to post all kinds of listings at inventory venues. Clients operating public surplus sales or market portal venues may or may not want registered members from outside their organization (the public) to post listings at such venues. The DynaSpecs system for user-controlled venue design contains a "doPostings" parameter that can be set in one of four ways to implement the desires of the venue owner:
Venues with limited posting privileges will still show both offers and wanteds from the "Source" (usually inventory) venues they display. | ||||||||||||||||||||
| class="notebb">top | |||||||||||||||||||||||
| |||||||||||||||||||||||
