Attachment_1Final.pdf
PDF 177 KB Posted
- Attached to
- technical support services for the DLA Sustainment, Restoration and Modernization Federal contract opportunity
- Solicitation number
- SP060016R0400
- Issued by
- Defense Logistics Agency Energy
About this file
Attachment 1 - TMP Spreadsheet
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Amendment_2_.pdf | ||
| 16-R-0400_conformed_thru_amend002.pdf | ||
| Attachment_2_QUASP.pdf | ||
| Amend_001_16-R-0400.pdf | ||
| Exhibit_A_Price_Sup_Data.pdf | ||
| SP0600-16-R-0400_conformed_thru_amend001.pdf | ||
| SP0600-16-R-0400_final.pdf | ||
| Small_Business_Subk_Plan_Exhibit_C.pdf | ||
| 16-R-0400_Exhibit_B_Past_Performance.docx | DOCX document |
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
Data Field Definition Input type for tool Function / Format
Project Manager Name of the Project Manager (PM) assigned to this site from the DLA SRM Office. Dropdown Full first and last name
DLA Site Code DLA Site Code abbreviation of the Installation where the tank is located. Dropdown Alphanumeric code
Site Name Name of site. Auto-populated Auto-populated based on DLA Site Code
DoD Site Code An 8 digit alphanumeric code used by the DoD to track sites. Auto-populated Auto-populated based on DLA Site Code
State State where the tank is located. Auto-populated Auto-populated based on DLA Site Code Country Country where the tank is located. Auto-populated Auto-populated based on DLA Site Code
Region Military region where the tank is located. Auto-populated
Auto-populated based on DLA Site Code with the following options: Americas, Europe & Africa, Mideast, Pacific
COCOM
Combatant Command (COCOM) abbreviation for the tank entry as designated in EBS. Auto-populated Auto-populated based on DLA Site Code
MAJCOM
Major Command (MAJCOM) abbreviation for the tank entry as designated in EBS. Auto-populated
Auto-populated based on DLA Site Code for Army and Air Force tanks only
FLC
Name of the Fleet Logistics Center (FLC) responsible for the tank entry. Dropdown
Dropdown populates based off of DLA Site Code; The format is a set FLC name for Navy tanks only
Service Military Service that owns and operates the tank. Dropdown Dropdown option RPUID Real property unique identifier for the tank. Manual Input Text limited to 5-10 characters Tank ID Unique tank identifier. Auto-populated Automatically generated by Tool
EBS Facility Number Facility number as identified by the real property record. Manual Input Text Facility Name Name of facility. Manual Input Text
Local Tank Name
Any additional information about the tank, such as numbers or names, to help the PM identify the specific tank. Manual Input Text
Current Tank Product Indicates what type of product (e.g., fuel type, other product) is held in tank. Dropdown Dropdown with fuel options
Shell Capacity (Ga.)
Amount of product that the tank can hold in gallons, as indicated on the Real Property record. Manual Input Number format required. Units: Ga.
Safe Fill Capacity (Ga.)
Amount of product that the tank can hold safely, as originally indicated on the Real Property record and modified based on tank age, inspection reports, and other properties.
Auto-populated with optional free number entry
Auto-populated based on Shell Capacity. Safe Fill Capacity is assumed to be 95% of the Shell Capacity for a tank, but can be overwritten up to 100% of Shell Capacity. Units: Ga.
Status
Binary field that indicates if the tank is in or out of service, with out of service being defined as when the tank is turned over to the contractor for inspection and/or repair. Dropdown
Binary dropdown with following options: In Service, Out of Service
Out of Service Date The date that the tank was taken out of service.
Log with series of Out of Service Dates populated with new date entry fields. Date; Format is: MM/DD/YYYY
Back into Service Date The date that the tank was put back into service.
Log with series of In Service Dates populated with new date entry fields. PM can change historical dates Date; Format is: MM/DD/YYYY
Inspection Type Type(s) of inspections required for the tank. Dropdown
Dropdown with the following options: STI, API 653 Internal, API 653 External, API 653 Modified, TUEV, Other
SP0600-16-R-0400
Attachment 1 Page 1 of 11
SOURCE SELECTION INFORMATION – See FAR 2.101 and 3.104
TASK ONE - Tank Management Plan TMP Data Fields
Actual Inspection Date Date that the inspection was performed on the tank.
Log of historical Actual Inspection Dates for a given Inspection Type for each tank, with capabilities to add multiple Actual Inspection Dates and to forecast future tank out of compliance dates.
Tool will record all previous dates of inspection for a given Inspection Type for each tank.
Date; Format is: MM/DD/YYYY
Final Inspection Report Received Date
Date the final inspection report is received by SRM from the EA. Free date entry Date; Format is: MM/DD/YYYY
Inspection Frequency Recommended frequency of inspections for the tank. Auto-populated
Auto-populated based on Inspection Type;
initial data entry will reflect the following rules:
API - External inspection date will be 5 years from previous inspection date, API - Internal inspection date will be 10 years from previous inspection date, STI - Inspection date will be 10 years from previous inspection date, TUEV - Inspection date will be 5 years from previous inspection date. Other - Inspection date will not be forecasted based on the previous inspection date. Users can override these rules; Units:
Years, Days, Months
Tank Inspection Out of Compliance Date (Tank OOC Date)
The date a tank inspection is required based on inspection type and historical inspection information.
Auto-populated with optional free date entry field
Auto-populated based on the previous inspection record and Future Tank Inspection Out of Compliance Date that is calculated
Planned Inspection Date Planned date of tank inspection. Free date entry Date; Format is: MM/DD/YYYY
Programmed Year The fiscal year that an inspection is programmed (i.e.
funded) for. Auto-populated
Auto-populated based on the Programmed Date
Fiscal Year The fiscal year that an inspection will be out of compliance. Auto-populated
Auto-populated based on the Tank Inspection Out of Compliance Date (Tank OOC Date)
Business Entity (BE) Business Entity (BE) number of the tank entry as designated in EBS. Auto-populated
Auto-populated based on the DLA Site Code;
Only using the number part of the business entity
Tank Type Indicator of tank type according to industry standards and capacity. Dropdown
Dropdown with the following options: API Aboveground, API Cut & Cover, STI, Other
Aboveground Storage Tank
Indicator of if the tank is an aboveground storage tank (AST) and therefore is tracked by SRM. If no, it is an underground storage tank (UST) and tracked by another entity. Dropdown Binary with Yes and No as options
Execution Agent (EA) Designated EA to manage the tank.
Auto-populated with optional dropdown
Auto-populated based on the Service associated with the DLA Site Code; initial data entry will reflect the following rules: Air Force - AFCEC, Army - USACE, Navy - NAVFAC.
Users can override these rules with the following dropdown options: AFCEC, NAFAC, SPAWAR, USACE
Cathodic Protection Indicates if the tank has Cathodic Protection (CP). Dropdown Binary with Yes and No as options Stilling Wells Indicates the amount of stilling wells in the tank. Dropdown Binary with Yes and No as options
Last Edit Date Date on which the last edit to a tank or inspection entry was made. Auto-populated
Auto-populated based on last edit made. Each tank and inspection record will have a last edit date if it has been edited after being created
Last Edited By User that last edited a tank or inspection entry. Auto-populated Auto-populated based on the last edit made
Construction Year Year that construction was completed for the tank. Free calendar year entry Calendar year; Format is: 4 numbers
SP0600-16-R-0400
Attachment 1 Page 2 of 11
Comments Free entry comment field about the tank. Free text entry Text
Compliance Status (New) Indicates if an inspection is In Compliance, Out of Compliance, or has an Unknown Compliance Status. Auto-populated
Auto-populated based on if the Tank Inspection Out of Compliance Date (Tank OOC Date) is before today's date, past today's date, or unknown
Expected Back into Service Date (New)
The expected date that the tank will be put back into service. Free date entry Date; Format is: MM/DD/YYYY
Future Tank Inspection Out of Compliance Date (New)
The date recommended for the next tank inspection based on inspection type and historical inspection information.
Auto-populated with optional free date entry field
Auto-populated based on latest Inspection Date and Inspection Frequency for an Inspection Type for a given tank. Used to populate Tank Inspection Out of Compliance Date for the next inspection record
Inspection Comments (New)
Free entry comment field about the historical or forecasted inspection. Free text entry Text
Inspection ID (New) Unique inspection identifier. Auto-populated Automatically generated by Tool
Inspection Planning Action Required (New)
Identifies a tank inspection with a Tank Inspection Out of Compliance Date in the next year with no Programmed Date. Auto-populated
Auto-populated based on the Tank Inspection Out of Compliance Date (Tank OOC Date), Programmed Date, and Actual Inspection Date
Out of Service Justification (New) The reason that the tank was taken out of service. Dropdown
Dropdown with the following options:
Inspection, Repair, Service Directed, Notice of Violation, Associated Facility Work, Replacement, Other
Programmed Date (New) The date in which an inspection is programmed (i.e.
funded). Free date entry Date; Format is: MM/DD/YYYY
Safe Fill Capacity (Bbl.)
(New)
Amount of product that the tank can hold safely, as originally indicated on the real property record and modified based on tank age and other properties.
Auto-populated based on Safe Fill Capacity (Ga.)
Auto-populated based on Safe Fill Capacity (Ga.). Units: Bbl.
Shell Capacity (Bbl.)
(New)
Amount of product that the tank can hold in barrels, as indicated on the real property record.
Auto-populated based on Shell Capacity (Ga.)
Auto-populated based on Shell Capacity (Ga.).
Units: Bbl.
SP0600-16-R-0400
Attachment 1 Page 3 of 11
User Type Functionality / Permissions Description Intended Users
Read-Only
- Ability to run reports and view metrics for all tanks and associated inspections under SRM cognizance.
- These users will not have the ability to input or edit any tank or inspection data.
- It is expected that read-only access will be provided to a select numbers of users outside the SRM Division.
Users from DLA Energy Supply Integration, DLA Installation Support, External Organizations outside DLA
Project Manager
(PM)
- Ability to add, input, and edit data for tanks and inspections at the DLA Site Codes under their responsibility. This includes the ability to add new tanks.
- Ability to run reports / view metrics for all tanks and associated inspections under SRM cognizance.
- These users will not have the ability to delete tanks, inspections, or out of service records
All PMs in the SRM Division
Project Manager Administrator
- Ability to add, input, and edit data for tanks and inspections at all DLA Site Codes for their respective Service. This includes the ability to add new tanks.
- Ability to run reports / view metrics for all tanks and associated inspections under SRM cognizance.
- These users will not have the ability to delete tanks, inspections, or out of service records
Select PMs in the SRM Division; typically designated by the Branch Chiefs
Division Chief / Branch Chief / PAMP Team
- Ability to input and edit data for tanks and inspections at all DLA Site Codes under SRM's responsibility.
-Ability to approve when tanks are added and deleted in the TMP Tool by the Project Manager user type.
- Ability to run reports / view metrics for all tanks and associated inspections under SRM cognizance.
- Ability to delete tanks
SRM Division PAMP Team and Leadership (i.e. Branch Chiefs, Division Chief)
System Administrator
- Ability to input and edit data for tanks and inspections at all DLA Site Codes under SRM's responsibility.
- Ability to run reports / view metrics for all tanks and associated inspections under SRM cognizance.
- Ability to delete tanks
- In addition, this user-type will have the ability to update functions such as updating the PM to DLA Site Code mapping, updating the DLA Site Code of specific tanks, accessing and deleting out of service records, and other functions required to enhance/maintain system records
SRM Division PAMP Team
SP0600-16-R-0400
Attachment 1 Page 4 of 11
TASK ONE - Tank Management Plan TMP Users
Count Description Data Field Inputs Data Field Filter Calculation, Target, and Thresholds
Total Tanks Count of all tanks tracked Total number of tanks entered in system EA, Service, COCOM
Total API Tanks Count of all API 653 tanks tracked
Total number of tanks entered in system, differentiated by Storage Tank Type (include API Aboveground and API Cut & Cover) EA, Service, COCOM
Total API Aboveground Tanks
Count of all API 653 Aboveground tanks tracked
Total number of tanks entered in system, differentiated by Storage Tank Type (include API Aboveground) EA, Service, COCOM
Total API Cut & Cover Tanks
Count of all API 653 Cut & Cover tanks tracked
Total number of tanks entered in system, differentiated by Storage Tank Type (include API Cut & Cover) EA, Service, COCOM
Total STI Tanks Count of all STI tanks tracked
Total number of tanks entered in system, differentiated by Storage Tank Type (include STI) EA, Service, COCOM
Total Out of Service Tanks
Count of all Out of Service tanks tracked Total number of tanks entered in system when Status = Out of Service EA, Service, COCOM, PM
Total Out of Compliance Tanks
Count of all Out of Compliance tanks tracked
Total number of tanks entered in system where the current date is past the most recent Tank Inspection Out of Compliance Date EA, Service, COCOM, PM
Total Open Inspections
Count of all upcoming inspections tracked
Total number of open inspections entered in system, found using Tank Inspection Out of Compliance Date, Inspection Date, and Inspection Frequency
EA, Service, COCOM, PM, DLA Site Code, Fiscal Year
Calculation
1. Inspection Type and Inspection Frequency define the inspection type a tank requires and at what intervals it needs to undergo those inspections
2. Inspection Date defines the last inspection date(s) according to the corresponding Inspection Type(s). The Inspection Date and Inspection Frequency result in the Tank Inspection Out of Compliance Date(s).
3. Tank Inspection Out of Compliance Date(s) for each tank should be entered into the Inspection Log (next tab) as separate line items, for fiscal year planning purposes.
Total Open API 653 Inspections
Count of all upcoming API 653 inspections tracked
Total number of open inspections entered in system, found using Tank Inspection Out of Compliance Date, Inspection Date, and Inspection Frequency (including API External, API Internal/External, and API Modified Inspection Types)
EA, Service, COCOM, PM, DLA Site Code, Fiscal Year See "Total Open Inspections" Report Calculation
Total Open API 653 Internal/External Inspections
Count of all upcoming API 653 Internal/External inspections tracked
Total number of open inspections entered in system, found using Tank Inspection Out of Compliance Date, Inspection Date, and Inspection Frequency (including API Internal/External Inspection Type)
EA, Service, COCOM, PM, DLA Site Code, Fiscal Year See "Total Open Inspections" Report Calculation
Total Open API 653 External Inspections
Count of all upcoming API 653 External inspections tracked
Total number of open inspections entered in system, found using Tank Inspection Out of Compliance Date, Inspection Date, and Inspection Frequency (including API External Inspection Type)
EA, Service, COCOM, PM, DLA Site Code, Fiscal Year See "Total Open Inspections" Report Calculation
Total Open API 653 Modified Inspections
Count of all upcoming API 653 Modified inspections tracked
Total number of open inspections entered in system, found using Tank Inspection Out of Compliance Date, Inspection Date, and Inspection Frequency (including API Modified Inspection Type)
EA, Service, COCOM, PM, DLA Site Code, Fiscal Year See "Total Open Inspections" Report Calculation
Total Open STI Inspections
Count of all upcoming STI inspections tracked
Total number of open inspections entered in system, found using Tank Inspection Out of Compliance Date, Inspection Date, and Inspection Frequency (including STI Inspection Type)
EA, Service, COCOM, PM, DLA Site Code, Fiscal Year See "Total Open Inspections" Report Calculation
Total Open TUEV Inspections
Count of all upcoming TUEV inspections tracked
Total number of open inspections entered in system, found using Tank Inspection Out of Compliance Date, Inspection Date, and Inspection Frequency (including TUEV Inspection Type)
EA, Service, COCOM, PM, DLA Site Code, Fiscal Year See "Total Open Inspections" Report Calculation
Out of Compliance Risk
Count of all tanks Out of Compliance or at risk of becoming Out of Compliance
Total number of open inspections entered in system with upcoming Tank Inspection Out of Compliance Dates (i.e. tanks with Tank Inspection Out of Compliance Dates within the next 6, 12, and 18 months)
EA, Service, COCOM, PM, DLA Site Code
Calculation
- Tank Out of Compliance = Current date - Tank Inspection Out of Compliance Date (inspection due date) Thresholds
- Green: > 6 months until Tank Inspection Out of Compliance Date
- Yellow: ≤ 6 months and > 90 days until Tank Inspection Out of Compliance Date
- Orange: ≤ 90 days until Tank Inspection Out of Compliance Date
- Red: Current date is past the Tank Inspection Out of Compliance Date
SP0600-16-R-0400
Attachment 1 Page 5 of 11
Metric Description Data Field Inputs Calculation, Target, and Thresholds Filters Purpose and Priority Type and Min. Frequency Required
Tanks Out of Service Rate Percentage of tanks out of service out of the total tank population
Status Calculation
- Tank OOS Percentage = Sum (tanks with OOS status) / Sum (all tanks) Target
- Less than 10% of tanks Thresholds
- Green: ≤ 10% of tanks
- Yellow: > 10% and < 20% of tanks
- Red: ≥ 20% of tanks
- COCOM, Service, PM
- Currently reported in the APR: COCOM by EA, EA by COCOM
Provides high-level understanding of the proportion of tanks in/out of service
Type
- Point in time metrics Min. Frequency Required
- Quarterly
Safe Fill Capacity of Tanks Out of Service (Barrels)
Percentage of safe fill capacity of tanks out of service out of total safe fill capacity (in barrels) of the total tank population
Status, Safe Fill Capacity
Calculation
- Capacity OOS Percentage = Sum (safe fill capacity of tanks with OOS status) / Sum (safe fill capacity of all tanks) Target
- Less than 10% of capacity Thresholds
- Green: ≤ 10% of capacity
- Yellow: > 10% and < 20% of capacity
- Red: ≥ 20% of capacity
- COCOM, Service, EA
- Currently reported in the APR: COCOM by EA, EA by COCOM
Provides high-level understanding of the proportion of tank capacity in/out of service
Type
- Point in time metrics Min. Frequency Required
- Quarterly
Tanks Out of Compliance Rate which includes three components:
- Percentage of Tanks In Compliance
- Percentage of Tanks Out of Compliance
- Percentage of Tanks with Unknown Compliance
Percentage of tanks out of compliance out of the total tank population
Tank Inspection Out of Compliance Date
Calculation
- Tank Out of Compliance Percentage = Sum (tanks with Out of Compliance status) / Sum (all tanks)
- Tank In Compliance Percentage = Sum (tanks In Compliance status) / Sum (all tanks)
- Tank Unknown Compliance Percentage = Sum (tanks with Unknown Compliance status) / Sum (all tanks) Target
- Less than 10% of tanks out of compliance Thresholds (will vary by service)
- Green: ≤ 10% of tanks out of compliance
- Yellow: > 10% and < 20% of tanks out of compliance
- Red: ≥ 20% of tanks out of compliance
COCOM, Service, EA Provides high-level understanding of the proportion of tanks in/out of compliance
Type
- Point in time metrics Min. Frequency Required
- Quarterly
Bow Wave
- Needs to be presented in terms of number of tanks and safe fill capacity
Tanks and associated safe fill capacity that is In Service and Out of Compliance or Unknown Compliance on an API Internal or API Modified Inspection Requirement
Safe Fill Capacity (bbls); Tank Inspection Out of Compliance Date;
Inspection Type;
Tank Status
Calculation
- Number of tanks and associated safe fill capacity (bbls) which are:
- In Service
- Out of Compliance or Unknown Compliance
- API Internal or API Modified Inspection Type
Target
- To be determined (new metric) Thresholds
- To be determined (new metric)
COCOM, Service, EA Provides the number of tanks and associated safe fill capacity which will need to be taken out of service in the near future to conduct inspections and associated repairs.
Type
- Point in time metrics Min. Frequency Required
- Quarterly
Tanks Currently Out of Service by Number of Days
- Includes the Backlog of tanks which are those tanks that have been out of service for 365+ days
Number of tanks currently out of service distributed by the number of days that each tank has been out of service.
Status, Date Out of Service (Out of Service Justification:
All)
Calculation -Number of days between current date and Date Out of Service Target -Less than 365 days Thresholds
- Green: Tanks Out of Service between 0-179 days
- Yellow: Tanks Out of Service between 180-269 days
- Orange: Tanks Out of Service 270-364 days
- Red: Tanks Out of Service 365+ days (Backlog) -Gray: Tanks with unknown number of Out of Service days (this category should exist, but the target is to always have it be zero)
-COCOM, Service EA Provide high-level understanding of tanks Out of Service for extended periods of time that should be focused on.
Type
- Point in time metrics Min. Frequency Required
- Quarterly
Average Out of Service Time for Tanks
- Reason: Inspection
- Reason: Mandatory Repairs
Measures the timeliness that a tank is entered back into service
Out of Service Status: Date Out of Service, Date Entered Back into Service (Out of Service Justification:
All)
Calculation
- Number of days between Date Out of Service and Date Entered Back into Service Target
- < 365 days out of service Thresholds
- Green: Less than 180 days OOS
- Yellow: 180 - 269 days OOS
- Orange: 270 - 365 days OOS
- Red: 365+ days OOS
- COCOM, Service, EA
- OOS Justification: All, Inspections, Repairs
Indicator of the efficiency of tanks being entered back into service
Type
- Average over period of time (by Fiscal Year and Year-to-Date) Min. Frequency Required
- Monthly
Final Inspection Report Received Percentage
Percentage of final inspection reports received out of all inspections completed for a given fiscal year
Inspection Date, Date Final Inspection Report Received
Calculation
- Final Inspection Report Received Percentage = Sum (tanks with Date Final Inspection Report Received entered, in the given fiscal year) / Sum (tanks with Inspection Date entered, in the given fiscal year) Target
- To be set after calculating the historical average to date Thresholds
- To be set after calculating the historical average to date
COCOM, Service, EA Provides high-level understanding of the proportion of final inspection reports received for all inspections completed
Type
- Point in time metrics Min. Frequency Required
- Monthly
Average Time to Receive Final Inspection Report
Measures the timeliness of when final reports are received for tank inspections
Next Planned Inspection Date, Date Final Inspection Report Received
Calculation
- Time to Inspect & Receive Final Inspection Report = Count of Days (Next Planned Inspection Date - Date Received Final Inspection Report) Target
- To be set after calculating the historical average to date Thresholds
- To be set after calculating the historical average to date
COCOM, Service, EA Indicator of the efficiency of tank inspections and process to receive final inspection reports
Type
- Average over period of time (by Fiscal Year and Year-to-Date) Min. Frequency Required
- Monthly
SP0600-16-R-0400
Attachment 1 Page 6 of 11
Data Field Comment
Assigned DLA SRM PM
Name of the Project Manager (PM) assigned to this project entry from the DLA SRM office
Select appropriate PM name in first name last name format from the drop down menu
DLA Site Code
DLA Site Code abbreviation of the project entry from EBS
Select appropriate 3 letter Site Code abbreviation from the drop down menu
Note: Columns E – L auto-populate based on Site Code entry. If Site information needs to be modified, update Site Code entry only.
Installation (DFSP) / Location
Installation name of the Defense Fuel Support Point (DFSP) and/or location of the project entry as designated by the PM
Full Installation name will be auto-populated for the project entry based on the DLA Site Code entered. Please do not modify Installation (DFSP) / Location field once it is auto-populated.
Service
Military Service of the project entry as designated in EBS
Service name will be auto-populated for the project entry based on the DLA Site Code entered. Please do not modify the Service field once it is auto-populated.
Major Command (MAJCOM)
Major Command (MAJCOM) name of the project entry as designated in EBS
Command abbreviation will be auto-populated for the project entry based on the DLA Site Code entered. Please do not modify MAJCOM field once it is auto-populated.
Fleet Logistics Center (FLC)
Fleet Logistics Center (FLC) name of the project entry as designated in EBS
Command abbreviation will be auto-populated for the project entry based on the DLA Site Code entered. Please do not modify FLC field once it is auto-populated.
Region/ Secondary Level Field Activity (SFLA)
Geographical Region / Secondary Level Field Activity (SLFA) of the project entry as designated in EBS
Region / SLFA will be auto-populated for the project entry based on the DLA Site Code entered. Please do not modify the Region / SLFA field once it is auto-populated.
Country
Country location of the project entry as designated in EBS
Country will be auto-populated for the project entry based on the DLA Site Code entered. Please do not modify Country field once it is auto-populated.
DoD Site Code
Department of Defense (DoD) site code of the project entry as designated in EBS
DoD Site Code alphanumeric abbreviation will be auto-populated for the project entry based on the DLA Site Code entered.
Please do not modify DoD Site Code field once it is auto-populated.
Business Entity (BE) Name
Business Entity (BE) Name of the project entry as designated in EBS
BE Name will be auto-populated for the project entry based on the DLA Site Code entered. Please do not modify BE name field once it is auto-populated.
Combatant Command
(COCOM)
Combatant Command (COCOM) of the project entry as designated in EBS
COCOM will be auto-populated for the project entry based on the DLA Site Code entered. Please do not modify COCOM field once it is auto-populated.
Deficiency Number
Number of deficiency line item as designated in EBS, which is used to create projects / Work Breakdown Structure (WBS) elements in EBS
Insert full deficiency number for the line item.
Deficiency Line Item Date
Final date of the deficiency line item's initiation as designated by the PM
Insert deficiency line item date in MM/DD/YYYY format.
SP0600-16-R-0400
Attachment 1 Page 7 of 11
TASK TWO - SRM Project Tracker Data Fields and Definitions
EBS Project Number
Project number assigned by EBS to the project entry
Insert alphanumeric project number as noted in EBS for the project entry.
WBS Element
WBS Element as designated in EBS. For full WBS number, reference the EBS Project Number and WBS Element fields
Select appropriate last three digits of WBS Element in .### format from the drop down menu.
Fiscal Year
Fiscal year during which the project entry began as tracked by the PM
Select appropriate fiscal year in the format FY## from the drop down menu.
Project Type
Project type of the entry as designated by the PM
Select appropriate project type description from the drop down menu.
Pillar
Pillar of the project entry as designated by the PM (i.e., Recurring Maintenance & Minor Repair [RM], Centrally Managed Programs [CMP], Planning Studies [PLAN], Emergent [EMG])
Pillar will be auto-populated for the project entry based on the Project Type selected. Please do not modify the Pillar field once it is auto-populated.
Project Title
Title of the project entry as designated in EBS
Insert project title text for the project entry.
Work Classification
Classification of the work involved with the project entry
Select appropriate classification from the drop down menu.
EBS Purchase Request (PR) Number
Purchase Request (PR) number assigned by EBS to the project entry
Insert PR number as noted in EBS for the project entry.
Date Project Purchase Request (PR) Parked
Final date on which the Purchase Request (PR) was submitted to Finance. At this point, the PM still retains the full ownership of the PR and the PR is editable; however, the PM must communicate to Finance any changes being made via e-mail.
Insert date in MM/DD/YYYY format.
MIPR Number
Military Interdepartmental Purchase Request (MIPR) number of the project entry as designated in EBS
Insert the MIPR number as noted in EBS for the project entry.
MIPR Type
Type of Military Interdepartmental Purchase Request (MIPR) (e.g., Basic, Amendment, Revised, De-obligated) of the project entry as designated by the PM
Select appropriate type from the drop down menu.
MIPR Amount
Dollar amount of the Military Interdepartmental Purchase Request (MIPR) for the project entry as designated by the PM
Insert dollar amount.
Date MIPR Committed
Final date that the Military Interdepartmental Purchase Request (MIPR) was committed for the project entry as tracked by the PM
Insert date in MM/DD/YYYY format.
Executing Engineering Agent
Name of the Executing Engineering Agent entity for the project entry as designated by the PM
Select appropriate entity name for the project entry.
Executing Agent PM
Name of the PM for the project entry from the Executing Agent (EA) entity
Insert Executing Agency PM name in first name last name format.
SP0600-16-R-0400 Attachment 1
Date MIPR Accepted By EA
Final date that the Military Interdepartmental Purchase Request (MIPR) was accepted for the project entry by the Executing Agent (EA) as tracked by the PM
Insert date in MM/DD/YYYY format.
Acceptance Category
Acceptance category code (i.e., CAT I, CAT II, CAT I and II) for the project entry as designated by the PM
Select appropriate acceptance category for the project entry.
Amount Obligated By EA
Dollar amount of funding obligated by the Executing Agent (EA) for the project entry as designated by the PM
Insert dollar amount.
DLA Purchase Order Number
Purchase Order number in DLA system for the project entry as tracked by the PM
Insert Purchase Order number for the project entry.
DLA Purchase Order Date
Final date that the DLA Purchase Order for the project entry was completed as designated by the PM
Insert date in MM/DD/YYYY format.
Date Site Visit / Inspection Completed
Date that the site visit and/or inspection for the project entry was completed
Insert date in MM/DD/YYYY format.
Date Initial Report Received
Date that the first report (previously known as Engineering Field Assessment Report [EFAR], Trip Report, or Deficiency Summary Report [DSR]) was received after the site visit for project entry
Insert date in MM/DD/YYYY format.
Date Project Package / Statement of Work Received
Date that the project package and/or Statement of Work (SOW) for the project entry was received as designated by the PM.
This also includes CMP inspection reports
Insert date in MM/DD/YYYY format.
Design (Y/N)
Indicate if there is a design for the project entry
Select “Y” for Yes and “N” for No from the drop down menu
Notice To Proceed Date
Final date that a notice to proceed for the project entry was received as tracked by the PM
Insert date in MM/DD/YYYY format. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed.
Design Contract Number
Contract number for the design of the project entry as tracked by the PM
Insert the number. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed.
Design Contract Date
Final date that the design contract for the project entry was awarded as tracked by the PM
Insert date in MM/DD/YYYY format. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed.
Design Architect Engineer Name
Name of the Architect-Engineer (AE) firm responsible for the design of the project entry as tracked by the PM
Insert in first name last name format. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed.
Design Contract Amount
Dollar amount of the contract for the design of the project entry as tracked by the PM
Insert dollar amount. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed.
Design Start Date
Dollar amount of the contract for the design of the project entry as tracked by the PM
Insert dollar amount. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed.
SP0600-16-R-0400 Attachment 1
Proposed Design Finish Date
Proposed date on which the design for the project entry is anticipated to be completed
Insert date in MM/DD/YYYY format. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed.
% Design Completed
Percentage completion of the design for the project entry as tracked by the PM
Select appropriate percentage from 0-100%, in increments of 10%, from the drop down. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed
100% Design Date
Projected date on which the design for the project entry is anticipated to be 100% complete
Insert date in MM/DD/YYYY format. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed.
Actual Design Completion Date
Final date on which the design for the project entry was actually completed
Insert date in MM/DD/YYYY format. Please note that if “N” was selected in the Design field, this field will be blacked out and does not need to be completed.
Beneficial Occupancy Date (BOD) Actual (eContracts)
Final date on which the beneficial occupancy process was completed for the project entry (through eContracts, if applicable)
Insert date in MM/DD/YYYY format.
EA Purchase Order Number
Executing Agent (EA) Purchase Order number for the project entry as tracked by the PM
Insert Purchase Order number.
EA Purchase Order Item Number
Executing Agent (EA) Purchase Order Item number for the project entry as tracked by the PM
Insert Purchase Order Item number.
EA Purchase Order Date
Final date of the Executing Agent (EA) Purchase Order submission for the project entry as tracked by the PM
Insert date in MM/DD/YYYY format.
EA Purchase Order Value ($)
Dollar value of the Executing Agent (EA) Purchase Order for the project entry as tracked by the PM
Insert dollar amount.
RFP / IFB Issued
Final date that the Request for Proposal (RFP) / Invitation for Bid (IFB) was issued for the project entry as designated by the
PM
Insert date in MM/DD/YYYY format.
Date Of Contract Award
Final date that the contract was awarded for the project entry as designated by the PM
Insert date in MM/DD/YYYY format.
Contract Number / Task Order Number
Contract number and/or task order number for the project entry as designated by the PM
Insert contract number and/or task order number, separating numbers by a comma if necessary.
Contract Award Amount / Task Order Amount
Dollar value of the contract award and/or task order for the project entry as designated by the PM
Insert dollar amount, separating dollar values by a comma if necessary.
Contractor Name
Name of the contractor responsible for the project entry as designated by the PM
Insert full name of the contractor.
Date Facility Turned Over To
EA
Final date that the facility for the project entry was turned over to the Executing Agent (EA) as designated by the PM
Insert date in MM/DD/YYYY format.
Construction Start Date
Final date that the construction started for the project entry as designated by the PM
Insert date in MM/DD/YYYY format.
SP0600-16-R-0400 Attachment 1
Proposed Construction Finish Date
Date on which the construction for the project entry is anticipated to be completed as designated by the PM
Insert date in MM/DD/YYYY format.
Contract Completion Date
Date on which the contract is anticipated to be completed for the project entry as designated by the PM
Insert date in MM/DD/YYYY format.
Contract Project Modifications
List of any contract modifications for the project entry as designated by the PM
Insert list of contract modifications, separating modification descriptions by a comma if necessary.
Period Of Performance (Number Of Calendar Days)
Number of days of the contract’s period of performance for the project entry as designated by the PM
Insert the number of calendar days to indicate period of performance duration
Project Final Report Received
Date on which the final report (previously known as the Project Package Report, Statement of Work [SOW], Work Plan, or 35% Design Document) containing technical scope and cost estimates as applicable for the project entry was received by the
PM
Insert date in MM/DD/YYYY format.
Project Technically Complete
Final date on which the project entry is technically completed as designated by the PM
Insert date in MM/DD/YYYY format.
% Construction Completed
Percentage completion of construction for the project entry as tracked by the PM
Select appropriate percentage from 0-100%, in increments of 10%, from the drop down.
Revised Contract Completion Date
Updated date on which the contract is anticipated to be completed for the project entry as designated by the PM
Insert date in MM/DD/YYYY format.
Actual Contract Completion Date
Final date on which the contract was completed for the project entry as designated by the PM
Insert date in MM/DD/YYYY format.
Amount Of Unobligated Funds Available
Dollar amount of available funds that are unobligated for the project entry as tracked by the PM
Insert dollar amount.
Date Unobligated Funds Returned To DLA
Final date that unobligated funds for the project entry were returned to DLA as tracked by the PM
Insert date in MM/DD/YYYY format.
Project Final Closure Date
Final date that the project entry was closed as designated by the PM
Insert date in MM/DD/YYYY format.
Status/Comments (Format - MM/DD/YYYY: PM Initials-Comment)
Any additional comments about the project entry to understand status and/or risks
Insert comments in the format of “MM/DD/YYYY date: PM initials – text of the comment”.
SP0600-16-R-0400 Attachment 1
| Appendix A - TMP Data Fields |
| Appendix C - TMP Users |
| Appendix E - TMP Reports |
| Appendix F - TMP Metrics |
| Attachment 1 TMP Spreadsheet.pdf |
| Sheet1 |
File details come from the government source that posted it. Updated .