atCODAP
by SSI ...
Sensible Systems, Inc -- A leader in
Automated Support for Responsible Occupational Analysis
For Historical Interest
ONLY!
For current information,
please see: <http://www.icodap.org>
Customer Service Page
Obtaining a Demonstration Copy of atCODAP
Note: atCODAP is the property of Sensible Systems, Inc. and is provided as a non-exclusive SITE LICENSE (see Price List). This product is not authorized for SALE and annual LICENSE renewal fees are required for proper execution of the software. This practice allows us to ensure that all sites are operating on the exact same version of the software in order to minimize OUR maintenance time. The result is YOU receive on-target customer service and maximize the benefit from your investment. There are NO OTHER "upgrade" fees other than annual license renewal so that budgeting is simplified.
Demonstration copies are fully functional versions of atCODAP and are provided to requestors after screening by SSI personnel. Large organizations, Trade unions, Industrial Consortiums, Universities, HR professionals, and students are considered primary candidates for Demo versions. The Demo version of atCODAP is the standard version with a short expiration date (60 to 90 days) while the standard version has a six-month expiration date with automatic semi-annual updates. The Innovation Center for Occupational Data Applications & Practices (ICODAP), a non-profit affiliate of SSI, will provide support to HR students at no cost. HR students are encouraged to use this "free service" of ICODAP/SSI where the students supply the survey data and ICODAP personnel not only perform CODAP runs for free, they also provide guidance on most appropriate and alternate analysis strategies for their individual project. Check out example papers on-line resulting from one such project: Curriculum Development and a Repeatable Methodology. Send inquiries to ICODAP@codap.com
When the software expires: When the Demo/Standard version "expires", parts of the software cease to function in a manner consistent with maximum security of customer data. Customer data is stored in a separate directory (even a different drive, if desired -- such as a Zip Drive) and is never affected by software expiration. The atCODAP system is typically used in sequence to "load the data base", "perform hierarchical clustering" and, "report job descriptions." The "graceful degradation" of an expired atCODAP system internally deactivates key programs which support this flow. Although the selection is random, a higher probability for deactivation is given to "up front" processing program (i.e., data base creation) and lower probability to "close-out" processing programs (i.e., report job description). The atCODAP focal point at each organization is given instructions on how to apply immediate patches to avoid severe problems caused by lapses in the license coverage.
Email request to Sensible Systems, Inc.
At present, atCODAP is delivered on floppy disks. The first disk is the System Installation Disk and is usually red. The next four disks are the Program Disks and these may be Green, Yellow, or Blue depending on available stock. One unlabeled disk is provided which has the Windows 95 icon for the atCODAP system in the atCODAP.exe file.
Process Overview
To start atCODAP from MS-DOS, type "@CODAP". Starting in April 1998, the older "atCODAP" will be reserved for the new, Windows 95, based system exclusively.
Once in atCODAP, you will be shown a list of available studies. Study 0000 was provided as a place to store run stream (control cards [cc] or batch files [*.bat]) samples, both from previous studies and from any local studies or standards you may develop. Study S001 is a sample data set with a survey booklet in POOL.TXT and data in DATA.NUL to do atCODAP test runs without having to navigate the booklet setup, data collection, and data aggregation sections which tend to be unique to each and every organization. When licensed, the first atCODAP installation includes 1 week of training for up to 10 people from your organization and that is when the front end is customized to expedite YOUR local requirements.
As you select "NEW STUDY" (Open a new study), you will be asked for descriptions of the project. Whatever you answer there will be repeated on every load of atCODAP, so NewStudy titles should be clear and comprehensive. The NEWSTUDY program creates a directory for each new project. Subdirectories are created for each standard survey booklet. Default directories are JI for Job Incumbents, TD for Task Learning Difficulty and TE for Training Emphasis. The standard system file "@CODAP.SYS" determines the "standard" directories for your local site. Each survey directory is assumed to be the "Processing" level for runs associated with that survey. Each survey directory has two standard subdirectories ("BOOK" and "DATA") reflecting atCODAP's expanded range over traditional CODAP systems. Hence, selecting a "study" usually involves entering 1) a study number, 2) a survey booklet type (JI - default, TD, or TE), and processing stage ("Processing"- default, "Booklet Preparation" -BOOK or "Data Aggregation"-DATA).
Once you have selected a study, the atCODAP Menu system appears. From this point on, the Main Menu ("M") shows atCODAP Documentation as option 7. Load that option, type the name of the desired document and review its contents. Everything from Computer Basics to Control Cards (CC) are covered. Soon, this will all be moved to the Web, but for now, they are in flat ASCII text files which means they can all be loaded into ANY word processor and printed, if desired.
Read the document on the MENU system to understand the mechanics. Every Menu has a Main Screen (1 of 5) and Four Support Menus (2 of 5 through 5 of 5). After the initial Menu ("M"), the support menus become standard and atCODAP documentation is available from those panels accessible with Left or Right arrow keys.
Because data preparation has, historically, been unique to every organization, it is recommended that you learn the atCODAP system by using the data set provided. This data set is of CODAP Practitioners from Australia, Canada, and the United States -- so the task list and data set itself are of professional interest. It is hoped that the "front end" processing preceding traditional CODAP will migrate to an integrated data collection system. This system should have all media sources (paper-and-pencil, floppy disk, email, internet, etc.) being generated from a centrally-define survey specification with variations allowed only for presentation format -- not for data elements or length. While atCODAP's GenBook and HardCopy/atENTER and atMASTER/atSURVEY began this practice in 1989, newer products (IJOA's AUTHOR system) are becoming available. In lieu of an actual "tutorial", download or review the following, annotated series of screen prints about "starting up" atCODAP. This sample assumes that you have already automated all the text for your survey booklet in JOBSUR standards and that your data has been "preprocessed" to the DATA.NUL stage. Transcript for converting BOOK.TXT & List Files, along with DATA.NUL into an atCODAP data base with appropriate audit runs. (To see box characters properly, this Runs01.TXT file is best viewed with the MS-DOS Edit program.)
(Under Construction)
Q: I was told that a certain atCODAP feature was operational, but every time I select the option from the Menu system, it says "THIS PROGRAM IS NOT YET AVAILABLE!" -- What should I do?
A: Send Email to Johnnyw@codap.com. Sometimes new programs are released (i.e. placed in the main program directory: C:\atCODAP\Ver1, but an older batch file (that prints the "Not Available" message) is not removed. As batch files have precedence over the *.COM files, the menu system only starts up the error message and never gets to running the program which is also there. If you check and see both the [name].BAT and the [name].COM or [name].EXE file, simply delete the [name].BAT file from the directory. Even if you solve the problem in this way, PLEASE notify SSI so that the next release of the system can be corrected for everyone.
This problem is complicated by the fact that new programs may have their names changed during the development process. In these cases, the Menu system may have been set up to invoke the earlier, proposed program name, but with the name change, the menu system points to a program which does not exist. These Menu-Program name disconnects happen because of the volatile and responsive nature of custom programming efforts for the occupational analysis community.
Q: How does atCODAP differ from Mainframe/RISC CODAP of Old?
A: Traditional versions of CODAP assumed that data would magically appear in the form of punched-cards (80-columns per record, many records per respondent) and its mission would end when computer print-outs (10 pitch on perforated 11" x 17" pages) hit the high-speed printer. The job of creating inventories, collecting and automating data and ensuring results could be used by an end-user was a local-site "people problem."
The "at" in "atCODAP" means "anchored to CODAP -- but not limited by it." Because "atCODAP" has moved it mission both earlier and later into the OA process, it appears to be stepping on people's toes. Most commonly heard is "THAT is NOT the way we've done data collection", or "Where's the XYZ report we give to Trainers." The front-end to atCODAP is a nightmare because of all the different methods that have been used for data collection, etc. While every attempt has been made to provide "paths" through the Menu system, the front end logic contains at least five times more options than any ONE user will use. Typical data aggregation options include input from 1) card-image files (IBM 7040/Unisys 1108 versus IBM 360/370); 2) optical scan systems (multi-record & single record formats); 3) atSurvey automated surveys; 4) OASurv automated surveys; 5) external, single-record data systems. By far, the worst possible input system is the traditional card-image file which requires SEVERAL levels of audit to ensure proper data registration. The most economical and highest quality data aggregation is provided by processing data from automated surveys (atSURVEY or OASurv). Both the MS-DOS and Windows version of the atCODAP Menu system run from "Menu Scripts." In other words, by editing a local text file, the atCODAP site manager can reconfigure the Menu system to meet local standards. Unused options can be removed and local processing can be added.
Q: How was the Menu System Developed?
A: We old programmers (from mainframe days) think nothing of memorizing hundreds of computer commands and just typing them in at the "C:>" when we want something to happen. Normal people, on the other hand, don't eat, drink, and breathe computers (i.e., they have a so-called "life"). In other words, they are infrequent users of the mystic and terse terminology known as computer commands. The atCODAP system began in 1982 on a TRS-80 Model II. It migrated to Xenix (a Unix-clone) in 1983. And finally landed on an IBM PC in 1984 where is grew until being announced as "available" as a service bureau in 1987. In 1990, I (Johnny) had to go to Australia for five months. Un/Fortunately we were doing operational studies for the US Coast Guard and had just starting a new project for the IRS Taxpayer Assister Job Family and automated surveys for the Ford Motor Company and Southwest Research Institute. Up until this point, I had been doing all the runs. I had to create a system by which our Corporate Secretary (a real secretary by profession) could do these runs in my absence.
I started by creating "Run Books". I ran through a few similar kinds of runs, documented which programs I ran in what order and NOTED where I supplied titles or inputs that had to be researched at run time (i.e., they were NOT constants). I was surprised at the complexity of what we did so routinely without notes. I went to Australia for five months. Thank heavens for FAX machines! (Aside from the 15 hour time difference) she provided me with a written list of what I overlooked or just plain had wrong.
SO, while in Australia in mid-1990, I wrote the first (two) versions of the atCODAP menu system. I foolishly believed that the menu system would solve all the problems because it was very "Windows-like". (Remember, this is 1990-1991 we're talking about.). Upon returning from Australia, the Adult Vocational-Occupational Education Department at the Ohio State University began teaching occupational analysis using atCODAP. With the very first students, suggestions for changes to the menu system flowed in. Rather than creating an entirely new system, the "Educational/Operational" submenu system was linked in as Option "1" on the Australian menu. For several years, the two system existed side-by-side and provided a "failsafe" if problems were encountered in one half or the other. Finally, in 1996, a massive effort was made to integrate and reformulate the two systems into a unified menu structure. That is the system which exists today.
Reporting Suggestions/Problems
Email suggestion/problems to Sensible Systems, Inc.
If you are reporting a problem, please specify the PROGRAM with the problem and how you determined a problem existed (e.g., "system hung", "garbage printout", "I/O Error #nnn", "reported values cannot be correct.", etc.) If you cannot determine the program name, please report the MENU SCREEN (Mxxx from the upper right corner of the screen) AND the option you selected which caused the problem. We may ask you to "turn on" the SaveStep option and repeat your selection to capture the actual run. If there are printed outputs, please attach the print file to your email or enclose it in your mail.
Copyright © 1997-2001 Sensible Systems, Inc.
