Technical_Exhibit_2_Deliverables.docx

TECHNICAL EXHIBIT 2

DELIVERABLES SCHEDULE

In Progress Review Report

MS PowerPoint presentation via email

COR

CTC Daily Status Reports

7.Below are the explanations of the deliverables which span the PWS.

7.1. In-Progress Reviews. The contractor shall participate in IPRs; the frequency and scope of which shall be determined at the Post Award Meeting chaired by the Contracting Officer’s Representative (COR). Schedule an initial visit with the COR within 10 working days of the start of the period of performance. The initial meeting will be held at Fort Gordon, GA. Specific units to be visited and researched will be determined at the initial meeting. IPR minutes shall also be submitted with the monthly invoice.

7.2. Monthly Status Reports. (A008) The contractor shall provide a monthly Contractor’s Progress, Status, and Management Report containing the following:

· Brief description of the requirements

· Brief summary of accomplishments during the reporting period

· Significant events regarding the Contract

· Progress on deliverable products

· Current or anticipated problems

· Action required by the Government if any

· Summary of activity planned for the next reporting period

7.3. L&BP Publications. This includes analysis, research, production, revision and staffing of handbooks, graphic training aids (GTA) and articles as applicable, for each project functional area.

7.3 Website updates. Lessons and Best Practice analysts will ensure the website is updated. This includes posting of approved observations from CTC rotations, post deployment collection visits (PDCV), home station training events, Industry Engagements, Federal Agencies and Academia.

7.4 L&BP Database Update. Lessons and Best Practice analysts will update the JLLIS database with observations from CTC rotations, PDVC, home station training events, Industry Engagement, Federal Agencies and Academia. The database will be updated after each event, this includes updating the questions in the database to ensure they are relevant to the collections.

7.5 Historical Report. Upon acceptance of concepts and doctrine products by the Government, the contractor shall develop a historical report for each product (sample format to be provided upon contract award). This report provides a detailed description of each project and all key events relating to the project, i.e. key personnel, references used, and any problem areas with recommendations. All documented reviews and reports will be retained by the COR and used as documented past performance for subsequent contracts. This report is due NLT 30 days prior to contract expiration.

7.6 After Action Reports (AAR)/L&BP Collection Form. Products will consist of detailed AARs (sample format to be provide upon contract award) which will include L&BP collection form (sample format to be provide upon contract award) for each Cyber/Signal L&BP collection effort. This information will be complied and entered into the L&BP JLLIS database repository by the L&BP Analyst. The AARs will be maintained for a three year period for audit trail capabilities.

7.7. L&BP SIGACTS. SIGACTS is due by 1000 every Monday morning in accordance with (IAW) guidance provided by the Doctrine Division, CDID. To include SIGACTS after an event when analyst completes travel on Friday, SIGACTS is due Monday by 1000. The SIGACTS will be provided to the L&BP Chief and Government Team Lead by the Contract Lead.

7.7 Trip Reports. The initial submission is due no later than (NLT) 3 working days after travel. This report shall provide a synopsis of accomplishments performed during the travel period. No collected L&BP specific information is included in this report.

· Trip report shall include:

· Organization Visited

· Dates

· Travelers’ names

· Destination

· Purpose / Scope

· Persons Contacted

· Discussion Background

· Concerns / Issues

· Identified and posted Cyber, Signal, and Electronic Warfare Observations by JLLIS number.

· Conclusions

· Recommendation if necessary

7.8. CTC Daily Status Reports. The contractor shall provide a daily report throughout the rotation by providing the following by email.

· Date and time when traveled to and from the training area (box)

· Contact and discussions with the rotational unit staff, i.e. S6, Communications Chief (25U40), Signal Company Commander, EWO, 255S, 25D, Signal Soldiers, Battalion S6, Commo Chief etc.,...

· Challenges and Successes as releasable by the CTCs

7.9. CTC Weekly SYNC Status Slide. The CTC analyst shall provide the following information to support the weekly L&BP and Doctrine Division synchronization meetings.

7.10. CTC Rotation SIGACTS. The CTC analyst shall provide a SIGACTS the first Monday by 1000 after the rotation in accordance with (IAW) guidance provided by the Doctrine Division, CDID. The SIGACTS will be provided to the L&BP Chief and Government Team Lead by the Contract Lead.

7.11. CTC Final Rotational Training Unit Rollup. The CTC analyst shall provide a report after each unit’s rotation by providing the following

- Compilation of the daily reports highlighting any gaps, trends and/or issues

- Identify any lessons learned, best practices and TTPs collected/identified during the rotation. Include a detailed report of each of the collected observations, trend, and or gap being submitted for review (MS Word no prescribed format).

- Reports, AARs (cyberspace, signal, and EW) from the rotation that are releasable from the CTC (JRTC/NTC)

7.12. Post cyberspace, signal, and electronic warfare observations. CCoE L&BP analyst will identify and post an observation on JLLIS for each cyberspace, signal and EW per CTC rotation or per collection event (i.e. FTX, CPX, Home Station Training, PDCV etc...). The analyst will provide the pertinent information using the format in JLLIS.