APPS_PWS_Bridge_18July2019.docx

Performance Work Statement (PWS) for

AFGHAN PERSONNEL AND PAY SYSTEM

SUSTAINMENT MANAGEMENT

Version 1.6

18 July 2019

Add ORGANIZATION EMBLEMS

UNCLASSIFIED/ACQUISITION SENSITIVE

UNCLASSIFIED/ACQUISITION SENSITIVE

DISTRIBUTION STATEMENT C. Distribution authorized to U.S. Government agencies and their contractors (Foreign Government Information) (date of determination). Other requests for this document shall be referred to PEO EIS/PL AIT.

UNCLASSIFIED/ ACQUISITION SENSITIVE

FOR OFFICIAL USE ONLY

FOR OFFICIAL USE ONLY

A-3

Table of Contents

List of Appendices

List of Tables Table 1 - Deliverable Matrix 39

List of Figures ii

UNCLASSIFIED/ACQUISITION SENSITIVE

iii

AFGHAN PERSONNEL AND PAY SYSTEM

SUSTAINMENT MANAGEMENT PWS

INTRODUCTION

Combined Security Transition Command – Afghanistan (CSTC-A) trains, advises, and assists within the Afghan Security Institutions to develop Resource Management, Inspector General (Transparency, Accountability and Oversight), and Rule of Law capabilities. Additionally, CSTC-A provides resources in accordance with the Afghan National Defense Security Forces (ANDSF) requirements while ensuring fiscal oversight, accountability of funds and materiel delivery. CSTC-A is focused on helping Afghanistan develop a sustainable, effective and affordable ANDSF in support of the Government of the Islamic Republic of Afghanistan (GIRoA). The intent of the Afghan Personnel and Pay System (APPS) is to replace a manual paper-based personnel and payroll system with an online, automated information system to streamline accountability and reduce corruption.

General Administrative Instructions The Contractor, as an independent entity and not as an agent of the U.S. Government (USG), shall provide the necessary resources and personnel to accomplish all tasks set forth below.

Contractor employees performing services under this contract shall be managed, directed and supervised at all times by authorized Contractor personnel. Actions of Contractor employees may not be interpreted or implemented in any manner that results in: (1) creating or modifying Federal policy; (2) unlawfully obligating the appropriated funds of the USG; (3) overseeing the work of Federal employees; (4) providing direct personal services to any Federal employee; or, (5) otherwise violating the prohibitions set forth in Parts 7.5 and 37.1 of the Federal Acquisition Regulation (FAR). The Contractor's management team shall ensure that assigned employees complete all contracted tasks to the standards described in this PWS and any subsequent contract modification(s).

The Contractor shall provide qualified engineering and technical services to fulfill the performance standards outlined in this Performance Work Statement (PWS) and any subsequent contract modification(s). The Contractor shall perform work at the Contractor’s facilities and at GIRoA sites in accordance with (IAW) this PWS. The Contractor is required to attend meetings at USG facilities in Kabul, Afghanistan. The USG will control access to the Government facilities and perform the inspection and acceptance of completed tasks described in this PWS and any subsequent contract modification(s).

Background APPS is an enterprise resource planning and payroll system for Afghanistan National Defense and Security Forces (ANDSF), specifically for the Afghanistan National Army (ANA) of Ministry of Defense (MoD) and Afghanistan National Police (ANP) of Ministry of Interior (MoI).

APPS integrates and automates the processes for personnel records management and payroll of individual soldier and police. Specifically, it provides: 1) human capital management capabilities in terms of Tashkil authorization planning and implementation, recruitment management and force strength management; 2) payroll and compensation report generation; 3) pension information management; and 4) report generation. The implementation of APPS is to enhance transparency and audit capability, and strengthen personnel accountability. In essence, APPS capabilities enable the ANDSF to manage current personnel and payroll requirements while providing a planning and projection capability required to budget for out-year requirements in both payroll and retirement compensation.

Objectives The Contractor shall support the APPS Program Management Office (PMO) goals and objectives focusing on best business practices and technical expertise necessary to enable ANDSF to sustain the currently deployed system. The Contractor shall provide technical support, services, and maintenance for the APPS capability that will provide GIRoA with a robust automated personnel and pay system.

Scope The Contractor shall provide technical support and subject matter expertise to enhance the APPS suite of programs, improve performance, maintain the system to optimum levels, provide data base entry, configuration management, quality control, systems administration and cyber security as outlined in this PWS. The Contractor shall continue to attend, coordinate, and/or lead Technical Exchange Meetings (TEMs) focusing on those areas where technical exchange is necessary to ensure program interests are addressed. The Contractor shall maintain the APPS baseline, operational control of source code, and maintenance of the system architecture. During the Period of Performance (PoP) of this effort, the Contractor shall assist with the transition of the APPS to the GIRoA.

APPLICABLE DOCUMENTS

References and Standards of this PWS are provided for information and guidance in the execution of this effort. The contractor must ensure that it obtains and complies with the latest version of the Government and commercial documents listed in the PWS and its attachments at the time of proposal submission.

All work, tasks, deliverables and requirements in this effort shall be governed and the contractors’ performance measured by the references, standards, USG-furnished information and site-specific guidance provided in this PWS.

References, standards, policies and guidance referenced within one of the documents in this section are, by default, applicable to the performance of this effort.

The contractor shall be responsible for ensuring complete knowledge of the applicable documents listed in this section necessary to execute this effort successfully.

The contractor must ensure it obtains and complies with the most current version of the USG and commercial documents listed in this section.

a) IA-748-B, Earned Value Management Systems, JUN 2007, Electronic Industries Alliance.

TECHNICAL REQUIREMENTS

This effort provides for systems engineering, sustainment, life-cycle maintenance, system documentation, training, and management support for all existing APPS applications and modules.

Sustainment The contractor shall maintain the current baseline of the system software and hardware and provide software change and problem fixes to these baselines as required. The Contractor shall provide to the USG 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 perform sustainment requirements to maintain the system to optimum levels.

System Administration The Contractor shall provide System Administration services to include administration on table structures, access to data, replication support, disaster recovery procedures and backups.

The contractor shall support system upgrades to hardware, software, and databases to maintain the system requirements for throughput, response times, and quality of service and system security posture.

Deficiencies and Enhancements The USG estimates a responsible contractor will require a minimum of six full-time equivalents (FTE) to support system deficiencies and enhancements.

Deficiencies The Contractor shall document, assess, prioritize, and report system deficiencies, and develop the required design changes to resolve operational issues. The contractor shall provide root cause analyses of issues and deficiencies as required. When implementing corrective actions and system repairs, the Contractor shall follow configuration management and maintenance processes while monitoring key sustainment metrics.

Enhancements The Contactor shall update, enhance, and add capability to the system baseline through continuous modernization. The Contractor shall document, assess, prioritize, and report system enhancements. When implementing updates, enhancements, and new capabilities, the Contractor shall follow configuration management and maintenance processes while monitoring key sustainment metrics.

Database Management The Contractor shall perform database management services to effectively meet the APPS PMO Data Server, Application Server, and Database requirements. The Contractor shall provide database services to include operations, monitoring, maintenance and life cycle support to the APPS sites.

The contractor shall demonstrate a good understanding of the data and access procedures necessary to support end-user requirements for data analysis and data mining.

The Contractor shall collect and store database information. The Contractor shall provide system support, administration and database maintenance for the APPS server sites.

The Contractor shall perform database administration, including indexing and backup/recovery, performance analysis and tuning, data dictionary maintenance, and database design on all database instances.

Availability Management The contractor shall ensure services, to include technical and functional, are available 24 hours per day, 7 days per week. The contractor shall provide the necessary support to address system outages within four hours from time of incident.

Tables and Matrices The contractor shall update and maintain tables and matrices.

System Architectures The contractor shall update and maintain the detailed system architectures to include: system schematics, including system and subsystem performance-based descriptions, and key interfaces between them.

Hardware and Software Specifications The contractor shall update and maintain hardware and software specifications to include: sizing and performance requirements, systems and subsystem, interface requirements, and systems control requirements.

Database and File Structures The contractor shall update and maintain database and file structures to include: definitions of file characteristics, file layouts, data dictionary entries, file indices for each subsystem and database schema and subschema.

Input and Output Design The contractor shall finalize the input and output design to include: data flows, data dictionary entries, dialogue specifications and lists of all inputs and outputs by subsystem.

Special Design Considerations The contractor shall update and maintain all existing special design considerations to include: network design approaches, data control, security and audit procedures; archived historical data, current data purging and data entry criteria, scheduling, disaster recovery, special quality assurance (QA) factors and configuration control (QC) requirements.

Specifications The contractor shall update and maintain all existing specifications to include: detailed processing logic for each module, data dictionary entries for parameter data and list of compiled and load units for each design unit and their component modules.

Capacity Requirements The contractor shall update and maintain all existing system hardware and software capacity requirements and any associated limitations. Specifically, coordinate with the Ministries to identify facility limitations and considerations.

Architecture Framework The contractor shall create, update, and maintain all Architecture Framework views and products to include; all views, operational views, system views, and technical views where applicable.

Pay Table Adjustments The Contractor shall maintain Pay Table Adjustments and additional APPS pay incentives, as required. This may include additional pro-pays and incentive pays identified during the performance of this effort.

System Log Monitoring, Analysis, and Management The Contractor shall maintain an audit program for system log/event monitoring, periodic analysis and reporting procedures and policies. The Contractor shall retain system logs for a period of no less than 12 months with three months available online and up to nine months archived. The Contractor shall review system logs weekly for anomalies and violations using Security Information and Event Management (SIEM) software. The following is the minimum event information to be captured detailed in the Preventive Maintenance Service Plan IAW the CDRL at Appendix A of this PWS:

a) Date/Time Stamp

b) User Identification

c) Event Type

d) Success/Failure

e) Event Description/Activity

f) Target System or Data Source Policies and Procedures to include:

a) SIEM Event Logging

b) Protection of Log Information

c) Administrator and Operator Logs

d) Systems Clock Synchronization Server Administration The Contractor shall manage and maintain multiple servers and the associated hardware in all environments.

The Contractor shall manage, maintain, and deploy server images, software baselines and patches, and maintain system baselines.

The Contractor shall maintain and deploy application configuration settings.

The Contractor shall perform maintenance updates to the existing servers.

Network Management and Administration The Contractor shall manage, configure, and monitor all APPS network devices.

The Contractor shall manage, configure, and troubleshoot subnets and Virtual Local Area Networks (VLANs).

The Contractor shall monitor, track, and manage Internet Protocol (IP) addresses.

The Contractor shall report any network outages as an incident.

Maintenance The Contractor shall be responsible for the operations and maintenance support of all hardware, software, and peripherals associated with the APPS capability, to include making repairs to the system.

Preventive Maintenance The Contractor shall develop and deliver, for USG approval, a Preventive Maintenance Service Plan based on the hardware and software components developed and delivered as part of the APPS capability. The Preventive Maintenance Service Plan shall, at a minimum, include routine and non-routine maintenance requirements. Preventative maintenance inspections and work shall be conducted on a weekly basis with a monthly Maintenance Service Report provided to the Ministry and APPS PMO Contracting Officer’s Representative (COR). The contractor shall provide the Preventive Maintenance Service Plan and Maintenance Service Report IAW the CDRL at Appendix A of this PWS.

Preventive Maintenance Service Plan The Contractor shall execute a Preventive Maintenance Service Plan that incorporates the following steps in alignment with standard accepted commercial business practices to ensure viruses, updates, spyware, malware and unauthorized users are unable to access the system. Some of the tools and measures that the vendor shall use include, but are not limited to:

a) Virus program updates

b) Virus definition updates

c) Review event logs

d) Spyware Removal

e) Data restoration tests

f) Removal and analysis of temporary hidden files

g) Scandisk

h) Defragmentation

i) Bios and Firmware updates

j) Service pack installation for software

k) Server image creation

l) Physical scan of computer

m) Hard Drive Data Recovery Preventive maintenance and other related activities shall be coordinated with the respective departments to ensure on time delivery of service. If during these inspections and testing periods, issues are discovered, the Contractor shall provide a Maintenance Service Report of the issue to the owning organization IAW the CDRL at Appendix A of this PWS. The Contractor shall coordinate with the organization to fix/repair the issue within four hours.

Systems Software Government Repository The Contractor shall provide all source code and pertinent APPS capability artifacts, including those identified in and all deployment disks, to the APPS PMO Technical Representative or designee IAW the CDRL at Appendix A of this PWS. The Contractor shall maintain an up-to-date document library in support of the APPS capability.

Data Visualization The Contractor shall maintain the software system display processes and visualization capabilities for APPS resource data. APPS resource data includes Authorization, Recruitment, Personnel, Compensation, Payroll, and Pension data modules. The Contractor shall provide software maintenance for all APPS resource software processes and display software.

Language and Regional Expertise Requirements The Contractor shall maintain the software system display processes and visualization capabilities to support language and regional expertise requirements. All modules will display data in English, Dari and, Pashtu.

Systems Configuration System Configuration Identification The Contractor shall maintain Configuration Baselines (Functional, Allocated, and Product) to provide identification of configuration items such as: documentation, data, services, processes, hardware, software, and firmware. The Contractor shall prepare required functional, allocated, and product-specific configuration baselines to include a complete listing of technical documentation, physical and logical configuration items, and any change requests defining the authorized configuration of the Government equipment/system’s functional and physical characteristics. The Configuration Baselines shall be provided IAW the CDRL at Appendix A of this PWS.

Systems Configuration Status Accounting Database The Contractor shall maintain a Configuration Status Accounting (CSA) database, which represents the configuration of the Systems Baseline. Systems baselines and changes shall be documented in the Contractor’s CSA database and provided IAW the CDRL at Appendix A of this PWS. The Contractor shall permit acceptance of commercial product information in the CSA database.

Systems Configuration Documentation The Contractor shall maintain an internal configuration management system for the control of system baseline configuration documentation, physical media, physical parts and software/firmware representing or comprising the system baseline. For software, the system shall address the evolving configuration and support environments of the systems baseline. The Contractor shall provide a Configuration Management Plan as part of the Program Management Plan IAW the CDRL at Appendix A of this PWS to identify software that comprises the APPS baseline.

Technical Data Package (TDP) The TDP will be used to document the Systems Baseline. The contractor shall provide the TDP IAW the CDRL at Appendix A of this PWS.

Software Engineering and Configuration/Change Review Boards The Contractor shall participate in Engineering Review Boards (ERB), Configuration/Change Control Boards (CCBs), and inspections to formally assess the maturity of Contractor-developed software, identify defects and defect trends, record corrective actions, and obtain technical authorization to release documents and drawings when directed to do so by the USG. External products shall be reviewed at regular intervals with USG teams, including final product review.

Training The contractor shall provide centralized MoD and MoI train-the-trainer services on a quarterly basis in the Kabul area for a total of 8 sessions per year (4 MoD sessions and 4 MoI sessions). MoD and MoI train-the-trainer sessions shall be tailored to the respective ministry. This training will cover operator, leader, and auditor/inspector training for all MoD and MoI APPS trainers. Training will be conducted in three different methods: 1) class room training, 2) over the shoulder training and 3) computer based training, covering the following areas:

a) APPS transactional processes for each module

b) APPS Analytical tools

c) APPS Reports generation

d) APPS business process execution for each module

e) Basic computer sills

f) Protecting Personally Identifiable Information

g) Importance of protecting the APPS information and data

h) Data at Rest requirements Contractor shall prepare materials to support an average class size of 30 students. The contractor shall develop and provide all training materials, aids, and manuals. Each new student must be provided a complete set of user manuals for their respective class, at the start of training, regardless of automated or online training tools available.

The contractor shall design, develop, document, and maintain an embedded Electronic Performance Support System (EPSS). This system shall provide up-to-date user documentation at all levels to enable end-user to directly access all training, user manuals, and applicable policy for the transaction or activity page currently being used while logged into the system.

Language Requirements Supervisory personnel and help desk operators shall at minimum have a Level 3 (as defined by the US Department of State Language Proficiency Definitions) proficiency in Dari and Pashtu and a Level 2 (as defined by the US Department of State Language Proficiency Definitions) in English. Reference website: https://careers.state.gov/faq-items/language-proficiency-definitions/.

Assessment of Training The contractor shall assess all trainees (to include Operators, Leaders, Auditors and Inspectors, Help Desk Operators and Database Administrators) of their comprehension level of the APPS training by written tests. Upon the completion of the training those trained must possess the competency, proficiency, and skills required to operate maintain/sustain the APPS systems.

Help Desk and Customer Support Operations The contractor shall provide training for APPS Help Desk support for each ministry. The contractor shall train ANDSF personnel in all Help Desk operations (Tier I, II, and III). The contractor shall also provide APPS Help Desk hardware and software support.

Background The Help Desk provides technical support to the sites by phone, email or visits to the sites.

The Help Desk generates reports on issues raised by MOI and MOD and assists the ministries in correcting repetitive issues.

The contractor shall train the ANDSF Help Desk operators in accordance with the following Tiers:

Tier I: The initial support level responsible for basic customer issues. The first job of a Tier I specialist is to gather the customer’s information and to determine the customer’s issue by analyzing the symptoms and figuring out the underlying problem. When analyzing the symptoms, it is important for the technician to identify what the customer is trying to accomplish so that time is not wasted on attempting to solve a symptom instead of a problem.

Tier II: Is a more in-depth technical support level than Tier I. Technicians are more experienced and knowledgeable on a particular product or service. Technicians in this tier are responsible for assisting Tier I personnel in solving basic technical problems and for investigating elevated issues by confirming the validity of the problem and seeking for known solutions related to these more complex issues.

Tier III: Is the highest level of support in a three-tiered technical support model responsible for handling the most difficult or advanced problems. Technicians are experts in their fields and are responsible for not only assisting both Tier I and Tier II personnel, but with the research and development of solutions to new or unknown issues.

Help Desk Training The contractor shall train MoI and MoD Help Desk Tier I, Tier II, and Tier III operators to fulfill all defined responsibilities in section 3.6.1.

Trained Tier II and III Help Desk support shall be capable of developing a continuous log of Frequently Asked Questions (FAQ) with validated answers.

Contractor Help Desk Support The Contractor shall provide hardware (HW) and software (SW) support to include the following:

a) Maintain configuration management of complete service records

b) Research, test, document validation and load patches and upgrades as directed

c) Investigate and repair site databases

d) Test other software packages, such as anti-viral software and patches, on the test system as directed by the APPS PMO to ensure that software does not conflict with the existing baseline prior to execution

e) Test other hardware as directed by the designated APPS PMO to ensure that software does not conflict with the existing baseline

f) Support audit and program/release checkpoint review

g) Baseline the test system with each maintenance release and document in the Change Management Record

h) Provide support during normal business hours Afghanistan Time Zone (ATZ), seven days a week; the same level of technical expertise and investigation capabilities should be provided to every customer.

Systems Security Cyber Security The Contractor shall provide a Cyber Security Services Program for the APPS application boundary. Program services shall include plans, policies and procedures adhering to ANDSF, MoD) and MoI mandated security standards and control requirements. The Contractor shall ensure that the application enclave complies with Ministry application accreditation standards for Authority to Operate (ATO) using the International Risk Framework (IRF) process model. Security control overlays will be added to baseline security controls to provide additional protections for Personal Identifiable Information (PII) and Financial Data (FD).

Security Management Plan The Contractor shall develop and submit an Organizational Information Security Strategy Policy, Security and Risk Assessment Plan (SAP) and System Security Plan (SSP) that defines the security policies, planning and procedures. The Security Assessment Plan and System Security Plan shallll include all 114 ISO/IEC 27001 security controls.

The Contractor shall provide the following in the Security Management Plan IAW the CDRL at Appendix A of this PWS:

a) Organizational Information Security Strategy Policy

b) Management Review of Information Security Policies

c) Security and Risk Assessment Plan

d) System Security Plan

e) Complete set of policies and procedures

f) Network Architecture Diagram

g) Security Architecture Diagram Data Encryption and Protection The Contractor shall develop written protection policies and requirements for handling and safeguarding PII, FD and other sensitive information. At a minimum, encryption should employ TLS 2.0 and AES 192 as encryption standards.

The Contractor shall address the following data encryption policies and requirements in the Security Management Plan IAW the CDRL at Appendix A of this PWS:

a) Data in Transit (DIT)

b) Data in Motion (DIM)

c) Data at Rest (DAR)

d) Removable Media Incident Response Program and Plan The Contractor shall develop an Incident Response Program and Plan that includes an Incident Response Team (IRT). The IRT will be comprised of at least one member from the Contractor, one member from the Ministry and one member from the APPS PMO. The Contractor shall notify the COR and IRT within four hours of any network activity or event that could be defined as a possible incident. An Incident Response After Action Report shall be created identifying the incident and mitigation. The contractor shall provide the Incident Response After Action Report IAW the CDRL in Appendix A of this PWS.

Confidential and Privacy Data Protection The Contractor shall protect all PII and confidential financial data according to MoD, MoI standards, policies and guidelines. The USG maintains system ownership and data custodianship until such time as the system has been legally transferred to the respective Ministries for full ownership. The Contractor shall operate and maintain the system with due diligence with regards to data protection and access controls. The Contractor shall report all unauthorized information disclosures to the COR and IRT within 24 hours.

Access Control Policies/Procedures The Contractor shall maintain the current access control policies and procedures for system and data access consistent with MoI and MoD guidelines and controls. The Contractor shall use the “Role Based Access Control” (RBAC) model for all accounts issued to users and IT personnel without exception. Segregation of duties must be maintained and governed by Contractor, MoD and MoI policies and controls. All Contractor users and Information Technology (IT) personnel shall complete Cyber Awareness, PII/Confidential Data Handling and Use of Removable Storage training prior to beginning work on this effort. The Contractor shall maintain and make available, upon request, the following items to the USG:

a) User System Access Authorization Request Policy and Procedures

b) Administrator/Privileged System Access Authorization Request Policy and Procedures

c) User Access Cyber Awareness Training Policy and Procedures

d) Acceptable Use Policy

e) Human Resources (HR) Procedural Violation Policy

f) Removable Media/Storage Policy and Procedures Data Access Controls The Contractor shall ensure that the systems supported by this PWS are capable of limiting access to information based on the users need to know. The Contractor shall ensure that the system allows authorized users to easily change what information users can view or update. The Contractor shall implement software system security services to support Afghan federated data access and update processes for data oriented services and interfacing services. The Contractor shall provide software life cycle management for all security service software they support.

Network Boundary Protection Program The Contractor shall implement technical controls, policies and procedures to protect primary and contingency systems and data against intrusions, exfiltration’s and unauthorized data traffic. The Contractor shall deploy Network Intrusion Protection Systems (NIPS) and Network Intrusion Detection Systems (NIDS). The Contractor shall deploy firewall systems and Access Control Lists (ACLs) for APPS boundary data and traffic control. The Contractor shall employ “Deny All, Open by Exception” policy for application boundary Ports, Protocols and Services (PPS).

Continuous Monitoring Program The Contractor shall maintain a continuous monitoring program that will define the policy and procedures for events and/or vulnerabilities that will effect or compromise system/data. The Contractor shall report these events to the IRT within four hours of detection. The report to the IRT shall be included in Incident Response After-Action Report IAW the CDRL in Appendix A of this PWS. The Incident Response After-Action Response Report shall contain the events and vulnerabilities that affect or compromise system/data integrity, availability or confidentiality.

Contingency Operations and Data Replications The Contractor shall maintain existing system contingency/failover plans, policies and procedures.

Furnish The contractor shall provide the software licensing, help desk support, and necessary hardware components to maintain existing servers and APPS capability.

Procurement The contractor shall procure all necessary software licensing, help desk support, and necessary hardware components to maintain existing servers and APPS capability. The contractor is responsible for ensuring that equipment and material is ordered in a timely fashion to meet the schedule and performance requirements of the project. The Contractor shall procure the materials identified in the contractor developed and USG approved Procurement Bill of Materials (BOM), which will be prepared IAW the CDRL in Appendix A of this PWS.

Contractor shall ensure all hardware and software contain the required basic and extended warranties and licenses required to meet the requirements. Extended warranties and licenses will not begin until after acceptance and approval by the USG and Host Nation Point of Contact (POC) of the multi-party Inventory.

Contractor shall ensure all equipment is compatible with country electrical outlets. All physical boxes should comply with country electrical standards and use appropriate power plugs and sockets, as applicable. All electrical connections and converters, where applicable, must be associated with Original Equipment Manufacturer (OEM) equipment. After-market converters and/or accessories may not be utilized.

The contractor shall conduct a multi-party inventory, equipment accountability, and hand over with the appropriate Host Nation and USG POCs. The contractor shall coordinate with the USG to schedule Host Nation availability 30 calendar days prior to inventory. The contractor shall inspect all items for completeness and damage at the Host Nation facility in-country with USG and Host Nation representative presence for validating receipt of equipment. A Material Management Plan shall be provided IAW the CDRL in Appendix A of this PWS.

All equipment must be registered to the Host Nation as the primary owner for warranty purposes. Specific registration information will be provided to the contractor by the USG.

Bill of Materials (BOM) The Contractor shall develop, review, update, and deliver a BOM that supports and tracks required purchasing for the APPS sustainment IAW the CDRL in Appendix A of this PWS. Required purchasing includes, but is not limited to, software licensing, help desk support, and necessary hardware components to maintain existing servers and APPS capability.

Material Fielding and Asset Management Material management and asset functions associated with Contractor Furnished Equipment (CFE) purchased by the contractor on behalf of the USG and subsequently issued to the Host Nation shall be maintained and tracked IAW Assistant Secretary of the Army for Acquisition, Logistics, and Technology (ASA ALT) guidance and the Defense Federal Acquisition Regulation Supplement (DFARS) applicable clauses.

The contractor shall develop a Material Management Plan and supporting materiel fielding documents that addresses logistics elements applicable to the capability being fielded, which shall be included in the Material Management Plan (PMP) IAW the CDRL in Appendix A of this PWS.

The contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) property in its possession. This requirement applies to all property under the contractor's accountability, stewardship, possession or control, including its vendors or subcontractors.

The contractor shall use appropriate database/forms to maintain accountability over equipment throughout the lifespan of the project. The contractor shall provide the required shipment tracking data, equipment damage/lost/stolen report, BOMs, on-site physical inventory lists, and excess material reports.

The contractor shall include all fielding tasks within the project Integrated Master Schedule (IMS). The tasks will identify in detail the activity installation capability being fielded, period of fielding, by function i.e. equipment order date; required delivery date; hardware install date; hardware/software configuration period; inspection; verification and validation; new equipment training; acceptance and handoff.

The contractor shall:

a) Provide shipping tracking number data, commercial invoices and other documentation containing tracking numbers for all equipment components associated with this fielding no later than (NLT) one business day after each shipment of equipment/material departs for its fielding destination IAW the Procurement BOM in Appendix A of this PWS.

b) Inspect all material for physical damage at each fielding site and report such damage to the Contracting Officer (KO), COR, and USG Project Lead along with a detailed report identifying a cumulative list of damaged equipment NLT than 24 hours after initial equipment assessment, and at any time before, during and after installation.

c) Report any material that is lost or stolen in an Incident Response Report within 24 hours of the incident IAW the CDRL in Appendix A of this PWS. Include in the report the criticality of the lost/stolen material, the costs of the item(s) and its impact to the IMS.

d) Investigate and report to the USG all incidents of property loss as soon as the facts become known in an Incident Response Report IAW the CDRL in Appendix A of this PWS.

e) The contractor shall provide a Material Status Report, to the KO and COR IAW the CDRL in Appendix A of this PWS.

f) The contractor shall secure the signature acceptance of the inventory from the USG and Host Nation POCs. The acceptance document shall be the Invoicing Receipt Acceptance and Property Transfer (iRAPT) (formerly Wide Area Workflow (WAWF) Material Inspection and Receiving Report (MIRR).

g) The contractor shall provide, in the Material Stats Report, a list of excess materials/equipment not used in support of fielding the capability IAW the CDRL in Appendix A of this PWS. The contractor shall turn-over all excess equipment/materials to the Host Nation for reutilization.

h) The contractor shall provide all required material fielding documentation to the Host Nation, to include but not limited to, transfer documents, hardware warranties/software licenses before the Transfer of Authorization.

The Material Management Plan shall address how the contractor will perform the requirements above.

Warranty The contractor shall provide a life-cycle support program that will ensure all installed components of the entire system will be covered under warranty, maintainable and supportable to meet reliability, availability and operational goals. The warranties and licenses should include technical support, maintenance, and product vulnerability and software updates.

Transfer Of Operational Use The contractor shall assist with the transition of the APPS to GIRoA. The Contractor shall develop an APPS Transition Plan IAW the CDRL in Appendix A of this PWS. The contractor shall describe the transition in detail, providing a schedule, team composition, risks, required training, giver and receiver responsibilities, success criteria, and reports. The Contractor shall consolidate key system technical manuals and prepare a configuration management baseline, system sustainment plan, and user manuals (as applicable) to facilitate timely and efficient transfer of the system for the intended operational use.

The contractor shall work with ministry representatives to develop the transition plan required to transition all maintenance, upgrades, and sustainment of the entire APPS system to the individual ministries with the intent to eliminate all contractor related services.

The contractor shall identify the minimum experience and training requirements for the database administrators and system administrators necessary to begin their training.

GENERAL REQUIREMENTS

The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision and other items necessary to perform the requirements as defined in this PWS.

Host Nation (Afghanistan) Requirements The contractor is required to fully understand and comply with any and all statutory and regulatory requirements of the Host Nation to include any applicable local requirements. This includes, but is not limited to, any statutes and regulations applicable to the work to be performed under the contract. The USG will not assume any responsibility to provide copies of any Host Nation statute or regulation. The USG will not assume any responsibility to notify contractors of applicable laws or regulations associated with the conduct of business in the Host Nation. The contractor is responsible to obtain any and all required business, engineering or construction licenses, permits, waivers, and translations required for the work to be performed in the Host Nation.

The USG will not be liable for any fines or fees assessed against the contractor during the performance of the contract due to a violation of existing statutory and regulatory requirements of the Host Nation to include any applicable local requirements.

The contractor must certify that it is, in fact, licensed to conduct business for the work to be performed within the Host Nation. All required licenses and permits must be in full force and effect prior to the beginning of work on site. The USG reserves the right to request certified copies of appropriate licenses and/or permits.

The Contractor shall ensure all personnel, including subcontractors, comply with, fully understand, and obey any and all statutory and regulatory requirements of the USG federal, DoD and host nation(s) laws, to include any local requirements and Combatant Command orders and directives applicable to personnel deployed outside of the United States (OCONUS) in the areas of operation.

Site Preparation The contractor shall perform site preparation activities required for the effort, employing Best Commercial Practices IAW applicable documents.

PROJECT MANAGEMENT REQUIREMENTS

The Contractor shall provide review and analysis of system requirements, and planning of all aspects of the project management, engineering, fielding and operating IT systems, and resources. Project management shall include in-country project reviews, decision meetings, briefings, preparation of project reports and documentation.

Processes and Performance Contractor program management practices shall incorporate risk mitigation measures, accepted business planning techniques, and control system elements that ensure the following programmatic requirements are met:

a) Assignment of authority and responsibility at the work performance level.

b) Integration of the cost, schedule, and technical aspects of the work into a detailed baseline plan.

c) Objective measurement of progress at the work performance level.

d) Accumulation and assignment of actual costs.

e) Analysis of variances from plans.

f) Summarization and reporting of performance data to higher levels of management for action.

g) Disciplined baseline maintenance and incorporation of baseline revisions in a timely manner.

Program Management Plan The Contractor shall provide a Program Management Plan that confirms the work under this contract is managed effectively and efficiently in terms of cost, schedule, and performance. The Program Management Plan shall include an Organizational Conflicts of Interest (OCI) Mitigation Plan, if required by the KO. The contractor shall provide the Program Management Plan (PMP) IAW the CDRL at Appendix A of this PWS. The PMP shall be comprehensive and sufficiently detailed to support successful execution, monitoring, controlling, and close-out for this effort.

The contractor shall update the PMP to reflect any approved changes, such as Key personnel, for the duration of the contract’s PoP. The contractor shall provide the PMP to the USG IAW the CDRL in Appendix A of this PWS.

After initial concurrence, the contractor shall provide the proposed changes to the PMP to the USG for concurrence prior to implementation of any changes.

The Program Management Plan shall include and clearly describe the following:

a) Management Structure

1) Corporate Organization

2) Resources

3) Organization Conflict of Interest Mitigation Plan

b) Processes

1) Requirements Management

2) Configuration Management

3) Quality Assurance

4) Sub-Contractor Management

5) Supply Chain Risk

6) Reliability

c) Program Protection

d) Work Breakdown Structure (WBS) Meetings The contractor will be required to attend meetings for the project. The development of the schedule and the duration of the meetings will be based on the effort and any ongoing issues. Other meetings may be scheduled and the contractor will be required to attend these meetings if requested to do so. These meetings may be face to face, telephonic, or Video Teleconference (VTC). The Contractor shall notify the APPS PMO, within 24 hours of a scheduled meeting, if the Contractor representatives are not able to attend the coordinated meeting. If briefing materials are required from the contractor for these meetings, the USG shall provide notification of this requirement. Briefing materials and Meeting Minutes shall be developed and submitted by the contractor IAW the CDRLs in Appendix A of this PWS.

Conference Meetings The contractor shall attend any post award conference meetings convened by the Contracting Activity or Contract Administration Office. The KO, COR, and other USG personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings, the KO or COR will apprise the contractor of how the USG views the contractor's performance and the contractor will apprise the USG 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 USG. Briefing materials and Meeting Minutes shall be developed and submitted by the contractor IAW the CDRLs in Appendix A of this PWS.

Monthly Project Status Meetings The contractor shall participate in Monthly Project Status Meetings telephonically or on-site. The contractor shall provide and update meeting documentation, including updates to the IMS, and on-going Action Item Register. This also may include briefing slides and any other documentation utilized. The contractor shall submit Meeting Minutes and Briefing Materials IAW the CDRL in Appendix A of this PWS.

Reporting Requirements Monthly Status Report The contractor shall provide a Monthly Status Report (MSR) to the USG IAW the CDRL in Appendix A of this PWS. The Contractor shall provide Status and Management reports that include the following programmatic data elements:

a) Funds and Man-Hours Expenditure

b) Priorities and Estimate of Task completion

c) Contract Funds Status

d) Percent expended on the task with applicable dollar rates annotated

e) Percent remaining with applicable dollar rates annotated

f) Cost Performance Index (CPI) at each WBS level

g) Schedule Performance Index (SPI) at each WBS level

h) Technical Updates (may include studies, white papers, and technical presentations (as required)

i) Root cause analyses (as requested by the USG)

j) Key system performance metrics (operational availability, system health and performance metrics, server management, CPU utilization, bandwidth, etc.) (as requested by the USG)

k) Prioritized list of system deficiencies and enhancements (as requested by the USG)

l) Delivery schedules for deficiency and enhancements (as requested by the USG)

m) Risk identification, risk assessment, and risk mitigation reporting (as requested by the USG)

n) Briefing charts, meeting minutes, spreadsheets, materials (as requested by the USG)

o) Trip reports Trip Reports The Contractor shall provide trip reports as directed by the USG.