CXE Support_PWS_Draft.docx

1. PART 1: GENERAL INFORMATION

Mission and Background

The Comptroller XML Exhibits (CXE) tool requires the continuation of support to continue continual application enhancements, prepare for and support the FY 2027 Budget Estimate Submission (BES27) through the FY 2031 President’s Budget (PB31) request budget cycles. The contractor will provide expert application and Financial Management Regulation (FMR) user support, provide data from BES and PB cycles and support for ingestion into both DTIC and OUSD(C) analytics tools, sustain the cybersecurity and functionality of application, and complete major architectural (Front-End and Back End) upgrades as-needed to remain as closely aligned with DTIC's Architectural Baseline as possible.

BACKGROUND

The Comptroller XML Exhibits was first implemented during the FY 2009 Budget Estimate Submission cycle for Research, Development, Test, and Evaluation (RDT&E) Budget Exhibits. The CXE application expanded to include all RDT&E Budget and Procurement exhibits in 2012. The application has been used in 48 separate Program Objective Memorandum (POM), Budget Estimate Submission (BSE), President’s Budget request and Amended budget submission cycles and is an essential component within the Department of Defense's (DoD) Budget Formulation process. It integrates over 600 individual RDT&E and over 70 individual Procurement budget exhibits created by all DoD components into standard, well formatted, validated, and math checked Justification Books, suitable for submission to Congress. Mandated by policy, the Budget Estimate Submission is required to be submitted to the Office of the Under Secretary of Defense, Comptroller (OUSD(C)) each September and mandated by law, the President’s Budget request must be delivered to Congress every year during the first week of February. Prior to CXE, the primary tools for creating Budget Exhibits for Congress were Microsoft Word and Microsoft Excel. The process created a high degree of inconsistent and inaccurate exhibits across the DoD. The implementation of the CXE application created consistent math and format checked exhibits for all DoD Services (Army, Navy, Marine Corps, and Air Force) and Agencies. DTIC, through its contractor support, has developed and implemented the complete set of RDT&E and Procurement exhibits, including the Shipbuilding and Conversion, Navy (SCN) Procurement budget exhibits, and supported multiple Office of the Secretary of Defense Federal Financial Management Regulation (OSD / FMR) reform efforts.

Over the course of several years, CXE was updated to parallel RDT&E user interface with the layout of the actual published exhibits so that entering data is more intuitive for users and deployed a SIPR classified network instance giving the Intelligence Community the ability to submit XML based classified budgets which was used for the first time during the Budget Estimate Submission for FY 2017. CXE was also enhanced to include further Data Validation Tools and an automated workflow process that moves finished exhibits to OUSD(C) Analysts and the Office of Management and Budget (OMB) Examiners for final review prior to submission to Congress. In more recent years, CXE has been configured to operate in and deployed to an Azure Cloud environment for both its NIPR and SIPR instances while continuing to deliver workflow and tracking tool enhancements requested by the OUSD(C) Product Owner.

Scope

This contract is designed to provide comprehensive support in the areas of administration, communications, cybersecurity, technical services, financial management, analytical services, joint/interagency organization, and program advisory services. These efforts are aimed at assisting the Office of the Under Secretary of Defense Comptroller (OUSD(C)) in fulfilling their missions and objectives.

This initiative represents a continuation of ongoing work that supports the Comptroller's XML Exhibits (CXE) tool. The Defense Technical Information Center (DTIC) is seeking non-personal services for this purpose. The selected contractor will be tasked with maintaining and monitoring the current functionality of the CXE tool, in addition to designing and developing necessary enhancements to improve its performance.

This PWS documents the professional services required to support the CXE tool. To meet these requirements, the Contractor shall perform the tasks articulated in Section 5 (Performance Requirements). Tasks under this Contract may also include support to other derivative offices of OUSD(R&E) that may result from reorganization.

The Contractor shall coordinate and collaborate only directly with the DTIC PM and COR in regard to the CXE tool support for over 400 individuals in OUSD offices, Joint Staff, Services, other defense agencies, allies, academia, and industry as required. The Contractor shall be directly responsible for ensuring the accuracy, timeliness, and completion of all requirements under this PWS.

1. PART 2: ACRONYM DEFINITIONS

Definitions:

CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

CONTRACTING OFFICER (CO). A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S.

Government appointed by the CO to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

DELIVERABLE. Anything that can be physically delivered but may include non-manufactured things such as meeting minutes or reports.

PERFORMANCE REQUIREMENTS SUMMARY. Includes the tasks, service or requirement being measured, mapping back to the performance work statement, including the specific paragraph in the PWS. a performance indicator or quality standard PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

QUALITY ASSURANCE. The Government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

WORK WEEK. Monday through Friday, unless specified otherwise.

1. PART 3: GOVERNMENT FURNISHED ITEMS AND SERVICES

Equipment

The Government will supply the necessary equipment required to complete the tasks in the PWS. Government-furnished property (GFP) will be issued with the approval of the Contracting Officer Representative (COR), and a detailed record of all GFP issued will be maintained. The Joint Service Provider (JSP) will assist with Government-furnished information technology (IT) equipment, including laptops and smartphones, as applicable.

Common Access Cards (CACs) will be issued by the Government on an as-needed basis. CACs are considered Government property and must be returned immediately upon expiration of this Task Order (TO) or upon employee termination. At the request of the Government, or upon completion of the TO, the Contractor must promptly return all GFP. The Contractor shall safeguard all GFP in the designated work areas and establish a Government Property Management Plan in accordance with FAR 52.245-1.

Utilities The Government will provide all utilities in the Government facility to be available for the Contractor’s use in performance of tasks outlined in this PWS. The Contractor shall instruct personnel in utilities of conservation practices.

Facilities When the Government provides facilities as specified under Section 10.2 (Place(s) of Performance), the Government will provide on-site workspace and office equipment, including a desk, chair, computer, printer, copier, telephone, and necessary operating supplies, to contractor staff to support the tasks outlined in the Performance Work Statement (PWS). The Contractor will be allowed access to the Government's facilities, as specified in Section 6 (Administrative Requirements). The Contractor is responsible for maintaining the provided workspace areas in a clean and orderly condition.

Information The Government will provide specific information, materials, and forms related to the task. The Contracting Officer's Representative (COR) will serve as the point of contact for identifying any required information that needs to be supplied by the Government. This information may include Standard Operating Procedures and the following Department of Defense (DoD) manuals:

- DoD Manual 5200.01, "DoD Information Security Program: Protection of Classified Information"

- DoD Manual 5200.2-R, "Personnel Security Program"

- DoD 5220.22-M, "National Industrial Security Program Operating Manual" (NISPOM)

The Contractor's performance on this Task Order (TO) may require access to and use of materials and information, such as studies, reports, and key data, which are proprietary to a government agency or contractor. The dissemination or use of this information, outside of the specific effort, could harm the interests of the Government and/or other parties. If access to such information is deemed necessary, the Contractor will be required to sign a non-disclosure agreement (NDA) before starting the work. Upon request from the Government or upon completion of this TO, the Contractor must immediately return any information provided by the Government.

1. PART 4: Constraint

Personal or company use of phones, utilities, computers, printers, or copiers not directly related to the required services under this contract is strictly prohibited. Contractor shall not remove any government-furnished equipment or supplies from the worksite without approval from the COR. The Contractor shall only use government-furnished facilities, equipment, and supplies to accomplish the tasks required under this contract. The Government will not reimburse the Contractor for any supplies.

The Contractor shall provide professional technical and analytical experts with appropriate skills, recent and relevant experience, and qualifications to provide administrative, communications, maintenance and sustainment, technical, financial, analytical, joint/interagency organization, and program advisory services support to DTIC. The tasks described below and in Technical Exhibit 1 (Labor Categories) dictate the types of, and essential skills for Contractor personnel to accomplish the required work.

To accomplish the work in this PWS, the Contractor shall identify a Program Manager (PM) (see Task 5.1.1, Program Management) who shall be responsible for the work performed under this contract; and may execute Task 5.1.1 responsibilities as additional duties to other responsibilities assigned under this TO. The contractor shall determine the exact composition of each team based on the specific tasks described in the PWS.

Support to OUSD (C) will be in the following specific task areas:

The Contractor shall

· Provide a single point of contact for all contract supervision and performance related matters. The Contractor’s Point of Contact shall ensure that all requirements are performed and that deliverables are submitted.

· Schedule a Kick-Off meeting within seven (7) business days of contract award. The kick-off meeting shall include a Project Management Plan (PMP) as described in this section. The kick-off meeting may be accomplished by teleconference or virtual environment based on current local regulations for gathering in a pandemic environment. The Government will approve the kick- off meeting format.

· Deliver a PMP that details the technical approach to meet all deliverables. The Contractor shall deliver the final PMP within fifteen (15) business days of the contract award. The plan must incorporate the technical approach chosen to fulfill the requirements and shall be submitted for review and approval by the Government. The PMP plan shall describe, in detail, the Contractor’s technical approach for each aspect of the tasks outlined herein. It shall include discussion of risk management, quality, technical management approach, quality assurance, communications, staffing, and schedule.

· Prepare monthly hours worked report for each Full Time Employee and for each Contract Line Item Number.

· Prepare a weekly activity report for software development activities in progress and completed.

5.1.1.3 Customer Support

Contractor shall support the over 400 registered DoD users, from the DoD Services and Agencies, who use the CXE application to prepare their budgets require a considerable amount of customer support. This support consistently begins at least six (6) weeks prior to submission deadlines and often requires support during off-duty times weekdays and weekends. Service/Agency users change regularly, and new users of the application require the most support.

· Support the customer and deploy fixes as necessary ugs during the budget submission.

· React frequently to application changes requested by OUSD (C) while budget submissions are underway.

The Contractor shall implement performance and functional enhancements to the CXE application as requested by the OUSD(C) Product Owner.

5.1.2.2 Collaboration for Enhancements of the CXE Application Contractor shall collaborate with the DTIC to document enhancements requested by the OUSD(C) Product Owner (PO), maintain a roadmap and backlog of customer requested performance and functional enhancements, and deliver enhancements in accordance with the roadmap.

5.1.2.3 Application Quality Assurance

Contractor shall:

· Develop and maintain software test procedures that ensure compatibility with DTIC automated testing for evaluating both existing and newly developed systems, system modifications and software defect repair

· Develop and maintain software manual test cases and automated test scripts that are compatible with DTIC’s automated testing architecture tools for performing independent testing of system/software change requests.

· Conduct functional tests on both the web application and web service to verify that the system change requirements are satisfied and standards are implemented.

· Coordinate and provide strategies for conducting load testing to be carried out by DTIC operations. Establish and maintain a software documentation library for all systems’ documentation, to include system specifications, user documentation, standards, and procedures.

· Develop software for deployment in alignment with the DTIC and DoD Enterprise DevSecOps Strategies. Deployment methods must also be in alignment with the DTIC cATO Strategy.

· Develop and support documentation for the required security documentation including the application security plan.

The Contractor shall:

· Plan, roadmap, schedule, develop, and deliver maintenance and sustainment updates including maintenance and sustainment activities including but not limited to:

· Document issues reported by CXE Application users and delivers break fixes.

· Review software and architecture security findings and make changes to ensure Confidentiality, Integrity, and Availability of the CXE Application and its data

· Supports software architecture change decisions for the CXE application in response to updates to DoD/Agency policies, DoD legislation, software development community tools, and technologies.

· Remediates CAT-I or CAT-II vulnerabilities in accordance with DoDI 8530.1 Sections 3.4 & 3.5.

· Remediates vulnerabilities or delivers a POA&M within 21 calendar days of vulnerability notification by DTIC Cybersecurity or DoD Cybersecurity activities including but not limited to JFHQ-DoDIN.

· Ensures compliance with the most current revision of the DISA Application Security and Development Security Technical Implementation Guide (STIG).

· Ensures compliance with NIST 800-53 Rev 5, “Security and Privacy Controls for Information Systems and Organizations.”

· Ensures audit logs produced are in compliance with OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents.”

5.1.3 Task 3: Budget Estimate Submission and President’s Budget request submission support The Contractor shall prepare for and support the 2027 Budget Estimate Submission through the 2031 President's Budget request submission cycles.

The Contractor shall:

· Perform Business Process Reengineering (BPR) methodologies to capture functional requirements.

· Define business rules within the XML validation code that ensures budget exhibits' data and formats adhere to the DoD FMR.

· Refine existing RDT&E and Procurement budget exhibits schemas, Extensible Stylesheet Language Transformations (XSLTs), XML Schema Definition (XSDs), business rules and code base to accommodate lessons learned and requirements generated from each successive budget submission.

· Document resulting functional requirements in a format and to a level of completeness suitable for development.

· Document resulting business rules in a format suitable for the Comptroller Community as well as developers.

· Participate in Agile development methodology, including development of product backlogs, participation in sprints, reviews, and other meetings as requested by the Government Program Manager (PM).

· Develop and maintain the XSDs and XSLTs, Database Design Model, Domain Object Model, User Interface, and Web Services in the UNIX operating system and MySQL database hosted at DTIC.

· Develop test plans and perform unit and integration testing in local and development environments, as well as full regression testing in IL4 and IL6 Cloud staging and production environments while ensuring compatibility with automated testing. Perform routine maintenance, defect repair, updates to code resulting from lifecycle upgrades to the platforms that support the software application.

· Perform administrative record keeping, journals, transaction logs, and updating of architecture documentation IAW the DoD Chief Information Officer DoD Architecture Framework (DoDAF) requirements.

· Provide similar support for the maintenance and modification of all previously implemented years RDT&E and Procurement exhibits.

5.1.4 Task 4: Data Analytical Support

The Contractor shall:

· Annually integrate new data into the current data analytics and visualization suite for CXE analytics.

· Design and create ad hoc or customized reports using current data analytics and visualization tools, as needed.

· Provide new data from President’s Budget cycles in a format usable for ingestion into Non-Secure Internet Protocol Router (NIPR) network and Secret Internet protocol Router (SIPR) network versions of the current analytics and visualization tools, Horizons Beta analytics application datalake ingestion point and Advana.

· Support current and future processes for the extraction and submission of budget data to OUSD(C) for Advana ingestion and to DTIC for analytics and search capability integration.

· Populate the existing analytics dataset annually, starting with President’s Budget request 2027 for RDT&E and Procurement budget exhibits.

· Support the extraction and delivery of data in JSON and XML formats.

· Recommend and implement resolutions to the differences between the data provided in XML across these cycles.

· Provide ad hoc query support to the OUSD(C), DoD Services and all DoD Agencies as required.

· Provide data mapping services to other DoD Services and DoD Agencies when requested (Budget Estimate Submission mapping requires need to know).

· Analyze customers' needs and create ad hoc and customized reports, as needed.

· Prepare data from pre-XML reports to make it available for expanded trending analytics.

· Provide business analyst support for documentation, systems requirements and training material for all components of the software including the User Interface (UI).

· Analysis of business requirements derived from the DoD Financial Management Regulation (FMR) and client needs that will be vetted by the Comptroller.

· Conduct interpretation of analysis that defines the structure of related budget data for creation/modification of the associated XML schema and UI.

· Design of prototype templates used in both generating PDF documents from XML data combined with XSL and XSLT, and UI development.

· Composing and documenting business rules to be enforced by the software schema and UI, updated regularly based on system changes and new requirements.

· Assisting in all aspects of XML/UI testing, including, but not limited to, accuracy of mathematical computations, data validation and business rules enforcement, XML to PDF conversion, and the generation of budget Justification Books.

5.1.5 Task 5: Financial Management Regulation Revision Support and CXE application alignment The Contractor shall:

· Provide DoD 7000.14-R Department of Defense Financial Management Regulation (FMR) revision support and align the CXE application with DoD 7000.14-R DoD FMR changes.

· Modify existing exhibits and develop new, sample exhibits that illustrate the future model.

· Update the schema, code base, business rules, user interface, and Web Services.

· Prepare briefings for joint OUSD(C) and DoD Component working groups that describe the current model and alternative future models.

· Prepare and submit to the OUSD Comptroller a change page for the Financial Management Regulation (FMR) when changes are required. The change page will denote any recommended changes to FMR wording such as updates to budget exhibits, funding thresholds, etc. All changes must be ready for publication, detailing the exhibit format, data definitions, and business rules that must be followed based on the FMR, for incorporation into the application.

· Contractor shall provide updates to the automation of business rules documentation and incorporate into site downloads section of the user interface.

· Contractor shall perform CXE application code platform lifecycle updates and upgrades.

5.1.6 GOVERNMENT OPTIONAL Task 6: Develop New User Interface and Migrate to SaaS Back End

5.1.6.1 Subject to Government decision to fund and award this optional task, the Contractor shall:

5.1.6.1.1 Maintain the current CXE User Interface, which is built with Apache Tapestry, while upgrading the entire application’s user interface to Angular. Examples of components included in this upgrade are:

- Site Landing Page

- Complete RDT&E User Interface

- Entire Procurement User Interface

- Justification and Master Justification Book Wizards

- Application Administration Sections

- Business Rules Administration Sections

5.1.6.1.2 Maintain the current containerized CXE Back End served via Apache Tomcat servers while. migrating the application code base back-end services to serverless function components compatible with a Software as a Service cloud-based architecture.

Once this option is required, a notice will be provided to the Contractor. Subsequently, the CO will modify the TO by exercising the Optional Labor Task CLIN to accommodate the tasks under section 5.1.6. The Optional Labor Task CLIN is set up as a Firm-Fixed-Price (FFP) Level-of-Effort (LOE) CLIN. Payment for these services will follow an FFP LOE structure, utilizing the labor rates negotiated at the time of award for each period of performance associated with the CLIN.

5.1.7 Task 7 Surge Support

CXE support anticipates the need for emerging in-scope requirement changes in response to changes in OUSD (C) mission. The Contractor will be required to provide additional intermittent support upon request via a surge contract line-item number (CLIN). The Surge CLIN will cover support where extra effort is required to take on short-term tasks or increase the level of effort under any of Tasks 1-6. Surge efforts may result from congressionally mandated reports, briefings, or studies, DoD directed tasks, or other obligations imposed on the program for which the anticipated level of effort described in tasks 1-6 above would be insufficient. The surge effort requires Contractor support with significant experience or specialized technical capabilities. Upon identifying a surge, the Government will inform the Contractor in writing and issue a request for proposal (RFP). Subsequently, the CO will modify this Contract by introducing the Surge CLIN to accommodate the surge requirement. The Surge CLIN will be set up as a FFP LOE CLIN. Payment for these services will follow an FFP LOE structure, utilizing the labor rates negotiated at the time of award for each period of performance associated with the Surge CLIN.

The Contractor shall invoice MONTHLY with description to include invoice performance period, short description of services completed and any other information required by the COR after email submittal of monthly status report to the CO and COR.

The Contractor shall possess and maintain a SECRET (S) facility clearance from the Defense Counterintelligence & Security Agency (DCSA) at all times during performance of the contract/task order. Reference DD254 for details. The Contractor’s employees, performing work in support of this contract shall have been granted a SECRET security clearance from the DoD Central Adjudication Facility (DoD CAF).

6.2.2 Personnel Clearances (PCL)

All contractor personnel, to include part-time personnel and subcontractors, shall possess at minimum a DoD Interim SECRET clearance at time of the proposal submission, and maintain the level of security required for the life of the contract. Table 1 below depicts the security clearance requirements for each task.

Table 1. Personnel Security Clearance Requirements

6.3 Security Requirements

The Contractor shall comply with all security requirements contained in this contract, DD Form 254, DoD Contract Security Classification Specification, and the terms and conditions set forth in FAR clause 52.204-2, Security Requirements, incorporated by reference. Security procedures shall be in accordance with DoD policies.

6.3.1 Physical Security

The Contractor shall be responsible for safeguarding all government equipment, information, and property provided for Contractor use. The Contractor shall secure government facilities, equipment, and materials at the close of each work period.

Physical access to federally controlled facilities will be required and identity verification will comply with FAR clause 52.204-9 Personal Identity Verification of Contractor Personnel. The Government will provide facility access, building identification, and systems access required for personnel to perform their duties in accordance with existing OSD facility access security procedures. The Contractor shall comply with all Washington Headquarters Service (WHS) and OSD Operational Security guidelines and directives and shall complete OSD mandatory training on an annual basis for Information Assurance and Security, Controlled Unclassified Information (CUI), and Cyber Awareness.

The contractor will be issued a Common Access Card (CAC) and facility accesses, in the performance of this contract.

6.3.2 Keys, Badge, and Common Access Card (CAC) Control

The Contractor shall establish and implement methods of making sure all badges and CACs issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. The Contractor shall prohibit the use of government issued keys/key cards by any persons other than the authorized Contractor personnel. The Contractor shall prohibit the opening of locked areas by Contractor personnel to permit entrance of persons other than authorized Contractor personnel engaged in the performance of assigned work in those areas, or personnel authorized entrance by the CO.

NOTE: No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key, badge, and CAC control that shall be included in an established Quality Control Plan (QCP). Such procedures shall include prompt return of any issued keys, badges, and CACs by personnel who no longer require access. The Contractor shall immediately report any occurrences of loss or other issues to the COR.

6.3.3 Lock Combinations

The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when contractor personnel having access to the combinations no longer have a need to know such combinations.

Information made available to the Contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written consent of the CO. Contractor and/or Contractor personnel shall not divulge or release data or information developed or obtained in performance of this effort until made public by the Government, except to authorized government personnel or upon written approval of the CO. The Contractor shall not use, disclose, or reproduce proprietary data that bears a restrictive legend other than as required in the performance of efforts within this contract. Nothing herein will preclude the use of any data independently acquired by the Contractor without such limitations nor prohibit an agreement at no cost to the Government between the Contractor and the data owner which provides for greater rights to the Contractor.

The Contractor agrees to assume responsibility for protecting the confidentiality of government records, which are not considered public information. Contractor personnel to whom information may be made available or disclosed shall be notified in writing by the Contractor that such information may be disclosed only for purposes and to the extent authorized within the contract. The Contractor shall not release any information received through this contract to the public, media, or other unauthorized persons or organizations (e.g., posting information to a public website) unless the Government has conducted the appropriate security review and granted written approval. Performance of this effort may require the Contractor to access and use data and information proprietary to a government agency or government contractor, which is of such a nature that its dissemination or use, other than in performance of this effort, would be averse to the interests of the Government and/or others. The Contractor will sign non-disclosure agreements (NDAs) at the beginning of this contract certifying that none of the information received through their work on this contract many be disseminated in any manner other than as allowed in the order.

6.3.6 Identification of Contractor Personnel

All Contractor personnel attending meetings, answering government telephones, and working in other situations where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are government officials. They must also ensure all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed. Contractor personnel will be required to obtain and wear badges in the performance of this service. Contractor personnel that need access to government systems and work locations will be issued a CAC as required.

6.4 Non-Personal Service Statement

Contractor personnel performing under this PWS will be managed, directed, and supervised at all times by the Contractor’s PM. The Contractor’s PM will ensure Contractor personnel properly comply with the performance work standards outlined in this PWS. Contractor personnel will perform their duties independent of, and without the supervision of, any government official. The services and performance required under this TO are determined to be not inherently governmental. The Contractor shall not perform or give the appearance of performing inherently governmental functions as described in FAR Part 2 and Subpart 7.5, and all applicable DoD policy. The tasks, duties, and responsibilities set forth in this TO may not be interpreted or implemented in any manner that results in any Contractor employee creating or modifying Federal policy, obligating the appropriated funds of the United States (U.S.) Government, overseeing work of Federal employees, providing direct personal services to any Federal employee, or otherwise violating the prohibitions set forth in FAR Subparts 7.5 and 37.1. The Government will perform the inspection and acceptance of the deliverables provided.

The Contractor shall provide highly qualified, team oriented, and innovative professionals dedicated to the development and implementation of CXE Programs and services. The Contractor shall function as a coordinated support team in grasping complex concepts and technologies, applying critical and innovative thinking, communicating effectively, and working seamlessly across the breath of functional areas. All Contractor personnel proposed shall meet the qualifications set forth as identified within the PWS.

6.5.2 Training

The Contractor shall participate in organizational training as required.

The Contractor shall complete the OSD mandatory training on an annual basis, which may include but not limited to Information Assurance and Security training, Operations Security (OPSEC) Training, OSD Counterintelligence Awareness & Reporting, Combating Trafficking in Persons training, Derivative Classification training, OSD/WHS Privacy Act Training, and Cyber Awareness training and other training assigned. Contractor shall comply with all WHS and OSD Operational Security guidelines and directives.

6.5.3 Positions

The Contractor shall hire and retain a quality work force, with minimal turnover in Contractor personnel. An integral part of successful performance under this contract is not only the production of quality products described in Section 5 (Performance Requirements) above, but also the responsiveness of Contractor personnel in the day-to-day output of work products. While the product or deliverable is vital to successful performance, day-to-day oversight also includes customer interaction and responsiveness.

6.5.4 Workforce Categories

The Contractor shall provide qualified personnel for the positions under this contract. Technical Exhibit 1 (Labor Categories) documents the labor categories that will be used in this contract aligned with primary subtasks to assist the Contractor with identifying qualified personnel. Technical Exhibit 2 (Historical Workload Data) will assist the Contractor with anticipating the required level of effort.

6.5.5 Key Personnel

The Contractor shall ensure the availability of Key Personnel with the requisite skills to perform the work detailed in this PWS. The Government designates three (3) positions as Key Personnel as outlined below:

· Senior-Level Program Manager/Software Engineer (PM) Position requires DoD Secret Security Clearance Estimated to be Staffed by - 1 FTE

· Senior-Level Business Analyst/Subject Matter Expert Position requires DoD Secret Security Clearance Estimated to be Staffed by - 1 FTE

· Software Quality Assurance (QA) Tester Position requires DoD Secret Clearance Estimated to be Staffed by - 1 FTE

6.6 Substitution of Team Members and Substitution of Personnel The Contractor agrees to assign the key person(s) identified in their proposal to this contract. During the first 90 days of performance, the Contractor may not substitute any Key Personnel unless it is necessary due to illness, death, or termination of employment. In such cases, the Contractor must notify the Contracting Officer (CO) and the Contracting Officer's Representative (COR) as soon as possible and provide the required information. After the initial 90 days, any substitutions must receive prior notification and written approval from both the CO and COR.

All proposed Key Personnel substitutions shall meet the requirements of the labor category for the position. The Contractor shall notify the CO and COR in writing of any proposed substitution at least 30 days, or 60 days if a security clearance is to be obtained, in advance of the proposed substitution. Such notification shall include:

The CO will notify the Contractor within fifteen (15) business days after receipt of all required information of the decision on proposed substitutions. Substitution of Non-Key Personnel is at the discretion of the Contractor; however, all proposed substitutions shall meet the applicable educational and experience requirements set forth in the PWS for the substituted position.

6.6.1 Conduct

Contractor personnel shall present a professional appearance at all times consistent with the usual and customary workforce attire of the assigned Government on-site locations, and their conduct shall not discredit the U.S. Government. The Government, at its sole discretion, may request the Contractor to remove any Contractor personnel from government facilities for misconduct, failure to perform, security reasons, or other appropriate reasons that may jeopardize the success of the mission. The CO may provide the Contractor with a written explanation to support any request to remove an employee. Removal of Contractor personnel does not relieve the Contractor of the responsibility to continue providing the services required under this contract.

6.6.2 Non-Disclosure Agreements (NDAs)

The Contractor may be required to access Confidential, Proprietary, and/or Sensitive Information held by the Government related to the tasks to be performed under this contract. In consideration of the Government granting the Contractor access to this information, an NDA shall be required between the Contractor and the Government. The terms and conditions are described in detail within the NDA. This agreement shall be signed by all Contractor personnel working under this contract and submitted within five (5) business days after contract award to the CO and COR. The Contractor shall ensure all Contractor personnel (including subcontractors) use said information only to meet the requirements of this contract. The Contractor (to include subcontractors) shall not disseminate proprietary information or place said information at risk of disclosure unless required and authorized by this contract. If Contractors are replaced during performance of this contract, the new Contractor personnel shall sign the NDA upon beginning work.

6.6.3 Non-personal Services/Inherently Governmental Functions All services described in this PWS are non-personal services, and the Contractor shall not perform any inherently governmental functions.

6.6.4 Data Rights

Data rights are defined by the clauses in this contract’s Defense Federal Acquisition Regulation Supplement (DFARS). The Contractor shall not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this effort.

6.8.4.1 Data Rights Provision: See DFARS 252.227-7015 – Technical Data - Commercial Products and Commercial Services

6.7 Telework

The Government may allow telecommuting (telework) for contractor employees when it serves the best interests of the Government in fulfilling work requirements, such as Continuity of Operations (COOP). Telework is permitted only if the contractor possesses a SECRET facility clearance. The contractor must have an established telework program that is subject to review by the Government. All telework agreements must receive authorization and approval from the Contracting Officer Representative (COR) and should include the date, time, and a description of the work to be performed.

Telework will not incur any additional costs to the Government. Upon approval, the Government may provide Government Furnished Equipment (GFE), which includes a secure laptop that grants access to necessary portals, networks, and business applications. However, the Government will not provide internet access; therefore, the contractor must arrange their own internet connection.

Contractor personnel covered under this contract are authorized to telework once they have received approval from the COR. They must also comply with the criteria and guidelines established by the Department of Defense (DoD) Chief Information Officer and its respective Components regarding the use of both Government Furnished Property (GFP) and non-GFP when accessing DoD information systems and networks for telework. The COR reserves the right to revise or terminate telework arrangements at the Government’s discretion. Certain positions may not be eligible for telework due to the specific duties and tasks that require on-site performance.

6.8 Service Contract Reporting (SCR)

The Contractor shall report ALL Contractor labor hours required for performance of services provided under this TO via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: https://www.sam.gov/. Reporting inputs will be for the labor executed during the period of performance during each government Fiscal Year (FY), designated from October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the web address help desk at https://www.sam.gov/.

6.9 Insurance

As prescribed in FAR 28.301(b) and 28.303, Contractors shall carry insurance under specific circumstances outlined in the provided regulations:

(a) Contractors subject to Cost Accounting Standard (CAS) 416 must obtain insurance for the perils they are exposed to, unless the government agrees to indemnify them or the contract relieves them of liability for loss or damage to government property. The government reserves the right to disapprove insurance purchases not in its interest, and the allowability of insurance costs is determined according to specified criteria.

(b) All contractors, whether subject to CAS 416 or not, must provide insurance for certain perils mandated by law and regulation (e.g., workers' compensation). Insurance becomes mandatory based on factors like commingling of property, type of operation, ownership circumstances, or contract conditions, for the protection of the government. The minimum insurance amounts required may be reduced for contracts performed outside the United States. Coordination between relevant agencies is necessary when multiple agencies are involved in reviewing and approving a contractor's insurance program, especially for significant insurance matters.

In instances where the Government mandates or endorses insurance to safeguard against loss or damage to Government property (refer to FAR 45.104, Responsibility and liability for Government property), such coverage can be obtained through dedicated insurance policies or by incorporating the risks into the contractor's current policies. The insurance policies must explicitly disclose the Government's interest in the covered property.

As prescribed in FAR 28.307-2, Contractors must adhere to Federal and State workers' compensation and occupational disease statutes. Occupational diseases not compensable under these statutes should be covered by the employer's liability section of the insurance policy, unless contract operations are so intertwined with a contractor's commercial operations that practicality dictates otherwise. A minimum employer's liability coverage of $100,000 is mandated, except in States with exclusive or monopolistic funds prohibiting private carriers from writing workers' compensation. Specific treatment for contracts subject to the Defense Base Act is outlined in 28.305(c).

For general liability:

The contracting officer (CO) must ensure bodily injury liability insurance coverage of at least $500,000 per occurrence.

Property damage liability insurance is required only in special circumstances as determined by the agency.

7.0 PART 7: DELIVERABLES AND SCHEDULE

In fulfillment of this effort, the Contractor shall provide specific deliverables as outlined in this PWS and summarized in Table 2 (Deliverables) below. All deliverables must meet professional standards and satisfy the requirements set forth in contractual documentation. The Contractor will be responsible for delivering all tasks specified. The dates by which specific deliverables shall be submitted will be as mutually agreed upon between the Government and the Contractor. All deliverables shall be submitted to the COR or the designated Government lead for the specific organizational area. In addition to the reports listed below, additional reports/products may be requested as deemed necessary.

Table 2. Deliverables

Due Date

Task 1 (Sections 5.1.1 ):Contractor Program Management Plan

Task 1 (Section 5.1.1):

· Monthly Progress Report

Task 2 (Section 5.1.2):

· May be included in Task 1 Progress Report

COR

· May be included in Task 1 Progress Report

(Section 6.1):

· Invoicing

(Section 6.10):

· Service Contract Reporting

(Section 7.2.2):

· Transition Phase-Out Plan

(Section 5.1.1/7.2.3):

· Post-Award Contract Kickoff Meeting Within ten (10)…