Attachment_09d_-_Task_Order_01-Transition_and_Sustainment_Contract_Data_Requirements_List.pdf
PDF 3 MB Posted
- Attached to
- Technology Applications Development and Sustainment (TADS) Federal contract opportunity
- Solicitation number
- FA4600-19-R-A001
About this file
This document outlines a solicitation for technology applications development and sustainment services to support Air Force weather capabilities. The Air Force intends to award a single-award IDIQ contract with a value of up to $500 million over five years, plus a six-month extension, to provide deployment and sustainment services for weather systems. Services will be ordered using contract types including cost-plus-fixed-fee, firm-fixed-price, cost-plus-incentive fee, cost reimbursement, and fixed-price incentive firm. Questions regarding the draft RFP are due by July 16, 2019, with the final solicitation to be issued on July 10, 2019 and proposals due in August 2019. The contract will support the 55th Contracting Squadron and Air Combat Command.
Attachment 09d - Task Order 01 - Transition and Sustainment Contract Data Requirements List
View the file
Other files for this federal contract opportunity
Show all 30
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
For the best experience, open this PDF portfolio in
Acrobat X or Adobe Reader X, or later.
Get Adobe Reader Now!
http://www.adobe.com/go/reader
DD FORM 1423-1, FEB 2001
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
PREVIOUS EDITION MAY BE USED.
Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE
7. DD 250 REQ
8. APP CODE
9. DIST STATEMENT
REQUIRED
10. FREQUENCY
11. AS OF DATE
12. DATE OF FIRST SUBMISSION
13. DATE OF SUBSEQUENT
SUBMISSION
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
Draft Final
Reg Repro
15. TOTAL
16. REMARKS
17. PRICE GROUP
18. ESTIMATED
TOTAL PRICE
G. PREPARED BY H. DATE I. APPROVED BY J. DATE
Page of Pages
16. REMARKS (Continued)
DD FORM 1423-1, FEB 2001 Page of Pages
INSTRUCTIONS FOR COMPLETING DD FORM 1423
(See DoD 5010.12-M for detailed instructions.)
FOR GOVERNMENT PERSONNEL
Item A. Self-explanatory.
Item B. Self-explanatory.
Item C. Mark (X) appropriate category: TDP - Technical Data Package;
TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.
Item D. Enter name of system/item being acquired that data will support.
Item E. Self-explanatory (to be filled in after contract award).
Item F. Self-explanatory (to be filled in after contract award).
Item G. Signature of preparer of CDRL.
Item H. Date CDRL was prepared.
Item I. Signature of CDRL approval authority.
Item J. Date CDRL was approved.
Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.
Item 2. Enter title as it appears on data acquisition document cited in Item 4.
Item 3. Enter subtitle of data item for further definition of data item (optional entry).
Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.
Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).
Item 6. Enter technical office responsible for ensuring adequacy of the data item.
Item 7. Specify requirement for inspection/acceptance of the data item by the Government.
Item 8. Specify requirement for approval of a draft before preparation of the final data item.
Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).
Item 10. Specify number of times data items are to be delivered.
Item 11. Specify as-of date of data item, when applicable.
Item 12. Specify when first submittal is required.
Item 13. Specify when subsequent submittals are required, when applicable.
Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.
Item 15. Enter total number of draft/final copies to be delivered.
Item 16. Use for additional/clarifying information for Items 1 through 15.
Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14.; Desired medium for delivery of the data item.
FOR THE CONTRACTOR
Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.
a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.
Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.
b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.
Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.
c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.
Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and
d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.
Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.
Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.
These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract.
DD FORM 1423-1 (BACK), FEB 2001
CCR Reviews are every Tuesday and Wednesday 0730-0830 in RM 3230 -- Those who have CCRs to be approved are encouraged to attend.
Dial In DSN 272-4585 or (402)232-4585
NOTE: PPS spreadsheets for the SIPR environment may NOT be attached to the CCR Documents tab. Send PPS spreadsheets via SIPR email to warren.l.hagelstien.civ@mail.smil.mil and tammy.k.llorens.civ@mail.smil.mil and reference the CCR number in the Subject line of that email.
Guidance for Security Artifacts:
Fortify Scans
· Fortify scan Critical and High issues have been audited with explanation/mitigation comments included.
· Scans must be cleared of scan warnings which indicate the scan did not complete. If unable to clear scan warnings, a CYBERCELL JIRA task must be created and included in CCR justification.
Peer Review
1. All code that cannot be scanned by Fortify or another automated static code analyzer for security issues should be peer reviewed.
2. The preferred presentation to CS for PeerReview documentation is FECru. A security summary should be included and any findings should be specifically addressed.
3. Teams should develop a checklist so that vulnerability areas such as .Data Validation . Authentication . Session Management . Authorization .Cryptography . Error Handling . Logging . Security Configuration & Network Architecture are consistently covered.
It should be apparent when reviewing FECru peer review documentation that specific security areas identified above have been addressed, perhaps in General Comments.
In addition, as is required for Fortify scans, no new security findings should be present.
Creating a New CCR:
· Access the CCR page via browser and select CCR Dashboard from the Entry Point selection window: https://wx-arweb.us.af.mil/home/continue.jsp?View=CCR+Dashboard
· Click the Create NEW CCR button on the top left of the dashboard.
On-screen help may be activated by clicking on the Show Help link in the top right quadrant of the CCR Submission window. Hovering over an input area with the mouse will activate a pop-up box with help text guidance.
· Drafts - can be saved at any point prior to formal submission of the form. It will display on the CCR Dashboard and can be edited at a later date. Click Save Draft in the lower right quadrant of the form. The CCR Submission window will remain open. You can continue editing the CCR or close the window and resume editing the CCR at a later time. The saved Draft can be retrieved by changing the Status to Draft in the Search tab. Select the CCR you wish to edit then click Update. This will bring up the CCR Submission window and allow editing of the CCR. A Draft CCR can be canceled by selecting the Cancel Request button in the CCR Submission window or on the CCR Dashboard.
Filling out the CCR Submission Form:
· Urgency - Routine or Priority
· Enclave - AUPE for Unclass, ASPE for SIPR, DREN, and SCI for SCI1 or SCI2.
· Sub-System - Based on the Enclave, a list of available systems will populate this list. Select the system you are modifying
· Classification - This field will auto populated if a classified Enclave is selected. Otherwise, select classification.
· Title - Brief description of CCR. Must begin with one of the following 3-letter indicators for easy identification: i.e. PRD – DEPLOY EDCSS 1.9.0
Indicator
Description/Use
**If it is not clear which indicator applies to your CCR, verify with CS prior to CCR submission.
ADM
Updating the CCR database to reflect current state – no actual software or hardware changes are being made
CFG
1. Software Configuration changes 2. IP/DNS requests 3. Virus scanning exclusions
DEV
Development
MGT
Management Network
OOC
Out of Cycle
PPS
Ports Protocols and Services (internal and external - required) and/or DMZ Whitelist Requests **attach a completed PPS worksheet found here to the documents tab - completion instructions found here *If the request requires an AFTO 265, that form should be attached to the CCR as well for ISSM signature.
PRD
Production
RTS
Return to Service
SLS
Temporary CCRs for software requests (no more than 14 days) to accomplish scan-load-scan and required artifact completion. (only required for RHEL, Windows requires 3215 / see Software Requests )
TST
Test
· Purpose - CONCISELY explain why the action is being taken and not just what the action is.
· Justification - What the mission requirement is for this change and the impact of CCR rejection. In addition to including a plain language text explanation and information, be sure to include associated JIRA task, Remedy ticket, TCNO, IAVM numbers. For decommission requests, include the IP address as well as the Remedy ticket to re-capture the IP address, firewall change, F5, and DNS entries to ensure we are cleaning up.
If the CCR is for a GOTS or COTS application provide the following information in the Justification.
NOTE: For DEV9, only a DEV CCR is required due to the limitations of the current CCR tool and the concurrent DEV/TST environment. A PRD CCR for PROD10 should follow. All security artifacts are required for both DEV and PRD CCRs and should be ready for CyberSecurity review when the CCR is submitted.
For DEV
1. EXECUTIVE SUMMARY - What is to be changed in the code and why? Include driving factors for why the specific STIG and FORTIFY findings identified below are being addressed. The reader should be able to rapidly become acquainted with the purpose of the change.
2. FINDINGS SNAPSHOT -
STIG CAT I – [# of findings to be worked in this release/ # of total CAT I findings] – [assoc. JIRA #s]
STIG CAT II – [# of findings to be worked in this release/ # of total CAT II findings] – [assoc. JIRA #s]
STIG CAT III – [# of findings to be worked in this release/ # of total CAT III findings] – [assoc. JIRA #s]
FORTIFY CRITICAL – [# of findings to be worked in this release/ # of total Critical findings] – [assoc. JIRA #s]
FORTIFY HIGH – [# of findings to be worked in this release/ # of total High findings] – [assoc. JIRA #s]
FORTIFY MEDIUM – [# of findings to be worked in this release/ # of total Medium findings] – [assoc. JIRA #s]
FORTIFY LOW – [# of findings to be worked in this release/ # of total Low findings] – [assoc. JIRA #s]
NOTE: If the STIG or FORTIFY category has no findings, it may be omitted. If no security findings are being/will be addressed, please provide an explanation.
3. STIG - IA JIRA issue # where (1)the STIG is attached or (2)the repository path to the STIG Checklist is specified. Repository path must be stig_final.
4. FORTIFY - Fortify SSC path - <Application>/<Version>/<Scan Filename> i.e. AFW-WEBS_AFW_WEBS/JavaScript_Baseline/AFW_WEBS_3.23.0.61.fpr
5. WEBINSPECT - location of the WebInspect scan if required.
FOR TST
1. EXECUTIVE SUMMARY - What was changed in the code and why? Include driving factors for why the specific STIG and FORTIFY findings identified below are being addressed. The reader should be able to rapidly become acquainted with the reason for the change.
STIG CAT I – [# of findings that were worked in this release/ # of total CAT I findings] – [assoc. JIRA #s]
STIG CAT II – [# of findings that were worked in this release/ # of total CAT II findings] – [assoc. JIRA #s]
STIG CAT III – [# of findings that were worked in this release/ # of total CAT III findings] – [assoc. JIRA #s]
Fortify Critical – [# of findings that were worked in this release/ # of total Critical findings] – [assoc. JIRA #s]
Fortify High – [# of findings that were worked in this release/ # of total High findings] – [assoc. JIRA #s]
Fortify Medium – [# of findings that were worked in this release/ # of total Medium findings] – [assoc. JIRA #s]
Fortify Low – [# of findings that were worked in this release/ # of total Low findings] – [assoc. JIRA #s]
NOTE: If the STIG or Fortify category has no findings, it may be omitted. If no security findings are being/will be addressed, please provide an explanation.
3. STIG - IA JIRA issue # where (1)the STIG is attached or (2)the repository path to the STIG Checklist is specified. Respository path must be stig_final.
4. FORTIFY - Fortify SSC path - <Application>/<Version>/<Scan Filename> i.e. AFW-WEBS_AFW_WEBS/JavaScript_Baseline/AFW_WEBS_3.23.0.61.fpr
6. DEV CCR #
FOR PRD
1. EXECUTIVE SUMMARY – This can be the same Executive Summary that was included in the TST CCR (as this should remain consistent)
STIG CAT I – [# of findings that were worked in this release/ # of total CAT I findings] – [assoc. JIRA #s] STIG CAT II – [# of findings that were worked in this release/ # of total CAT II findings] – [assoc. JIRA #s] STIG CAT III – [# of findings that were worked in this release/ # of total CAT III findings] – [assoc. JIRA #s] Fortify Critical – [# of findings that were worked in this release/ # of total Critical findings] – [assoc. JIRA #s] Fortify High – [# of findings that were worked in this release/ # of total High findings] – [assoc. JIRA #s] Fortify Medium – [# of findings that were worked in this release/ # of total Medium findings] – [assoc. JIRA #s] Fortify Low – [# of findings that were worked in this release/ # of total Low findings] – [assoc. JIRA #s] NOTE: If the STIG or Fortify category has no findings, it may be omitted. If no security findings are being/will be addressed, please provide an explanation. If the findings snapshot has changed since the TST CCR, please provide an explanation.
3. STIG - IA JIRA issue # where (1)the STIG is attached or (2)the repository path to the STIG Checklist is specified. Respository path must be stig_final.
4. FORTIFY - Fortify SSC path - <Application>/<Version>/<Scan Filename> i.e. AFW-WEBS_AFW_WEBS/JavaScript_Baseline/AFW_WEBS_3.23.0.61.fpr
6. TST CCR #
· Duration - Temporary or Permanent change.
▪ Use temporary with a duration of no more than 90 days for development systems that have not been STIG'd or security scanned. The understanding is that the required artifacts will be supplied within the indicated time frame. A selection of temporary will require Planned From and To dates. Temporary CCRs must be Reversed after the "To date" or sooner based on the completion of the work being requested.
· Planned Implementation – Date of planned implementation
· Radio Buttons - Note: radio buttons do not always function as expected.
▪ Hardware, Software and Application Scans - These are all yes/no radio buttons. Application Scans refer to the requirement for security scans (STIGs, etc.)
▪ Dataflow - Provide any changes to system dataflows. If the change is elaborate and/or you have an external document describing the dataflow indicate it here and attach it under the Documents tab on the right.
▪ PPS (Ports Protocols and Services) – Indicate if there is a change needed to PPS (internal and external - required). If yes, provide a list of detailed changes being requested and upload the PPS Worksheet in the Documents Tab.
· Tabs -
▪ POC(s) - The CCR Submission form will put your name as Submitter and Technical POC by default. Using the Add New button, you may add other Technical POCs. This will provide the reviewers a source for technical questions concerning the changes being requested. The other roles available are Watcher, who will receive email notifications of changes and approvals to the CCR, and Sponsor, who is the originating organization/office POC requiring the system changes, typically the person submitting the original requirement. This area is used to track approval status of CCR.
▪ Documents - Any supporting additional documentation can be uploaded here (ie. Dataflow Diagrams, PPS Worksheet, ACAS Scan-Load-Scan). Documents can be removed or added after the CCR is submitted. This allows for corrections without rejecting the CCR.
▪ PPS (Ports Protocols and Services) – Tab currently not in use.
▪ Hardware -
§ Create New is used when any new hardware is added to the network.
§ Add Exist pops up a window listing all entries for the SubSystem selected. Highlight appropriate selections (CTRL allows multiple selections) such as Production, Test and Development, then the Select button.
§ Add HWID + function allows you to enter individually by HWID.
▪ Software - The Software Tab itself is not used to select software. Software is selected based on Hardware component. You must double-click an item from the available Hardware list created previous step. The Software tab in the description shows what software is currently associated with that hardware. **The submitter is responsible for the content including legacy information.
§ To add a new application or update the version number you must click the Create New button.
· Select the Vendor.
· Select the Source.
· Select the application name or enter the name.
· Enter the version in the Version text box. Use the actual version number, not "Current".
· Select the Type.
· Enter the URL if applicable.
· Enter the Purpose of the Application.
· Indicate IA Enabled and IA Certification only if the software functionality provides specific security services.
· In the Action window the appropriate response (Add or Remove).
· Click Submit when all fields when done.
▪ Log - Messages from Approval Officers will be listed here and responses may be entered using the New Entry button. When submitting a new log entry, Save & Send will send an email to all names that have been checked.
▪ Dependencies – After the CCR is created, this area will list any CCRs associated with the HWID that need to close prior to this one closing.
▪ Audit - The Audit tab tracks changes to the CCR.
Submitting the CCR
The CCR is submitted for approval by selecting Submit from the CCR Submission window. A CCR must be approved by four offices to be finalized: IAM -AFLCMC/HBAW-OL, Network Management – 2 SYOS/SYOM, Engineering – AFLCMC/HBAW-OL, and Architecture Group - AFLCMC/HBAW-OL. As the CCR goes through the approval process, its status is documented in the Audit Tab. Additionally, when an office approves the CCR an entry is added to the POC(s) list. Any message or question from an approval officer is annotated in the Log. The log should be checked daily for status update messages. An email is generated when the CCR is finalized.
Completing the CCR
After a CCR has been approved and implementation actions have been completed, send an email to: AFLCMC.HBAW-OL.CyberSecurityOffice@us.af.mil Include the CCR number and the date of completion.
Rejected CCRs
If a CCR is Rejected, you have 15 calendar days in which you can save the CCR as a draft. A draft CCR could then be modified/revised as necessary and resubmitted on a future date.
After 15 days, the CCR will be cancelled.
false,false,1 image2.wmf image3.wmf image4.png image1.wmf data_item: A027 title: Information Assurance Design Review Information Package and Configuration Change Control Data Information Packet sub: Configuration Change Request auth: DI-MGMT-81845_Tailored ref: PWS para 2.3.1 req_ofc: AFLCMC/HBAW-OL dd250: LT appcode: N/A dist: D freq: ASREQ asof: N/A firstsub: ASREQ subsub: N/A addressee1: 2 WxG/COR draft1: 0 reg1: 1 repro1: 0 addressee2: AFLCMC/HBAW-OL draft2: 0 reg2: 1 repro2: 0 addressee3: -----------------------------draft3:
reg3:
repro3:
addressee4:
draft4:
reg4:
repro4:
addressee5:
draft5:
reg5:
repro5:
addressee6:
draft6:
reg6:
repro6:
addressee7:
draft7:
reg7:
repro7:
addressee8:
draft8:
reg8:
repro8:
addressee9:
draft9:
reg9:
repro9:
addressee10:
draft10:
reg10:
repro10:
addressee11:
draft11:
reg11:
repro11:
addressee12:
draft12:
reg12:
repro12:
addressee13:
draft13:
reg13:
repro13:
addressee14:
draft14:
reg14:
repro14:
addressee15:
draft15:
reg15:
repro15:
addressee16:
draft16:
reg16:
repro16:
addressee17:
draft17:
reg17:
repro17:
addressee18:
draft18:
reg18:
repro18:
addressee19:
draft19:
reg19:
repro19:
addressee20:
draft20:
reg20:
repro20:
addressee21:
draft21:
reg21:
repro21:
addressee22:
draft22:
reg22:
repro22:
addressee23:
draft23:
reg23:
repro23:
addressee24:
draft24:
reg24:
repro24:
addressee25:
draft25:
reg25:
repro25:
addressee26:
draft26:
reg26:
repro26:
addressee27:
draft27:
reg27:
repro27:
addressee28:
draft28:
reg28:
repro28:
addressee29:
draft29:
reg29:
repro29:
addressee30:
draft30:
reg30:
repro30:
addressee31:
draft31:
reg31:
repro31:
addressee32:
draft32:
reg32:
repro32:
addressee33:
draft33:
reg33:
repro33:
addressee34:
draft34:
reg34:
repro34:
addressee35:
draft35:
reg35:
repro35:
addressee36:
draft36:
reg36:
repro36:
addressee37:
draft37:
reg37:
repro37:
addressee38:
draft38:
reg38x:
repro38:
total_draft: 0 total_reg: 2 total_repro: 0 remarks: Block 4: DI-MGMT-81845 tailoring Delete para 2.2, 2.3, 2.4.2, 2.4.3, 2.4.4, 2.5, and 2.6. Contractor will use Government configuration change request format. Instructions are attached.
Block 12: 10 work days before required change
Block 14: Electronic format required.
group:
total_price:
prep_name:
line_item: X008 exhibit: A xtdp: Off xtm: Off othercat: Engineering Data system: TADS - Sustainment ctr_no: TBD (Task Order 01) contr: TBD remarksb:
Page2:
Reset:
prep_date:
app_by:
app_date:
Page:
of_pages:
app: Adobe Professional 8.0
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any data_item: A029 title: Technical Report - Study/Services sub: Hardware and Software Trouble Shooting Aids and Guides auth: DI-MISC-80508B_Tailored ref: PWS para 2.0.3, 2.4.1.1, and 2.6.1.2 req_ofc: AFLCMC/HBAW-OL dd250: LT appcode: N/A dist: D freq: ASREQ asof: N/A firstsub: ASREQ subsub: ASREQ addressee1: 2 WxG/COR draft1: 0 reg1: 1 repro1: 0 addressee2: AFLCMC/HBAW-OL draft2: 0 reg2: 1 repro2: 0 addressee3: -----------------------------draft3:
reg3:
repro3:
addressee4:
draft4:
reg4:
repro4:
addressee5:
draft5:
reg5:
repro5:
addressee6:
draft6:
reg6:
repro6:
addressee7:
draft7:
reg7:
repro7:
addressee8:
draft8:
reg8:
repro8:
addressee9:
draft9:
reg9:
repro9:
addressee10:
draft10:
reg10:
repro10:
addressee11:
draft11:
reg11:
repro11:
addressee12:
draft12:
reg12:
repro12:
addressee13:
draft13:
reg13:
repro13:
addressee14:
draft14:
reg14:
repro14:
addressee15:
draft15:
reg15:
repro15:
addressee16:
draft16:
reg16:
repro16:
addressee17:
draft17:
reg17:
repro17:
addressee18:
draft18:
reg18:
repro18:
addressee19:
draft19:
reg19:
repro19:
addressee20:
draft20:
reg20:
repro20:
addressee21:
draft21:
reg21:
repro21:
addressee22:
draft22:
reg22:
repro22:
addressee23:
draft23:
reg23:
repro23:
addressee24:
draft24:
reg24:
repro24:
addressee25:
draft25:
reg25:
repro25:
addressee26:
draft26:
reg26:
repro26:
addressee27:
draft27:
reg27:
repro27:
addressee28:
draft28:
reg28:
repro28:
addressee29:
draft29:
reg29:
repro29:
addressee30:
draft30:
reg30:
repro30:
addressee31:
draft31:
reg31:
repro31:
addressee32:
draft32:
reg32:
repro32:
addressee33:
draft33:
reg33:
repro33:
addressee34:
draft34:
reg34:
repro34:
addressee35:
draft35:
reg35:
repro35:
addressee36:
draft36:
reg36:
repro36:
addressee37:
draft37:
reg37:
repro37:
addressee38:
draft38:
reg38x:
repro38:
total_draft: 0 total_reg: 2 total_repro: 0 remarks: Block 4: DI-MISC-80508B tailoring -- Replace 2(b) with "Text shall be prepared in electronic format standard letter size (8 1/2 x 11")." Remove the word "paper" from 2(c).
-- Add to 3(d) "Overview/Introduction – short description of the hardware or software system being highlighted in the trouble shooting guide; Statement of the problem/issue – present the problem or issue that was encountered or could be encountered; Provide diagnostic steps – list known problems/issues, describe possible causes, and provide potential solutions; Example format: Problem, issue, or error description, Cause, and Solution; and Additional information – provide any additional information that could be useful in trouble shooting the problem.
Block 12 and 13: Within 5 work days of a change to or new maintenance procedures
Block 14: Electronic format required.
group:
total_price:
prep_name:
line_item: X008 exhibit: A xtdp: Off xtm: Off othercat: Engineering Data system: TADS - Sustainment ctr_no: TBD (Task Order 01) contr: TBD remarksb:
Page2:
Reset:
prep_date:
app_by:
app_date:
Page:
of_pages:
app: Adobe Professional 8.0
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any
TO # - NAME
SECURITY CLASSIFICATION Unclassified
COST DATA SUMMARY REPORT Form Approved
The public reporting burden for this collection of information is estimated to average 8 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.
PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
1. MAJOR PROGRAM a. NAME:
b. PHASE/MILESTONE 2. PRIME MISSION PRODUCT 3. REPORTING ORGANIZATION TYPE 4. NAME/ADDRESS (Include ZIP Code) 5. APPROVED PLAN NUMBER
Pre-A B C-FRP PRIME / ASSOCIATE CONTRACTOR DIRECT-REPORTING SUBCONTRACTOR GOVERNMENT a. PERFORMING ORGANIZATION b. DIVISION
A C-LRIP O&S
6. CUSTOMER (Direct-reporting subcontractor use only) 7. CONTRACT TYPE 8. CONTRACT PRICE 9. CONTRACT CEILING 10. TYPE ACTION
a. CONTRACT NO.: c. SOLICITATION NO.: e. TASK ORDER/DELIVERY ORDER/LOT NO.:
b. LATEST MODIFICATION: d. NAME:
11. PERIOD OF PERFORMANCE 12. APPROPRIATION 13. REPORT CYCLE 14. SUBMISSION NUMBER 15. RESUBMISSION NUMBER 16. REPORT AS OF (YYYYMMDD)
a. START DATE (YYYYMMDD): RDT&E INITIAL
b. END DATE (YYYYMMDD): PROCUREMENT INTERIM
O&M FINAL
17. NAME (Last, First, Middle Initial) 18. DEPARTMENT 19. TELEPHONE NUMBER (Include Area Code) 20. EMAIL ADDRESS 21. DATE PREPARED (YYYYMMDD)
WBS
ELEMENT
CODE WBS REPORTING ELEMENTS NUMBER OF
UNITS
TO DATE COSTS INCURRED TO DATE (thousands of U.S. Dollars) NUMBER OF
UNITS AT
COMPLETION COSTS INCURRED AT COMPLETION (thousands of U.S. Dollars)
NONRECURRING RECURRING TOTAL NONRECURRING RECURRING TOTAL
A B C D E F G H I J
1.0 Information Systems (IS)/Defense Business Systems (DBS) Investment
1.1 IS/DBS Development/Customization/Configuration (PMP)
1.1.1 Custom Application 1…n (Specify)
1.1.2 Enterprise Service Element 1…n (Specify)
1.1.3 Enterprise/Management Information System 1…n (Specify)
1.1.4 External System Interface Development 1…n (Specify)
1.1.5 System Level Hardware
1.1.6 System Level Software
1.2 System Level Integration
1.3 System Engineering
1.3.1 Software Systems Engineering
1.3.2 Integrated Logistics Support (ILS) Systems Engineering
1.3.3 Cybersecurity Systems Engineering
1.3.4 Core Systems Engineering
1.3.5 Other Systems Engineering 1…n (Specify)
1.4 Program Management
1.5 Change Management
1.6 Data Management
1.7 System Test and Evaluation
1.8 Training
1.9 Data
1.10 Peculiar Support Equipment
1.11 Common Support Equipment
1.12 Operational/Site Activation
1.12.1 Initial Hardware Procurement
1.12.2 Initial Software License Procurement
1.12.3 Initial Software Release (Pre-IOC) Modification/Enhancement
1.12.4 Site Activation
1.12.4.1 Data Migration
1.12.4.2 User Training
1.12.4.3 User Documentation
1.12.4.4 Management/Engineering Support
1.12.4.5 Site Installation, Test, and Checkout
1.12.4.6 Other 1…n (Specify)
1.12.5 Interim Operations and Support (Pre-IOC)
1.13 Industrial Facilities
1.14 Initial Spares and Repair Parts
2.0 Information Systems (IS)/Defense Business Systems (DBS) Sustainment
2.1 Program Management
2.2 Systems/Sustainment Engineering
2.3 Change Management
2.4 Help Desk
2.5 Data Cleansing/Data Maintenance
2.6 System/Database Administration
2.7 IT Infrastructure/Network Maintenance Support
2.8 Operational Hardware Refresh/Upgrade
2.9 Operational Software License Refresh/Update
2.10 Cybersecurity Maintenance Management
2.11 Follow-on User Training
2.12 System Independent Verification and Validation
2.13 Continuing System Improvement
2.13.1 Operational Hardware Modification
2.13.2 Software Release Modification/Enhancement 1…n (Specify)
2.13.2.1 Modifications/Enhancements
2.13.2.2 Routine Fixes and Deficiency Correction
2.13.2.3 Installation/Test
2.13.2.4 IAVAs
2.14 AW/Safety/Networthiness Certification
2.15 Facilities
22. REMARKS
DD FORM 1921, MAY 2011 PREVIOUS EDITION IS OBSOLETE. SECURITY CLASSIFICATION Unclassified data_item: A030 title: Cost Data Summary Report sub: Cost Data Summary Report auth: DI-FNCL-81565C ref: PWS Para 2.1 req_ofc: AFLCMC/HBAF dd250: LT appcode: N/A dist: D freq: ASREQ asof: N/A firstsub: ASREQ subsub: ASREQ addressee1: AFLCMC/HBAF draft1: 0 reg1: 1 repro1: 0 addressee2: DCARC (see Block 16) draft2: 0 reg2: 1 repro2: 0 addressee3: AFLCMC/HBAW-OL draft3: 0 reg3: 1 repro3: 0 addressee4: 2 WxG/COR draft4: 0 reg4: 1 repro4: 0 addressee5: -----------------------------draft5:
reg5:
repro5:
addressee6:
draft6:
reg6:
repro6:
addressee7:
draft7:
reg7:
repro7:
addressee8:
draft8:
reg8:
repro8:
addressee9:
draft9:
reg9:
repro9:
addressee10:
draft10:
reg10:
repro10:
addressee11:
draft11:
reg11:
repro11:
addressee12:
draft12:
reg12:
repro12:
addressee13:
draft13:
reg13:
repro13:
addressee14:
draft14:
reg14:
repro14:
addressee15:
draft15:
reg15:
repro15:
addressee16:
draft16:
reg16:
repro16:
addressee17:
draft17:
reg17:
repro17:
addressee18:
draft18:
reg18:
repro18:
addressee19:
draft19:
reg19:
repro19:
addressee20:
draft20:
reg20:
repro20:
addressee21:
draft21:
reg21:
repro21:
addressee22:
draft22:
reg22:
repro22:
addressee23:
draft23:
reg23:
repro23:
addressee24:
draft24:
reg24:
repro24:
addressee25:
draft25:
reg25:
repro25:
addressee26:
draft26:
reg26:
repro26:
addressee27:
draft27:
reg27:
repro27:
addressee28:
draft28:
reg28:
repro28:
addressee29:
draft29:
reg29:
repro29:
addressee30:
draft30:
reg30:
repro30:
addressee31:
draft31:
reg31:
repro31:
addressee32:
draft32:
reg32:
repro32:
addressee33:
draft33:
reg33:
repro33:
addressee34:
draft34:
reg34:
repro34:
addressee35:
draft35:
reg35:
repro35:
addressee36:
draft36:
reg36:
repro36:
addressee37:
draft37:
reg37:
repro37:
addressee38:
draft38:
reg38x:
repro38:
total_draft: 0 total_reg: 4 total_repro: 0 remarks: Block 4 - Format and content preparation instructions: The contractor shall organize and provide to the Government in the required format (MS Excel format, titled "Cost Data Summary Report - 1921," is attached)
Block 10 - Frequency shall be IAW the appropriate TADS DD Form 2794 CSDR Plan. (attached)
Block 11 - As of Contract Award.
Block 12 - The contractor shall submit an initial DD Form 1921 to AFLCMC/HBAF per the appropriate TADS DD Form 2794 CSDR Plan thirty (30) calendar days after contract award. The Government will provide comments and approval/disapproval to Contractor within thirty (30) days. The contractor shall incorporate comments and resubmit thirty (30) days after receipt.
Block 13 - Subsequent submissions to AFLCMC/HBAF and DCARC shall be IAW the appropriate DD Form 2794 CSDR Plan.
Block 14 - The Cost Data Summary Report shall be submitted to DCARC electronically using the CSDR Submit-Review System. Data submitters must register through the DCARC website and possess a DoD-approved ECA digital certificate or a DoD-issued CAC to obtain a DCARC Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the DCARC portal and requesting a CSDR submitter user role. After the registration information has been verified, the DCARC shall authorize the user account and requested role. All DCARC Portal accounts need to be renewed at least annually.
group:
total_price:
prep_name:
line_item: X008 exhibit: A xtdp: Off xtm: Off othercat: Financial system: TADS - Sustainment ctr_no: TBD (Task Order 01) contr: TBD remarksb:
Page2:
Reset:
prep_date:
app_by:
app_date:
Page:
of_pages:
app: Adobe Professional 8.0
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any
WBS 2.0
SECURITY CLASSIFICATION Unclassified
SUSTAINMENT FUNCTIONAL COST-HOUR REPORT
The public reporting burden for this collection of information is estimated to average 16 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Executive Services Directorate, Directives Division, 4800 Mark Center Drive, East Tower, Suite 02G09, Alexandria, VA 22350-3100 (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
1. MAJOR PROGRAM a. NAME:
b. PHASE/MILESTONE 2. PRIME MISSION PRODUCT 3. REPORTING ORGANIZATION TYPE 4. NAME/ADDRESS (Include Zip Code) 5. APPROVED PLAN NUMBER
Pre-A B C-FRP PRIME / ASSOCIATE CONTRACTOR DIRECT-REPORTING SUBCONTRACTOR GOVERNMENT a. PERFORMING ORGANIZATION b. DIVISION
A C-LRIP O&S
6. CUSTOMER (Direct-Reporting Subcontractor Use Only) 7. TYPE ACTION
a. CONTRACT NO.: c. SOLICITATION NO.: e. TASK ORDER/DELIVERY ORDER/LOT NO.:
b. LATEST MODIFICATION: d. NAME:
8. PERIOD OF PERFORMANCE 9. REPORT CYCLE 10. SUBMISSION NUMBER 11. RESUBMISSION NUMBER 12. REPORT AS OF (YYYYMMDD)
a. START DATE (YYYYMMDD): INITIAL
b. END DATE (YYYYMMDD): INTERIM
FINAL
13. NAME (Last, First, Middle Initial) 14. DEPARTMENT 15. TELEPHONE NO. (Include Area Code) 16. EMAIL ADDRESS 17. DATE PREPARED (YYYYMMDD)
18. WBS ELEMENT CODE 19. WBS REPORTING ELEMENT 20. NUMBER OF UNITS 21. APPROPRIATION
a. TO DATE b. AT COMPLETION RDT&E
PROCUREMENT
O&M
| SUSTAINMENT FUNCTIONAL DATA ELEMENTS | COSTS AND HOURS INCURRED TO DATE | ||
| (thousands of U.S. Dollars or thousands of hours) | COSTS AND HOURS INCURRED AT COMPLETION |
(thousands of U.S. Dollars or thousands of hours)
A. NONRECURRING B. RECURRING C. TOTAL D. NONRECURRING E. RECURRING F.TOTAL
ENGINEERING
(1) DIRECT ENGINEERING LABOR HOURS
(2) DIRECT ENGINEERING LABOR DOLLARS
(3) ENGINEERING OVERHEAD DOLLARS
(4) TOTAL ENGINEERING DOLLARS
PROGRAM MANAGEMENT
(5) DIRECT PROGRAM MANAGEMENT LABOR HOURS
(6) DIRECT PROGRAM MANAGEMENT LABOR DOLLARS
(7) PROGRAM MANAGEMENT OVERHEAD DOLLARS
(8) TOTAL PROGRAM MANAGMENT DOLLARS
MAINTENANCE OPERATIONS
(9) TOUCH MAINTENANCE LABOR HOURS
(10) TOUCH MAINTENANCE LABOR DOLLARS
(11) TOUCH MAINTENANCE OVERHEAD DOLLARS
(12) SUPPORT MAINTENANCE LABOR HOURS
(13) SUPPORT MAINTENANCE LABOR DOLLARS
(14) SUPPORT MAINTENANCE OVERHEAD DOLLARS
(15) TOTAL MAINTENANCE OPERATIONS HOURS
(16) TOTAL MAINTENANCE OPERATIONS DOLLARS
MATERIALS
(17) RAW MATERIAL DOLLARS
(18) PURCHASED PARTS DOLLARS
(19) PURCHASED EQUIPMENT DOLLARS
(20) MATERIAL HANDLING/OVERHEAD DOLLARS
(21) TOTAL DIRECT-REPORTING SUBCONTRACTOR DOLLARS
(22) TOTAL MATERIAL DOLLARS
OTHER COSTS
(23) OTHER COSTS NOT SHOWN ELSEWHERE (Specify in Remarks)
SUMMARY
(24) TOTAL COST (Direct and Overhead)
22. REMARKS
DD FORM 1921-5, DEC 2015 SECURITY CLASSIFICATION Unclassified
WBS 2.1
SECURITY CLASSIFICATION Unclassified
FUNCTIONAL COST-HOUR REPORT Form Approved
The public reporting burden for this collection of information is estimated to average 16 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
1. MAJOR PROGRAM a. NAME:
b. PHASE/MILESTONE 2. PRIME MISSION PRODUCT 3. REPORTING ORGANIZATION TYPE 4. NAME/ADDRESS (Include Zip Code) 5. APPROVED PLAN NUMBER
Pre-A B C-FRP PRIME / ASSOCIATE CONTRACTOR DIRECT-REPORTING SUBCONTRACTOR GOVERNMENT a. PERFORMING ORGANIZATION b. DIVISION
A C-LRIP O&S
6. CUSTOMER (Direct-Reporting Subcontractor Use Only) 7. TYPE ACTION
a. CONTRACT NO.: c. SOLICITATION NO.: e. TASK ORDER/DELIVERY ORDER/LOT NO.:
b. LATEST MODIFICATION: d. NAME:
8. PERIOD OF PERFORMANCE 9. REPORT CYCLE 10. SUBMISSION NUMBER 11. RESUBMISSION NUMBER 12. REPORT AS OF (YYYYMMDD)
a. START DATE (YYYYMMDD): INITIAL
b. END DATE (YYYYMMDD): INTERIM
FINAL
13. NAME (Last, First, Middle Initial) 14. DEPARTMENT 15. TELEPHONE NO. (Include Area Code) 16. EMAIL ADDRESS 17. DATE PREPARED (YYYYMMDD)
18. WBS ELEMENT CODE 19. WBS REPORTING ELEMENT 20. NUMBER OF UNITS 21. APPROPRIATION
a. TO DATE b. AT COMPLETION RDT&E
PROCUREMENT
O&M
| FUNCTIONAL DATA ELEMENTS | COSTS AND HOURS INCURRED TO DATE | ||
| (thousands of U.S. Dollars or thousands of hours) | FORECAST OF COSTS AND HOURS INCURRED AT COMPLETION |
A. NONRECURRING B. RECURRING C. TOTAL D. NONRECURRING E. RECURRING F.TOTAL
LABOR
TOTAL LABOR HOURS
TOTAL LABOR DOLLARS
MATERIALS
TOTAL MATERIAL DOLLARS
OTHER COSTS
OTHER COSTS NOT SHOWN ELSEWHERE (Specify in Remarks)
SUMMARY
TOTAL COST (Direct and Overhead)
22. REMARKS
DD FORM 1921-1, MAY 2011 SECURITY CLASSIFICATION Unclassified
WBS 2.2
SECURITY CLASSIFICATION Unclassified
FUNCTIONAL COST-HOUR REPORT Form Approved
The public reporting burden for this collection of information is estimated to average 16 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
1. MAJOR PROGRAM a. NAME:
b. PHASE/MILESTONE 2. PRIME MISSION PRODUCT 3. REPORTING ORGANIZATION TYPE 4. NAME/ADDRESS (Include Zip Code) 5. APPROVED PLAN NUMBER
Pre-A B C-FRP PRIME / ASSOCIATE CONTRACTOR DIRECT-REPORTING SUBCONTRACTOR GOVERNMENT a. PERFORMING ORGANIZATION b. DIVISION
A C-LRIP O&S
6. CUSTOMER (Direct-Reporting Subcontractor Use Only) 7. TYPE ACTION
a. CONTRACT NO.: c. SOLICITATION NO.: e. TASK ORDER/DELIVERY ORDER/LOT NO.:
b. LATEST MODIFICATION: d. NAME:
8. PERIOD OF PERFORMANCE 9. REPORT CYCLE 10. SUBMISSION NUMBER 11. RESUBMISSION NUMBER 12. REPORT AS OF (YYYYMMDD)
a. START DATE (YYYYMMDD): INITIAL
b. END DATE (YYYYMMDD): INTERIM
FINAL
13. NAME (Last, First, Middle Initial) 14. DEPARTMENT 15. TELEPHONE NO. (Include Area Code) 16. EMAIL ADDRESS 17. DATE PREPARED (YYYYMMDD)
18. WBS ELEMENT CODE 19. WBS REPORTING ELEMENT 20. NUMBER OF UNITS 21. APPROPRIATION
a. TO DATE b. AT COMPLETION RDT&E
PROCUREMENT
O&M
| FUNCTIONAL DATA ELEMENTS | COSTS AND HOURS INCURRED TO DATE | ||
| (thousands of U.S. Dollars or thousands of hours) | FORECAST OF COSTS AND HOURS INCURRED AT COMPLETION |
A. NONRECURRING B. RECURRING C. TOTAL D. NONRECURRING E. RECURRING F.TOTAL
LABOR
TOTAL LABOR HOURS
TOTAL LABOR DOLLARS
MATERIALS
TOTAL MATERIAL DOLLARS
OTHER COSTS
OTHER COSTS NOT SHOWN ELSEWHERE (Specify in Remarks)
SUMMARY
TOTAL COST (Direct and Overhead)
22. REMARKS
DD FORM 1921-1, MAY 2011 SECURITY CLASSIFICATION Unclassified
WBS 2.3
SECURITY CLASSIFICATION Unclassified
FUNCTIONAL COST-HOUR REPORT Form Approved
The public reporting burden for this collection of information is estimated to average 16 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
1. MAJOR PROGRAM a. NAME:
b. PHASE/MILESTONE 2. PRIME MISSION PRODUCT 3. REPORTING ORGANIZATION TYPE 4. NAME/ADDRESS (Include Zip Code) 5. APPROVED PLAN NUMBER
Pre-A B C-FRP PRIME / ASSOCIATE CONTRACTOR DIRECT-REPORTING SUBCONTRACTOR GOVERNMENT a. PERFORMING ORGANIZATION b. DIVISION
A C-LRIP O&S
6. CUSTOMER (Direct-Reporting Subcontractor Use Only) 7. TYPE ACTION
a. CONTRACT NO.: c. SOLICITATION NO.: e. TASK ORDER/DELIVERY ORDER/LOT NO.:
b. LATEST MODIFICATION: d. NAME:
8. PERIOD OF PERFORMANCE 9. REPORT CYCLE 10. SUBMISSION NUMBER 11. RESUBMISSION NUMBER 12. REPORT AS OF (YYYYMMDD)
a. START DATE (YYYYMMDD): INITIAL
b. END DATE (YYYYMMDD): INTERIM
FINAL
13. NAME (Last, First, Middle Initial) 14. DEPARTMENT 15. TELEPHONE NO. (Include Area Code) 16. EMAIL ADDRESS 17. DATE PREPARED (YYYYMMDD)
18. WBS ELEMENT CODE 19. WBS REPORTING ELEMENT 20. NUMBER OF UNITS 21. APPROPRIATION
a. TO DATE b. AT COMPLETION RDT&E
PROCUREMENT
O&M
| FUNCTIONAL DATA ELEMENTS | COSTS AND HOURS INCURRED TO DATE | ||
| (thousands of U.S. Dollars or thousands of hours) | FORECAST OF COSTS AND HOURS INCURRED AT COMPLETION |
A. NONRECURRING B. RECURRING C. TOTAL D. NONRECURRING E. RECURRING F.TOTAL
LABOR
TOTAL LABOR HOURS
TOTAL LABOR DOLLARS
MATERIALS
TOTAL MATERIAL DOLLARS
OTHER COSTS
OTHER COSTS NOT SHOWN ELSEWHERE (Specify in Remarks)
SUMMARY
TOTAL COST (Direct and Overhead)
22. REMARKS
DD FORM 1921-1, MAY 2011 SECURITY CLASSIFICATION Unclassified
WBS 2.4
SECURITY CLASSIFICATION Unclassified
FUNCTIONAL COST-HOUR REPORT Form Approved
The public reporting burden for this collection of information is estimated to average 16 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
1. MAJOR PROGRAM a. NAME:
b. PHASE/MILESTONE 2. PRIME MISSION PRODUCT 3. REPORTING ORGANIZATION TYPE 4. NAME/ADDRESS (Include Zip Code) 5. APPROVED PLAN NUMBER
Pre-A B C-FRP PRIME / ASSOCIATE CONTRACTOR DIRECT-REPORTING SUBCONTRACTOR GOVERNMENT a. PERFORMING ORGANIZATION b. DIVISION
A C-LRIP O&S
6. CUSTOMER (Direct-Reporting Subcontractor Use Only) 7. TYPE ACTION
a. CONTRACT NO.: c. SOLICITATION NO.: e. TASK ORDER/DELIVERY ORDER/LOT NO.:
b. LATEST MODIFICATION: d. NAME:
8. PERIOD OF PERFORMANCE 9. REPORT CYCLE 10. SUBMISSION NUMBER 11. RESUBMISSION NUMBER 12. REPORT AS OF (YYYYMMDD)
a. START DATE (YYYYMMDD): INITIAL
b. END DATE (YYYYMMDD): INTERIM
FINAL
13. NAME (Last, First, Middle Initial) 14. DEPARTMENT 15. TELEPHONE NO. (Include Area Code) 16. EMAIL ADDRESS 17. DATE PREPARED (YYYYMMDD)
18. WBS ELEMENT CODE 19. WBS REPORTING ELEMENT 20. NUMBER OF UNITS 21. APPROPRIATION
a. TO DATE b. AT COMPLETION RDT&E
PROCUREMENT
O&M
| FUNCTIONAL DATA ELEMENTS | COSTS AND HOURS INCURRED TO DATE |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .