Amendment_0001_to_HQ0013-16-R-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

SEE CONTINUATION PAGE

1. CONTRACT ID CODE PAGE OF PAGES

S 1 21

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 28-Feb-2016

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HQ0013-16-R-0002

X 9B. DATED (SEE ITEM 11)

12-Feb-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

28-Feb-2016

CODE

DEFENSE SECURITY COOPERATION AGENCY-CON

WOODROW W. BELL JR

201 12TH STREET, SOUTH

SUITE 203

ARLINGTON VA 22202-5408

HQ0013 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HQ0013-16-R-0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

1. The purpose of this modification is to incorporate the Questions and Answers into the solicitation and to make revisions to the solicitation.

2. The Questions and Answers document, Attachment 01 to this modification, is incorporated as Attachment 07 to the overall solicitation.

3. In response to Question 1, the Performance Requirements Summary (PRS), Attachment 02 to this modification, is incorporated as Attachment 08 to the overall solicitation.

4. In response to Question 3, the estimate of labor distribution at 2.1.4.c of the PWS is changed

From:

c. The estimate of labor distribution for each period of performance is as follows:

i. Project Manager: 31%

ii. Analyst: 40%

iii. Programmer: 100%

iv. Programmer: 100%

To:

iv. Programmer: 8%

5. FAR 52.243-3 Changes--Time-And-Material Or Labor-Hours (SEP 2000) is deleted from the solicitation.

6. Paragraph 1.3.5, of the Instructions to Offerors, is changed

From:

The Government will choose the excluded contract(s) at random, or in any manner that the Government, in their absolute discretion, deems appropriate, without any consideration for the best interests of the offeror.

To:

In the event more than three contracts are submitted by an offeror, the Government will choose the contract(s) to exclude at random, or in any manner that the Government, in their absolute discretion, deems appropriate, without any consideration for the best interests of the offeror. If a firm submits ONLY three past performance samples, none will be excluded

7. In response to Question 8, the hour and date specified for receipt of Offer is extended. The new hour and date is

3:00 pm EST, on 9 March 2016.

8. 5.6.a is changed from reading as-

Project Manager: Master’s Degree, Security+ CE (required for DoD system), high level experience with

Microsoft applications, minimum of an ADP-3 level of trust, minimum 10 years’ experience with each task identified in the PWS under CLINS 1-3, minimum 5 years’ experience with CLIN 4, Secret Clearance.

to reading as-

Project Manager: Master’s Degree, Security+ CE (required for DoD system), high level experience with

Microsoft applications, minimum of an ADP-2 level of trust, minimum 10 years’ experience with tasks similar to those identified in the PWS under CLINS 1-3 and minimum 5 years’ experience with tasks similar to those identified in the PWS under CLIN 4, Secret Clearance.

9. 5.6.c is changed from reading as-

Data Analyst: Minimum 5 years’ experience with logistics practices and policies, minimum 5 years’ with Help

Desk experience, minimum familiarization course from Defense Institute of Security Assistance Management

(DISAM) course for awareness of Security Assistance Programs, Software Quality Assurance, and Secret

Clearance.

to reading as –

Analyst: Minimum 5 years’ experience with logistics practices and policies, minimum 5 years’ with Help Desk experience, minimum familiarization course from Defense Institute of Security Assistance Management

(DISAM) course for awareness of Security Assistance Programs, Software Quality Assurance, and Secret

Clearance.

10. 5.7 is changed from reading as-

General skills required: Minimum five years’ experience directly related to Security Assistance programs (to manage the EUM Helpdesk), minimum five years’ experience with programs similar to the EUM program (to assist Security Cooperation Officer’s worldwide), five years’ experience with software programs similar to the

Security Cooperation Information Portal (to train users during EUM Regional Forum Training Seminars), knowledge and prior experience in planning, execution, and closing of projects (to manage new enhancements listed in CLIN 4). Must be able to manage and control periodic work and customized reports from CLIN 3 including: assisting in the preparation of collection of data requirements; development and scheduling/phasing;

change management; scope management; status tracking; communication and resolving multiple project issues.

to reading as-

General skills required: Minimum five years’ experience directly related to Security Assistance programs (to manage the EUM Helpdesk), minimum five years’ experience with programs similar to the EUM program (to assist Security Cooperation Officer’s worldwide), five years’ experience with software programs similar to the

Security Cooperation Information Portal (to train users during EUM Regional Forum Training Seminars), knowledge and five years’ prior experience in planning, execution, and closing of projects (to manage new enhancements listed in CLIN 4). Must be able to manage and control periodic work and customized reports from CLIN 3 including: assisting in the preparation of collection of data requirements; development and scheduling/phases; change management; scope management; status tracking; communication and resolving multiple project issues.

11. All other terms and conditions remain unchanged.

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 04-Mar-2016 02:00 PM to 09-Mar-2016 03:00 PM.

The following have been modified:

ATTACHMENTS AND EXHIBITS

Attachments/Exhibits Description No. of

Pages

Date

01 Security Cooperation Information Portal (SCIP) 1 12 Feb 2016

02 End-Use Monitoring EUM Application 2 12 Feb 2016

03 Vendor SCIP-EUM Permissions Matrix 1 12 Feb 2016

04 Performance Matrix 1 12 Feb 2016

05 Projects for Base Period 2 12 Feb 2016

06 Past Performance Questionnaire 4 12 Feb 2016

07 Questions and Answers 3 25 Feb 2016

08 Performance Requirements Summary 3 12 Feb 2016

PWS

PERFORMANCE WORK STATEMENT FOR

SUPPORT TO THE END-USE MONITORING PROGRAM

11 February 2016.

This Performance Work Statement defines work to be performed in support of the Defense Security Cooperation

Agency’s (DSCA) Golden Sentry End-Use Monitoring (EUM) program. It includes both programmatic and information technology activities.

1.1 Background

1.1.1 About DSCA

DSCA is responsible for planning, coordinating, administering, and supervising Department of Defense (DoD) programs for transfer of defense articles, services, and technology, by sale or grant, to foreign governments and international organizations. These programs include Foreign Military Sales (FMS) where defense articles and services are sold to foreign countries or international organizations, Foreign Military Financing (FMF) under which grants or loans are provided to foreign countries for financing of FMS or direct commercial contracts with U.S.

industry, International Military Education and Training (IMET) under which financial assistance is provided to foreign students attending U.S. military schools, and Humanitarian Assistance and Mine Action (HA/MA) under which support is provided to foreign governments. In value, these programs total billions of dollars annually, and

DSCA is responsible for directing and supervising them from inception through completion by accounting and reporting. In addition, DSCA develops computer applications, unique to the Security Cooperation mission, to support the business processes of both DSCA Headquarters and other elements of DoD that execute the mission.

Detailed responsibilities of the Agency are set forth in DoD Directive 5105.65. DSCA headquarters is located in

Arlington, VA.

The Security Assistance Directorate is responsible for the oversight of the End Use Monitoring program and as such will provide overall guidance.

1.1.2 About the End-Use Monitoring Program

In 1996, Congress enacted section 40A of the Arms Export Control Act (AECA) [22U.S.C. 2785]. Section 40A requires The President to establish an EUM program of defense articles sold, leased, or exported under the AECA or the Foreign Assistance Act (FAA) to: 1) improve accountability and provide “reasonable assurance” that recipients comply with U.S. export control requirements regarding the use, transfer, and security of defense articles and services and; 2) ensure that the program provides end-use verification of defense articles and services for sensitive technology. DSCA developed the Golden Sentry EUM program in 2001 to comply with Section 40A. The program’s focus is on government-to-government transfers and ensures that defense articles and services are only sent to authorized recipients and that recipients clearly understand their responsibilities regarding end use, retransfer restrictions and security of the equipment provided. U.S. personnel assigned to Security Cooperation Organizations

(SCO) at embassies worldwide are required to observe and report any potential misuse or illegal transfer of U.S.-origin defense articles. For determined defense articles, Golden Sentry has established a EUM regime of physical security and inventory checks which requires entering each serial number in a database for inventory monitoring and historical data.

The EUM program continues to improve its processes and establish new guidance and policy. Education of participants is accomplished via Regional Forums and a Quarterly EUM newsletter. An initial version of supporting education via automation is being fielded by DSCA. Population of the database continues to be ongoing and challenging due to the quantity and various manufactures of Defense Articles. In regards to the data, DSCA is working with military departments and trying to establish the baseline of all identified Enhanced EUM (EEUM) articles.

Security Cooperation Information Portal

The Security Cooperation Information Portal (SCIP) is a web-based system housing a family of applications. The two major current areas of functionality involve FMS case execution and EUM tracking of determined defense articles and defense services. The EUM application was deployed in a subset of SCIP functionality known as

“SCIP-EUM” in December 2004. Basic information on the SCIP can be found at https://www.scportal.us/home/.

2.0 Objective

The SCIP-EUM program will have four major thrusts:

- User support which includes assisting the DSCA EUM Program Office in educating the SCIP-EUM users on how to use SCIP-EUM and creating the appropriate documentation.

- Weapons data research and database population includes obtaining records from the Military Departments

(MILDEPs) and Implementing Agencies (IAs) and updating the serial numbers to the SCIP-EUM database prior to the articles being shipped.

- Program analysis, data retrieval, and report generation

- Application maintenance and enhancement includes creating and enhancing current automation to maintain a database of delivered weapons, to schedule inspections, to allow the inspectors to record their findings, and to allow DSCA to monitor overall program progress

2.1 Specific Tasks: The Government estimates the following labor categories will be required to perform the tasks of User Support (2.1.1), Weapons Data Research and Database Population (2.1.2), Program Analysis (2.1.3) and Application Maintenance and Enhancement (2.1.4). The Labor categories are Project Manager (1 each), Analyst (1 each) and Programmer (2 each). The qualification are found at Section 5.6 of this PWS. The estimated breakout of effort for each labor category at each task follows the task description, at each subsection below. The estimated effort is displayed as a percentage of one hundred percent (100%). The combined percentages for each labor category across the task is equal to 100%. 100% of effort equals one Full Time Employee (FTE).

2.1.1 User Support

a. The contractor shall assist the DSCA EUM Program in training the security cooperation community (e.g., DSCA, implementing agencies, combatant commands, security cooperation organizations, and host nations) by educating the participants via EUM Training Seminar, Quarterly EUM Newsletter and answering questions by viewing SCIP-

EUM data regarding deliveries and inventory information.

As a result, the contractor must have a complete understanding of the EUM program. This task will include the following sub-tasks:

- Communicate with users to answer questions and provide instructions

- Provide help desk support to accommodate EUM questions within 24 business hours

- Update and keep current user enrollment and permissions

- To assist the DSCA EUM Program Office in training the SCO community during EUM Training Seminars.

- Update and keep current the SCIP-EUM User Guide

(https://www.scportal.us/portal/server.pt/gateway/PTARGS_0_0_239_226_0_43/Resources/handbook/SCI

P-EUM%20Handbook%20Version%203.8.pdf)

- Review and process access requests and ensure only authorized users obtain access

- Create and electronically send a quarterly EUM newsletter

- Mail instructional handbooks and other material

- Maintain the EUM Support page in SCIP-EUM

- Research EUM questions

- Coordinate with the SCIP Help Desk (Defense Security Assistance Development Center, Mechanicsburg, PA -DSADC) to resolve automation issues

b. The contractor shall support the development of end user documentation of input forms, tables, reports, error messages, and other graphic user interfaces as implemented for reference by test staff, user population, etc. The purpose of this documentation is to describe the programs and provide guidance to end users through the various steps of invoking and using the programs. This is currently described in the SCIP-EUM Customer Assistance

Handbook and other related documents.

c. The contractor shall provide documentation of revisions/updates to code, algorithms, application program interfaces, validation logic, error handling, and special behaviors associated with data structures. The purpose of this documentation is to support life cycle maintenance by Government staff and furnish troubleshooting assistance to

Government programmers who subsequently maintain the program code.

d. Documentation developed by the contactor must be stored into the Defense Security Assistance Development

Center (DSADC) End User Document Template referenced in Addendum A of the Performance Work Statement

(PWS).

e. The estimate of labor distribution for each period of performance is as follows:

i. Project Manager: 17%

ii. Analyst: 20%

f. The DSCA EUM Contracting Officer’s Representative will monitor contractor performance under this task.

2.1.2 Weapons Data Research and Database Population:

a. This task entails locating the source of serial numbers and other program data for various weapons supplied by

DoD to foreign governments. Items of inventory to be managed include, Communication Security (COMSEC)

Equipment, STINGER Missiles and Gripstocks, Night Vision Devices (NVDs), JAVELIN missiles and CLU’s, TOW IIB, AMRAAM missiles and Guidance Sections, AIM-9X missiles and Guidance Units, SLAM-ER, Harpoon

Block 1G/II and GCU, JASSM, JSOW, SM-3, Tomahawk, Large Aircraft Infrared Countermeasures (LAIRCM), Terminal High Altitude Area Defense (THAAD), Unmanned Aircraft System (UAS) and other articles deemed enhanced, including certain routine and grant assistance.” The contractor shall compile serial numbers, notes, inspection histories, technical details, types of transfer (i.e. grant, MAP, FMS, Presidential determination, etc.), delivery dates, etc.

Specific tasks that are completed for this CLIN include:

Weapons Data Research:

- Conduct research, in accordance with the priorities of the End-Use Monitoring (EUM) Contracting

Officer’s Representative, of military departments, major commands, program offices, and manufacturers’ data to locate lists of selected weapons and their serial numbers.

- Review Foreign Military Sales (FMS) cases with Enhanced EUM items to ensure these items properly appear on the EEUM Reconciliation Report with an accurate item description and to ensure quantities and delivered items are properly annotated in SCIP-EUM.

- Review FMS cases to compile working lists of FMS case lines for which serial numbers have not yet been received but are expected to be delivered.

- Research late deliveries to determine the nature of the delay. This task involves contacting individuals at the MILDEP program office and SCOs; running reports in SCIP and DSAMS to include case information, information extract, active requisitions, and case reports; and contacting case managers/writers to obtain other details.

- Maintain a POC list by MILDEP of contacts for all EEUM weapon system programs.

Weapons Database Population:

- Load weapon serial numbers received from MILDEPs using either the Microsoft Excel bulk item load tool or the SCIP ‘Add Item’ tool.

- Research delivery quantity discrepancies in weapon data provided by MILDEPs, and contact

MILDEPs/SCOs to reconcile the discrepancies.

- Perform additional research if duplicate serial numbers are reported and work with the MILDEPs/SCOs to resolve the duplicates.

- Contact SCOs to advise of the initial inventory requirement once items are loaded.

- Contact SCOs that do not perform the initial inventory of items that were loaded in advance, to determine if shipment has occurred and adjust delivery dates accordingly.

- Enter inventory information for SCOs that have limited internet access or encounter difficulties using SCIP.

- Maintain a POC list of all EUM SCO and COCOM personnel worldwide.

- Ensure Figure of Merit and other Night Vision Device (NVD) performance characteristics are populated in the EEUM Reconciliation Report.

- Review all locations entered by country and work with the SCOs and EUM Program Office to correct and standardize location data worldwide. This review will be used to ensure the accuracy of data on EEUM checks.

- Populate new EEUM item names in the SCIP-EUM item database, and maintain the Microsoft Excel bulk item load tool to ensure that it has the current list of available item names.

- Research all known sources of item delivery dates, including but not limited to MILSTRIP, DSAMS, SCIP case information, SCIP Enhanced Freight Tracking System, Wide Area Workflow. This research will be used in conjunction with CLIN 4 task E4136, Improve Estimated Ship Date.

b. Once data has been located for various weapons, it must be properly loaded into the SCIP-EUM database. There are two methods to achieve this requirement: “entering data a single record at a time or batch data loads.”

c. The preferred method is to employ batch data loads to load large quantities of data into the SCIP-EUM. Single record entry is most appropriate for corrections or for low volume weapons. Once data is loaded, it shall be reviewed in the SCIP-EUM to verify it was loaded correctly and notify the SCO so he/she can identify its disposition.

d. The estimate of labor distribution for each period of performance is as follows:

i. Project Manager: 32%

e. The DSCA EUM Contracting Officer’s Representative will monitor contractor performance under this task.

2.1.3 Program Analysis

a. The contractor will perform periodic and customized reports to the DSCA EUM Program Office upon request of the Government. These reports will likely be created by ad-hoc retrievals from the SCIP-EUM application or other sources. This may include data comparison and analysis from SCIP-EUM or other Excel reports. This will help gauge the success of the program. Examples of requested reports may include:

- Size of the inventory in SCIP-EUM

- Comparison of data, actual inspections to planned inspections, decomposed articles, country analysis, and whether a host country or SAO conducted the inspection

- Tabulate weekly reports that detail all new and changed SCIP-EUM items

- Program statistics (e.g., number of weapons identified, number of SNs entered, etc.)

b. Data on all weapons sold, transferred, or otherwise delivered to a country are to be included in the EUM program.

The data will remain in the database regardless of status of the weapon (i.e., expended, transferred, or otherwise disposed of).

i. Project Manager: 20%

d. The DSCA EUM Contracting Officer’s Representative will monitor contractor performance under this task.

2.1.4 Application Maintenance and Enhancement

a. Contractor shall provide information technology (IT) system enhancement to SCIP on time. There are ten specific, defined software development and enhancement tasks to be performed in the base year. See Attachment 05. The projects for the base year will be numbered Project E0142 through Project E0151. The milestone chart for completing of the projects will be defined by DSADC’s release schedule, which is developed in the beginning of each fiscal year. A list of ten new projects will be provided for each option year that is exercised. The estimated effort to complete the projects will remain as shown at Paragraph c of this section, for the base year and each option year.

b. The contractor shall perform the requirements analysis, design, coding, unit test, and system test of the functionality of these ten new projects before submitting them to the Government for acceptance. Each project shall include an update to the SCIP-EUM design documentation and functional specification. Contractor testing must confirm, not only that the applications run, but that they compute correct results.

iv. Programmer: 8%

d. All development will be done using the SCIP Development System at DSADC, sometimes known as the “sandbox”. The sandbox can be accessed on-site at DSADC. Testing will be performed on the SCIP Quality Assurance (QA) server at DSADC.

e. The SCIP Program Office at DSADC and DSCA EUM Contracting Officer’s Representative will monitor contractor performance under this task.

2.1.5 Travel

Personnel may travel both CONUS and OCONUS (US and foreign locations) with a maximum estimate of local trips, NTE 250 miles, at 10 trips per year, 5 trips per year exceeding 250 miles, and 4 trips per year OCONUS.

3.0 Acceptance Testing

Acceptance Testing of delivered products by DSCA will be performed in a two-step process:

1) Members of the EUM program office, or other assigned DSADC staff, will test the system for correctness, usability, conformance with requirements, and performance.

2) Members of the EUM program office will test the system for the same criteria and the DSCA EUM Contracting

Officer Representative will give final release authorization.

The DSCA SCIP Program Office and DSCA EUM Contracting Officer Representative will monitor this task.

4.0 Work Location

Personnel will be located on-site at the DSCA satellite office in Mechanicsburg, Pennsylvania (DSADC). In this case, all facility and automation support will be provided as Government Furnished Equipment.

Normal operating hours for this contract will be during DSADC's core hours from 0630 to 1700

Monday through Friday. Access to the DSADC facility outside of these hours should be approved by the COR, contractor employees' supervisor, the DSADC security officer or DSADC front office. In addition, access to the DSADC facility requires government personnel to accompany contractors outside of the normal operating hours.

5.0 Personnel and Special Qualifications

5.1 The contractor shall be responsible for providing technically qualified personnel to perform the work specified in this PWS. The contractor shall maintain the personnel, organization, and administrative control necessary to ensure that the work delivered meets the contract specifications and requirements.

5.2 The resume of the contract employee must reflect experience directly related to the task and functions he/she is intended to perform under this contract.

5.3 The contractor shall submit the resumes of personnel to the Government, for the purpose of confirming for the purpose of verifying compliance with the qualification requirements listed in 5.6 of this PWS.

5.4 Personnel assigned to, or utilized by, the contractor in performance of work shall be fully capable of performing the contemplated functions in an efficient, reliable, and professional manner. The contractor shall provide a programmer, data analyst, and a project manager to satisfy the requirements of this project. The contractor must provide resumes for all proposed personnel in response to this PWS. The resumes must identify all proposed personnel and identify their anticipated role in the execution of this PWS. Once identified as such, key personnel may not be removed from this project without written acknowledgement from the DSCA Contracting

Officer/Contracting Specialist.

5.5 All work associated with the SCIP-EUM application is unclassified/sensitive, as the SCIP system is accredited as a MAC III, Sensitive system. Only U.S. citizens are authorized to participate in the development of the above projects, or any SCIP software applications, in accordance with the defined U.S. citizenship standard for all SCIP development team members. Personnel must have a minimum of an ADP-3 level of trust. Programmers performing

Application Maintenance and Enhancement must have an ADP-2 level of trust. Any personnel located at DSADC must have a minimum of a SECRET security clearance. This requires a Single Scope Background Investigation

(SSBI).

5.6 General Qualifications:

a. Project Manager: Master’s Degree, Security+ CE (required for DoD system), high level experience with

Microsoft applications, minimum of an ADP-2 level of trust, minimum 10 years experience with tasks similar to those identified in the PWS under CLINS 1-3 and minimum 5 years experience with tasks similar to those identified in the PWS under CLIN 4, Secret Clearance.

b. Programmer: Bachelor’s Degree, minimum 5 years’ experience in programming in Java web development, Microsoft .Net web development, Oracle WebCenter Interaction Portal development and administration Software deployments. Must maintain and have a minimum Security+ CE (required for DoD system) and minimum of an ADP-2 level of trust, Secret Clearance.

c. Analyst: Minimum 5 years’ experience with logistics practices and policies, minimum 5 years’ with Help

Desk experience, minimum familiarization course from Defense Institute of Security Assistance Management

(DISAM) course for awareness of Security Assistance Programs, Software Quality Assurance, and Secret Clearance.

5.7 General skills required: Minimum five years’ experience directly related to Security Assistance programs (to manage the EUM Helpdesk), minimum five years’ experience with programs similar to the EUM program (to assist

Security Cooperation Officer’s worldwide), five years’ experience with software programs similar to the Security

Cooperation Information Portal (to train users during EUM Regional Forum Training Seminars), knowledge and five years’ prior experience in planning, execution, and closing of projects (to manage new enhancements listed in

CLIN 4). Must be able to manage and control periodic work and customized reports from CLIN 3 including:

assisting in the preparation of collection of data requirements; development and scheduling/phases; change management; scope management; status tracking; communication and resolving multiple project issues.

5.8 Computer skills required: Proficient in MS Office Suite applications of MS Project, Outlook, Word, Access, and PowerPoint; proficiency with Excel to perform data evaluation, pivot tables, formulas and analytics. Must be able to utilize MS Project for management of tasks, collaboration, managing timelines and measuring progress utilizing system to generate reports.

Must be able to transfer presentation graphics from Excel into PowerPoint.

5.9 Security Requirements: Security and Academic Informational Requirements: The contractor shall establish appropriate administrative, technical, and physical safeguards to protect all Government data to ensure the confidentiality, integrity, and availability of government data. The contractor should refer to DoD Regulation

5200.2-R, Personnel Security Program for details.

5.9.1. The contractor employees will comply with all applicable government security directives and regulations during the performance of work. All contractors are required to complete DSCA security annual requirement

(OPSEC, Security Refresher, AT and CI training). Contractor personnel are responsible for safeguarding building passes and other badges, and must immediately report a lost or stolen badge to the COR, and DSCA Security office.

5.9.2. The overall classification for this contract is unclassified, but sensitive. However, a secret clearance is required for classified discussion and presentations conducted at DSCA Headquarters. The contractor is required to have a minimum Interim Secret Clearance before coming on board.

5.9.3. All work associated with the SCIP-EUM application is unclassified/sensitive. However, the SCIP system is accredited as a MAC III, Sensitive System, and the following additional requirements are required before participating in the development of the projects specified in this PWS.

5.9.3.a Must be a U.S. citizen, in accordance with the defined U.S. citizenship standard for all SCIP development team members.

5.9.3.b Personnel must have a minimum of an ADP-3 level of trust. Personnel working on CLIN 4, “Application Maintenance and Enhancement” must have an ADP-2 level of trust.

5.9.3.c Any personnel supporting the EUM Program Office must have a minimum of a SECRET security clearance. A DD 254 shall be completed by the contractor for classification and subsequent security requirements for the contractor, any subcontractors, and personnel assigned to this contract. A DD Form 254 shall be attached to the contract.

5.9.4. Upon award of this contract, names and social security numbers (SSN) of contract employees working on this contract will be submitted to regional center security officer. If a contract member does not have the appropriate investigative or security clearance requirement the contract employee will be denied the ability to work in support of this PWS. If the Government notifies the contractor that the employment or the continued employment of any contractor employee is prejudicial to the interests or endangers the security of the United States of America, that person will be removed and barred from the worksite. This includes security deviations/incidents and credible derogatory information on contract members during the course of the contract period. The awarded contract company shall make any changes necessary in the appointment(s).

5.9.5. Upon completion of this contract, the contract employee will surrender all government supplies, materials and equipment to the COR/designated government representative. Upon the completion of the contract, the contractor is required to out-process with the designated center’s Security; and return all access badges accordingly.

5.9.6. For Official Use Only (FOUO) applies for all unclassified material. For information and regulatory guidance for FOUO refer to DoD 5200.1-R, Appendix 3 and the Under Secretary of Defense for Intelligence memorandum, "Interim Information Security Guidance," dated 16 April 2004, (http://www.fas.org/sgp/othergov/dod/dod041604.pdf), for specific guidance on the handling & safeguarding of

FOUO information. Contract companies can be held under punitive damages for releasing FOUO information outside government computer systems without prior authorization from the designated center’s Information Security

Officer or COR.

5.9.7 The contractor is responsible for safeguarding all classified, sensitive or proprietary information. Failure to safeguard any classified, sensitive or proprietary information which may involve the contractor or the contractor’s personnel or to which they may have access may subject the contractor and/or the contractor’s employees to criminal liability. Provisions of the Privacy Act apply to all records and reports maintained by the contractor. All programs and materials developed at government expense during the course of this contract are the property of the government. Contractor personnel assigned to work at a Government work site shall have a security clearance as required at Section 5.9 of the PWS. In accordance with DoD Directive 5220.22-M, Department of Defense

Industrial Security Manual for Safeguarding Classified Information, and any revisions, thereto, as well as Industrial

Security Regulation DoD 5220.22-R.

5.9.8 Physical Security. The contractor shall safeguard all government equipment, information and property provided for contractor use in accordance with DoD 5200.08-R, DoD Physical Security Program. At the close of each work period, government facilities, equipment, and materials shall be secured as required by the local

Government facility.

5.9.9 Copyright Considerations. In conducting work under this contract, course materials, texts, audio and video training aids, materials, and equipment are developed. The Contractor, in the normal course of contract performance, contributes and/or assists in this effort. Since these original materials are produced specifically for the

Government and are produced using Government materials and equipment, all rights to these materials belong to the

Government. The Contractor waives all right to and claims for compensation against these materials, other than the normal compensation for performance of the contract.

5.9.10. If the Government notifies the contractor that the employment or the continued employment of any contractor employee is prejudicial to the interests or endangers the security of the United States of America, that person will be removed and barred from the worksite. This includes security deviations/incidents and credible derogatory information on contract members during the course of the contract period. The awarded contract company shall make any changes necessary in the appointment(s). Security incidents involving contractors will be posted by appropriate center Security personnel and the details forwarded to DISCO and the contractor FSO for action.

5.9.11. Comply with Personal Identity Verification (PIV) issuance requirements, known as the Common Access

Card (CAC); and applicable data access and other security related training according to appropriate

NESA/ACSS/WJPC and NDU regulations.

5.9.12. Execute a DD Form 2841, Department of Defense (DoD) Public Key Infrastructure (PKI) Certificate of

Acceptance and Acknowledgement of Responsibilities, and applicable Non-Disclosure Agreements prior to being provided access to any NDU/NESA/ACSS/WJPC application, system, and/ or password.

5.10 Contracting Officer Representative (COR):

5.10.1 The (COR) is identified by separate letter. A copy of this letter is sent to the Contractor and states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the contract.

5.10.2 The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel.

5.10.3 The COR is the point of contact for the Project Manager. The COR will provide the contractor with the materials and information necessary for the proper performance of the tasks under the contract.

6.0 Deliverables

1. Monthly progress reports

2. A monthly activity log of user interactions.

3. A monthly activity log of contacts made to obtain weapons and serial number data.

4. Monthly and cumulative progress in the volume of countries, weapons, and serial numbers identified and loaded into SCIP-EUM.

5. Status of application modification and enhancement tasks underway.

6. A monthly and cumulative list of application tasks initiated, completed, and accepted.

All reports shall be submitted in Microsoft Word, Excel, Power Point, or Adobe PDF format in electronic copy.

7.0 Duration of Contract

The performance period for services include a twelve month (12) base year and two (2) twelve month option years.

8.0 GFI/GFE

Contractor personnel will work at DSADC and the Government will provide a suitable workstation, with computer, access to the local DSADC network, access to network printer, access to the Internet, and telephone. For personnel working at DSCA HQ the same type GFI/GFE will be provided.

9.0 Period of Performance

One year with two optional years.

1 April 2016 – 31 March 2017 (Base Year)

1 April 2017 – 31 March 2018 (Option Year 1)

1 April 2018 – 31 March 2019 (Option Year 2)

10.0 Manpower Reporting Requirement

The contractor shall report ALL contractor labor hours, by CLIN, (including subcontractor labor hours) required for performance of services provided under this contract for DSCA via secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year

(FY), which runs October 1 through September 30. While inputs may be reported anytime during FY, all data shall be reported no later than October 31 of each calendar year. Contractor may direct question to the help desk at http://www.ecmra.mil/.

11.0 Payment Information

Invoicing Instructions: Requests for payments must be submitted electronically via the Internet through the Wide

Area Workflow – Receipt and Acceptance (WAWF-RA) system at https://wawf.eb.mil. All contractors must create two documents (Invoice and Receiving Report; i.e. Combo Documents) with a single-data entry session.

12.0 Contract Type

This contract is a hybrid type contact with Firm Fixed Price (FFP) CLINs and Cost-Reimbursement (Cost) CLIN.

http://www.ecmra.mil/ http://www.ecmra.mil/ https://wawf.eb.mil/

13.0 Measures, Standards and Objectives

See Attachment 04.

INSTRUCTIONS TO OFFERORS

1. Instructions to Offerors

1.1 Proposal Submission

1.1.1 Offerors shall submit the proposal in three (3) volumes.

a. Volume I: Technical Expertise

b. Volume II: Past Performance

c. Volume III: Price

1.1.2. Offerors shall submit five (5) hard copy versions of their proposal. Four (4) of the copies shall have the offeror’s name and any other identifiers redacted or removed.

1.1.3. Text shall be single-spaced, on 8½” x 11” paper (except as specifically noted), with a minimum one-inch margin all around. Pages shall be numbered consecutively. A page printed on both sides shall be counted as two pages. Submission as double-sided printing/copying on recycled paper is encouraged. Offerors may use 11” x 17” sized fold-out pages for tables, charts, graphs, or pictures that cannot be legibly presented on 8½” x 11” paper. An 11” x 17” is a two-sheet equivalent (with regards to the page count limitations). Print shall be of a minimum 12-point font size or a maximum 10 characters per inch spacing. Bolding, underlining, and italics may be used to identify topic demarcations or points of emphasis. Graphic presentations, including tables, while not subject to the same font size and spacing requirements, shall have spacing and text that is easily readable.

1.1.4 Each volume in the proposal shall include a copy of the cover letter (letter of transmittal), title page and table of contents. The table of contents shall list sections, subsections and page numbers. Each volume shall contain a glossary of all abbreviations and acronyms used. Each acronym used shall be spelled out in the text the first time it appears in each proposal volume.

1.1.5. In addition to the paper copies identified above, the offeror shall submit all proposal information in electronic format on a CD. Text and graphics portions of the electronic copies shall be in a format readable by Microsoft (MS) Word 2000. Data submitted in spreadsheet format shall be readable by MS Excel 2000. Oral presentation (if conducted) material shall be readable by MS Office 2000 or MS PowerPoint 2000. In case of conflict between the paper copy and the electronic copy of the proposals submitted, the paper copy shall take precedence.

1.1.6. Restriction of Disclosure/Proprietary Information. If the offeror wishes to restrict the disclosure or use of its proposal, use the legend permitted by FAR 52.215-1(e). Individual subcontractor/vendor proprietary information may be submitted via separate binders/CDs. The information contained in these binders/CDs must be referenced (by binder title, page and section number as appropriate) within the main proposal where the information would have been included if it were not subcontractor/vendor proprietary. The information in these separate binders/CDs is subject to all other requirements of the RFP and must be well-marked to clearly indicate any special handling instructions.

1.1.7. Cross Referencing. Each volume, other than the Cost volume, shall be written to the greatest extent possible on a stand-alone basis so that its content may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

Hyperlinking of cross-references is permissible. Information required for proposal evaluation, which is not found in its designated volume or cross-referenced, is assumed omitted from the proposal.

1.1.8 Period for acceptance of offers. The Offeror agrees to hold firm the prices in its offer for

120 calendar days from the date specified for receipt of offers.

1.1.9 Acknowledgement of Solicitation Amendments. Should amendments be issued against this solicitation, the Offeror shall acknowledge by signing the Standard Form (SF) 30 entitled

Amendment of Solicitation/Modification of Contract and include it in the proposal submission.

1.1.10 Offerors shall submit questions no later than, 12:00 pm, EST, on 24 February 2016.

Offerors shall submit the questions and comments via email to Woodrow Bell at woodrow.w.bell.civ@mail.mil.

1.2. Volume I: Technical Expertise

1.2.1. Offerors shall submit a technical proposal of no more than forty (40) pages. The offeror shall include any assumptions and constraints to achieving PWS objectives within this 40 page limit. Proposal contents that exceed the stated page limitations will be removed from the proposal by the Contracting Officer, prior to turning the proposal over to the Government evaluation teams, and will not be considered in the evaluation. This volume shall be sufficiently specific, detailed, and complete as to demonstrate clearly and fully that the Offeror has a thorough understanding and knowledge of the complexities inherent in the performance of this requirement. Statements that the Offeror understands, can, or will perform the listed functions without supporting information or narratives are inadequate. Paraphrasing the PWS or parts thereof, is similarly inadequate, as are phrases such as “standard procedures will be employed” or “well-known” techniques will be used.” This volume shall be written such as to enable evaluators to make a thorough evaluation as to whether the services proposed adequately respond to the specific Government requirements. (Notice: The Government reserves the right to reject any proposals that include any assumptions or conditions that impacts or affects the

Government’s requirements.)

1.2.2 Sub-Factor A – Capability and Understanding to Conduct the Work:

1.2.2.a. Offeror shall submit an approach that details how the offeror will address all the requirements of the PWS. The offeror shall identify the methodology and analytical techniques that shall be used to fulfill the technical requirements. The technical approach should clearly describe the following:

(i) An overview of the methodology guiding performance of the technical requirements identified in the PWS, and a general description of how the technical approach will be applied in accomplishing the requirements. The offeror shall demonstrate the following technical proficiency:

(1) Providing explanatory guidance to Security Cooperation Organizations (SCOs), Combatant Commands, military departments, other U.S.G. elements, and industry members responsible for interacting and providing input for the outlined tasks.

(2) Researching historical policy and reports based on questions from a variety of sources within DoD and the State Department and assembling the resulting research into a comprehensive technically complete response.

(3) Demonstrating knowledge of and ability to differentiate among the linkage of legislation, regulation, and policy in accomplishing technical requirements.

(4) Preparing briefing charts and other electronic presentations or ability to take and shape draft briefing charts into a clean final product as envisioned by the

Action Officer or Director/Deputy Director concerned.

(ii) The logical sequence of tasks that will be performed to accomplish the requirements.

Identify and describe the specific techniques and steps that will be applied during the accomplishment of all tasks of this project.

1.2.2.b. Offeror shall provide sample outputs from earlier programs or projects or outputs formulated for the achievement of this solicitation task. At a minimum, the outputs will be comprised of:

-Sample user guide pages (2 pages total)

-Training materials/slides (2 pages total)

-Web page screen capture (1 page total)

-Newsletter (1 page total)

1.2.2.c. Offeror shall address how the offeror intends to meet the qualifications identified in the

PWS, and should also identify those areas the offeror sees as critical to the customers for this contract

1.2.3 Sub-Factor B – Management Approach of overall project management:

1.2.3.a. The Offeror shall address how the team will use this approach in monitoring and adjusting project performance and mitigating risks.

1.2.3.b. The Offeror shall address the internal processes and tools in order to effectively manage technical performance, risk, and milestone scheduling for future projects. Proposed internal processes and tools will be evaluated for feasibility and potential for technical benefits or schedule efficiencies to the Government.

1.2.4 Sub-Factor C – Staffing Plan and Key Personnel required qualifications:

1.2.4.a. Offeror shall submit approach to recruit and hire qualified and knowledgeable subject matter experts and personnel to accomplish PWS requirements.

1.2.4.b. Offeror shall submit resumes for all proposed personnel. If proposing personnel that are currently performing services and the offeror is not the applicable incumbent, the offeror shall provide proof of the employees consent for the offeror to propose his/her services.