B_FA880723R0005_Exhibit B - CDRL.pdf

EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST (CDRL)

TO THE PERFORMANCE WORK STATEMENT

FOR

MOBILE USER OBJECTIVE SYSTEM (MUOS)

SERVICE LIFE EXTENSION (SLE)

Phase One Risk Reduction and Early Design

Contract #: FA8807-23-R-0005

24 MARCH 2023

Version 1.0

Prepared By:

United States Space Force

Space Systems Command (SSC) Acquisition Delta (CGN) Narrowband SATCOM

4301 Pacific Highway San Diego, California 92110-3127

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 2 of 29

[This page intentionally blank]

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 3 of 29

Revision APPROVAL DATE DESCRIPTION OF CHANGE MODIFICATION (P000) NO.

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 4 of 29

GENERAL REQUIREMENTS

Acceptance of CDRLs does not constitute authorization for any contract changes.

1. Classified, restricted, or proprietary information shall be isolated, by category, and submitted on separate media.

2. Questions pertaining to a CDRL and any particular items should generally be directed to SSC/CGN. Request for deviation from the written instruction should be directed to the SSC/CGN Contracting Officer Representative (COR).

3. All CDRL deliverables shall bear the contract and Data Item Number.

4. All “Day(s)” references in the CDRL are calendar days, unless otherwise specified.

5. Preparation and format of all data may be in accordance with best commercial practice; however, the technical requirements of the data must be satisfied. Other forms of data submission (such as that used to satisfy DIDs used for Government contracts) are acceptable, providing that the technical requirements of the data are satisfied.

6. All CDRLs requiring a Classified Annex shall be delivered in accordance with DD-254 instructions and referenced in the corresponding unclassified CDRL deliverable.

7. Document data:

A. Include a cover page that at least identifies the following:

• Program Name and Nomenclature

• Title with Revision

• Contract Data Requirement List (CDRL) Number

• Contract Number

• Date

• Program Manager’s name and telephone number

• Prepared For

• Prepared By

B. Classification markings in accordance with DD-254 and Classification Guide

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 5 of 29 ted Master Schedule

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. 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

B

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

MUOS SLE SPACE

E. CONTRACT/PR NO.

FA880723R0005

F. CONTRACTOR

1. DATA ITEM NO.

B002

2. TITLE OF DATA ITEM

STATUS REPORT

3. SUBTITLE

MONTHLY STATUS REPORT (MSR)

17. PRICE GROUP

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-80368A/T

5. CONTRACT REFERENCE

SOW PARA 7.1.1

6. REQUIRING OFFICE

SSC/CGN

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

BLK 16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

ASREQ

13. DATE IF SUBSEQUENT

SUBMISSION

BLK 16

Draft Final

16. REMARKS SSC/CGN 1

Requirements: Paragraph 3.

Contents:

a. DID Section 3.2.1.a: Delete and replace with: “A statement as to whether or not the program/project/task is on schedule; if not, the effort planned to meet the schedule shall be indicated. Include a milestone chart in linear time phasing covering the major program activities (e.g., SRR, SFR, EDR, major events, etc.), detailing baseline date, forecast date, schedule margin baselined and margin used, if applicable. Include updated schedule sheets and percent complete of each task.”

b. DID Section 3.2.1.h: Delete and replace with: “Equipment/facilities chart: A chart depicting major government furnished equipment (GFE) and the date and duration that such GFE and facilities are required.”

c. DID Section 3.2.3: Itemized man-hours and costs. Add the following: “A cost chart depicting by month the estimated program spend forecast per fiscal year.”

d. DID Section 3.2.4: Contract deliveries status: renumber to 3.2.7

e. Add DID Section 3.2.4: “Technical Performance: Include a TPM status chart and SWaP by subsystem chart (include margins vs. time).”

f. DID Section 3.2.5: Report preparer: renumber to 3.2.8

g. Add DID Section 3.2.5: “Program risk status: Discuss top 10 program risk status using a 5x5 matrix. Provide risk mitigation plans and the results of steps taken.”

h. Add DID Section 3.2.6: “Organization data. Submit with first delivery and submit updates only when required. 1. Program organization chart: A chart showing the structure of the program organization by title and name. Identify the program office, support contractors, and major subcontractors. 2. Program/functional organization relationship chart: A chart showing the relationship of the program functions to the functional organizations indicating lines of authority and communications.”

BLOCK 8:

a. Government approval if no comment received within 10 WD after submission.

b. Government comment or rejection will be provided by Contractual Document Action (CDA).

Resubmit within 10 WD after receipt of comments or with next submission if CDA allows.

BLOCKs 10- 13:

a. Continue monthly submissions upon option exercise, 15 WD after close of Contractor’s first full monthly accounting period.

15. TOTAL 1

G. PREPARED BY

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

J. DATE

24 MAR 2023

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 6 of 29

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the

B. EXHIBIT

B

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

MUOS SLE SPACE

E. CONTRACT/PR NO.

B003

2. TITLE OF DATA ITEM

STATUS REPORT

3. SUBTITLE

INTEGRATED MASTER SCHEDULE (IMS)

DI-MGMT-80368A/T

5. CONTRACT REFERENCE

SOW PARA 7.1.1

6. REQUIRING OFFICE

SSC/CGN

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

BLK 16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

. ADDRESSEE

b. COPIES

8. APP CODE

N/A

SUBMISSION

16. REMARKS SSC/CGN 1 1

Requirements: Paragraph 3. Contents:

a. DID Section 3.2.1.a Delete and replace with: “A statement as to whether or not the program/project/task is on schedule; if not, the effort planned to meet the schedule shall be indicated. Include a milestone chart in linear time phasing covering the major program activities (e.g., SRR, SFR, EDR, major events, etc.), detailing baseline date, forecast date, schedule margin baselined and margin used, if applicable. Include updated schedule sheets and percent complete of each task.”

b. DID Section 3.2.1.b-i Delete

c. DID Section 3.2.2-3.2.4 Delete

d. DID Section 3.2.5 Report preparer: renumber to 3.2.2

e. DID Section 3.3 Delete and replace with: "Appendix. The appendix shall include an Integrated Master Schedule (IMS)"

f. Add DID Section 3.3.1 "Format. The IMS shall be submitted in Microsoft Project (MSP) 2016 (or MSP version format compatible with MSP 2016) electronic file format."

g. Add DID Section 3.3.2 "IMS Requirements"

h. Add DID Section 3.3.2.1 "Content Required. The IMS shall include, at a minimum, discrete tasks/activities, consistent with all authorized work, and relationships necessary for successful contract completion. Subcontractor discrete work shall be incorporated as tasks within the prime IMS at a level necessary for a realistic critical path. The IMS is a single integrated network that also contains significant external interfaces, Government furnished equipment / information / property and relationship dependencies for the entire contractual effort.

i. Add DID Section 3.3.2.2 "IMS Content Elements. The IMS shall contain the contract milestones, accomplishments, criteria, discrete tasks/activities, work packages and planning packages, as applicable, from contract award to contract completion.

- The IMS shall be an integrated, logically driven network-based schedule that is vertically and horizontally traceable.

- The IMS shall have traceability to the WBS, and SOW.

- The IMS shall contain contractual milestones and descriptions and shall display summary, intermediate, and detailed schedules.

- The IMS shall include fields and data that enable access to the information by product and organizational lines.

- The IMS shall contain all calendars that define working and nonworking time periods or other information that may impact the schedule."

CONTINUED ON PAGE 2

15. TOTAL 1 1

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 7 of 29

A. CONTRACT LINE ITEM NO.

B. EXHIBIT

B

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

MUOS SLE SPACE

E. CONTRACT/PR NO.

16. REMARKS

PAGE 2 OF 3 – INTEGRATED MASTER SCHEDULE (CONTINUED)

j. Add DID Section 3.3.2.2.1 "Contract Milestones. Key programmatic events which represent progress and completion of the contract."

k. Add DID Section 3.3.2.2.2 "Summary Master Schedule. A top-level schedule of key tasks/activities and milestones at the summary level which can be sorted by the WBS (if applicable). It shall be a vertically integrated roll up of the intermediate and detailed levels within the IMS."

l. Add DID Section 3.3.2.2.3 "Intermediate Schedules. Mid-level contract schedules that include key tasks/activities, milestones, and all associated accomplishments as shown in the summary master schedule. The WBS elements (as applicable) are traceable 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 vertically integrated roll ups of the detailed level schedules."

m. Add DID Section 3.3.2.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 discrete tasks/activities, work packages and planning packages necessary to create a networked schedule capable of identifying a valid critical path."

n. Add DID Section 3.3.2.3 "IMS Detailed Elements. The IMS, at a minimum, shall include the following:"

o. Add DID Section 3.3.2.3.1 "Task/Activity. An element of work with duration."

p. Add DID Section 3.3.2.3.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."

q. Add DID Section 3.3.2.3.3 "Duration. The length of time estimated or realized to accomplish a task/activity."

r. Add DID Section 3.3.2.3.4 "Schedule Percent Complete. Schedule percent complete is a time-based status calculated by the schedule tool without regard to task scope accomplishment."

s. Add DID Section 3.3.2.3.5 "Task/Activity and Milestone Descriptions. These are descriptive titles that are concise, complete, and clearly identify the work effort being accomplished. The task/activity title shall reflect the scope, its output (i.e., deliverable) and its place within the IMS architecture so that the content can be understood without the subproject task structure, if applicable. Abbreviations may be used to shorten the descriptive titles. The title for a task shall be unique in respect to other titles in the same IMS."

t. Add DID Section 3.3.2.3.6 "Relationships/Dependencies. Identify how predecessor and successor tasks/activities and milestones are logically linked. All non-constrained discrete tasks/activities/milestones, except the start and end of the contract or interim delivery, shall have at least one predecessor and successor."

u. Add DID Section 3.3.2.3.7 "Total Float/Slack. The amount of time a task/activity or milestone forecast finish date can slip before delaying contract completion or constraint date."

v. Add DID Section 3.3.2.3.8 "Driving Path. The longest sequence of discrete tasks/activities from time-now to a selected interim contract milestone. Discrete tasks/activities on the driving path have the least amount of total float/slack to the interim contract milestone. If a task on a driving path slips, the interim contract milestone will slip. Driving path may not be part of the contract critical path. The Government may specify which driving path is currently reportable. Without Government direction, the contractor reports the driving path to the next major event, at a minimum."

w. Add DID Section 3.3.2.3.9 "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. Activities that contain “0” or negative total float are not by default the critical path. The critical path calculation is based on relationships, lead/lag times, durations, constraints, and status. Excessive constraints and incomplete, incorrect, or overly constrained logic shall be avoided because they can skew the critical path."

x. Add DID Section 3.3.2.3.10 "Current Schedule. The IMS shall reflect status and forecast discrete activities. Forecast start and forecast finish dates, shall not be earlier than the status date."

y. Add DID Section 3.3.2.3.11 “Baseline Schedule. The IMS shall have baseline dates for all tasks within the PMB and those dates shall be consistent with the start and finish of the cost baseline. The baseline is typically set equal to the current schedule early dates at the time of the baseline establishment when change control is initiated.”

z. Add DID Section 3.3.2.3.12 “Baseline Schedule Changes. Changes to the baseline schedule shall be made in accordance with the contractor’s EVM process when applicable. In the event that the IMS is implemented without an EVM requirement, the change shall be made in accordance with the contractor’s schedule change management 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.”

CONTINUED ON PAGE 3

SEE PAGE 1

H. DATE

24 MAR 2023

I. APPROVED BY

SEE PAGE 1

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 8 of 29

(1 Data Item)

A. CONTRACT LINE ITEM NO.

B. EXHIBIT

B

E. CONTRACT/PR NO.

PAGE 3 OF 3 – INTEGRATED MASTER SCHEDULE (CONTINUED)

aa. Add DID Section 3.3.2.3.13 “Schedule Progress. The IMS shall reflect actual progress and maintain accurate start and finish dates for all tasks/activities and milestones. The requirements for reflecting schedule progress are as follows:

- Actual start and actual finish dates shall be recorded in the IMS. The Actual start and actual finish dates shall not be later than the status date.

- The progress line is the date on which the schedule is statused, also known as “time-now,” “data date,” or “status date.” All tasks/activities shall be progressed to the status date of the IMS.

- Forecast start and forecast finish dates shall not be earlier than the status date.”

ab. Add DID Section 3.3.2.3.14 “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.”

ac. Add DID Section 3.3.2.3.15 “External Dependencies. As agreed to by the Government and contractor, the IMS shall identify significant external dependencies that involve a relationship or interface with external organizations, including Government-furnished items (e.g., decisions, facilities, equipment, information, data) as defined in the contract. The required or expected delivery dates shall also be identified in the IMS. External dependencies shall be logically linked in the schedule to the appropriate IMS tasks.”

ad. Add DID Section 3.3.2.3.16 “Lead/Lag. An interval of time that must occur between a predecessor and successor task/activity or milestone. Documenting the purpose of each lead/lag within the IMS (i.e. in a user defined field) to facilitate the ease of IMS status and analysis is required. Since negative time is not demonstrable, leads are discouraged. Lead/lag shall not be used to manipulate float/slack or to artificially constrain the tasks/activities. If a coding field is used for justification of leads/lags, the terms shall be defined in the data dictionary”

ae. Add DID Section 3.3.2.3.17 “Constraints. Constraints are limits applied to network start and finish dates (e.g., “Finish No Later Than,” “Finish On or Before”).

Constraints shall be minimized if they affect “late” dates or both “late and early” dates. The constraints that require justification include:

- All constraints that affect “late” dates or both “late and early” dates as defined by the schedule tool.

- All constraints that affect “early” dates beyond 20 working days from the current status period.

Constraints requiring justification shall be justified in an associated notes field provided within the scheduling software application. If a coding field is used for justification of constraints the definitions shall be defined in the data dictionary.”

af. Add DID Section 3.3.2.3.18 “Schedule Margin. Schedule margin is an optional technique used for insight and management of schedule risks. Schedule margin is represented by a task or tasks within the IMS with no assigned resources (budget or ETC) and is established as part of the baseline. Schedule margin shall be under the control of the contractor’s program manager. Schedule margin shall only be placed as the last task before key contractual events, significant logical integration/test milestones, end item deliverables, or contract completion. Schedule margin is associated with schedule risk as part of a formal risk management plan. Schedule margin may be directly or indirectly connected to discrete predecessor and successor activities and fall on critical paths. All schedule margin tasks shall be clearly and consistently identifiable. Significant changes to the status of schedule margin tasks and impacts to the program’s primary critical path, if any, shall be discussed in the Summary Report.”

ag. Add DID Section 3.3.2.3.19 “Task/Activity Codes and Data Dictionary. This is a list of all contractor defined fields, definitions, and code structures in the IMS.

This list shall define all of the required fields in the IMS. The list shall be provided to the procuring activity upon initial submission of the IMS and any subsequent change to the dictionary.”

BLOCKs 10- 13:

a. Continue monthly submission upon option exercise, 15 WD after close of Contractor’s first full monthly accounting period.

SEE PAGE 1

H. DATE

24 MAR 2023

I. APPROVED BY

SEE PAGE 1

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 9 of 29

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract PR No. listed in Block E.

B. EXHIBIT

B

E. CONTRACT/PR NO.

B005

2. TITLE OF DATA ITEM

RISK MANAGEMENT STATUS REPORT

3. SUBTITLE

DI-MGMT-81809/T

5. CONTRACT REFERENCE

SOW PARA 7.1.1

6. REQUIRING OFFICE

SSC/CGN

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

BLK 16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

SUBMISSION

Requirements: Paragraph 2.

Content:

a. Replace DID Section 2.4 with: “The report shall contain a narrative briefly describing the risk, title, type (Performance, Schedule, or Cost), root cause, current mitigations, and planned mitigations efforts identified, along with critical dates (date risk will be realized, and estimated start/end dates of risk reduction activities).”

b. Add DID Section 2.5: “The report shall define the criteria utilized for estimating the likelihood and consequence.”

BLOCKS 10-13:

a. Submit NLT 6 months after option exercise.

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 10 of 29

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the

B. EXHIBIT

B

TDP TM OTHER FINANCIAL

E. CONTRACT/PR NO.

B006

2. TITLE OF DATA ITEM

COST & SOFTWARE DATA REPORTING

3. SUBTITLE

SOFTWARE RESOURCES DATA REPORT -

DEVELOPMENT (SRDR)

DI-MGMT-82035A

5. CONTRACT REFERENCE

SOW PARA 7.1.2

6. REQUIRING OFFICE

SSC/CGN

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

BLK 16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

SUBMISSION

BLOCK 4: Prepare in electronic format in accordance with the detailed instructions in Data Item Description DI-MGMT-82035A. Each SRDR format contains a Part 1 and a Part 2. Part 1 is required to be submitted in eXtensible Markup Language (XML) format when cPet functionality is available to generate an XML file from the completed Excel forms. Part 2 must be submitted in Excel format only. Until the cPet functionality is available to generate the XML format, both Part 1 and Part 2 must be submitted in Excel format.

All reports must be submitted electronically using the Cost Assessment Data Enterprise (CADE) CSDR Submit Review System. Data submitters must register through the CADE website (http://cade.osd.mil) and possess DoD-approved ECA digital certificate of DoD-issued CAC to obtain a CADE Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the CADE Portal and requesting a CSDR Submitter user role. After the registration information has been verified, CAPE shall authorize the user account and requested roles. All CADE portal accounts need to be renewed at least annually.

Prime contractors are responsible for flowing down CSDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds specified in DoDI 5000.73, or as required by the Cost Working-Group Integrated Product Team (CWIPT). This includes requiring subcontractors to electronically report directly to the CADE Portal using the CSDR Submit- Review System. The prime contractor shall work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR Plans for submission to the DCARC for OSD Deputy Director Cost Assessment (DDCA) approval.

The prime contractor and reporting subcontractors shall allocate resources for Integrated Baseline Review (IBR) and Verification & Validation (V&V) support of SRDRs as required by the Government to ensure accurate and consistent software data reporting. The reviews will be conducted in accordance with each SRDR submission.

The prime contractor and supporting subcontractors shall utilize the Government-approved version of the University of Southern California (USC) Center for Systems and Software Engineering (CSSE) Unified Code Counter (UCC), known as the UCC-G, to obtain a set of standardized code counts that reflect logical size, as opposed to physical, non-commented, etc. The Government reserves the right to ask the prime contractor and reporting subcontractors to provide the UCC and Diff Tool output files for software by Source Lines of Code (SLOC) by Computer Software Configuration Item (CSCI) for the entire program. Instructions for downloading the UCC-G are available for download from the CADE website at https://cade.osd.mil/tools/unifiedcodecounter.

CADE PORTAL 1

15. TOTAL 2

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 11 of 29

A. CONTRACT LINE ITEM NO.

B. EXHIBIT

B

C. CATEGORY:

TDP TM OTHER FINANCIAL

D. SYSTEM/ITEM

MUOS SLE SPACE

E. CONTRACT/PR NO.

PAGE 2 OF 2 – SRDR (CONTINUED)

Technical data will be available to support contractors who work for the OSD or the services. Access to the data is granted only while the contractor is supporting a legitimate DoD contract, the contractor has a need to know, and a Non-Disclosure Agreement has been signed with the Government organization the contractor supports.

The staff hour “estimate at complete” is for completion of all Phase 1 efforts under this contract.

BLOCKS 10-14: To be submitted at frequencies specified in the DDCA-approved contract CSDR Plan (DD Form 2794), provided in the Bidder’s Library The “As Of Dates” and “Due Dates” are notional. The CSDR Plan uses the submission event names as the driving mechanism for the submittal of reports, not the “As Of Date”. In the event of a schedule slip, notify SSC/CGN that a date change is needed. SSC CGN will submit a date change request with supporting documentation in the CADE system for approval. An updated DDCA-approved CSDR Plan will not be issued for revisions based solely on date changes.

Reports are required at event driven and annual report frequency. If the annual reports are due within 60 days of the event driven reports, the Contractor may request the annual reports to be waived. Annual reports can be waived at the discretion of the CWIPT.

Allow 30 days for Government (SSC/CGN and OSD DCARC) comment. Allow 15 days for Contractor to incorporate Government comments and resubmit.

Additional revisions may be required. Delivery not complete until Government acceptance.

G. PREPARED BY

SEE PAGE 1

H. DATE

24 MAR 2023

I. APPROVED BY

SEE PAGE 1

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 12 of 29

A006 Software Resources Data Report (SRDR) –

(1 Data Item)

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the

B. EXHIBIT

B

C. CATEGORY:

TDP TM OTHER FINANCIAL

D. SYSTEM/ITEM

MUOS SLE SPACE

E. CONTRACT/PR NO.

B007

2. TITLE OF DATA ITEM

QUANTITY DATA REPORT

DI-MGMT-82164

5. CONTRACT REFERENCE

SOW PARA 7.1.2

6. REQUIRING OFFICE

SSC/CGN

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

BLK 16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

SUBMISSION

Description DI-MGMT-82164 and the OSD CAPE Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID, DI-MGMT-82164, is available from the Cost Assessment Data Enterprise (CADE) website at https://cade.osd.mil/policy/dids. The CSDR Plan is included as a contract attachment. The Quantity Data Report shall be delivered in either a) MS Excel (.xlsx) or comma separated values (.csv) in the contractor’s format of choosing, so long as it fulfills the requirements of DD Form 2794 and is in accordance with the Quantity Data Report DID or b) JavaScript Object Notation (JSON) as described in the Quantity Data Report Format Specification (FFS) and Data Exchange Instructions (DEI) reference in the Quantity Data Report DID Requirements Section 2.

All reports must be submitted electronically using the Cost Assessment Data Enterprise (CADE) CSDR Submit Review System. Data submitters must register through the CADE website (http://cade.osd.mil) and possess DoD-approved ECA digital certificate or DoD-issued CAC to obtain a CADE Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the CADE Portal and requesting a CSDR Submitter user role. After the registration information has been verified, CAPE shall authorize the user account and requested roles. All CADE portal accounts need to be renewed at least annually.

Prime contractors are responsible for flowing down CSDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds specified in DoDI 5000.73, or as required by the Cost Working-Group Integrated Product Team (CWIPT). This includes requiring subcontractors to electronically report directly to the CADE Portal using the CSDR Submit- Review System. The prime contractor shall work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR Plans for submission to the DCARC for OSD Deputy Director Cost Assessment (DDCA) approval.

BLOCKS 10-14: To be submitted at frequencies specified in the DDCA-approved contract CSDR Plan (DD Form 2794), provided in the Bidder’s Library. The “As Of Dates” and “Due Dates” are notional. The CSDR Plan uses the submission event names as the driving mechanism for the submittal of reports, not the “As Of Date”. In the event of a schedule slip, notify SSC CGN that a date change is needed. SSC CGN will submit a date change request with supporting documentation in the CADE system for approval. An updated DDCA-approved CSDR Plan will not be issued for revisions based solely on date changes.

Reports are required at event driven and annual report frequency. If the annual reports are due within 60 days of the event driven reports, the Contractor may request the annual reports to be waived. Annual reports can be waived at the discretion of the CWIPT.

Allow 30 days for Government (SSC/CGN and OSD DCARC) comment. Allow 15 days for Contractor to incorporate Government comments and resubmit. Additional revisions may be required. Delivery not complete until Government acceptance.

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 13 of 29

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the

B. EXHIBIT

B

C. CATEGORY:

TDP TM OTHER FINANCIAL

D. SYSTEM/ITEM

MUOS SLE SPACE

E. CONTRACT/PR NO.

B008

2. TITLE OF DATA ITEM

COST & HOUR REPORT (FLEXFILE)

DI-FNCL-82162

5. CONTRACT REFERENCE

SOW PARA 7.1.2

6. REQUIRING OFFICE

SSC/CGN

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

BLK 16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK 16

13. DATE IF SUBSEQUENT

SUBMISSION

Description DI-FNCL-82162 and the OSD CAPE Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID, DI-FNCL-82162, is available from the Cost Assessment Data Enterprise (CADE) website at https://cade.osd.mil/policy/dids. The CSDR Plan is provided in the Bidder’s Library.

The FlexFile shall be delivered in either a) MS Excel (.xlsx) or comma separated values (.csv) in the contractor’s format of choosing, so long as it fulfills the requirements of DD Form 2794 and is in accordance with the FlexFile DID or b) JavaScript Object Notation (JSON) as described in the FlexFile Format Specification (FFS) and Data Exchange Instructions (DEI) reference in the FlexFile DID Requirements Section 2.

The following DID tailoring is acceptable: Data Group B – Item 4 – Additional Data Fields #1-#12 are not required.

All reports must be submitted electronically using the Cost Assessment Data Enterprise (CADE) CSDR Submit Review System. Data submitters must register through the CADE website (http://cade.osd.mil) and possess DoD-approved ECA digital certificate or DoD-issued CAC to obtain a CADE Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the CADE Portal and requesting a CSDR Submitter user role. After the registration information has been verified, CAPE shall authorize the user account and requested roles. All CADE portal accounts need to be renewed at least annually.

Prime contractors are responsible for flowing down CSDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds specified in DoDI 5000.73, or as required by the Cost Working-Group Integrated Product Team (CWIPT). This includes requiring subcontractors to electronically report directly to the CADE Portal using the CSDR Submit-Review System. The prime contractor shall work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR Plans for submission to the DCARC for OSD Deputy Director Cost Assessment (DDCA) approval.

The cost and labor hour “estimates at complete” is for completion of all Phase 1 efforts under this contract.

BLOCKS 10-14: To be submitted at frequencies specified in the DDCA-approved contract CSDR Plan (DD Form 2794), provided in the Bidder’s Library. The “As Of Dates” and “Due Dates” are notional. The CSDR Plan uses the submission event names as the driving mechanism for the submittal of reports, not the “As Of Date”. In the event of a schedule slip, notify SSC/CGN that a date change is needed. SSC/CGN will submit a date change request with supporting documentation in the CADE system for approval. An updated DDCA-approved CSDR Plan will not be issued for revisions based solely on date changes.

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 14 of 29

(1 Data Item)

A. CONTRACT LINE ITEM NO.

B. EXHIBIT

B

E. CONTRACT/PR NO.

PAGE 2 OF 2 – COST & HOUR REPORT (FLEXFILE) (CONTINUED)

Reports are required at event driven and annual report frequency. If the annual reports are due within 60 days of the event driven reports, the Contractor may request the annual reports to be waived. Annual reports can be waived at the discretion of the CWIPT.

Allow 30 days for Government (SSC/CGN and OSD DCARC) comment. Allow 15 days for Contractor to incorporate Government comments and resubmit. Additional revisions may be required. Delivery not complete until Government acceptance.

H. DATE

24 MAR 2023

I. APPROVED BY

SEE PAGE 1

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 15 of 29

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the

B. EXHIBIT

B

C. CATEGORY:

TDP TM OTHER FINANCIAL

D. SYSTEM/ITEM

MUOS SLE SPACE

E. CONTRACT/PR NO.

B009

2. TITLE OF DATA ITEM

TECHNICAL DATA REPORT

DI-MGMT-82165

5. CONTRACT REFERENCE

SOW PARA 7.1.2

6. REQUIRING OFFICE

SSC/CGN

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

BLK 16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

SUBMISSION

Description DI-MGMT-82165 and the OSD CAPE Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID, DI-MGMT-82165, is available from the Cost Assessment Data Enterprise (CADE) website at https://cade.osd.mil/policy/dids. The CSDR Plan is provided in the Bidder’s Library. All reports must be submitted electronically using the Cost Assessment Data Enterprise (CADE) CSDR Submit Review System. Only unclassified technical data may be uploaded to the CADE Portal. The Contractor must review all data prior to submission to ensure aggregation of technical data does not warrant a higher classification level.

Data submitters must register through the CADE website (http://cade.osd.mil) and possess DoD-approved ECA digital certificate or DoD-issued CAC to obtain a CADE Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the CADE Portal and requesting a CSDR Submitter user role. After the registration information has been verified, CAPE shall authorize the user account and requested roles. All CADE portal accounts need to be renewed at least annually.

Prime contractors are responsible for flowing down CSDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds specified in DoDI 5000.73, or as required by the Cost Working-Group Integrated Product Team (CWIPT). This includes requiring subcontractors to electronically report directly to the CADE Portal using the CSDR Submit- Review System. The prime contractor shall work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR Plans for submission to the DCARC for OSD Deputy Director Cost Assessment (DDCA) approval.

Technical data will be available to support contractors who work for the OSD or the services.

Access to the data is granted only while the contractor is supporting a legitimate DoD contract, the contractor has a need to know, and a Non-Disclosure Agreement has been signed with the Government organization the contractor supports.

BLOCKS 10-14: To be submitted at frequencies specified in the DDCA-approved contract CSDR Plan (DD Form 2794), provided in the Bidder’s Library, and in the contract task/delivery orders.

The “As Of Dates” and “Due Dates” are notional. The CSDR Plan uses the submission event names as the driving mechanism for the submittal of reports, not the “As Of Date”. In the event of a schedule slip, notify SSC/CGN that a date change is needed. SSC/CGN will submit a date change request with supporting documentation in the CADE system for approval. An updated DDCA-approved CSDR Plan will not be issued for revisions based solely on date changes.

Reports are required at event driven and annual report frequency. If the annual reports are due within 60 days of the event driven reports, the Contractor may request the annual reports to be waived. Annual reports can be waived at the discretion of the CWIPT.

Allow 30 days for Government (SSC/CGN and OSD DCARC) comment. Allow 15 days for Contractor to incorporate Government comments and resubmit. Additional revisions may be required. Delivery not complete until Government acceptance.

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 16 of 29

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the

B. EXHIBIT

B

E. CONTRACT/PR NO.

B010

2. TITLE OF DATA ITEM

CONTRACTOR BUSINESS DATA REPORT (DD FORM 1921-3)

3. SUBTITLE

CBDR

DI-FNCL-81765C

5. CONTRACT REFERENCE

SOW PARA 7.1.2

6. REQUIRING OFFICE

OSD CAPE

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

BLK 16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

SUBMISSION

The DD Form 1921-3 requirement applies to business entities holding DoD contracts with CSDR requirements that, in aggregate, are expected to exceed $250 million then-year dollar value per DoDI 5000.73 Table 1. The Contractor Business Data Report is to be prepared by and for the business entity (e.g., plant, site, or business unit) responsible for submitting the Forward Pricing Rate Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the government. In the absence of a FPR requirement, the term “FPR unit” should be interpreted for reporting purposes as “business unit” as defined in the FAR.

Description DI-FNCL-81765C (or most recently approved version) and the DD Form 1921-3 template, available from the Cost Assessment Data Enterprise (CADE) website at https://cade.osd.mil/policy/1921-3.

Submit the 1921-3 electronically as a stand-alone Excel-compatible file to the CADE’s secure website using the 1921-3 and Forward Pricing Rate Submit Review System. Uploading requires the use of either a DoD-approved ECA digital certificate or DoD-issued CAC. See the CADE website (https://cade.osd.mil) for certificate and other submission instructions. If the submission is classified, contact the Program Office to coordinate with the appropriate need-to-know personnel.

BLOCKS 10-14: Only one report is required to be completed and submitted by each FPR (Forward Pricing Rate) unit (e.g., plant, site, business unit) per year, independent of the number of contracts within the FPR unit which contain this CDRL item. The 1921-3 is due 60 days after the end of the FPR unit’s fiscal year.

Subcontractor Reporting: Prime contractors shall ensure CSDR requirements contained in their prime contracts are flowed down to all subcontractors who meet the reporting thresholds specified in the DoDI 5000.73, or as required by the cost working integrated product team (CWIPT). This includes requiring subcontractors to electronically report directly to CAPE using the CSDR Submit-Review System.

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 17 of 29

A003 D

(1 Data Item)

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the

B. EXHIBIT

B

E. CONTRACT/PR NO.

B011

2. TITLE OF DATA ITEM

BASELINE DESCRIPTION DOCUMENT

3. SUBTITLE

BDD

DI-SESS-81121A

5. CONTRACT REFERENCE

SOW PARA 7.2.1

6. REQUIRING OFFICE

SSC/CGN

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

SUBMISSION

BLOCK 4: Contractor format is acceptable. Documents listed on the BDD will be made available upon request.

BLOCKS 10, 11 12 & 13: Submit Baseline Description Document NLT 7 days after completion of EDR. Allow 15 days for Government review and approval of technical content, contractor incorporates Government review comments and resubmits for approval NLT 7 DARC. Resubmit quarterly if there are changes to the baseline. At the end of contract, provide a complete BDD covering the entire program from contract award to the end of the contract.

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 18 of 29

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 thus burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the

B. EXHIBIT

B

E. CONTRACT/PR NO.

B013

2. TITLE OF DATA ITEM

DATA ACCESSION LIST

3. SUBTITLE

DAL

DI-MGMT-81453B

5. CONTRACT REFERENCE

SOW PARA 7.2.1

6. REQUIRING OFFICE

SSC/CGN

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

QRTLY

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

SUBMISSION

BLOCK 4: Use DI-MGMT-81453B as guidance; Contractor format is acceptable.

BLOCKS 12 & 13: First submission 90 DACA provide complete listing. Subsequent Quarterly submissions may provide only new items since last submit. At the end of contract, provide a complete Data Accession List covering the entire program from contract award to that date.

BLOCK 16 Description: The Contractor shall identify the Government Rights to the data as applicable on the DAL using the following codes:

UR - Unlimited Rights

LR - Limited Rights

RR - Restricted Rights (computer software only)

GPR - Government Purpose Rights

CLR - Commercial License Rights for commercial technical data

CSLR - Commercial Software License Rights for commercial computer software and commercial computer software documentation

SNLR - Specifically Negotiated License Rights

LUKE OZECK

H. DATE

24 MAR 2023

I. APPROVED BY

BRYAN BOARDWAY

FA8807-23-R-0005 EXHIBIT B – CONTRACT DATA REQUIREMENTS LIST Page 19 of 29

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.