Home : Introduction requirements issues capabilities ECM proposal project life metrics CMMI benefits motivation author academic lessons learned policy
Demonstrated: distributed database conveyor emulation


Infinite Delta Corp supports the ideals maintained by the Free Software Foundation's (FSF) and Debian GNU/Linux. Specifically the Debian's eloquent freedom description. Core products including documentation will be released under the GNU Public Licensing (GPL) version 3.

Support customer proprietary policies and strategies

Infinite Delta Corp shall support customer proprietary policies, security, and strategies. As expressed in Debian's freedom description, some have gone to far in evangelizing the free world effectively hurting their own cause. One of the proposed and now dead GPL proposals and the GNU Free Documentation License make free products from being fully and openly used.

EXCEPT: Planned obsolescence as a business model.

Planned obsolescence as a business model is to be discouraged. When end customers are drained by unnecessarily dependencies, changes, and training. Infinite Delta Corp is about handing a lot of change, hence the corporate name, but its not about change just at the customer expense. Managing change at customers benefit makes the customer strong and loyal. This is a very important distinction.

GPL for documentation

The ECM process truly blurs the boundary for documentation, data, and code. The Debian's freedom policy better reflects our goals. The FSF separate documentation licensing shall not be used.

Distinctions between GPL and Proprietary data

Strict distinctions between GPL data and different levels of Proprietary data shall be supported and guarded. Different proprietary data levels shall be maintained by separate files with one way links to allow safe dissemination of capabilities. This is an extremely important point and deserves some examples.

Geothermal example

A manufacturer of a Geothermal Heat Pump desires to offer a capability to the residential Heating Ventilation Air Conditioning (HVAC) designers. An open ECM file is created for all HVAC designers to see. It includes specifications and limitations the manufacture wants totally visible. However, price and schedule are not so public, it requires contact information. A second file, a little more private file which refers to the first that gives price and schedule information and is available only to those contacts. Finally, a third file, containing actual proprietary information is used internally to help internal processes, including the possible generation of the more public files.

Large contract example

A large commercial building contract has been awarded to a primary building contractor XYZ. The HVAC subcontractor is dependant on some heat pump capabilities and keeps an ECM file specific for XYZ so that the XYZ cost and schedule can be always monitored and still not impose on the HVAC's agreements with the manufacturer.

Public data example

A geothermal heat pump installer, with permission of the individual system owners, publishes just the site thermal conductivity ECM file. Research institutions and equipment manufactures can perform area analysis to better support the community. Geothermal heat pump installers can quickly discover areas not supported.

Binary encoded capabilities files

The ECM file uses a very simple binary association scheme. An ASCII, XML, and database schemes have been ruled out for international language and internal company language issues. Example phrase "On Time" in one department means milliseconds, where another department may mean today. International has similar problems with plurals and gender assignments. Finally, as Adobe learned with its Postscript to PDF transition, it minimizes confusion by using a well defined binary system.

Copyright (C) 2007-2020 Infinite Delta Corp. GNU General Public License (GPL) version 3.