Attachment_06_(TM02).doc
DOC document 72 KB Posted
- Attached to
- Infrastructure, Design, Engineering, Architecture, and Integration, (IDEAI-2) Full and Open Federal contract opportunity
- Solicitation number
- DOC52PAPT1300015
About this file
Attachment 6
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| RFP_DOC52PAPT1300015_Amendment_1.pdf | ||
| Attachment_05_(GD17).doc | DOC document | |
| Attachment_12_(Termination_Worksheet).doc | DOC document | |
| Attachment_13_(Experience_Reference_Worksheet).doc | DOC document | |
| Attachment_11_(Labor_Categories)_full_and_open.xls | XLS spreadsheet | |
| RFP_DOC52PAPT1300015_IDEAI2_Unrestricted.pdf | ||
| Attachment_07_(Document_Receipt).doc | DOC document | |
| Attachment_09_(Invoices).xls | XLS spreadsheet | |
| Attachment_08_(Weekly_Funding_Analysis).doc | DOC document | |
| Attachment_04_(PN01).doc | DOC document | |
| Attachment_01_(FN01).doc | DOC document | |
| Attachment_03_(GD16).doc | DOC document | |
| Attachment_10_Contract_Actuals_Templates.xls | XLS spreadsheet | |
| Attachment_02_(FN07).doc | DOC document |
Show all 14
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DOC52PAPT1300015
Attachment 6
TM02
CONTRACT DELIVERABLE DESCRIPTION
Deliverable Number:
TM02
Title/Description:
Task Management Plan (TMP)
Frequency of Submission:
See Remarks Number of Copies:
10 + Magnetic Media
First Submission Due:
See Remarks
Subsequent Submissions Due:
As required, following approval of a Resource Estimate (FN07)
Government Acceptance Required:
Yes
Government Response Due:
Ten (10) working days after receipt
Remarks:
For Level of Effort (LOE) Task Orders, a Task Management Plan shall be prepared by the contractor within thirty (30) calendar days after Government approval of a Task Description. For Discrete Task Orders, a Task Management Plan shall be prepared within ten (10) calendar days of the Government providing an Activity Description download.
Format/Content Requirements and Instructions:
A Task Management Plan (TMP) shall be prepared by the contractor to describe the work scope, schedule, technical requirements, and resources required for the performance of each Task Order proposed by either the Government or the contractor.
The TMP shall fully describe the technical scope, schedule, resources, and costs associated with executing a Task Order.
Preparation Instructions:
The TMP shall, as a minimum, consist of the following:
Section 1. Introduction The Introduction shall consist of the following:
A brief description of the Scope of the Task Order and the Period of Performance
Identification of the applicable Statement of Work reference from Section C of the Contract that applies to the effort described in the TMP
DELIVERABLE NUMBER:
TM02 page 2
FORMAT/CONTENT REQUIREMENTS AND INSTRUCTIONS (Continued)
Responsibility Assignment Matrix for the Task Order, at the task level
Task Management Plan organization.
Section 2. Task Description The Task Description section shall consist of the following:
A brief introduction to the technical effort.
Assumptions that may be appropriate to the effort. Every attempt will be made to include assumptions and constraints in the task descriptions.
Work Breakdown Structure (WBS).
Task-by-Task Description and Schedule.
For LOE Task Orders, descriptions will be provided that include an Objective, Task-level Assumptions/Constraints. Descriptions of the Activities identified in the WBS, Deliverables, Schedule, Task Manager, PTO Dependencies, and Other Task Dependencies. The Task Order schedule will normally be the period of performance for the Task Order.
For Discrete Task Orders, the descriptions will consist of the Network Activity Descriptions provided by the PTO in a download of activity network and narrative description data. Schedule information will be included with the individual Activity Descriptions and baselined activity network.
The Task Order schedule will serve as the baseline against which Task Order schedule performance will be reported in contract deliverable FN01 (Monthly Status Report).
Section 3. Cost Proposal An estimate of contractor and subcontractor (if a subcontractor is utilized) labor hours and costs shall be provided with each TMP. Resource estimates shall be provided at the task level for each month of the task period of performance. Contractor labor requirements shall be expressed in staffhours required by labor category. If a subcontractor is used, subcontractor requirements shall be expressed in total staffhours required per task.
The Cost Proposal section shall consist of the following:
Pricing Assumptions, including direct and indirect rate references (not the specific rates will not be included in the TMP), accounting calendar
Facilities Capital Cost of Money (FCCOM) calculation at the total Task Order level
Task Order Level
DELIVERABLE NUMBER:
TM02 page 3
FORMAT/CONTENT REQUIREMENTS AND INSTRUCTIONS (Continued)
Task Order costs by cost element by month
Task Order labor hours by month (roll-up labor categories)
Task Order labor hours by month (detailed labor categories)
Supporting Schedules for Documentation, Other Direct Costs, Local Travel, Distant Travel, and Bill of Materials
Task Level
Task costs by cost element by month
Task labor hours by month (roll-up labor categories)
Task labor hours by month (detailed labor categories)
The Task Order cost estimate will serve as the baseline against which Task Order actual costs will be reported in deliverable FN01, Monthly Status Report.
Mechanized Data Submissions The contractor shall submit cost proposal information in accordance with the data format attached.
Section 4. Contract Deliverables The contractor shall, in the TMP, reference the appropriate contract deliverable number and title from the contract Statement of Work for all deliverables to be provided during the course of Task Order execution. Deliverables may be tailored, subject to PTO approval, by the contractor to meet any unique Task Order requirements. In the event that a description of the proposed data deliverable is not contained in the Contract Statement of Work, the contractor shall provide a recommended description to be approved by the PTO and incorporated in the contract Statement of Work through a modification to the contract.
The Contract Deliverables section shall consist of the following:
CDRL Number
Deliverable Title
Task/Activity Number
Program Code, as applicable
Delivery Date
Mechanized Data Submission The contractor shall submit contract deliverables information in accordance with the attached format.
Task Order Budget Download Requirements (TM02) May 2014 This document explains the requirements for submitting task order budget data (hours and dollars) electronically. An example of the format is provided.
Overview
1. A budget download is submitted with each approved Task Management Plan (TMP).
2. A hard copy of the TMP must accompany the download for data verification, per deliverable instructions on TM02 per the contract.
3. Actuals are provided via a flat ASCII text file in Comma Separated Values (.csv) format and cannot contain any special word processing or other characters.
4. No double or single quotes are to be present in the file.
5. Do not format dollar values with commas (,) or dollar signs ($).
6. Each line in the file represents one fiscal year’s worth of dollars or hours for a given task, year, contractor, and cost element combination.
7. The file must contain the entire budget for the task order.
File Naming Convention
Each file must be named using the following convention:
<code><task order number>.<month><day>
The <code> identifies the contractor submitting the file.
The <task order code> is a four-digit code and does not contain a dash. For example, use “0501” for task order 05-01.
The month and day combination identify the effective date of the Task Management Plan.
The <month> must be a single character: numeric for the first nine months, and alphabetic for the last three months, of the calendar year. For example:
January
February
March
April
May
June
July
August
September
October
O (the letter O not the number 0)
November N
December D
The <day> is a two digit number identifying the day of the month.
For example:
C0501.811 Budget for 05-01, effective August 11th, from CSCS
R0502.d01 Budget for 05-02, effective December 1st, from Raytheon
File Data
The first line of the file must be a comment indicating the effective date of the Task Management Plan. Use a pound sign (#) to start the comment line.
For example: #Effective 05/01/2014 Each budget record is a single line containing 12 monthly dollar or hour values; each line consists of a total of 17 fields, separated by commas, as follows:
1. Data type flag Either D (dollar values) or H (hour’s values)
2. Task number Example: 05-01.01 (include the dash)
3. Fiscal Year Format YYYY, i.e. 2005
4. Contractor Code A complete list of contractor codes is available from your COTR. This field differentiates between prime and subcontractor efforts. A null value indicates the prime contractor; however, a comma must be provided as a place holder for the value.
5. Cost Element Code A complete list of cost element codes is available from your COTR 6-17.
Budget values for each month of the fiscal year, starting with the October value. Do not use commas, dollar signs, or spaces in the values. Negative numbers are not allowed. An example of a series of budget values follows:
0.00,9064.88,12000.22,15000.65,0.00,etc...
Example:
D,05-01.01,2005,CSC,01,0.00,263.59,3183.84,0.00,1382.30,1202.00,0.00,0.00,0.00,0.00,0.00,0.00
H,05-02.01,2005,RAY,02,159,52,27,00,00,00,45,58,00,00,00,00
D,05-03.01,2005,GALX,39,0.00,323.47,563.78,454.18,115.86,265.38,79.86,25898,909.65,0.00,0.00,0.00
Corrections
If a contractor needs to re-submit a revised or corrected file, re-submission will be accepted provided the corrected file contains the entire budget for the task order and accompanies the new TMP.
CDRL Download Requirements (TM02)
May 2014 The USPTO tracks contract deliverables using the Automated Program Management System (APMS). Specifically, an APMS application called the Product Deliverables Acceptance Management System (PDAMS) is used to enter, update, report, and archive information about each contract deliverable.
Whenever a Task Management Plan (TM02) is accepted for a new Task Order, the contractor provides a CDRL Download, an electronic file listing all scheduled deliverables (deliverables with specific due dates) for that Task Order. The information contained in the download is loaded to the PDAMS database; it is then updated by the PTO as each deliverable is received.
This document explains how to prepare a CDRL Download file.
A. File Format
· ASCII data with Comma Separated Values.
· Quotation Marks surrounding the values are optional.
· No spaces are permitted within the values, except within the title.
· No commas are allowed within any value, including the title.
· Each line represents ONE record and must contain values or place holders for all ten of the data elements identified in section C.
B. File Naming
· Format: cdrl<task order code>.< contractor code>
· Omit any dashes from the task order code. Example: cdrl0501.ray
· See your COTR if you do not know your contractor code.
C. File Contents
The file is to contain one record for each scheduled deliverable that has a specific due date. Deliverables that are submitted “As Required or "Monthly" or "weekly" are not included in the file.
The following fields are provided for each record/line of the file.
1. New Record Flag - must equal "NEW". This is provided to support a planned capability to submit updated deliverable information. Not case sensitive.
2. Deliverable ID - unique identifier number from the contractor's database (the COTR can provide examples for formatting this for SDI contractors). This identifies which deliverables were provided via CDRL download; it also supports the planned capability to submit updated deliverables. This field holds up to eight alpha-numeric characters.
3. Task Code - The TASK Code (as opposed to the network activity code) with which the deliverable is associated. This code also identifies the Task Order Number and subTask Code.
Example: 05-01.01.
4. PE Code (only for discrete task orders)e - the NETWORK (baselined CAT chart) activity code (as opposed to the task code) with which the deliverable is associated. Provide a null value (“”) for LOE Task Order deliverables.
Example: "GLOPAT-100-022"
5. Negotiated Labor (only for discrete task orders) - the negotiated staff months associated with the network activity as documented in the negotiated ICE. . Used for earned value calculations. Provide a null value (“”) for LOE Task Order deliverables or for deliverables not specifically associated with a CAT chart activity code.
6. CDRL Code - The deliverable category, e.g., "QA01". A complete list of codes is available from the COTR.
7. Title - The title of the deliverable.
8. Draft/Final Flag - identifies the deliverable as "d" (Draft) or "f" (Final). Not case sensitive.
9. Due Date - the deliverable due date, in the format DD-MMM-YYYY or MM/DD/YYYY. If the deliverable is not scheduled with a due date it should not be provided in the download.
10. Primary Deliverable Flag - Provide "y" if the deliverable represents completion of a network activity. Provide a null value ("") if the deliverable is not a primary deliverable or is for an LOE Task Order.
D. Example
"NEW","1232","05-01.03","PTCSOM-OEM-130","1.7","GD16","Letter of Completion for Setup and Establish Configuration Management Control for OEMS","F”, “07/21/2005”, “y”
E. Validations
The following must be true on each line, or the entire download file is rejected:
1. Column 1 must say “NEW” - capability to update revised deliverables is not yet because a unique key is required.
2. Column 2 must contain the Contractor’s deliverable ID (a unique numeric that the contractor assigns). (the COTR can provide examples to the SDI contractors)
3. Column 3 must contain the task activity code.
The following must be true or the given line within the file is rejected:
1. Deliverable ID cannot already be present in the PDAMS database.
2. CDRL Code must be a valid code as stored in the PDAMS database.
SAMPLE
TOTAL COSTS
TASK ORDER LEVEL
TASK ORDER: 99-1 EXAMPLE TASK ORDER
GFY: 2014
OCT
NOV
DEC
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
GFY
CONTRACTOR LABOR COSTS
FACILITY A
LABOR CATEGORY A
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY B
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY C
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY D
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY E
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY F
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SUBTOTAL FACILITY A
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
TOTAL LABOR COSTS
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
DOCUMENT
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
TRAVEL
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
OTHERDIR
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
MATERIAL
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SERVICES
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
G&A/ODMS
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
2014 TOTAL DOLLARS
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
GRAND TOTAL DOLLARS
0.00
SAMPLE
LABOR HOURS
TASK ORDER LEVEL BY GFY
TASK ORDER: 99-1 EXAMPLE TASK ORDER
GFY: 2014
OCT
NOV
DEC
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
GFY
CONTRACTOR LABOR HOURS
FACILITY A
LABOR CATEGORY A
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY B
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY C
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY D
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY E
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY F
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SUBTOTAL
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
CONTRACTOR TOTAL HOURS
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
2014 TOTAL HOURS
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
2014 CONTRACTOR STAFF MONTHS
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
GRAND TOTAL HOURS
0.00
GRAND TOTAL STAFF MONTHS
0.00
SAMPLE
HOURS BY LABOR CATEGORY
TASK ORDER LEVEL
TASK ORDER: 99-1 EXAMPLE TASK ORDER
GFY: 2014
OCT
NOV
DEC
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
GFY
FACILITY A
LABOR CATEGORY A
COM-PRINCIPAL
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SUBTOTAL: CATEGORY A
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY B
COM-SENIOR
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SUBTOTAL: CATEGORY B
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY C
COM-MID LEVEL
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SUBTOTAL: CATEGORY C
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY D
COM-ASSOCIATE
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SUBTOTAL: CATEGORY D
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SAMPLE
HOURS BY LABOR CATEGORY
TASK ORDER LEVEL
TASK ORDER: 99-1 EXAMPLE TASK ORDER
(Page 2)
GFY: 2014
OCT
NOV
DEC
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
GFY
LABOR CATEGORY E
COM-ASSISTANT
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SUBTOTAL: CATEGORY E
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
LABOR CATEGORY F
NON-SR-SECRETARY
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
SUBTOTAL: CATEGORY F
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
2014 TOTAL DOLLARS
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
GRAND TOTAL HOURS
0.00
SAMPLE
DOCUMENTATION
TASK ORDER LEVEL
TASK ORDER: 99-1 EXAMPLE TASK ORDER
DOCUMENT
ART
FOLDOUT
INTERNAL
CLIENT
TOTAL
ACTIVITY
MONTH
CDRL
TYPE
NAME
PAGES
PAGES
PAGES
VOLUMES
COPIES
COPIES
COST
99-1.1.1
JUL 14
N/A F
SAMPLE
0.00
GFY 2014 TOTAL TASK: 99-1.1
0.00
TOTAL DOCUMENTATION FOR TASK: 99-1.1
0.00
TOTAL DOCUMENTATION FOR TASK ORDER: 99-1
0.00
SAMPLE
OTHER DIRECT COSTS
ACTIVITY
MONTH
ITEM NAME
QUANTITY
UNIT
PER UNIT
ODC EXAMPLE
0.00 0.00
GFY 1995 TOTAL FOR TASK: 99-1.1
0.00
TOTAL OTHER DIRECT COSTS FOR TASK: 99-1.1
0.00
TOTAL ODCs FOR TASK ORDER: 99-1 0.00
SAMPLE
LOCAL TRAVEL
PARKING
MONTH
# TRIPS
R/T MILES
FEE
TOLL
0.00 0.00 0.00 0.00
GFY 2014 TOTAL FOR TASK: 99-1.1
0.00
TOTAL LOCAL TRAVEL FOR TASK: 99-1.1
0.00
TOTAL LOCAL TRAVEL FOR TASK ORDER: 99-1
0.00
SAMPLE
DISTANT TRAVEL
# CAR
RENTAL
PER
AIR
ACTIVITY
MONTH
FROM
TO
# TRIPS
# PEOPLE
# DAYS
# NIGHTS
# CARS
DAYS
FEE
DIEM
HOTEL
FARE
HERE
THERE
0.00 0.00 0.00 0.00
GFY 2014 TOTAL TASK: 99-1.1
0.00
TOTAL DISTANT TRAVEL FOR TASK: 99-1.1
0.00
TOTAL DISTANT TRAVEL FOR TASK ORDER: 99-1
0.00
SAMPLE
BILL OF MATERIALS
PARKING
MONTH
ITEM NAME
QUANTITY
UNIT
PER UNIT
MATERIAL EXAMPLE
0.00 0.00
GFY 2014 TOTAL FOR TASK: 99-1.1
0.00
TOTAL MATERIAL FOR TASK: 99-1.1
0.00
TOTAL MATERIAL FOR TASK ORDER: 99-1
0.00
SAMPLE
Contract Task Order Accounting Cost Element Codes
September 16, 2014 These codes are used to identify hours and/or dollars as appropriate.
Labor Codes
01 Program Manager
02 Project Manager
03 Principal Transition Project Manager
04 Principal Software Engineer
05 Senior Software Engineer
06 Junior Software Engineer
07 Senior Communications Engineer
08 Operations Research Analyst
09 Principal Systems Engineer
10 Senior Systems Engineer
11 Principal Information Engineer
12 Principal Business Process Engineer
13 Senior Info Engineer /Bus Pro Engineer
14 Junior Info Engineer /Bus Pro Engineer
15 Database Specialist
16 Senior Info Systems Specialist
17 Junior Info Systems Specialist
18 Principal Systems Analyst/ Programmer
19 Senior Systems Analyst/ Programmer
20 Junior Systems Analyst/ Programmer
21 Systems Programmer
22 Subject Matter Specialist
23 Library Scientist or Computer Specialist
24 Technical Writer/Editor
25 Administration and Clerical Staff
26 Senior Business Support Admin
27 Junior Business Support Admin
28 Reserved
29 Reserved
50 Principal Systems Architect
55 Principal IT Security Engineer
56 Senior IT Security Engineer
60 Principal Network Engineer
61 Senior Network Engineer
62 Junior Network Engineer
65 Acquisition Support Staff
File details come from the government source that posted it. Updated .