ATT0056 CDRL TS28 Installation Schedule.pdf
PDF 108 KB Posted
- Attached to
- TOTAL ENGINEERING and INTEGRATION SERVICES-TEIS IV Federal contract opportunity
- Solicitation number
- W9128Z-20-R-0001
About this file
This document contains a Contract Data Requirements List (CDRL) and details of a federal contract opportunity with the Department of the Army. The CDRL outlines requirements for an Installation Schedule data item to be delivered under the contract. It requires submission of a draft within 45 days of award and monthly updates thereafter, using Microsoft Project format. The Installation Schedule must include milestones, tasks, durations, percent completes, descriptions, and logical relationships showing the integrated project schedule from award through completion. It also requires a monthly progress analysis identifying potential problems and variances from the baseline. One soft copy of the report is to be emailed to the Technical Monitor and Contracting Officer's Representative.
The federal contract opportunity is for Total Engineering and Integration Services to provide information systems engineering and information technology support services to the United States Army Information Systems Engineering Command. Support is required for all phases of projects worldwide, including secure and challenging environments, and may involve work in highly secure facilities with highest clearances.
View the file
Other files for this federal contract opportunity
Show all 50
TOTAL ENGINEERING and INTEGRATION SERVICES-TEIS IV has more files on GovTribe.
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
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
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
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 delivering such data item to the Government.
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
| data_item: TS28 |
| title: Installation Schedule |
| sub: |
| auth: N/A |
| ref: Sample Task 2 para 3.1.16, 3.2.5 |
| req_ofc: HQUSAISEC ELIE-ISE-TS |
| dd250: |
| appcode: |
| dist: |
| freq: |
| asof: |
| firstsub: |
| subsub: |
| addressee1: TM |
| draft1: 1 |
| reg1: 1 |
| repro1: |
| addressee2: COR |
| draft2: 1 |
| reg2: 1 |
| repro2: |
| 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: 2 |
| total_reg: 2 |
| total_repro: 0 |
| remarks: General. The Installation Schedule (IS) is an integrated schedule containing the networked, detailed tasks necessary to ensure successful project execution. The installation schedule will be developed and maintained by acquiring the project schedules from all contributing organizations and updates of their schedules. The Integrated Project Schedule (IPS) shall be used to verify attainability of project objectives, to evaluate progress toward meeting project objectives, and to integrate the project schedule activities with input from all stakeholders. |
1. Dates of submission. Submit a draft IS 45 calendar days after date of contract award and provide updates to the Government on a monthly basis thereafter.
2. Format. Provide the IS in Microsoft Project 2013 or later version.
3. Content. The IS shall contain the milestones, accomplishments, and discrete tasks/activities to include planning packages (where applicable) from contract award through completion of the project. The IS shall be an integrated, logical network-based schedule. It shall contain milestones and descriptions, and periodic analysis of progress to date. The IS shall include fields and data that enable the user to access the information by product, process, or organizational lines.
A. Milestones and definitions. The IS shall show key project events, which define progress and completion of each event, along with the definition for successful completion of the milestone.
B. Key elements of the schedule. The key elements of the detailed schedules include the following:
1) Task/activity. An element of work with duration.
2) Milestone. A specific definable accomplishment in the contract network, recognizable at a particular point in time. Milestones have zero duration and do not consume resources.
3) Duration. The length of time estimated (or realized) to accomplish a task/activity.
| group: |
| total_price: |
| prep_name: GOVERNMENT |
| line_item: |
| exhibit: |
| xtdp: Off |
| xtm: Off |
| othercat: |
| system: |
| ctr_no: |
| contr: |
| remarksb: 4) Percent complete. The proportion of an activity or task that has been completed to present (now). |
5) Task/activity and milestone description. These are descriptive titles that are concise, complete, and clearly identify the work effort being accomplished, to include the inherent logistics issues.
6) Task/activity codes and data dictionary. A list of field definitions and code structure.
7) Relationship/dependency. These identify how predecessor and successor task/activities and milestones are logically linked. The relationships shall be modeled from start to finish.
C. Monthly analysis. The IS shall be assessed monthly for progress to date and include changes to the schedule, and variances to the baseline schedule. The assessment shall identify potential problems and an analysis of the critical path and near critical paths.
4. Method of delivery: One (1) soft copy of the report shall be submitted to the Technical Monitor (TM), and Contracting Officer’s Representative (COR) via e-mail. The report shall be fully identified and referenced in the subject line of the email message. The document shall not be locked or protected in any fashion that would prevent text to be copied or edited by the Government after delivery.
| Page2: 2 |
| Reset: |
| prep_date: |
| app_by: |
| app_date: |
| Page: 1 |
| of_pages: 2 |
| app: Adobe Professional 8.0 |
File details come from the government source that posted it. Updated .