PERFORMANCE WORK STATEMENT (PWS)

Resource Enterprise Services (RES) for Program Review and Enterprise Services Division (PRESD), for the Office of the Secretary of War

(OSW), Cost Assessment and Program Evaluation (CAPE)

12 March 2026

General Information

1. INTRODUCTION: This is a non-personal services contract to provide Resource Enterprise Services (RES) for Program Review and Enterprise Services Division (PRESD). The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform Resource Enterprise Services (RES) for Program Review and Enterprise Services Division (PRESD) as defined in this Performance Work Statement except for those items specified as government furnished property and services.

The services and performance requirements under this contract are 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 DOW policy. The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. All contractor personnel shall identify themselves as contracted support personnel in all forms of communication with all entities with whom OSW CAPE has business dealings.

It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Contracting Officer immediately.

1.2 Background: The PRESD division of OSW, CAPE is responsible for maintaining of business applications to support matters relating to the planning and programming phases of the Planning, Programming, Budgeting, and Execution (PPBE) and the preparation of material and guidance for such systems PPBE is the Department of War (DOW) process for allocating resources. The annual process serves as the framework for DOW civilian and military leaders to decide which programs and force structure requirements to fund based on strategic objectives. Products produced include the Program Decision Memorandum and the Department of War Future Years Defense Program (FYDP) and supplementary data including the data structure. Applications have their authority to operate under the DOW Risk Management Framework under the system name Resource Enterprise Services (RES). See APPENDIX A for list of applications.

1.3 OBJECTIVES: The objective of this effort is to provide analytical and information management support to implement PRESD objectives associated with the Department of War’s budgetary requirements and to modernize technologies within the Resource Enterprise Services (RES) system. This includes the following:

1.3.1 Provide secure expert systems complaint with the Risk Management

Framework (RMF), Zero Trust and analytical support for the OSW Program Review process supporting leadership’s decision-making processes

1.3.2 Provide expert advice to leadership on methods to improve and automate the Planning, Programming, Budgeting, and Execution (PPBE) system.

1.3.3 Modernize existing PPBE systems to improve user experience and efficiency

1.3.4 Improve PPBE data exchanges with other DOW applications

1.3.5 Integrate program, budget, acquisition, and other strategic information processes and systems.

1.3.6 Migrate capabilities to the cloud utilizing cloud services

1.3.7 Carry out initiatives improving the efficiency and effectiveness of PPBE processes, systems, and data.

1.3.8 Modernize Program Review to leverage technological advancements, including

Artificial Intelligence (AI) and robust digital infrastructure, to improve its effectiveness, efficiency, and Net-Centric capabilities.

1.3.9 Integrate program, budget, acquisition, and other strategic information processes and systems.

1.3.10 Support analysis and help resolve data issues.

1.3.11 Make data available for broad DOW analysis using analytical tools and integrated displays, and dashboards enhancing its usefulness.

1.3.12 Developing standard technology frameworks for data collection, report generation, web displays, and software development life cycle Develop and implement a standard technology framework for software development life cycle.

1.3.13 Provide expert systems and analytical tools that produce fulfill reporting requirements.

1.4 SCOPE: OSW/CAPE/IO/PRESD Resource Enterprise Services currently supports business applications that provide for the collection, dissemination, reports, and analytical displays of PPBE data on the SIPRNET and NIPRNET. To accomplish the objectives, the contractor shall provide program analyst/integrators and technical experts having adequate certifications with expertise implementing analytic solutions to support budgetary systems associated with the PPBE specifically the Program Review process.

Analytical knowledge and experience of the Program Review process is necessary.

Knowledge of FYDP data and structures and how to validate data between Comptroller Next Generation Resource Management System (NGRMS) is required. The ability to create and maintain complex Oracle triggers, procedures, and functions is necessary.

Technologies associated with all tasks (including Optional) are listed in Appendix A.

Applications are listed under Appendix B. The contractor shall work with the government to standardize the technology to enable developers to be matrixed and able to support multiple applications during the base year.

1.4.1 User security is centralized and controlled using the CAPE Single Sign-On system EXPRESSO. All of the applications use the CAPE’s EXPRESSO application for provisioning. The legacy EXPRESSO handles user authentication and authorization while the cloud version will utilize DISA ICAM IDP with the F5 for authentication. This will be transitioned from Web Gates to using Security Assertion Markup Language (SAML) to authenticate. Users manage their access requests through the EXPRESSO web siteand EXPRESSO transfers the account information to a central Lightweight Directory Access Protocol (LDAP) server. The SNaP applications use the .NET Active Directory Application Program Interface (API) to query the LDAP. On the NIPRNET platform, the user authentication is performed using the Common Access Card (CAC).

On the SIPRNet user access is performed using the SIPRNet Token card. All roles for provisioning are controlled through EXPRESSO. Applications that control pre-decisional data have additional security features. Additional security features including excluding persona types that are. CTR or requiring a signed Non-Disclosure Agreement.

Each application has its own unique user authorization groups within EXPRESSO. The contractor is responsible for the following:

• Determining the specific requirements for these groups.

• Creating the necessary user groups within the EXPRESSO database.

• Integrating these groups with the DISA ICAM system.

1.4.2 On the NIPRNET and on the SIPRNET cloud platform additional security is provided for outward facing web sites, such as SNaP, by the DISA F5 server. The F5 server authenticates the user's DOW Common Access Card (CAC) or SIPR token as a part of enterprise ICAM IDP transition and if valid passes control to the web server. The application then determines the user authorizations by examining the EXPRESSO Light Directory Access Protocol (LDAP) data. The next phase will require SAML queries from the applications to DISA ICAM. This is part of the ICAM implementation and subject to change to reach Zero Trust compliance.

1.4.3 On the OnPrem SIPRNET platform user authentication and authorization are controlled by the OSW/CAPE Oracle Single Sign-On (SSO) system. The OnPrem web traffic passes through the SSO server which confirms that the user has a valid session token. User authorizations are determined by the application using Representational State Transfer (REST) queries of the SSO system.

1.4.4 All applications operate 24 hours a day, 7 days a week (24-7), and consists of production, development and test machines.

1.4.5 All systems must comply with the Department of War’s Computer Emergency Response Team (DOW CERT) guidelines maintained in the Vulnerability Management System (VMS) web site. Application development shall follow Security Technical Implementation Guidelines (STIGS).

1.5 PERIOD OF PERFORMANCE: The period of performance shall be for one (1) 12-month base period and four (4) 12-month option periods.

Base Period: 30 AUG 2026 to 29 AUG 2027 Option Period One: 30 AUG 2027 to 29 AUG 2028 Option Period Two: 30 AUG 2029 to 29 AUG 2030 Option Period Three: 30 AUG 2030 to 29 AUG 2031 Option Period Four: 30 AUG 2031 to 29 AUG 2032

1.6 CONTRACT TYPE: The Government will award a Firm-Fixed Price (FFP) Contract.

1.7 PLACE OF PERFORMANCE: The work to be performed under this contract will be performed in a government provided office space in the National Capital Region (NCR) to include the Pentagon, Arlington, Virginia; Mark Center, Alexandria, Virginia.

Contractor personnel may be requested to work at the Governments alternate locations during emergencies and emergency exercises. Individual contractor personnel may be designated as essential personnel to support contingency operations at alternate Government locations during actual emergencies and emergency exercises.

1.8 TELEWORK: The COR will determine whether the work to be performed can be successfully accomplished offsite. Teleworking must be accomplished at no additional cost to the Government and with no detrimental impacts to contract performance.

Contractor personnel may be required to report on onsite to a government facility to perform services at any time as required by the KO or COR.

1.9 HOURS OF OPERATION: The Contractor is responsible for providing services, between the core hours of 9:00 AM to 5:00 PM Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Workers typically work eight (8) hours per day, 40 hours per week but can be flexed to support the mission. For other than firm fixed price contracts, the Contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential. The Contractor shall submit written weekend and shift work requests to the COR and Contracting officer for approval within three (3) business days of start date of request.

1.9.1 Onsite Working Conditions, Holidays and other Closures:

Contractor personnel are not customarily expected to work on holidays, but holiday work is possible, if required by the Government and/or with adequate Government oversight at Government facilities, subject to advance scheduling with the Contractor. The amounts in the schedule of the contract include an allowance for holidays to be observed. The Government will not be billed for such holidays, except when services are required by the Government and are actually performed on a holiday.

When the Government grants administrative leave to Government employees, or is closed as a result of inclement weather, potentially hazardous conditions, or other special circumstances, contractor personnel working at the specific facility/location granted administrative leave may also be dismissed at the discretion of the On-site Manager to the extent that the overall performance is not adversely impacted. The Contractor shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons.

The Contractor shall provide the COR and Task Monitor a current schedule for its entire staff assigned to the contract, including planned leave. The Contractor shall assign alternates to cover assignments of any of its staff that are absent to ensure that the services are not disrupted.

1.9.2 Washington Headquarters Services facilities are smoking restricted workplaces.

Due to the nature of the work, facilities, and requirements, Contractor staff may only smoke outside in designated smoking areas.

1.9.3 The Contractor shall establish normal operating hours under this contract between 9:00 AM to 5:00 PM, Eastern Standard Time (EST) Monday through Friday. The Contractor’s Program Manager (PM) and the Government’s Contracting Officer’s Representative (COR) shall consult and coordinate on any proposed alternate work schedules that may be arranged depending on the operational tempo/needs of the mission.

1.10 RECOGNIZED HOLIDAYS: Government personnel observe the following holidays as governed by 5 U.S.C. § 6103. Government facilities will be closed and unavailable to Contractor personnel:

*If the date falls on a Saturday, the Government holiday is the preceding Friday. If the date falls on a Sunday, the Government holiday is the following Monday.

In addition to the days designated as holidays, the Government observes the following days:

• Any other day designated by Federal Statute

• Any other day designated by Executive Order

• Any other day designated by the President’s Proclamation

1.11 QUALITY CONTROL/ASSURANCE:

1.11.1 Quality Control: The Contractor shall develop and maintain an effective Quality Control Plan (QCP) to ensure services are performed in accordance with this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor’s QCP is the means by which it ensures that its work complies with the requirements of the contract. A draft QCP should be submitted at award. The final QCP shall be delivered via electronic mail within 60 calendar days after contract award. Amendments/changes to the QCP shall be delivered to the COR and Contracting Officer within three (3) business days following any change(s). After acceptance of the QCP, the Contractor shall receive the Contracting Officer’s acceptance in writing of any proposed change(s) to is QCP.

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day Washington’s Birthday Veterans Day Memorial Day Thanksgiving Day Juneteenth Independence Day Christmas Day

1.11.2 Quality Assurance: The Government will evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP).

This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.12 PERSONNEL MATTERS

1.12.1: Key Personnel/Minimum Qualifications: The personnel listed below are considered essential to the work being performed under this contract. Before removing, replacing, or diverting any of the listed or specified personnel or facilities, the Contractor shall (1) notify the Contracting Officer reasonably in advance and (2) submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this contract. The Contractor shall make no diversion without the Contracting Officer's written consent. Please see the below Key Personnel positions.

Task: Position: Qualifications:

5.1, 5.2.1, 5.2.2, 5.2.4, 5.2.5, 5.3.1.1, 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.2.3, 5.3.2.1, 5.3.2.2, 5.3.2.3, 5.3.2.4, 5.3.2.5, 5.3.2.6, 5.3.2.8,5.3.3.1, 5.3.4.1

Senior Systems Analyst/Solution Integrator

Functional Responsibility:

Responsible for designing and supporting agile applications that respond to meet client requirements. Works with the project business owner and/or executive to ensure delivery that responds to timelines.

Minimum Job Qualifications:

Must have a minimum of ten

(10) years of experience working with the Future Years Defense Program data and with Program Review, experience with Oracle APEX and other programming languages, experience developing RESTful services like Oracle RESTful Data Services (ORDs), technical expertise with developing web based analytical front-ends and ten years being a solution provider. A Bachelor's degree in Computer Science, Information Systems, Engineering, Business or other related scientific or technical discipline or a Master’s Degree with 8 years IT experience or a PH.D with 6 years of IT experience. With twelve years of experience, a degree is not required.

Certifications:

DoDM 8140.03 IA certification is a requirement.

Preferred:

At least five (5) years of information systems management experience.

5.1, 5.2.1, 5.2.2, 5.2.4, 5.2.5, 5.3.1.1, 5.3.1.2, 5.3.1.3, 5.3.1.4, 5.3.1.5, 5.2.3, 5.3.2.1, 5.3.2.2, 5.3.2.3, 5.3.2.4, 5.3.2.5, 5.3.2.6, 5.3.2.8,5.3.3.1, 5.3.4.1, 5.3.2.9

Systems Analyst/Solution

Skills: HTML, Oracle APEX, RESTful Web services, Services, Java, JSP, PL/SQL, MS Word ML, MS Access, SQL, Aspose, Agile Software Development, Software Development Life Cycle.

Minimum Job Qualifications:

At least ten (10) years’ experience working the PPBE process, Program Decision workflow, and FYDP data structure with extensive knowledge of manpower data and how to calculate MILPERS and how to correct data anomalies between the FYDP and Comptroller New Gen application (NGRMS).

Preferred:

At least ten (10) years of experience in architecting Web Application system solutions.

5.3.6, 5.3.7, 5.3.17, 5.3.18, 5.3.19

Senior Systems Engineer Scientist (Optional Task):

Works in an engineering environment focusing on engineering and/or scientific studies and analysis providing technical solutions. Supports programs with exceptional creativity and resourcefulness in the most demanding and complex assignments.

Performs analyses and develops recommendations that may impact acquisition programs and activities.

Provides technical direction or perform complex analyses.

Provides design, implementation, testing services for complex information systems providing Business Intelligence solutions.

Minimum Job Qualifications:

A Bachelor's degree in Computer Science, Information Systems, Engineering, Business or other related scientific or technical discipline and at least 10 years of relevant experience or a Master’s Degree with 8 years IT experience or a PH.D with 6 years of IT experience.

With twelve years of experience, a degree is not required.

Certifications:

DoD 8140.03 IA certification is a requirement

Preferred:

- At least five (5) years of information systems management experience.

- Skills: HTML, Visual Basic, Java, JSP, Java Struts, Java Script, Java Servlet, PL/SQL, CVS, Eclipse, Apache, WebLogic, IIS,

- , OBIEE/Oracle Analytics, Oracle Data Visualization, D3, MS Access, SQL, Agile Software Development, Software Development Life Cycle.

- At least five (5) years of Data Warehousing experience including familiarity with Data Modeling, Data Warehousing, Agile Software Development, Software Development Life Cycle concepts, and implementing Hyperion Interactive Reporting and OBIEE+ solutions.

- At least five (5) years of experience in architecting Business Intelligence (BI) or Web Application system solutions.

- At least five (5) years of software development or COTS solution deployment project management experience.

- At least five (5) years of experience with PPBE process, data structure (program, budget, and acquisition) with BI solutions and related products and systems.

5.2.9, 5.3.10, 5.2.11, 5.3.12, 5.3.13, 5.3.14, 5.3.15, 5.3.16

Software/Web Developer III (Optional Task):

Functional Responsibility:

Provides requirement analysis, systems design, development, installation, testing, system certification and accreditation, and/or operational support.

Performs basic analysis of alternatives, systems design, integration, testing, and problem diagnosis/resolution. Prepares associated documentation, block diagrams, and logic flowcharts.

Prepares sample test data, conducts program tests, and analyzes test results;

recommends corrections for debugging program errors.

Modifies existing programs as required by changing systems requirements or equipment configurations. Confers with systems personnel to clarify program intent, output requirements, and input data acquisition. Evaluates vendor capabilities to provide required products or services. Designs, develops, and analyzes software programs. Designs and develops web sites based on approved customer objectives. Proposes web site strategies and creates action plans and applications to carry out strategies and accomplish objectives.

Customizes web-based interactive features, builds database gateways, and implements electronic commerce services. Collaborates with hardware design engineers on machine characteristics that affect software systems, and works with them to resolve incompatibilities. Also can perform operational readiness of systems by providing infrastructure technical support.

May provide direction to less experienced software engineers.

Minimum Job Qualifications:

A Bachelor's degree in Computer Science, Information Systems, Engineering, Business or other related scientific or technical discipline and at least four (4) years of relevant experience or a Master’s degree with two years of specialized experience.

Eight years or more of specialized experience, a degree is not required.

Preferred:

Experience with PPBE data is desired.

5.2.9, 5.3.10, 5.2.11, 5.3.12, Software/Web Developer IV (Optional Task):

Comprehensive knowledge in the development and application methods, theories, and research techniques in the investigation and solution of software applications.

Performs requirement analysis, systems design, development, installation, testing, system certification and accreditation, and operational support for large-scale and distributed systems. Prepares associated documentation, block diagrams, and logic flowcharts.

Prepares sample test data, conducts program tests, and analyzes test results;

recommends corrections for debugging program errors.

Modifies existing programs as required by changing systems requirements or equipment configurations. Confers with systems personnel to clarify program intent, output requirements, and input data acquisition. Evaluates vendor capabilities to provide required products or services. Designs, develops, and analyzes software programs. Designs and develops web sites based on approved customer objectives. Proposes web site strategies and creates action plans and applications to carry out strategies and accomplish objectives. Customizes web-based interactive features, builds database gateways, and implements electronic commerce services.

Collaborates with hardware design engineers on machine characteristics that affect software systems, and works with them to resolve incompatibilities. Also, can perform operational readiness of systems by providing infrastructure technical expertise in capacity planning.

May provide daily supervision and direction to support staff.

Minimum Job Qualifications:

A Bachelor's degree in Computer Science, Information Systems, Engineering, Business or other related scientific or technical discipline and at least seven (7) years of relevant experience or a Master’s degree with five years of specialized experience or a Ph.D. with three years of specialized experience. With at least eleven years of specialized experience, a degree is not required.

Preferred:

Experience with developing and submitting OSW CIO Congressional IT budget reporting is desired

5.3.9, 5.3.10, 5.3.11, 5.3.12, Project Manager (Optional Task):

Responsible for coordinating, defining, staffing, and managing single or for defined projects or large program(s) in accordance with client requirements. Supports analysis, directs, organizes, and monitors work and is responsible for meeting program cost, schedule, and performance objectives. Works with the project business owner and/or executive to oversee delivery performance, ensure delivery quality and report schedule, cost, and execution performance. Also organizes, directs, and coordinates the planning and production of all contract support activities.

Minimum Job Qualifications:

A Bachelor's degree in Computer Science, Information Systems, Engineering, Business or other related scientific or technical discipline and at least 10 years of relevant experience or a Master’s Degree with 8 years IT experience or a PH.D with 6 years of IT experience. With twelve years of experience, a degree is not required.

Preferred:

Experience with overseeing OSW CIO Congressional IT budget reporting.

1.12.2 Identification of Contractor Employees: All contract 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 that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.

1.12.3 Special Qualifications: The Contractor shall ensure that the key personnel possess the skills, knowledge, training, and certification(s) required to satisfactorily perform all services required by the contract. Availability of contractor staff familiar with PPBE components, industry standards, DOW’s policies and techniques for management of application DoDM 8140.03 and will possess NATO cleared certification. A final security clearance at the appropriate level is required for access to NATO information. Written concurrence of the Technical Point of Contact/Contracting Officer Representative/ Contracting Officer Representative for Security (as applicable) is required prior to subcontracting IAW 32 CFR Part 117 NISPOM 117.19(g)(9).

1.12.4 The following training is required for onsite Contractor personnel: The Contractor shall ensure that all Contractor employees complete annual Government-furnished training in Information Assurance, Privacy Act, Operational Security, and other assigned training required. Any Contractor behavior deviating from standards taught in the course shall be grounds for termination of the contract. The Contractor shall maintain a cyber-threat plan security awareness certification plan. The Contractor shall submit certificates of completion for each affected Contractor employee and Subcontractor employee, to the COR. This training shall be completed and reported to the COR within 30 calendar days of contract award and annual refresher training for the remaining contract duration.

1.13 SECURITY:

1.13.1 The Contractor shall possess and maintain an active Secret facility clearance from the Defense Counterintelligence and Security Agency (DCSA). Contractor personnel performing work under this contract shall have at minimum an interim Secret clearance at the time of proposal submission and shall maintain the level of security required for the life of the contract. The security requirements are in accordance with the attached

DD254 (

1.13.1.2 The Contractor shall not divulge, or release data or information developed or obtained in performance of this contract except to DOW Government personnel, other authorized Government personnel designated by DOW Government personnel, or upon written approval of the COR.

1.13.1.3 The Contractor shall not use, disclose, or reproduce proprietary data, other than as required in the performance of this contract. The limitations above do not apply to data or information that has been made public by the Government.

1.13.1.4 The final DD Form 254, Contract Security Classification Specification, will be incorporated into the award document. The Contractor’s Facility Security Officer (FSO) shall report, in writing, to the Contracting Officer any changes in the Contractor’s security status throughout the contract period of performance.

1.13.1.5 Prior to assignment of contractor employees under this contract, the Contractor’s FSO shall submit Personnel (Security) Clearance (PCL) validation through use of a Visit Authorization Request (VAR) for each employee, in accordance with 32 CFR Part 17, National Industrial Security Program Operating Manual (NISPOM) to the designated security representative. Changes in PCL status of contractor employees shall be forwarded in writing to the Contracting Officer and the designated security representative.

1.13.1.6 Subcontractors shall comply with the same security requirements as the Contractor. The Contractor shall issue DD Form 254s to each subcontractor reflecting the same security requirements applicable to the prime contract. The contractor shall also sponsor subcontractor(s) for a Facility (Security) Clearance (FCL) and associated PCL(s) required in accordance with the DD Form 254.

1.13.2 Physical Security: The Contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured.

1.13.3 Access Control: The Contractor shall establish and implement methods of making sure all Personal Identification Codes and/or Personal Identification Numbers (PIC/PINS) assigned to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. The Contractor shall follow established Government Office policies/procedures for safeguarding PIC/PINs.

1.13.4 The Contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.13.5 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 personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s QCP.

1.13.6 Operations Security (OPSEC) is a structured process that identifies critical information, analyzes friendly actions, integrates threat analysis and risk assessments, then helps personnel apply protective measures to mitigate unacceptable risk. The contractor shall agree to comply with the same basic OPSEC rules, requirements, and standards as government personnel. When contractor personnel are working primarily in government facilities, OPSEC Awareness Education and Training will be provided or coordinated through the appropriate government security channels and OPSEC protective measures (countermeasures) will be applied as directed by the government. When contractor personnel are working primarily in contractor facilities, OPSEC Awareness Education and Training shall be provided by the contractor. All contractor support personnel are required to receive OPSEC Awareness Education and Duty-Related Training. All contract 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. The contractor shall comply with the DOW Customers Operations Security Program, specifically DODD

5205.02 “DoD Operations Security (OPSEC) Program” March 6, 2006. All software, database and web development for the DoD must comply with Defense Information System Agency (DISA) published Security Technical Implementation Guides (STIGs).

1.14 CONTRACT ADMINISTRATION

1.14.1 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5.

The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced.

Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.14.2 Phase-in/Phase-out Period: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the 45-day phase in/phase out periods. During the phase in period, the Contractor shall become familiar and execute with performance requirements in order to commence full performance of services on the contract start date. During the phase-out period, the existing Contractor shall coordinate with incoming Contractor as necessary to ensure a smooth transition of performance.

1.14.3 The phase-in period shall not exceed 45 calendar days during which the Contractor shall complete administrative and transition requirements, overlapping with the incumbent contracts. The phase-in period will include a 15-day administrative period for onboarding new contractor staff and a 30-calendar day transition overlap period; the periods shall run consecutively. During the 15-day administrative period, the Contractor shall obtain the following, including but not limited to: network accounts, permissions, Common Access Cards, GFE, desktop software installations/configurations and any other materials or access needed to assume responsibility for supported systems. During the 30-calendar day transition overlap period, the Contractor shall become familiar with task performance requirements, transfer accountability of government furnished equipment and tools, review respective standard operating procedures, and interface with appropriate RES PRESD OSW CAPE government leadership. The transition plan must be detailed and include start-up activities required to transition to full operational capability to successfully assume all duties under this PWS. A draft transition plan, but near to complete draft plan, shall be provided to the Government at proposal submission. The Final transition plan shall be delivered to the government by the 15th day of the Administrative Period. At a minimum, the Contractor shall:

- Provide a detailed transition methodology in logical sequence to ensure a smooth transition of all tasks of the contract without interruption or degradation of service levels;

- Interface and coordination with the government;

- Identification of key transition events and objectives with a corresponding completion timeline;

- Identification of associated risks and issues with risk mitigation strategies; and

- Identification of key persons participating in the transition.

1.14.4 Monthly Status Report: The Contractor shall provide a monthly written Status Report documenting task support, issues, and progress no later than the 10th calendar day of each month. The Report shall detail contractor activities during the reporting month and plans for the following two months. The Report shall include a summary of work performed and deliverables completed, current or projected problems and issues and their resolution, an explanation of deviations from the last month's projections, and any recommendations related to the effort. The Contractor may be asked to provide a percentage of development hours to support Internal Use Software reporting.

1.14.5 Reserved

1.14.6 Progress Reviews:

1.14.6.1 Progress Reviews will be performed as directed by the COR and will generally summarize the status and progress of all activities being performed by the Contractor under the PWS. Progress reviews will take place at those locations requested by the Task Monitor and COR. Specific dates for progress reviews will be agreed between the Task Monitor, COR and the Contractor's Program Manager.

1.14.6.2 Documents, data files, reports, correspondence, and all other documents and writings, together with any charts, graphs, tables, illustrations, photographs, images, and other illustrative, explanatory, historical documents related thereto or independent thereof, regardless of the medium (or media) by which they were produced, preserved, stored, or created in connection with or for purpose(s) of work performed under this PWS and contract, are property of the Government and shall be delivered to the COR and Task Monitor promptly, upon request.

1.14.6.3 The Contractor agrees to assume responsibility for protecting the confidentiality of Government records, which is not considered public information. Each Contractor or employee of the Contractor 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 herein. The Contractor shall not release any information related to this contract to the public, media or other unauthorized persons or organizations unless the government has conducted the appropriate security review and granted written approval (e.g. posting information to a public website).

1.14.6.4 Plan of Action and Milestones (POAM): The Contractor shall develop a Plan of Action and Milestones for all tasks and deliver the document to the government no later than 30 calendar days from award of contract.

1.14.6.5 Need-To-Know: Some of the work associated with this PWS is classified. The need-to-know access associated with the activities in this PWS will limit the ability of contractor employees performing work on this PWS from working on other contracts.

Exceptions to the requirement to work on-site and work on other contracts will be approved in writing, on a case-by-case basis, by the government Task Monitor and COR.

1.15 TRAVEL/TDY/DEPLOYMENT: Not Applicable

1.16: OTHER DIRECT COST: Not Applicable

1.17 DATA RIGHTS: The Contractor shall refer to the applicable FAR/DFARS clause in the Solicitation/Contract.

1.18 CONFLICT OF INTEREST

1.18.1 Organizational Conflict of Interest/Personal Conflict of Interest: Contractor and Subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interest (OCI) as defined in FAR Subpart 9.5 as well as personal conflicts of interest. Using the Contractor OCI/COI Disclosure Form, the Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential conflict and shall promptly submit the conflict-of-interest disclosure form to the Contracting Officer to avoid or mitigate any such conflict.

1.18.2 The Contractor’s mitigation plan will be reviewed and accepted/rejected solely at the discretion of the Government, and in the event the Government unilaterally determines that any such conflict cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the conflict.

1.18.3 In addition, Contractors shall conduct internal reviews as necessary to identify financial interests and determine if any personal conflicts of interest exist or may arise.

The Contractor shall ensure that the organization has analyzed each financial disclosure to determine whether actual or potential conflicts exist. Information should be gathered and analyzed for all governing body members (e.g., board of directors, trustees, etc.) and principals of the organization as defined by FAR 52.203-13 and for each manager and key personnel who would be or are involved with the performance of the contract.

1.18.4 All Contractor and Subcontractor employees supporting this contract shall sign the WHS AD non-disclosure agreements.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. 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.

2.1.2. CONTRACTING OFFICER. 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.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer 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.

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

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

2.1.6. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

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

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

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

2.1.11. SUBCONTRACTOR. One that enters into a contract with a prime contractor.

The Government does not have privity of contract with the subcontractor.

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

2.1.12. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2. ACRONYMS:

ACOR Alternate Contracting Officer's Representative API Application Program Interface AWS-3 Advanced Wireless Services 3 BCTF Boards, Commissions, and Task Forces BES Budget Estimate Submission BI Business Intelligence CAC Common Access Card CADAT Characterization and Dependency Analysis Tool CAPE Cost Assessment and Program Evaluation CFR Code of Federal Regulations CIS Comptroller Information System CJB Congressional Justification Book CMO Chief Management Officer CN Counternarcotics CN&GT Counternarcotics and Global Threats CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTR Contracting Officer's Technical Representative COTS Commercial-Off-the-Shelf CTA Central Transfer Account DBS Defense Business System DCIM Data Center Inventory Management DCMO Deputy Chief Management Officer DCS Defense Collaboration Services DD Form 254 Department of Defense Contract Security Requirement List DFARS Defense Federal Acquisition Regulation Supplement DITIP Defense Information Technology Investment Portal DITPR Defense Information Technology Portfolio Registry DISA Defense Information System Agency DMDC Defense Manpower Data Center DoW Department of War DoW CERT Department of Wars Computer Emergency Response Team DSS Defense Security Service EM Enterprise Management Directorate FAR Federal Acquisition Regulation FCL Facility (Security) Clearance FLSA Fair Labor Standards Act FMR Financial Management Regulation FYDP Future Years Defense Program FSO Facility Security Officer HIPAA Health Insurance Portability and Accountability Act of 1996

HTML Hypertext Markup Language IIS Internet Information Services IT Information Technology JSP Joint Service Provider KO Contracting Officer LDAP Light Directory Access Protocol MYP Multiyear Procurement NACI National Agency Check NCR National Capital Region NIPRNet Non-classified Internet Protocol (IP) Router Network NISPOM National Industrial Security Program Operating Manual OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODASD Office of the Deputy Assistant Secretary of Defense ODBC Open Database Connectivity ODC Other Direct Costs OMB Office and Management and Budget OPSEC Operations Security OSW Office of the Secretary of War PB President’s Budget PCL Personnel (Security) Clearance PIC Personal Identification Code PINS Personal Identification Numbers PIPO Phase In/Phase Out PM Program Manager POAM Plan of Action and Milestones POC Point of Contact POM Program Objective Memorandum PPBE Planning, Programming and Budgeting Execution PRCP Program Resources Collection Process PRESD Program Review and Enterprise Services Division PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Plan REST Representational State Transfer SDCS Standard Data Collection System SENSR Spectrum Efficient National Surveillance Radar SIPRNet Secret Internet Protocol Router Network SNAP Select and Native Programming, Budget and Resource Data Input Systems SNAP-IT Select and Native Programming, Budget and Resource Data Input

Systems Information Technology Application SNAP-MYP Select and Native Programming, Budget and Resource Data Input

Systems Multiyear Procurement Application

SNAP-SAR&DP/SENSR Select and Native Programming, Budget and Resource Data Input Systems-SPECTRUM Access Research & Development Plan and Spectrum Efficient National Surveillance Radar

SNAP-SRF II Select and Native Programming, Budget and Resource Data Input Systems-SPECTRUM Relocation Fund II

SQL Structured Query Language SSO Single Sign-On STIGS Security Technical Implementation Guidelines TE Technical Exhibit TM Task Monitor VAR Visit Authorization Request VMS Vulnerability Management System WHS Washington Headquarters Services XML Extensible Markup Language

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services: The government will provide basic services to phones, desks, utilities, information technology, and general office supplies) while working in Government facilities.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this

PWS.

4.2 Secret Facility Clearance: The Contractor shall have a Secret Facility Clearance from Defense Security Services (DSS) at proposal submission. If there is turnover an interim Secret clearance may be allowed at the discretion of the government for a new hire for up to 45 days. The contractor shall hold and maintain the level of facility clearance for the life of the contract. Contractor personnel performing work under this contract shall have and maintain a fully adjudicated Secret clearance for the life of the contract. The DD 254 is provided as an attachment.

4.3 Materials: NA

4.4 Equipment: NA

4.5 Training: The Contractor shall provide training, as necessary, for their own personnel to ensure that analysts/developers are trained on the common suite of software tools and Microsoft Office tools (e.g., Word, Excel, PowerPoint). The Contractor shall also ensure that all of its employees have been properly trained and are qualified to perform assigned tasks under this PWS. The Government will provide or coordinate training on any new Government-provided equipment or Government-directed training (e.g., Information Assurance). If such training requires travel on the part of contractor employees, local travel costs (i.e., Metro) will be borne by the contract personnel.

4.6 Business Relations: The Contractor shall successfully integrate and coordinate all activity needed to execute the requirements specified herein. The Contractor shall manage the timeliness, completeness, and quality of the contract deliverables. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of all contractor personnel (including subcontractors). The Contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel.

4.7…