EMAILS Announcing

“Strategic Perspective – Analysis Needs (SPAN-2004) Survey”

 

Quick Reference Links: (in Word, Use [Ctrl]+Click to Jump..)

 

The Follow-Up Email (To Programmers & Analysts)

The Initial Announcement (To Task Scientists, et al.)

 

FOLLOW-UP Email (to Programmers & Analysts)

 

From: Johnny J. Weissmuller [johnnyw@codap.com]

Sent: Saturday, May 01, 2004 1:58 PM

To: <Programmer-Analyst List>

Subject: The AFHRL Legacy (Data)- Follow-up

 

Dear ex-AFHRL Programmer/Analysts/Auditors/Data Base/Study Tracking Personnel,

 

I know most of you. (Some of you were referred to me by Dick Rogers & Others). 

 

Side Note: If you have an electronic copy of GDIT or STUDY-STATUS (SS/JOCAS

- with study numbers & titles) I would really like to get a copy!

 

==== ACTION ITEMS ====

I am specifically looking for programmers/analysts who dealt directly with one or more AFHRL Master Files or its tracking (GDIT) or coding (FIDO) systems.

 

== Item 1:==

I need MORE CONTACTS in this area -- people who knew or indexed the Master Files. Darryl -- if you have Jim Glanden's email address or John Hughs, I really want those and others you may have.  Please review your email address book for those long-forgotten entries of the guardians of the AFHRL master files and those who made it accessible.

 

== Item 2:==

If you know me, you know that I "grew up" in the occupational survey arena and had little actual contact with the Master Files.  For this reason I have very little insight as to the kinds of DATA ELEMENTS requested from Master Files by "mainstream" Task Scientists.  If you could provide me with your personal list of "DATA ELEMENTS I HAVE KNOWN (and loved or hated)! I would appreciate that.  I know we will have the standard ones (the ones I actually used!) - NAME, SSAN, AFQT, and the Air Force ASVAB COMPOSITES (Mech, Admin, Gen, Elec). If you could give me a quick list that you can remember with (or without) references to other people I would be in your debt.  -- Johnny

 

=== BACKGROUND INFORMATION ===

 

Here is the kind of information I hope to get from you and all those you refer to me...

 

====== DO NOT ACT (YET) UPON THE FOLLOWING EXCEPT TO PROVIDE YOUR RESPONSE TO QUESTIONS RAISED BELOW AS WELL AS YOUR SUGGESTED ADDITIONS OR REVISIONS FOR THE UPCOMING SURVEY ===

 

NOTE: The following are EXAMPLES of the survey input & results for programmer/analysts -- I am NOT asking you to address these questions yet, just give you an idea of where I am headed in developing the survey.  I will try to tailor separate sections for psychologists (linking "type of data" to "personnel system benefits") and for programmer/analysts (linking " Actual Master Files" to "types of data") -- but anyone who wants may respond to either or both sections.

 

QUESTION 1: Heres a format question about "YOUR USE OF Master files or data

elements": Which do you think would be better -- to ask for "relative frequency" of use (like an estimated count of the STUDY Numbers you worked

on) or "percent of your career time working with data from.." (and ask for total number of years worked)?

 

Here are examples of what I hope to get from the programmer/analyst survey.

  At present, I expect to ask, "In your experience with AFHRL over the years, what was the relative frequency (% of studies) with which you used the following historical files..." (list would follow). Results for DIFFERENT individuals might show the following:

 

EXAMPLE 1:

In the studies I was associated with, the most used files, in descending order were:

 

(Airman Studies Profile)

55% UAR Extract

20% UAR Master

20% PACE File

15% AFEES/MEPS (ASVAB subtest scores)

10% Airman Gain & Loss File ... etc.

 

(Officer Retention Studies Profile)

EXAMPLE 2:

40% Separated Officer File

30% UOR Master

20% AFOQT Master

15% Flying Training Data Base

 

(Occupational Analysis Projects Profile)

EXAMPLE 3:

95% Occupational Survey Files from AFOMS (aka USAFOMC)

20% Data from new/custom surveys

15% UAR Extract

10% AFEES/MEPS (ASVAB subtest scores)

 

(Recruiting/AFOQT/ASVAB Studies)

EXAMPLE 4:

55% AFEES/MEPS (ASVAB on applicants)

50% UAR

45% AFOQT Master

45% UOR Extract

 

I know that people like Mike Staley would have a hard time with this if I just ask across "your entire career at AFHRL". (He worked in the Data Base Section and then moved to the CODAP Programming section -- two diverse profiles).

 

QUESTION 2:  Should I ask people to indicate a DATE RANGE & Job Title and respond for that range -- and allow people to define multiple ranges (one per job type at AFHRL?)

 

Any way, please provide me names, email addresses and your thoughts –

 

-- Johnny

 

 

The Initial Announcement (To Task Scientists, et al.)

 

 

From: Weissmuller Johnny J Civ AFPC/DPPPWT

Sent: Wednesday, April 28, 2004 3:07 PM

To: <Task Scientist & Interested Parties List>

Subject: FW: The AFHRL Legacy (Data)

 

 

Dear ALL,

 

If you want to see extended background of the AFHRL legacy (data) see the “Data Files” link on this web page: (Use Ctrl+Click to Jump in Word) <http://www.icodap.org/papers/AFHRL/index.html>

 

==== Please Read =====

 

I need to perform a short suspense "needs" analysis to drive a requirements statement due in 2-1/2 weeks. I will be forwarding results to Mr. Ken Schwartz AFPC/DPPPWT who is formally charged with submitting the Requirements Statement. (See driving reasons in BACKGROUND below).

 

ACTION ITEMS:

 

I am asking for your help on three fronts.

 

FRONT 1:  Will you provide me with an email address for ANYone who qualifies as any of the following: 

 

A. An ex-AFHRL/AL/AFRL researcher/analyst/programmer,

B. A person who used to write "Requests for Personnel Research" (RPRs) to the lab,

C. A provider of data from an internal (AFPC or MPC)or external (AETC, ROTC, OTS) source, or

D. A Contractor using or supplying personnel-system related data, methods, or software

 

FRONT 2: Will you provide me with suggested topics for a quick-turn-around survey to identify TOPICS that AFPC should consider in evaluating the "worth" of historical data -- i.e. research streams that make sense in the modern environment (see Background below). I need to solicit some type of linkage between the needs TOPICS and traditional (or new) data elements/files/sources -- including standardized submissions of data and code structures.  Examples should span areas such as accession evaluation (recruiting/ASVAB/AFOQT) through classification, assignments, training (requirements & evaluation), promotion testing/WAPS, career development, force modeling & management, mentoring & outplacement.  Anything you can tell me would be appreciated.

 

FRONT 3: When I get a quick survey together, would you be willing to take the survey as an "expert witness."  Anonyomous replies will be used as long as your background info provided establishes your perspective, i.e. user/analyst/data OPR, etc. Would you be willing to participate (assume about a 10-20 survey.)  -- Johnny

 

P.S. The survey would be conducted by the ICODAP non-profit with results to be turned over the Air Force. If you don't want your identify released, I can guarantee your privacy will NOT be violated.

 

 

==== BACKGROUND INFORMATION ======

 

The Air Force Personnel Center is undergoing restructuring and realignment.  Three current  goals at AFPC include downsizing to get within end strength limits, to rotate-out/deploy AFPC personnel and internal realignment to support the new Air Force-wide Force Development initiative. 

 

The data transferred to AFPC in 1999 is in jeopardy for a number of reasons. The MOA with DPX and AFRL expires 30 September 2004, but that's the least of our worries. TSgt Martinez, who came over with the data files, is the only person supporting the AFHRL data function. Part of the realignment is to replace military personnel with contractors ASAP.  TSgt Martinez's position was targeted for replacement in Dec 2004 -- then changed to September, then changed to 1 July, then change to be deployed three weeks from now (mid May 2004).  He has tried to document what he does.  Since coming to AFPC, however, he hasn’t maintained data flows from sources outside AFPC nor updated "FIDO" codes on data elements within AFPC.  DPX (AFPOA) has major contracts outstanding that want traditional AFHRL type data, but the sources have forgotten who they are and when data are negotiated on a case-by-case basis it is coming from "operational data systems" with short memories, volatile use of data columns and no "focal points" who can explain how data was collected, coded or stored for any recent fields.  Getting program changes implemented takes forever so many sources simply re-use existing variable names to hold new data which has not yet been accommodated officially.

 

The powers that be want to know what data (and sources & analysis tools) need to be documented in new MOAs to warrant evaluation for survival in critical resource allocations.  -- Johnny

 

Wireless:   (210) 379-6570  Home Phone: (210) 349-9001

Professional Web Page:  <http://www.codap.com/jjw>

Prefered Email Address: <mailto:johnnyw@codap.com>