PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

Washington Headquarters Services / Acquisition Directorate

In Support of Defense Security Cooperation Agency (DSCA)

Information Management & Technology (IM&T) Socium Development and Operation & Sustainment & Support

28 July 2025

PART 1

GENERAL INFORMATION

1. GENERAL: This is a non-personal services contract to provide development and Operation & Sustainment (O&S) and development support for Socium. 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 Socium development and O&S support as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: The Defense Security Cooperation Agency (DSCA) has program responsibilities regarding the sale and transfer of defense articles and services to international customers. As part of its overall responsibilities, DSCA is the Department of Defense (DOD) agency delegated the responsibility to manage the transfer, sale, and lease of U.S. military end- items under Sections 516 and 623 of the Foreign Assistance Act (FAA) of 1961 (22 U.S.C. 2321j) as amended, and Chapters 2, 3, and 6 of the Arms Export Control Act (AECA). DSCA requires contractor support pertaining to Socium to execute these responsibilities.

Socium is a mission critical cloud-based DOD enterprise-wide capability to facilitate and integrate planning, budgeting, collaboration, design, management, assessment, monitoring, evaluation, and reporting in support of all U.S. Security Cooperation (SC) activities. The system execution model is a web-based platform that is multi-domain and multi-functional.

The application was developed to reform the DOD’s SC enterprise by consolidating various SC authorities, providing greater program scope clarity, and improving program management and oversight. This enables DSCA to manage its global SC activities and initiatives in a single integrated system. As an innovative application, Socium has the capability to facilitate and integrate planning, budgeting, collaboration, design, management, assessment monitoring, evaluation, and reporting that allows analysts, planners, and reviewers to plan, monitor, and budget SC activities with partners across the globe.

This PWS requires the vendor to work with DSCA IT Operations and Infrastructure Support for Socium’s O&S and the Government Product Owner (PO) to provide business capabilities and requirements gathering support and development for this innovative solution to remain capable of meeting the needs of the SC enterprise within a time boxed period of Agile methodology development and overall O&S. Concurrently, continue to apply the innovative Development, Security, and Operations (DevSecOps) program executive model to the multi-domain, multi-functional system that DSCA has been using. The vendor must communicate downtime or issues in a timely, consistent manner since Socium is used in all time zones.

1.2.1 Tasks: The primary tasks for Socium Development and O&S are:

• Basic Socium Services

• Agile Framework and Project Management

• Agile Development Management

• Agile Product Owner Support

• Development, Engineering and Capability

• Operation & Sustainment Services

1.2.2 Objectives: The objective of this requirement is the O&S and further enhancement of Socium Non-classified Internet Protocol Router (NIPR) and Secret Internet Protocol Router (SIPR) through development, which includes supporting product ownership, Agile and project management, O&S, development, technical support, compliance, and enhancing and upgrading Socium to deliver enhanced functionality in accordance with (IAW) DOD guidance.

1.3 Scope: The services will include:

• Development of new or improved capabilities for operational use in Socium

• O&S support and improvement to the Socium software to ensure its enterprise operational capability

The support requested is intended to provide services for the areas shown in Part 5 below.

1.4 Period of Performance: The period of performance shall be for one (1) Base Year and four (4) twelve-month option periods, and one (1) six (6) month optional period. The Period of Performance reads as follows:

Phase-In: 19 February 2026 - 18 March 2026 Base Year: 19 March 2026 – 18 March 2027 Option Year 1: 19 March 2027 – 18 March 2028 Option Year 2: 19 March 2028 – 18 March 2029 Option Year 3: 19 March 2029 – 18 March 2030 Option Year 4: 19 March 2030 – 18 March 2031 Optional 52.217-8; 6 Month: 19 March 2031 – 18 September 2031

1.5 General Information:

1.5.1 Quality Control: The contractor shall develop and maintain an effective quality control program 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 quality control program (QCP) is the means by which they assure the work complies with the requirement of the contract. The QCP is to be delivered within 15 days after contract award. A copy shall be submitted to the Contracting Officer (KO) and Contracting Officer Representative (COR) within five (5) working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to the Quality Control (QC) system.

1.5.1.1 Inspection and Acceptance Criteria: The COR or technical representative will require up to five (5) business days from receipt of all deliverables for review and comment/acceptance. Government acceptance will be based upon the deliverables meeting accepted professional standards for technical content, workmanship, and relevance to stated functional task requirements.

1.5.2 Quality Assurance: The government shall 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.5.2.1 Identification of Non-Disclosure Requirements: The activities in this PWS will require the contractor to receive Government Furnished Information (GFI), and access data and information proprietary to other contractors or Government agencies and/or of such a nature that its dissemination or use, other than in performance of this PWS, would be averse to the interests of the Government and/or others. The contractor, including contractor personnel, subcontractors, and consultants, will not divulge or release data or information developed or obtained in performance of this PWS except to Government authorized personnel or upon written approval of the CO or COR.

The contractor will not use, disclose, or reproduce proprietary data, which bears a restrictive legend, other than as required in the performance of this PWS. The limitations above do not apply to data or information that has been made public by the Government. All products, deliverables and work produced, as well as associated back-up documentation will be considered the property of the Government. The contractors will be expected to sign Non- Disclosure Agreements (NDA) within one (1) business day of onboarding.

1.5.3 Recognized Holidays: The contractor is not required to work on federal holidays. However, if a program occurs over a holiday period, a limited number of personnel may be needed to support a program. Prior coordination shall be made and approved between the COR and KO.

New Year’s Day, January 1.

Martin Luther King Jr.’s Birthday, the third Monday in January.

President’s Day, the third Monday in February.

Memorial Day, the last Monday in May.

Juneteenth National Independence Day, June 19.

Independence Day, July 4.

Labor Day, the first Monday in September.

Columbus Day, the second Monday in October.

Veterans Day, November 11.

Thanksgiving Day, the fourth Thursday in November.

Christmas Day, December 25

1.5.4 Hours of Operation: The contractor is responsible for conducting business between the hours of 0800 – 1700 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. 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 maintain an adequate workforce at all times 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.

1.5.5 Place of Performance: The work to be performed under this contract will be completed at the contractor’s facilities or when necessary, at the DSCA Headquarters (HQ), 201 12th Street South, Suite 300, East Tower Arlington, Virginia 22202 and/or Navy Supply Annex (NSA), 5450 Carlisle Pink, Mechanicsburg, PA 17050. The Government will not pay for contractor travel to Government locations.

1.5.5.1 Telework: The Government may permit telecommuting (telework) to contractors when determined to be in the best interest of the Government in meeting work requirements (e.g. COOP).

The contractor must identify to the COR any task/work requirements that may be performed at an alternate worksite.

The Individual contractor Personnel shall provide services from their authorized telework worksite location IAW Department of Defense Instructions (DoDI) 1035.01 Telework Policy.

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/103501p.pdf

1.5.6 Type of Contract: The government will award a Hybrid contract, which will consist of firm-fixed and labor hour pricing.

1.5.7 Security Requirements: The overall classification of work associated with this PWS is at the SECRET level.

The contractor shall have a current facility clearance of SECRET at the time of proposal to work this effort. All personnel assigned to this contract must be U.S. citizens.

1.5.8 Special Qualifications: Within ten (10) business days of award of this contract or ten (10) days of employment, 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 must maintain a cyber-threat security awareness certification plan.

http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/103501p.pdf

The contractor is expected to provide a fully trained workforce to the Government; therefore, personal development training costs and hours are not billable to the Government. The key positions can be found under paragraph 1.5.11.

1.5.9 Post Award Contractor/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 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.5.10 Contracting Officer Representative (COR): Refer to DFARS Clause 252.201-7000 “Contracting Officer’s Representative”.

1.5.11 Key Personnel: 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 chart for the three (3) key personnel positions.

1.5.11.1 Key Personnel Minimum Qualifications. Key personnel submitted require resumes and signed letters of commitment from the Key Personnel.

POSITION & TASKS QUALIFICATIONS

UI/UX Designer

PWS: 5.1, 5.2, 5.3, 5.4,

5.5, 5.6

Five (5) or more years of UI/UX design experience in Agile environments.

• Five (5) or more years of experience collaborating with cross-functional teams, including program, project, product management, engineering, and customers to create seamless user experiences and product innovation.

• Five (5) or more years of experience developing and communicating a clear design strategy ensuring that the user interfaces are intuitive, engaging, and aligned with business objectives. Five (5) years of experience identifying opportunities for improving user experience and defining the design roadmap.

• Five (5) or more years of experience in data visualization, creating wireframes, user flows, rapid prototyping, and conducting user research to understand user needs, behaviors, and pain points.

• Active Secret clearance Platform Engineer

Eight (8) or more years of experience in software engineering.

• Eight (8) or more years of experience developing and executing project plans, creating technical specifications, maintaining the operation and sustainment of systems, designing and developing test cases, adopting Agile methodologies to develop software, analyzing existing systems to provide recommendations for improvement, monitoring system performance and performing predictive maintenance, performing system risk and reliability analysis with a strong DevSecOps focus.

• Eight (8) or more years of experience building and deploying infrastructure with cloud deployment technologies.

• Eight (8) or more years of experience with Scrum or Agile development methodologies.

• Active Secret clearance

Backend Software Engineer

Five (5) or more years of experience with large technology systems.

• Five (5) or more years of experience supporting technology systems for DOD.

• Five (5) or more years of experience identifying opportunities for improving user experience and defining the design roadmap.

• Bachelor’s degree in Computer Science, Information Systems Technology, or

Information Technology

• Active Secret clearance

1.5.12 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. All contractor personnel will be required to obtain, use, and display a Common Access Card (CAC) throughout the performance of this requirement.

1.5.13 Contractor Travel: The Contractor shall be required to travel CONUS during the performance of this contract.

All travel shall occur on an “as needed” basis, as determined by the Socium Program Manager. Travel may be required outside of regular business hours. All travel requests shall be coordinated and pre-approved in writing by the Government COR prior to any trips within thirty (30) business days. Requests for approval of costs more than maximum per diem rates in accordance with the procedures contained in FAR 31.205-46(a)(3) must be submitted to the COR for final approval prior to commencement of travel. The Contractor is responsible for all travel arrangements including airline, hotel, and rental car reservations. The Contractor should estimate travel costs in accordance with FAR 31.205-46. The contract will designate a separate Contract Line-Item Number (CLIN) to cover travel costs. Trave will be coordinated with the Program Office and approved by the COR.

1.5.13.1 Safety: The contractor shall comply with all Federal, State, and local authorities having jurisdiction, and with safety and fire regulations promulgated by the Department of Labor’s Occupational Safety and Health Administration (OSHA) under Title 29, Section 1900 of the Code of Federal Regulations. Contractor is solely responsible for compliance and cost of compliance with Federal, State, and local laws and regulations. Contractor shall provide written notification to the Contracting Officer within twenty-four (24) hours of being notified by any Federal, State or local agency that a safety law and/or regulation has been violated. This report shall provide at a minimum the following: time and date of the occurrence, a description of the violation, required corrective action(s), and a projected correction date.

1.5.13 Other Direct Costs: N/A.

1.5.14 Data Rights: Reference FAR 52.227.14 Rights in Data clause.

1.5.15 Organizational Conflict of Interest (OCI): 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 OCIs as defined in FAR Subpart 9.5.

The contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI 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 OCI.

1.5.16 Phase – In: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the 30-day phase in period. During the phase in period, the Contractor shall become familiar with performance requirements to commence full performance of services on the contract start date. Moreover, the Contractor shall schedule, coordinate, and host a Project Kick-

Off Meeting at the location approved by the Government. The meeting shall provide an introduction between the Contractor personnel and DSCA Government personnel who will be involved with the Project/PWS. The meeting shall provide the opportunity to discuss technical, management, and security issues, travel authorization, reporting procedures, etc. The Contractor projects and services are required to be delivered on time and as required with accurate progress reporting. The Contractor shall provide a Project Kick-Off Meeting Agenda for review and approval by the CO and COR prior to finalizing. The agenda shall include, at a minimum, the following topics/deliverables:

a. Points of Contact (POCs) for all parties.

b. Personnel discussion (i.e., roles and responsibilities and lines of communication between contractor and

Government).

c. Project Staffing Plan that depicts the Contractor’s plan to achieve full staffing and transition-in of support.

d. Transition-In Plan.

1. Status of on-going projects.

2. Identification of POCs.

3. Location of technical and project management documentation, including Smartbook/turnover binders containing copies of all plans, policies, and procedures.

4. Status of ongoing technical initiatives and projects.

5. Incumbent contractor coordination to ensure a seamless transition.

6. Transition of Key Personnel roles and responsibilities.

7. Identification of schedules and milestones.

8. Identification of actions required of the Government.

9. Establishment and maintenance of effective communication with the incoming contractor and

Government personnel for the period of the transition via weekly status meetings.

e. Security discussion and requirements (e.g., building access, badges, Common Access Cards (CACs), etc.).

f. Financial reporting and invoicing processes

g. Present the Contractor’s Agile Development Management Plan (ADMP)

h. The Government will provide the Contractor with the number of Government participants for the Project

Kick-Off Meeting, and the Contractor shall provide copies of the presentation for all present.

i. The Contractor shall draft and provide Kick-Off Meeting Minutes Report documenting the discussion and capturing any action items. Meeting minutes requirement may be satisfied with recordings provided by Government collaboration tools (e.g., Microsoft Teams, Zoom for Government, etc.) and inclusion of an executive summary that summarizes the discussion and action items.

1.5.18 Phase-Out: The Contractor shall provide a phase-out plan no later than ninety (90) days prior to expiration of this contract. The contractor shall maintain documentation that is assessable to designated government representatives via a web portal or other electronic means as designated by the government. Prior to the end of the contract, the incumbent contractor shall support a thirty (30) calendar days transition period with the in-coming contractor. The contractor shall overlap with an incoming contractor during transition and will work with Government personnel and the incoming contractor to transfer knowledge, information, and documentation for all projects and tasks related to this contract. The type of information and documentation to be transferred includes, at a minimum:

• Points of Contacts

• Location of technical and project management documentation

• Program data, databases and data management systems

• Status of ongoing technical initiatives and deliverables

• Appropriate contractor-to-contractor coordination to ensure a seamless transition

• Identify schedules, deliverables, and milestones

• Identify actions required of the Government

• Establish and maintain effective communication the incoming contractor/Government personnel for the period of the transition via weekly status meetings. The Contractor shall facilitate the accomplishment of a seamless transition from the incumbent to an incoming contractor at the expiration of the PWS.

1.5.18.1 The Contractor shall develop a Transition-Out Plan for transitioning and delivering all material and information to the Government.

1.15.18.2 The Plan shall identify all Government-Furnished Material (GFM) and Contractor-Furnished Material (CFM) as well as information and material developed during the PWS that was used in the execution of this PWS.

1.15.18.3 The Transition-Out Plan shall be submitted for Government approval. Upon incorporation of comments and Government acceptance, the Contractor shall follow the Plan to transfer all material, information, and rights thereto to the Government.

1.15.18.4 The Contractor shall facilitate and conduct transition-out activities.

1.15.18.5 The Contractor shall update system descriptions and technical descriptions of all software, systems, and support activities delivered or performed under this PWS.

1.5.18.7 The Contractor shall support transition of administrative and privileged access to the incoming contractor/Government, ensuring that no administrative access is lost.

1.5.18.8 The Contractor shall prepare a Final Contract Report documenting the status of all ongoing efforts and projects and a list of the physical and electronic storage location on each domain of existing plans, policies, procedures, POCs, technical diagrams and documentation, and other information requested by the Government.

Transition-out shall ensure no disruption to vital Government business.

1.5.18.9 The Contractor shall provide full cooperation in providing necessary operational knowledge to the incoming contractor.

1.15.18.10 The Contractor’s Transition-out shall include the following types of services and information for knowledge transfer:

1. Status of on-going projects.

2. Identification of POCs.

3. Location of technical and project management documentation, including Laptop/turnover binders containing copies of all plans, policies, and procedures.

4. Deletion of any meetings scheduled using an individuals email account instead of the shared mailbox.

5. Status of ongoing technical initiatives and projects.

6. Incumbent contractor coordination to ensure a seamless transition.

7. Transition of Key Personnel roles and responsibilities.

8. Identification of schedules and milestones.

9. Identification of actions required of the Government.

10. Establishment and maintenance of effective communication with the incoming contractor and

Government personnel for the period of the transition via weekly status meetings.

PART 2

DEFINITIONS & ACRONYMS

2 DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. BUSINESS DAY. The term business day means Monday through Friday, except the legal public holidays specified in PWS section 1.5.3.

2.1.2. 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.3. 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.4. 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.5. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

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

2.1.7. 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.8. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

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

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

2.1.11. 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.12. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.2. ACRONYMS:

ADMP Agile Development Management Plan AECA Arms Export Control Act ATO Authority to Operate AVS Adjudication and Vetting Services CAC Common Access Card CDS Cross Domain Solution CFM Contractor-Furnished Material CFR Code of Federal Regulations CLIN Contract Line-Item Number COI Community of Interest CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative DAG Director’s Action Group DevSecOps Development, Security, and Operations DFARS Defense Federal Acquisition Regulation Supplement DOD Department of Defense DODI Department of Defense Instructions DSCA Defense Security Cooperation Agency FAA Foreign Assistance Act FAR Federal Acquisition Regulation FOIA Freedom of Information Act FSO Facility Security Officer GFI Government Furnished Information GFM Government Furnished Material HQ Headquarters IAW In Accordance With IL4 Impact Level 4 IM&T Information Management and Technology ISL Industrial Security Letter ITFM IT Financial Management ITSM IT Service Management ITP Insider Threat Program KO Contracting Officer KUC Key User Committee LOE Level of Effort MOSCOW Must-have, Should-have, Could-have, and Won’t have MS Microsoft NDA Non-Disclosure Agreement NIPR Non-classified Protocol Router NSA Navy Supply Annex O&S Operation & Sustainment OCI Organizational Conflict of Interest OSHA Occupational Safety and Health Administration PO Product Owner POC Point of Contact 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 Program RMF Risk Management Framework SC Security Cooperation

SIPR Secret Internet Protocol Router SME Subject Matter Expert TE Technical Exhibit VAR Visitor Authorization Request WAR Weekly Assessment Report WBS Work Breakdown Structures

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3 GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services: The Government will provide access to DSCA Headquarters (HQ), 201 12th Street South, Suite 300, East Tower Arlington, Virginia 22202 and/or Navy Supply Annex (NSA), 5450 Carlisle Pink, Mechanicsburg, PA 17050.

3.2. Facilities: The Government will provide the necessary workspace for the contractor staff to provide the support outlined in the PWS to include desk space, telephones, computers, and other items necessary to maintain an office environment.

3.3. Utilities: The Government will provide all utilities in the facility available for the contractor’s use if the contractor is working at a DSCA facility.

3.4. Equipment: The Government will provide the contractor Government equipment required to complete PWS tasks. The Contractor shall maintain and submit an active inventory of all GFE provided by the Government. This inventory shall identify all GFE provided by the government including make, model, category, serial and/or inventory number where available, and the individual to whom the GFE is issued.

3.5. Materials: The Government will provide the contractor access to regulations, directives or other policy documents required to complete PWS tasks.

3.6 Systems: The Government will provide the contractor with access to systems needed to complete PWS tasks including interacting with Government personnel.

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 possess and maintain a SECRET facility clearance from Defense Counterintelligence and Security Agency (DCSA) at quote submission. 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 Form 254 is provided as an attachment.

PART 5

SPECIFIC TASKS

5. Specific Tasks:

5.1. Task 1 Basic Socium Services: The contractor shall provide services for O&S and continued Socium development.

5.2. Task 2 Agile Framework and Project Management: The contractor shall coordinate between the developers infrastructure support, data support, cyber management, customer support, and research development innovation teams to ensure the development and operation and sustainment are in alignment. Additionally, the contractor shall prepare and update, as requested, product and project management documentation for efforts designated by DSCA IM&T as projects to be tracked and reported. Agile and project management system updates and documentation shall include the following: product backlog, sprint backlog, user stories, burndown/burnup charts, and retrospective notes, project plans, product roadmaps, and schedules prepared and updated in Microsoft (MS) Project, JIRA, ServiceNow, or other formats/applications agreed upon by the Government. Contractor will provide capability roadmaps, feature roadmaps, acceptance criteria, definition of done, Work Breakdown Structures (WBS), activities, milestones, schedules, or other process documentation, reporting, Agile and project management artifacts, and information as appropriate for the project.

5.2.1 To support DSCA IM&T planning and decision processes, the contractor shall deliver cost estimates, level of effort (LOE) estimates, staffing plans, project plans, technical approach documentation, and other decision support information. The contractor shall provide project-level tracking (e.g., funds expenditures, EVM, EAC, work completion, etc.) for project-based activities as appropriate for the project and when directed in the government agreed/approved system (ServiceNow, etc.). The contractor will provide:

5.2.2 Revised staffing plans and cost estimates that capture changes in Level of Effort (LOE) resulting from evolving Socium requirements and summary of enhancements.

5.2.3 A Weekly Assessment Report (WAR) updated and presented as a “Quad Chart” (or other technical formats as approved by DSCA IM&T Program Manager) detailing the project's progress, including but not limited to, the name of the capability, feature, sprint, tasks, the report date, summary of the week's work, upcoming week's action plan, challenges, risks, and mitigation strategies. These will be delivered during a bi-weekly meeting.

5.2.4 A one-page “Quad Chart” (or other technical formats as approved by DSCA IM&T Program Manager) updated and presented monthly for each designated project, including a short project description, overall status, risk statements including severity (impact and likelihood) and recommended mitigations, next actions, and scheduled milestone(s) status.

5.2.5 Participation in related management meetings, Ad-Hoc meetings, technical working groups, technical interchange meetings, and program management reviews. The vendor shall support technical requirements review meetings throughout the period of performance in support of Socium O&S development activities. These meetings can include but are not limited to non-recurring and recurring (on a daily, weekly, or monthly basis), stand-up meetings, IT leadership meetings, project and technical status briefings, requirements reviews, technical exchanges meetings with internal and external organizations, recurring briefings to Government leadership, and other briefings and meeting support as required. All re-occurring meetings must be scheduled using a shared mailbox for continuity.

5.3. Task 3 Agile Development Management: This PWS defines the functionality desired for Socium at a high-level.

Socium requirements will be refined adaptively and iteratively over the course of the effort, continuously evolving to meet specified user needs which will be prioritized based on mission value and technical dependencies. Priorities will be reflected in roadmaps, sprint plans, and the Product Backlog. The government will designate a key stakeholder Product Owner (PO), who will be responsible for working with the Community of Interest (COI) and articulating work/priorities to the Contractor. Additionally, the Continued delivery of enhanced functional capabilities, subsequent releases, and any additional requirements will be through the contractor established agile engineering environment processes that at a minimum includes the following that the contractor will provide:

5.3.1 Proposal of an Agile Development Management Plan (ADMP) that demonstrates how the contractor intends to manage, develop, implement, and maintain the requirements described in this PWS. The ADMP is required thirty days after award. The ADMP will support the contractor’s approach to Agile software development, best practices and include, at a minimum, the following topics/deliverables:

5.3.1.1 Development of a determination process to govern the complexity of developing, estimating, integrating, delivering, and describing the necessary activities to support Socium’s Agile development aligning to a capabilities and features roadmap.

5.3.1.2 A notional release schedule which maps the proposed iteration cycle to the calendar Period of Performance including relevant governance process checkpoints, e.g., technical reviews, iteration releases, agile methodology functions such as Iteration Planning, Iteration Reviews, and Retrospectives, testing, training, security, cut over planning, etc. DSCA standard agile schedules are two weeks sprints with a release at every sprint.

5.3.1.3 An approach and methodology for Socium stakeholders’ business requirements gathering.

5.3.1.4 A methodology for working with the PO in a continuous, iterative fashion throughout the development process to establish and prioritize capabilities, features, stories, acceptance criteria, etc. based on discovery/user research findings.

5.3.1.5 A methodology to configure, test, stage, and release Socium in alignment with the Agile methodologies and release schedule. As well as provide the full range of System/Software Development Lifecycle activities to include requirements, analysis, design, development, test, security and deployment.

5.3.1.6 A methodology for incremental documentation through sprint cycles that results in full technical and end-user documentation or configuration for all software development efforts and product releases with all information necessary to document processes, procedures, code artifacts, and/or policies that were implemented in the creation of the development work.

5.3.1.7 A methodology to understand the federal PO’s needs and goals, iteratively develop and update (as relevant) the product vision, product roadmap(s), and product backlog(s) with associated user stories.

5.3.1.8 A methodology for user testing and acceptance review.

5.3.1.9 A methodology for Data Management.

5.3.1.10 An account for accessibility considerations and ensure that Section 508 requirements are considered, designed for, and met.

5.3.1.11 A methodology for clarification on requirements during Agile ceremonies such as recurring backlog refinement sessions to continuously refine and prioritize requirements and decision-making during sprint planning and implementation.

5.3.1.12 A methodology for work prioritization such as Must-MOSCOW, facilitate Scrum Meetings, Sprint planning, Backlog Refinement, Sprint Reviews, Sprint Retrospectives, and provide records.

5.4. Task 4 Agile Product Owner Support: This PWS defines the functionality desired for Socium at a high-level.

Socium requirements will be refined adaptively and iteratively over the course of the effort, continuously evolving to meet specified user needs which will be prioritized based on mission value and technical dependencies. Priorities will be reflected in roadmaps, sprint plans, and the Product Backlog. The government will designate a key stakeholder Product Owner (PO), who will be responsible for working with the Community of Interest (COI) and articulating work/priorities to the contractor. Additionally, the continued delivery of enhanced functional capabilities, subsequent releases, and any additional requirements will be through the contractor established agile engineering environment processes that at a minimum include the following:

5.4.1 Facilitated user acceptance testing with priorities reflected in roadmaps, sprint plans, and the product backlog.

5.4.2 Provide stories with the requisite information to complete the work and refine stories adaptively and iteratively over the course of the effort and document stories in Jira, ServiceNow, or approved application.

5.4.3 Coordinate all activities (analysis, design, development, testing and deployment) required to complete each story as defined by the Acceptance Criteria and Definition of Done. Stories and sprints include the PO’s acceptance criteria and definition of done.

5.4.4 Stories are required to be approved by the PO, the contractor will ensure stories include acceptance criteria and a definition of done.

5.4.5 Support the PO who will define and prioritize user stories via the backlog.

5.4.6 Support the PO in Agile based requirements gathering, conducting interviews, surveys, facilitated sessions, end-user requirements gathering, etc.

5.4.7 Identify all tasks required to successfully complete each story, show traceability, and the dependencies between requirements e.g., epics, themes, stories, tasks, and systems.

5.4.8 Effectively facilitate scrum and agile events by customizing the facilitation materials based on the nature of the discussion and the audience.

5.4.9 Project information, such as estimates and productivity metrics will be made available to the government in real time, using a government approved dashboard or project management system providing such visuals as burn-down charts, resource assignment, and test results.

5.4.10 Establish a collaborative planning process and methodology to facilitate collaboration meetings to refine, prioritize, schedule, and maintain the Socium backlog.

5.4.11 Engage with the Community of Interest (COI), Key User Committee (KUC), and Government Program Team, including the Product Owner, as required to assist the PO in refining and prioritizing the backlog for each sprint.

5.4.12 Leverage DSCA’s NIPRNet and SIPRNet deployment environment to enable verification of Socium capabilities, collect and integrate user feedback, promote deploy-ability and testability, and measure outcomes.

5.5 Task 5 Development, Engineering, and Capability: The contractor will be responsible for working with the application team, infrastructure support, IT operations, architecting, engineering, developing, configuring, customizing, optimizing, securing, designing, developing workflows, data management, creating orchestrations, performing releases, coordinating meetings and other technical exchanges, and create reporting necessary to develop and sustain Socium for the Government. Additionally, Socium related IT system, Cross Domain Solution (CDS), system integration, interface, development, browser capability, responsive design, cyber security (Risk Management Framework (RMF)/Authority to Operate (ATO)/Cyber Issues), 508 Compliance, support current environment transition and all future transitions, and additional related services will be delivered seamlessly across the system lifecycle and fully coordinated across DSCA to achieve delivery on time and as required. Various required reporting of these activities is listed in Technical Exhibit 2, Deliverables Schedule. The contractor will provide the full range of expertise and experience required to continually meet the evolving Socium mission requirements to identify and recommend solutions to challenges associated with day-to-day service delivery and mission performance that at a minimum includes the following:

5.5.1 The contractor shall be responsible for all development, deployment, and release activities such as release notes, development, testing, user acceptance testing, troubleshooting, and deployment activities across all instances and deliver capabilities to internal customers, external customers, and mission partners.

5.5.2 The contractor shall test and validate software products at the system and subsystems using an automated testing approach to validate that functional requirements were implemented and continue to function over the development of the final solution.

5.5.3 Meet DSCA’s standardization of technical guardrails systems.

5.5.4 Ensure Socium related services are delivered seamlessly across the system lifecycle and fully coordinate/manage/align across functional areas/DSCA to achieve delivery on time and as required.

5.5.5 Enterprise-level architecture and engineering services to innovate, design, engineer and deliver capabilities in response to requirements to support internal users and external mission partners operating on NIPRNet and SIPRNet.

5.5.6 Design, engineering, and delivery of solutions, cloud development, and DOD mandated capabilities (e.g., Zero Trust, Comply to Connect, analytical capabilities, etc.)

5.5.7 Design, documentation, engineering, and implementation support for DSCA IM&T DevSecOps platform(s) to continuously modernize and optimize the applications, systems, and enable automated capability delivery methods (e.g., Continuous Integration/Continuous Delivery, etc.) for use by Socium Stakeholders, etc. This includes development in cloud hosting environments and hybrid environments.

5.5.8 Proposing and updating delivery pipelines, processes and procedures in alignment with Socium’s evolving DevSecOps and capability delivery strategy and requirements.

5.5.9 Ensure support for new, specialized, or tailored delivery pipelines that are adapted to mission use cases and delivery requirements.

5.5.10 Making recommendations for innovations and improvements in Socium capabilities that result in increased efficiency, improved services, and reduced costs to the government while maintaining alignment with Socium mission priorities.

5.5.11 The contractor shall investigate and recommend solutions to problems associated with day-to-day service delivery/provisioning/etc.

5.5.12 Training Support for End Users: The vendor will provide Socium training support, providing either embedded or web-based training tools to facilitate effective individual and collective team, staff, and unit training essential training elements. Develop electronic training materials for each end user role or ‘persona’ e.g., training videos and/or other training material. Train DSCA trainers plus designated organizational SMEs (subject matter expert) to train future Socium users. Update or replace any training material that is outdated, incorrect, or overcome by new development. Use the DSCA SOCIUM knowledge base to store all materials. Confirm all training information is also linked correctly in the SOCIUM application.

5.5.13 Training Support to DSCA Service Desk: Train DSCA Service Desk Technicians to provide Level I and II support to Socium users.

5.5.14 Training Support to DSCA System Engineers, Systems Administrators, etc.: Train DSCA systems engineers, systems administrators, developers, and analysts to provide Socium O&S.

5.6 Task 6 Operation & Sustainment Services: For Socium, O&S services refer to the Agile based ongoing activities needed to keep IT systems, application, and infrastructure running smoothly, including application, maintenance, fixes, and upgrades. Using the Agile methodology, the contractor shall design, develop, test and package systems and software changes as well as provide problem resolutions for the existing system. The contractor shall maintain the current baseline of the system and provide software changes and problem fixes to these baselines as required. The contractor shall provide to the Government all developed, modified or converted source modules, processes, programs, scripts, operating instructions, databases, system files, documentation, test files and test conditions used to develop each approved systems change request. The contractor shall administer, maintain, remediate, and provide the support required for internal and partner users operating on Socium NIPR and SIPR.

5.6.1 The contractor will maintain existing systems and environments IAW the organizations policy, procedures, and guidance or disciplined engineering practices and sustain applications, databases and interfaces in compliance with applicable DOD standards. Additionally, the contractor will perform system performance tuning, system re-hosting and integration services, while also provide Socium sustainment support, bug fixes, SLAs for bugfixes, use and follow organizational guidance on ServiceNow for service desk ticketing, configuration, administration, operations, maintenance, and operational availability, environment cloud migration support, data migration support, application migration support, create supporting cyber artifacts, integration, testing, and staging for NIPR and SIPR support to Socium.

5.6.2 Support cloud-specific development, cloud implementations, cloud migration, test environments, infrastructure, systems, and shared environments in support of Socium. Maintain existing systems and environments IAW disciplined engineering practices and sustain applications, databases and interfaces in compliance with applicable DOD/DSCA/IM&T standards.

5.6.3 Provide mission operations support, migration support, including administration and capability delivery support utilizing Socium’s DevSecOps and CI/CD capability pipeline(s), containerized application provisioning, hosting…