Sie sind auf Seite 1von 24

Attachment 4 SF -182 Requirements

1 SF-182
A feature of the LMS manages employees SF-182 requests (The Request,
Authorization, Agreement, and Certification of Training form). An SF-182 is an
authorization form that employees shall submit to request outside training for
which there may or may not be a fee. It must be approved by up to six
approvers (depending upon agency). The form may serves as a purchase order
for the training provider.

2 SF-182 Functionality
The LMS for Peace Corps shall have SF-182 functionality as described in this
document.

3 Definition of Terms
The following terms are used in this Requirements Document.
In the LMS, employees logged in as learners shall be referred to as
Requestors.
Users with a variety of permissions for accessing, approving, and
updating Requestors SF-182 requests shall be referred to as
Administrators.
A Requestors immediate supervisor shall be referred to as the
Supervisor.
A Supervisors immediate supervisor shall be referred to as the Manager.
An Administrator with permissions to update LMS configurations shall be
referred to as a System Administrator.
Training managed and approved via an SF-182 shall be referred to as a
Class.
The entity providing the requested Class shall be referred to as a Vendor.
The term organization is used to represent configured organizational
breakdowns. Depending upon a clients structure, it may be organization
or another classification such as agency, department, division, location or
accounting unit.

4 Requirements
4.1 System Administrator
System Administrators shall be able to configure the input criteria for an
SF-182 according to the clients requirements.
System Administrators shall be able to populate reference values from
which various fields can be selected and against which various fields can
be edited (such as Vendors, Appropriation Funds, and all of the fields
required for EHRI reporting).

Page 1 of 24
Attachment 4 SF -182 Requirements

System Administrators shall be able to configure approval processes for a


submitted SF-182, preferably with the option for different processes by
vendor type (Federal and non-Federal), organization, and Requestors role.
System Administrators shall be able to configure approval processes for a
verified SF-182, preferably with the option for different processes by
organization and Requestors role.
System Administrators shall be able to designate roles and permissions
relating to SF-182 processing for Organization Administrators, Training
Administrators, Supervisors, and Requestors.
4.2 Organization Administrator
Administrators shall be able to approve a submitted SF-182 for a user in
and organization for which he has permissions on behalf of a configured
approver.
Administrators shall be able to approve a verified SF-182 for a user in an
organization for which he has permissions on behalf of a configured
approver.
Administrators shall be able to withdraw a submitted SF-182 for a user
in an organization for which he has permissions on behalf of a configured
approver.
Approvers shall be able to designate another user as a temporary
approver in his stead.
4.3 Training Administrator
Training Administrators shall be able to view some or all SF-182 requests,
subject to organizational configurations.
Training Administrators shall be able to view some or all SF-182
verification requests, subject to organizational configurations.
Training Administrators shall be able to approve SF-182 verifications if
included in the approval process.
4.4 Supervisor
Supervisors shall be able to view SF-182 requests for their direct and
indirect reports.
Supervisors shall be able to approve SF-182 requests if included in the
approval process.
Supervisors shallbe able to approve SF-182 verifications if included in the
approval process.
Supervisors shallbe able to print SF-182s that have been approved in
order to send a copy of the form to the procurement team.

Page 2 of 24
Attachment 4 SF -182 Requirements

4.5 Requestor
Requestors shallhave the ability to view a list of all forms, including identifying
information and action options to:
Create a new form: When selected, the Requestor is presented with a
blank form and options to:
> Enter some, all, or no information and cancel out of the form (with a
pop-up confirming cancelation)
> Complete some or all information, save, and exit
> Complete some or all information and request that the entered
information be edited
> Complete all information and submit, which invokes editing and allows
submission only if error free (with a pop-up confirming submission)
View an existing form: When selected, the Requestor is presented with
the pre-populated form with options to:
> Exit
> Edit the form, which converts the action to Update an existing form
Update an existing form: This option is available only for requests that
have not been submitted, withdrawn, or deleted. When selected, the
Requestor is presented with the pre-populated form with options to:
> Update some, all, or no information and cancel out of the form (with a
pop-up confirming cancelation)
> Update some or all information, save, and exit
> Complete some or all information and request that the entered
information be edited
> Complete all information and submit, which invokes editing and allows
submission only if error free (with a pop-up confirming submission)
Delete an existing form: This option is available only for requests that
have not been submitted or withdrawn. When selected, the user is
presented with the completed form and a pop-up to either confirm
deletion or cancel. When deletion of a form is confirmed, the application
must flag the form as deleted and prevent any future actions on the form.
Withdraw a request: This option is available only for requests that have
been submitted and completion has not been verified.
Submit an existing request: This option is available only for requests that
have not already been submitted. Selection of this option invokes editing
and allows submission only if error free (with a pop-up confirming
submission). Upon submission, the Requestor shall be able to view the
approvers to whom the request will be forwarded.
Copy an existing request form to create a new form: This option is not
available for forms that have been deleted. When selected, the Requestor

Page 3 of 24
Attachment 4 SF -182 Requirements

is presented with a form that is pre-populated with all of the information


from the copied form but with a new request identity.
Print a form: this option is not available for forms that have been deleted.
When selected, the user is presented with the form in .pdf format with
standard printer options.
Verify completion status: This option is available only for an approved
request and only after the end date of the Class. When selected, the
Requestor is presented with two options, Complete and Incomplete.
4.6 Approvals
An automated e-mail shall notify an approver when a submitted request
is in his queue for approval.
An automated e-mail shall notify an approver when a verified request is
in his queue for approval.
An approvers home page shall include indication that he has pending
approvals.
An approvers home page shall include a link to navigate to his list of
approvals queue.
An approver shall have the ability to view his approval queue, select one
or all pending approvals, and approve or deny.
An approver shall have the ability to record a comment related to an
approval or denial that shall be available for future viewing or reporting by
the approver or the Requestor.
4.7 Roles and Permissions
Roles and associated permissions must be configurable for the System
Administrator, Organization Administrators, Training Administrators,
Supervisors, and Requestors.

4.8 The SF-182 Request Form


The following section outlines the requirements specific to the SF-182 Request
Form. The form must follow the format specified by the Office of Personnel
Management.
4.8.1 General Requirements
SF-182 requests are generally available only for employees. Access by
employee type shall be a configurable option.
The data entry screen shall mirror the official SF-182 form, including the
lettering for each section and the numbering for each field.
Each request shall be stored within the application with the unique
identifier for the user and a unique identifier for the request (such as a
request number). The request identifier shall be displayed on the form and
wherever requests are reported or listed.
A configurable text box shall be available for each section in which client-
specific instructions can be displayed.

Page 4 of 24
Attachment 4 SF -182 Requirements

Each field shall have the configurable option to be mandatory, optional,


or suppressed from display (ideally based on other criteria, such as
organization and role).
The fields identified with an asterisk* are required for EHRI reporting.
Appendix B contains a list of the EHRI fields and associated valid values.
Search functionality or dynamically-populated dropdown selections shall
be available for fields where limited fixed values are permitted.
Prior to permitting a request to be submitted, it shall be fully edited. This
includes validating field values, cross-editing between fields, and
adherence to configurable custom business rules.
If errors exist as a result of validation, the application shall highlight the
erroneous fields and display appropriate error messages.
Any invalid field shall prevent a form from being submitted.
There must be a configured option for each field to be pre-populated on
the form from data that exists elsewhere in the LMS. Agency Code shall be
pre-populated on all forms.
Search functionality shall be available for populating the Vendor.
Search functionality shall be available for populating the Appropriation
Fund.
There must be a configured option to display a message of instruction or
information after a form is submitted.
4.8.2 Heading Section
Field Requirement
A. Agency Code: agency sub Pre-populate with configured Agency Code
element and submitting office
number *
B. Request Status / Record Not needed
Action:

4.8.3 Trainee Information Section


Field Suggestion Validation
1. Applicants Name * Pre-populate with users
name (last, first middle
initial)
Do not allow update
First Five Letters of Last Pre-populate with the
Name * first five letters of the
users name
Do not allow update
2. Social Security Number * Not needed on the form
but is needed for EHRI
reporting; if it can be
derived elsewhere for
EHRI, do not include on

Page 5 of 24
Attachment 4 SF -182 Requirements

the form
3. Date of Birth * Not needed on the form
but is needed for EHRI
reporting; if it can be
derived elsewhere for
EHRI, do not include on
the form
4. Street Address
4. City
4. State/Province Optional edit per
client- configured
values
4. Postal Code
4. Country Optional edit per
client- configured
values
5. Home Phone Valid telephone
number format
6. Position Level: displayed Radio buttons One must be
as radio buttons for the selected
choices: Radio buttons for:
a. Non-supervisory
b. Manager
c. Supervisory
d. Executive
7. Organization Address 1
7. Organization Address 2
7. Organization City
7. Organization Optional edit per
State/Province client- configured
values
7. Organization Postal Code
8. Office Telephone Valid telephone
number format
9. Work Email Address Valid e-mail format
10. Position Title Optional edit per
client- configured
values
11. Does Applicant Need Radio buttons One must be
Special Accommodation? selected
If yes, please describe
below
12. Type of Appointment Optional edit per
client- configured
values
13. Education Level Optional edit per
client- configured
values

Page 6 of 24
Attachment 4 SF -182 Requirements

14. Pay Plan Optional edit per


client- configured
values
15. Series Optional edit per
client- configured
values
16. Grade Optional edit per
client- configured
values
17. Step Optional edit per
client- configured
values

4.8.4 Training Course Data Section


Field Suggestion Validation
1a. Vendor Name Optional search Or optional edit per
functionality to select client- configured
from an authorized list values
1a. Vendor Address 1
1a. Vendor Address 2
1a. Vendor City
1a. Vendor State/Province Optional edit per client-
configured values
1a. Vendor Postal Code
1a. Vendor Country Optional edit per client-
configured values
1b. Location of Training (if
same, mark box)
1b. Training Site Address 2
1b. Training Site City
1b. Training Site Optional edit per client-
State/Province configured values
1b. Training Site Postal
Code
1c. Vendor Telephone Valid telephone number
Number format
1d. Vendor Email address Valid e-mail format
2a. Course Title *
2b. Course Number Code
3. Training Start Date * Calendar icon Valid date
4. Training End Date * Calendar icon Valid date
5. Training Duty Hours * Numeric
6. Training Non-Duty Hours Numeric
*

Page 7 of 24
Attachment 4 SF -182 Requirements

Field Suggestion Validation


7. Training Purpose Type * Search/dropdown Valid per EHRI
functionality to select Reference Values
from a list of valid
values
8. Training Type Code * This field can be derived
from sub-type and need
not be included on the
form
9. Training Sub-Type Code Search/dropdown Valid per EHRI
* functionality to select Reference Values
from a list of valid
values
10. Delivery Type * Search/dropdown Valid per EHRI
functionality to select Reference Values
from a list of valid
values
11. Designation Type * Search/dropdown Valid per EHRI
functionality to select Reference Values
from a list of valid
values
12. Training Credit * Search/dropdown Valid per EHRI
functionality to select Reference Values
from a list of valid
values
13. Training Credit Type Search/dropdown Valid per EHRI
Code * functionality to select Reference Values
from a list of valid
values
14. Training Accreditation Radio buttons One must be selected
Indicator
15. Continued Service Radio buttons One must be selected
Agreement Required
Indicator
16. Continued Service Calendar icon Valid date
Agreement Required
Expiration Date
17. Training Source Type * Search/dropdown Valid per EHRI
functionality to select Reference Values
from a list of valid
values
18. Training Objectives
19. Agency Use Only

Page 8 of 24
Attachment 4 SF -182 Requirements

4.8.5 Costs and Billing Information Section


Field Suggestion Validation
1a. Tuition and Fee * Numeric; configurable
minimum and
maximum
1a.Tuition and Fee Search/dropdown Or optional edit per
Appropriation Fund functionality to select client- configured
from a list of valid values
values
1b. Books/Materials * Numeric; configurable
minimum and
maximum
1b.Books/Materials Search/dropdown Or optional edit per
Appropriation Fund functionality to select client- configured
from a list of valid values
values
1c. Direct Costs TOTAL Protected and
automatically populated
as the sum of 1a, 1b,
and 1c
2a. Travel Amount Numeric; configurable
minimum and
maximum
2a.Travel Appropriation Search/dropdown Or optional edit per
Fund functionality to select client- configured
from a list of valid values
values
2b. Per Diem Amount Numeric; configurable
minimum and
maximum
2b.Per Diem Appropriation Search/dropdown Or optional edit per
Fund functionality to select client- configured
from a list of valid values
values
2c. Direct Costs TOTAL Protected and
automatically populated
as the sum of 2a, 2b,
and 2c
3. Total Training Non-
Government Contribution
Cost
4. Document/Purchase
Order/Requisition Number
5. 8-digit Station Symbol
6. Billing Instruction

Page 9 of 24
Attachment 4 SF -182 Requirements

4.9 SF-182 Verification


After the completion date of the Class, the Requestor must record information
relating to the completion. A Class must be verified as Completed to appear in
the Requestors Completed Learning in the LMS and to be included in EHRI
reporting.
At minimum, the Requestor must indicate that the course was completed. In
addition, the Verification process may be configured to allow or require the
following additional information:
Actual Start Date (if other than per the original request)
Actual End Date (if other than per the original request)
Actual Duty Hours (if other than per the original request)
Actual Non-Duty Hours (if other than per the original request)
All Sessions were Attended (yes or no)
Comments
When the Requestor completes the Verification process indicating that the
course was complete, the application shall update the activity such that it
appears in the Requestors Completed Learning.

4.10 Notifications
Several automated e-mail notifications shall be available with configurable
from e-mail address, subject line, and message text.
Description Trigger Recipient
SF-182 Approval When SF-182 request is Request Approvers
Required submitted, triggered to the
first approver
When approved by an
approver, triggered to the
next approver (in a multi-
level approval process)
SF-182 Approval When an approver Requestor
Progressed approves and the request
moves to the next
approver (in a multi-level
approval process)
SF-182 Approved Final approval is made Requestor
SF-182 Denied An approver denies the Requestor
request
Reminder to Verify After the completion date Requestor
of the Class and optionally,
periodically until verified
SF-182 Verification When SF-182 Verification is Verification Approvers
Approval Required submitted, triggered to the
first approver

Page 10 of 24
Attachment 4 SF -182 Requirements

When approved by an
approver, triggered to the
next approver (in a multi-
level approval process)
SF-182 Verification Verification approval is Requestor
Approved made
SF-182 Verification An approver denies the Requestor
Denied Verification

The system shall be configured to leverage the various notifications available


in Totara.

4.11 Reporting
The LMS shall provide the following reports:
SF-182: This report is run for an individual SF-182 request and creates a
print-image of the SF-182 form.
SF-182 Data: This report, typically in .csv format, can be run with filters
such as organization, Requestor, approver, and approval date ranges and
provides a list of SF-182 requests with all associated data. This data shall
be integrated into the non-SF-182 training data available in the system.
Organization Approvers: This report lists all approvers and the entities for
which they are authorized to approve. It helps Administrators to ensure
that every entity has an approver and identify the approvers for an
individual user.
Users without Approvers: This report identifies users for whom there are
no organizational approvers.
Approvers Pending Approvals: This report lists an approvers pending
approvals with various information about the Requestor or the request.
Even though approvers can view their pending queue online, the
additional information on the report facilitates their ability to make their
approvals quickly.
Approval History: This report can be run with filters such as organization,
Requestor, approver, and approval date ranges and shows statistics and
trends for approvals and denials.
Cost Reporting: This report details expenses relating to external training
with runtime filters and summaries by breakdowns such as organization,
appropriation fund, user, and vendor.
Proxy Approvals: This report lists approvals that were made by someone
other than the configured approver.
EHRI: This report is described in further detail in the next section. The
report shall be exportable to Excel because it is transmitted to OPM as an
Excel spreadsheet.

Page 11 of 24
Attachment 4 SF -182 Requirements

4.12 EHRI Reporting


Enterprise Human Resources Integration (EHRI) is an Office of Personnel
Management (OPM) program designed to standardize the approach for HR
record storage, access, sharing, and archiving. Its goal is to provide official
government-wide human resources data and enable technology to support the
federal employee lifecycle. Through Web-based access to personnel folders,
EHRI access to personnel information by Human Resources (HR) staff, and
employees. It also allows for seamless electronic transfer of federal employees
from one agency to another. The suite of analytical tools and a comprehensive
Data Warehouse provides on demand, custom reports to plan and forecast the
personnel needs of the Federal Government.
In support of EHRI, agencies are required to provide a record of all employees
training. Agencies satisfy this requirement by submitting a file each month that
is in the standard format and uses standard course metadata as defined by
OPM. EHRI files are transmitted monthly.
The file format must comply with specific rules. Appendix C includes the layout
of the EHRI file.

Page 12 of 24
Attachment 4 SF -182 Requirements

5 SF-182 Flow / Use Cases


5.1 Overview
The routine SF-182 submission process consists of four basic components:
Creation and Submission: Requestor
Approvals: Approvers
Post-training Verification: Requestor and Approvers
EHRI Reporting: automated reporting to the Federal government Office of
Personnel Management (OPM) Enterprise Human Resources Integration
(EHRI)

The following sections describe the process flow and use case for each
component of the process.

5.2 Creation and Submission


The following chart outlines the basic flow of a SF-182 request from initiation
through submission.
Step Name Action
Start Requestor views a Forms List of all forms, list includes
Class name, Vendor name, start date, and request status
with options to start a New Request, View, Update,
Delete (unavailable if status is Submitted, Withdrawn, or
Deleted), Submit, Withdraw, Copy to a new request, Print
(unavailable if status is Deleted), or Verify (see Post
Training Verification section). Proceed to the appropriate
step.
Add New Request Blank or copied form opens; Requestor enters some or all
information, has the option to perform a pre-edit on all
fields, and does one of the following:
Cancels out of the form
Saves the incomplete form and exits
Completes and saves the form
Completes and submits the form (see the Submit
Request step)
View Request Existing form opens; Requestor views the request; exits
leaving it as is.
Update Request Existing form opens; Requestor updates some or all
information and does one of the following:
Cancels out of the form
Saves the incomplete form and exits
Completes and saves the form
Completes and submits the form (proceed to the
Submit Request step)

Page 13 of 24
Attachment 4 SF -182 Requirements

Step Name Action


Delete Request Existing form opens with a pop-up request to confirm
deletion; Requestor does one of the following:
Confirms deletion
> Request is tagged as deleted
> Request will appear in the Forms List with a status of
deleted
> Request can be copied to a new form, but is
otherwise not accessible
Exits, leaving the form as is, not deleted
Withdraw Request Existing form opens with a pop-up request to confirm
withdraw; Requestor does one of the following:
Confirms withdraw
> Request is tagged as withdrawn
> Request will appear in the Forms List with a status of
withdrawn
> Request can be copied to a new form, but is
otherwise not accessible
Exits, leaving the form as is, not withdrawn
Submit Request Existing form is open or reopens with a pop-up request to
confirm submission; Requestor does one of the following:
Confirms submission
> Request is edited (validation confirms field values,
cross-edit between fields, and configurable custom
business rules)
> If errors exist, highlights the erroneous fields and
displays appropriate error messages
> User updates invalid fields and re-submits
> If/when no errors, the request is tagged as
submitted
> Request appears in the Forms List with a status of
submitted, can be viewed, withdrawn, or copied to
a new form
Exits, leaving the form as is, not submitted
Copy Request New form opens prepopulated with information from the
copied form; Requestor does one of the following:
Proceed to Add New Request step
Cancels, leaving the form not copied
Exits, leaving the form as is, copied but not updated
Print Request Existing form opens with a pop-up request to confirm
printing; Requestor does one of the following:
Confirms printing, request is displayed in the format
of the SF-182 form in .pdf format with print options
Exits, leaving without printing the form

Page 14 of 24
Attachment 4 SF -182 Requirements

Page 15 of 24
Attachment 4 SF -182 Requirements

5.3 Approvals
The SF-182 Request is reviewed by one or more successive approvers, with
each being notified via e-mail that the action is required. Approvers may
approve or deny the request.
Post Training Verification is reviewed by one or more successive approvers, with
each being notified via e-mail that the action is required. Approvers may
approve or deny the verification.

5.4 Post Training Verification


After the end date of a Course, the Requestor is reminded via e-mail to record
and confirm his completion status for the Course. The user may indicate that
he completed the Course or that he did not complete the Course.
Verification of completion is required for the Course to appear in the
Requestors Training History and for the completion to be included in EHRI
Reporting.

5.5 EHRI Reporting


Completed, verified external training Courses are included in the next EHRI file
that is generated for reporting to OPM.

Page 16 of 24
Attachment 4 SF -182 Requirements

6 Appendix A: SF-182 Form

Page 17 of 24
Attachment 4 SF -182 Requirements

Page 18 of 24
Attachment 4 SF -182 Requirements

7 Appendix B: Reference Values


7.1 Training Vendors
Vendor information will be provided to the successful bidder at time of award.
7.2 Training Type Purpose Code
Code Value
01 Program/Mission Change
02 New Work Assignment
03 Improve Present Performance
04 Future Staffing Needs
05 Develop Unavailable Skills
06 Retention

7.3 Training Credit Type Code


Code Value
01 Semester Hours
02 Quarter Hours
03 Continuing Education Unit
04 N/A

7.4 Training Type Code


Code Value
01 Training Program Area: Functional or specialized training
programs
02 Developmental Training Area: Formal
developmental/training programs
03 Basic Training Area: Fundamental and/or required training
programs
04 N/A

7.5 Training Sub-Type Code


Code Value Type
Derived
from Sub-
Type
01 Legal: Education or training in the concepts, principles, 01
theories, or techniques of law
02 Medical and Health: Education or training in the 01
concepts, principles, theories, or techniques of
medicine.

Page 19 of 24
Attachment 4 SF -182 Requirements

Code Value Type


Derived
from Sub-
Type
03 Scientific: Education or training in the concepts, 01
principles, theories, or techniques of disciplines such
as the physical, biological, natural, social sciences;
education; economics; mathematics; or statistics.
04 Engineering and Architecture: Education or training in 01
the concepts, principles, theories, or techniques of
disciplines such as architecture and engineering.
05 Human Resources: Education or training in the 01
concepts, principles, theories of such fields as public
Administration; personnel; training; equal employment
opportunity; human resources policy analysis;
succession planning; performance management;
classification; and staffing.
06 Budget/finance Business Administration: Education or 01
training in the concepts, principles, theories of
business Administration, accounts payable and
receivable; auditing and internal control; and cash
management.
07 Planning and Analysis: Education or training in the 01
concepts, principles, theories of systems analysis;
policy, program or management analysis; or planning,
including strategic planning.
08 Information Technology: Education and training in the 01
concepts and application of data and the processing
thereof; i.e., the automatic acquisition, storage,
manipulation (including transformation), management,
system analysis, movement, control, display,
switching, interchange, transmission or reception of
data, computer security and the development and use
of the hardware, software, firmware, and procedures
associated with this processing. This training type
does not include any IT training on agency proprietary
system.
09 Project Management: Education and training in the 01
concepts, principles, theories necessary to develop,
modify, or enhance a product, service, or system
which is constrained by the relationships among
scope, resources, and time.
10 Acquisition: Education or training in the concepts, 01
principles, theories or techniques related to the 1102
occupation.

Page 20 of 24
Attachment 4 SF -182 Requirements

Code Value Type


Derived
from Sub-
Type
11 Logistic Specialty: Training for professional skills of a 01
specialized nature in the methods and techniques of
such fields as supply, procurement, transportation, or
air traffic control.
12 Security: Training of a specialized nature in the 01
methods and techniques of investigation, physical
security, personal security, and police science.
13 Clerical (Non-supervisory clerical/Administrative): 01
Training in skills such as office management, typing,
shorthand, computer operating, letter writing,
telephone techniques, or word processing.
14 Trade and Craft: Training in the knowledge, skills, and 01
abilities needed in such fields as electronic equipment
installation, maintenance, or repair; tool and die
making; welding, and carpentry.
15 Foreign Affairs: Training for professional skills of a 01
specialized nature in the methods and techniques of
such fields as foreign languages, foreign culture,
diplomacy, strategic studies.
16 Leadership/Manager/Communications Courses: 01
Training that address skill area such as
Leadership/Management and Communication (i.e.,
written, oral and interpersonal) coursework.
20 Pre-supervisory Program: Development/training 02
program for non-supervisors
21 Supervisory Program: Development/training program 02
which provides education or training in supervisory
principles and techniques in such subjects as
personnel policies and practices (including equal
employment opportunity, merit promotion, and labor
relations); human behavior and motivation,
communication processes in supervision, work
planning, scheduling, and review; and performance
evaluation for first line supervisors.
22 Management Program: Development/training program 02
which provides mid-management level education or
training in the concepts, principles, and theories of
such subject matters as public policy formulation and
implementation, management principles and
practices, quantitative approaches to management, or
management planning organizing and controlling.
(Supervisors of supervisors; GS-14/15 supervisors; GS-
14/15 direct reports to SES)

Page 21 of 24
Attachment 4 SF -182 Requirements

Code Value Type


Derived
from Sub-
Type
23 Leadership Development Program: Formal 02
developmental program that provide leadership
training and development opportunities.
24 SES Candidate Development: OPM-approved program 02
to prepare potential SES members
25 Executive Development: Continuing development for 02
leaders above the GS-15 level
26 Mentoring Program: Formal standalone program with 02
established goals, measured outcomes, access open
to all who qualify, protges and mentors paired to
facilitate compatibility, training and support provided;
company benefits directly.
27 Coaching Program: Formal standalone which provides 02
ongoing partnership with an employee and coach that
helps employee produce desired results in professional
lives
30 Employee Orientation: Training of a general nature to 03
provide an understanding of the Organization and
missions of the Federal Government, or the employing
agency or activity, or a broad overview and
understanding of matters of public policy.
31 Adult Basic Education: Education or training to provide 03
basic completeness in such subjects as remedial
reading, grammar, arithmetic, lip reading or Braille.
32 Mandated Training: Mandatory training for all 03
employee Government wide. This includes training
required by law and/or regulation; such as ethics,
information system awareness, safety or health.
33 Work-life: Training to promote work-life (i.e.., health 03
and wellness training, employee retirement/benefits
training).
34 Soft Skills: Training involving development of 03
employees' ability to relate to others (i.e., customer
service, effective communication, dealing with difficult
people).
35 Agency Specific: Agency specific required training that 03
is not addressed in Training Program Type 01 Appendix
R. This training type does include IT training on agency
proprietary system.

7.6 Delivery Type


Code Value

Page 22 of 24
Attachment 4 SF -182 Requirements

01 Traditional Classroom
02 On the Job
03 Technology Based
04 Conference / Workshop
05 Blended
06 Correspondence (Self-study course material)

7.7 Designation Type


Code Value
01 Undergraduate Credit
02 Graduate Credit
03 Continuing Education Unity
04 Post-graduate Credit
05 Other N/A

7.8 Training Source Type


Code Value
01 Government Internal
02 Government External
03 Non-government
04 Government State/Local
05 Foreign Governments and Organizations

Page 23 of 24
Attachment 4 SF -182 Requirements

8 Appendix C: EHRI File Format


Field positions are identified as columns.
Column A: The value A
Column B: Social Security Number
Column C: Date of Birth
Column D: EHRI Employee ID
Column E: Agency Code
Column F: Course Title
Column G: Training Type Code
Column H: Training Sub-Type-Code
Column I: Start Date
Column J: End Date
Column K: Continued Service Agreement Required Indicator
Column L: Training Accreditation Indicator
Column M: Training Credit
Column N: Training Credit Designation Type Code
Column P: Training Credit Type Code
Column Q: Training Duty Hours
Column R: Training Non-Duty Hours
Column S: Delivery Type Code
Column T: Purpose Type Code
Column U: Source Type Code
Column V: Materials Cost
Column W: Per Diem Cost
Column X: Travel Cost
Column Y: Tuition and Fees
Column Z: Non-Government Contribution to Training
Column AA: Travel Indicator

Page 24 of 24