RFP_N0018919RZ070.docx

N0018919RZ070

Section SF 1449 - CONTINUATION SHEET

Navy Operations and Systems Integration

FFP

In accordance with the Performance Work Statement Period of Performance: 29 September 2019 through 28 September 2020 FOB: Destination

PSC CD: R703

NET AMT

Travel

FFP

In accordance with the Joint Travel Regulations (JTR) Period of Performance: 29 September 2019 through 28 September 2020 Not to Exceed amount: $60,000

NET AMT

FFP

In accordance with the Performance Work Statement Period of Performance: 29 September 2020 through 28 September 2021

NET AMT

FFP

In accordance with the Joint Travel Regulations (JTR) Period of Performance: 29 September 2020 through 28 September 2021 Not to Exceed amount: $60,000

NET AMT

FFP

In accordance with the Performance Work Statement Period of Performance: 29 September 2021 through 28 September 2022

NET AMT

FFP

In accordance with the Joint Travel Regulations (JTR) Period of Performance: 29 September 2021 through 28 September 2022 Not to Exceed amount: $60,000

NET AMT

FFP

In accordance with the Performance Work Statement Period of Performance: 29 September 2022 through 28 September 2023

NET AMT

FFP

In accordance with the Joint Travel Regulations (JTR) Period of Performance: 29 September 2022 through 28 September 2023 Not to Exceed amount: $60,000

NET AMT

FFP

In accordance with the Performance Work Statement Period of Performance: 29 September 2023 through 28 September 2024

NET AMT

FFP

In accordance with the Joint Travel Regulations (JTR) Period of Performance: 29 September 2023 through 28 September 2024 Not to Exceed amount: $60,000

NET AMT

PERFORMANCE WORK STATEMENT

DoN Financial Improvement and Audit Readiness Performance Work Statement for Navy Operations and Systems Integration Support (OASIS)

1. BACKGROUND

In response to the Public’s desire for increased transparency and efficiency in spending, Congress passed the National Defense Authorization Act (NDAA) in 2010, requiring Department of Defense financial statements to be fully auditable by 2017. As a result, delivering financial information with greater accuracy, reliability, and accessibility is a strategic imperative for the Department of the Navy (DoN or Navy). To comply, all DoN Budget Submitting Offices (BSOs) must migrate from the existing STARS-FL system over to the audit tested Standard Accounting Budgeting and Reporting System (SABRS) Suite of Tools. The suite consists of PR Builder, SABRS and SMARTS, and any additional Financial Feeder System (as designated by FMP), and provides an enhanced financial management solution for end users with benefits such as, customized work flows, automated data feeds, and enhanced Business Intelligence. The objective is to produce financial information with greater accuracy, reliability and accessibility to support near and long-term audit goals. To that end, the DoN will transition BSOs currently using STARS to the SABRS suite, maximizing the use of audit-proven business processes and management information systems.

2. SCOPE OF THE CONTRACT

This effort will require the contractor to provide resources for functional and technical subject matter expertise, for all Navy BSOs and all Navy users using the SABRS Suite of systems for all phases of the requirement, deployment and implementation of the help desk effort for functional and technical support effort for SABRS.

The following BSOs and activities are within scope of the effort of this contract:

· DoN Assistant for Administration (DON/AA)

· Commander, Naval Installations Command (CNIC)

· Field Support Activity (FSA)

· Naval Intelligence Activity (NIA)

· Bureau of Naval Personnel (BUPERS)

· U.S. Fleet Forces Command (USFF)

· Naval Facilities Engineering Command (NAVFAC)

· U.S. Pacific Fleet (PACFLT)

· Navy Reserve Force (RESFOR)

· Naval Special Warfare Command (SPECWAR)

· Bureau of Medicine and Surgery (BUMED)

The Contractor shall prepare and maintain a Contract Management Plan (CMP) describing the technical approach, organizational resources, and management controls to be employed to meet the performance and schedule requirements throughout contract execution. The CMP must include a Government-approved Quality Assurance Plan (QAP) that identifies the procedures and processes to be implemented by the contractor to assure that Navy Operations and Systems Integration Support (OASIS) quality services will be consistently delivered during the period of performance. The QAP, at a minimum, shall include::

Recommendations for future improved reporting may be proposed in writing by the Contractor. Any change to the reporting requirements must be approved by the Contracting Officer Representative (COR) with concurrence from the Navy OASIS management team.

3. Information Sources

The contractor shall utilize the following sources, policies, regulations and project documentations. All of the below listed documents is publicly available and will be provided by the Government at the request of the Contractor.

3.1 Federal Management Financial Integrity Act of 1982

3.2 Chief Financial Officers Act of 1990

3.3 Government Performance and Results Act (GPRA) of 1993, as amended

3.4 Government Management Reform Act of 1994, as amended

3.5 Federal Financial Management Improvement Act of 1996

3.6 Department of Defense Financial Management Regulation (DoD FMR)

3.7 OMB Circulars A-123 and A-136,

3.8 Related Executive Memorandums

3.9 Treasury Financial Manual

3.10 DoD and DoN Guidance

3.11 DoD Instruction 8500.01 Cybersecurity

3.12 Prompt Payment Act (PPA)

3.13 Anti-Deficiency Act (ADA)

3.14 Improper Payment Improvement Act

3.15 Federal Acquisition Streamlining Act (FASA)

3.16 Federal Acquisition Regulation (FAR)

3.17 Defense Federal Acquisition Regulation Supplement (DFARS)

3.18 Generally Accepted Accounting Principles (GAAP)

3.19 Statement of Federal Financial Accounting Concepts (SFFAC) Number 2, Entity and Display

3.20 Federal Accounting Standards Advisory Board

3.21 Other DoD guidance as applicable

4. Government Furnished Information (GFI) and Government Furnished Property (GFP)

The Government will provide the Contractor with all reasonably available information requested concerning this PWS and the applicable documents as identified in this PWS. The Contractor shall protect all GFI (technical data) provided by the Government from public disclosure in accordance with the marking contained therein. All data developed by the Contractor during this contract shall become the property of the Department of Navy. The Contractor shall be required to abide by the disclosure standards set forth in DFARS 252.204-7000 and to complete Employee Confidentiality and Non-Disclosure forms. The Contractor shall not release any information to regulators, media, or other parties without permission from the Contracting Officer. All records shall be maintained IAW DoD Directive (DoDD) 5015.02 dated February 24, 2015, Incorporating Change 1, August 17, 2017.

Government furnished facilities or workspace will be provided for 65% of the effort within the NCR. All Help Desk support shall be 100% on-site at Government facilities. In performance of this effort, the contractor will be provided documents and relevant data, as may be necessary to provide the support specified herein.

For on-site support at the Government facility(ies), the Government will furnish NMCI laptops.

5 Tasks

5.1 PROJECT MANAGEMENT SUPPORT: The Contractor shall provide Program Management support for Navy OASIS.

5.1.1 Administrative Financial Systems Support:

Contractor is expected to complement and sustain administrative support for Navy OASIS initiatives as follows:

· analyze financial and mixed-use systems and applications

· provide recommended performance measures and analysis reports

· support system and application training efforts

· support the maintenance, analysis and execution of existing databases, reports, performance measures, tools, and documentation.

The Contractor shall be responsible for assisting with strategic planning, assisting with oversight, and advising the Government on development of necessary policies, directives and technology reporting solutions required to institute and sustain the Navy OASIS data management and enterprise architecture programs.

5.1.2 Administrative Advisory Support: Contractor shall provide support services, planning, development, implementation, monitoring, and maintenance (of enterprise level data, tables, and documentation) of the necessary systems to support data management objectives and enterprise architecture implementation. This will include recommending policies, directives, and guidelines to ensure enterprise architecture implementation and the uniform application of data management principles, methods, and practices in support of Navy OASIS goals and objectives.

5.1.3 Administrative Accounting and Financial Management Policies and Guidelines Support: The Contractor shall assist Navy BSOs in interpreting data management requirements and in applying DoN accounting and financial management policies and guidelines.

In particular, the contractor shall:

1) Apply comprehensive understanding of data management concepts to provide advice and guidance to senior government staff;

2) Provide support in the use of data management systems and in the implementation or sustainment of Navy OASIS policies, directives, and principles governing data management and enterprise architecture so as to ensure complementary conformance with DoN accounting/auditing and financial management review requirements, guidelines, and objectives;

3) Support Navy OASIS data management and enterprise architecture needs through application of skill in understanding, using, and managing databases and other automated information systems;

4) Provide policies and guidelines support through use of knowledge of the concepts, principles, and practices of data management and the technology required to extract data and/or support accounting and mixed-use financial management system implementation or enhancement; and,

5) Interpret data management and enterprise architecture requirements to determine the effects on DoN programs, accounting, and financial management practices and propose strategies for meeting these requirements.

5.2 Tier 1 & 2 SABRS & SMARTS Help Desk Functions - Contractor shall provide operational SABRS support to field users by troubleshooting technical issues and developing solutions for remediation. Contractor will also create user accounts, manage group policies, provide updates to SABRS manuals based on Help Desk trending, and document processes. The Contractor will be accountable for meeting customer service performance metrics (see appendix).

5.2.1 Customer service includes but is not limited to the loading of tables in the systems, granting access to users, responding to emails, answering phones, logging tickets, external coordination with various SABRS stakeholders, and other customer service support.

The contractor will support government personnel in administering accounting system access controls and Terminal Area Security Officer (TASO) responsibilities.

Navy OASIS will maintain and implement the SABRSHELP Operations Manual for Service Desk Personnel (SOM-SDP) that specifies policies, standards, and procedures for operation of the Help Desk.

At a minimum, this manual shall include the following:

· procedures for ticket management,

· incident management and problem escalation,

· trend identification, and reporting.

Other applicable procedures and standards may be added during the life of the contract at the discretion of the Government, and must be approved by the COR with concurrence from the Navy OASIS management team. The Contractor shall update and enhance the SOM-SDP as appropriate throughout the life of the contract. However, the most current non-Draft copy of the SOM-SDP is a deliverable to be provided to the Government no less than quarterly, on a schedule that is off-cycle from the financial reporting schedule so that it does not interfere with services associated with monthly/quarterly close-out.

5.2.2 The contractor shall operate and maintain an onsite SABRS Help Desk service capable of supporting at least 1,200 tickets per month. The contractor shall implement a ticket system to log, track and report all incidents and requests. FMP management may request regular or ad hoc reports associated with incidents and incident tracking. FMP personnel shall have the availability to submit incidents and requests directly into the contractor-provided, government Incident Ticket system. The contractor shall ensure each verbal, telephonic and email request is input to an Incident Ticket for tracking and reporting purposes and each ticket is updated no less than weekly. The contractor shall support ad hoc incidents and requests as directed by the Government. Trend Analysis shall be performed and provided to the government regarding sustained variances from the projected 800 to 1,200 tickets per month.

5.2.2.1 Very Important Person (VIP) Support – The contractor shall maintain a current and accurate list of VIPs, providing immediate and exceptional response time for those on the VIP list. In addition to the top most senior executives in the United States Navy and Marine Corps, the contractor shall provide VIP support to all Assistant Secretaries (ASNs), other Political Appointees, Admirals, SESs, Directors, Comptrollers and other individuals that are designated by the Government as VIPs. All VIP tickets shall be placed on priority and tickets should be closed within 24 hours. VIP tickets shall be handled within 1 hour of when the ticket was created.

5.2.2.2 Tiered Support – The contractor shall support a tiered approach to Customer Service. It is expected that as the tier requirement increases, so does the subject matter expertise and knowledge of the support being provided. Once escalated, the contractor shall not downgrade the ticket to a lower tier. The contractor shall not escalate the ticket to a higher tier than necessary without prior approval from the Government.

5.2.2.2.1 Tier One – BSO Headquarters (HQ) Level comptroller staff will typically assist their organization’s users in remediating what would be considered a Tier One event. However, in such cases wherein the BSO HQ Level comptroller staff cannot bring the event to a successful conclusion, either due to skill level, knowledge, or lack of access, the contractor shall provide this initial Tier One level support. This support is at the help desk and administrative levels, using experience and working document SOPs to assist in the triage and remediation of the requested event. As this is typically the face of FMP-43 to its customer, a courteous, professional attitude is required. On the occasions that the experience and SOPs do not remediate the event, the Tier One shall escalate the event to Tier Two.

5.2.2.2.2 Tier Two – The contractor shall provide Tier Two level support. This tier is not a subject matter expert in a specific field, but is cross functional in many areas of SABRS Suite Support. Tier Two personnel shall have the knowledge and experience to triage and remediate most events. Tier Two Support provides Enterprise level subject matter expertise regarding business processes and enterprise level standardized data. In the unlikely cases that the event is not completed, the Tier Two shall escalate the event to Tier Three (USMC TSO). Tier Two shall develop and maintain the SOPs provided to the Tier One personnel. Tier Two shall also be responsible for liaising with CMFS-C Tier Two and Tier Three support to resolve customer support and financial reporting issues affecting the SABRS federated suite of systems.

5.2.3 Functional Support For Mixed-Use And Accounting Systems Associated With Navy OASIS Initiatives: Contractor shall be responsible for providing financial and accounting systems support which includes support in the development of quality systems performance metrics. Assistance includes activities that require the functional understanding of various tools and languages needed to perform data queries to extract financial information from various mainframes (e.g., SABRS) and web-based applications (e.g., SABRS Management Analytical Retrieval Tools (SMARTS)).

5.2.4 System Support: Contractor shall ensure implementation of processes and systems, support user training on new or modified systems functionality, and yield training specific to interpretations of performance measure reports and queries. The contractor will also be responsible for assisting with system testing to include reviewing test scenarios, plans and scripts and conducting user acceptance testing.

5.3 SABRS User Manual Development & Maintenance:

· The contractor shall write, publish, and maintain SABRS/SMARTS accounting procedures, accounting release notifications, accounting application procedures, accounting codes manuals, accounting user manuals, desktop procedures, and Functional Requirement Documents (FRD).

· The contractor shall also maintain Accounting and Financial Standard Operating Procedures (SOPs) that support Accounting Systems, Financial Reporting and data management. Contractor shall assist with standard updating and publishing of SOPs, NAVADMINS, and Naval Messages for SABRS Financial System Suite.

· Contractor shall update and enhance the manual(s) as needed or directed by the Government throughout the life of the contract. The materials detailed herein shall be provided to the government and housed on a government provided website, such as the Navy OASIS, Financial Management Policies and Systems (FMP-43) SharePoint site.

· Contractor shall create maintain and update an inventory of procedures, manuals, notifications, SOPs, Functional Requirements Documents (FRDs), NAVADMINS, etc., that were authored, distributed, or edited and the dates which those materials were authored, distributed, or edited.

· Contractor shall create the Sub-Object Class Codes (SOCC) and Cost Account Codes (CAC) manuals. Provide subject matter expertise and coordination for the Fiscal Codes Configuration Change Board (FCCCB) for the Navy. Attend and facilitate meetings once a year to establish the standardized data elements which will be used for the next year’s execution.

· The contractor shall coordinate the logistics for the meeting, develop the agenda and topics of discussion, and update the SOCC, CAC and any other manuals/policies based on the recommendations by the board.

5.4 Systems Governance Support for Financial Management Systems Environment (e.g. SABRS, SMARTS, PRB):

· Contractor shall support in the preparation of Business Requirements Documents (BRDs) via analyses of functional requirements, emerging technologies, in response to audit Corrective Action Plans (CAP), policy changes (or other Laws and Regulations), and support/participate in Change Management and Software Development activities.

· Contractor shall support the entire change management process for both SABRS and SMARTS from requirements generation through testing, production release, and post release support services.

· Contractor shall provide an inventory of SCRs prepared or tracked, upon which actual effort was expended (for example, does not include listening to someone else’s status call where an SCR number was read off a list, but no action was performed by the Contractor) which will be included in the Weekly Status Report.

· Contractor shall support (functional) ECP creation for changes to PRBuilder.

· Contractor shall support SCR creation for changes to CFMS, FASTDATA, and for all other FIS/MIS which will interface with SABRS.

· Contractor shall assist in software testing, user acceptance testing, and creation/submission test plans and scenarios, test scripts, testing results, and problem ticket reports.

· Contractor shall advise the government and provide subject matter expertise in the proper integration of the PBIS Overlay between PBIS and SABRS.

5.4.1 Applications/interface Requirements Development and Testing Support:

· Contractor shall provide advice and support extraction of accounting data elements through programmatic scripting and mainframe query functions via demonstrated experience with Job Control Language (JCL), Natural, Cognos software solutions, and/or data modeling tools via SharePoint collaboration functions, SQL/Microsoft Access databases and other document-management platforms.

· The contractor shall assist in the performance of program unit testing, systems acceptance testing and submit test discrepancy reports and problem trouble reports. Provide an inventory and status of issues in Requirements Development and Testing for the Weekly Status Report.

· Contractor shall provide subject matter expertise regarding data elements, transaction types, and data extractions for the purpose of liaising with interface partners, adding or eliminating interfaces, or providing functional knowledge for the implementation of Enterprise Service Bus technology or Application Programming Interface (API).

5.4.2 Integration liaison w/ external agencies, external systems, and functional business processes (e.g. IPP, DLA-TS, GEX | P2P, O2C, FRD, Tier I Business Feeder Systems):

· Contractor shall support the assessment of requirements for systems associated with the STARS/SABRS transition and the subsequent vetting of these requirements internally within Navy OASIS and across external stakeholders by identifying proposed courses of action (COAs), coordinating the execution of defined program schedules, producing and managing program schedules, producing and managing program documentation, and assisting in the maintenance, analysis and execution of existing database reporting performance measures, tools, and documentation. These efforts will also require Contractor support in the development and/or improvement of financially-centric web-based tools, reports and content, Financial Improvement Initiative (FII) web-based tools, reports and content, SMARTS (Cognos) tools and reports, and other review and analysis tools and reports required to execute accounting operations, budget execution and audit support. All most recent drafts/non-working copies of schedules, reports, and documentation will be held on government servers, such as SharePoint, except in cases where reports or queries are housed natively in the systems (e.g. SMARTS). An inventory and disposition of these products will be provided in the Weekly Status Report.

5.5 Navy Accounting And Analysis Branch: In fulfilling its accounting oversight role, Navy OASIS publishes exception type reports, affectionately known as the “Deadly Sins”, that reflect transactions requiring detailed investigation, research, and timely correction. Accurate and judicious financial information provides Navy financial managers and senior leadership with a comprehensible financial picture in order to be good stewards of public funds, accurately account for funds spent, and to comprehend the impact when expending limited financial resources. Inaccurate accounting of limited financial resources ultimately leads to lost opportunities to provide critical support to the war fighter. The purpose of this manual is to provide explanation, impact, corrective action, and an overall working knowledge of the “Deadly Sins” reports. Good stewardship of appropriated funds demands the Tri-Annual Reviews (TAR) be conducted in accordance with the DoD Financial Management Regulation (DoD FMR). According to the DOD FMR Volume 3, Chapter 8, Section 0804, Tri-Annual Reviews of commitments and obligations are to be conducted three times a year during each of the four-month Tri-Annual Review periods ending on 31 January, 31 May, and 30 September of each fiscal year. Even though the requirement is to conduct these reviews during these periods, Fund Holders should continuously monitor financial transactions for timeliness, accuracy and completeness and to confirm commitments, obligations, liquidations, accounts payable, and accounts receivable are properly recorded and documented. These reviews should also assess whether commitments and obligations recorded are a bona fide need of the appropriations charged. In addition, the DoD FMR requires Fund Holders to maintain adequate documentation supporting those reviews for 24 months. According to the DCFO’s signed memo dated February 28, 2013, the goal in performing the Tri-Annual Review is to increase the Component's ability to use available appropriations before they expire and ensure remaining open obligations are fairly stated and valid. From a financial audit perspective, one outcome of a well-executed and documented Tri-Annual Review is to provide support for the reasonableness of all open recorded obligations. The Office of the Under Secretary of Defense – Comptroller (OUSD (C)) publishes annual financial operations metrics goals. These metrics track DoD’s progress toward improved and consistent accuracy, efficiency and effectiveness in the financial stewardship areas of accounts receivable, accounts payable, financial management accounting, pay services and electronic commerce.

5.5.1 Key Performance Indicators & Process Analysis:

· Contractor shall develop dashboard and enhanced SMARTS reporting on Key Performance Indicators KPIs). Provide weekly and quarterly KPI review brief generation and analysis.

· Contractor shall provide Financial Statement Compilation support. Provide detailed transaction level support, to include analysis of Universe of Transactions (UoT).

· Contractor will assist in providing explanations to UoT data source generation and SABRS processes. Perform Unadjusted Trial Balance (UTB) to Adjusted Trial Balance (ATB) reconciliation from the General Ledger through DDRS and AFS to the Financial Statements. Support the UTB to ATB reconciliation based on detailed documentation for each journal entry.

· Contractor shall review Journal Vouchers and underlying support documentation.

· Contractor shall perform variance analysis and determine/document root cause of variance in order to mitigate future variances.

· Contractor shall validate opening balances for the year under audit.

· Contractor shall document accounting posting logic and processes in Process Cycle Memorandums (PCMs).

· Contractor shall perform close-out activities, data mining.

· Contractor shall support audit walk-throughs and inquiries as needed. Examples of weekly, monthly and quarterly reconciliations include, but are not limited to: SABRS Detail; Transaction to General Ledger output; SABRS Feeder File to DDRS; DFAS Unadjusted Trial Balance (UTB) to SABRS Trial Balance; DDRS UTB/ATB to SF-133; SF-133 to SBA; FBWT CARS to SABRS DCA.

5.5.2 Prepare & Maintain Abnormal/Overage Accounting & Financial Reports:

· The contractor shall assist in the preparation and delivery of Financial and Accounting Reports.

· Contractor will be responsible for preparing the abnormal financial transactions and conditions reports on a monthly basis.

· Contractor shall prepare reports and document them in an Abnormal Reports Manual, which will be used by the Navy Financial Management community in understanding and employing the various financial reports that are produced by SABRS through SMARTS.

5.5.3 Tri-Annual Review And Year-End Certification Reporting:

· Contractor shall provide operational support and assist with facilitating and support guidance with assisting in annual and quarterly certification and validation processes (i.e. Tri-Annual Review and Year-End Certification).

· Contractor shall assist with training for various e-commerce (paperless) acquisition tools that interface with the accounting system.

· Contractor shall support the Analysis & Review section for various custom reporting and financial management resource office duties

5.5.4 Department Of Defense Financial Operations Metrics Goals Reporting:

· The contractor shall assist in the preparation and delivery of Financial Operations Metrics Goals.

5.5.5 Financial Accounting Support:

· Contractor shall assess and evaluate financial management business practices and oversee financial management improvements that advance accounting information accuracy and timeliness in recording and reporting financial information.

· Contractor shall be required to provide service support to the BSOs in the review of implemented financial processes and report compliance with standard financial processes.

· Contractor shall analyze documentation and alternative procedures for compliance with regulatory and policy requirements and recommend changes in existing policies or procedures based on reviews and site specific deviations from standard processes, organizations, and systems. Furthermore, the Contractor may be required to provide support in reviewing, analyzing and recommending changes to financial statement preparation processes and procedures, analyzing financial processes, and providing recommended performance measures and analyses reports. These are core requirements that are resident primarily at DoN FMO and extended to Navy OASIS for which Contractor support is required.

5.5.6 Data Collection And Reporting:

· Contractor shall support the Government with data calls. Data calls present an administrative requirement to Navy OASIS that should be minimized for both the number and scope of separate data collections. Standing DoN Accounting and Financial data repositories managed by Navy OASIS should be kept current and used as a source of accounting data/information and to minimize the same information being requested from the installations.

· The contractor shall support Navy OASIS with maintaining and assuring the quality of Accounting and Financial data/information on a SharePoint Portal.

· The contractor shall develop “Best of Breed” reports in SMARTs at the enterprise level and for use by each SABRS BSO and existing customer base in order to improve standardized accounting processes and procedures across the DoN.

· The contractor shall be responsible for developing and improving the 1071 Summary, and ensuring the accuracy of the contents prior to transmission to external business partners and interfaces.

· The contractor shall develop and disseminate financial reporting from an Enterprise Portal.

5.6 Navy Accounting Solutions Branch

5.6.1 Process Improvement & Sustainment:

· Contractor shall provide process improvement implementation based on audit findings.

· Contractor shall perform internal control remediation in regards to system and accounting process findings. Contractor shall assist government with ensuring compliancy with Treasury Financial Regs, OMB Circulars A-11, A-123, A-136, OSD Guidance, DoD Financial Management Regulations (FMR), DFAS Guidance, MFMIP/FSIO, DoN Financial Guidance, CFO Act of 1990, GAAP, FASAB, OUSD(C) Directives.

· Contractor shall monitor financial activity integrity and review and reconcile monthly & quarterly reports.

5.6.2 Substantive Procedures: Substantive procedures are intended to create evidence that an accountant assembles to support the assertion that there are no material misstatements in regard to the completeness, validity, and accuracy of the financial records of an entity. Thus, substantive procedures are performed by an accountant to detect whether there are any material misstatements in accounting transactions. As the Navy’s SABRS experts, Contractor may be required to provide support to implement process improvements based on audit findings and to support and strengthen the DoN financial statements.

5.6.2.1 Pursuant to 5.6.2, Contractor shall assist with testing classes of transactions, account balances, and disclosures agreeing the financial statements and accompanying notes to the underlying accounting records and examining material journal entries and other adjustments made during the preparation of the financial statements to include quarterly Statements of Budgetary Activity (SBA) and the Annual Financial Report (AFR).

5.6.2.2 Pursuant to 5.6.2, Contractor shall assist with examining documentation indicating that a procedure was performed, re-performing a procedure to ensure that the procedure functions as planned and inquiring or observing regarding a transaction. Examples of substantive procedures include, but are not limited to: Accounts receivable confirmation; Inquire of management regarding the collectability of customer accounts; Match customer orders to invoices billed; Match collected funds to invoices billed; Confirm the calculations on an inventory valuation report; Observe fixed assets; Confirm accounts payable; Examine accounts payable supporting documents; Confirm debt; Analytical analysis of assets, liabilities, revenue, and expenses.

5.6.2.3 Contractor shall be responsible for developing and disseminating, to include Super-User training thereof, Standardized Closeout Procedures for financial closing periods in SABRS.

5.6.3 Reversions Minimization:

· The contractor shall monitor business processes and financial systems related to SABRS Suite throughput, and provide an approach to minimize reversions.

· The contractor shall focus on increasing the DoN’s spending capability inherently through minimizing the risk of reversions.

· The contractor shall also focus on decreasing Unliquidated Obligations (ULOs), and provide analysis and validation on a quarterly basis. Testing shall be conducted of ULO samples to determine if the obligation on the accounting records is still valid, and the services/goods are anticipated to be received in a reasonable timeframe.

· The contractor shall develop Corrective Action Plans (CAPs) based on the findings noted during testing. CAPs shall focus on the condition, criteria, causative factors and recommendations for mitigating future risk. The contractor shall provide training to users based on lessons learned to minimize the risk of reversions going forward.

5.6.4 SABRS Functional Data Management and Advisory Services:

· The contractor shall perform Analysis of Requirements and Develop Queries, and/or Data Anomaly Programs and/or Data Process to Data Integrity (System Internal Control Checks).

· The contractor will assist in data mining to provide accounting data for analysis, produce financial accounting management reports, and recommend accounting policy, procedural and process changes for corrective action for DoN/USMC system and accounting functions. All query results, programs, reports and documentation will be housed on government servers. An inventory and disposition of these products will be provided in the Weekly Status Report.

5.6.5 SABRS Transition Post-Deployment Support Coordination Service:

· The contractor will coordinate with the STARS/SABRS Transition Project Office (FMP-4) and associated staff in providing Post Deployment Support for STARS/SABRS transition efforts for Deployments occurring within the POP.

· The contractor shall assist Navy OASIS with the large increase in the Navy user base and business transacted through SABRS, and act as representative for the functional owner (Navy OASIS) of the integrated DoN SABRS solution providing BSO support.

· The contractor shall assist the project office in using the previously identified trend analysis to recommend and make updates to existing training, mirroring the work stream with which trend analysis for help-desk issues would be used to identify and develop BRDs.

5.7 Transition-In Support

5.7.1 Facilitate the accomplishment of a seamless transition from the incumbent to the contractor. Transition-In services shall begin on the effective date of the award and shall be complete on the date which is thirty (30) days after the effective date when the contractor will assume full responsibility for Tasks. A Draft Transition Plan shall be provided to the Government within five business days following effective date of the award. The plan shall describe, at a minimum, how the contractor will address the items in section 5.7 of this PWS. Updates to the plan shall be submitted if needed and in coordination with the Government on a weekly basis until Transition-In is complete.

5.7.2 Identify Points of Contact (POCs) for liaison between the Government, the prime contractor, and other contracted industry partners to ensure a proper and orderly transition and transfer of services and assets between the parties cited.

5.7.3 Ensure minimum disruption to vital Government business. The contractor shall ensure that there shall be no service degradation during or after transition.

5.7.4 Establish an overview of the transition efforts and describe the activities to transition, which shall include a schedule with milestones by activity.

5.7.5 Obtain transition knowledge and information regarding risk or problem areas from contractor personnel or Government personnel.

6. Deliverables

Annual Work Plan The Contractor shall provide Navy OASIS with a draft annual work plan within two weeks after contract award. A given work plan will detail specific actions to be performed for the performance period in support of each of the efforts described, and related schedule of deliverables. A final work plan shall be delivered to the Government within two weeks of receiving the Contracting Officer’s Representative (COR) comments on the draft work plan.

Annual or Closeout Summary Report The Contractor shall provide Navy OASIS with an annual report summarizing all work performed and completed under this Performance Work Statement (PWS). A given annual summary report will be utilized to maintain a knowledge base and provide a general overview of the Contractor’s accomplishments, as they pertain to the tasks identified herein, in the preceding performance period.

Planning Meeting Agenda The contractor shall submit an agenda for a monthly planning meeting each month on all anticipated efforts in sections 5 of the PWS. The meeting agenda is the plan for a meeting that will last no more than two hours. At a minimum this meeting will include, addressing status and providing a Plan of Actions and Milestones (POA&M) of the planned effort to be furnished along with the commensurate efforts from section 5&6 of the PWS that the contractor intends/plans to accomplish during the next calendar month.

Planning Meeting Minutes The contractor shall provide minutes from the monthly planning meeting within five days after the meeting is held. The minutes shall reflect a chronological, detailed explanation of the topics discussed, the critical decisions made and efforts from section “5” of the PWS to be focused on, and agreed-to timelines. The minutes shall also provide a record for future efforts and shall follow the agenda format with more detailed notes under each section. The minutes will inform updates of the monthly POA&M.

Weekly/Monthly Status Report The contractor shall provide the weekly/monthly status report which covers at a minimum each of the areas referenced in section 5 of the PWS and the POA&M. This report shall assess the status of each planned effort referenced in the minutes, and performed in accordance with the PWS. This report shall include an explanation of the efforts that have been completed, the efforts that are currently being worked on and the efforts that will be worked on over the next week/month.

The report shall address specific accomplishments for each effort referenced in the minutes and explain any deviations from the minutes. The report should also include any communications that occurred throughout the week/month with other Government employees and/or contractors involved with SABRS efforts.

The report shall include any barriers that the contractor is facing, as well as recommendations for overcoming such barriers. The report shall facilitate the agenda for upcoming planning meetings, discussion during the weekly/monthly planning meetings and allow for effective project management. All projects designated by the Director, Financial Services will have their own separate updates independent of this monthly status report, but will provide a short summary for this report.

Other Deliverables and Work Products The Contractor shall provide other deliverables and work products as described in the sub-tasks of Sections 2 and 5 of this PWS. These shall be provided in accordance with the PWS and/or as required by the Government.

7. Labor Category Description/Requirements:

The Offeror shall provide personnel that have knowledge of DoD policy in the areas of systems, finance, and procurement to include: knowledge of systems architecture, process design, SABRS, SMARTS, CFMS, PR Builder, and other systems and their implementation, solution analysis, blueprinting, prototyping, training, testing, data standards, data cleansing and reporting, interface development, systems audit to key DoD enterprise systems.

A description of the skills and experience level for each labor category is provided below:

1. Program Manager:

The Program Manager has extensive experience in strategy, business and action planning, process, and productivity improvement and delivery of successful solutions. The Program Manager provides expert guidance and knowledge management. The Program Manager possesses demonstrated advanced project management and/or industry skills. They will manage either large or numerous teams through the lifecycle of the contract. Other work will include providing guidance and leadership to the contracting team, providing expert advice and counseling to clients on critical issues, managing client relationships, issues and feedback and delivering completed quality products within contract provisions and project resources.

Experience: Fifteen (15) years in a leadership capacity within management consulting or the federal government, including at least fifteen (15) years of experience in various aspects of Federal Government financial systems operations with the knowledge of related systems of the SABRS Suite of systems.

Education: Bachelor’s degree from an accredited college or university and an equivalent professional certification in Program/Project Management such as the PMP. An additional 6 years of Management experience can be substituted for an MS/MBA degree or professional certification.

2. Facilitation Specialist:

Possesses extensive knowledge or demonstrated experience in business process improvement projects, facilitating project teams, and developing team objectives. Possesses knowledge and experience with providing documentation planning and support. Demonstrates proven experience in working in team environment; ability to meet and operate under deadlines; ability to prepare and deliver quality documents, presentations, and briefings. Ensures adequacy, accuracy and quality of relevant deliverables. Acts as liaison to FMP Branch Chiefs and BSO Comptroller Staff.

Experience: At least six (6) years of relevant experience performing facilitation, business process improvement, and/or facilitating project teams.

Education: At least an Associates Degree (AA) in communications, business, or other relevant technical field. An additional 3 years of specialized experience may substitute for degree requirement.

3. Financial Systems Architect:

The Financial Systems Architect has experience in designing business and technical architectures, business processes, and technical solutions across multiple organizational functions. The Architect combines a range of industry knowledge with business process and technical data modeling experience to break down conceptual, vaguely defined business and technical challenges into manageable and actionable performance improvement plans. Review and analyze programmatic roadmaps and blueprints developed by various Financial Management systems and their Program Offices to ensure audit ready business environment. Provide substantive quantitative data to support the recommendations/changes to system design plans to ensure that the particular operational requirements and priorities are considered. In conjunction with the FM Business Process Leads and Audit Leads, this position supports various business and technical management decisions to support successful execution of the DoN’s target enterprise business/IT environment.

Experience: At least six (6) years of relevant experience designing business and technical architectures, business processes, and technical solutions.

Education: At least an AA in IT, business, or other relevant technical field. An additional 3 years of specialized experience may substitute for degree requirement.

4. Systems Accountant with a Financial Statement Auditing Background:

A systems accountant is experienced in reviewing and evaluating all the financial systems as they relate to the production of timely, accurate and supportable financial statements. The success of a systems accountant depends largely on his/her combined expertise in understanding and applying the concepts of information technology, accounting and financial management, financial statement auditing, and guidance and regulations directed by authoritative sources.

The systems accountant assigned to this position will support the FMP staff in the evaluation of source accounting systems, and detailed financial transactions to assist in determining the completeness and accuracy of the financial transactions, and whether the transactions adhere to official DoN business processes, Generally Accepted Accounting Principles (GAAP), and other authoritative sources. Knowledge of the United States Standard General Ledger (USSGL) and the business processes in support of the DoN financial statements is preferred.

The Systems Account will assist FMP managers with determining the impact of new functional accounting requirements. To meet these requirements, System Accountants are required to work with the various system owners to identify, develop, and implement system changes.

Experience: At least six (6) years of relevant experience reviewing and evaluating financial systems as they relate to production of financial statements.

Education: At least an AA in Accounting, IT, business, or other relevant technical field. An additional 3 years of specialized experience may substitute for degree requirement.

5. Data Analyst:

A data analyst will be involved in the planning, development, implementation, and administration of systems for the acquisition, storage, and retrieval of data. The data analyst will be analyzing and defining data requirements and specifications; designing, normalizing, developing, installing, and implementing databases; maintaining, monitoring, performance tuning, backup, and recovery of databases; installing, configuring, and maintaining database management systems software; analyzing and planning for anticipated changes in data capacity requirements; developing and administering data standards, policies, and procedures; developing and implementing data mining and data warehousing programs; evaluating and providing recommendations on new database technologies and architectures; and/or ensuring the rigorous application of information security/ information assurance policies, principles, and practices ensuring the rigorous application of information security/ information assurance policies, principles, and practices in the delivery of data management services. In conjunction with the FM Accounting Leads and Audit Readiness Leads, this position supports various business and technical management decisions to support successful execution of the DoN’s business/IT environment as it relates to the creation of timely, accurate, and supportable financial statements.

Experience: At least four (4) years of relevant experience planning, development, implementation, and administration of systems for the acquisition, storage, and retrieval of data.

Education: At least an AA in data science, IT, or other relevant technical field. An additional 3 years of specialized experience may substitute for degree requirement.

6. Information Systems Manager:

The systems analyst will be providing support for the planning, designing, and implementing of new and improved information systems to meet the business requirements for FMP. The systems analyst is required to support the FMP team leads in analyses that defines opportunities for new or improved business process solutions; identify and specify requirements; developing overall functional and systems requirements and specifications; comparative analysis of financial systems; conducting feasibility studies and trade-off analyses; preparing business cases for the application of IT solutions; defining systems scope and objectives; developing cost estimates for new or modified systems; ensuring the integration of all systems components; e.g., procedures, databases, policies, software, and hardware; planning systems implementation; and/or ensuring the rigorous application of information security/ information assurance policies, principles, and practices to the systems analysis process. Assist government lead with tracking and implementing systems changes.

E…