AHRIMS_PWS.pdf

PERFORMANCE WORK STATEMENT

AFGHAN HUMAN RESOURCE INFORMATION MANAGEMENT SYSTEM (AHRIMS)

1.0 General:

1.1 Scope of Work: This Performance Work Statement (PWS) defines the software requirements for the maintenance and sustainment of the Version 1.1 of the Afghanistan Human Resources Information Management System (AHRIMS). The 1.1 version of the AHRIMS database focuses on addressing gaps identified in Version 1.0 findings and recommendations, in addition to content improvements proposed by stakeholders. Each gap addresses key initiatives that directly impact and improve personnel management and readiness across the Afghan National Security Force (ANSF). The 1.1 version of the AHRIMS database encompasses additional functions associated with accession to separation from the organization; profile record management; career development and management; execution of human resources policies, procedures, and ANSF member’s information management. These activities include the following: recruitment, strength management, placement and assignment, position fill management and classification, adverse actions, education, training and development, and competency management.

2.0 Objectives:

2.1 Task order #1 and Task Order #2 are inherited into this Task Order.

2.2 AHRIMS is to emulate current ANSF processes for ease of transition.

2.3 Obtain configuration control of current AHRIMS 1.0 and subsequent versions.

2.4 Train/maintain/sustain AHRIMS across MoI & MoD.

2.5 Develop sustainment training plan (Training/Implementation Plan).

2.5.1 Continue to field and train AHRIMS at MoI and MoD sites, training centers, and other locations deemed necessary by ANSF.

2.5.2 Update the AHRIMS servers with Version 1.1 enhancements identified in previous PWS.

3.0 Requirements: The Contractor Will:

3.1 Continue to prepare and submit system status reviews to the customer bi-weekly. Reviews should include at a minimum the overall program status, test data, schedule, and percentage of work completed.

3.2 Meet with all parties involved to discuss program status at least once each month and upon request by the customer.

3.3 Maintain a secure personnel database with requirements identified in this PWS that will be maintained and used to manage MOD/MOI personnel records and personnel information. The contractor will maintain redundant security measures to ensure no unauthorized access can be obtained and security features are included with database.

3.4 Continue to maintain the database with protected secondary and tertiary backup systems for every populated record. The contractor will perform daily backups on the system. The contractor will ensure that the system has up-to-date anti-virus and firewall software at all times by verifying

Network Operations Centers scheduled updates are run at least weekly. The contractor will provide valid software licensing for all software used throughout performance of contract.

3.5 Complete fielding of AHRIMS 1.0 with version 1.1 upgrades at all locations deemed by the

ANSF.

3.6 Provide continuous “train the trainer” type training at all locations deemed by ANSF. Requires loading of AHRIMS on school server for training purposes only.

3.7 Maintain the following data fields, tables, and reports to the AHRIMS version 1.0/1.1:

Data fields and tables will be the same for both MoD and MoI with system controls in-place so that the specific operator is able to view and update only those fields applicable to their particular Ministry and function.

a. Recruitment/Re-contracting: The purpose of these features is to establish and maintain accurate account of all recruitment and retention activities for all ANA and ANP. This will be a separate screen and users will be given access to one or multiple screens. The purpose of this screen will be achieved by capturing the below listed information:

Enlistment Date: (YYYYMMDD) New Enl Period Start Date: (YYYYMMDD) Extension Term: (YY)/(MM) Drop Down YY=0-10 / MM=0-11 add time to End of Service Date New End of Service Date: (YYYYMMDD) – (As updated, needs to auto populate end of service date field on main screen)

1st Recontracting: (YYYYMMDD) 2nd Recontracting: (YYYYMMDD) 3rd Recontracting: (YYYYMMDD) Re-contracting Consult Consulting Date: (YYYYMMDD), (YYYYMMDD), (YYYYMMDD), (YYYYMMDD) Counselor’s Comments: Free Text Soldier/Policeman’s Reassignment Special Requests: Free Text Box

Standard Reports for Re-contracting:

Eligibility Report

Data Fields: UIC, Name, Rank, ID Card Number, Ethnicity, End of Service (EOS) Date, Eligible to re-contract: Y/N

Re-contracted Report Data Fields: UIC, Name, Rank, ID Card Number, Ethnicity, Re-contract date, New End of Service (EOS) Date

b. Duty Status: The purpose of these features is to ensure the HR professional can determine the duty status and maintain accountability of all Soldiers and policeman across the ANSF. This will be achieved by capturing the below listed information in a drop down under duty status field. Need to ensure duty status history is viewable. Duty status field is mandatory prior to saving record. Drop down list required with the following data fields.

Present for Duty

AWOL Without Weapon

Start Date: (YYYYMMDD) End Date: (YYYYMMDD)

AWOL With Weapon:

Civilian Custody

Leave

End Date: (YYYYMMDD)

Hospital Start Date: (YYYYMMDD) End Date: (YYYYMMDD)

Training Start Date: (YYYYMMDD) End Date: (YYYYMMDD)

In Transit Depart Date: (YYYYMMDD) Expected Arrival Date: (YYYYMMDD) required

Killed in Action (Automatically make record inactive) Date: (YYYYMMDD) (Casualty Section Required)

Cadet Under Training Start Date: (YYYYMMDD) End Date: (YYYYMMDD)

Combat Mission Start Date: (YYYYMMDD) End Date: (YYYYMMDD)

Temporary Duty Start Date: (YYYYMMDD) End Date: (YYYYMMDD) Duty Location: Free text, required

Duty status Whereabouts Unknown

Captured

End Date: (YYYYMMDD) Repatriation Date: (YYYYMMDD) Comments: Free Text

c. Personnel Separation and Termination: The purpose of these features is to allow the HR professional to separate Soldiers and Policeman in accordance with the MoD and the MoI separation and termination policies. Separate table under personnel services section in 1.0.

Type Separation (Drop down with bolded headings below)

Involuntary Separation (Drop down)

Dropped from Roll Misconduct

Sub-Standard Performance Qualitative Management Quantitative Management

Convicted of a Misdemeanor Abandons Duty during Crisis Insubordination Drug addiction or use of illegal drugs Fraternization Act of Contrary Unable to Perform Duties Reduction in Force Mandatory Retirement Criminal Act

Voluntary Separation (Drop down)

Expiration of Contract (Effective Date) Resignation: (Effective Date: (YYYYMMDD)) (Rule: can add future date not to exceed 5 days) Retirement: (Effective Date: (YYYYMMDD)) (Rule: can add future date not to exceed 5 days)

Medical Separation (YYYYMMDD) Free Text Box with up to 250 Characters

Temporary Involuntary Suspension (Drop down)

Unsuitability Voluntary Separation Medical Separation

Remarks: Free Text Box with up to 256 Characters

Date Separated: (YYYYMMDD) (Automatically make record inactive the day after the date in this field) -- Field should be able to capture a future date of up to 5 days from current date

d. Literacy: The purpose of these features is to allow the HR professional to identify a soldier’s and policeman’s literacy level to allow the MoD and MoI to identify ANSF members with certain skill sets and qualifications to execute certain mission sets.

ANQF Levels Literacy and

Basic Education Secondary and

Higher Education Technical and

Vocational Education

(TVET

Islamic Education

Level 8 (L8) H.E./PHD Level 7 (L7) H.E./Master Degree Level 6 (L6) H.E./Bachelor

Degree

Level 5 (L5) Tertiary Education/ Grade 14 Diploma

Tertiary Vocational Education/ Grade 14 Diploma

Tertiary Islamic Education/Grade 14 Diploma

Level 4 (L4) Advanced Certificate Advanced Islamic Advanced

High School/Grade 12 Certificate TVET High School

Certificate Islamic High School

Level 3 (L3) Intermediate Education/ Grade 9 Certificate

Intermediate Vocational Education and Training Certificate

Intermediate Islamic Education Grade 9 Certificate

School Preparation Literacy (L2C) Progression Literacy (L2B)

Level 2 (L2)

Foundation Literacy (L2A)

Vocational Training

Level 1 (L1) Basic Level Apprenticeship **Top row of this table will be data fields, columns will be drop downs linked to Level selected**

e. Reassignment: The purpose of these features is to allow the HR professional to properly track the reassignment of all ANSF members. This will be part of the assignment table.

New Unit of Assignment: Unit name (Drop down)

Gaining UIC: Auto populate from “New Unit of Assignment” Date of Reassignment: (YYYYMMDD) (Required if new unit selected)

-- Record automatically transferred to gaining UIC five days from reassignment date

f. Instructor Training Levels: The purpose of these features is to allow the HR professional to identify soldiers and policemen that are trained at certain levels to provide instruction of certain courses across the ANSF. Drop down list with the below. This will be part of the training table.

Satha One (1) Apprentice (Untrained Instructor) Satha Two (2) Instructor (Instructor with Supervision) Satha Three (3) Specialist Instructor (Unsupervised Instructor) Satha Four (4) Master Instructor (Training Manager and Instructor) Satha Five (5) Academy Instructor (Academic Instructor)

g. PASR: The purpose of these features is to allow the HR professional to provide personnel accountability;

report other strength-related information such as duty status, unit of assignment, location, and MOS/specialty code; and update command databases at all levels. This information will be captured in the following manner:

h. Personnel Summary (EXAMPLE—See Reports Section for Details)

PERSONNEL SUMMARY

Reporting Unit Date/Time of Report (As of :)

Previous Gains Losses Duty Status Changes Current OP

Stren gth

A ut h

Assi gned

OP

Stre ngth

Replace ments

Atta ched

Reass igned

K I A

R T D

M

IA

N B L

T D Y

O th

Assi gned

OP

Stre ngth

O N S C

To tal

PERSONNEL SUMMARY

Reporting Unit Date/Time of Report (As of :)

Previous Gains Losses Duty Status Changes Current OP

Stren gth

A ut h

Assi gned

OP

Stre ngth

Replace ments

Atta ched

Reass igned

K I A

R T D

M

IA

N B L

T D Y

O th

Assi gned

OP

Stre ngth

O N P C

To tal

***** Above format required for this report*****

i. Security Clearance: The purpose of these features is to allow the HR professional to identify the type of security clearance the soldier and/or policeman has and to allow the authorized security representative to make updates as required. The security clearance data will be read-only to all except the authorized security representative.

a. Security Clearance Type Drop Down Values should be: 1. Top Secret a.HUMINT b.SIGINT

2. Secret

3. Official

b. Date Security Clearance Granted (YYYYMMDD)

c. Date Security Clearance Expires (YYYMMDD)

d. Clearance Grantor Name, Rank, Date (YYYYMMDD) & title (free text up to 30 Characters)

e. MOD or MOI (Drop Down)

j. Casualty: The purpose of this feature is to allow the HR professional to capture casualty data within the area of operation, create casualty reports and transmits the reports to MoD and MoI casualty representatives.

The casualty information will be captured in the following manner merging current table in 1.0 with a new casualty screen:

ID Card Number (automatically populates all available data from main table) Name

Family Name Rank Profession Unit

Date of Birth Nationality Date of Incident Category Type (Drop Down)

(1) Martyred

(2) Injured

(3) Deceased

Was Body Recovered: Yes/No (Drop Down) Cypher Yes/No (Drop Down) Cypher Date (YYYYMMDD) Required date if Cypher “Y” Date of Report: (YYYYMMDD) Sex Religion Next of Kin

k. ADSO: The purpose of these features is to allow the HR professional to identify a soldier or policeman’s service obligation from initial entry.

NCO: 5 years from date of rank: Drop down box with Date of rank (YYYYMMDD) and auto populate new ADSO date (YYYYMMDD) Officer: 10 years from date of rank: Drop down box with Date of rank (YYYYMMDD) and auto populate new ADSO date (YYYYMMDD)

Note: Scan of supporting document required.

l. Civilian Data Fields Required on Main Screen: The purpose of these features is to allow the HR professional to identify and capture all information relating to civilians assigned to the organization. Drop down for all data elements that are possible (Sex, Blood Type, Rank, Position, Education Level, etc). Add fields that are not already on main screen in 1.0 and a check box to indentify civilian or military.

1. ID Number

2. Name

3. Family Name

4. Father name

5. Grand Father Name

6. Date of Birth

7. Sex

8. Blood type

9. Height

10. Weight

11. Eye Color

12. Hair Color

13. Distinctive Marks

14. Marital Status (drop down) “Married, Single, Widowed”)

15. Ethnicity (drop down)

16. Original Address

17. Current Address

18. Position

19. Rank

20. Education Level

21. Human Force Directorate Number (Unique number…free text not allowing duplicates)

ANP Civilian Ranks

General

Lieutenant General

Major General

Brigadier General

Colonel

Lieutenant Colonel

Major

Captain

Lt.CPT

1st Lieutenant

2nd Lieutenant

3rd Lt

Chief NCO

Senior Sergeant

Staff Sergeant

Sergeant

Patrolman First Class

Patrolman Second Class

PRR

Civilian rank

Grade 10

Grade 9

Grade 8

Grade 7

Rank 6

Rank 5

Rank 4

Rank 3

Rank 2

Rank 1

CTR GRADE 4

Above Rank

Out Of Rank

ANA Civilian Ranks OOR None

OR General

AR Lieutenant General

R1 Major General

R2 Brigadier General

R3 Colonel

R4 Lieutenant Colonel

R5 Major

R6 Captain

R7 1st Lieutenant

R8 2nd Lieutenant

G1 Sergeant Major

G2 Master Sergeant

G3 Sergeant 1st Class

G4 Staff Sergeant

G5 Sergeant

G6 Soldier

C1

C2

C3

C4

C5

C6

C7

C8

m. ANA Tashkil: The purpose of this feature is to allow the HR professional to identify, capture and document all ANA manpower and equipment requirements and provide support, analysis, and discipline for MoD’s (personnel, material, resource and force managers) plans and decisions. The Tashkil will be built as a separate screen linked to unit, UIC, position, paragraph number, line number, and other data fields listed on tashkil. Users at all level must have “view only” access Tashkil. This applies to both ANA and ANP Tashkil.

a. A tool will be included to allow Administrators to modify the Tashkil for future revisions/versions. This tool will emulate the current modification method that has already been provided to the contractor.

n. ANP Tashkil: The purpose of this feature is to allow the HR professional to identify, capture and document all ANP manpower and equipment requirements and provide support, analysis, and discipline for MoI’s (personnel, material, resource and force managers) plans and decisions. The Tashkil will be built as a separate screen linked to unit, UIC, position, paragraph number, line number, and other data fields listed on tashkil. Users at all level must have “view only” access Tashkil. This applies to both ANA and ANP Tashkil.

a. A tool will be included to allow Administrators to modify the Tashkil for future revisions/versions. This tool will emulate current modification method that has already been provided to the contractor.

o. Standard Reports: Excel format unless otherwise specified.

Personnel Summary Report (Data to capture below – report captures count # of each)

Unit details (Name/UIC):

Date of Report:

Authorized:

Assigned:

Operation Strength: (Authorized/Assigned) In-Transit:

Reassigned:

KIA:

Duty Status Whereabouts Unknown:

Temporary Duty:

Other:

Daily PERSTAT (Data to capture below – report captures count # of each)

Rank:

Authorized:

Assigned:

Strength percentage:

Present for Duty:

Combat Operation:

Martyred:

Wounded:

Duty Status Where about Unknown:

Captured:

AWOL with weapon:

AWOL without weapon:

Return to Unit:

In-Transit:

Re-contracting:

Passed Away:

Leave:

Sick:

TDY:

Detained:

Total Temporary Reductions:

Transfer:

Release/Separation:

DFR:

Total Permanent Reductions:

Shortages:

Weekly PERSTAT (Data to capture below – report captures count # of each)

Authorized:

Assigned:

Available:

AWOL with weapon:

AWOL without weapon:

Temporary Absence broken down by Sick:

Leave:

Total Temp Absence:

Monthly PERSTAT (Data to capture below – report captures count # of each)

Authorized:

Fielded (Annex K):

Present broken down by Combat Mission:

Garrison Duty:

Not present broken down by

AWOL:

Not Available:

Vacant:

Casualty Report (Martyrs and Wounded Status Report)

Last Name:

First Name:

Cypher:

Cypher Date:

Rank:

Duty Position:

Company:

Kandak:

Brigade:

Corps:

Tribe:

Registration Number:

Village:

District:

Province:

Date of incident:

Incident Type:

Type of Casualty:

Remarks:

Afghan National Readiness Report (Data to capture below – report captures count # of each)

Reporting Period:

Date:

Authorized:

Assigned:

Available:

Present for Duty:

Free Flow Text: 256 characters

ANA/ANP Absent Without Leave (AWOL) Unit details (Name/UIC):

Date:

Name:

ID Card Number:

Rank:

Duty Status: (AWOL and AWOL/With Weapon) Date of AWOL:

ANA/ANP Accountability Report

Date:

Name:

ID Card Number:

Rank:

Duty Status:

Duty Status Start Date:

Afghan Record Brief

Update current record summary to include data on the attached Record Brief and picture

Strength Report ANA (Data to capture below – report captures count # of each)

Unit details (Name/UIC):

Authorized:

Assigned:

Present for Duty:

AWOL /W:

AWOL:

Leave:

Hospital:

Consolidated Strength Report (Data to capture below – report captures count # of each)

Unit details (Names/UICs):

Authorized:

Assigned:

Present for Duty:

AWOL/W:

AWOL:

Hospital:

Strength Report ANP (Data to capture below – report captures count # of each)

Authorized:

Assigned:

Present for Duty:

AWOL /W:

AWOL:

Hospital:

p. Recruitment Table:

1. Soldier/Policeman Information

1. Record Number (Unique number automatically created by system)

2. Name

3. Family Name

4. Father name

5. Grand Father Name

6. Date of Birth

7. Sex

8. Height

9. Weight

10. Eye Color

11. Hair Color

12. Distinctive Marks

13. Marital Status (drop down) “Married, Single, Widowed”

14. Ethnicity (drop down)

15. Original Address

16. Current Address

17. Village: Free Text

18. District: (drop down)

19. Province: (drop down)

20. Ethnicity: (drop down)

21. Tribe or subset: (drop down)

22. Date of Birth: (YYYYMMDD)

23. Nationality: (drop down)

24. Education Level

25. Registration Number

2. Guarantor information:

1. Record Number

2. Name

3. Family Name

4. Father name

5. Grand Father Name

6. Date of Birth

7. Sex

8. Height (cm)

9. Weight (kg)

10. Eye Color

11. Hair Color

12. Distinctive Marks

13. Marital Status (drop down) “Married, Single, Widowed”

14. Ethnicity (drop down)

15. Original Address

16. Current Address

19. District: (drop down)

20. Province: (drop down)

21. Ethnicity: (drop down)

22. Tribe or subset: (drop down)

23. Date of Birth: (YYYYMMDD)

24. Nationality: (drop down)

3. Family information: (Drop down boxes)

Both Parents Living: Yes/No Married: Yes/No Children: Yes/No Ages Other Free text entry required

4. Physical information: (Drop down boxes)

Age Height (cm) Weight (kg) Distinguishing characteristics (Free Text Box)

5. In-processing

Date of Entry: (YYYYMMDD) Drug Test: (YYYYMMDD) Results:

Drop Down: Positive: Yes/No (drop down) Drop Down: Negative: Yes/No (drop down) Background check: (YYYYMMDD) Commissioners: Free Text Medical Exam: (YYYYMMDD) Biometric Enrollment: (YYYYMMDD)

BIV: (YYYYMMDD)

Date Shipped to Training: (YYYYMMDD)

Class information: Free Flow Text

6. Recruiting Stats

(1) Referral By: Drop Down (Uncle, Father, Cousin, Brother, Recruiter, Mullah, Other (Free text entry required)

(2) Media influence: Drop Down (TV, Radio, Billboard, Flyer, School Visit, and Promotional Item)

(3) Incentive with most influence: Drop Down (Pay, Skills Training, Literacy Training, Better Life, support GIROA, Other Free text entry required

In addition to adding the tables, data fields, and standard reports above, the contractor will make the following changes to the current version of AHRIMS:

1. Any field that uses a list as a dropdown field will remain a dropdown field throughout AHRIMS.

2. All pages, tables, and data within AHRIMS will be related and shared.(for example: Fields from main screen of the Recruitment tab should update AHRIMS Main Screen fields after record is in “Approved” Status)

3. The report building tool shall define reports without having to write a SQL query. Where possible, options shall be dropdown fields.

4. Watermark will be on the scanned images so that the scanned documents cannot be printed without the watermark from any screen/printer.

5. Maintain government provided Security Statement to main screen on log-in for First Time.

6. Maintain attachment requirement – a record update cannot be saved unless the supporting document is scanned.

7. Maintain Online Help, with Help Desk contact info and user manuals, to each page describing how to use the system, what information needs to be captured and how to load the information.

8. Screens and data fields will allow users to only type Dari in Dari screens/fields and English in English screens/fields.

9. Maintain “From” and “To” date fields to Afghan Militia Force (AMF).

10. Dari Numeric Field numbers will appear in Dari format.

11. Sort all drop down lists alphabetically or numerically, whichever is applicable.

12. Apache Batch File will run as a service so a login is not required to run.

13. Establish relationships between related data elements so that when one data element is updated, the other one must be as well. For example, when the Province is updated, the District must be updated as well.

14. Must retain capability to scan multiple page documents into one file/record and browse to upload pre-scanned document.

15. Must retain capability to make record active/inactive/retired. Active is the default for new records.

16. ONLY administrator is authorized to change record from inactive to active.

17. All addresses will display Province, District, and village fields (Province and District as drop down).

18. Attachments will be possible but not required in remarks, previous travel, previous job, references, and relatives screens.

19. National ID Place field will be a drop down.

20. Position field on assignment screen will be a drop down.

21. Type of Employment on assignment screen will be a drop down.

22. On Data Entry User main page, only show records newly assigned and those requiring update/correction.

23. Original and Current Address fields will be displayed on the Reference screen.

24. Ensure all drop down fields are searchable.

25. Mandatory remark field for Reviewer on records returned to Data Entry User for correction to clarify reason why returned.

26. Online Help Desk request/trouble ticket via simple email message.

27. Combine “Supplies” and “Equipment” screens/tables and move to “Personal Services” section.

28. “Duty Status” field on main screen is automatically populated when Duty Status screen is updated. The “Duty Status” field on the Main Screen is not editable just for viewing purposes.

29. Data Entry User retains rights to update any field/screen for all records in his/her UIC without having to be assigned by Reviewer. Updates must be approved by reviewer before being saved to records except Duty Status should automatically update without Reviewer.

30. Remove requirement of reviewer having to assign records to data entry user.

31. Contractor will establish and maintain a link to the respective ID Card system to import ID Card records.

This will be an import of data from the ID Card system.

32. Contractor will establicsh and maintain a link to the respective pay systems to assist the pay systems in validating personnel data. This will be an export of data to the pay systems.

4.0 Program Management:

4.1 The Contractor's program planning and control will include scheduling, program metrics, configuration management, contract change management, quality assurance, risk management, system transition planning, and subcontractor management.

5.0 Configuration Management (CM) Plan:

5.1 The Contractor will implement and maintain a formal CM program. This program will document the methodologies used for the application of CM techniques as they relate to all documentation, software, and other deliverables in a Contractor’s Configuration Management Plan (CCMP). The Contractor agrees to preserve and make available to the government, as requested, copies of all records and other documentation, developed or acquired under this contract regarding performance of the work required by this contract. The CCMP will be included as an appendix of the PMP.

6.0 Integrated Master Schedule (IMS):

8.1 The Contractor will develop and maintain a single schedule to manage the contractually authorized work. All scheduled work elements will be integrated into one IMS, including subcontractor and purchasing schedules. The schedule will identify all proposed activities, constraints, milestones, deliverables, and resource requirements for the entire period of performance. The schedule will be built to a sufficient level of detail to mitigate risk and measure performance, and will ensure that vertical and horizontal traceability is maintained at all times.

7.0 Software Test Program:

7.1 Contractor development and testing will be done at the Contractor’s facility. The Contractor will support a test approach in which Functional Management Office testers participate in architecture definition, initial design, functional analysis, Software Test Plan (STP) and Software Test Description (STD) evolution, system integration and testing. The Contractor will conduct and document testing to include unit, system, integration, and external interface testing for all software products. The Contractor will develop, update, and deliver an STP, an STD, and a Software Test Report (STR) for each defined testing phase. The STP will address all testing and test environments. The STD will include test cases and test scripts with test data inputs/outputs, and be sufficiently definitive to enable the functional users to assess the testing and its results. All Priority 1, 2, and 3 Deficiency Reports (DRs) as determined by the Government (for example reference Institute of Electrical and Electronic Engineers/Electronic Industries Association (IEEE/EIA) 12207.2) from development testing will be corrected prior to Test Readiness Review I (TRR I). The Contractor will create and manage a master test repository to capture all testing artifacts and provide accessibility to the testing community, and satisfy the requirements for a common Test and Evaluation (T&E) database. This T&E database will be delivered to the Government with the STR.

7.2 The Contractor will support Government Customer Acceptance Testing. The Government will test the full functionality of the system in the operational environment. The contractor will ensure CAT has no detrimental effect to the AHRIMS operational system. The Contractor will correct all Discrepancy Reports and submit for closure by the Government prior to final product fielding.

8.0 Quality Assurance:

8.1 The Contractor will implement and maintain a formal QA program, in accordance with a documented and approved Quality Control Plan (QCP) provided in the proposal, and will use those methodologies in satisfying all the requirements in this task order. The Government may conduct quality assurance audits to verify the Contractor’s compliance with the QCP. The QCP will encompass both products and processes.

8.2 Transitional Training Plan:

8.3 The Contractor will develop a transitional Training/Implementation Plan that outlines the overall strategy for transitioning AHRIMS to the ANSF. The plan will address key activities such as, but not limited to, software release, training schedule, , database administration and help desk support.

The plan will document milestones and schedule for each training implementation activity, and the dependencies between each. The plan will identify and document any risks associated with the activities necessary to achieve successful training/implementation.

8.4 The Contractor will provide a Training Manual of the Training Plan to verify Course Outline.

8.5 Disaster Recovery/Continuity of Operations Plan:

8.6 The Contractor will prepare a Disaster Recovery/Continuity of Operations Plan. The plan will include system recovery/restoration activities to ensure no loss of data.

8.7 This Disaster Recovery/Continuity of Operations Plan will include both hardware and software solutionsfor system recovery

8.8 Training:

8.9 The Contractor will provide necessary information and supporting material, such as updated User Manuals or requested “screen shots”, to assist the MoI/MoD Training Teams to develop training materials reflecting the capabilities of AHRIMS 1.1 software and to conduct training on the use of AHRIMS 1.1. The contractor will be responsible for updating MoI/MoD training materials as required to reflect system changes and new releases.

8.10 The Contractor will provide continuous training to ANA and ANP as needed to ensure system training and implementation is successful.

8.11 The Contractor will maintain the capability to train at a minimum of 15 locations simultaneously during fielding and implementation.

8.12 The Contractor will provide training to ANA and ANP on changes to the system or added functionalities.

8.13 Transitional training will include the following positions: DataBase Administrator (DBA), help desk personnel, “Train the Trainer” at training institutions, and other positions deemed necessary by government and/or ANSF.

8.14 Sustainment and Maintenance:

8.15 Operations Support

8.16 The AHRIMS system Contractor will support AHRIMS software production and operations. These tasks may include installation/checkout, system administration, database administration, security administration, disaster recovery, problem investigation/resolution, and others as they apply to AHRIMS.

8.17 Performance Monitoring, Optimization, and Minor Updates

8.18 The Contractor will monitor system performance to determine if optimal levels are being achieved, and if nominal availability levels are maintained. Significant deviations will be analyzed and corrected.

8.18.1 Provide latest Full backup once a week to the Government by Tuesday.

8.19 Optimization may include, but not limited to, database schema modifications and/or modification of existing application code.

8.20 Help Desk – AHRIMS Contractor Support

8.21 The Contractor will provide help desk support coverage 0800 – 1700 (Afghanistan Time), Saturday through Thursday, excluding official Government holidays. Maximum response time outside of normal support coverage hours will be 2 hours. Help desk activities and descriptions of the different levels of support will be described in the AHRIMS Help Desk Plan (Help Desk Plan). Help desk activities include, but are not limited to:

Resolving identified problems Conducting metrics collection, reporting, and trending Monitoring user activity and reporting anomalies to COR and MoD/MoI leadership

9.0 Contractor Furnished Facilities, Supplies, Equipment, and Services:

9.1 Equipment –

9.1.1 The Contractor will, with prior consent of the AHRIMS Contracting Officer, acquire, install, maintain, and provide any equipment required to accomplish tasks in PWS. At a termination or completion of the contract, all equipment will become the property of the Government.

9.2 Software –

9.2.1 The Contractor will, with prior consent of the AHRIMS Contracting Officer, acquire, install, maintain, and provide any additional software products needed to accomplish the tasks related to this PWS. At a termination or completion of the contract, all items purchased will become the property of the Government.

9.3 Data Rights –

9.3.1 The Government will have unlimited data rights to all efforts and products developed in direct support of the AHRIMS 1.1 effort, including but not limited to all software, source code, and documentation, without any restrictions whatsoever by the Contractor.

9.4 Travel –

9.5 The contractor will secure travel and low profile security for travel to training/implementation sites. Travel costs will be reimbursable upon government’s receipt of monthly invoice.

10.0 Place of Performance:

10.1 The majority of the AHRIMS software enhancement work is expected to be accomplished at the

Contractor’s facilities. As necessary, some work will be accomplished at Government or other Contractor locations (i.e., meetings, reviews, etc.).

10.2 Testing is to be performed at the Contractor’s facility prior to initial fielding and subsequent software version releases.

10.3 Contract employees will work within the Force Protection umbrella of coalition or Afghan

National Security Forces when conducting training/implementation at MoD/MoI sites throughout Afghanistan.

11.0 Period of Performance:

The Government estimates the Period of Performance for this effort as follows:

Task Order 4003:

Test, Field, Maintain & Support AHRIMS Version 1.1

19 Mar 2012 through 30 Sep 2013

12.0 Hours of Performance:

12.1 Nor

mal Hours/Duty Hours: Saturdays through Thursdays from 8:00 AM to 4:00 PM, except Afghan National Holidays.

12.2 Overtime Hours: Saturday through Thursday from 5:01 PM to 7:59 AM, except Afghan National

Holidays (must be requested and/or authorized by the COR).

12.3 The Contractor will establish an on-call schedule for services to be provided on Fridays, holidays, and after normal business hours described above. **On-call services should only be used in emergency situations, where in the best judgment of the MOI/MOD representative or COR, that would result in the database crashing or server inoperable.**

12.4 Recognized Holidays: The contactor is not be required to provide services on the following holidays, only an on-call service is required:

New Years (2 days) Mohammad’s Birthday The Victory Day of Islamic Revolution Independence Day Masood’s Day Parliamentary Elections 1st Day of Ramadan Eid Days (3 days) Big Eid (4 days) Ashura Day

13.0 Contracting Officer’s Representative:

13.1 A Contracting Officer’s Representative (COR) may be designated in writing by the Contracting Officer. All duties and authorities will be as stated in a COR delegation letter that will be provided to the Contractor. The COR will not be delegated contractual authority and therefore may make no changes in the terms and conditions of the contract.

14.0 Inherently Governmental Functions:

14.1 In accordance with FAR Subpart 7.503, the Contractor will not perform inherently governmental functions. Contracting Officers will retain all decision making authority for all Government contracts during all phases of the acquisition cycle.

15.0 Performance Requirements Summary (PRS):

The following PRS cites the performance standards for key areas of the contract and the associated thresholds that must be attained, over which the Government will exercise surveillance.

PWS Reference Task Performance Threshold Method of Surveillance

3.1 Status Reports Prepare and submit status 75% of reports submitted to Customer Receipt of Physical reports customer by the 1st and 15th of every month or Electronic Report

3.3 Maintain Secure Database Establish redundant security

measures to ensure no unauthorized access

100% of users IDs and passwords are for authorized users identified by MoI/MoD leadership

Periodic scheduled inspections

3.4 System/Server Protection Update/installation of

antivirus software

100% weekly update of antivirus and patch of the Data Base Server File and Windows Server File to keep server free of Virus worms, and other malicious code.

Periodic scheduled inspections

3.4 Data Protection Ensure secondary and tertiary

backups for every record

100% of daily backups performed and maintained ID Database

Periodic scheduled inspections

3.6 Data Fields, Tables, Reports

Ensure all data fields, tables, and reports are added to current version of system

100% of data fields, tables, and reports in this PWS are in version 1.1 and functioning properly

Customer Acceptance Testing

16.0 Deliverables: The contractor will provide the following deliverables to the Contracting Officer or

Contracting Officer Representative (COR) as indicated. All written deliverables will be translated and one copy provided in Dari and one copy in English except those submitted with proposal which will be in English only. Government has 7 work days to review and approve the preliminary draft of all contractor plans. The contractor has 7 work days, after receipt of Government comments, to prepare and deliver the final plan. If the contractor receives no input from the Government within 7 days, approval is implied.

22.1 Project Execution Plan and Schedule

Hard copy with proposal to Contracting Officer

22.2 Quality Control Plan

Hard copy with proposal to Contracting Officer

22.3 Synchronized Predeployment Operational Tracker (SPOT) Data Upload

On-Line data entry at https://spot.altess.army.mil/ by contract award + 10 calendar days

22.5 Bi-weekly Status Reports

Electronic (MS Word or PDF) format attached to email submitted bi-weekly to COR

22.6 Transitional Training Plan

Electronic (MS Word or PDF) format attached to email submitted to Contracting Officer and COR by contract award + 45 calendar days

22.7 Software Test Plan

Electronic (MS Word or PDF) format attached to email submitted to Contracting Officer and COR by contract award + 30 calendar days

22.8 Updates to Software User Manuals and Training Materials

Electronic (MS Word or PDF) format attached to email submitted to Contracting Officer and COR by contract award + 45 calendar days

22.9 Contractor Manpower Reporting

By 31 October 2012

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor will report all contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor is required to completely fill in all the information in the format using the following web address https://contractormanpower.army.pentagon.mil.

**** this Contract line Item Is for Informational Purpose Only, and is not a Separately priced Solicitation line item.****

The required information includes:

(1) Contracting Office, Contracting Officers, Contracting Officer’s Technical Representative; (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data; (5) Estimated direct labor hours (including subcontractors); (6) Estimated direct labor dollars paid this reporting period (including subcontractors); (7) Total payments (including subcontractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each subcontractor if different); (9) Estimated data collection costs;

(10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information); (11) Locations where contractor and subcontractors perform work (specified by zip code in the United States and nearest city, country, when in an overseas location, using the standardized nomenclature provided on the website); (12) Presence of deployment or contingency contract language; and (13) Number of contractor and subcontractor employees deployed in theater this reporting period (per country). As part of this submission, the contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the field on the website. The XML direct transfer is a format for transferring filed from a contractor’s systems to the secure website without the need for separate data entries for each required data element at the website. The specific formats for the XML direct transfer may be downloaded from the website. *Note: Information from the secure website is considered to be proprietary in nature when the contract number and contractor identity are associated with direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

CONTRACTOR MANPOWER REPORTING

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure

Army data collection site where the contractor will report all contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor is required to completely fill in all the information in the format using the following web address https://contractormanpower.army.pentagon.mil.

**** this Contract line Item Is for Informational Purpose Only, and is not a Separately priced Solicitation line item.****

The required information includes:

(1) Contracting Office, Contracting Officers, Contracting Officer’s Technical Representative; (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data; (5)

Estimated direct labor hours (including subcontractors); (6) Estimated direct labor dollars paid this reporting period (including subcontractors); (7) Total payments (including subcontractors); (8) Predominant Federal Service Code

(FSC) reflecting services provided by contractor (and separate predominant FSC for each subcontractor if different);

(9) Estimated data collection costs; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information); (11) Locations where contractor and subcontractors perform work

(specified by zip code in the United States and nearest city, country, when in an overseas location, using the standardized nomenclature provided on the website); (12) Presence of deployment or contingency contract language;

and (13) Number of contractor and subcontractor employees deployed in theater this reporting period (per country).

As part of this submission, the contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year.

Contractors may use a direct XML data transfer to the database server or fill in the field on the website. The XML direct transfer is a format for transferring filed from a contractor’s systems to the secure website without the need for separate data entries for each required data element at the website. The specific formats for the XML direct transfer may be downloaded from the website. *Note: Information from the secure website is considered to be proprietary in nature when the contract number and contractor identity are associated with direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

--- END OF PERFORMANCE WORK STATEMENT---