Would love to save $$$ with OSS, but the software I need (robust, full-featured POS system) is non-existent. Bummer.
I was looking into this in the past and I came across OpenBravo (http://www.openbravo.com). They have two main components: ERP and a POS. They appear to have been designed to integrate.
I've never personally deployed this, but they offer the standard "commercial support for OSS product" model.
From my own light exploration, they appear to be pretty flexible applications. Might be helpful to your business especially if you are looking for front-end/back-end integration between internal business logistics/inventory and the front-line PoS systems.
There are a few caveats, as with any system, but maybe they're worth a look if you're seriously interested. Actually, I'd like to hear how you make out with that as I've been looking into its application elsewhere.
As for almost any kind of implementation, OSS or otherwise, it's important to make sure you've got your business requirements down. Then find a solution that works for your business needs - not the other way around. (But I'm sure everyone here already knows that and doesn't fall for the old 'gadget/feature' trap.... Right?;) )
Anyhow, I'm rambling now. Let me wrap up:
* OpenBravo's one option, I'm sure there are more.
* It will be rare that an OSS or commercial product will be perfect 'out of the box'. You may need devel work done, but YMMV.
* If you don't want to do/commission any devel to meet your needs, you will likely be disappointed by the OSS world. Most OSS projects I've used are best-effort unless they're commercially backed. It wouldn't be fair to you or the projects to bring unrealistic expectations to the eval table.
* Even though I'm not a devel, I don't think OSS simply exists for others to party w/o sharing some of the cake. If it works, feel free to contribute in some manner. (ie. paid support, code, donations, feedback (not whining), even 'championship'/promotion.)
My company tends to stick with paid support and we will do testimonials where appropriate. I tend to do advocacy (championing/promotion) by recommending what I believe the best tool is for the job, OSS or otherwise. That way people know what to expect and what its limitations are and what recourse they have to get assistance.
* Despite what I've heard about people's understanding of OSS, I don't think the OSS community planned OSS to be "free" as in "free ride." (Not to imply that that this is what you're looking for.)
* OSS is not a magic bullet for saving money. Every solution has a cost and that cost is sometimes not quantifiable in dollars and cents.
* Lastly, I'm not associated w/ OpenBravo or any other OSS/commercial product. Just my 2,3 and 4 bits.
"That damage is in the past, stop it from happening anymore in the future."
I don't think that it's as simple as the above statement. Sure, the most visible damage would have happened initially, but the thing is that there are 'rolling' reprecussions that ripple down the time line as affected companies try to recover from the damage done.
For instance: A small organization that was working with a consultancy is considering Linux and a series of service agreements. With all the fear-mongering happening due to SCO's claims, the smaller organization is scared away from Linux and decides to stick with a vanilla Microsoft business environment. What happens?
The organization takes a substancial financial hit to pay for the usual Windows license agreements (OS, applications, etc.)
The consultancy they're dealing with is out of luck.
Open Source projects aren't given their fair chance.
If this happens too often, the consultancy could face more lost contracts, etc, etc.
As for preventing it from happening in the future, I completely agree. While some may claim that it infringes on their rights to restrict business practices, there are limits. I've noticed, here in North America, companies have too much freedom to do pretty much whatever they want, whenever they want, to whomever they want, for almost whatever reason. I'm sure many (if not most) of you share the same sentiments.
Wow - Having bought a Dell some years ago, I was quite pleased w/ their hardware and support. As such, I've always recommended their laptops though now I guess I'll have to give my recommendations more thought.
While I do recall the 'You agree to the EULA if you open the package' issue, but I don't remember having such hassles.
My feeling is that it might make a bit of difference if more people did what RobertB did - Call Dell and ask for a real explanation. Considering you've just made a 'sizable' purchase, that's the least they could do.
Does anyone know how this situation is handled in a larger organization where there would be hundreds of these 'mystery meat' EULAs that need to be 'agreed' to? It's probably safe to bet that most of the time admins just simply 'agree' to the EULA so they can get on with their work. Capitalizing on that bet it can most likely be said that a close examination of the EULA rarely happens and that they're rarely re-visited to check for changes since they were last reviewed.
To some it would seems like an extreme comparison, but it's almost like they've got your $xxxx investment for hostage and they're demanding a blank cheque so you can actually use it.
Now that I've read more and more about EULA 'landmines' I'm definately going to pay more attention to them. Luckily, nowadays, most of the EULAs I read are GNU or BSD in nature. (Yay!)
In any case, I'll admit - it would pain me to have to return the device, but principle is principle.
Actually, that's basically correct at its most rudimentary level. The difference is that Voice over IP (VoIP) calls are typically full-duplex now a days. This means that you can talk [send] and listen [recieve] at the same time like on a normal phone.
Before, back in the old my old 'BBSing with my 14.4 dial-up' days VoIP calls were very basic with very poor call quality. (They were also half-duplex much like talking on a walkie-talkie - you talk, then stop sending so they can reply.)
Anyhow, VoIP has definately moved along and large telco carriers are using it in their infrastructures to squeeze more value out of their existing network connectivity. My understanding is that if you're using Telus as you phone provider, chances are that at some point (especially if long distance) your call actually passes through some VoIP call legs.)
I always am amused (and at the same time somewhat disgusted) by this kind of elitist reply that seems to plague Slashdot.
Of course, I understand that we're all busy people with our own busy things to do so people don't have time to make some sort of constructive response. Then one gets to thinking: "If everyone's too busy or important to reply, why do they have time to write a reply that isn't constructive and actually seems to be more of a drag on the 'community' as a whole?"
Not too busy to take the time to point out how superiorior and resourceful they are to the 'n00bs', I guess.:\
People will go out of their ways to berate a perfectly logical question instead of answer 'yes' or 'no' (Which would be a simple reply to the first part of his question.)
Anyhow, I'd best stop for now. I've had my 2 bits and I'm not interested in starting a flame war. (I'm a really 'busy' person too! hehe Also, I'm beginning to think that I'm beginning to look like I'm getting a little hypocritical myself.)
Here are a few truths about 802.11b gear (and a couple of tips):
1) 11mbit/sec actually turns into about 5mbit/sec because of error correction. (if I remember correctly, the 802.11b standard does errorchecking in a manner where it sends 12 bits and half of that is check sum.)
2) The top speed of the wireless wan is affected by the number of people on it. Just because each client connects to the AP at 11mbit/sec, it doesn't mean that the 11mbit will be guaranteed speeds.
3) you'll most likely require more than a 'couple' of access points to achieve building-wide coverage. Even the number of people in the facility that you're trying to cover affects the cell coverage size. (water absorbs and reflects RF - make sure you keep that in mind if you have plenty of foliage in and around the buildings.)
4) load-balancing is possible, but I've only seen it with the higher-end gear (ie. ciscos, etc.) That'll help with multiple people.
5) RF is prone to SERIOUS interference and even the waves are affected by the structures. This is very evident when you are a few metersaway from a radio (not line of sight) and you get a strong signal, then suddenly you walk into a RF null. not fun.
6)Make sure you use decent antennae (and make sure that the radios can handle the power requirements of the antennae you're using.)
7)Make sure that your cables and the like are properly made if you're doing them youself. If your cables suck, your signal will go to hades.
tip: make sure you have secure authentication systems and xmission security. it's no fun when someone gets 'smart' and steals free bandwidth... or worse, account data.
tip: make sure you have something there that can protect your arse should something REALLY go wrong with the network. Hell hath no fury like a geek bereft of network access.
tip: take the time to do the surveys. If you do proper surveys, you will be a much happier person in the long run.
Anyhow -- There you go. I'm sure there's some more stuff I missed. Let's hear them.:)
Slashdot Mirror
Would love to save $$$ with OSS, but the software I need (robust, full-featured POS system) is non-existent. Bummer.
I was looking into this in the past and I came across OpenBravo (http://www.openbravo.com). They have two main components: ERP and a POS. They appear to have been designed to integrate.
I've never personally deployed this, but they offer the standard "commercial support for OSS product" model.
From my own light exploration, they appear to be pretty flexible applications. Might be helpful to your business especially if you are looking for front-end/back-end integration between internal business logistics/inventory and the front-line PoS systems.
There are a few caveats, as with any system, but maybe they're worth a look if you're seriously interested. Actually, I'd like to hear how you make out with that as I've been looking into its application elsewhere.
As for almost any kind of implementation, OSS or otherwise, it's important to make sure you've got your business requirements down. Then find a solution that works for your business needs - not the other way around. (But I'm sure everyone here already knows that and doesn't fall for the old 'gadget/feature' trap.... Right? ;) )
Anyhow, I'm rambling now. Let me wrap up:
* OpenBravo's one option, I'm sure there are more.
* It will be rare that an OSS or commercial product will be perfect 'out of the box'. You may need devel work done, but YMMV.
* If you don't want to do/commission any devel to meet your needs, you will likely be disappointed by the OSS world. Most OSS projects I've used are best-effort unless they're commercially backed. It wouldn't be fair to you or the projects to bring unrealistic expectations to the eval table.
* Even though I'm not a devel, I don't think OSS simply exists for others to party w/o sharing some of the cake. If it works, feel free to contribute in some manner. (ie. paid support, code, donations, feedback (not whining), even 'championship'/promotion.)
My company tends to stick with paid support and we will do testimonials where appropriate. I tend to do advocacy (championing/promotion) by recommending what I believe the best tool is for the job, OSS or otherwise. That way people know what to expect and what its limitations are and what recourse they have to get assistance.
* Despite what I've heard about people's understanding of OSS, I don't think the OSS community planned OSS to be "free" as in "free ride." (Not to imply that that this is what you're looking for.)
* OSS is not a magic bullet for saving money. Every solution has a cost and that cost is sometimes not quantifiable in dollars and cents.
* Lastly, I'm not associated w/ OpenBravo or any other OSS/commercial product. Just my 2,3 and 4 bits.
Good luck on your search!
I carry the cables for his spintronics! Ya gotta believe me!
I can now whistle at women without being immediately slapped!
Hopefully not! If that were to happen all the time, Slashdot would be sued off the net!
Just another thought - For all of you folks that work in consultancies that depend upon and recommend Linux:
How has the SCO FUD affected your relations with your clients both financially and in other business relation aspects?
(There, I used the term 'FUD.' *sighs*)
"That damage is in the past, stop it from happening anymore in the future."
I don't think that it's as simple as the above statement. Sure, the most visible damage would have happened initially, but the thing is that there are 'rolling' reprecussions that ripple down the time line as affected companies try to recover from the damage done.
For instance: A small organization that was working with a consultancy is considering Linux and a series of service agreements. With all the fear-mongering happening due to SCO's claims, the smaller organization is scared away from Linux and decides to stick with a vanilla Microsoft business environment. What happens?
As for preventing it from happening in the future, I completely agree. While some may claim that it infringes on their rights to restrict business practices, there are limits. I've noticed, here in North America, companies have too much freedom to do pretty much whatever they want, whenever they want, to whomever they want, for almost whatever reason. I'm sure many (if not most) of you share the same sentiments.
Wow - Having bought a Dell some years ago, I was quite pleased w/ their hardware and support. As such, I've always recommended their laptops though now I guess I'll have to give my recommendations more thought.
While I do recall the 'You agree to the EULA if you open the package' issue, but I don't remember having such hassles.
My feeling is that it might make a bit of difference if more people did what RobertB did - Call Dell and ask for a real explanation. Considering you've just made a 'sizable' purchase, that's the least they could do.
Does anyone know how this situation is handled in a larger organization where there would be hundreds of these 'mystery meat' EULAs that need to be 'agreed' to? It's probably safe to bet that most of the time admins just simply 'agree' to the EULA so they can get on with their work. Capitalizing on that bet it can most likely be said that a close examination of the EULA rarely happens and that they're rarely re-visited to check for changes since they were last reviewed.
To some it would seems like an extreme comparison, but it's almost like they've got your $xxxx investment for hostage and they're demanding a blank cheque so you can actually use it.
Now that I've read more and more about EULA 'landmines' I'm definately going to pay more attention to them. Luckily, nowadays, most of the EULAs I read are GNU or BSD in nature. (Yay!)
In any case, I'll admit - it would pain me to have to return the device, but principle is principle.
Actually, that's basically correct at its most rudimentary level. The difference is that Voice over IP (VoIP) calls are typically full-duplex now a days. This means that you can talk [send] and listen [recieve] at the same time like on a normal phone.
Before, back in the old my old 'BBSing with my 14.4 dial-up' days VoIP calls were very basic with very poor call quality. (They were also half-duplex much like talking on a walkie-talkie - you talk, then stop sending so they can reply.)
Anyhow, VoIP has definately moved along and large telco carriers are using it in their infrastructures to squeeze more value out of their existing network connectivity. My understanding is that if you're using Telus as you phone provider, chances are that at some point (especially if long distance) your call actually passes through some VoIP call legs.)
I always am amused (and at the same time somewhat disgusted) by this kind of elitist reply that seems to plague Slashdot.
Of course, I understand that we're all busy people with our own busy things to do so people don't have time to make some sort of constructive response. Then one gets to thinking: "If everyone's too busy or important to reply, why do they have time to write a reply that isn't constructive and actually seems to be more of a drag on the 'community' as a whole?"
Not too busy to take the time to point out how superiorior and resourceful they are to the 'n00bs', I guess. :\
People will go out of their ways to berate a perfectly logical question instead of answer 'yes' or 'no' (Which would be a simple reply to the first part of his question.)
Anyhow, I'd best stop for now. I've had my 2 bits and I'm not interested in starting a flame war. (I'm a really 'busy' person too! hehe Also, I'm beginning to think that I'm beginning to look like I'm getting a little hypocritical myself.)
[Last ditch attempt to be constructive]
Here's a link to help kick-start a new 'net you!'
http://www.albion.com/netiquette/corerules.html hehe ^^I could almost imagine sysadmins looking for the seat-cover version to increase productivity and deter stupid questions within sales/management.
Somehow, I keep thinking: network connectivity for these things and a cron job that runs every 5 mins.
Here are a few truths about 802.11b gear (and a couple of tips):
:)
1) 11mbit/sec actually turns into about 5mbit/sec because of error correction. (if I remember correctly, the 802.11b standard does errorchecking in a manner where it sends 12 bits and half of that is check sum.)
2) The top speed of the wireless wan is affected by the number of people on it. Just because each client connects to the AP at 11mbit/sec, it doesn't mean that the 11mbit will be guaranteed speeds.
3) you'll most likely require more than a 'couple' of access points to achieve building-wide coverage. Even the number of people in the facility that you're trying to cover affects the cell coverage size. (water absorbs and reflects RF - make sure you keep that in mind if you have plenty of foliage in and around the buildings.)
4) load-balancing is possible, but I've only seen it with the higher-end gear (ie. ciscos, etc.) That'll help with multiple people.
5) RF is prone to SERIOUS interference and even the waves are affected by the structures. This is very evident when you are a few metersaway from a radio (not line of sight) and you get a strong signal, then suddenly you walk into a RF null. not fun.
6)Make sure you use decent antennae (and make sure that the radios can handle the power requirements of the antennae you're using.)
7)Make sure that your cables and the like are properly made if you're doing them youself. If your cables suck, your signal will go to hades.
tip: make sure you have secure authentication systems and xmission security. it's no fun when someone gets 'smart' and steals free bandwidth... or worse, account data.
tip: make sure you have something there that can protect your arse should something REALLY go wrong with the network. Hell hath no fury like a geek bereft of network access.
tip: take the time to do the surveys. If you do proper surveys, you will be a much happier person in the long run.
Anyhow -- There you go. I'm sure there's some more stuff I missed. Let's hear them.