FRDCSA | internal codebases | SHOPS

[Project image]

Architecture Diagram: GIF

Jump to: Project Description | Parent Description | Capabilities

Project Description

shops: Squirrel Hill Point of Sale

The shops system provides several features that are tailored to the small retailer who intends to survive on the basis of location, against larger chains.

The point is to provide a relative improvement in ordering capabilities and information management on the basis of free software for the smaller guy - because this will still further increase the problem solving capabilities of communities.

By utilizing the explosive capabilities of free software (derived from individuals, industry and academia alike), we can effectively represent the interests of small business.

The key feature of our approach is integration via Debian GNU/Linux of existing software to perform important capabilities. In addition to shops, we are building a live linux distribution remastered from the Knoppix genre, called Shoppix, which includes shops, as well as a coherent installation containing many other free software systems which we will use to severely augment the shops system, which we add as part of our packaging effort.

The main features of the shops system are:

Version 0.9.5 includes the following features:

  • Automatic inventory reordering
    • Based on projected sales, current inventory
    • Maximize expected profit and customer satisfaction
    • Choose the cheapest supplier or the quickest one
  • Product locator (useful for rare items like surplus)
  • Tracking of all sales
    • Support for dynamic pricing to determine appropriate regional pricing
    • Ability to price differently to different demographics
    • Special handling of accounts
    • Automatic generation of window displays
  • Tracking of all requests
    • Ability to put items on order and contact customer when they arrive.
    • Tracking of product and service requests.
  • Tracking of all jobs
    • Barcodes for every job item
    • Ability to choose services from unlimited number of subcontractors
    • Detailed understand of pricing options
  • Agenda based employee management
    • Direct employee to perform certain operations well in advance of their deadline
    • Sensitive understanding of deadline options
    • Sophisticated time management planning, based on expected profit and customer satisfaction.

Planned for Squirrel Hill POS System, Release 1.0

    • Integration with agenda system - cost/benefit analysis
    • Sophisticated Supplier Planning and Integration
    • Web based tracking using CSIMS/Ariadne/XWrapElite/etc
    • Ecommerce/Liquidation/Ebay asset aquisition
    • Knowledge based inventory management
    • Ontological categorization of inventory using OpenCyc
    • Ability to select inventory by formula
    • Ability to group inventory, and edit inventory KBS
    • Learning of product equivalence classes (thanks to Gopi Flaherty)
    • Detect lemons - i.e. defective products
    • Object Oriented Management of Inventory classes using Perl OO
    • Allow poly of treatment of inventory
    • Whether internal use, repairs, returns, or stock.
    • Image based inventory management
    • Storage of product photographs
    • Displayable on Kiosks, e-commerce websites, Ebay and window displays
    • OCR of product information on labels.
    • Question Answering (NLP) applied to product labels and defaulting to WWW.
    • Wavelet-based image/product retrieval
    • similar products/categories.
    • Algebraicly closed operations
    • For dealing with inventory location
    • For dealing with inventory uncertainty
    • Customer face detection and recognition using OpenCV
    • Dynamic pricing
    • Sensitive mechanisms for pricing based on facial recognition and datamining of inventory KBS.
    • Reordering
    • Classes
    • Subcontractor Bulletin
    • Business Process Intelligent Tutoring Systems to Retain and Train Employees
    • Store Operations manager using PDDL2.2
    • Expert system representation of organizational tasks using Jess, Clips, OpenCyc or equivalent.
    • VSAM


  • Sorcerer, -n shops
  • Sorcerer, -a shops
  • There is a lot of interest relatively speaking in shops.sf.net, we have to update that so people know where the current version is.
  • Notice similarities between shops and setanta
  • In order to account for throwing things out for gourmet, normal-forms, shops, etc, should have a barcode on the trash and simply move the item to the trash location.
  • Perhaps invent.blend could be made into an applet that users could download to display inventory from shops for online browsing.
  • Obviously shops should have a web based method of accessing the contents, for online customers.
  • We could use c4.5 to determine customer purchase behaviour for shops
  • shops should use ARMiner to mine product association rules.
  • Whereas shops was the tough product with Al, gourmet is the tough product with Mike.
  • Dreamt that Al was in town at a store of his. And there were two ladies singing in the store at closing time. We briefly discussed a few things. Al really showed his intelligence in this dream executing all of his tasks perfectly. I told him over IM in the store that I had ported shops. His brother could use it. I said it didn't have a gui.
  • Secondly we can use UML tools to design IM/broker/shops to be a general purpose system. The IM features should be OO and independent of shops, which is simply the pricing mechanism, along with broker. The idea is of inventory/goods Input/Output. I.e. buying and selling are featured more symmetrically within the system. Only later are front ends thrown on the thing.
  • The notion of modelling people's interests with shops is funny - model interests and tasks as a sell.
  • I was thinking maybe mstevens would be interested in a deal where we all sit down, one day out of each week, and simply finish a system. For instance, we could sit down and finish shops.
  • We can start with a manual todo list - the shops agenda system. That way, I can put deadlines on certain tasks, also assert preconditions in the planner for these tasks. Cool
  • There is a simple way to plans/ parts lists and integration to broker/shops for our construction projects and that is simply like ingrediants.
  • shops should have a command line interface, called shops
  • shops IR light.
  • Here are some of the things we need to do next: fix the way pse craps out all the time, get Clairvoyance working and with some basic document management systems, including for instance authorized reports to ensure back to me that various people are learning various things (based on testing), find some way to get those recipes normalized, get shops up and running and taking inventory of everything I have, add this information to verber, get MDR (minimum detection route) planning operational, get new tagsets for AWB/Predator working, fix problem with script determining perl dependencies, make packages of my systems and upload, fix mini-dinstall problem, write tutorial on agentification, agentify or otherwise get command line bugzilla working, fix up manager with sleep learning capabilities, create a sample course for clairvoyance, and run backup. You're such a lazy guy, you know that?
  • Add mysql password support to shops
  • Two features need to be added. The first is to #$Clairvoyance so that it can cash URL and read webpages to the user, monitoring of courese what the user has been reading. The seond system that needs to be worked on is that #$broker ought to be able to look on the classified adds in newsgroups etc, for instance, "shops, soundcard", should return the cheapest sound card infomration.
  • We should add this kind of thing to unilang: shops, baseball cap.
  • shops could use the recommender system.
  • The shops purchasing system should have the ability to basically do this: find these items, have them approved by this person, have them billed to this account and have them shipped to this location. Report any anamologies.
  • shops - Business Intelligence for the Masses
  • We can use some of those graph theoretic notions of centrality from the CASOS papers in order to make determination of usage. Really, I should spend alot of today either reading the Schaums Software Engineering, or planning what to do (as long as it includes Schaums). But knowing myself, I will not, prefering to program radar and predator. Which is in a way, the most intelligent choice possible. I do have to definitely plan for when work is to return on shops. Let's say to be stupid that I will do it after sending out AIX 1.0.
  • Anyhow I must get shops done.
  • I should get shops in a workable condition.
  • shops is the key to many of our problems.
  • We shall go ahead then and declare a jihad, that we have to finish gourmet, and make a package, within 3 days. Then on to shops after a brief break.
  • should get a minimal shops system written and deployed very soon. it just logs sales, with a nice GUI, and prints receipts, etc. Should only do basic things, be very forgiving, and then we should scan in their entire inventory. get this all planned out. deploy it on a given day.
  • some things to work on: come up with a complete plan for the completion and deployment of shops at Al's store.
  • I'm making shops be an asynchronous system suitable for GUI programming, for example, using Event.pm
  • sql-ledger 4 shops
  • tell Al that part of the thinking in writing my system first is by the time that I run into doing shops, I will have experimented and tried out several methods of OO Programming. shops is a much more serious system than any of the ones I have written, although it can use them for its development I am sure.
  • at some point must initiate work on getting shops complete.
  • Basic plan for now is to use the shops system to finish the telnet communication part of unilang. Then go about trying to get modules installed on our system and reading that manuals for packages that apply to what we are doing. Then go ahead and try to get that part of the system done that sends messages back and forth from pse.
  • I think I should get shops done and then work solely on pse, with the others naturally being developed.
  • Here is my plan, get a working version of shops, with remote administration, figure out how they will use it, write the manual. Then work solely on AI for a while.
  • Finish shops.
  • The main purpose of shops is ordering.
  • After installing the shops system, you the next step is to begin scanning When an item sells, .
  • There are several imporatntc considerations in seeting up shops to run your store. The first is to Teh first consideration is installation of the computer system runing SHPS . If your To do this, you need to insert the CD into a system. WARNING: YOU WILL LOSE all DATA ON THE SYSTEM. shops REFORMATS YOUR SSTEM. Only use a PC thatyou don't need any more data an.
  • Welcome the to the shops Point of Sale system. This manual will explain how to use shops This manual will walk you through making your store run off of the shops system.
  • shops User Manual.
  • We need to get shops squared away.
  • The real priority here is to get shops ready, and the other store finished. This is because, as we have seen in the past, without that stable abiilty, things are less and less likely.
  • I need to get shops manual complete, as is well known.
  • Write them and see whether they want to integrate with shops.
  • Then work on writing the shops manual and getting everything into place including working dynamic IP address with dynamic POS stuff.
  • Today I got shops done.

This page is part of the FWeb package.
Last updated Sat Oct 26 16:55:00 EDT 2019 .