PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

Washington Headquarters Services / Acquisition Directorate

In Support of Defense Security Cooperation Agency (DSCA)

Global Execution (GEX) Golden Sentry Inventory Reporting (GSIR) End Use Monitoring (EUM) Scanner Project

January 07, 2025

PART 1

GENERAL INFORMATION

1. GENERAL: This is a non-personal services contract to provide the Defense Security Cooperation Agency’s (DSCA) Golden Sentry End-Use Monitoring (EUM) Scanner Project with both programmatic and information technology activities. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform the Golden Sentry Inventory Reporting (GSIR) End Use Monitoring (EUM) Scanner Project as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

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

In 1996, Congress enacted section 40A of the Arms Export Control Act (AECA) [22 U.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 Defense Security Cooperation University (DSCU) resident and online courses.

Population of the database continues to be ongoing and challenging due to the quantity and various manufactures of Defense Articles. Regarding the data, DSCA is working with military departments to continue the baseline of all identified Enhanced EUM (EEUM) articles. Effort is underway to improve automation of database population.

The Security Cooperation Information Portal (SCIP) is a web-based system housing a family of applications. The two major current areas of functionality involve Foreign Military Sales (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/ .

https://www.scportal.us/home/

The Golden Sentry Inventory Reporting (GSIP) program is intended to use licensed commercial off the shelf software (COTS) installed on DoDIN Approved Items List scanners, to collect defense article inventory data at the serial number level through barcode scanning, securely share it with an aggregation application on SCIP, update the EUM database either manually or automatically, and use the COTS license owner to manage changes to the software that improve functionality, efficiency, accuracy, and security. GSIR will increase the volume, accuracy, and timeliness of EUM inventory reporting either in a benign environment by US Government (USG) personnel or in hostile environments by trusted country personnel.

1.3 Objectives: The Golden Sentry Inventory Reporting (GSIR) program has four (4) major objectives:

• GSIR Applications Enhancements and Sustainment

• GSIR Customer Support

• GSIR Program Analysis

• GSIR Integration

1.4 Scope: The scope consists of the following areas of support: GSIR Applications Enhancements and Sustainment (5.2.1), GSIR Customer Support (5.2.2), GSIR Program Analysis (5.2.3), GSIR Integration (5.2.4).

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

1.5 Period of Performance: The period of performance shall be for one (1) Base Year of 12 months and two (2) 12-month option years and an optional 6-month extension. The Period of Performance reads as follows:

Base Year: 29 April 2025 – 28 April 2026 Option Year I: 29 April 2026 – 28 April 2027 Option Year II: 29 April 2027 – 28 April 2028 52.217-8 Extension: 29 April 2028 – 29 October 2028

1.6 General Information:

1.6.1 Quality Control: The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program (QCP) is how they assures themselves that the work complies with the requirement of the contract. The QCP is to be delivered within 15 days after contract award. A copy shall be submitted to the KO and COR within five (5) working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to the Quality Control (QC) system.

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

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.2.1 Identification of Non-Disclosure Requirements: The activities in this PWS will require the Contractor to receive Government Furnished Information (GFI), and access data and information proprietary to other Contractors or Government agencies of such a nature that its dissemination or use, other than in performance of this PWS, would be averse to the interests of the Government and others. The Contractor, including Contractor personnel, subcontractors, and consultants, will not divulge or release data or information developed or obtained in performance of this PWS except to Government authorized personnel or upon written approval of the CO or COR.

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

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

New Year’s Day, January 1.

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

President’s Day, the third Monday in February.

Memorial Day, the last Monday in May.

Juneteenth National Independence Day, June 19.

Independence Day, July 4.

Labor Day, the first Monday in September.

Columbus Day, the second Monday in October.

Veterans Day, November 11.

Thanksgiving Day, the fourth Thursday in November.

Christmas Day, December 25.

1.6.4 Hours of Operation: The Contractor is responsible for conducting business between the hours of 0800 – 1630 Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The contractor shall accommodate availably as required for supporting global operations. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor shall always maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5 Place of Performance: The work to be performed under this contract will be executed at the Contractor’s facility.

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

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

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

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

1.6.6 Type of Contract: The government will award a Firm-Fixed-Price contract.

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

The Contractor shall have a current facility clearance of SECRET at the time of proposal to work this effort. All personnel assigned to this contract must be U.S. citizens. Additional security requirements in Technical Exhibit 5.

1.6.8 Special Qualifications: Within ten (10) business days of award of this contract or ten (10) days of employment, the Contractor shall ensure that all Contractor employees complete annual Government- furnished training in Information Assurance, Privacy Act, Operational Security, and other assigned training required. Any Contractor behavior deviating from standards taught in the course shall be grounds for termination of the contract. Contractor must maintain a cyber-threat security awareness certification plan.

The Contractor is expected to provide a fully trained workforce to the Government; therefore, personal development training costs and hours are not billable to the Government. The following key position have been identified: Senior Analyst (Subject Matter Expert).

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

1.6.9 Post Award Contractor/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings, the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced.

Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.10 Contracting Officer Representative (COR): Refer to DFARS Clause 252.201-7000 “Contracting Officer’s Representative”.

1.6.11 Contract Personnel:

1.6.11.1 Key Personnel: The personnel listed below are considered essential to the work being performed under this contract. Before removing, replacing, or diverting any of the listed or specified personnel or facilities, the Contractor shall (1) notify the Contracting Officer reasonably in advance and (2) submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this contract. The Contractor shall make no diversion without the Contracting Officer's written consent. Please see the below chart for the one (1) key personnel position.

1.6.11.1.1 Key Personnel Minimum Qualifications

SUPPORT TASK POSITION QUALIFICATIONS

Section 5.1, 5.2, 5.3, 5.4, 5.5, 5.6

Senior Analyst SME

Minimum qualifications:

• Baccalaureate’s degree from an accredited college and 15 years of relevant experience or an advanced degree may be used with 10 years of experience.

• Minimum 5 years’ experience supporting FMS or other security cooperation programs, and supply change management.

• 5 years’ experience with tasks like those identified in PWS.

• 10 years’ experience supporting IT tools focused on asset visibility.

• 15 years’ experience supporting FMS or other security cooperation programs focused on asset visibility and transportation.

• 15 years’ experience in supply chain management.

• 15 years’ experience in supply chain management.

• Secret Security Clearance

1.6.12 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed. All Contractor personnel will be required to obtain, use, and display a CAC throughout the performance of this requirement.

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

1.6.14 Travel Reports: The Contractor will submit a monthly travel report that includes all travel costs incurred by the Contractor, in addition to invoicing requirements. The report shall be formatted to provide a breakout of costs for the current period to date and the total amount expended to include the remaining balance on the Travel CLIN.

This format allows accurate tracking and provides effective insight into declining funds availability.

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

1.6.16 Other Direct Costs: Other Direct Costs (ODCs) may include require reproduction and shipping expenses associated with training activities, visits to contractor facilities, suitable training venues as needed, and equipment.

The procurement of devices for scanning or printing including accessories and consumables; application licenses;

device support agreements, 3rd party software licenses; miscellaneous charges for device shipment costs, and any other approved direct charge associated with the GSIR objectives.

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

1.6.18 Organizational Conflict of Interest (OCI): Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications, or work statements, etc.) or perform evaluation services which may create a current or subsequent OCIs as defined in FAR Subpart 9.5.

The contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the contractor from participation in subsequent contracted requirements which may be affected by the OCI.

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

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

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

2.1.2. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

2.1.3. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

2.1.4. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.5. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

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

2.1.7. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.8. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

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

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

2.1.11. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.12. SUBCONTRACTOR. One that enters into a contract with a prime Contractor. The Government does not have privity of contract with the subcontractor.

2.1.13. WORKDAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.12. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2. ACRONYMS:

ANACI Access National Agency Check and Inquiries AVS Adjudication and Vetting Services CAC Common Access Card CFR Code of Federal Regulations CIS Center for Internet Security CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTs Commercial off the Shelf Software CUI Controlled Unclassified Information DD254 Department of Defense Contract Security Requirement List DevSecOps Development, Security, and Operations DFARS Defense Federal Acquisition Regulation Supplement DISS Defense Information System for Security DOD Department of Defense DOD CAF DOD Consolidated Adjudication Facility DODI Department of Defense Instructions DSCA Defense Security Cooperation Agency DSCU Defense Security Cooperation University EUM End Use Monitoring FAA Foreign Assistance Act FAR Federal Acquisition Regulation FFP Firm Fixed Price FOIA Freedom of Information Act FMS Foreign Military Sales FSO Facility Security Officer GFI Government Furnished Information GFS Government Furnished Software GSIR Golden Sentry Inventory Reporting HQ Headquarters IM&T Information Management and Technology ISL Industrial Security Letter ISSM Information Systems Security Manager ITP Insider Threat Program JTR Joint Travel Regulation KO Contracting Officer MIM Machine Identity Management NDA Non-Disclosure Agreement NIPR Non-classified Internet Protocol Router Network NISPOM National Industrial Security Program Operating Manual NIST National Institute of Standards and Technology NTE Not to Exceed OBO Office of Business Operations OCI Organizational Conflict of Interest OCONUS Outside of the Continental United States ODC Other Direct Cost OPSEC Operation Security PO Product Owner PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control

QCP Quality Control Program RMF Risk Management Framework SC Security Cooperation SCIP Security Cooperation Information Portal SecOps Security Operations SME Subject Matter Expert SOP Standard Operating Procedures STIG Secure Technical Implementation Guidance TE Technical Exhibit VAR Visitor Authorization Request VPN Virtual Private Network WHS Washington Headquarters Services

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services: The Government will provide access to DSCA.

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

3.3. Utilities: The Government will provide all utilities in the facility available for the Contractor’s use in performance of tasks outlined in this PWS.

3.4. Equipment: The Government will provide the Contractor access to scanners, fax machines, printers, computers, audio visual, and other equipment.

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

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The Contractor shall furnish all supplies, equipment, facilities, and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2 Secret Facility Clearance: The contractor shall possess and maintain a SECRET facility clearance from Defense Counterintelligence and Security Agency (DCSA) at quote submission. The contractor shall hold and maintain the level of facility clearance for the life of the contract. Contractor personnel performing work under this contract shall have and maintain a fully adjudicated Secret clearance for the life of the contract. The DD Form 254 is provided as an attachment.

PART 5

SPECIFIC TASKS

5. Specific Tasks:

5.1. Basic Services: The contractor shall provide services for GSIR EUM Scanner Special Project.

5.1.1 Project Management: The Contractor shall prepare and update, as requested, project management documentation for efforts designated by DSCA IM&T as projects to be tracked and reported no less than once a month. Project management documentation shall include the following:

5.1.1.1 The contractor shall participate in PWS related management meetings, Ad-Hoc meetings, technical working groups, technical interchange meetings, and program management reviews, and shall support technical requirements review meetings throughout the period of performance in support of GSIR activities.

5.1.1.2 Examples include non-recurring and recurring (on a daily, weekly, or monthly basis), stand-up meetings, leadership meetings, project and technical status briefings, requirements reviews, technical exchanges meetings with internal and external organizations, recurring briefings to Government leadership, and other briefings and meeting support as required.

5.2. Task 1 GSIR Applications Enhancements and Sustainment. The Contractor shall provide GSIR requirements development, programming, software integration, communications design, and application interface development, to improve scanning capacity, capability, and security of the GSIR program on SCIP. Perform all development, programming, functional and compliance testing, associated with GSIR expansion and sustainment of GSIR functionality. Work in collaboration with other SCIP and DSCA applications as required to establish manual and automated application program interfaces (API) for the transfer of data between and among GSIR and other SCIP and DSCA applications. Generate performance monitoring tools for both the device application and inventory results. The support shall include the following:

5.2.1 Properly safeguard Government Furnished Equipment and Software provided by DSCA.

5.2.2 Modify existing GSIR commercial applications, Commercial Off the Shelf (COTS) software HawkTrack TM and HawkScan TM, to comply with requirements of the Security Cooperation Information Portal (SCIP) environment and authority to operate. For initial transition to the GSIR SCIP environment, modifications are limited to those necessary to comply with SCIP cyber security and infrastructure requirements.

5.2.3 Collect, evaluate, research, articulate, and propose functional solutions to fielding program functionality including cost, benefit, and priority.

5.2.4 Identify software solutions that improve program stability, efficiency, accuracy, sustainability, and compliance.

5.2.5 Use Jira to manage the development associated new, improved, or correction of with GSIR.

5.2.6 Maintain a list of all collected requirements associated with GSIR as a backlog report and schedule of program enhancements.

5.2.7 Establish, track, and resolve bugs and helpdesk issues in Jira.

5.2.8 Summarize all releases with release notes describing fixes or improved functionality. Provide release notes to Customer Support so it can be posted on the SCIP website.

5.2.9 Accommodate and integrate various multifactor authentication techniques into GSIR for secure access, operation, data transfer, and update.

5.2.10 Identify and address all critical Security Technical Implementation Guide (STIG) issues. Identify and schedule mediation of all non-critical STIG issues.

5.2.11 Establish a QA environment that includes testing of both device application and web application interaction, e.g., log on, profile update, data transfer, etc.

5.2.12 Establish test data, standard test processes, standard test sequences, validation of proper device configuration, and record actionable test results in a test data repository to maintain a history of testing effectiveness.

5.2.13 Add government warning and EULA to both device and website landing page.

5.2.14 Government Warning will be persistent (every sign on).

5.2.15 EULA will be periodic. User acceptance once for each new release and a minimum of once annually.

5.2.16 Link all transactions to specific users and devices using Machine Identity Management (MIM) identification.

5.2.17 Expanded barcode parsing that addresses the most common constructs of Unique Item Identifier (UII) in use for EUM defense articles. Where possible, parse non-UII barcode labels that contain a UII or serial number (SN).

Recognize, parse, and extract properly formatted labels containing multiple UII/SN from a single barcode and establish an inventory transaction for each.

5.2.18 Include user ability to provide receipt and initial inventory reporting.

5.2.19 Establish two GSIR production environments in SCIP one for users to report inventories and one for training and familiarization.

5.2.20 Program GSIR to prepare inventory data for upload with a minimum or manual intervention and a maximum of automation

5.2.21 Program delivery of software updates in an automated and secure manner minimizing user involvement.

Record software updates automatically and associated with the specific device identity using MIM.

5.2.22 Identify and implement methods to protect or recognize and report tampering with the application or data in devices…End Point Detection. Establish tamper evident triggers that shut down the device until issue is resolved and the device is reset with proper user validation.

5.2.23 Program secure remote access to trouble shoot devices and remotely reconfigure devices.

5.2.24 Program devices to eliminate all unnecessary applications and limit access to device configuration with differing user and administrative controls on device configuration.

5.2.25 Implement cyber security features to protect data at rest in the deployed device, inventory data residing in the device, the device software.

5.2.26 Implement secure communications for data in transit from the device to GSIR SCIP.

5.2.27 Determine feasibility of integrating virtual private networks (VPN) and other secure use of internet browser.

5.2.28 In collaboration with EUM SCIP personnel, establish Application Program Interface (API) with SCIP EUM to download and upload data between or among scanning devices, GSIR SCIP and EUM SCIP.

5.2.29 Establish methods to securely access and download inventory data from EUM SCIP, import it into the device, format it in the device to enable rapid access and match with scanned information, formatting matched scanned results into a format that can be uploaded manually or automatically.

5.2.30 Develop the most reliable and efficient methods of rapidly matching scanned item to database in device.

5.2.31 Coordinate proper GSIR data formatting with EUM SCIP team to comply with EUM SCIP update characteristics and format.

5.2.32 Assess inventory data for proper reporting including scanned frequency, multiple scans in same location, multiple scans in different locations, unmatched scans (new or non-us source), multiple scans from different users, multiple scans from same user, scans matching inactive items, etc.

5.2.33 Identify methods to incorporate controlled tamper evident seals containing either single or multiple UII/SN or links to UII/SN to collect data from sealed containers.

5.2.34 Program performance feedback in the scanner for in-process and complete status.

5.2.35 Prevent users from losing any scanned data due to unplanned exit from the program, device shutdown, or loss if connectivity. In-process inventory data will be able to be resumed when device is restored.

5.2.36 Notify users of in-process inventories that require completion.

5.2.37 Upon request from DSCA EUM Program Office, collaborate with owners of other USG databases to establish an API with GSIR SCIP.

5.2.38 Use third party software to expand GSIR SCIP features for improved security, functionality, or performance, i.e., CAC reader and software, performance software for device app, etc.

5.2.39 Establish tools in GSIR SCIP to manage registration, assignment of roles and responsibilities, activate and suspend users, and maintain country tailored information management to for device application users.

5.2.40 Establish analysis of device performance that tracks application performance, reports crashes, and causes.

5.2.41 Develop capability to implement MIM to continuously monitor device identity, usage, configuration, using any of the various methods of uniquely identifying a device (IMEI: International Mobile Equipment Identity, MAC:

Machine Access Control Address, UDID: Unique Device Identifier, IP address: Internet Protocol address).

5.2.42 Properly document all software additions, deletions, and modifications.

5.3 Task 2 GSIR Customer Support: The Contractor shall provide customer support to GSIR customers e.g., GSIR operators, users, and managers of applications with a GSIR API. Provide device man GSIR Device Management Device procurement, preparation, inventory management, configuration management, and troubleshooting. The Contractor shall support the following tasks

5.3.1 Provide a point of contact to collaborate with the SCIP Helpdesk for customer issues with GSIR.

5.3.1.1 Integrate GSIR customer support contact and reporting with SCIP Helpdesk and comply with performance standards established by SCIP Helpdesk

5.3.1.2 Prepare standard Helpdesk tracking document: date/time, user, device, software configuration, contact information, problem, help sequence, resolution, date/time

5.3.1.3 Develop trouble shooting checklist.

5.3.1.4 Manage SCIP Helpdesk tasks using their ticket system or control numbers.

5.3.1.5 Retain statistics of customer requests (tickets), time to resolve, frequency of types of issues, and analysis for further requirement determination or programming.

5.3.1.6 Coordinate software bugs with development team. Triage responses as critical, serious, or routine.

5.3.1.7 Establish mandatory response times equal or better than SCIP Helpdesk standards.

5.3.1.8 Coordinate response to customers with SCIP Helpdesk to ensure accurate accountability, responsiveness, and efficiency.

5.3.1.9 Establish communication channels with user to notify them of system problems, planned downtime, unplanned downtime, and estimated time to restore access, alerts to changing program information, quick response tasking, helpful hints, etc.

5.3.1.10 Prepare training documents associated with each software release. Work with development team to make training documents available.

5.3.1.11 Use screenshots of software, PowerPoint, and Microsoft Word.

5.3.2 Translate as necessary using google translate or SCO resources.

5.3.2.1 Provide training examples of inventory process, software familiarization, and label/barcode recognition, contact information for assistance.

5.3.2.2 Order devices that are listed in DoDIN Approved Products List as funded by DSCA EUM Program Office

5.3.2.3 Prepare detailed device preparation/configuration/access setup and certification.

5.3.2.4 Prepare detailed software load instructions and certification.

5.3.2.5 Prepare detailed full functional testing and certification.

5.3.2.6 Prior to shipment, fully prep, load current software, and test device. Update MIM.

5.3.2.7 Maintain online inventory records of devices and accessories. Record: receipt by SN/MIM/IMEI/MAC/UDID/IP address, documented device prep, installed software, test software using standard procedure, shipment, acknowledged receipt by accountable custodian or user, trouble ticket history.

5.3.2.8 Ship devices, using DSCA authorized shipment account and shipment office, to authorized government addresses, MAPACs or DODAACs.

5.3.2.9 Manage return, tracking, and receipt reporting for devices returned for repair or reallocation.

5.4 Task 3 GSIR Program Analysis: The Contractor shall monitor and report performance, provide process improvement analysis and recommendations, assist DSCA EUM Program Office in policy development and expansion of the GSIR. The Contractor shall:

5.4.1 Participate in meetings associated with GSIR, in transit visibility of EUM, and EUM initial and annual reporting techniques for inclusion in GSIR.

5.4.2 Conduct research of issues encountered in the field affecting GSIR accuracy/effectiveness.

5.4.3 Conduct research, in accordance with the priorities of the End-Use Monitoring (EUM) Contracting Officer’s Representative (COR), of military departments, major commands, program offices, and manufacturers’ data to properly identify and locate label for GSIR.

5.4.4 Conduct process improvement reviews of GSIR process and procedures, including factors external to GSIR that affect GSIR effectiveness, e.g., opportunities to reduce effort associated with inventorying containers with multiple defense articles requiring inventory.

5.4.5 Review performance data collected monthly and provide observations of interest

5.4.6 Prepare monthly reports associated with GSIR, deployed scanner inventory, transaction analysis, customer support events and performance, software development progress, performance to timelines, and any other event of significance impacting GSIR.

5.4.7 Review and assess requirement priority and scheduling.

5.4.8 Provide guidance to development team as required to assist in software functionality.

5.4.9 At the request of DSCA EUM Program Office, research and provide recommendations for initiatives ancillary to GSIR

5.5 Task 4 GSIR Integration: The Contractor shall provide integration and support associated with ancillary initiatives that leverage GSIR capabilities to improve GSIR inventory performance and leverage GSIR functionality to solve related issues. The Contractor shall:

5.5.1 The Contractor shall be responsible the DSCA EUM Program Officer will require review and recommendations of initiatives that are ancillary to GSIR either to leverage GSIR capability to solve similar issues, uses GSIR capability to augment a desired initiative, or integrate an ancillary initiative with GSIR policy, procedure, or functionality. An example application of unique barcode labeling to EUM items that is integrated with GSIR SCIP and EUM SCIP.

5.5.2 Recommendations can be technical, policy, procedure, facilities, or equipment related.

5.5.3 GSIR can be tasked and funded with supporting or assuming responsibility for ancillary initiatives, as part of the GSIR program. for all development, deployment, and release activities such as release notes, development, testing, troubleshooting, and deployment activities across all instances and deliver capabilities to internal customers, external customers, and mission partners.

PART 6

APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS (CURRENT EDITIONS)

6.1. The Contractor must abide by all applicable regulations, publications, manuals, and local policies and procedures:

• https://www.whs.mil/COVID-19

• https://comptroller.defense.gov/Portals/45/documents/fmr/current/10/10_12.pdf

• https://www.ecfr.gov/current/title-5/chapter-XVI/subchapter-B/part-2635/subpart-H/section- 2635.807

• https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-A/part-73/subpart-G/section-73.735-701

• https://www.acquisition.gov/far/part-35

• Security Assistance Management Manual (SAMM): https://www.samm.dsca.mil/chapter/chapter-8

• SCIP-EUM Handbook Part 7 https://www.whs.mil/COVID-19 https://comptroller.defense.gov/Portals/45/documents/fmr/current/10/10_12.pdf https://www.ecfr.gov/current/title-5/chapter-XVI/subchapter-B/part-2635/subpart-H/section-https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-A/part-73/subpart-G/section-73.735-https://www.acquisition.gov/far/part-35 http://www.samm.dsca.mil/chapter/chapter-8 http://www.samm.dsca.mil/chapter/chapter-8 http://www.samm.dsca.mil/chapter/chapter-8 http://www.samm.dsca.mil/chapter/chapter-8

PART 7

ATTACHMENT/TECHNICAL EXHIBIT LISTING

7. Attachment/Technical Exhibit List:

7.1. Attachment 1/Technical Exhibit 1 – Performance Requirements Summary

7.2. Attachment 2/Technical Exhibit 2 – Deliverables Schedule

7.3. Attachment 3/Technical Exhibit 3 – Estimated Workload Data

7.4. Attachment 4/Technical Exhibit 4 – Projected Level of Effort

7.5. Attachment 5/Technical Exhibit 5 – Security Requirements

TECHNICAL EXHIBIT 1

Performance Requirements Summary

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objective (The Service required usually a shall statement)

Performance Standards

Performance Threshold

Method of Surveillance

PRS# 1. Provide support personnel to meet PWS requirements.

Para 1.1; 1.6.2.1; 1.6.4;

1.6.7; 1.6.11

All Contractor personnel possess the skills needed to perform the required tasks as specified in the PWS.

All Contractor personnel possess the needed skills needed to perform services for this PWS.

The Contractor's work products are suitable to support the full range of analysis as specified in the PWS.

The Contractor's personnel are qualified and adept with IT development and sustainment activities while supporting the DoD.

100% Inspection by the Government

PRS #2 Provide and retain qualified key personnel and maintain a stable workforce.

Para: 1.6.11

Key personnel possess qualifications, certifications and experience as identified in the Staffing Plan

Performance is acceptable when: Qualified key personnel are on the job at contract start, unless previously negotiated by the KO.

Vacancies are filled with qualified key personnel within ten (10) business days of vacancy unless approved in writing or otherwise directed in advance by the KO AND There is no mission impact due to position vacancies or unqualified personnel.

90% / 20 business days – Satisfactory

95% / 15 business days– Very Good

100% / 10 business days – Excellent

100% Inspection by the Government

PRS#3 Submit a monthly status report on last business day of the month and as requested.

Para: 5.1

The Status Report accurately reflects progress, status;

proactively identifies and addresses any problems or issues encountered; and recommended resolutions are feasible and likely to succeed in resolving issues.

Report is submitted on the last business day of the month.

Reports are grammatically correct and professional in appearance.

Draft documents contain minor typographical errors; Final documents are error free

100% Inspection by the Government

PRS#4 Hours of Work/Workload Management

Para 1.6.4

The Contractor shall ensure its personnel accomplish the assigned tasks within agreed upon schedules, and at an acceptable level of quality.

The Contractor ensures that sufficient staff is available during core business hours to proactively interact with clients and complete the requirements specified in the PWS. Contractor also ensures the COR is informed of developments with assigned actions.

100% Inspection by the Government

TECHNICAL EXHIBIT 2

DELIVERABLES SCHEDULE

PWS

SECTION

DELIVERABLE TITLE FREQUENCY # OF

COPIES

MEDIUM/

FORMAT

SUBMIT TO

1.6.1 Quality Control Plan 30 days after award 3 MS Word COR and KO

1.6.8 Annual Training 10 days following

award 3 System Format COR

1.6.19 Transition In Plan At Project Kick-Off

Meeting 3 Presentation, PowerPoint, prior to meeting via email

COR, KO, Gov’t

POC

5.1 Monthly Status Report (MSR) & Meeting

Minutes

Last business day of the month. 3 PowerPoint, prior to meeting via email

COR, Gov’t

POC

1.6.9 Project Kick-off Agenda

3 days prior to Project Kick-Off Meeting 3 PDF, prior to meeting via email COR, KO, Gov’t

POC

5.1 Briefing/Presentation Materials, Reports, and Plans

As required 3 MS Word, Excel, Project, etc.

COR, Gov’t

POC

1.6.9 5.1, 5.2, 5.3

Meeting Minutes / After Action Reports (AARs) (includes Project Kick-Off Meeting Minutes)

5 days after the meeting or event

3 PDF, via email COR, Gov’t

POC

5.2.12 Test and Analysis of Findings and Reports As directed 3 Electronic. Gov’t POC

5.2 Establish manual and automated application

program interfaces (API) for the transfer of data between and among GSIR and other SCIP and DSCA applications

As directed 3 Electronic. Gov’t POC

5.2 Generate performance monitoring tools for

both the device application and inventory results

As Directed 3 PO specified Format

COR and Gov’t

POC

5.2.3 Financial Solutions including Cost, benefit, and priority

As directed 3 Electronic. As required

5.2.20 Prepare inventory data for upload with a

minimum or manual intervention and a maximum of automation.

As needed 3 GSIR Gov’t POC

5.5 Provide documentation to DSCA IM&T

DevSecOps for modernization and optimization

As needed 3 PO specified Format

Gov’t POC

5.2.6 Backlog report and schedule of program

enhancements

Continuous 3 PO specified Format

Gov’t POC

5.3.1.2 Helpdesk tracking document As directed 3 PO specified Format

Gov’t POC

5.3.1.10 Prepare training documents associated with

each software release.

As needed 3 PO specified Format

Gov’t POC

5.4.6 Prepare monthly reports associated with

GSIR

Monthly 3 PO specified Format

Gov’t POC

1.6.2.1 Non-Disclosure Agreement Within 1 day of

onboarding

3 System Format COR and KO

1.6.13;

1.6.14

Travel Reports As needed 3 MS Word COR

Limitations on Subcontracting FAR Clause 52.219-14

Conclusion of POP 3 Email electronically to the CO and

COR

COR and KO

TECHNICAL EXHIBIT 3

ESTIMATED WORKLOAD DATA

This is an estimated workload based on previous work completed for this task. The vendor should consider that this is a firm-fixed price contract and labor categories, and hours are at their discretion – with the exception of key-personnel positions.

Labor Category (FFP CLIN) Clearance Level

Supported Tasks Estimated

FTE

Senior Analyst (SME) - Key Personnel Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5 .5

Project Manager Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5 .5

Senior Lead Software Engineer

Secret PWS 5.2, 5.5 .75

Senior Software Engineer Secret PWS 5.1, 5.5 .75 Senior Network/Security Engineer Secret PWS 5.2, 5.5 .75 Senior Quality Assurance and Documentation Engineer

Secret PWS 5.1, 5.2, 5.5 .75

Mid-Grade Software Engineer Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5

.75

Junior Software Engineer Secret PWS 5.2, 5.3, 5.4 .75 Program Coordinator Secret PWS 5.2, 5.3, 5.4 .25

Option Year 1 Senior Analyst (SME) - Key Personnel Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5 1 Project Manager Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5 .75 Senior Lead Software Engineer

Secret PWS 5.2, 5.5 .75

Senior Software Engineer Secret PWS 5.1, 5.5 .75 Senior Network/Security Engineer Secret PWS 5.2, 5.5 .75 Senior Quality Assurance and Documentation Engineer

Secret PWS 5.1, 5.2, 5.5 .75

Mid-Grade Software Engineer Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5

.75

Junior Software Engineer Secret PWS 5.2, 5.3, 5.4 .75 Program Coordinator Secret PWS 5.2, 5.3, 5.4 .25

Option Year 2

Senior Analyst (SME) - Key Personnel Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5

.5

Project Manager Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5

Senior Lead Software Engineer

Secret PWS 5.2, 5.5 .5

Senior Software Engineer Secret PWS 5.1, 5.5 .5 Senior Network/Security Engineer Secret PWS 5.2, 5.5 .5 Senior Quality Assurance and Documentation Engineer

Secret PWS 5.1, 5.2, 5.5 .5

Mid-Grade Software Engineer Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5 .5

Junior Software Engineer Secret PWS 5.2, 5.3, 5.4 .5 Program Coordinator Secret PWS 5.2, 5.3, 5.4 .25

52.217-8 6 Month Extension Senior Analyst (SME) - Key Personnel Secret PWS 5.1, 5.2, 5.3,5.4, 5.5 .25

Project Manager Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5 .5 Senior Lead Software Engineer Secret PWS 5.2, 5.4 .25 Senior Software Engineer Secret PWS 5.1, 5.5 .25 Senior Network/Security Engineer Secret PWS 5.2, 5.5 .25 Senior Quality Assurance and Documentation Engineer

Secret PWS 5.1, 5.2,

5.5 .25

Mid-Grade Software Engineer Secret PWS 5.1, 5.2, 5.3, 5.4, 5.5 .25

Junior Software Engineer Secret PWS 5.2, 5.3, 5.4 .25 Program Coordinator Secret PWS 5.2, 5.3, 5.4 .125

TECHNICAL EXHIBIT 4

PROJECTED LEVEL OF EFFORT

Estimated level of effort to provide the vendor with a reasonable workload within a month.