technical profilehome.windstream.net/jloefer/resume/techprof.doc · web viewantenna base load...

Technical ProfileJason Loefer

Address: 124 Wood Crest LaneHoschton, GA 30548

Phone: (706)658-2630Email: [email protected] efer/ResumeIndex.htm

document.doc

http://home.windstream.net/jloefer/ResumeIndex.htm

Experience and Proficiency Technical Profile - Jason Loefer

Legend

Table of contents 1 Experience and Proficiency................................................................................................................................... 4

Languages......................................................................................................................................................... 5Operating Systems............................................................................................................................................. 5

Skills Overview....................................................................................................................................................... 6Languages......................................................................................................................................................... 7Operating Systems............................................................................................................................................. 7Libraries............................................................................................................................................................. 8Applications........................................................................................................................................................ 8Environments..................................................................................................................................................... 9Systems............................................................................................................................................................. 9Equipment.......................................................................................................................................................... 9

Project Details....................................................................................................................................................... 10ComplianceFactory 1/2005 to Present.........................................................................................................11Snap (Special Network Applications Processor) 3/2003 to 12/2003.............................................................12Prism GUI 1/1999 to 4/2003......................................................................................................................... 13DoBuild 3/2003 to 12/2003........................................................................................................................14UniToPri (Unipage to Prism) 1/1999 to 4/1999............................................................................................15BSC (Base Station Controller) 6/1998 to 1/1999..........................................................................................16FileNamePad 10/98 to Present.................................................................................................................... 17

1 Page numbers are hyperlinks to document sections.document.doc

of 35 Legend: Embedded; Windows / DOS; UNIX; Microsoft Office; (other or hybrid) 4/9/09

EmbeddedWindows / DOSUNIXMicrosoft Office(other or hybrid)

Technical Profile - Jason Loefer Error! Style not defined.

WSerMon 7/96 to 12/99............................................................................................................................... 18TNPP Engine 5/1996 to 1/1997................................................................................................................... 19Energy rate conversion 10/1996 to 1/1997..................................................................................................20Portia 6/1996 to 9/1996.......................................................................................................................... 21MTOSIF (MTOS Interface) 9/1995 to 11/1995.............................................................................................22ALFADB 2/1995 to 4/1995.......................................................................................................................... 23Message Maker™ 4/1994 to 6/1994............................................................................................................24NETTNP 11/1992 to 9/1995........................................................................................................................25MRS (Management Reporting System) 9/1991 to 10/1992..........................................................................26AAS (Agent Access System) 6/1989 to 12/1990..........................................................................................27MBA (Mobile Billing Accumulator) 6/1989 to 2/1990....................................................................................28MMI/NSR2 (Man/Machine Interface) 8/1989 to 2/1990................................................................................29Starlink 4/1989 to 6/1989.......................................................................................................................... 30CIIO/CVT (Computer Interface I/O / Converter) 6/1987 to 8/1988................................................................31DLO (Data Logging Option) 3/1988 to 5/1988..............................................................................................32DSKIO (Disk I/O) 6/1987 to 8/1988..............................................................................................................33System III 6/1985 to 5/1986.........................................................................................................................34

Index....................................................................................................................................................................... 35

Total pages: 35

document.doc

4/9/09 Legend: Embedded; Windows / DOS; UNIX; Microsoft Office; (other or hybrid) of 35


Experience and ProficiencyExperience and Proficiency

document.doc

of 35 Legend: ; ; ; ; 4/9/09

Technical Profile - Jason Loefer Experience and Proficiency

Languages

LanguageProficiency

(1 to 10)

Experience(in years)

C 7 22C++ 6 16C++Builder 9 13VBA, VBScript 6 8VB 4 2.NET 3 1Delphi 3 2Access 4 6SQL 5 5FoxPro 5 2Clipper 7 10dBase 8 1180x86/87 6 7Z80/280 7 8

Operating Systems

Operating SystemProficiency

(1 to 10)

Experience(in years)

Windows 9 17MS-DOS 10 17UNIX / Linux 8 20PC-MOS 7 3Xenix 9 5Solaris 5 1AIX 2 1

document.doc

4/9/09 Legend: ; ; ; ; of 35


Skills OverviewSkills Overview

document.doc

of 35 Legend: ; ; ; ; 4/9/09


Languages

C++Microsoft Visual Studio .NET, 2003, 7 - 5UNIXgccBorland C++Builder 6.0 - 1.0Borland 5.2 - 3.0Borland Turbo 1.0

CMicrosoft Visual Studio .NET, 2003, 7 - 5Linux gccUNIX gcc, ccSolaris, ccXenix, ccMicrosoft C 7.0 - 5.1Borland Turbo C 2.0 - 1.0

ShellsUNIX KornUNIX CUNIX BourneWindowsMS-DOS

Database (non-SQL)Microsoft Access 2000 - 3.5Borland Database Engine (BDE)MS ODBCVisual FoxPro 6.0 - 5.0FoxPro DOS 2.5, 2.0ParadoxCA-Clipper 5.2Clipper Summer '87dBase V - IIFoxBase 1.0

Database (SQL)Microsoft SQL Server 2005, 2003, 2000 TSQLMicrosoft SQLMySQLOracleInformixBorland “local SQL” (BDE)Pervasive SQL 2000 / 7.52 - 7.4FoxPro DOS SQLFoxPro Windows SQLParadox SQL

PASCALDelphi 5.0 - 1.0Borland Turbo PASCAL

Assembly80x86/87 MASM80x86/87 Borland Turbo Assembler80486HC11

805168056802680x0Z80Z280

BasicMicrosoft Visual Basic .NET 2003, 6.0 - 4.0GWBasicUNIXVAXCommodore

SpreadsheetsMicrosoft Excel 2003 - 4.0Quattro Pro 5.0 - 2.0Lotus 123 2.1 and 1.02SCO Professional 2.1Supercalc

CommunicationsuucptelnetftpPC Anywhere 10.5 - 5.0PROCOMM PLUS for Windows ASPECT 4.5,

2.11, 2.0, 1.0ProComm 2.01 DOS ASPECT

Operating Systems

LinuxRedhatDebianCentOSKnoppix

UNIXAIX 5.2Solaris x86 2.xSCO 3.2v4Solaris 2.4-2.5AT&TNCRMotorolaMicroport System VZilog System IIIWicat System 7

XenixSCO 3.2 (286, 386), 2.4, 2.3, 2.2, 2.1, 1.2Xinu

MS-DOS6.22 - 2.2

WindowsXP

document.doc

4/9/09 Legend: ; ; ; ; of 35

Experience and Proficiency Technical Profile - Jason Loefer 2000 Server/ProfessionalNT 4.0, 3.5198 to SE95 to OEMSR2.5386/286 3.11 - 2.1

OtherOS/2 2.1, 1.2sPCDOS 7.0 - 5.0PC-MOSMTOSG4WDOSCP/MCommodore

Libraries

GeneralBorland Object Windows Library 2.0 and 1.0TurboVision 1.0

CommunicationsAsync Pro 5.0 - 2.1Magna CartaBlaiseGreenleaf

User interfaceInfragisticsInfoPowerC-WorthyVitamin CVermont ViewsCurses

DatabaseCodeBase 5.2, 5.0, 4.5, 4.2

Applications

Debuggers / ProfilersMutek AppSight 1.0Mutek Bugtrapper 3.0Microsoft Visual Studio C++Borland C++BuilderUNIX SDB / ADBBorland Turbo DebugBorland Turbo ProfilerMicrosoft CodeviewWinSightWinspector

Documentation (Word Processors / Publishing / Help / Spreadsheets)Microsoft Word 2005-1.0Microsoft PowerPointMicrosoft VisioCodeWrightAdobe Acrobat / Exchange / DistillerVentura Publisher

Word PerfectWordstarRoboHELPForeHelpDoxygenGraphvizMicrosoft Help Compiler

Version ControlCVS / WinCVSMicrosoft Visual Source SafeMKS Source IntegrityMKS RCSsccsmakenmakePVCS (MS-DOS & Windows) Version Manager /

Configuration Builder / TrackerPolyMAKE

Installation SDKsInstallShield 12, 11, 6.1, 5.5, 5.1, 5.0, 3.0InstallShield PackageForTheWeb 2.2Microsoft Setup Toolkit 2.0 - 1.0

CommunicationsPCAnywhere 10.5 – 5.0uucptelnetftpProComm (MS-DOS & Windows)MirrorR2CoSessionCarbon CopyBreak-out II

GraphicsPixar RendermanPixar TypestryMicrosoft PublisherABC FlowcharterHarvard GraphicsDesignCAD 3DEasyflowArts&LettersCorelMagic

Environments

DevelopmentMicrosoft Visual Studio .NET - 1.0Borland C++Builder 6.0 - 1.0Borland Delphi 5.0 - 1.0Borland C++ (all) Windows / DOSBorland C++ 5.02Borland Turbo C++Sun OpenWinUNIX System V - 7 command line

document.doc

of 35 Legend: ; ; ; ; 4/9/09

jloefer, 01/03/-1,

add Linux IDE front end

Technical Profile - Jason Loefer Experience and ProficiencyMS-DOSCP/M

Systems

Platform / targetIBM PC compatibles and CSS industrial chassis

Pentium 4 - I, Pro, 80486 - 8086Sun Sparc 10, 20, x86Motorola 2616, 1132, 1131 VME BusNCR Tower, XP, 1632Zilog System 8000 32, 31, 21VAX 11/750AT&T 6386/WGS, 6300, 7300, UNIX PC, 3B20,

3B2Apple Mac II, MacIntosh, 2e, 3Z80 SBCCommodore Vic-20

Embedded target80486HC11Z80 / Z280Z800080516802068056802

HardwareRS232 and RS422 serial portsparallel portsLCDGPSkeypadsjoystick portsbarcode scanner16550 and 8250 UARTPICDMA

FPUPICSIOPIOCTCsecurity access devicesfloppyfixed diskradiospagerspager programmers

Equipment

HardwareIn-circuit emulatorlogic analyzerPROM / EPROM / PAL programmernetwork analyzerT1/E1 analyzertrunk traffic generatoroscilloscope (digital storage, analog)signal generatorbench power supply2

RF service monitordata line monitor3

RS232 breakoutantenna base loadsignal strength meterSWR meterDMManalog voltmeter and ammeterVOMmeggerdegauserAC and DC motor / generator set, switchboard,

and controller up to 600VDC and 900KVA (1200hp)

2 I am also designing my own switching bench power supply.3 I also designed and wrote my own full duplex DLM.document.doc

4/9/09 Legend: ; ; ; ; of 35


Project DetailsProject Details

document.doc

of 35 Legend: ; ; ; ; 4/9/09


ComplianceFactory 1/2005 to Present

Was partially responsible for the design, development, and maintenance of several back-end web server applications for Business Software, Inc.

DESCRIPTION OF SYSTEM:The ComplianceFactory provides taxing authority compliance and reporting function for payroll processing entities.

Taxing authority rules and reports embodied in the product database are first configured with custom client company information via a Java front end application. These client companies then periodically provide employee payroll information via a number of APIs including file, XML, and library calls to the back end server daemon (UNIX / Linux) or services (Windows).

The back end servers continuously calculate and aggregate the various deductions and provide electronic and hard-copy payments and reports to the various taxing authorities based on the authorities’ rules.

The operating system / database support matrix is very large.

SPECIFIC RESPONSIBILITIES:I was partially responsible for engineering design, development, testing, documentation and support of ComplianceFactory. Database conversions from older database schema, database differencing, and maintenance of department internal test databases was also my responsibility.

Five direct reports.

TECHNOLOGY:The system was developed in MSVC 6.0 C using ODBC and in gcc embedded SQL.

document.doc

4/9/09 Legend: ; ; ; ; of 35


Snap (Special Network Applications Processor) 3/2003 to 12/2003

Was completely responsible for the design, development, documentation and maintenance of an Internet protocol interface front-end to a paging terminal for TGA Technologies, Inc.

DESCRIPTION OF SYSTEM:The SNAP (Special Network Applications Processor) provides a gateway function from Web, EMail, and SNPP clients into the TGA Technologies’ Prism paging terminal.

These Windows services accept inputs from Simple Network Paging Protocol (SNPP, RFC1645), EMail (SMTP), and Web (HTTP) clients, validate the subscriber or subscribers and forward messages to the paging terminal for queueing and broadcast over the paging network or over the air.

Another complimentary set of services forward messages generated in the paging terminal to outbound Simple Network Paging Protocol (SNPP) and EMail (SMTP) servers.

It features Windows service implementation, IIS front-end, automatic restart in case of system or service failure, ala carte service installation, STL email message classes for limitless message and queue sizes, HTML templates, Installshield deployment and much, much more.

SPECIFIC RESPONSIBILITIES:I was entirely responsible for developing requirements, engineering design, development, testing, documentation and support of SNAP.

TECHNOLOGY:The system was developed in Borland C++Builder 5.0 on a Windows 2000 Server PC.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


Prism GUI 1/1999 to 4/2003

Was completely responsible for the re-design, development, documentation and maintenance of a user interface applications for the configuration of a one-way paging terminal for TGA Technologies, Inc.

DESCRIPTION OF SYSTEM:The Prism GUI provides a user interface for configuration and control of TGA Technologies’ Prism paging terminal.

Over 40 Windows GUI applications to control, configure, and test various aspects of both analog and T1/E1 telephone trunk OEM cards, output RF channel control OEM cards, network interfaces, serial ports, and subscriber database.

Features included Windows SysTray presence, login challenge using hardware security device (dongle) communication, a tree view, dynamically configurable (scripted) application executive, and COM interfaces to the subscriber database engine and to the output encoder configuration which provided dynamic updates.

A support API was developed in Borland C++ Builder’s Visual Control Language to provide common library functions.

SPECIFIC RESPONSIBILITIES:I was entirely responsible for developing requirements, engineering design, development, testing, documentation and support of SNAP.

TECHNOLOGY:The system was developed in Borland C++Builder 4.0 and 5.0 and Microsoft Visual Studio 6 on Windows NT and 2000 workstations. A few applications were ported from Borland Delphi 4.0.

document.doc

4/9/09 Legend: ; ; ; ; of 35


DoBuild 3/2003 to 12/2003

Was completely responsible for the design, development, documentation and maintenance of a completely automated build process for TGA Technologies, Inc.

DESCRIPTION OF SYSTEM:What started out as a few makefiles and a simple Windows NT batch program developed into a fully automated, ONE KEYSTROKE activated build process which performs a complete cross-platform build of a two-way radio paging system operating system, it's support APIs and applications.

The processing included Borland C++Builder, Visual Studio 6 and .NET command line interfaces and makefiles for each of the compilers' native make utilities, complete compiler output capture, error detection, and error compilation, check in, check out and labeling of CVS source and target repositories, kickoff of concurrent remote Linux build, automatic email step completion notifications to broadcast list, zip compression of resultant output files, and ftp upload scripting.

In addition, the same code would run not only on build systems, but was also used by the developers to build code for which they were responsible or check out binaries for which they were not. It was primarily written in little more than Windows NT4 extended BATCH instructions, with a few MKS Toolkit programs and homemade ones, too.

It also had to be compatible with Windows NT4 and Windows 2000 development machines.

SPECIFIC RESPONSIBILITIES:I was entirely responsible for developing requirements, engineering design, development, testing, documentation and support of DoBuild.

TECHNOLOGY:The system was developed in Borland C++Builder 5.0, Microsoft Visual C++ 6, Windows NT4 and Windows 2000 batch commands, and MKS Toolkit Korn Shell on Windows NT and 2000 workstations.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


UniToPri (Unipage to Prism) 1/1999 to 4/1999

Was completely responsible for the design, development, documentation and maintenance of a program to convert the subscriber and configuration databases of a foreign OEM product to the company’s OEM product for TGA Technologies, Inc.

DESCRIPTION OF SYSTEM:Unipage is the name of a paging terminal manufacturer (and the name of the product). The UniPage Console is a PC-based user interface for the paging terminal which contains the esoteric, as well as the core portion of the subscriber database.

TGA was seeking to replace many of these terminals with their own product (the Prism). Many of these potential customers had a significant number of subscribers for which manual entry into the new system was prohibitively time-consuming, error-prone, and therefore expensive. Since I was familiar with both makes of systems. I was charged with developing a conversion program to deal with the problem.

UniToPri read the source data files in the form of a combination of binary, dBase II, and text files either from a fixed disk location, or from a compressed backup floppy, performed a somewhat sophisticated analysis of the data to clean and then convert it, optionally based on pre-configurable customer profiles.

Unconvertable records were saved and the user was given the opportunity to correct problems with individual records and re-run the program.

As a by-product of the analysis, the customer was given a statistical analysis of their database for performance tuning or marketing review.

SPECIFIC RESPONSIBILITIES:I was entirely responsible for developing requirements, engineering design, development, testing, and documentation of UniToPri.

TECHNOLOGY:The system was developed in Borland C++Builder 5.0, Borland Database Engine (BDE) on a Windows 2000 workstation.

document.doc

4/9/09 Legend: ; ; ; ; of 35


BSC (Base Station Controller) 6/1998 to 1/1999

Was completely responsible for the development and maintenance of a real time embedded BSC (Base Station Controller) for TGA Technologies, Inc.

DESCRIPTION OF SYSTEM:The BSC (Base Station Controller) provides a radio frequency control link to direct and control the broadcast output power levels and various other operating parameters and control the timing, synchronization, and transmission of paging output data to multiple one-way radio paging transmitters.

It features an embedded Motorola HC11 processor to manage reference timing from a GPS receiver via RS-422 interface to the high-stability oscillator, manage output signals and send output data. It also features an embedded Intel 80486 which provides supervision of the HC11, user interface control via an LCD screen output and keypad input, serial port supervision, and network interfaces.

SPECIFIC RESPONSIBILITIES:I was entirely responsible for hardware engineering liaison and continuing hardware requirements, software engineering development and maintenance, testing, documentation and support of the BSC.

TECHNOLOGY:The system was developed in HC11 assembly language (HC11), and Paradigm C++ 80486 cross compiler add-on to Borland C++ 5.02 (80486) on a Windows NT 4.0 development platform.

Updates and testing also required the use of FLASH memory parts and tools, as well as EPROM programmers.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


FileNamePad 10/98 to Present

Was completely responsible for the design, development, documentation and maintenance of a Windows Shell file and directory name clipboard application for MSW Engineering Services.

DESCRIPTION OF SYSTEM:FileNamePad is an application that provides a Windows user with the ability to reference objects from the Windows Explorer interface by only their file or folder names, as opposed to the objects themselves. This is particularly useful when only the file names themselves or their absolute paths are desired.

It can accept input from a number of sources: paste from clipboard, drag and drop, shell context menu, command line or Send To context menu.

It also optionally recurses folders to include files in subfolders, can optionally gather details about the subsequent list of files, such as CRC32, file length, attributes, short filenames, parts of filenames, such as the extension, basename, etc.

The processed list may then be copied to the clipboard, written to an output file, etc., for processing by another program.

A shareware version of this program is available upon request.

SPECIFIC RESPONSIBILITIES:I was entirely responsible for developing requirements, engineering design, development, testing, documentation and support of FileNamePad.

TECHNOLOGY:The system was developed in Borland C++Builder 3.0 through 5.0 on various Windows workstations. The full-color, duplex end-user documentation was authored in Microsoft Word 2000.

document.doc

4/9/09 Legend: ; ; ; ; of 35


WSerMon 7/96 to 12/99

Was completely responsible for the design, development, documentation and maintenance of a software serial data line monitor application for MSW Engineering Services.

DESCRIPTION OF SYSTEM:WSerMon, a contraction of “Windows Serial port Monitor” is a 32-bit Windows application that traces activity on RS-232 serial ports.

It operates in one of two modes: simplex or duplex. In simplex mode a serial port on the PC is attached to the serial device to be monitored and acts simply as a dumb terminal, decoding serial data as ASCII, plain text or hexadecimal. In this mode, hardware handshake line statuses are also monitored and displayed.

However, in duplex mode, which requires two serial ports on the monitoring PC and a special cable, WSerMon emulates a hardware data line monitor by transparently monitoring (and optionally recording) a serial conversation between two devices, complete with timing information.

A shareware version of this program is available upon request.

SPECIFIC RESPONSIBILITIES:I was entirely responsible for developing requirements, engineering design, development, testing, documentation and support of WSerMon.

TECHNOLOGY:The system was developed in Borland C++Builder 3.0 through 5.0 on various Windows workstations. The cable schematic was authored in Visio 5.0 Technical.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


TNPP Engine 5/1996 to 1/1997

Was completely responsible for the design, development, documentation and maintenance of a communications interface back-end to a paging network for Turner Broadcasting (CNN Interactive) and Paging Networks (PageNet).

DESCRIPTION OF SYSTEM:The TNPP Engine is an application that delivers CNN news feeds to all PageNet nationwide paging subscribers.

The application accepts input from a scheduler which, in turn accepts news feeds from both editors and automated news wire sources. It then categorizes, formats and delivers this information via paging industry standard network protocol to the RCC’s (radio common carrier) point of presence via leased line connection.

It features serial communications class definitions, news drop categories (classes), UNIX IPC, hot re-configuration, message queuing, multi-level error logging, modem configuration, dial backup-up, critical error detection, alarm reporting, and full color, duplex documentation.

SPECIFIC RESPONSIBILITIES:I was entirely responsible for developing requirements, engineering design, development, testing, documentation and support of the TNPP Engine.

TECHNOLOGY:The system was developed in C++ and C-shell on a Solaris 2.5 (UNIX) x86 and ported and implemented on a SPARC 5 workstation.

document.doc

4/9/09 Legend: ; ; ; ; of 35


Energy rate conversion 10/1996 to 1/1997

Was partially responsible for the maintenance and conversion of billing utility energy rate analysis and conversion for EnerLink, a former Southern Company subsidiary.

DESCRIPTION OF SYSTEM:Enerlink was converting their energy supplying clients from a coordinate text graphics MS-DOS application to a Windows GUI version. The program, which is used by EnerLink’s clients, accepts raw meter data from the energy supplier’s industrial clients. Applying given energy-over-time, peak demand parameters, etc., analysis is performed and various rates based on legislated tariffs result in a billing solution.

Most “rates” (the energy industry term for the programmatical embodiment of a tariff) were in existance when the old system was being replaced and had to be converted. As well, new tariffs came into existance which also had to be programmed into the new system.

In addition, analytical functions embodied in the program could help industrial customers plan for peak efficiency, minimum cost, and minimize impact on the power grid.

SPECIFIC RESPONSIBILITIES:I was partially responsible for ongoing maintenance, rate conversion, rate analysis and programming, and the addition of statistical analysis functions to the utility rate program.

TECHNOLOGY:The system was implemented in proprietary scripting language for IBM AT compatibles under Windows and MS-DOS.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


Portia 6/1996 to 9/1996

Was partially responsible for the maintenance of a billing database utility for Southern Company.

DESCRIPTION OF SYSTEM:Portia was the Delphi application that performed business analysis on energy subscriber accounts for accounting, marketing, and sales departments.

SPECIFIC RESPONSIBILITIES:I was partially responsible for ongoing maintenance and the addition of statistical analysis functions to Portia.

TECHNOLOGY:The system was implemented in Borland Delphi for the IBM AT compatible under Windows.

document.doc

4/9/09 Legend: ; ; ; ; of 35


MTOSIF (MTOS Interface) 9/1995 to 11/1995

Was mostly responsible for the design, development, documentation and maintenance of a GUI communications script interface to a proprietary operating system for regional bell operating companies and radio paging common carriers.

DESCRIPTION OF SYSTEM:MTOSIF is an application that provides reliable communications and file transfer capability externally to an operating system and application that have no inherent communications capability for the purpose of maintenance of operating system and application software.

It features full color duplex documentation and on-line, context-sensitive help, both of which I also personally developed.

SPECIFIC RESPONSIBILITIES:I was mostly responsible for developing requirements document, engineering design, development, testing, documentation, support and demonstration of MTOSIF.

TECHNOLOGY:The system was implemented in PROCOMM PLUS for Windows version 2.11 ASPECT script language for the IBM AT compatible under the Windows operating system.

document.doc

of 35 Legend: ; ; ; ; 4/9/09

jloefer, 01/03/-1,

add AT&T API, interface library for Pizza Hut before MTOSIF


ALFADB 2/1995 to 4/1995

Was completely responsible for the development and maintenance of a communications and database conversion utility for regional bell operating companies and radio paging common carriers.

DESCRIPTION OF SYSTEM:The ALFADB application is a utility to transfer subscriber databases between two versions of an AlphaMate™ alphanumeric paging device.

My own custom library as well as Magna Carta communication library was required to communicate via serial port to the hardware devices. Intimate knowledge of the internal database transfer protocols of both machines was required.

The core of the software was designed to target both MS-DOS and Windows. The Windows version is harnessed by a purely C++ interface program.

SPECIFIC RESPONSIBILITIES:I was solely responsible for engineering design, development, testing, documentation, support and demonstration of ALFADBW.

I saw a need to develop this application, and used the opportunity to learn Windows programming. I developed it completely on my own personal time and gave it to the company to do with as they saw fit.

TECHNOLOGY:The system was implemented in C++ and C for the IBM AT compatible under the MS-DOS and Windows operating systems.

document.doc

4/9/09 Legend: ; ; ; ; of 35


Message Maker™ 4/1994 to 6/1994

Was completely responsible for the development and maintenance of a static message entry paging terminal device for regional bell operating companies and radio paging common carriers.

DESCRIPTION OF SYSTEM:The Message Maker™ is a means by which callers wishing to send alphanumeric pages to alphanumeric pager subscribers may do so without the need for alphanumeric paging input devices; The page may be made from any telephone. This is especially important to carriers because this reduces the trunk hold times significantly over traditional DTMF to ASCII conversions some paging terminal manufacturers require. It also elleviates the need for expensive alphanumeric transcription operators.

This project has enjoyed very high degree of visibility, as it was an idea of the President of Motorola himself, Mr. Chris Galvin. It was also a centerpiece at the P.C.I.A. show in September, 1994 in Seattle. I was chosen out of the many engineers in the Ft. Worth operation to develop this application.

SPECIFIC RESPONSIBILITIES:I was solely responsible for engineering design, development, testing, documentation, and demonstration of Message Maker™.

TECHNOLOGY:The system was implemented in C++ and FoxPro for the IBM AT compatible under the MS-DOS operating system.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


NETTNP 11/1992 to 9/1995

Was partially responsible for the development and maintenance of paging terminal networking firmware for regional Motorola, Inc., Advanced Messaging Systems division.

DESCRIPTION OF SYSTEM:The network firmware interconnects radio paging terminals via dedicated leased line, RF, dial-up, or satellite link. Paging traffic, database updates and queries, as well as paging terminal commands and data are passed from node to node using an industry standard protocol (Telocator Network Paging Protocol, or TNPP).

Many fixes and improvements were being made to this firmware including a transparent acknowledgment scheme in which response characters to the far end may be inserted into the outgoing data stream. Also load balancing, table-driven CRC, etc.

SPECIFIC RESPONSIBILITIES:I was solely responsible for maintenance of NETTNP and development of NETROUT, as well as testing, documentation of both.

TECHNOLOGY:The system was implemented in Z80/Z280 assembly language for the OEM CPU boards under proprietary operating system.

document.doc

4/9/09 Legend: ; ; ; ; of 35


MRS (Management Reporting System) 9/1991 to 10/1992

Was completely responsible for the design, development, technical writing, installation, and training of a MRS (Management Reporting System) for regional bell operating companies and pay telephone owner/operator/aggregators.

DESCRIPTION OF SYSTEM:The MRS manages databases for the Protocall 2000 subsystem, generates one-plus invoices for direct billing, generates EMI (Exchange Message Interface) for billing zero-plus traffic, as well as traffic statistics and other reports.

SPECIFIC RESPONSIBILITIES:I was solely responsible for design, development, testing, documentation, installation, troubleshooting of and training for the MRS.

TECHNOLOGY:The system was implemented in FoxPro/LAN 2.0, Microsoft C, and Microsoft LAN Manager 2.1 for the 80x86 AT platform under DOS 5.0. It interfaces (via LAN) to applications written in C and using CodeBASE 4.5 for 80x86 AT platforms under OS/2 1.3 and 2.0. These platforms, in turn, interface (via Dialogic Springboards and DT101 (T1 interface cards)) to the Harris 20/20 T1 telephone switch.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


AAS (Agent Access System) 6/1989 to 12/1990

Was mostly responsible for the contract, specification, design, development, technical writing, installation, and training of an AAS (Agent Access System) for radio common carriers and telephone companies.

DESCRIPTION OF SYSTEM:The Agent Access System is used by an RCC or telephone company to provide agents with controlled access to paging terminal resources in an AT platform. It combines a high-speed data link to the paging terminal and transaction logging on the back-end with a layered, high-security, full-screen front-end featuring on-line, context-sensitive help and adjustable over- and under-usage logouts.

Written in C and using UNIX IPC message queues and semaphores, the AAS can be ported to any 286, 386, or 486 UNIX or Xenix platform. The AAS engine alone has great potential for use in many other applications, and we hold exclusive rights to it.

SPECIFIC RESPONSIBILITIES:With an attorney, I composed the sales contract. I composed the design specification for customer approval. I designed, developed and extensively tested the engine that is the core of AAS, as with a vast majority of the attendant software including custom(ADM) installation, and my own version of uucp callback.

I wrote the technical, user's, and agent's manual, which include a generated table of contents, an index, and appendices showing and describing the screens in Ventura Publisher.

I helped to install the prototype system and train their people.

TECHNOLOGY:The system was implemented in C using UNIX IPC, CURSES, named pipes, etc., Bourne shell, and SCO Project Engineering Toolkit (installation) for the 80x86 AT platform under SCO Xenix 2.3.3.

document.doc

4/9/09 Legend: ; ; ; ; of 35


MBA (Mobile Billing Accumulator) 6/1989 to 2/1990

Participated in the development, support, maintenance of a MBA (Mobile Billing Accumulator) for telephone companies and radio common carriers.

DESCRIPTION OF SYSTEM:The MBA provides synchronous collection SMDR (Station Message Detail Recording) records from multiple mobile telephone exchanges for processing into billing records. This is done internally, and the billing data is uploaded via uucp to the mainframe billing computer.

It features hardware backup of billing data, which is accessed via polling in the event of system failure, hardware alarms in the event of de-synchronization, remote hardware diagnostics, a menu-driven, screen-oriented user interface, and scheduled backups.

This application was originally supported by a major paging OEM, and was given over to myself and an associate to maintain and develop for the existing customer base.

SPECIFIC RESPONSIBILITIES:I programmed quite a few of the internals of the newer Xenix version.

Provided disaster recovery.

TECHNOLOGY:The system was implemented in NCR C, SCO/Microsoft C using CURSES, C shell and Bourne shell for the NCR Tower, XP, 1632 and 80x86 AT platform under UNIX System V and SCO Xenix.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


MMI/NSR2 (Man/Machine Interface) 8/1989 to 2/1990

Participated in the development of a MMI/NSR2 (Man/Machine Interface) for Northern Telecom.

DESCRIPTION OF SYSTEM:Written in C for the MS-DOS environment, this application is a DE-4E smart T1 channel bank network manager.

It provides remote supervision, configuration, and analysis of T1 telephone switches throughout a channel bank network.

My company was a prime mover in a six-man team on this project which topped $25 million in gross sales.

SPECIFIC RESPONSIBILITIES:I wrote approximately 12-15 of the 90+ modules that comprised NSR2 (a 360K application at last glance).

Assisted junior company programmers with design, practical, and implementation questions, as well as language nuances.

I was assigned the task of converting from Microsoft C v5.1 to Turbo C v2.0.

I designed, wrote and implemented the version control system, and check-out procedures used for development. It was written in the MKS Korn shell using Polytron PVCS.

TECHNOLOGY:The system was implemented in Turbo C v2.0 and Microsoft C v5.1 using Vitamin C screen libraries, MKS Korn shell for the 80x86 AT platform under MS-DOS.

document.doc

4/9/09 Legend: ; ; ; ; of 35


Starlink 4/1989 to 6/1989

Participated in the development of a smart pay telephone network manager (Starlink) for a pay telephone OEM.

DESCRIPTION OF SYSTEM:Starlink is an AT-based pay telephone network manager. It serves as a central office switch. It provides smart pay telephones with zero-plus calling card and credit card validation.

When a subscriber places a calling card call with zero plus the number, the pay phone dials up the Starlink and forwards call information. The Starlink, dials up the validation entity, logs in and validates the number. Upon a validation, the Starlink dials the 1+ number direct, and patches the subscriber through.

The voice patch, voice file playback and recording, tone and cadence detection, and tone generation are done via multi-channel Dialogic ADPCM cards.

The application that drives the Starlink is a real-time, finite state machine and provides multiplexed calling card validation. The validation is handled via dialup link to NDC's X.25 hub via US Sprint's network.

SPECIFIC RESPONSIBILITIES:I was responsible for implementing the move from voice cadence-detection validation to data link validation, which required serial communications, a Hayes compatible command set and interface to the state machine.

I also designed and implemented the process by which Starlink machines encrypt, store and forward billing information back to the company which provided third-party billing.

I also co-wrote the third-party billing software in Clipper to specification.

TECHNOLOGY:The system was implemented in Microsoft C v5.1 using Vermont Views (Starlink) and Clipper Summer '87 (billing package). for the 80x86 AT platform under MS-DOS.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


CIIO/CVT (Computer Interface I/O / Converter) 6/1987 to 8/1988

Was solely responsible for design, development and implementation of a CIIO/CVT (Computer Interface I/O / Converter) for a radio paging, mobile telephone, and voice messaging OEM.

DESCRIPTION OF SYSTEM:Originally written on a UNIX system, this application provides serial computer interface access to a paging terminal subscriber database.

In conjunction with CVT (a database conversion program that converts records from the older to the newer paging terminal format), CIIO allows a customer in need of a system upgrade to choose our company's new paging product because we support the conversion of the database - little need for them to look for another manufacturer's product, if we can save 150,000 hand conversions.

The later version was ported (CVT without modification) to MS-DOS, so that a field service engineer can make the cut-over to the new terminal on the customer site in a matter of an hour or two.

SPECIFIC RESPONSIBILITIES:I designed and implemented the program, including customer interface for input on specifics and customization of the conversion.

TECHNOLOGY:The system was implemented in Zilog C and Turbo C v1.5 / Turbo Assembler v1.0 (80x86) for the Zilog System 8000 and 80x86 AT/XT platform under Zilog UNIX System III and MS-DOS.

document.doc

4/9/09 Legend: ; ; ; ; of 35


DLO (Data Logging Option) 3/1988 to 5/1988

Was solely responsible for the design and development of a Traffic statistics monitor; DLO (Data Logging Option) for a radio paging, mobile telephone, and voice messaging OEM.

DESCRIPTION OF SYSTEM:This application was designed to gather SMDR (Station Message Detail Recording) records from the traffic statistics port of an output module in a paging terminal. These records represent a real-time accounting of paging throughput in the terminal and are transmitted via high-speed RS232C port, and provide telephone company or radio common carrier personnel with additional diagnostic capability than that offered by the terminal itself. It was designed to operate on an external PC and gather these records from this port and format and display them into readable format.

It was displayed at the 1988 Telocator show in Atlanta alongside the new paging terminal, and quickly won the admiration of the President of the company.

The DLO was the predecessor of an application called ETS (External Traffic Statistics) which would have provided statistical analysis of aspects of the frames efficiency from port and trunk usage, over- and under-loading, and potential growth and expansion possibilities in advance of their necessity.

It featured an interrupt-driven ISR for serial communications, full-screen display, scroll down data window (latest record displayed at the top), ACK/NAK, XON/XOFF, hardware handshaking (or a combination), and ping pong buffering. This functionality was encompassed by a COM file less than 900 bytes long, and would withstand a constant 19200 baud data stream (the fastest the DOCM would go).

I just recently resurrected this program, and it serves as the basis for a serial communications library package I am presently implementing in C++ and Turbo assembler IDEAL mode 80x86 assembly language to provide multiple high-speed simultaneous COM port usage for applications developers.

SPECIFIC RESPONSIBILITIES:I designed and wrote the entire program.

TECHNOLOGY:The system was implemented in 8086 assembly language for the 8086 XT/AT (Compaq III) under MS-DOS.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


DSKIO (Disk I/O) 6/1987 to 8/1988

Was solely responsible for design, development and implementation of a DSKIO (Disk I/O) for a radio paging, mobile telephone, and voice messaging OEM.

DESCRIPTION OF SYSTEM:A spin-off of CIIO/CVT, this application alleviates the time-consuming bottleneck of serial I/O and directly reads and writes several non-DOS format paging terminal subscriber database backup diskette types. It can also read and write streaming tape media from several paging terminals.

We can now convert (in tandem with CVT) that database to the desired paging terminal record and media format in a matter of minutes, and the customer loses NO record changes when cutting over to the new paging terminal.

This application required direct access and modification of the disk base table to alter the access parameters of a particular type of floppy. This program has encountered a recent resurrection as well.

The SCSI tape drive interface was accomplished with the help of a Future Domain SCSI controller, which was programmed directly to modify it's tape write characteristics to those of the paging terminal's.

SPECIFIC RESPONSIBILITIES:I designed and implemented the program.

TECHNOLOGY:The system was implemented in Turbo C v1.5 and v2.0 / Turbo Assembler v1.0 (80x86) for the 80x86 AT/XT platform under MS-DOS.

document.doc

4/9/09 Legend: ; ; ; ; of 35


System III 6/1985 to 5/1986

Was solely responsible for the maintenance and enhancements of a System III Recorder and Digital Link (DLM) Modules for a radio paging, mobile telephone and voice messaging OEM.

DESCRIPTION OF SYSTEM:This paging terminal module was part of many such embedded processors with their own peripherals (PIO, SIO, CTC, memory, etc.) that comprised the overall paging terminal or mobile telephone exchange or voice messaging system, or a combination thereof.

Some modules processed incoming pages or calls via trunking, others processed digital pages, another networked the terminals together, some buffered, stored and replayed voice messages, others controlled the databases and system alarms, etc. Most were Z80 based, although the Z8000 and 68010 were later used extensively.

The modules I was responsible for maintaining and improving were:

The Recorder Module. This Z80-based module was responsible for digitizing voice messages received by the trunk module, and playing them back at the appropriate time to the output module for broadcast.

The DLM Module. This Z80-based module was responsible for a type of token-ring implementation of network paging, wherein many paging terminals could be arranged in MANs or LANs so that a single pager could be paged in several different cities around the country or the world almost simultaneously.

Several patents are registered to the company for this product.

SPECIFIC RESPONSIBILITIES:I maintained both of these modules and implemented quite a few enhancements and bug fixes.

TECHNOLOGY:The system was implemented in Z80 assembly language for the System III, MTX, VRS terminals under an embedded OS.

document.doc

of 35 Legend: ; ; ; ; 4/9/09


Index

.NETexperience.....................................................................5proficiency......................................................................5projects........................................................................14

80x86 assemblyexperience.....................................................................5proficiency......................................................................5projects............................................................31, 32, 33

AIXexperience.....................................................................5proficiency......................................................................5

assemblers.......................................................................7assembly language...............See specific CPU or microBorland C++Builder................................See C++BuilderBorland Delphi.................................................See DelphiC

compilers.......................................................................7experience.....................................................................5proficiency......................................................................5projects....................................23, 26, 27, 28, 29, 30, 31

C++compilers.......................................................................7experience.....................................................................5proficiency......................................................................5projects..................13, 14, 15, 16, 17, 18, 19, 23, 24, 32

C++Builderexperience.....................................................................5proficiency......................................................................5projects..........................................12, 13, 14, 15, 17, 18

databases....................................................See also SQLDelphi

experience.....................................................................5proficiency......................................................................5projects..................................................................13, 21

interpretersBASIC............................................................................7PASCAL.........................................................................7SQL................................................................................7

MS-DOSexperience.....................................................................5proficiency......................................................................5projects..............................20, 23, 24, 29, 30, 31, 32, 33

PASCAL............................................................See DelphiPC-MOS

experience.....................................................................5proficiency......................................................................5

Solaris.................................................................See UNIXprojects........................................................................19

SQLexperience.....................................................................5proficiency......................................................................5

UNIXexperience.....................................................................5proficiency......................................................................5projects......................................................19, 27, 28, 31

VBexperience.....................................................................5proficiency......................................................................5

VBAexperience.....................................................................5proficiency......................................................................5

VBScript...............................................................See VBAVCL...........................................................See C++BuilderVisual Basic...........................................................See VBVisual Basic for Applications............................See VBAVisual Component Library (VCL)...........See C++BuilderWindows

experience.....................................................................5Windows

proficiency......................................................................5projects..............5, 12, 13, 14, 15, 17, 18, 20, 21, 22, 23

Xenix...................................................................See UNIXZ80 assembly

experience.....................................................................5proficiency......................................................................5projects..............................................................5, 25, 34

document.doc

4/9/09 Legend: ; ; ; ; of 35

technical profilehome.windstream.net/jloefer/resume/techprof.doc · web viewantenna base load...

Documents