Attachment 0001- Performance Work Statement Revised 15OCT2020.pdf

UNCLASSIFIED/ACQUISITION SENSITIVE

PERFORMANCE WORK STATEMENT (PWS)

FOR

AFGHAN PERSONNEL AND PAY SYSTEM

SUSTAINMENT MANAGEMENT

15 October 2020

AFGHAN PERSONNEL AND PAY SYSTEM

SUSTAINMENT MANAGEMENT PWS

1.0 INTRODUCTION

Combined Security Transition Command – Afghanistan (CSTC-A) trains, advises, and supports 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.

1.1 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 U.S. Government; (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 shall attend meetings in and around Kabul, Afghanistan.

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, except for those items specified as Government Furnished Property (GFP).

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 regulations. 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 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 shall certify that it is licensed to conduct business for the work to be performed within the Host Nation. All required licenses and permits shall 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, fully understand, comply with, and follow all statutory and regulatory requirements of the USG, Department of Defense (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.

As of 1 September 2015: (1) all companies operating in Afghanistan are required to have a business license issued by the Afghanistan Investment Support Agency; and, (2) all U.S. and NATO Contractor employees should have a valid national passport and Afghan visa at the time of entry into Afghanistan. The Contractor shall comply with all the business requisites articulated at the following link below.

https://www.acq.osd.mil/dpap/pacc/cc/Contracting%20in%20Afghanistan%20- %20BSA%20and%20SOFA%20Overview.pdf

The prime Contractor shall be responsible for any subcontract management actions or security compliance necessary to fulfill the requirements of this PWS and any subsequent contract modification(s). The prime Contractor shall notify the Contracting Officer (KO) and Contracting Officer Representative (COR) of any subcontractors being added to support this effort before they are subcontracted to perform any work under this contract or any subsequent modification(s).

1.2 BACKGROUND

APPS is an enterprise resource planning and payroll system for 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 the 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 maintain transparency and audit capability, while also strengthening 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.

1.3 OBJECTIVES

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

1.4 SCOPE

The Contractor shall provide technical support and subject matter expertise to continue to modernize the APPS suite of programs, improve performance, enhance 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 improve the APPS baseline, operational control of source code, and maintenance of the system architecture. The Contractor shall continue to attend, coordinate, and/or lead Technical Exchange Meetings focusing on those areas where technical exchange is necessary to ensure program interests are addressed. During the Period of Performance (PoP) of this effort, the Contractor shall support the transition of the APPS to the GIRoA.

1.5 PERIOD OF PERFORMANCE

The PoP for this effort will consist of a twelve (12) month Base Period, with four (4) subsequent twelve (12) month Option Periods, and one (1) six (6) month extension option IAW FAR 52.217-8. The total performance period will not exceed sixty-six (66) months from date of award inclusive of all options and extensions.

1.6 PLACE OF PERFORMANCE

The Contractor shall maintain a support facility in Kabul, Afghanistan. The work shall be performed at the Contractor’s Kabul support facility, within MoD/MoI designated locations and associated North Atlantic Treaty Organization (NATO) Resolute Support locations throughout the area of responsibility (AOR). Contractor employees shall abide by ANDSF regulations when performing tasks at MoD and MoI sites.

1.7 HOURS OF OPERATION

The Contractor shall provide services during normal ANDSF working hours Saturday through Thursday from 0800–1700.

1.8 RECOGNIZED HOLIDAYS

Recognized holidays for this effort are as follows:

New Solar Year (Naw Roz) and Farmer’s Day 2 days Celebration of Islamic Revolution in Afghanistan 1 day 1st Day of Ramadan (Religious Day)* 1 day Eid-ul-Feter (Religious Day)* 3 days Arafat (Religious Day) 1 day Eid-ul-Adha (Religious Day)* 3 days The Independence Day of Afghanistan 1 day Martyrs and Ahmad Shah Masoud Day 1 day Tenth of Moharam, Ashora (Religious Day) 1 day Prophet Mohamad (PBUH) birthday / Mawlod –e- Sharif 1 day Former Socialist Russian troops exit day from Afghanistan 1 day Ramadan - Working hours during Ramadan shall be from 0800-1200

1.9 APPLICABLE DOCUMENTS

References and Standards of this PWS are provided for information and guidance in the execution of this effort. The Contractor shall ensure that it obtains and complies with the latest version of the Government, Commercial Documents, and applicable attachments listed in the PWS at the time of proposal submission.

All work, tasks, deliverables and requirements in this effort shall be governed by the COR 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 shall ensure it obtains and complies with the most current version of the USG and commercial documents listed in this section.

a) ISO/IEC 12207:2008(E) (IEEE Std 12207-2008), Systems and Software Engineering- Software Life Cycle Processes.

b) IEEE/EIA 12207.1-1997 IEEE, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data.

c) GEIA-STD-0007, Logistics Product Data Handbook

d) MIL-HDBK-61B, Configuration Management Guidance

e) Timing Service API Primer; version 1.0, 04 SEP 2014

f) Software Communications Architecture Specification User's Guide; version 4.1, 23 FEB 2016

g) MIL-STD-881C, DOD Standard practice for Work Breakdown Structures, OCT

h) DODI-8500.2, Information Assurance Implementation

2.0 CONTRACTOR PERSONNEL

2.1 KEY PERSONNEL

The Contractor shall notify the COR and KO prior to making any changes in Key Personnel. No changes in Key Personnel will be made unless the Contractor can demonstrate that the qualifications of prospective replacement personnel are equal to or greater than the required qualifications of the Key Personnel written in the PWS. All proposed substitutes shall have qualifications equal to or greater than the qualifications required in the PWS. The KO shall be notified in writing of any proposed substitution at least fifteen (15) calendar days in advance of the proposed substitution. Such notification shall include:

a. an explanation of the circumstances necessitating the substitution;

b. any other information requested by the Contracting Officer to enable him/her to judge whether or not the Contractor is maintaining the same high quality of personnel that provided the partial basis for award.

The COR will evaluate Key Personnel substitutions. All disapprovals will require resubmission of another substitution within 15 calendar days by the Contractor. The Contractor shall provide properly qualified personnel to complete all requirements and contract deliverables. The Contractor’s detailed staffing approach shall be described and included in the Program Management Plan (PMP). The Contractor shall fill all positions with personnel qualified to perform the duties assigned for the particular role and responsibility.

2.1.1 Program Manager

The Contractor shall provide a Program Manager (PM) responsible for the performance and fulfillment of the work for the APPS capability. The name of this person and an alternate who shall represent the Contractor when the PM is absent shall be designated in writing to the USG Contracting Officer. The PM shall oversee the team using best business practices, working as a member of an integrated team, and shall be responsible for all contractual responsibilities and contract deliverables. The PM shall collaborate with USG personnel and shall ensure an efficient, effective and economical level of support is provided to the APPS PMO. The PM shall have a minimum of 10 years’ experience in Project/Program Management, as well as a minimum of a bachelor’s degree in an area related to management, business or similar focus.

2.1.2 Technical Lead

The Technical Lead shall serve as a direct liaison to function process owners in order to translate and prioritize requirements for assigned areas of project and maintenance work. The Technical Lead is responsible for translating high-level business requirements into detailed functional specifications and managing requests for changes to the design specifications, and support the business in determining which business requirements can and should be automated and how they are then integrated with other business and technical processes. The Technical Lead shall have a minimum of 10 years’ experience in the areas described, as well as in the field of Information Technology (IT), as well as a minimum of a bachelor’s degree in either information technology, computer science, software engineering or a degree with similar focus.

2.1.3 Functional Lead

The Functional Lead is responsible for program activities related to analysis, design (including fit/gap analysis), documentation, and sustainment of the APPS. The Functional Lead shall have a minimum of 5 years of IT experience, specifically in system analysis and design, as well as a minimum of a bachelor’s degree in either information technology, computer science, software engineering or a degree with similar focus in Management Information Systems or comparable field.

2.1.4 Life-Cycle Logistics Manager

The Life-Cycle Logistics Manager will be responsible for directing and coordinating program activities that support the deployment, sustainment, and customer support of the APPS. The Life-Cycle Logistics Manager shall anticipate logistics problems related to operational effectiveness, reliability, availability, and maintainability. The Life-Cycle Logistics Manager shall have a minimum of 5 years of experience with directing cross-functional teams of technical experts to analyze systems and processes, implementation and sustainment of software updates, and IT improvements of Information Systems. Additionally, the Life-Cycle Logistics Manager shall have a minimum of a bachelor’s degree in systems logistics, business, management, or related technical field.

2.1.5 Contracts Manager

The contract manager shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The contract manager shall have a minimum of 10 years’ experience in contract management to include monitoring, negotiating, execution, extension, modifications, renewal and closeout of all contract aspects. Experience to include knowledge of contractual language, contract lifecycle, legal and financial implications and understanding of the business or industry as well as working knowledge of the FAR. Additionally, the Contracts Manager shall have a minimum of a bachelor’s degree in business, contract management, or related field.

2.2 OTHER COUNTRY NATIONAL (OCN) / LOCAL NATIONAL (LN) PERSONNEL

REQUIREMENTS

2.2.1 Screening Requirements

All personnel must meet initial screening requirements. Employees must obtain an escort base access badge. All personnel shall maintain continuous eligibility to possess the required access badge throughout the life of the contract.

2.2.2 Biometrics

All personnel will be required to give biometrics data to include, but not limited to, fingerprints, DNA and registration in the BATS/HIDES system.

2.2.3 Security Screening

The Contractor shall provide information to U.S. Government personnel for security screening of their workers. While documentation requirements will vary with installations around Afghanistan, and could change at any time based on security requirements, the following are the minimum amounts of documentation that are required:

a) Tazkara (National ID for Afghan citizens)

b) Passport (for Third Country Nationals)

c) Name (to include any nicknames)

d) Father's Name

e) Maiden Name

f) Address (Residence)

g) Phone Number

h) Driver License # (If applicable)

i) Estimated Date of Birth

2.2.4 Criminal Investigation Screening

All employees working under this contract will be required to pass a Criminal Investigation Screening for security purposes.

2.2.5 Employee Monitoring

The Contractor shall screen and monitor each employee as well as any potential employee to identify those who may pose a potential threat to the health, safety, security, general well-being, or operational mission of the installation and its population.

The Contractor shall notify the COR of any reason or condition that identifies an employee or potential employee as a potential threat to the health, safety, security, general wellbeing, or operational mission of the installation and its population. The Contractor shall not employ individuals identified by the Contractor, COR, Contracting Office or US Government security personnel as a potential threat to the health, safety, security, general well-being, or operational mission of the installation and its population in the performance of this contract.

2.2.6 Medical Screening

All contractor employees will be medically screened for pulmonary disease/tuberculosis (PD/TB) and other illness as necessary determined by Public Health Officials. The contractor shall bear the cost of any required medical screenings. Any contractor employee that tests positive for TB or is otherwise ill, will be further evaluated by the FOB Public Health Officer (PHO). The PHO will make a recommendation to allow or deny access to the FOB. Personnel denied access to the FOB due to medical reasons must be medically cleared by FOBs PHO before access can be granted. OCN/LN employees involved in food service, water, and ice production must be screened annually for signs and symptoms of infectious diseases. Contractors must ensure employees receive typhoid and hepatitis a vaccinations, and this information must be documented in the employees’ medical record / screening documentation.

2.2.7 Escort Policy

Contractor personnel shall comply with Base contractor escort policy. Violations of this policy may result in termination of the contract. Contractor personnel found outside of the prescribed work area will be detained, and then removed from the site. Contractor personnel will only take direction from the COR or KO. Contractor personnel will never take direction regarding any aspect of the project from escorts or other unit personnel

2.2.8 Force Protection

All contractor employees are subject to search at the gate, and at any other time deemed necessary by the COR, or security personnel. All contractor employees shall be comply with applicable Force Protection requirements. Employees shall undergo a security screening, and be given identification badges which must be worn and be visible at all times while on the installation. Each contractor employee shall abide by the authorizations and restrictions as identified on the badge. All directives shall be strictly followed. Failure to follow the directives, or the permissions granted by the badging office, may result in an immediate escort off the installation. Contractor employees who are escorted off the installation for failure to follow directives and permissions will not be permitted access until the individual is cleared by the badging office.

2.2.9 Replacement Employees

The contractor shall insure that any replacement employees are coordinated through the KO and COR. The contractor shall certify that all proper medical screening has been obtained, and will produce records/documentation upon request. The contractor is responsible for coordinating all necessary paperwork through access control to insure their employees are properly badged and cleared. A monthly employee roster will be provided to the COR, listing all employee names, place of origin, and nationality, badge number and Taskera number. If at any time five (5) or more employees are replaced at one time the Contractor shall immediately provide the COR with an updated employee roster.

2.3 CONDUCT OF OCN / LN PERSONNEL

The Contractor shall comply with and hold accountable all of its employees and sub- Contractors to a comprehensive ethical code of conduct as described in FAR clause

52.203-13, Contractor Code of Business Ethics and Conduct.

2.3.1 Termination of Employment

The government may require the contractor to terminate the employment of any contractor employee under this contract for reasons of misconduct, security breaches, or found to be or suspected to be under the influence of alcohol, drugs, or other incapacitating agents. The government will immediately confiscate all badges and escort the employee off the installation.

2.3.2 Weapons

Weapons of any type, to include knives, are not to be in any contractor employee’s possession.

2.3.3 Object Removal

Removing objects from refuse/trash for personal use is not authorized.

2.3.4 Purchase of Items

At no time, without authorization from the COR, will a laborer purchase any items from the local economy for any Soldier.

2.3.5 Forbidden Items

The following items are forbidden:

a) Alcohol (beer, wine, liquor, etc.)

b) Illegal drugs (marijuana, opium, hash, heroin, cocaine, etc.)

c) Prescription drugs (not dispensed from a licensed pharmacy, DoD facility, or not prescribed to the individual in possession)

d) Drug paraphernalia (pipes, bongs, cigarette paper, etc.)

e) Local tobacco products

f) Pornography

2.3.6 Personal Appearance and Hygiene

The contractor shall ensure employees present a professional appearance commensurate with standards delineated for government civilian personnel acting in similar capacities. Clothing shall be as clean and neat (i.e. no debris, mud, stains, rips, tears, or holes) as practicable considering work conditions. The contractor shall ensure employees maintain good hygiene for health and safety practices.

2.3.7 BAT/HIIDE Enrollment

All FOBs will establish procedure to ensure that all local nationals go through the process of Biometric Automated Toolset (BAT) which is used to collect fingerprints, iris scan, facial photos and biographical information of persons of interest into a searchable data base. This will include Tactical Operations; force Protection, Detainee Operations, Population control, Base Access, IED Forensics Operations, Special Operations, and

Local hire Screening/Intelligence.

2.3.8 Interaction with Others

The Contractor shall cooperate in good faith with other Contractors, USG organizations and Host Nation personnel working on the project at all times.

This cooperation shall include, but is not limited to:

a) Participating in technical exchange meetings.

b) Coordinating logistics and logistics related activities.

c) Troubleshooting and resolving designs, engineering documents or installation issues.

All Contractor deliverables may be provided to other Contractors at the Government’s discretion.

2.3.9 Identification of Contractor Personnel

The Contractor shall require its employees to identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel. The contractor shall also be required to display distinguishing contractor badges or other visible contractor identification for meetings with USG and Host Nation personnel.

The Contractor shall require its personnel to identify themselves appropriately as Contractor employees in all telephone conversations, and in formal and informal written correspondence.

3.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL LICENSES,

AND WARRANTIES

3.1 GOVERNMENT FURNISHED PROPERTY (GFP)

GFP shall be furnished by the U.S. Government to the Contractor in support of this contract. GFP consists of equipment, licenses, user manuals, training material, standard operating procedures (SOP) and source code. GFP is listed in Attachment A. The Contractor shall inventory all GFP and provide quarterly an updated Government Property Inventory Report IAW CDRL A019.

3.1.1 Original Equipment Manufacturers/Warranty

The Contractor shall provide, maintain and monitor a current listing of all GFP which shall include and identify standard vendor warranties, and support agreements for hardware, software and licensing.

3.1.2 Facilities

GIROA will provide the facilities at MoI and MoD locations to include desk space and telephones. The Contractor shall have an office located in Kabul, Afghanistan that will be utilized in addition to the MoI and MoD locations.

3.2 REPLACEMENT, UPDATES AND UPGRADES

In support of this contract, if the Contractor requires replacement of new hardware, equipment, software, licensing or ancillary equipment, to include standard commercial warranties, the Contractor shall submit a deliverable listing all of such items, not less than 12 weeks prior of the required need to the COR for evaluation and approval. The Government will evaluate the need to procure the items required based on the information provided in the deliverable listing. With respect to system warranty, an upgrade is defined as any software version other than what is currently authorized on the system.

3.2.1 Warranty

The Contractor shall provide a life-cycle support program that ensures all newly installed components of the system shall be covered under a standard commercial warranty. Components shall be maintainable and supportable to meet reliability, availability and operational goals.

3.2.2 Material Receipt

The Contractor shall provide a Material Inspection and Receiving Report (DD Form 250) each time a piece of equipment/license/software is procured IAW CDRL A018. All procured equipment/licensing/software on this contract will be added/updated to the GFP listing IAW CDRL A019. The Contractor shall be on-site to receive, install, inventory, move, and/or store equipment.

4.0 TECHNICAL

4.1 SUSTAINMENT

The Contractor shall continue the current baseline of the system software and hardware and provide software changes and problem fixes to these baselines as required. The Contractor shall perform sustainment requirements that ensure the system is maintained and performing to optimum levels. 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 Technical Data Package (TDP) consists of Source Code, Conceptual design drawings/models, Developmental design drawings/models and associated lists, Product engineering design data, Engineering design data, Specifications, Software documentation, Quality Assurance Provisions (QAPs), and will be used to document the System Baseline. The Contractor shall update and provide the TDP revisions IAW CDRL A004.

4.1.1 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 and updates to hardware, software, licenses and databases to maintain the system requirements for throughput, response times, and quality of service and system security posture.

4.1.2 Deficiencies

The Contractor shall document, assess, prioritize, and report system deficiencies, and develop the required design changes to resolve all 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 (operational availability, system health and performance metrics, server management, CPU utilization, bandwidth, etc.).

4.1.3 Modernization

After award, an in-depth review of the technical data, along with further knowledge and experience of the system, the contractor shall update the AMP and submit proposals focusing on areas within the APPS system where changes can be made to the existing infrastructure, baseline, software, hardware and/or architecture in order to improve the systems performance, efficiency and a more user friendly approach. The AMP shall be included as part of the Systems Engineering Management Plan (SEMP) IAW CDRL A012 and be submitted to the COR 30 days after contract award for review.

The AMP may include, but is not limited to, such activities as updating, replacing and/or streamlining outdated or inefficient system hardware, software, processes, applications, updating modules, adding new feature capabilities, or special design considerations;

improving modules, adding user interfaces, data storage and table structure and resolving any associated limitations that affect the performance of the system, hardware and software architecture.

4.1.4 Enhancement

The Contactor shall update and enhance system capabilities to the baseline through continuous system changes in support of the Government of the Islamic Republic of Afghanistan (GIRoA) user requirements, changes in Inherent Law and other required changes. Requests for changes shall be submitted to contractor via a System Change Request (SCR) for review and determination of validity. When the Contractor has sufficient insight into the change, the Contractor shall submit a Software Requirements Specification (SRS) for review and approval to the COR/ministry defining the requirement and the proposed way forward. If the workflow is changed causing current operability of a feature/module to be significantly changed/modified it will be considered an enhancement. To add a workflow that does not currently exist in the system shall be considered a modification. SRS is to also include estimated completion timeline, testing and deployment plan, identify updates to the APPS training manuals, user guides, SOPs, incentive pay primer SOP, pay policy primer and TDP (if required). Updates required to manuals, guides and SOPS are to be completed prior to release if possible or, no later than 5 working days upon release of enhancement. The Contractor shall capture and maintain all pay policy changes and shall be updated after every Pay and Compensation Board (PCB) or when directed by the COR. Upon review and the clarification of the SRS, the Contractor shall submit technical change for approval to the COR using the APPS Execution Request and Authorization Form (AEARF), Attachment C.

Enhancement is defined as any system change, improvement or upgrade that increases system, software or hardware capabilities to meet GIRoA requirement changes or improvements. Enhancement shall include but is not limited to: software and architecture changes with existing baseline data, source code changes, modifying of software products, software/hardware/architecture product performance scalability, replacements for obsolete components, safety, compatibility, security, product improvements and technology improvements that currently exist in workflows, modules and reports, process changes that affect the process while not affecting other workflows and processes.

When implementing enhancements and updates, the Contractor shall follow configuration management processes IAW CRDL A002. Enhancements are not considered a modification and shall not be separately proposed, billed, and/or charged against the contract. If during the AEARF review the requirement is identified to be out of scope and a modification is required, an Engineering Change Proposal (ECP) shall be submitted IAW CDRL A015. All AEARFs will be tracked by the Contractor and submitted with the CPSR, IAW CDRL A010.

4.1.5 Database Management

The Contractor shall perform database management services to effectively meet the APPS PMO Data Server, Application Server, and Database for each site (MoD and MoI) requirements to include help desk tier 2 and tier 3 support. The Contractor shall provide database services to include operations, monitoring, maintenance, and life cycle support to the APPS sites. Services to include the immediate updating upon identified changes of user/training manuals, and standard operating procedures in the APPS system as well as system software operational change notifications. Additional manual/SOP updates not related to requirements changes are to be updated in the manuals/system on a monthly basis and documented in the CPSR CDRL A010.

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.

Tier 1 help desk support has been transitioned to the ministries to be maintained and supported. The Contractor will be responsible for all activities pertaining to technical and data management support associated with Tier 2 and Tier 3 help desk requests submitted through official ciphers, Contractor shall submit change approval to the COR using the APPS Execution Request and Authorization Form (AEARF), Attachment C.

The Contractor shall screen all MoD and MoI requests for data corrections i.e. back pay and other transactions for accuracy and compliance to current pay policy. The Contractor shall reject and inform the COR of requests that are fraudulent or not compliant. The Contractor shall perform back end system data entry, to include at a minimum; reviewing/screening of records, identifying errors, ensuring validity/accuracy of request and proper documentation prior to system entry corrections.

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.

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

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

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

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

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

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

4.1.12 Architecture Framework

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

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

4.1.14 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 IAW CDRL A005:

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

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

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

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

The Contractor shall report any network outages as an incident.

4.2 MAINTENANCE

Maintenance is defined as all routine actions required to ensure the optimum operation of the system.

The Contractor shall be responsible for maintenance of the systems operations, hardware, software, system architecture and peripherals associated with the APPS capability. Maintenance activity includes, but is not limited to the following areas pertaining to the system as well as requests from the APPS PMO: day-to-day issues, deficiencies, glitches, errors, anomalies, repairs, system updates, data entry and corrections, database management actions, data reports/analyses, help desk support and general system maintenance.

The Contractor shall develop and deliver, for USG approval, a Contractor’s Maintenance Program Plan (CMPP) IAW CDRL A005 based on the hardware and software components developed and delivered as part of the APPS capability. The CMPP shall, at a minimum, include routine and non-routine maintenance requirements.

4.2.1 Preventive Maintenance

Preventative maintenance and inspections are performed in order to maintain the operational availability of the APPS system. 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

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.

Maintenance performed is to be reported in the monthly Maintenance Service Report (MSR) IAW CDRL A006 APPS PMO Contracting Officer’s Representative (COR).

4.2.2 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 MSR of the issue to the owning organization IAW CDRL A006. The Contractor shall coordinate with the organization to fix/repair the issue within four hours.

4.3 ENGINEERING CHANGE PROPOSAL (ECP)

The Contractor shall utilize the Engineering Change Proposal (ECP) processes by generating and submitting a DD1692 ECP for proposed configuration changes IAW CDRL A015. The Contractor shall submit a firm fixed price (FFP) ECP proposal within 30 calendar days upon official request. All change proposals shall remain valid for a period of no less than 180 calendar days from the date of submission to the Government. ECPs shall be classified as Class I or Class II based on the definitions in MIL-HDBK-61B. All ECPs shall be submitted to the Government COR for review and requests must be submitted initially in enough detail to determine if the change is a Class I or a Class II. ECPs can be either solicited or unsolicited. All areas within the TDP that are affected by the ECP change shall be updated as part of the ECP process to include the updates in APPS of the training/user manuals and SOPs.

ECP’s shall only be incorporated into the contract via a contract modification signed by the KO. During the modification process, the Contractor is not authorized to begin work until a KO signed contract modification has been distributed to the Contractor.

4.3.1 Class I ECP

Following classification determination of Class I within the Contractor’s CM system and MIL-HDBK-61B, the Contractor shall provide the COR an initial request for review of the ECP. This request must include sufficient information to allow the Government to perform initial merit review for the associated effort, and to concur with the classification as Class I. For a solicited ECP, this step is not required. For a solicited ECP, the COR shall submit a request for proposal of the Class I ECP, and shall summarize any conditions related to this proposal.

The Contractor shall prepare a complete proposal that describes the change needed, and either a proposed solution or a process to determine the complete change necessary, including material, labor and all associated costs.

Following discussions or re-submittals, the Government shall conduct a CCB, and shall decide to approve or disapprove the proposal. ECP status shall be included as part of the Contractors Progress and Status Report IAW A010 until all actions associated with the ECP are completed.

All areas within the TDP that are affected by the ECP shall be updated as part of the ECP process.

4.3.2 Class II ECP

Following classification determination of Class II within the Contractor CM system and MIL-HDBK-61B, for all Class II ECPs, the proposed change is presented to the COR for concurrence of classification for concurrence of classification.

All obsolescence, enhancements, shall be submitted as Class II ECPs and shall not be separately priced. The Government shall examine the change(s) and the COR shall issue a contract action or a letter to approve or disapprove each proposed Class II ECP.

Class II ECPs will be at No-Cost. ECP’s shall be incorporated via contract modification signed by the KO. ECP status shall be included as part of the Contractors Progress and Status Report IAW A010 until all actions associated with the ECP are completed.

4.3.3 ECP Software Changes

Software created, modified, and procured under this contract at the expense of the Government shall be delivered with Unlimited Rights and shall include, but is not limited to, the source code including documentation, executable documentation, hardware, manuals and licensing.

4.4 SYSTEMS SOFTWARE

4.4.1 Government Repository

Computer software is defined as source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulas and related material that enables the software to be reproduced, recreated or recompiled. Software created, modified, and procured under this contract at the expense of the Government shall be delivered with Unlimited Rights and shall include but is not limited to the source code including documentation, executable documentation, and hardware. The Contractor shall update, maintain and sustain all source code and pertinent APPS capability artifacts IAW CDRL A001. The Contractor shall maintain an up-to-date document library in support of the APPS capability.

4.4.2 Standard Commercial Software and License

The Government shall receive, at a minimum, standard commercial license rights in all commercial computer software, as identified and proposed in the Contractor’s technical solution, associated with this contract as outlined in DFARS 227.7202. A Software License Requirements List (SLRL) shall be provided as GFP for all end-items delivered.

The Contractor shall maintain and update this list as part of the Government Furnished Property (GFP) in Appendix B.

4.4.3 APPS System Software Updates

The Contractor shall perform at a minimum one (1) annual APPS system software update to encompass commercial software updates that are used with the system.

Testing shall be performed prior to ensure there is no break in system operations.

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

4.4.5 Language and Regional Expertise Requirements

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

4.5 SYSTEMS CONFIGURATION

4.5.1 System Configuration Identification

The Contractor shall provide a Configuration Management Plan (CMP) to maintain Configuration Baselines (Functional, Allocated, and Product) and 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 CMP shall be provided IAW CDRL A002.

4.5.2 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 CDRL A003.

The Contractor shall permit acceptance of commercial product information in the CSA database.

4.5.3 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 use the approved Configuration Management Plan protocols to identify software that comprises the APPS baseline.

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

4.6 SYSTEMS SECURITY

The Contractor shall provide a Contractor’s System Security Plan (CSSP). The plan shall include a description of system boundaries, system environments of operation, how security requirements are implemented or how organizations plan to meet the requirements, and the relationships with or connections to other systems.