CDRLs--APS.pdf

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 and Communications 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

DATA ITEM DESCRIPTION

TITLE: INTEGRATED MASTER SCHEDULE (IMS)

NUMBER: DI-MGMT-81650 APPROVAL DATE: 20050330

AMSC NUMBER: D7544 LIMITATION:

DTIC APPLICABLE: GIDEP APPLICABLE:

PREPARING ACTIVITY: OUSD(AT&L)ARA/AM(SO)

APPLICABLE FORMS: None

USE/RELATIONSHIP: The Integrated Master Schedule (IMS) is an integrated schedule containing the networked, detailed tasks necessary to ensure successful program execution. The IMS is vertically traceable to the Integrated Master Plan (IMP) (if applicable), the Contract Work Breakdown Structure (CWBS), and the Statement of Work (SOW). The IMS shall be used to verify attainability of contract objectives, to evaluate progress toward meeting program objectives, and to integrate the program schedule activities with all related components. This DID is applicable to development, major modification, and low rate initial production efforts; it is not typically applied to full rate production efforts.

a. This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

b. This DID shall be applied to contracts that require Earned Value Management (EVM) and other contracts based on the contract risk assessment.

Refer to the Earned Value Management Implementation Guide (EVMIG) for guidance on tailoring reporting.

c. The prime contractor is required to include significant external interfaces and critical items from suppliers, teammates, or other detailed schedules that depict significant and/or critical elements and Government furnished equipment or information dependencies for the entire contractual effort in a single integrated network. The determination of significant and critical shall be agreed to by the Government and the contractor and shall be defined and documented in the Contract Data Requirements List (CDRL).

d. The IMS shall be statused according to the contractor’s management control system and shall be submitted no less frequently than monthly. If a Contract Performance Report (CPR) is required, the IMS shall be statused and submitted to the procuring activity prior to or concurrently with CPR Formats 1-5 (as applicable). The IMS may reflect data either as of the end of the calendar month or as of the contractor’s accounting period cutoff date, provided it is consistent and traceable to the CPR (if applicable). When subcontractor schedule data reflects a different status date than the prime contractor’s schedule status date, these status dates shall be described in the analysis section of the IMS.

e. This DID shall be used in conjunction with the CWBS DID, DI-MGMT-81334A, and the CPR DID, DI-MGMT-81466. (Note: The IMS DID may be required when there is no EVM (CPR) requirement.)

REQUIREMENTS:

1. Format. The IMS shall be created using a network capable Commercially Off the Shelf (COTS) scheduling software application. Unless otherwise provided in the CDRL, the IMS shall be delivered electronically in the native digital format (i.e., an electronic file produced by the contractor’s scheduling

Source: https://assist.dla.mil -- Downloaded: 2015-10-06T19:13Z Check the source to verify that this is the current version before use.

DI-MGMT-81650

tool). (Note: When the technology is available, the CDRL may be tailored, upon agreement between the prime contractor and the Government representative, to allow the American National Standards Institute (ANSI) X12 standard (806 transaction set), the United Nations Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT) standard (PROTAP message), or the XML equivalent to be used to submit data electronically to the procuring activity with on-line access to the data.)

2. Content. The schedule shall contain the contract milestones, accomplishments, and discrete tasks/activities (including planning packages where applicable) from contract award to the completion of the contract. The schedule shall be an integrated, logical network-based schedule that correlates to the CWBS, and is vertically and horizontally traceable to the cost/schedule reporting instrument used to address variances such as the CPR (if applicable). The schedule shall have a numbering system that provides traceability to the IMP (if applicable) and SOW. It shall contain contractual milestones and descriptions and display summary, intermediate, and detailed schedules, and periodic analysis of progress to date. It shall include fields and data that enable the user to access the information by product, process, or organizational lines.

2.1 Contract Milestones and Definitions. Key programmatic events, which define progress and completion for each CWBS element, along with the definition for successful completion of the milestone.

2.2 Summary Master Schedule. A top-level schedule of key tasks/activities and milestones at the summary level of the CWBS and IMP (if applicable). It shall be an integrated roll up of the intermediate and detailed schedules (see

2.3 and 2.4 below) (vertical integration).

2.3 Intermediate Schedules. Mid-level contract schedules that include key tasks/activities and milestones and all associated accomplishments in the summary master schedule, traceable to the CWBS element or IMP event as necessary to display work effort at the intermediate level of summarization.

There may be several intermediate schedules that depict varying levels of detail. They shall be integrated roll ups of the detailed schedules (see 2.4 below) (vertical integration).

2.4 Detailed Schedules. The lowest level of contract tasks/activities that form the network. The detailed schedules shall contain horizontal and vertical integration, as a minimum, at the work package and planning package level. The detailed schedules shall include all tasks/activities, work packages, and planning packages identified in the contract Performance Measurement Baseline (PMB). Every discrete task/activity, work package, and planning package shall be clearly identified and directly related to a control account. Work packages and planning packages shall be individually represented and summarize to or reconcile with the total budget for that control account. If Level of Effort (LOE) control accounts, work packages, or planning packages are included as tasks in the IMS, they shall be clearly identified as such. The detailed tasks/activities, work packages, and planning packages shall be traceable to only one CWBS, IMP, and performing organizational element, as applicable. The level of detail in the IMS (including number and duration of tasks/activities) shall follow the contractor’s EVM process as documented in the EVMS system description, program directives, etc. Shorter-term work packages (ideally equal in length to the statusing interval) are preferred because they provide more accurate and reliable measures of work accomplished.

2.4.1 Key Elements of Detailed Schedules. The key elements of the detailed schedules include the following:

2.4.1.1 Task/Activity. An element of work with duration.

2.4.1.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.

2.4.1.3 Duration. The length of time estimated (or realized) to accomplish a task/activity.

2.4.1.4 Percent Complete (Schedule). The proportion of an activity or task that has been completed to time now. This usually involves updating or statusing the activity or task utilizing one of two methods: (1) update the remaining time to complete (remaining duration) and the scheduling software will then automatically update the schedule percent complete or (2) update the schedule percent complete and allow the scheduling software to calculate the time remaining (remaining duration) to complete. Either method will use the following formula: Percent of Duration Completed = (Actual Duration / Total Duration) X 100.

2.4.1.5 Task/Activity and Milestone Descriptions. These are descriptive titles that are concise, complete, and clearly identify the work effort being accomplished. Abbreviations may be used to shorten the descriptive titles.

2.4.1.6 Task/Activity Codes and Data Dictionary. A list of field definitions and code structures. This list shall be provided to the procuring activity.

2.4.1.7 Relationship/Dependency. These identify how predecessor and successor tasks/activities and milestones are logically linked.

Relationships, also called network logic, are modeled in four ways:

2.4.1.7.1 FS (Finish to Start). A predecessor task/activity or milestone that must finish before a succeeding task/activity or milestone can start. FS relationships shall be used whenever possible.

2.4.1.7.2 SS (Start to Start). A predecessor task/activity or milestone that must start before a succeeding task/activity or milestone can start.

2.4.1.7.3 FF (Finish to Finish). A predecessor task/activity or milestone that must finish before a succeeding task/activity or milestone can finish.

2.4.1.7.4 SF (Start to Finish). A predecessor task/activity or milestone that must start before a succeeding task/activity or milestone can finish.

2.4.1.8 Total Float/Slack. The amount of time a task/activity or milestone can slip before it delays the contract or project finish date.

2.4.1.9 Free Float/Slack. The amount of time a task/activity or milestone can slip before it delays any of its successor tasks/activities or milestones.

2.4.1.10 Lag. An interval of time that must occur between a predecessor and successor task/activity or milestone. Since negative time is not demonstrable, negative lag is not encouraged. (Note: Lag should not be used to manipulate float/slack or constrain schedule.)

2.4.1.11 Early Start (ES). The earliest start date a task/activity or milestone can begin the precedence relationships. A computer-calculated date.

2.4.1.12 Early Finish (EF). The earliest finish date a task/activity or milestone can end. A computer-calculated date.

2.4.1.13 Late Start (LS). The latest start date a task/activity or milestone can start without delaying the contract or project target completion date. A computer-calculated date.

2.4.1.14 Late Finish (LF). The latest date a task/activity or milestone can finish without delaying the contract or project target completion date. A computer-calculated date.

2.4.1.15 Critical Path. A sequence of discrete tasks/activities in the network that has the longest total duration through the contract or project.

Discrete tasks/activities along the critical path have the least amount of float/slack. The critical path and near-critical paths (reporting requirements for near-critical paths shall be specified in the CDRL) are calculated by the scheduling software application. The guidelines for critical path and near-critical path reporting are as follows:

2.4.1.15.1 Methodology. The IMS software application computes a critical path and near-critical paths based on precedence relationships, lag times, durations, constraints, and status. Artificial constraints and incorrect, incomplete, or overly constrained logic shall be avoided because they can skew the critical path and near-critical paths.

2.4.1.15.2 Identification. The critical path shall be easily identified.

2.4.1.16 Constraints. Limits applied to network start and finish dates (e.g., “finish no later than”). (Note: Certain types of constraints should be used judiciously because they may impact or distort the network critical path.)

2.4.1.17 Current Schedule. The IMS reflects the current status and forecast.

It includes forecasted starts and finishes for all remaining tasks/activities and milestones. Significant variances to the baseline schedule shall be explained in the periodic analysis. Thresholds for reporting shall be specified in the CDRL.

2.4.1.18 Baseline Schedule. Baseline dates in the IMS shall be consistent with the baseline dates in the PMB for all work packages, planning packages, and control accounts (if applicable). The guidelines for maintaining the baseline schedule are as follows:

2.4.1.18.1 Schedule Changes. Changes to the schedule shall be baselined when incorporated into the schedule.

2.4.1.18.2 Baseline Schedule Changes. Changes to the baseline schedule shall be made in accordance with the contractor’s EVM process. Any movement of contractual milestones in the baseline schedule shall be derived only from either authorized contract changes or an approved over target schedule.

2.4.1.19 Schedule Progress. The IMS shall reflect actual progress and maintain accurate start and finish dates for all tasks/activities and milestones. The guidelines for reflecting schedule progress are as follows:

2.4.1.19.1 Actual Start and Finish Dates. Actual start and actual finish dates shall be recorded in the IMS. Actual start and actual finish dates, as recorded, shall not be later than the status date.

2.4.1.19.2 Progress Line. The progress line depicted in a Gantt chart shall be applied to the current schedule.

2.4.1.20 Retention of Data for Completed Tasks/Activities. Historical performance on completed tasks/activities shall be maintained electronically for analytical use. Historical performance shall be maintained at the time of key program events (Integrated Baseline Review, Critical Design Review, etc.)

for all critical tasks/activities. Data to be retained includes logic, actual and baseline durations, actual and baseline start and finish dates, and the three-point estimates that were used before the task/activity started.

2.4.1.21 External Dependencies. The IMS shall identify significant external dependencies that involve a relationship or interface with external organizations, including all Government furnished items (e.g., decisions, facilities, equipment, information, data, etc.). The determination of significant shall be agreed to by the Government and contractor and shall be defined and documented in the CDRL. The required or expected delivery dates shall also be identified in the IMS.

2.4.1.22 Schedule Margin. A management method for accommodating schedule contingencies. It is a designated buffer and shall be identified separately and considered part of the baseline. Schedule margin is the difference between contractual milestone date(s) and the contractor’s planned date(s) of accomplishment.

2.4.1.23 Schedule Risk Assessment. A schedule risk assessment predicts the probability of project completion by contractual dates. Three-point estimates shall be developed for remaining durations of remaining tasks/activities that meet any of the following criteria: (1) critical path tasks/activities, (2) near-critical path tasks/activities (as specified in the CDRL), (3) high risk tasks/activities in the program’s risk management plan. These estimates include the most likely, best case, and worst case durations. They are used by the contractor to perform a probability analysis of key contract completion dates. The criteria for estimated best and worst case durations shall be applied consistently across the entire schedule and documented in the contractor’s schedule notes and management plan. The guidelines for estimates are as follows:

2.4.1.23.1 Most Likely Estimate. Schedule durations based on the most likely estimates.

2.4.1.23.2 Best/Worst Case Estimates. Best and worst case assumptions shall be disclosed.

The contractor schedule risk assessment shall explain changes to the critical path, margin erosion, and mitigation plans. It shall be incorporated into the contractor’s program risk management process. The schedule risk assessment shall be submitted as specified in the CDRL and prior to the Integrated Baseline Review. The risk analysis may be performed within the IMS or within a separate risk tool as appropriate based on the capability of the automated scheduling tool.

2.4.1.24 User Defined Fields. All user defined fields in the IMS shall be identified by providing a mapping of all fields used in the scheduling software application.

2.4.1.25 Reserved Fields. The Government may reserve some fields and/or require the contractor to use certain fields for specific information. The requirement for reserved fields shall be specified in the CDRL.

2.4.1.26 Calendar. The arrangement of normal working days, together with non-working days, such as holidays, as well as special work days (i.e., overtime periods) used to determine dates on which project work will be completed.

2.5 Monthly Analysis. Monthly analysis is a monthly assessment of schedule progress to date and includes changes to schedule assumptions, variances to the baseline schedule, causes for the variances, potential impacts, and recommended corrective actions to minimize schedule delays. The analysis shall also identify potential problems and an assessment of the critical path and near-critical paths. Thresholds for reporting significant variances to the baseline schedule and near-critical paths shall be specified in the CDRL.

If a CPR Format 5 is required, the monthly analysis shall be submitted to the procuring activity prior to or concurrently with the CPR Format 5.

END OF DI-MGMT-81650

Source: https://assist.dla.mil -- Downloaded: 2015-10-06T19:12Z

1_DATA_ITEM_NO: E003

2_TITLE_OF_DATA_ITEM: INTEGRATED MASTER SCHEDULE

3_SUBTITLE: INTEGRATED MASTER SCHEDULE

4_AUTHORITY_Data_Acquisit: 2 DID'S TO CHOOSE FROM

5_CONTRACT_REFERENCE: PWS

6_REQUIRING_OFFICE: AFLCMC/HBDH

7_DID_250_REQ: LT

8_APP_CODE: A

DIST_STATEMENT: F

10_FREQUENCY: BLK 16

11_AS_OF_DATE: ASREQ

12_DATE_OF_FIRST_SUBMISSI: SEE BLK 16

13_DATE_OF_SUBSEQUENT_SUB: SEE BLK 16

addressee1: AFLCMC/HBDH draft1: 0 reg1: 1 repro1: 0 addressee2:

draft2:

reg2:

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: 0 total_repro: 0

16_REMARKS: BLOCK 4: TAILOR DATA ITEM AS FOLLOWS:

CONTRACTOR FORMAT IS ACCEPTABLE.

DATA TO BE PROVIDED ON CD ROM OR OTHER APPROVED MEDIA AS AUTHORIZED BY THE GOVERNMENT.

17_PRICE_GROUP:

ESTIMATED_TOTAL_PRICE:

G_PREPARED_BY:

H_DATE:

1_APPROVED_BY:

J_DATE:

Page: 1 reg38t: 1

A_CONTRACT_LINE_ITEM_NO:

B_EXHIBIT: A

TDP:

TM:

OTHER: PROG

DSYSTEMITEM:

E_CONTRACTPR_NO:

FCONTRACTOR:

16_REMARKS_Continued:

Page2:

of_pages: 1

Reset:

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

Title: Management Plan

Number: DI-MGMT-80004A Approval Date: 30 OCT 2006 AMSC Number: 7621 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: The management plan describes the contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID may be applied in any contract or program phase where the contract management is under the direction and control of the contractor.

Requirements:

1. Reference documents. None.

2. Format. The plan shall be in a format that the contractor devises and conforms to the following:

a. Identification. The plan shall be identified with the preparing office or contractors title, the identifying numbers or designation of the Contract/Procurement Request, the identify and/or nomenclature of the system/component/program/project, the security classification and the Government activity issuing the controlling contract.

b. Descriptive material. As may be needed to clarify or explain matters in the text, the plan may include descriptive material, sketches, drawings, photographs, tables, forms, graphs, worksheets, charts, etc.

c. Page size. The plan may be typewritten or printed on standard size paper, e.g., 8 ½ x 11 inches or metric A4. The pages shall be sequentially numbered and security bound together. As necessary, graphic material may be one-way fold-outs. All attachments shall be identified and referenced in the text. Each section and paragraph shall be numbered.

d. Table of contents and index. Plans of more than 30 pages in length shall contain a

Source: https://assist.dla.mil -- Downloaded: 2015-10-06T19:23Z

h. delivery procedures

DI-MGMT-80004A

table of contents. Plans more than 120 pages in length shall also include an Index.

e. Legibility. The document shall be legible and reproducible.

3.1 General. The Management Plan shall consist of the organizational structure, the assignment of functions, duties, and responsibilities, the procedures and policies and the reporting requirements that are established for the initiation, monitoring, control, completion, test and verification, and reporting of contractual tasks, projects, and programs.

3.2 Specific contents. The Management Plan shall cover the organizational structure, program management methodology, personnel, security, and the reports as described herein. Other subjects to be included are as follows:

a. design control

b. reliability

c. configuration control

d. standardization

e. quality assurance

f. provisioning

g. control of Government property

i. tests

j. certifications

k. packaging

l. shipping

m. other

3.3 Organizational structure. The plan shall present an organizational chart and supporting narrative portraying the contractor’s business (corporate) structure. It shall describe the functional relationships and responsibilities among the organizational elements that will participate in the accomplishment of the contractual commitments.

3.4 Program management. The plan shall present an organizational chart and supporting narrative describing the management office the contractor establishes to manage the contractual commitments. The plan shall define the direct lines of control, responsibilities, functional relationships, and authority between the management office and the contractor’s other organizational elements. The plan shall also describe all interfaces between the contractor and the Government and between the contractor and other contractors which are necessary and pertinent to the accomplishment of contractual tasks, projects and programs.

3.5 Methodology.

a. The plan include a narrative description of the technical approach or methods the contractor will employ to accomplish contractual tasks, projects, and programs, including, as applicable, development, tests, manufacture, construction, formulation, installation, logistics support, training, maintenance documentation, and configuration controls.

b. The plan shall include a milestone chart graphically depicting the schedule of events associated with accomplishing each contractual commitment.

3.6 Personnel.

a. The plan shall list the personnel staffing of the contractor’s management office that directs the contractual tasks, projects, and programs and assist in completing the contract. The listing shall include the education, training, skills, experience, and security clearance that personnel require to fill each such position and shall state the identity, background, and work experience of the personnel assigned to fill these positions.

b. The plan shall also describe the staffing required for proper accomplishment of each contractual task by skill type, skill level, number of personnel, and security clearance. When submitted as part of a proposal, the plan shall state how many such personnel are currently available and how many new hires are required to staff fully to accomplish each task as scheduled.

3.7 Security.

a. Provide a Standard Practice Procedure (SPP) which fully describes the security program, safeguards emergency procedures to be established to the protection of Government-furnished and contractor-developed classified materials prepared In conjunction with the project. The SPP shall be prepared in accordance with guidelines contained in the Industrial Security Manual, Purchase Description, and such additional requirements as may be stipulated by the cognizant security compliance organization. The SPP shall require approval by the Government.

b. Develop a comprehensive security accreditation plan to demonstrate how the computer security requirements stipulated in the PD, as applicable, have been accounted for in the system design, and how satisfaction of each requirement will be explicitly demonstrated in the test program. This plan shall also identify any specific support equipment or software to be provided for demonstration of design compliance and/or system compliance with the planned security requirements. The plan shall require approval by the Government prior to implementation.

c. Reports. The plan shall describe the management methods the contractor will employ to ensure meeting all preparations, format, and submittal requirements established by the CDRL (DD Form 1423) for data to be delivered to the Government.

4. END OF DI-MGMT-80004A

DATA ITEM DESCRIPTION

Requirements:

data_item: E004 title: MANAGEMENT PLAN sub:

auth: DI-MGMT-80004A ref: PWS 1.1.2.10.9, 1.1.5, Table 2-1 req_ofc: AFLCMC/HBDH dd250: DD appcode: A dist: D freq: BLK 16 asof: AS REQ firstsub: BLK 16 subsub: BLK 16 addressee1: AFLCMC/HBDH draft1: 1 reg1: 1 repro1: 1 addressee2:

draft2:

reg2:

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: 1 total_reg: 1 total_repro: 1 remarks: THE CONTRACTOR SHALL PROVIDE AS DIRECTED BY THE PCO.

DATA TO BE PROVIDED ON CD ROM OR OTHER APPROVED MEDIA AS AUTHORIZED BY THE GOVERNMENT.

group:

total_price:

prep_name:

line_item:

exhibit:

xtdp: Off xtm: Off othercat:

system: Antenna Program Support ctr_no:

contr:

remarksb:

Page2:

Reset:

2015-12-01T11:40:32-0600

SCHULTZ.LISSA.A.1216586332

prep_date: 1 Dec 15 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

Title: Technical Report–Study/Services

Number: DI-MISC-80508B Approval Date: 14 Nov 2006 AMSC Number: 7633 Limitation: N/A DTIC Applicable: Yes Defense Technical Information Center (DTIC), 8725 John J. Kingman Rd.

Suite. 0944, Fort Belvoir, VA 22060-6218 GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: A technical report provides fully documented results of studies or analysis performed.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID supersede DI-MISC-80508A

Requirements:

1. Reference documents. None.

2. Format.

(a) The report and all attachments shall be typewritten, or otherwise clearly lettered, and shall be duplicated using non-fading ink.

(b) Text shall be prepared on standard letter size paper (8 ½ x 11”) .

(c) When attachments are included, they shall be fully identified, referenced in the text, and folded to conform to the size paper used in the report.

(d) Security classification and distribution markings shall conform to the requirements of the contract, purchase description and security requirements checklist, as

Source: https://assist.dla.mil -- Downloaded: 2015-10-06T14:53Z

DI-MISC-80508B

3. Contents.

(a) Title Page – Identifies the report by providing contract number, project name or purchase description title, task number, and reporting period.

(b) Table of Contents.

(c) Section I – Includes the following:

(1) Introduction

(2) Summary – A brief statement of results obtained for the analytic effort.

(3) Conclusions and their condensed technical substantiation’s.

(d) Section II – A complete and detailed description of the analytic results which led to the conclusions stated in Section I above.

4. END OF DI-MISC-80508B

Source: https://assist.dla.mil -- Downloaded: 2015-10-06T14:53Z

DATA ITEM DESCRIPTION

Requirements:

data_item: E005 title: TECH REPORTS/STUDY SERVICES sub: CORRECTIVE ACTION RPT auth: DI-MISC-80508B ref: PWS 1.12.10.4 & 1.1.3.4.5 req_ofc: AFLCMC/HBDH dd250: DD appcode: A dist: D freq: BLK 16 asof: AS REQ firstsub: BLK 16 subsub: BLK 16 addressee1: AFLCMC/HBDH draft1: 1 reg1: 1 repro1: 1 addressee2:

draft2:

reg2:

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: 1 total_reg: 1 total_repro: 1 remarks: BLOCK 4: TAILOR DATA ITEM DESCRIPTION (DID) IS AMENDED AS FOLLOWS:

ADD 4) :

LIST ALL DISCREPANCIES AND ASSOCIATED CORRECTIVE ACTIONS/RECOMMENDATIONS TO ADDRESS DISCREPANCIES OR CORRECTIVE ACTION TAKEN.

CONTRACTOR FORMAT IS ACCEPTABLE.

THE FOLLOWING INFORMATION SHALL BE SUBMITTED BY ANTENNA, BUILDING OR SUBSYSTEM IDENTIFICATION NUMBER:

A) DAMAGE LOCATION & TYPE (CORROSION, STRIKE, ETC.)

B) SEVERITY

C) REPAIR ACTION TAKEN

D) PHOTO DOCUMENTATION

BLOCKS 10, 11, 12 & 13: A MAINTENACE ASSESSMENT REPORT SHALL BE DELIVERED FOR EACH STATION. THE REPORT IS DUE 30 CALENDAR DAYS AFTER COMPLETION OF THE SITE SURVEY. THE GOVERNMENT REQUIRES 15 CALENDAR DAYS FOR REVIEW.

DATA TO BE PROVIDED ON CD ROM OR OTHER APPROVED MEDIA AS AUTHORIZED BY THE GOVERNMENT.

group:

total_price:

prep_name:

line_item:

exhibit:

xtdp: Off xtm: Off othercat:

system: Antenna Program Support ctr_no:

contr:

remarksb:

Page2:

Reset:

2015-12-01T11:41:23-0600

SCHULTZ.LISSA.A.1216586332

prep_date: 1 Dec 15 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

Title: Management Plan

Number: DI-MGMT-80004A Approval Date: 30 OCT 2006 AMSC Number: 7621 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: The management plan describes the contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID may be applied in any contract or program phase where the contract management is under the direction and control of the contractor.

Requirements:

1. Reference documents. None.

2. Format. The plan shall be in a format that the contractor devises and conforms to the following:

a. Identification. The plan shall be identified with the preparing office or contractors title, the identifying numbers or designation of the Contract/Procurement Request, the identify and/or nomenclature of the system/component/program/project, the security classification and the Government activity issuing the controlling contract.

b. Descriptive material. As may be needed to clarify or explain matters in the text, the plan may include descriptive material, sketches, drawings, photographs, tables, forms, graphs, worksheets, charts, etc.

c. Page size. The plan may be typewritten or printed on standard size paper, e.g., 8 ½ x 11 inches or metric A4. The pages shall be sequentially numbered and security bound together. As necessary, graphic material may be one-way fold-outs. All attachments shall be identified and referenced in the text. Each section and paragraph shall be numbered.

d. Table of contents and index. Plans of more than 30 pages in length shall contain a

h. delivery procedures table of contents. Plans more than 120 pages in length shall also include an Index.

e. Legibility. The document shall be legible and reproducible.

3.1 General. The Management Plan shall consist of the organizational structure, the assignment of functions, duties, and responsibilities, the procedures and policies and the reporting requirements that are established for the initiation, monitoring, control, completion, test and verification, and reporting of contractual tasks, projects, and programs.

3.2 Specific contents. The Management Plan shall cover the organizational structure, program management methodology, personnel, security, and the reports as described herein. Other subjects to be included are as follows:

a. design control

b. reliability

c. configuration control

d. standardization

e. quality assurance

f. provisioning

g. control of Government property

i. tests

j. certifications

k. packaging

l. shipping

m. other

3.3 Organizational structure. The plan shall present an organizational chart and supporting narrative portraying the contractor’s business (corporate) structure. It shall describe the functional relationships and responsibilities among the organizational elements that will participate in the accomplishment of the contractual commitments.

3.4 Program management. The plan shall present an organizational chart and supporting narrative describing the management office the contractor establishes to manage the contractual commitments. The plan shall define the direct lines of control, responsibilities, functional relationships, and authority between the management office and the contractor’s other organizational elements. The plan shall also describe all interfaces between the contractor and the Government and between the contractor and other contractors which are necessary and pertinent to the accomplishment of contractual tasks, projects and programs.

3.5 Methodology.

a. The plan include a narrative description of the technical approach or methods the contractor will employ to accomplish contractual tasks, projects, and programs, including, as applicable, development, tests, manufacture, construction, formulation, installation, logistics support, training, maintenance documentation, and configuration controls.

b. The plan shall include a milestone chart graphically depicting the schedule of events associated with accomplishing each contractual commitment.

3.6 Personnel.

a. The plan shall list the personnel staffing of the contractor’s management office that directs the contractual tasks, projects, and programs and assist in completing the contract. The listing shall include the education, training, skills, experience, and security clearance that personnel require to fill each such position and shall state the identity, background, and work experience of the personnel assigned to fill these positions.

b. The plan shall also describe the staffing required for proper accomplishment of each contractual task by skill type, skill level, number of personnel, and security clearance. When submitted as part of a proposal, the plan shall state how many such personnel are currently available and how many new hires are required to staff fully to accomplish each task as scheduled.

3.7 Security.

a. Provide a Standard Practice Procedure (SPP) which fully describes the security program, safeguards emergency procedures to be established to the protection of Government-furnished and contractor-developed classified materials prepared In conjunction with the project. The SPP shall be prepared in accordance with guidelines contained in the Industrial Security Manual, Purchase Description, and such additional requirements as may be stipulated by the cognizant security compliance organization. The SPP shall require approval by the Government.

b. Develop a comprehensive security accreditation plan to demonstrate how the computer security requirements stipulated in the PD, as applicable, have been accounted for in the system design, and how satisfaction of each requirement will be explicitly demonstrated in the test program. This plan shall also identify any specific support equipment or software to be provided for demonstration of design compliance and/or system compliance with the planned security requirements. The plan shall require approval by the Government prior to implementation.

c. Reports. The plan shall describe the management methods the contractor will employ to ensure meeting all preparations, format, and submittal requirements established by the CDRL (DD Form 1423) for data to be delivered to the Government.

4. END OF DI-MGMT-80004A

DATA ITEM DESCRIPTION

Requirements:

data_item: E006 title: PHASE OUT TRANSITION PLAN sub:

auth: DI-MGMT-81945 ref: PWS 1.12 req_ofc: AFLCMC/HBDH dd250: DD appcode: A dist: D freq: BLK 16 asof: AS REQ firstsub: BLK 16 subsub: BLK 16 addressee1: AFLCMC/HBDH draft1: 1 reg1: 1 repro1: 1 addressee2: ACO 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:

ad…