Attachment 1 - PWS ATTACHMENT B - DELIVERABLES.pdf

FA7014-24-R-0001

PWS Attachment B

Deliverable Details

1. Management/Staffing Plan

2. Organizational Conflict of

Interest (OCI) Plan

3. Transition Plan

4. Small Business

Subcontracting Plan

This is IDIQ Specific.

Reference: IDIQ Request for Proposal Due Date: All plans listed at left will be submitted as part of the ID/IQ Proposal and will be incorporated into the contract.

Delivery:

• All documents shall be delivered IAW the criteria established in the ID/IQ RFP Technical Criteria

• The OCI Plan shall also be submitted IAW RFP/contract section 4, paragraph 4a-6

• The Small Business Subcontracting Plan shall also be submitted IAW RFP/contract section 4, paragraph 4a-7 Updates: The Contractor shall provide any changes or updates to the Government PMO (CO, Program Manager, Quality Assurance Manager (QAM)) and COR prior to Contractor implementation.

Quality Control Plan (QCP)

This is IDIQ Specific

Reference: PWS Section 8 Due Date: The Contractor shall provide a QCP to the Government PMO and COR, as specified in PWS paragraph 6.2, NLT 10 calendar days after AF FIAR Support ID/IQ contract award.

Updates: The Contractor shall provide any changes or updates to the Government PMO and COR prior to Contractor implementation.

Data Accession List CDRL

AF FIAR Spt CDRL A001 Data Accession

Reference: PWS paragraph 2.1.9 Due Date: Data shall be as of the last day of the contractual quarter. First submittal shall be NLT 90 days after contract start. Following submittals shall be NLT the 15th calendar day (last weekday before the 15th calendar day if it falls on a weekend or holiday) following the contractual quarter.

Updates: Quarterly per above.

Kick-off Meeting

Reference: PWS paragraph 7.4 Due Date: The Contractor shall attend the Kick-Off Meeting within 10 business days of contract award.

Details:

• Government PMO responsible for setting up meeting

Subcontractor List

This is specific to IDIQ.

Reference: See below Due Date: The Contractor shall provide a Subcontractor List to the Government PMO NLT 10 calendar days after AF FIAR Support ID/IQ contract award.

Updates: The Contractor shall disclose new teaming partners/ subcontractors prior to that entity’s participation in response to a task order solicitation. The Contractor shall coordinate with the CO prior to adding or deleting subcontractors from the prime’s subcontractor list. The Contractor shall provide timely notification to the CO of any acquisitions or mergers that impact this contract.

Individual and/or Summary Subcontracting Report

(ISR/SSR).

This is specific to IDIQ.

Reference: See below Due Date: The Contractor shall submit ISR/SSR using the Electronic Subcontracting Reporting System (eSRS) at http://www.esrs.gov) IAW FAR 19.704(a)(10)(iii)(A) and guidance in eSRS.

Contractor Labor Hours Report(eCMRA)

Reference: PWS Paragraph 7.6 and subparagraphs Due Date: The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract at http://www.ecmra.mil.

Contractor-identified concern that impacts the Contractor’s ability to meet deliverable milestones/timelines

Reference: PWS paragraph 9.2 Due Date:

• Verbal and electronic notification identifying the nature of the issue to the COR within three (3) business hours of identification.

• Written recommendations and corrective actions required to meet deliverable milestones/timelines within eight (8) business hours of identification, unless otherwise approved in writing by the applicable COR.

Scoping and Planning Activities Report

Reference: PWS Para 2.2.1.8

Trip Report Reference: PWS Para 2.1.7 Following official travel, the Contractor shall prepare a trip report detailing the purpose of the trip, the individuals contacted, any agreements that were reached during the trip or any other significant issues that were identified during the travel. The Contractor shall provide this trip report to the COR within two (2) days after the completion of travel

Document Testing Report Reference: PWS Para 2.2.1.8

Report and Monitoring Results Reference: PWS Para 2.2.1.8

Corrective Actions Report Reference: PWS Para 2.3 http://www.esrs.gov/ http://www.ecmra.mil/

Monitor and Report Corrective Actions

Reference: PWS Para 2.3.1

Monthly Activity Report Reference: PWS Paragraph 2.8 Due Date: The Contractor shall provide two Monthly Activity Reports - one for Air Force Working Capital Fund FIAR efforts and a second that reports on Contractor Program Management by Task Order by the 15th of every month. If the 15th occurs on a weekend or holiday, then the Contractor shall provide the Report the previous business day. Report to reflect major accomplishments, projected major tasks, and identified risks for each task order and all applicable Tasks outlined in the PWS.

Task Order Invoices Reference: PWS Paragraph 7.1

All invoicing will be at the CLIN level.

Documented Security Controls Assessment Results and Workpapers

Reference: PWS Paragraph 2.5.1 Due Date: After completion of Security Controls Assessments. By email to COR in format identified by contractor but must be readable by Gov’t.

Documented Business Process Control Assessment Results and Workpapers

Reference: PWS Paragraph 2.5.2 Due Date: After completion of Business Process Control Assessments. By email to COR in format identified by contractor but must be readable by Gov’t.

Documented Recommendations on Business Process Improvements

Reference: PWS Paragraph 2.5.2 Due Date: After completion of Business Process Control Assessments. By email to COR in format identified by contractor but must be readable by Gov’t.

Documented Test and Validation Results including workpapers

Reference: PWS Paragraph 2.5.4 Due Date: After submittal of CAPs, SIDs or other IT issues for closure. By email to COR in format identified by contractor but must be readable by Gov’t.

Self-Identified Deficiencies (SIDs)

Reference: PWS Paragraph 2.5.5 Due Date: After Security Controls, Business process, or any IT Assessments. By email to COR in format identified by contractor but must be readable by Gov’t.

Corrective Action Plans (CAPs)

Reference: PWS Paragraph 2.5.5 Due Date: After Security Controls, Business process, or any IT Assessments. By email to COR in format identified by contractor but must be readable by Gov’t.

Integrated Master Schedule

(IMS)

Reference: PWS Paragraph 2.5.5 Due Date: 5th business day of month. By email to COR in format identified by contractor but must be readable by Gov’t.

Documented Audit Best Practices guidelines

Reference: PWS Paragraph 2.5.8 Due Date: 5 months post award. By email to COR in format identified by contractor but must be readable by Gov’t.

Documented final system capabilities for DAF identified major investment systems

Reference: PWS Paragraph 2.5.12 Due Date: 8 months post award. By email to COR in format identified by contractor but must be readable by Gov’t.

FIAR IT CAP Tracker Reference: PWS Paragraph 2.5.18 Due Date: Weekly on Friday, if Friday falls on holiday, then next Monday. By email to COR in format identified by contractor but must be readable by Gov’t.

OSD Database Updates Reference: PWS Paragraph 2.5.18 Due Date: Weekly on Friday, if Friday falls on holiday, then next Monday. By email to COR in format identified by contractor but must be readable by Gov’t.

DAF FIAR IT System Listing Reference: PWS Paragraph 2.5.19 Due Date: 5th business day of month. By email to COR in format identified by contractor but must be readable by Gov’t.

Documented CPI Assessment on current CFP process with recommendations for improvement

Reference: PWS Paragraph 2.5.22 Due Date: 6 months post award. By email to COR in format identified by contractor but must be readable by Gov’t.

Complete Implementation of Audit Remediation Tools

Reference: PWS Paragraph 2.5.24 Due Date: 12 months post award. By email to COR in format identified by contractor but must be readable by Gov’t.

Monthly Activity Report Reference: PWS Paragraph 2.5.25 Due Date: 5th business day of month. By email to COR in format identified by contractor but must be readable by Gov’t.

Agile Work Management Plans

Reference: PWS Paragraph 2.5.25 Due Date: 1 month post award. By email to COR in format identified by contractor but must be readable by Gov’t.

Program Increment Plans Reference: PWS Paragraph 2.5.25 Due Date: Before each Program Increment spanning 3-4 sprints. By email to COR in format identified by contractor but must be readable by Gov’t.

Sprint Plans Reference: PWS Paragraph 2.5.25 Due Date: 1 month post award. By email to COR in format identified by contractor but must be readable by Gov’t.

Sprint Delivery Reports Reference: PWS Paragraph 2.5.25 Due Date: As required after each sprint. By email to COR in format identified by contractor but must be readable by Gov’t.

Security Plans Reference: PWS Paragraph 2.5.25 Due Date: 3 months post award. By email to COR in format identified by contractor but must be readable by Gov’t.

Solution Architectures Reference: PWS Paragraph 2.5.25 Due date: 3 months post award. By email to COR in format identified by contractor but must be readable by Gov’t.

System Design Documents Reference: PWS Paragraph 2.5.25 Due date: 4 months post award. By email to COR in format identified by contractor but must be readable by Gov’t

Testing Plans Reference: PWS Paragraph 2.5.25 Due date: 4 months post award. By email to COR in format identified by contractor but must be readable by Gov’t

CONOPS Reference: PWS Paragraph 2.5.25 Due date: 5 months post award. By email to COR in format identified by contractor but must be readable by Gov’t

Infrastructure Testing Plans Reference: PWS Paragraph 2.5.25 Due date: 8 months post award. By email to COR in format identified by contractor but must be readable by Gov’t

Functional Testing reports Reference: PWS Paragraph 2.5.25 Due date: 9 months post award. By email to COR in format identified by contractor but must be readable by Gov’t

User Acceptance Testing Reports

Reference: PWS Paragraph 2.5.25 Due date: 5 days after User Acceptance Testing (UAT). By email to COR in format identified by contractor but must be readable by Gov’t

Transition Plans Reference: PWS Paragraph 2.5.25 Due date: 10 months post award. By email to COR in format identified by contractor but must be readable by Gov’t

End-to-end Business Process Enterprise Architecture artifacts aligned to BEA 11.2 and in compliance with DoDAF 2.02 standards.

Reference: PWS Paragraph 2.5.27 Due date: 11 months post award and quarterly updates thereafter. By email to COR in format identified by contractor but must be readable by Gov’t

Quarterly Statement of Assurance Submission Packages

Reference: PWS Paragraph 2.1.7 Due date: As required by OUSD(C) SOA Handbook, by email to govt POCs

Updated A-123 Publications

(AFPD, AFI, RMIC

Playbook/DAFMAN)

Reference: PWS Paragraph 2.1.10 Due date: As required, but at a minimum, review for updates annually, by email to govt POCs

Executive Steering Committee / Senior Assessment Team (ESC/SAT) Charter

Reference: PWS Paragraph 2.1.4 Due date: As required, by email to govt POCs

ESC/SAT Governance Meeting Package

Reference: PWS Paragraph 2.1.4 Due date: Quarterly, by email to govt POCs

Annual RMIC Training Reference: PWS Paragraph 2.1.5 Due date: Annually, Quarter 1, Virtually

DAF General Fund Scoping Document

Reference: PWS Paragraph 2.1.7 Due date: Annually, Quarter 1, by email to govt POCs

Updated Process Cycle Memorandum (PCM) Template

Reference: PWS Paragraph 2.1.8 Due date: Annually, by email to govt POCs

Assessable Unit (AU) PCM Review comments

Updated Control Evaluation Matrix (CEM) Template

AU CEM Review comments Reference: PWS Paragraph 2.1.8

Updated Control Testing Workbook Template

Updated Walkthrough Template Reference: PWS Paragraph 2.1.8

Self-Identified Deficiency (SID) Template

Updated Summary of Aggregated Deficiencies (SAD) Template

Due date: Annually, Q3, by email to govt POCs

Summary of Aggregated Deficiencies (SAD) Template

AFAA-Agreed Upon Procedures (AUPs) requirements listing

Due date: Annually, Q4, by email to govt POCs

Updated Entity Level Control (ELC) Testing Matrix

ELC Testing results report Reference: PWS Paragraph 2.1.7

ELC SIDs Reference: PWS Paragraph 2.1.7

Updated Fraud Risk Assessment template

Reference: PWS Paragraph 2.1.3, 2.1.7

Fraud Risk control Testing Results Reference: PWS Paragraph 2.1. 3, 2.1.7

Recurring updates (A4 Audit Update, MAJCOM Audit Update, etc.)

Reference: PWS Paragraph 2.1.4, 2.1.7

CAP for A-123 deficiencies (Self- Identified or External)

DAF Risk Profile Reference: PWS Paragraph 2.1.3

Automated A-123 testing activities uploaded into production

Reference: PWS Paragraph 2.1.1 Due date: In accordance with a mutually agreed upon schedule, Demonstration and User Acceptance Testing

(UAT)

Develop an automated Form in eGRC fed by an automated Entity Level Control process

Reference: PWS Paragraph 2.1.1 Due date: In accordance with a mutually agreed upon schedule, Demonstration and UAT

Real-time risk and control posture dashboard

Export capability for AFAA Agreed Upon Procedures work papers

Automated initiation of fraud control assessment to populate OUSD(C) Template

Automated data quality control assessments and population of the OUSD(C) data quality testing and reporting template

User training, and configuration documentation

Due date: Prior to Go-Live, “How to” function embedded in the GRC system

Certification Statement Call Letter Reference: PWS Paragraph 2.1.

Due date: Annual, Quarter 4

SOC 1 Monitoring Reports Reference: PWS Paragraph 2.1.7 Due date: Annual, End of Quarter 3, by email to govt POCs

SOC 1 Report Feedback Reference: PWS Paragraph 2.1.7 Due date: Annual, as required by the Service Provider Working Group, by email to govt POCs

SOC 1 Deficiency Tracker Reference: PWS Paragraph 2.1.7 Due date: Annual, two weeks after receipt of last SOC 1 Report, by email to govt POCs

Review/refresh Service Provider MOUs

Due date: Annual, initiate review 60 days prior to expiration date, by email to govt POCs

Review/refresh MOU Appendices Reference: PWS Paragraph 2.1.7 Due date: Annual, after completion of PCMs/CEMs, by email to govt POCs

CUEC Update Distribution Reference: PWS Paragraph 2.1.7 Due date: Bi-Annual, within five business days of the OUSD(C) Service Provider Working Group, by email to govt POCs

Agency Financial Report (AFR) schedule

Reference: PWS Paragraph 2.4.1 Due date: 30 March, by email to govt POCs

AFR status updates Reference: PWS Paragraph 2.4.1 Due date: Bi-weekly (until 15 July); Weekly (15 July- 15 Nov), by email to govt POCs

AFR theme options Reference: PWS Paragraph 2.4.1 Due date: 30 March, by email to govt POCs

AFR outline Reference: PWS Paragraph 2.4.1 Due date: 29 April, by email to govt POCs

Draft Management’s Discussion and Analysis (MD&A)

Due date: 29 July, by email to govt POCs

Draft Agency Head Letter Reference: PWS Paragraph 2.4.1 Due date: 10 August, by email to govt POCs

Draft CFO Message Reference: PWS Paragraph 2.4.1 Due date: 15 August, by email to govt POCs

Draft Management Response Letter Reference: PWS Paragraph 2.4.1 Due date: 15 August, by email to govt POCs

Prepare Management Schedule of Information (MSI) that reconciles to the Legal Representation Letter

Due date: 13 July (Interim); 6 October (Final), by email to govt POCs

TMT packages for Agency Head Letter, CFO Message, Management Response Letters

Due date: 29 August, by email to govt POCs

OMB A-136 compliance review Reference: PWS Paragraph 2.4.1 Due date: 1 September, by email to govt POCs

TMT packages for Management Representation Letters

Due date: 19 September, by email to govt POCs

Reconciliation of DDRS-AFS financial statements and footnotes to AFR

Due date: 23 October, by email to govt POCs

Draft AFR Reference: PWS Paragraph 2.4.1 Due date: 23 October, by email to govt POCs

Final AFR Reference: PWS Paragraph 2.4.1 Due date: 7 November, by email to govt POCs

Identify all lines requiring variance analyses explanation

Reference: PWS Paragraph 2.4.2 Due date: 15th Business Day (Q1-Q3); 18th Calendar Day (Q4), by email to govt POCs

Final Variance Analysis briefing materials

Reference: PWS Paragraph 2.4.2 Due date: 17th Business Day (Q1-Q3); 20th Calendar Day (Q4), by email to govt POCs

Quarterly Datacall JV packages and tracker

Reference: PWS Paragraph 2.4.3 Due date: Quarterly, by email to govt POCs

JV review documentation and root cause analysis

Reference: PWS Paragraph 2.4.4 Due date: Monthly, by email to govt POCs and posted to joint FSCR SharePoint website

Fund Balance with Treasury (FBwT) Consolidated Cash Accountability System (CCAS) Oversight

Reference: PWS Paragraph 2.2.4 Due date: Monthly

FBwT CCAS Supplemental File Analysis

Reference: PWS Paragraph 2.2.4 Due date: Monthly

FBwT CCAS Manual Change Log Analysis

Reference: PWS Paragraph 2.2.4 Due date: Monthly

FBwT Lookback Analysis Reference: PWS Paragraph 2.2.4 Due date: Monthly

FBwT CCAS Source File to Universe of Transactions Reconciliation

Reference: PWS Paragraph 2.2.4 Due date: Monthly

FBwT Mechanization of Contract Administration Services (MOCAS) to Central Accounting and Reporting System (CARS) Oversight

Reference: PWS Paragraph 2.2.4 Due date: Monthly

FBwT 7113 Reperformance Reference: PWS Paragraph 2.2.4 Due date: Monthly

FBwT Trend Analytic Reference: PWS Paragraph 2.2.4 Due date: Monthly

FBwT CCAS Reconciliation Reperformance

Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT Statement of Difference (SOD) Materiality Assessment Oversight

Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT Suspense Materiality Assessment Oversight

Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT Deposit Fund Analysis Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT Historical Trend Analysis (HTA) and HTA JVs

Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT CCAS Crosswalk Documentation and Assessment

Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT Civilian Pay Reperformance Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT Civilian Pay SOD Oversight Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT Defense Enterprise Accounting and Management System (DEAMS) Treasury Direct Disbursing (TDD) to CARS

Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT CARS to Governmentwide Accounting (GWA) to 1329 Reconciliation

Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT CCAS User Access Review Reference: PWS Paragraph 2.2.4 Due date: Quarterly

FBwT CCAS Source File Assessment

Reference: PWS Paragraph 2.2.4 Due date: Annually with Quarter (Q) 1 Reperformance

FBwT CCAS Source File Parameter Assessment

Reference: PWS Paragraph 2.2.4 Due date: Annually with Q2 Reperformance

FBwT SOC-1 and CUEC Analysis Reference: PWS Paragraph 2.2.4 Due date: Annually

FBwT CCAS Report Generation and Standard Operating Procedure (SOP) Review

Reference: PWS Paragraph 2.2.4 Due date: Annually

FBwT CCAS Parameter Assessment Review

Reference: PWS Paragraph 2.2.4 Due date: Annually with Q2 Reperformance

FBwT CCAS Manual Change Log and Supplemental Customer Request Sampling

Reference: PWS Paragraph 2.2.4 Due date: Annually with Q4 Reperformance

UoT DDRS Reconciliations Reference: PWS Paragraph 2.7.4 Due date: Quarterly

UoT GAFS-R Reconciliations Reference: PWS Paragraph 2.7.4 Due date: Monthly

UoT DEAMS Reconciliations Reference: PWS Paragraph 2.7.4

UoT Legacy Feeder Reconciliations

Reference: PWS Paragraph 2.7.4

UoT APSR Reconciliations Reference: PWS Paragraph 2.7.4

GAFS-R GL Posting Logic Oversight

Reference: PWS Paragraph 2.7.4 Due date: As required

DEAMS Posting Logic Oversight Reference: PWS Paragraph 2.7.4

DDRS Crosswalk Oversight Reference: PWS Paragraph 2.7.4

UoT NFR Remediation (CAP) Reference: PWS Paragraph 2.7.4