Ex A_CDRLs.pdf

PREVIOUS EDITION MAY BE USED.

DD FORM 1423, FEB 2024 Page 1 of 2

UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

TSM IT & ENG SPT SERVICES

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

SAIC

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

SOFTWARE SUSTAINABILITY PACKAGE

3. SUBTITLE

SOURCE CODE, SYSTEM CAPABILITIES DOCUMEN

4. AUTHORITY (Data Acquisition Document No.)

DI-IPSC-82134

5. CONTRACT REFERENCE

SOW Paragraph 4.3

6. REQUIRING OFFICE

SEA 04

7. DD 250 REQ

LT

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

SEE REMARKS

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

30 DARP

13. DATE OF SUBSEQUENT

SUBMISSION

30 DARP

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

BLOCK 9: Distribution Statement D: Distribution authorized to Department of Defense and U.S. DoD Contractors only. Other requests for this documents shall be referred to NAVSEA 04Z, Naval Sea Systems Command, WNYD, Washington, DC 20376.

BLOCK 10: AFTER EACH SOFTWARE CODE RELEASE

The submission shall consist of:

1. Updated Data Dictionary (PDF format)

2. Updated TSM and ETC System Capabilities Document (PDF format)

3. Updated TSM Operations and Maintenance Plan (PDF format)

4. Source code, installation notes and installation instructions via compact disc or other electronic media approved by the program manager.

COR, SEA 04Z 0 1 1

15.TOTAL 1 1

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

Varnana Beuria

H. SIGNATURE I. APPROVED BY

Jason Jones

J. SIGNATURE

BEURIA.VARNA

NA.1596453739

Digitally signed by

BEURIA.VARNANA.1596453739

Date: 2025.02.12 09:46:55 -05'00'

JONES.JASON.TO

MAR.1407195953

Digitally signed by

JONES.JASON.TOMAR.1407195953

Date: 2025.02.12 10:11:49 -05'00'

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DoDM 5010.12 for detailed instructions.)

DD FORM 1423, FEB 2024 Page 2 of 2

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 (e.g., Mission Design Series (MDS) designator).

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Name of preparer of CDRL.

Item H. Date CDRL was prepared and signature of preparer of CDRL.

Item I. Name of CDRL approval authority.

Item J. Date CDRL was approved and signature of CDRL approval authority.

Item 1. See DFARS Subpart 204.71 for proper numbering. To add or delete additional data items, point and click the plus or minus sign to the right of Block J.

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. Identify only one Data Acquisition Document No. If a single work task generates more than one deliverable data product, prepare a separate data item for each deliverable data product.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work/Performance Work Statement 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 and computer software, specify the contractor's requirement to mark the appropriate distribution statement on the technical data or computer software (ref. DoDI 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.

Identify for which data item additional remarks are provided. When tailoring the Data Acquisition Document invoked in Item 4, identify which portions of that Document are being tailored.

Identify any referenced attachments to the form. Attachments can be added using the button at the bottom of page 1.

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 rights to use the data shall be governed by the pertinent provisions of the contract.

DATA ITEM DESCRIPTION

Title: SOFTWARE SUSTAINABILITY PACKAGE

Number: DI-IPSC-82134 Approval Date: 20170615 AMSC Number: N9821 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: AS Project Number: IPSC-2017-003 Applicable Forms: N/A

Use/relationship: The Software Sustainability Package (SSP) contains the superset of source code, design details, models, algorithms, processes, flow charts, formulae and related materials that would allow the software to be reproduced, recreated or recompiled, as needed for sustainment by non-developer(s) or the original equipment manufacturer (OEM). This includes all executable software, des ign models , source files, and software sustainment information, including "as built" design information and compilation, build, and modification procedures, for each Computer Software Configuration Item (CSCI).

The SSP is to be used in conjunction with a Contract Line Item Numbers (CLINs) or CLIN Options to procure the executable software and source files for a CSCI and is the primary software sustainment document for each CSCI which could be maintained by non-OEM(s). The SSP is the line item description of the data and products that are to be procured through the CLINs.

Note: Different organizations have different policies for ordering delivery of software. These policies should be determined before applying this Data Item Description (DID).

This DID is used when the developer is tasked, either by CLIN, Statement of Work (SOW) or Statement of Objectives (SOO), to prepare executable software, source files, "as built" CSCI design, hardware and related sustainment information for delivery.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract SOW.

Requirements:

1. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices and revisions, shall be as specified in the contract.

2. Format. The SSP shall be in contractor format. The SSP shall adhere to the format described under Content.

3. Content. The specification shall contain the following items:

DI-IPSC-82134

3.1 Scope

a. A detailed and complete identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).

b. Briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and sustainment agencies; identify current and planned operating sites.

c. Describe the relationship to other project management plans.

3.2 Provide a detailed listing of source files, including source code in its original language, batch files, build scripts, data files, and libraries necessary to successfully regenerate the software product from scratch and to be able to successfully execute the regenerated software product on the target hardware without any involvement from the software

OEM.

3.3 Identify and describe in detail the hardware and associated documentation needed to sustain the deliverable software. This hardware may include computers, peripherals, hardware simulators, stimulators, emulators, diagnostic equipment, programming equipment (e.g. erasure of software from, loading software onto, and verification of software on a hardware device), firmware devices, and non-computer equipment. The following shall be included in the description:

a. Specific models, versions and configurations.

b. Operator manuals or instructions for each item, as applicable.

c. Whether the item is furnished by the developer, by the OEM, as GFE/GFI, etc. and whether the item is still supported by that particular organization. If the item is no longer supported or manufactured, a plan for procuring replacements (e.g. new source of supply) should be identified.

d. Information about licensing, data rights, etc.

e. Security and privacy considerations, limitations, or any other items of interest.

f. Information about the operational and environmental limits to which the item may be subjected and maintain satisfactory operation.

3.4 Provide a detailed description of the complete software development environment (SDE) and software test environment. The following shall be included in the description:

a. All software tools (Cybersecurity, compilers, linkers, loaders, debuggers, scripts, etc).

b. Procedural documentation.

c. Operational data and settings, such as compiler flags and environmental variables required to regenerate and maintain the software product.

3.5 Provide a detailed listing and description of automated test tools associated with the software product.

DI-IPSC-82134

3.6 As an appendix to this document or as a standalone document, identify, detail and list all unit, component and CSCI level test procedures and all test scripts.

3.7 As an appendix to this document or as a standalone document, identify, detail and list all CSCI, CSC, CSU and system integration procedures; hardware/software integration procedures; and instructions for use of integration procedures.

3.8 As an appendix to this document or as a standalone document, identify, detail and list all system development testing suites such as System Integration Lab (SIL) subsystems, and data acquisition, data reduction, and data analysis tools, along with all custom test equipment.

3.9 Provide a detailed description of problem tracking, software configuration management, and data management tools and licenses.

3.10 Provide a detailed description of requirements, design, source code and processes for devices and software which load software into the subsystems.

3.11 Provide a detailed description of licenses, including commercial and open source, which are utilized at the SDE, software test environment, and SIL.

3.12 As an appendix to this document identify and detail all software architecture artifacts, including Unified Modeling Language (UML) diagrams, UML modeling and executable code, and data models.

3.13 As an appendix to this document identify and detail training materials to teach the sustainers the complexities of the systems and the interfaces with other systems.

3.14 Identify and detail other items required for software development and sustainment that are not previously requested or identified in the previous sections.

4. Notes. This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document.

5. Appendixes. Appendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling.

Appendixes shall be lettered alphabetically (A, B, etc.).

End of DI-IPSC-82134

PREVIOUS EDITION MAY BE USED.

DD FORM 1423, FEB 2024 Page 1 of 2

UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

TBD

B. EXHIBIT

A

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

TSM IT & ENG SPT SERVICES

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

SAIC

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

CONTRACTOR'S PROGRESS, STATUS & MANAGEMENT REPO

3. SUBTITLE

PROGRAM STATUS REPORT

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81864

5. CONTRACT REFERENCE

SOW Paragraph 4.6

6. REQUIRING OFFICE

SEA 04

7. DD 250 REQ

LT

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

D

10. FREQUENCY

MONTHLY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

14 DARP

13. DATE OF SUBSEQUENT

SUBMISSION

14 DARP

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

BLOCK 9: Distribution Statement D: Distribution authorized to Department of Defense and U.S. DoD Contractors only. Other requests for this documents shall be referred to NAVSEA 04Z, Naval Sea Systems Command, WNYD, Washington, DC 20376.

The report shall consist of, at a minimum, the following:

- Work accomplished for the period

- Work planned for the next period

- Problems encountered or anticipated with recommendations

- Travel

- Task Area Self-Assessment

- Costs (Labor & ODC) and man-hours expended at the CLIN to provide auditable details for payment approval

- Funding burn rate chart at the CLIN level for the Period of Performance

- ODC expenditure details for the period

- Help Desk status report as indicated in the SOW.

COR, SEA 04Z 0 1 1

15.TOTAL 1 1

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

Varnana Beuria

H. SIGNATURE I. APPROVED BY

Jason Jones

J. SIGNATURE

BEURIA.VARNA

NA.1596453739

Digitally signed by

BEURIA.VARNANA.1596453739

Date: 2025.02.12 09:47:30 -05'00'

JONES.JASON.TO

MAR.1407195953

Digitally signed by

JONES.JASON.TOMAR.1407195953

Date: 2025.02.12 10:14:09 -05'00'

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DoDM 5010.12 for detailed instructions.)

DD FORM 1423, FEB 2024 Page 2 of 2

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 (e.g., Mission Design Series (MDS) designator).

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Name of preparer of CDRL.

Item H. Date CDRL was prepared and signature of preparer of CDRL.

Item I. Name of CDRL approval authority.

Item J. Date CDRL was approved and signature of CDRL approval authority.

Item 1. See DFARS Subpart 204.71 for proper numbering. To add or delete additional data items, point and click the plus or minus sign to the right of Block J.

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. Identify only one Data Acquisition Document No. If a single work task generates more than one deliverable data product, prepare a separate data item for each deliverable data product.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work/Performance Work Statement 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 and computer software, specify the contractor's requirement to mark the appropriate distribution statement on the technical data or computer software (ref. DoDI 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.

Identify for which data item additional remarks are provided. When tailoring the Data Acquisition Document invoked in Item 4, identify which portions of that Document are being tailored.

Identify any referenced attachments to the form. Attachments can be added using the button at the bottom of page 1.

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 rights to use the data shall be governed by the pertinent provisions of the contract.

DATA ITEM DESCRIPTION

Number: DI-MGMT-81864 Approval Date: 20120628 AMSC Number: N9268 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: N/A Office of Primary Responsibility: SH/NSWCDD Applicable Forms: N/A

Use/Relationship: This report indicates the progress of work and the status of the program and of the assigned tasks, reports costs, identifies and informs of existing or potential problem areas.

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

2. This DID may be applied in any contract and during any program phase.

Requirements:

1.

2.

describe work accomplished in terms of technical accomplishments and expenditure data for each project area/task/technical instruction funded under the contract.

3. Content. The Report shall contain a title page identifying the following:

a.

b. Name and telephone number of preparer of the report;

c. Contract number;

d. Nomenclature of the system or program;

e. Date of the report;

f. Period covered by the report;

g. The title of the report;

h. Either the serial number of the report or the Contract Data Requirements List (CDRL) sequence number;

i. The security classification;

j. The name of the issuing Government activity.

3.1 The report shall also contain the following sections:

3.1.1 Section - 1 Work Summary. A brief summary of all funded tasks/projects/technical instructions under the contract. The summary shall identify Task Order period (Base, Option 1, etc.) and shall include the following:

a. Project name;

b. TI number (if applicable);

DI-MGMT-81864

c. Funded amount;

d. Expenditures to date;

e. Funding balance.

3.1.1.2 The report shall include tables that demonstrate:

a. ceiling hours;

b. funded hours;

c. current and cumulative hours separately identifying regular hours from UT/TTA hours) charged to the labor category for current and completed CLINs;

d. subtotals for key and non-key categories.

3.1.2 Section 2 - Invoice Information shall identify the following:

3.1.2.1 Direct labor. The report shall identify:

a. current and cumulative expenditures (both labor hours and dollars) invoiced by Cost Center where charges originated;

b. totals for current and cumulative invoiced amounts by cost center.

3.1.2.2 Indirects. The report shall identify:

a. indirect rate being invoiced with applicable Cost Center as well as current and cumulative dollar amounts by Cost Center;

b. total current and cumulative indirect costs.

3.1.2.3 Subcontractors/Consultants. The report shall include copies of

3.1.2.4 Fixed Fee. The report shall specify:

a. each fee rate applied, together with current and cumulative dollar amounts;

b. the base to which each fee rate was applied.

3.1.2.5 Other Direct Costs. The report shall include:

a. list of expenses by category (airfare, per diem, supplies, etc.);

b. current and cumulative expenditures for each category.

3.1.2.6 Total Expenditures. The report shall include total expenditures compared to those invoiced for the same period and differences explained.

3.1.2.7 Current CLIN. The report shall identify the current CLIN being performed and its period of performance.

3.1.2.8 The report shall contain the current CLIN modifications and shall be listed by number, date issued and description.

3.1.2.9 The report shall include a table that identifies the following:

a. technical instructions/funded projects/work areas by number (where applicable);

b. date issued;

c. description;

d. amount funded;

e. total expenditures;

g. funding balance;

h. total invoiced to date;

j. grand total.

3.1.3 Section 3 - Detailed Information By Project/Work Area/Technical Instruction. This section shall contain:

a. Description of the progress made against milestones during the reporting period. Specifically address the value-added tasks performed by the prime contractor when work is performed by a subcontractor; clearly identify the key and non-key personnel performing the tasks described.

b. Identification of problem areas affecting technical, scheduling or costs elements, with background and any recommendations for solutions beyond the scope of the contract. Specifically, address results, positive or negative, obtained related to previously-identified program areas, with conclusions and recommendations for solutions.

c. Whether the task is on schedule, ahead of schedule, or behind schedule. Discuss what steps are being or will be taken to complete all requirements on time if possible, or provide a proposed revised schedule based on best current estimates if behind schedule.

d. The status of all assigned deliverables, including title, CDRL number, due date, date delivered, Contractor point of contact and description or title of deliverable(s). The report for each contract period shall include a cumulative list of all deliverable items provided.

e. A table of approved personnel identifying labor category, key or non-key, individual's name, employer, fully burdened labor rate, location (on-site/off-site), date resume submitted, date resume approved, and date removed shall be included. If a resume was submitted as a replacement for a Key Person approved at time of award, the name of the individual being replaced shall also be provided.

f. Include current and cumulative expenditures of both hours and dollars. Separately show expenditures by CLIN and SubCLIN (labor and ODC). Identify the amount funded and compute a funding balance. Present the current and cumulative total percentage of ODCs to labor;

g. Include graphs showing cumulative expenditures of both hours and dollars. Line graphs shall show planned cumulative expenditures as well as cumulative funded level(s). Include numerical values for all points graphed; quantities of labor hours shall show rounded to the nearest hour;

h. Include the names of all personnel charging. Organize these data by labor category, fully burdened labor rate (e.g. fee and prime pass-through, where applicable), and show current and cumulative hours charged for each individual. Separately show uncompensated hours/total time accounting (TTA) hours worked (if applicable). Labor categories shall be identified as to whether they are key or non-key categories. Subtotals shall be provided for key and non-key categories as well as total current and cumulative hours. Provide average hourly rates (fully burdened) for each labor category (applicable only for cost plus incentive fee (CPIF) contracts). These data shall include subcontractor/consultant hours in appropriate labor categories;

i. Include spend rates compared to average bid rate averages.

Any variation of actual-to-bid rate averages greater than 10% shall be addressed; Fully burdened rates (e.g. fee and prime pass-through, where applicable) that exceed $260K shall be addressed.

j. Identify of all items charged. Include description of item, quantity, purpose, vendor, unit price, extended price and disposition;

k. Identify all travel direct-charged during the period, for each:

(1) Destination

(2) purpose of trip

(3) number of travelers

(4) length of trip

(5) estimated cost of the trip;

l. Identify any new subcontractors approved during the reporting period and any proposed subcontractors/consultants for the next reporting period. Their capability set and areas of expertise shall be thoroughly addressed.

m. Record of significant telephone calls and any commitments made by telephone shall be included;

n. Plans and recommendations for activities during the next reporting period;

o. Appendixes for any necessary tables, references, photographs, illustrations, and charts.

4. END OF DI-MGMT-81864.