WordPress - Web publishing software
Copyright 2011 by the contributors
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
This program incorporates work covered by the following copyright and
b2 is (c) 2001, 2002 Michel Valdrighi - firstname.lastname@example.org -
Wherever third party code has been used, credit has been given in the code's
b2 is released under the GPL
WordPress - Web publishing software
Copyright 2003-2010 by the contributors
WordPress is released under the GPL
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
June 28, 2010
IWMS expert and Lucernex President, Joe Valeri (see Joe’s management summary here), discusses the reasons some IWMS implementations are easier than others.
There is a very wide range in how long an IWMS implementation will take from as little as a few weeks to as long as a few years. There are a number of reasons for the variances in implementation time frame but I will focus on three that I believe are the most significance: product flexibility, delivered functionality and client requirement complexity. These three issues are actually highly entwined making it even harder for most companies selecting an IWMS to properly assess each one.
When companies look at applications they often make the mistake of basing their analysis of how well the product fits them based on what they are shown in a demo. Even though those demos may be as long as 8 hours, what you don’t know is how long the vendor spent preparing it and how much of what your seeing is real functionality vs. “configuration magic”. Pre-configured product can be a good thing if the items configured are actually truly usable by the client. However what most often happens is the client is shown a demo, let’s say of sample real estate transaction management processes, thinking that what they are seeing is actually part of the delivered product only to find out later that it was a configuration item and they will need to build their own base functionality from scratch. This of coarse means professional services cost to get it done, often in the form of a change order over the initial estimate.
To avoid this ask vendors to first give you and “out-of-the-box” demo before getting the long demo full of “configuration magic”. You will then be able to properly assess what you are and are not getting.
There are also products that deliver a lot of out-of-the-box functionality providing clients a better starting point for their implementations but that are inherently hard to change. For example a vendor may have a very specific IWMS product for restaurants or cell towers, delivering a lot of specific features to fit that market BUT when you begin to implement you realize that changing critical system pages, building a simple report or creating a data export requires a software developer immediately extending the implementation timeframe and running up cost.
Ask the vendor to modify a few critical pages during the demo and add, delete and change fields. Ask them to add a page someplace in the menu structure that you identify. Make them create an ad-hoc report on the fly and show how that can be scheduled. All of these items will indicate a level of flexibility that will significantly decrease the implementation timeframe and overall project cost. This level of flexibility can mean the difference between a 2-month project and a 6-month project.
Client requirements complexity
Every client is different and each client always has unique requirements. Applying those unique requirements will require some degree of configuration or, with some less flexible software, customization. As the number of locations gets larger, typically, the complexity of configuration also gets larger. Larger firms not only have more complex business processes they also have many integrations and data conversions adding complexity and cost to any implementation. All of these items will add to the timeline and cost of an implementation project though a large degree of the business process complexity can me mitigated with a highly flexible product.
Can an IWMS really be implementing in weeks or a few months instead of a few quarters or years? Lucernex provides a Quickstart® program that can have smaller companies live in two to nine weeks. We have the most flexible product on the market allowing for client or implementation team configuration of nearly every page, wizard, form, workflow or report in the system. The Lx IWMS also is delivered with a huge amount of industry specific functionality out-of-the-box and also comes with many best practices forms, workflows, reports and pages pre-configured. Unlike may other vendors we are doing everything we can to AVOID high professional services fees for implementation by making the product easy to configure without ANY software development resources. It is extremely rare that any of our implementation require any customization.
Configuration – adapting a software application to meet unique client needs using tools provided by the software developer; this may or may not require a software programmer
Customization – programming code written by a software developer that impacts either base code or client specific code to meet the unique needs of a small number of clients
Integration – programming code that allows two different software programs to exchange data and/or activities on an on-going basis
Data Conversion – a one-time movement of data from one software application to another usually with the intent of replacing the originating system
Previous IWMS related Blogs
What is IWMS anyway?
IWMS? It’s Location! Location! Location!
The Power of Location Management
IWMS – Why so expensive?
IWMS in the “Cloud”
How Capital Project Management fits in an IWMS