Attachment_1_-_TSO_Labor_Reporting_Guideline.docx

TSO LABOR REPORTING GUIDELINE

TSO LABOR REPORTING GUIDELINE

1. Purpose. This document provides guidance for labor reporting in the Labor Reporting System (LRS) for all military, government civilian, and contract employees of the Technology Services Organization.

2. Time and Attendance v Labor Reporting. “Time and Attendance” refers to the hours and type of hours an employee reports for pay purposes. “Labor” refers to the systems, projects, tasks, hours, and activities (type of hours) an employee reports for billing purposes.

· Time and attendance for government civilians is reported using the Standard Labor Data Collection and Distribution Application (SLDCADA). SLDCADA interfaces with the Defense Civilian Pay System (DCPS) for civilian pay and leave. A SLDCADA link is available on the TSO Home Page. SLDCADA documentation is available on the application site.

· Time and attendance for the TSO’s contract employees is reported using E-TES for pay and leave.

· LRS Web captures labor information for all employees at a detailed level for metrics and management reporting. An LRS Web link is available on the TSO Home Page and directs the user to an external, commercial site.

3. Dual Entry. All government civilians and contract employees will enter hours in LRS as well as their time and attendance system. Supervisors are responsible for ensurirng LRS Web entries match time and attendance entries. Military employees will enter hours only in LRS Web.

4. Direct v Indirect Hours

· Direct Hours. The majority of an employee’s time will be charged as direct hours to an SCR. Some time that had been considered to be indirect hours in the past, including technical and non-technical training, meetings, Director’s Chats, and fire drills is now considered direct hours.

· Indirect Hours. The only activities that should be charged by employees as indirect time are leave related. Each leave type is further defined in the Hour Types section later in this document. Examples are:

· Personal leave (e.g., annual, sick)

· Administrative leave (e.g., in conjunction with a holiday, weather-related time off)

· Military leave

5. Project Types. All direct hours will be charged to a project which falls into one of three categories of work. The project types are:

· Sustainment. Sustainment projects are SCRs which add or modify the functionality of existing systems. These projects are primarily funded with Operation & Maintenance (O&M) funds. As an example, MCTFS CCB projects and standalones are primarily performed under sustainment.

· Operational Support. Operational Support projects are SCRs established to report tasks which support direct system development efforts such as design, programming, and test. As an example, training, configuration management, and organization admin. These projects are typically for the entire fiscal year of activity. These projects are also funded with Operation & Maintenance (O&M) funds.

· Maintenance. Maintenance projects include work performed on production systems, such as production trouble reports (PTR’s). Development divisions may also have fiscal year projects for maintenance work for ongoing production support.

6. Hour Types. The following charts define the type of hours (Activity) to be reported in LRS Web.

· Break Time. Breaks are reported as time worked to the current project.

· Lunch Time. Lunch time is never charged to a project.

Direct Hours

Indirect Hours (Leave)

· Used by government civilian employees to record leave taken to perform military duties.

7. Task Types. The following charts define the various tasks to be reported in LRS Web. The tasks are specific to the project types to which they are associated.

· Sustainment and Maintenance Tasks. The following tasks will be available for all Sustainment projects and Maintenance projects. In general, only those employees assigned to the MCTFS, IAD, TFAD, SABRS and OWD development divisions will charge to Sustainment and Maintenance SCR(s). Support divisions and branches, such as SMD, ICD, SEPG and SQA and CSC management do not typically charge to Sustainment and Maintenance SCRs unless an estimate has been done by the support group for work on an individual SCR.

Analysis

Perform business process and data analysis.

· Attend JAD sessions

· Attend concept and problem solving meetings

· Review draft SCR(s) for comments back to the customer

· Create logical data and process models

· Perform data modeling

· Pay business rule decomposition

· Personnel and pay legacy data mapping

· Pre-design, pre-programming, pre-testing analysis for approved SCR(s)

· Identify and understand the current functional requirements

· Evaluate the impact of changes to the AIS based on functional requirements

Data Admin

Management of data definitions and their associated data repositories, primarily during the Analysis and Design portions of the software development effort.

· Record, enter into repositories, and develop and maintain data structure repositories and dictionaries

· Identify standard data for further reuse

· Promote standard data elements and structures

· Eliminate data redundancies

· Pay data mapping

· Activities involving the use of Designer 2000, Power Designer, Data Manager, etc.

· Confirming the use of data naming conventions

· Defining domain values

Database Admin & Spt

Used to record time in managing and administration of a database and user accounts.

· Populating tables and databases

· Sizing and tuning databases

Database Admin & Spt Rework

Used to record rework time in managing and administration of a database and user accounts.

· Populating tables and databases

· Sizing and tuning databases

Deliverable Planning

· Update estimates (Maintenance)

Design

Translate the logical requirements and software change specifications into physical specifications.

· Creation of application, system, subsystem, program, file, etc., specifications

· Create physical data and process models

· Determine file type, I/O, equipment requirements, system capacity and performance

· Document detail design

Design Rework

Used to correct design work previously released, not as a result of new work (i.e. Addenda).

Documentation

Create, maintain, and disseminate all documentation that is not a specific output of another phase. For example, this would not include specifications of any kind, because specifications are an output of Design and would therefore be charged to Design rather than Documentation.

· Release specific documentation

· Operations Manuals

· Users Manuals

Documentation Rework

Time to create, maintain, and disseminate all documentation that is not a specific output of another phase. For example, this would not include specifications of any kind, because specifications are an output of Design and would therefore be charged to Design rather than Documentation.

· Release specific documentation

· Operations Manuals

· Users Manuals

Military Pay - Res

Program and unit test to satisfy the logical and physical specifications. Perform programmer test of the completed modules, screens, programs, etc.

· Writing, compiling, testing program code

· Performing programmer unit tests / completing a unit test checklist

· Writing batch files

Military Pay - Spec

Program and unit test to satisfy the logical and physical specifications. Perform programmer test of the completed modules, screens, programs, etc.

· Performing programmer unit tests / completing a unit test checklist

Military Pay – U&E

Program and unit test to satisfy the logical and physical specifications. Perform programmer test of the completed modules, screens, programs, etc.

· Performing programmer unit tests / completing a unit test checklist

Programming

Program and unit test to satisfy the logical and physical specifications. Perform programmer test of the completed modules, screens, programs, etc.

· Performing programmer unit tests / completing a unit test checklist

· Writing scripts (install, load, PL/SQL, triggers, server, etc.)

· Writing and modifying programs and objects (HTML, JSP, ASP, PBL, etc.)

· Writing batch files

· Writing PADIA/MSI packages for NMCI

Programming Rework

Used to correct programs previously coded and peer reviewed, not as a result of new work (i.e. Addenda).

Quality Assurance

Plan, execute, and record results of software quality assurance peer review activities.

· Requirements Peer Review

· Design Peer Review

· Critical Design Review

· Code Peer Review

· Test Readiness Review

· Test Peer Review

· Technical Writing Peer Review

· Formal and informal walkthroughs

· Software product and process reviews

System Interface - MIS

Program and unit test to satisfy the logical and physical specifications. Perform programmer test of the completed modules, screens, programs, etc.

· Performing programmer unit tests / completing a unit test checklist

System Interface - ONLN

Program and unit test to satisfy the logical and physical specifications. Perform programmer test of the completed modules, screens, programs, etc.

· Performing programmer unit tests / completing a unit test checklist

· Writing and modifying programs and objects (HTML, JSP, ASP, PBL, etc.)

System Interface - Tables

Program and unit test to satisfy the logical and physical specifications. Perform programmer test of the completed modules, screens, programs, etc.

· Performing programmer unit tests / completing a unit test checklist

Test Planning

The test planning phase is where time is spent researching and identifying records to be used to write test conditions/ test cases and scenarios for test execution. The work product from this effort is input to the peer review process.

Testing

Plan, execute, and evaluate all test activities other than unit testing.

· Beta testing

· Functional testing

· Link testing

· String testing

· Integration test planning

· Integration testing

· Qualification testing

· Acceptance testing

· Stress testing

· Environment testing

Testing Rework

Used to correct all test activities previously submitted, not as a result of new work (i.e. Addenda).

Transactions

Program and unit test to satisfy the logical and physical specifications. Perform programmer test of the completed modules, screens, programs, etc.

· Performing programmer unit tests / completing a unit test checklist

· Writing scripts (install, load, PL/SQL, triggers, server, etc.)

· Writing batch files

· Operational Support Tasks. The following tasks will be available for all Operational Support projects. All Operational Support projects will be TSO projects, using the numbering schema TSO9999AAA-FY. (E.g., TSO1020-13, TSO1020MFR-13)

Administrative – This is for Office Assistants only.

Used to record time by all Office Assistants.

APP Admin – This is for Infrastructure & Communication Division only.

Installation and upgrades of all Application software for all tiers (workstation, web, application, and database); application support to include troubleshooting, backup and recovery and security.

· Apply System Software Patches/Upgrades

· System Software Application Performance Monitoring

· System Software Application Troubleshooting

· System Software Application Support

· System Software Application Security

· System Software Application Backup/Recovery

APP Build ENG – This is for Infrastructure & Communication Division only.

Used to record time spent in establishing application and system environments for each lifecycle.

· Establish application servers

· Establish communications

· Establish migrations

· Deployment builds

· Deployment Scripts

Appraisal Administration

Time spent on SCAMPI appraisals, including participation, preparation, document review, report preparation and review. This includes serving as an appraisal team member or site coordinator and participating in presentations and interviews during an appraisal. If more than one division is included in an appraisal, time should be split evenly between the divisions. This time will also be charged directly to the system supported.

Appraisals Preparation

Time spent preparing evidence and facilities for a SCAMPI appraisal at the TSO. This does not include time spent working with individual divisions. This time will be charged directly to the system supported. It also does not include time spent serving as an appraisal team member, supporting an appraisal team as site coordinator or participating in appraisal activities.

BMO Support

Used by the Business Management Office Team to record all Budget, financial reporting and contracting activities. Including:

· Budget formulation, justification, execution

· Financial analysis and reporting

· Procurement activities relating to items/services procured via contract: procurement and COR/COTR activities

Certification and Accreditation

Used by the Certification and Accreditation (C&A) Team to record all C&A activities. Including:

· Initiating a package or assisting System IAOs with XACTA/MCCAST activities

· Conducting training or providing informational briefs on C&A processes/procedures

· Developing C&A documentation (i.e., process documents, training materials, etc.)

· Performing or assisting with computer scans and test plans.

· Assisting system IAOs with annual system reviews.

CMMI Consulting

Time spent supporting external agencies and activities (e.g., DFAS and Marine Corps Systems Command) process improvement activities. This includes providing CMMI training, appraisal support and process consulting support. This category will also be used if additional Marine Corps organizations are supported.

Configuration Mgmt

Used by Development Divisions, ICD and SMD to record time spent in configuration management to include the following:

· Plan, execute, and record activities associated with configuration management, including release management, version control, etc.

· Configuration management activities, including the use of such tools as CMIS, PVCS, and PANAPT

· DLT Tool maintenance and Software Release roll-up.

· Configuration auditing of production baselines

· Version control

· Promoting directory structures for the next release

· Archiving previous releases, support and development software

· System library updates

· Documentation maintenance

Contractor Mgmt

Contractor task management, to include:

· Reviewing and approving contractor deliverables

· Developing and maintaining letters of instruction

· Evaluating and reporting on contractor performance

DB Admin – This is for Infrastructure & Communication Division only.

Monitoring database performance and availability in all environments for all tiers to include network.

· Apply database system software patches/upgrades

· DB System Troubleshooting

· DB System Application Support

· DB System Performance Tuning

· DB System Backup/Recovery

· DB System Security

Director Chat

Do not use. For Director Chat, post that time to Director’s Office & MSC.

Director’s Office & MSC

Time spent in meetings with the TSO director and deputy director, working specific assignments from the director’s office, participating in director’s chat, reporting on the balanced scorecard or setting up meetings like the DMM or All-hands. This also includes time spent preparing for and participating in Management Steering Committee meetings.

Document Management

Time spent on reviewing and updating organizational documentation prior to taking it to either the MSC or document review group for review. Also includes time spent in document review group activities, time spent on DMS related issues and time spent reviewing SEPG internal documents.

General SEPG Admin

Time spent on general activities not related to any of the other SEPG time categories (e.g. answering email, logging time on LRS, general SPI discussions, participation in general SPI meetings or in communication efforts.) This also includes time spent on SEPG Getting Our Act Together (GOAT) activities, which include internal meetings, process reviews and definition efforts concentrated on the SEPG activities and action planning.

Implementation Support

Planning, coordination, and execution of actions to install a new application or release.

· Installation customer service

· TSO provided training to users

· Actual implementation of application or system at the customer’s site

· Travel associated with system or release implementation

· Prepare and maintain Implementation Plan

· Conduct release implementation meetings

Information Assurance – This is for Information System Security personnel only.

System Information Assurance Officers will use this task to record all IA activities and any activities related to the certification and accreditation process.

Internal Tool Management

This task is for use by the functional managers (not the development teams) of TSO support tools, (DMS, SQMS, EMS, etc.). Example activities are:

· Soliciting, coordinating, and managing functionality requests from TSO users.

· Submitting and managing change requests to the tool development team.

· Planning and managing tool releases.

· Meeting with the tool development team.

· Testing and reviewing test output of proposed tool deployments.

Mainframe Security– This is for Mainframe Security Team only.

All Mainframe Security activities for MCTFS and SABRS.

Military Duties - This is for active-duty Marines assigned to the TSO only

Marines are required to maintain good order and displine and a standard of performance to ensure combat readiness. Military activities can expand a wide array of areas. Here are some of the most common areas:

· Physical Training

· Combat Fitness and Physical Fitness Testing

· Uniform Inspections

· Formations

· Fitness Report and PRO/CON preparations, or other administrative reporting paperwork

· Military Ceremonies

· Formal and informal Professional Military Education (PME)

· Officer Calls

· Managing specific Marine Corps personnel issues

Network Security– This is for Network Security section only.

To record all Network security activities.

OPS Support

Used to record time spent involved in comparison testing production baseline processing with development software processing.

1. Writing and testing JCL for test execution

1. Executing cyclic testing

1. Analyzing and documenting test results

1. Assigning personnel to research and correct development software

1. Researching and coding corrections due to test results

Operational Test– This is for Marine Corps Total Force System Programming only.

Used to record time spent involved in comparison testing production baseline processing with development software processing.

· Writing and testing JCL for test execution

· Executing cyclic testing

· Analyzing and documenting test results

· Assigning personnel to research and correct development software

· Researching and coding corrections due to test results

Organization Admin

Used to record miscellaneous activities.

· All Hands/Award

· Fire Drills

· Office Picnic

· Office Christmas Party

· Filling out Background Clearance information

· System downtime (i.e. due to JIRA/SharePoint)

· Getting CAC cards

Personnel Security – This is for Personnel Security team only.

Record all personnel security activities. Including:

· Initiating EQIP questionnaires and providing assistance as necessary

· All JPAS activities

· Conducting or attending briefs on personnel security

· Personnel Records Management

Physical Security – This is for Physical Security personnel only

Record all physical security activities. Including:

· Building Badges (i.e., employee access cards, etc.)

· Visitor Access control

· Security of government assets

· Reporting security breaches

Policy & Plans – This is for Security Plans and Policy team only.

Rrecord all plans and policy activities. Including:

· Conducting research necessary to develop all security plans and policies

· Developing security plans and policies for TSO

· Establishing security procedures for TSO personnel (i.e. process documents, access, etc)

· Assisting with the preparation of security appointment letters. (i.e., IAO, Network, Security Manager, etc.)

· Maintaining repositories for all TSO plans and policies, as well as other USMC, DoD, and federal regulations pertaining to security

Post Implementation Review

Used to record time preparing for, attending, conducting and follow-up for Post Implementation Reviews (PIR).

· Conduct and coordinate Post Implementation reviews

· Gathering and validating release data

· Follow-on activities due to PIR results or reports

Process Improvement

Used to record time spent in reviewing and updating processes to ensure that they meet the structure provided by the Capability Maturity Model Integration (CMMI). Process Improvement includes process documentation and measurement of process performance.

· Collect and analyze measurements

· Develop and coordinate Software Process Improvement Plan

· Identify and document non-compliance issues

· Provide feedback to project staff and managers on the results

· Coordinate division impact on all policies, plans and standards

· Review documents

· Participate in the Champions of Excellence program, to include meeting attendance and submitting award nominations

Project Management

Used to record all aspects of Project Management.

· Status Meeting Management

· Prepare for and attend meetings, such as Configuration Control Board (CCB), Software Release Meetings

· Identify and track Risks

· Attend impact and information meetings

· Conduct planning and status meetings and prepare MFR

· Project Planning and Tracking

· Develop and coordinate Software Development Plans (SDP) for the release or deliverable

· Coordinate, track and submit estimates

· Coordinate milestones between divisions and branches

· Prepare and maintain plans and schedules

· Prepare and maintain information to track projects

· Requirements Management

· Receive, route, and log SCR(s)

· Project Monitoring and Control

· Generate and publish reports needed to internally track projects

· Project Tracking Tools Management

· Develop and enhance Project Estimating and Tracking tools

· Modify and refresh data in project tracking tools

· Business and administrative activities associated with the planning, organizing, evaluating, coordinating, and managing of a sustainment, development, or maintenance program/system.

· Travel

· Budget preparation

· Management briefing preparation

· Management control reviews

· Audit response preparation

· Vendor liaison

· General Supervisor Duties

· Review, counsel employees

· Write and give performance reviews

· Supervision of direct billable software development activities

· Plan work assignments

· Track results

Quality Assurance (Audit)

Plan, execute, and record results of internal software quality assurance audit activities.

· Audits listed on the division audit plan

· Audits listed on the TSO audit plan

Resource Management – This is for the Infrastructure & Communication Division only.

Managing all server based critical computer resources (CCR).

· Hardware and Software License management

· Development of specifications (CCR) for DISA resources

· DISA liaison for web and client server applications

· Operations management for web and client server applications

Safety/Facilities – This is for Safety and Facility personnel only.

Record all safety and facility activities for TSO.

Security – This is for the Information Systems Security Officer only.

Record high level security activities for TSO.

SEPG Support – This is for Software Engineering Process Group only.

Used to record activities the SEPG does to assist the software engineers in documenting and implementing standard processes that will improve the manageability of the USMC applications’ development cycle and provide a higher quality product to the customers.

SMD Support –This is for the Systems Management Divison only.

Used to record activities performed by the Systems Management Division to support the development divisions.

SPI Meetings

Time spent in SPI related meetings not related to process definition, PIRs or appraisals.

SQA Support (AIS-Specific)

Used to record activities performed by Software Quality Assurance Branch to support the development divisions. To be used only by the SQA. Effort reported to this task will be managed as division-wide for budget purposes

· Preparing for, conducting, attending, and reporting status meetings

· Miscellaneous activities not specifically covered by the other tasks

SQA Support (Div Audits)

Used to record activities performed by Software Quality Assurance Branch to support the development divisions. To be used only by SQA . Effort reported to this task will be managed as division-wide for budget purposes.

· Preparing for, conducting, and reporting audits and reviews for development divisions

SQA Support (TSO Audits)

Used to record activities performed by Software Quality Assurance Branch to support the TSO. To be used only by SQA. Effort reported to this task will be managed as AIS-specfic for budget purposes.

· Preparing for, conducting, and reporting audits and reviews for TSO

SQA Support (TSO-Wide)

Used to record activities performed by Software Quality Assurance Branch to support the TSO. To be used only by SQA. Effort reported to this task will be managed as AIS-specfic for budget purposes.

· Preparing for, conducting, attending, and reporting status meetings (TSO Director, support division, MSC, etc.)

· Miscellaneous activities not specifically covered by the other tasks

SYS Admin – This is for Infrastructure & Communication Division only.

Installation and upgrades of all Operating systems for all Devices managed by the TSO.

· Apply OS/Hardware Patches/Upgrades

· OS/Hardware Performance Monitoring

· OS/Hardware Troubleshooting

· OS/Hardware Application Support

· OS Backup/Recovery

· OS/Hardware Security

· Firewall maintenance

· Special equipment installation

· Environment setup and support

· RED workstation setup and support

Tech Upgrades/Analysis

Used to record activities in conjunction with minor upgrades to application software for all tiers (workstation, web, application, and database). Upgrades of significant size are performed under maintenance.

Test Unit – This is for the Marine Corps Total Force Systems Test Unit only.

Test Unit runs a series of production control jobs (JCL) in support of the testers, functional customers and system developers that are necessary for test setup and test execution. Test unit also prepares ‘Tool Box’ JCL to allow testers to run specific actions on records and datasets. In addition, testers may submit special JCL requests for on-time applications, which would not be part of the Tool Box.

Training

Used to record time spent in training, such as the following:

· Management training

· Team Building

· Leadership training

· New Employee

· Succession

· EEO / No Fear

· Technical Training

· Training on specific software or hardware

· Software Process Improvement

CMMI

SEPG Conference Balance Score Card

· Software Quality Assurance

· Training on new versions of programming languages, new databases, operating system upgrades, etc.

· Microsoft Office training

· Design and Testing training

Training - Security

1. Training on Anti-Terrorism

1. Training on Operations Security

1. Training on Counterintelligence

1. Training on Physical Security

1. Training on Combating the trafficking of persons

1. Security Orientation

1. Security awareness training

1. Any job-related security training/courses and security briefs

Travel Coordinator

Used exclusively by the TSO Travel Coordinator to record time spent in those duties, such as the following:

· Lead Defense Travel Administrator

· Manage Defense Travel System (DTS) for TSO

· Supervise Organization Defense Travel Administrators (ODTA)

· DTS Training

· Budget and Lines of Accounting within DTS

· Handle all Permanent Change of Station (PCS) Orders/Claims