The Story Behind CIS Software
From Quality Management in the Field to CIS Software
CIS did not begin as a software idea. It grew out of decades of hands-on work in manufacturing, aerospace, defense and quality management – solving the same practical problems organizations still face today.
The early years
Quality management before connected systems
My career began when quality systems were largely paper-based, departmental and dependent on people manually moving information from one place to another.
Working in aerospace, defense and manufacturing environments, I kept seeing the same problem. Organizations were putting considerable effort into quality, but management often lacked current information and processes were duplicated across departments.
Procedures were rewritten, records were difficult to retrieve and decisions were often based on information that was already out of date.
The recurring problem
The effort was there. The visibility was not.
The challenge was not that people did not care about quality.
The challenge was getting the right information to the right people, connecting related processes and making the management system useful while the work was actually happening.
The turning point
Stop describing the problem and start rebuilding the system
Rather than accepting the limitations of traditional quality systems, I began working directly with organizations to redesign the way their systems operated.
In some cases, I was prepared to demonstrate the value of a better system before expecting the organization to make a significant commitment. The objective was simple: prove that better process design could reduce recurring problems, improve control and make quality more useful to management.
How the idea evolved
CIS was built one practical problem at a time
Learning where traditional systems broke down
Experience in manufacturing, aerospace and defense exposed the limits of fragmented documents, manual reporting and disconnected departmental systems.
Building systems directly inside organizations
Working closely with employees and management made it possible to see which processes added value, which created unnecessary work and where information was being lost.
Using technology to remove repetitive administration
Individual database tools began replacing paper and spreadsheet processes where better retrieval, responsibility and visibility could make a practical difference.
Separate tools gradually became an integrated system
As more processes were computerized, the value increasingly came from connecting them rather than operating each one independently.
Continuous Improvement Software
Those ideas eventually became CIS – a configurable system designed to connect quality and operational information and make it useful throughout the organization.
Industry recognition
Professional of the Year – Quality Magazine
My work in quality management was recognized by Quality Magazine when I was named Professional of the Year.
The feature, “Living Proof,” told part of the story behind my approach to quality systems and continuous improvement.
Why the recognition matters
The approach existed before CIS became the product it is today
The software came out of the same philosophy that shaped the consulting work: make quality practical, measurable and connected to business performance.
CIS became a way to put that philosophy into a system organizations could use every day.
The birth of CIS
The software followed the management philosophy
Years of consulting and system development kept pointing to the same requirements.
Current information
Management needed information while it was still useful, not weeks later in a manually prepared report.
Connected processes
Audits, corrective action, training, inspection, suppliers and other processes work better when related information remains connected.
Organizational visibility
People needed access to the information relevant to their responsibilities without relying on separate departmental files.
Practical flexibility
The software had to adapt to the organization rather than forcing every company into exactly the same workflow.
A change in thinking
From “quality system” to “improvement system”
A management system should not become static once certification is achieved.
It should continue to expose problems, generate information, assign responsibility and help the organization improve how work is done.
The philosophy behind CIS
Measure. Understand. Improve.
Continuous improvement becomes much more practical when information is retained and connected.
Every audit finding, nonconformity, inspection, corrective action, supplier issue, training requirement or maintenance activity can become useful information rather than simply another completed form.
Today
The original idea is still visible in CIS
CIS now supports far more than the early quality databases, but the purpose remains the same: reduce unnecessary administration, connect information and make the management system useful to the people running the organization.
Quality
Audits, inspections, nonconformities, corrective action and continuous improvement.
People
Training, competency, responsibilities and organizational knowledge.
Operations
Suppliers, products, inventory, maintenance, production and related operational controls.
Management
Reporting, objectives, meetings, actions and information for decision-making.
The story continues
CIS is still being shaped by real organizations and real problems
The system continues to evolve as customers identify new needs, processes change and better ways of managing information become possible.