Curriculum Vitae

William T. Voris

AI Computer Scientist

Cyberneticist

.

He is a computer scientist, a data scientist and an artificial intelligence pioneer. Worked as a mainframe systems, management and field consultant for over 30 years. Has extensive background and understanding of all facets of the software development life cycle. Assisted numerous mainframe and multi-tier computer centers with their information technology needs. These tasks range from software development and data modeling to implementing computer architectures and multi-tier integrations. He has developed web sites, expert systems, voice interfaces, inference engines, CASE tools, PC, server and mainframe software systems. Operates at a high bandwidth, but remains grounded by understanding the practical value of information technology. He is able to apply and use technology to advance an infrastructure, streamline and automate business processes and often reduce the total costs of computing. Can organize, document and explain the most complex of systems software. Feels equally comfortable with coding technology, interfacing with C-level management or providing presentations. Has a gift with computers, but also a gift with being able to draw out and interest others in the value of technology. Holds a Bachelor's Degree in Physics and Education, with post graduate work in Computer Science. Consulted at numerous companies in various technical roles, but more recently solved P NP. Generally described as low key, didactic and personable, but he enjoys individuals that share in his passion for technology. Enthusiastic, hardworking and persevering are aspects of his work ethic.

P NP – 2006-2019

Took a sabbatical from consulting in 2006 and started working on the solution to P NP, the world’s greatest math challenge and also the greatest problem in theoretical computer science. Solved P NP in 2010, but could not prove the algorithms would work. Developed a DOS 32 bit mainframe-like app called PNPSOLVE in microfocus COBOL to demonstrate proof of concept. Runs with all 32 bit versions of Windows, XP and prior versions and also on Windows 7 if installed in 32 bit mode. In 2011 developed a beta copy of the P NP software to demonstrate how these algorithms could be applied to software development. Floated a beta copy to many sources in the computer industry. The reaction and interest generated from the beta was encouragement to perfect the software. In the winter of 2013 he perfected the software to demonstrate proof of concept, specifically that the algorithms worked. Contacted Clay Mathematics Institute for instruction. They recommended that a white paper be developed. Mouse click the P NP button to the right. 

Field Assignments

Nationwide Insurance – 2002-2006, 1993-1994

In the winter of 2006 completed a consulting assignment working in the personal property section as a business and technical consultant. Developed a plan for the modernization and web enablement of the fire and auto insurance computer software. It was a client-server system with links to the mainframe that was generating over $10 billion a year in revenue. The plan included using a hybrid edition of microfocus COBOL and reverse-engineering a legacy COBOL/VM application. A previous assignment included developing a software re-engineering plan. Environment was an IBM mainframe annuity system. C-level management reviewed the plan, then implemented it. It saved Nationwide over $2 million a year in IT costs. Worked with Nationwide previously in the early 1990’s and developed a migration and integration plan for a Peoplesoft payroll implementation

Mead West Vaco 2003-2004

Was initially contracted to Mead West Vaco as a Senior MVS IBM systems analyst. However, soon was responsible for three tier support for both the client-server and mainframe systems. Task activities were the monitoring of all computer systems for problems and taking appropriate recovery actions. This included interfacing with individuals across the infrastructure as well as IBM and HP product support and system engineers, outside vendors, suppliers and management personnel. This was an exceptionally diverse and technically challenging assignment. Software environment was composed of IBM mainframe MVS/zOS, DB2, CICS, Websphere, Lotus Notes, Netview, TSO-ISPF, RMM, SA390, Omegaview, NT Server, Rconsole, NWAdmin, SAP/R3, Windows 2000 Server and UNIX-AIX. It also included using and augmenting procedures for batch scheduling packages, e.g. TWS, OPC, CA7, CA Scheduler and UC4. Worked with the system programmers and DB2 administrators to develop procedures for the automation of mainframes using the SA390 product. Installed numerous package upgrades. Assisted IBM SE’s with load balancing concerns on the Parallel Sysplex LPAR’s. Mead was in the process of developing an IT transformation strategy to combine two different mainframe manufacturing systems, specifically Mead’s SAP and West Vaco’s custom written manufacturing system. To help with this transformation he developed a run manual for all processes that occurred on a repetitive basis, including parm cards, run cycles, contentions, backup and recovery and hardware monitoring. He also fine-tuned LPAR’s, the parallel sysplex, and oversaw systems programming installations. When systems programming, operations and the data base team could not resolve a problem, it came to him. He was documented to have solved 100’s of technical and computer related problems.

The Limited – 2001

Responsible for meeting with subject matter analysts, extracting needs and then developing Purchase Order software creating interoperability between a midrange (AS400) and a mainframe (S/390) system. Software used was CICS, DB2 and SPF on the mainframe. Also, developed numerous macros between Windows NT linked to an AS/400 and the mainframe. Rehearsed the linking between mainframe and AS/400 numerous times for data pattern matching and complete flow of the data, from entry into the system, to processing and reconciliation. Both unique data mining techniques and SQL were used to process data. Used SPUFI, QMF and Fileaid to query and populate new data bases and data structures. Developed numerous JCL PROCS and FTP computer programs. When completed, there were over 1000 individual steps in the process. Each step requiring a program, a macro, an FTP, an MVS PROC, a Clist or REXX. On first production (parallel) run all software worked with no errors, and balanced.

Toyota – 2000

Contracted to Toyota as an IBM mainframe programmer for the installation of a large manufacturing predictive analytics system called eKanban, aka Toyota's Total Production System. Toyota has the only known functioning implementation of JIT and MRP analytics applied to lean manufacturing software. Developed the master data base program for eKanban which is the technological fulfillment of Toyota's Total Production System. It employed significant use of SQL and trivalent logic. Also developed a (mainframe) job production schedule, software tools to assist with remote transmissions TCP/IP to SNA and MVS. Additionally, performed feasibility and planning for the MVS operating system and VSAM, IMS and DB2 file structures, i.e. size and space considerations, as well as backup and recovery, contentions and batch window issues. Interfaced with systems programming, database administration teams and project managers. Assumed a lead position for numerous mainframe tasks. Used Visio for design and analysis documents. Also, developed production mainframe programs in IMS DC, DB2 and COBOL, including a CLIST JCL parser with auto-compile features.

Note: Toyota does not provide verbal or written letters of recommendation.

Intelidata – 1998-1999

Worked as a Cloud Computing analyst and software developer for an Internet banking system called Interpose. Created software to interface unformatted data structures into a mainframe banking application. Created software and procedures to capture data from the Internet and stack them into temp-storage queues. Then created a transaction to query these inbound servers and interface into a mainframe CICS VSAM banking system. Once data was processed, created transactions to distribute data to an outbound server. Worked with several banks interfacing their legacy mainframe systems with the Internet Interpose software. Performed data mapping, integration analysis and developed routing software based on the banks needs and unique software interface requirements. Intelidata was acquired by Fiserv Corillian on-line banking. 

Procter and Gamble - 1995-1996

Designed, developed and programmed a shipments to customers reporting software system that included totals for all products, distribution and monetary considerations. This included every product that P&G produces, from brand level to elemental product across all six divisions. It took extensive testing to get everything to balance, with timings, extractions, unknown and undiscovered variables. Two days before the software was to go into production 100’s of problems started occurring in testing. Therefore, he developed a unique file extraction technique from Teradata into a symbolic, cascading and replicative KSDS VSAM data base structure more complex and powerful than DB2. However, with the first full production test (with all six divisions processing simultaneously) it brought all of P&G’s mainframes to a standstill. Phones ran, then he changed the process to single thread. At the end of the day the software worked without error and balanced to the penny. The user was exceptionally pleased with the results. Contracted to P&G multiple times, however this was the most significant pieces of software. For another assignment he fixed problems with a freight accounting system in COBOL, DB2 and MVS. To accomplish this he worked for several months getting the bugs out of a system developed by external consultants. It worked without error for several months, but then all of the sudden the software quit functioning. Upon analysis he found an imaginary 13th month, buried in the code and not in any DB2 tables. He made numerous changes; but, after only minor testing he was able to get the software to function without error. Then he worked on another accounting software system. He constructed an MVS job production schedule. Developed JCL and checkpoint/restart procedures. Upon testing the system operated without errors and he moved it to production.

Transportation Research Center – 1993

Worked as an Infrastructure Architect. Met with and managed a steering committee to merge two IT centers. The two environments were a DEC VAX and an AS400. Developed an integrated plan in Visio and Microsoft Project. This was a collaborative effort soliciting the input of numerous people working at the center along with executive management. He reviewed the plan with the president and referred additional concerns to IBM. At this time he had no communication with IBM. However, they came in to manage the project after he completed the design.

Eli Lilly & Co. 1992

Worked on a number of mainframe projects. These included setting up the Peoplesoft migration plan from unit testing to user acceptance testing. The physical plan was documented in over 20 white binders; cross-referenced and indexed. These were the outcome of trouble shooting, production scheduling and extensive user interaction. This payroll personnel system was and still is one of the most integrated three-tier implementations of Peoplesoft.

MDC Lexis-Nexis 1989-1990

Developed a futuristic enterprise model for Mead Data Central called Next Generation Systems. The model was constructed inadvertently using a paradigm of threes methodology. The plan was too advanced for MDC at that time, however they found it interesting. They said, “You appear to be a futuristic theorist. If you are truly a futuristic theorist you will eventually figure out what part of the future you understand and how far into the future you are”. On January 14, 1993 discovered the paradigm of threes and believes it represents a breakthrough in artificial intelligence.

Other Projects

Business Architect Software - 2000-2001

Developed a tool to benchmark infrastructure processes against three-tier computer architectures for IT centers that are considering a migration to AI. The outcome of this effort was an expert system called the Business Architect. It was a predictive enterprise modeling tool that help determine what technology exists, how it is being used and identifies interoperability issues, redundancies and the technological maturity of an IT center. It contained a ternary inference engine and features were internally programmed. It ran as a 32-bit app, Windows XP.

IBM Blueprint 2000 - 1993

Developed a plan in 1993 called IBM Blueprint 2000. The basis of the plan was IBM’s SAA and AD/Cycle explained through a discovered concept called the paradigm of threes. When IBM reviewed the white binders, they compared the work to a room full of geniuses that had been locked up for years. He is often rumored to be in line for the CEO position at IBM. Sam Palmisano tried to hire him in 2010 as his successor, but didn't. Since then, IBM has focused almost exclusively on areas of AI.

CASE Workstation – 1989 - 1990

Developed a Computer-Aided Software Engineering workstation for mainframe software development external to a mainframe. Contained a TSO-SPF like product to emulate the mainframe, CICS and a COBOL compiler. Was used to develop text-based software for a PC, an Intel server or a mainframe. Was used to develop the P NP software and also the Business Architect expert system. The product was excellent for working with ASCII files, flat files and no-SQL data to enhance data mining and also reduce, organize and model big data.  This allowed it to be in a format for migration to a data base or an indexed file for the purposes of more rapid access, searching and reduction of irrelevancy. Had an internal COBOL coding generator that produced zero defect code through a series of templates, but then dynamically pulled all pieces of a computer program together at compile time. Was highly advanced for the mainframe marketplace as it used an object-oriented method applied to the coding of an application but could also be for rapid prototyping. In the past he would take a PC with the workstation installed to the client sites and then would use it to develop mainframe software. Once unit tested, he would then upload, reducing development time by as much as 50%. Click this link for published information about CASE Technology. CASE Technology has generally been deemed a failure; however, the paradox is that this Workstation worked in the late 80's and early 90's as a DOS 32-bit app with older editions of Windows.      

International Business Machines - 1997

Was contracted by CTG to solve the millennium bug for IBM. What did Voris do? Nobody knows, but whatever it was it obviously worked.

NATIONWIDE - Over the phone. Over the web. Over the desk.

You

You

You

Hello Phyllis,

I often think about you, Joni and Julie and my days with PDR. You were always so supportive and helpful. Moreover, both Joni and Julie knew how to manage my idiosyncrasies to get the best from me. Perhaps now I've finally found an outlet for my genius. Please wish me luck and again I thank you and everyone for all their help and support.

Bill  

Think first. Think more. Think different.

People are having a difficult time finding current or relevant information about me in search engines. They are mainly finding dated information, for example my sex life and The Elusive Paradox. That book was an experiment. I wrote it to confirm that I had the intellectual disciple to write a 300+ page book. Most people who started reading it gave up as the material is exceptionally complex. The material jumps around, but the content is sprinkled with bits of brilliance, mixed with intellectual dichotomies. Prior to consolidation, many of the chapters were shared with executives in the computer industry. The responses ranged from stunningly profound to a prophet of doom. Microsoft's founder particularly liked the Collapsing Time Theory. The experiment was successful. But the content of the book is best described by Co-pilot (see below). The material has errors. Some have been addressed in The Theory of Creative Evolution, specifically the Theory of Symmetry and the time-space issues. I am thinking about bringing it back into print, as I know that it would be a best seller despite its errors. The final chapter is projected to be many, many years into the future. These days I want to make AI a success, not be an author.

I never figured AI would be taken seriously in my lifetime. This is especially true after decades of presenting myself and my theory to the computer industry. It is a prescient phenomenon to recognize my paradigm of threes theory and the value of AI was confirmed while I was away. Moreover, I would prefer to be defined by the Theory of Creative Evolution, rather than The Elusive Paradox. I was convinced that Co-pilot was a glorified search engine, until I read this. Co-pilot actually read and understood the material. That has to be the most awesome assessment any(one) has ever written about my writing. I thank you Microsoft, or should I say Co-pilot and AI.  

You may review the website below to extract whatever value it may possess. You may accept or reject its premises based your connection to it. Unlike The Elusive Paradox, it is extensively researched. I wrote this theory while incarcerated. Is it inspired from beyond? You decide. It is, however, the most fascinating document in the world right now. If it is true, then nothing else in the world matters, but the Theory of Creative Evolution. 

Addendums

https://theoryofcreativeevolution.webstarts.com

Google ideas moved to the Nebula.

  https://artificalintelligence.yourwebsitespace.com/nebula

What is causing this miraculous transformation?