JOIST-DRD-15-Status_Reports_and_Reviews.docx

JSC DATA REQUIREMENTS DESCRIPTION (DRD)

(Based on JSC –STD-123. See work page for instructions.)

5. Use (Define need for, intended use of, and/or anticipated results of data)

6. DRD Category: (check one)

☐Administrative

☐S&MA

6. References

7. Interrelationships (e.g., with other DRDs) (Optional)

a. JSC-63756A, Mission Operations Directorate Software Management Plan

b. CD-UWI-0013, Mission Systems Division Governance Plan

c. NASA-STD-8739.8, Software Assurance Standard, Section 6.7, Software Assurance Status Reporting

8. PREPARATION INFORMATION:

The Contractor shall prepare the data delivery as follows:

8a. DATA TYPE:

☐ Type 1 – Written approval ☒Type 2 – Mandatory Submittal ☐Type 3 – Submittal Upon Request

8b. SCOPE:

This DRD establishes the reporting for the activity, performance, and utilization of the JOIST elements. This DRD will also identify the Contractor’s progress and accomplishments.

8c. CONTENT:

(i) Status Reports and Reviews: Include overall technical, administrative progress, and status of significant activities relating to the accomplishments of the contractual objectives. Risks to the accomplishment of contractual objectives shall also be identified. These reports and reviews also include performance and utilization data of major systems.

(ii) Activity Reports: Include significant accomplishments, high level run reports for simulations, tests, problems encountered, quality assurance results, corrective actions, and significant facility problems or mishaps.

(iii) Surveillance Reports: Include a description of the surveillance methodology for internal and supplier surveillance, internal and supplier surveillance performed in the evaluation period, internal and supplier surveillance findings, internal and supplier corrective action requests issued, and plans for improvement.

(iv) Status Reports and meetings include, but are not limited to:

1. Weekly or as required reports:

(a) Weekly activity reports

(b) Control Boards (CBs), governing boards, and panels

(c) Delivery schedules

(d) Work plans

(e) The following weekly report is applicable only to Baseline A: The contractor shall describe the following:

a. Significant issues that were encountered in the previous week that require NASA management attention or that may impact contractor’s performance on the task

b. Significant accomplishments that the contractor feels should be brought to NASA’s attention

c. Brief statements of the status of all ongoing tasks

d. Achievement or failure to achieve any milestones

e. Other information that the contractor feels is significant

2. Monthly or as required reports:

(a) Progress reports

(b) Delivery schedules

(c) Work plans

(d) DRD status reports

(e) IT Security reports

(f) QA reports

(g) SQA monthly report (in accordance with NASA-STD-8739.8, Software Assurance Standard, Section 6.7, Software Assurance Status Reporting)

(h) Surveillance reports

(i) Travel reports

(j) The following monthly report is applicable only to Baseline A: The contractor shall describe the following:

a. Significant issues that were encountered in the previous month that require NASA management attention or that may impact contractor’s performance on the task

b. Significant task accomplishments that the contractor feels should be brought to NASA’s attention

c. Narrative description of the previous month’s activities, including the status of quality assurance audits of contractor products

d. Any and all innovative or exceptional performance areas which the contractor believes occurred during the previous month

e. Briefly describe any focus areas planned for the following month

f. Summary breakdown of year-to-date, monthly actuals/forecast costs by task and/or task area. This section shall include metrics which must include hours forecast, hours accomplished, and percentage of task area completed. This is in addition to the 533M DRD.

g. Status of contract metrics, including labor hours by task and task area. It shall also include the status of contractor’s small business and small business subcategory performance for the period, year to date, and contract to date, expressed both as percentages of total labor hours and percentages of total contract value.

8d. FORMAT:

Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be determined by mutual agreement between the Contractor and the COR.

8e. DISTRIBUTION:

Distribution shall be in accordance with Attachment J-01, Data Requirements List.

8f. SUBMISSION:

(i) Initial – Due at the end of the first applicable reporting period after contract start.

(ii) Final – Due at the end of the final applicable reporting period.

(iii) Approval – N/A.

(iv) Frequency – Due on the last day of the applicable period for status reports covering one week or less. Due 10 calendar days following close of the applicable period for all status reports covering periods of time greater than one week. Other frequencies are acceptable with mutual agreement of the Contractor and the COR.

JSC Form 2341 (Rev October 19, 2011) (MS Word 2007) (Previous editions are obsolete.)

NNJ17580323R Attachment J-02 – DRD-15-1