SP7000-18-Q-0033_Attachment_1_-_WarehouseVision_PWS.pdf

Defense Logistics Agency Performance Work Statement

BAR CODE INTEGRATORS INC.

1. Background

DLA Distribution Corpus Christi, Texas in cooperation with DLA Distribution J3, Warehouse Team, identified a need for warehouse software system to provide enhanced slotting capability, improve visibility and utilization of storage areas, plan capital equipment and construction projects and support future stock positioning initiatives. Additionally, the software must be able to operate within the DLA information architecture which requires that any solution be Windows 10 compatible and in compliance with Chief Information Officer’s policy regarding Virtual Desktop Initiative (VDI) and Citrix. Only Bar Code Integrators’ WarehouseVision (WV) Software was deemed satisfactory after reviewing through the J6 Front Door process to fulfill DLA Distribution’s warehouse requirements and comply with the existing DLA IT architecture and policies.

2. Scope

The scope of work is to obtain BCI Professional Services to support installation, initial training and product troubleshooting for a pilot of this software at DLA Distribution Corpus Christi, Texas. BCI Professional Services support includes:

Implementation of WV Planner and Auditor Bundle Integration of WV with existing warehouse management system End-user Training for WV Planner and Auditor

The Contractor shall retain operational configuration and control of data repository systems used to process and store government data to include any or remote work. The Contractor shall not subcontract the operational configuration and control of any government data.

The project will be managed by the DLA Distribution Corpus Christi, Texas, who will coordinate all communication between affected parties. The Government is responsible for day-to-day operations of the infrastructure to include the hands on system administration of the equipment. The Government will maintain oversight of the environment.

3. Task Requirements

The vendor will be required to perform tasks such as the following:

Install WV applications on server and client PCs per network design to be determined o Vendor will coordinate with J64 and DISA to install software on DLA’s existing network, at a hosting site acceptable to DISA. Coordination should take place at first scheduled on-site meeting between vendor, end users, and J6 network technicians.

Assist in the loading of SQL tables in to SQL server Configure WV per DC requirements

Attachment 1 SP7000-18-Q-0033 o Vendor will work in conjunction with end user and database technicians to provide integration between WV Planner and Auditor and required data elements and tables in Warehouse Management System (WMS). Standard data will be resident in WMS. If end user is missing data elements, the end user will be responsible for data gathering. The vendor will show the end user how to measure correctly and advise on units of measure.

Complete set of base reports (A sample will be provided) Configure System Monitor Integration of WV with existing warehouse management system End-user Training for WV Planner and Auditor one week before Go-Live o In the WV Auditor module, end user should be able to run scenarios, run standard reports provided by the vendor, and create their own ad hoc reports.

o End users will become familiar with the WV Planner module.

o Vendor will provide any follow-on learning support on an ongoing basis.

3.1. Task 1- Project Management

The Contractor shall provide project management support the successful completion of the tasks within scope of this contract and successful test migration process to include:

Run migration (i.e., monitor) Validate objects (i.e., checking errors) Validate data (i.e., confirm number of rose) Adjust migration timings Remediate issues/bottlenecks

In addition, the contractor shall provide the following activities:

Planning and Resource Facilitation: Orientation and planning sessions conducted with government management and staff. The purpose of these meetings is to discuss the support services available, gather input regarding government support needs, and jointly plan government use of the support services.

o There will be 3 on-site meetings in Corpus Christi between the vendor, end user, and J6 technical support.

1st meeting at the beginning of the project: Vendor will gather info, validate data from WMS/EBS, and meet with end users to create slotting strategies.

2nd meeting, vendor will make a first attempt to create reports. This may be done virtually. The goal is to integrate the data.

3rd meeting, shortly before Go-Live, vendor will generate more physical moves and ensure functionality. Will need J6 support throughout.

Status Meetings and Reporting: A standard status report can be prepared twice monthly, to summarize the services delivered during the previous reporting period. Status meetings will be conducted to discuss support service activities, monitor government satisfaction levels, and discuss actions or adjustments that may be required. Customized reporting can be provided at government request. Customized reporting to include any SQL scripting code needed to create reports as requested by end users. Standard reports will be included during training. The status meeting will be coordinated with the DLA representatives no later than 14 days after award and will last approximately one hour.

Escalation Management: Support issues that require escalation to other resources within the contractor team and closely manage and expedite resolution.

Deliverables:

1. Project Plan and Schedule; due two (2) weeks upon contract award

3.2. Task 2 – Database Migration Preparation

The contractor shall provide database migration preparation plan and analysis within 10 business days after award.

The pre-migration analysis includes:

Rapid analysis of source and destination databases Identification and classification of all objects Identification of installed options Identification of complex objects/objects requiring special handling Identification of areas where features can be exploited e.g. compression, partitioning Identification of invalid objects

The configurable migration plan includes:

Creation of migration execution plan and tailored job scripts (object and data migration) Configurable object level migration options Configurable migration approach by Advanced Support Engineers e.g. feature usage, parallelism, etc.

3.2.1. Task 2.1 – BCI Preparation Support

The contractor shall provide preparation support of source and target servers and databases

3.2.2. Task 2.2 – BCI Preparation Support

The contractor shall provide preparation support of source and target servers. The contractor shall provide documentation review tasks in support of tasks identified in section 3.2

3.3. Task 3 – Audit Process

The contractor shall provide services for databases identified below.

Review of databases Review of WV Configuration Review of Reporting Review of System Monitor Configuration

3.4. Task 4 – Post Audit Steps

The contractor shall provide post-migration reporting that validates the successful migration and operation of the migrated objects and data within the databases.

3.5. Task 5 – Documentation

The contractor shall document and review database documentation and review one end-to end migration of each database. The contractor shall store and make available documentation in an approved DLA repository as deemed acceptable by the Government.

It is recommended the vendor make the report available to the customer and the customer post reports in the DLA repository which is accessible by all stakeholders

3.6. Task 6 – Completion Report

The contractor will submit a report documenting the hours expended and the completion rate of the activities within the scope of this document. This will be submitted to the COR/COTR by the last day of each month during this contract. A sample report will be provided.

4. Quality Assurance Surveillance Plan (QASP)

In fulfillment of this effort, the Contractor shall provide the deliverables identified in Section 3.

All deliverables shall be submitted to the Contracting Officer’s Representative (COR) / Contracting Officer’s Technical Representative (COTR) for acceptance unless otherwise directed by the Government.

Unless otherwise specified, the Government will review draft deliverables and provide comments back to the contractor or approve or disapprove the deliverable(s) within 30 days. The contractor will have a maximum of ten (10) working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government. All days identified are intended to be workdays unless otherwise specified.

The format for the individual deliverables will be determined through consultation between the COTR and the contractor. The QASP identifies the methods the government will use to measure performance of the service provider against the requirements and performance standards of the PWS. The QASP consists of guidelines for performance surveillance, evaluation, reporting, deficiency notification, and adjustments.

4.1. Performance Requirements Summary

The tasks the Contractor shall perform are defined in Section 3. All deliverables will be submitted to the COR/COTR for acceptance unless otherwise agreed upon.

The Government will make objective and subjective assessments of the contractor’s performance to determine whether contract performance is acceptable. The contractor is expected to perform all functions in a professional manner and prepare accurate and timely documentation. Progress will normally be tracked based on the milestone event when the contractor receives a specific tasking. Performance may vary with the complexity of the acquisition and/or technical document. It is expected that the documentation and procedures will comply with all major regulatory and process requirements and agency policies and procedures.

4.2. Method of Surveillance

The Government will ensure quality assurance and timeliness of all tasks via COR/COTR Inspections and Customer Feedback. The Government will inspect and evaluate performance of each completed task or deliverable required in the PWS.

4.2.1.1.Inspection and Acceptance Criteria

Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COR/COTR. All deliverables will be inspected for content, completeness, accuracy, legibility and conformance to contract requirements by the COR/COTR. At the discretion of the Government, inspection may include validation of information or software through the use of automated tools and/or testing of the deliverables, as specified in the PWS.

If the Government finds that a draft or final deliverable contains spelling errors, grammatical errors, improper format, or otherwise does not conform to the requirements stated within the task order PWS, the document may be immediately rejected without further review and returned to the Contractor for correction and re-submission. If the Contractor requires additional Government guidance to produce an acceptable draft, the Contractor shall arrange a meeting with the COR/COTR.

The basis for acceptance shall be compliance with the requirements set forth in this task order PWS, the Contractor's proposal and other terms and conditions of the contract. Deliverable items rejected shall be corrected in accordance with the applicable clauses. Reports and document deliverables will be accepted when all discrepancies, errors or other deficiencies identified in writing by the COR/COTR have been corrected to the Government’s satisfaction.

The Contractor shall provide electronic copies of deliverables. Electronic copies shall be delivered via e-mail attachment or other media by mutual agreement of the parties. The electronic copies shall be compatible with the current DLA Microsoft (MS) Office products or other applications as appropriate and mutually agreed to by the parties. The Contractor shall use best commercial practices for formatting deliverables under this contract. If the draft deliverable is adequate, the Government may accept the draft and provide comments for incorporation into the final version. All of the Government's comments to deliverables must either be incorporated in the succeeding version or the Contractor must demonstrate to the Government's satisfaction why such comments should not be incorporated.

4.3. General Acceptance Criteria

General quality measures, as set forth below, will be applied to each work product received from the contractor under the resultant task order. These performance measurements are defined as:

Quality

Accuracy – Work products shall be accurate in presentation, technical content, and adherence to accepted elements of style.

Clarity – Work products shall be clear and concise. Any/all diagrams shall be easy to understand and be relevant to the supporting narrative.

Consistency to Requirements – All work products must satisfy the requirements of this Performance Work Statement.

Format – Work products shall be submitted in hard copy (where applicable) and in media mutually agreed upon prior to submission. Hard copy formats shall follow any specified Directives or Manuals. All text and diagrammatic files shall be editable by the Government.

Timeliness

Work products shall be submitted on or before the due dates determined/specified between the task order COR/COTR and contractor or submitted in accordance with a later scheduled date determined by the Government.

4.3.1. Performance Review

Below are the Performance Standards that will be used in evaluating performance. These Performance Standards apply to the deliverables listed in Section 4.2 and to all performance under this task order PWS.

Overall Performance Ratings Satisfactory – Performance meets or exceeds contractual requirements. The contractual performance reflects some minor problem(s) for which corrective actions taken by the contractor appear or were satisfactory. Completion of all tasks in section 3.0 within the period of performance.

Fair – Performance does not meet some contractual requirements. The contractual performance reflects a minor problem(s) for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented. The minor performance problem(s) do not adversely impact the mission of the Agency. Completion of 9 tasks in section 3.0 within the period of performance.

Marginal – Performance does not meet some contractual requirements. The contractual performance reflects a serious problem(s) for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented. Completion of 8 tasks in section 3.0 within the period of performance.

Unsatisfactory – Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective. Completion of 7 tasks or less in section 3.0 within the period of performance.

Timeliness Satisfactory Meets or exceeds contractual requirements in terms of timeliness of delivery. The timeliness of contractual performance reflects some minor problem(s) for which corrective actions taken by the contractor appear or were satisfactory.

Fair Does not meet some contractual requirements in terms of timeliness of delivery. The timeliness of contractual performance reflects a minor timeliness problem(s) for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented. The minor timeliness problem(s) do not adversely impact the mission of the Agency.

Marginal Does not meet some contractual requirements in terms of timeliness of delivery. The timeliness of contractual performance reflects a serious problem(s) for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented.

Unsatisfactory Does not meet most contractual requirements in terms of timeliness of delivery and recovery is not likely in a timely manner. The timeliness of contractual performance contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

Quality Satisfactory Meets or exceeds contractual requirements in terms of quality of work performed. The quality of contractual performance reflects some minor problem(s) for which corrective actions taken by the contractor appear or were satisfactory.

Fair Does not meet some contractual requirements in terms of quality of work performed. The quality of contractual performance reflects a minor quality problem(s) for which the contractor has not yet identified corrective actions.

The contractor’s proposed actions appear only marginally effective or were not fully implemented. The minor quality problem(s) do not adversely impact the mission of the Agency.

Marginal Does not meet some contractual requirements in terms of quality. The quality of contractual performance reflects a serious problem(s) for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented.

Unsatisfactory Does not meet most contractual requirements in terms of quality and recovery is not likely in a timely manner. The quality of contractual performance contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

5. Deliverables

The Table below identifies the deliverables resulting from the tasks defined in Section 3.0 Task Requirements. All completed deliverables shall be forwarded to the COR/COTR. Contractor shall use best commercial practices for formatting all deliverables under this task order. Electronic copies of all deliverables shall be sent to the COTR via email in Microsoft Office compatible formats. If deliverable exceeds email size limitations, the deliverable shall be uploaded to the AMRDEC Safe site at https://safe.amrdec.army.mil/safe. A written monthly status report (in Word format) shall be delivered to the COR/COTR that includes information on problems, items to track, and a list of activities and deliverables completed during the preceding month via email to the COR/COTR. A sample will be provided.

TABLE 1: DELIVERABLES:

Table 1 identifies the Deliverables resulting from the tasks defined in Section 3.0

Deliverable Deliverable Reference #

Quantity: No.

of

Reports/Data Calls

Deliverable Due Date

Project Plan and Schedule 3.1 1 Soft Copy Two (2) weeks after contract award

Completion Report 3.6 1 Soft Copy Last day of each month

Quality Control Plan (QCP) 5.1 1 Soft Copy Within 10 business days of contract start date

TABLE 2: PERFORMANCE REQUIREMENTS:

Table 2 identifies the Performance Requirements resulting from the Deliverables in Table 1

Deliverable Title Deliverable Ref #

Surveillance Method and Performance Standards

Surveillance Schedule (Daily, Weekly, Monthly, Quarterly) Incentive

Project Plan and Schedule 3.1

100% COTR

Inspection Performance Standards - see Section 4.3.2 As needed

Timeliness and quality ratings to be assigned pursuant to section 5.1

Completion Report 3.6

100% COTR

Inspection Performance Standards - see Section 4.3.2 Monthly

Timeliness and quality ratings to be assigned pursuant to section 5.1

Quality Control Plan

(QCP) 5.1

100% COTR

Inspection Performance Standards - see Section 4.3.2 Weekly

Timeliness and quality ratings to be assigned pursuant to section 5.1

5.1. Contractor Quality Control Plan (QCP)

The contractor shall submit a QCP within 10-business days of contract start date to the COTR and Contracting Officer Representative (COR). This plan shall describe the contractor’s methodology of compliance with the Deliverables and Performance Requirements Summary outlined above. The COTR will notify the contractor of concurrence or required modifications to the QCP within 10 business days of receipt. The contractor shall make appropriate modifications within 5-business days of the COTR’s notification and provide a revised QCP within 5-business days.

6. Requirements

WV Planner and Auditor Bundle successfully implemented on DLA network WV Planner and Auditor Bundle successfully installed on end user computers All data successfully transferred/imported and accessible to end users All end users are proficient and self-sustained in using WV Planner and Auditor Bundle All end users are aware of how to troubleshoot and whom to consult for follow-on assistance All J6 personnel are aware of how to maintain interface All deliverables stated in Section _ are complete and submitted

The Contractor shall provide sufficient management to ensure that these tasks are performed efficiently, accurately, on time, and in compliance with the requirements of this document. Specifically, the Contractor shall designate a single manager to oversee these tasks and supervise staff assigned to these tasks. The Contractor shall ensure that a Monthly Progress Report is submitted outlining the expenditures, billings, progress, status, and any problems/ issues encountered in the performance of these tasks.

In order to ensure a smooth and orderly startup of this contract, it is essential that the key personnel specified in the Contractor's proposal be available on the effective start date of the contract.

The contractor is expected to minimize employee turnover with respect to personnel performing under this Performance Work Statement. The Contractor shall not remove or replace any personnel designated as "key" personnel, without the prior written notification and approval by the Contracting Officer, although the Government recognizes that the contractor cannot compel any individual to remain under its employ.

Written notification of the pending substitution shall be submitted to the Contracting Officer no later than (10) calendar days in advance of any proposed substitution and shall include a resume and justification of the proposed substitution(s) in sufficient detail to permit evaluation of the impact on contract performance. The Government will review the resume(s) and justification to ensure compliance with this clause and other requirements contained in this Performance Work Statement. Any replacement personnel proposed shall, at a minimum, be at least as qualified as the individual being replaced.

This contract is a “non-personal services contract” as defined in FAR 37.101. It is, therefore, understood and agreed that the contractor and/or the contractor’s employees:

(1) shall perform the services specified herein as independent contractors, not as employees of the Government; (2) shall be responsible for their own management and administration of work required and bear sole responsibility for complying with any and all technical, schedule, or financial requirements or constraints attendant to the performance of this contract; (3) shall be free from supervision or control by any Government employee with respect to the manner or method of performance of the services specified; but (4) shall, pursuant to the Government’s right and obligation to inspect, accept, or reject the work, comply with such general direction of the Contracting Officer, or the duly authorized representative of the Contracting Officer as is necessary to ensure accomplishment of the contract requirements.

The Contractor will not employ any person whose employment will violate the requirements of DOD5500.7, Joint Ethics Regulation.

All Contractor personnel shall observe local policy and procedures provided by the Office of Information Resources governing the use of computer equipment and passwords. Violations of local policy shall include password sharing, performing personal work, file access violations or browsing files outside the scope of the contract.

The Contracting Officer shall adjudicate each case and his/her decision shall be final.

Where the Government has requested removal of contractor personnel, the contractor will provide an appropriately trained replacement. Individuals removed from this task order are removed for the duration of the task order. The contractor will notify the COR/COTR within 24 hours when for reasons of personnel resignations, reassignments, terminations, or completion of portions of the task order, or contractor personnel no longer require access to Government computers.

Contractor personnel are only authorized to attend meetings, town halls, etc., as they relate to the performance of the tasks outlined in the PWS.

6.1. Minimum Requirements

The contractor must ensure all personnel are eligible for access to Department of Defense facilities in accordance with the authority in DoD Directive (DoDD) 5143.01 (Reference (a)) Directive Type Memorandum (DTM 09-012) which establishes DoD access control policy and the minimum DoD security standards for controlling entry to DoD installations and stand-alone facilities. Contractor personnel not eligible will not be acceptable for the tasks which require on-site location at the DLA facility.

6.2. Security

6.2.1. Access to Classified and Sensitive Information

This Project is categorized as “Unclassified”. The provisions listed below apply to the Awardee Contractor and any subcontractors the Awardee Contractor may employ during the course of this contract.

6.2.2. IT Level Investigation Requirements

DLA retains the right to request removal of Contractor personnel, regardless of prior clearance or adjudication status, whose actions, while assigned to this contract, clearly conflict with the interest of the Government. The reason for removal shall be documented in writing by the Contracting Officer. When and if such removal occurs, the Contractor shall within a two to four-week timeframe, assign qualified personnel to vacancy(s) thus created regardless of whether the individual was in a key- or non-key personnel position.

6.3. Software

The Contractor shall observe all copyright agreements and shall be held liable for any infringement of copyrighted software licensing agreements and shall compensate the appropriate contractor for each instance of copyright violation. In the interest of protecting Government systems from computer viruses, the Contractor shall not use public domain software nor shall Contractor personnel download software from public bulletin boards. The Contractor shall use only COTS, Contractor-developed, or Government-furnished software in performance of this PWS. The Contractor shall use the Microsoft Office suite of software for preparation of all documentation required in the delivery order. Should the introduction of a computer virus or malicious destruction of computer software, stored information, or hardware result from the use of public domain software or from software taken from a public bulletin board, the Contractor shall be required to repair the damage at no expense to the Government and without impact on delivery schedules or daily operation.

6.4. Data Use, Disclosure of Information and Handling of Sensitive Information (including

Personally Identifiable Information)

The contractor will maintain, transmit, retain in strictest confidence, and prevent the unauthorized duplication, use, and disclosure of information. The contractor will provide information only to employees, Contractors, and subcontractors having a need to know such information in the performance of their duties for this project.

Information made available to the contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the Contracting Officer. Contractor personnel will be required to sign a non-disclosure statement.

If proprietary information is provided to the contractor for use in performance or administration of this effort, the contractor may not use such information for any other purpose except with the written permission of the Contracting Officer. If the contractor is uncertain about the availability or proposed use of information provided for the performance or administration, then the contractor will consult with the COR/COTR regarding use of that information for other purposes.

The contractor agrees to assume responsibility for protecting the confidentiality of Government records which are not public information. Each employee of the contractor to whom information may be made available or disclosed shall be notified in writing by the contractor that such information may be disclosed only for a purpose and to the extent authorized herein.

Performance of this effort may require the contractor to access and use data and information proprietary to a Government agency or Government Contractor which is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the Government and/or others.

Contractor and contractor personnel shall not divulge or release data or information developed or obtained in performance of this effort, until made public by the Government, except to authorized Government personnel or upon written approval of the Contracting Officer. The contractor will not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this effort. Nothing herein shall preclude the use of any data independently acquired by the contractor without such limitations or prohibit an agreement at no cost to the Government between the contractor and the data owner that provides for greater rights to the contractor.

Contractor and contractor personnel shall sign a Non-Disclosure Agreement prior to commencing work on a task order.

6.5. Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI).

The Government will furnish workspace, general administrative support equipment, to include access to phone, copiers, facsimile equipment, printers, office supplies, and materials during the time when vendor personnel are on-site at the DLA facility only.

7. Contract Format

This will be a firm-fixed price award. The contractor shall include all aspects of completing the task in proposed pricing. Contract Line Item Numbers (CLINs) are as follows:

CLIN 0001: WarehouseVision Planner and Auditor Bundle CLIN 0002: Implementation of WarehouseVision Planner and Auditor Bundle CLIN 0003: Integration of WarehouseVision Planner and Auditor Bundle CLIN 0004: Training on WarehouseVision Planner and Auditor

8. Place of Performance

The work to be performed will be primarily located at the vendor’s facility. Vendor personnel will be on-site at the DLA Corpus Christi facility for certain meetings and trainings only.

9. Period of Performance

The Period of Performance (POP) will be for a period of twelve (12) months from September 30, 2018 to September 29, 2019.

The contractor is expected to be at 100 percent performance on the first day of the performance period. This is defined as the contractor being able to support all tasks on that day. As directed by the COTR, the contractor shall continue performance in emergency or mission essential conditions. Additionally, the contractor may be required to account for the whereabouts of their personnel should this information be requested by the COTR.

Generally, this technical support shall be performed by the Contractor between the hours of 0600 - 1800, Monday through Friday, excluding Federal holidays. However, deviations from these hours may be required to meet changing government business schedules.

In the event mission requirements dictate work performance outside of 0600 - 1800, the Government reserves the right to request flexible work hours from contractor personnel.

Upon a 24 hour advance, written notification from the COTR, the Government and contractor may establish a mutually agreed upon time to perform the required work.

Contractor personnel shall substitute the hours for an equal number of weekday core hours.

In the event vendor personnel are on-site at the DLA Corpus Christi facility, when the Government installation grants administrative leave to its employees (e.g. as a result of inclement weather, potentially hazardous condition, or other special circumstances), Contractor personnel working on-site may also be dismissed. However, the Contractor shall not invoice for these absences. If directed by the Contracting Officer or authorized representative, the Contractor shall provide sufficient on-site personnel to complete or continue critical work already in process or provide on-call response in accordance with the

PWS/TO.

10. Invoicing and Payment Schedule

The Contractor shall invoice no more frequently than MONTHLY. Travel charges must be in accordance with the Joint Travel Regulations, DODI 5154.31 Volume 5. The invoice should include the specific line items performed on and accepted, and associated performance payments being invoiced for the month. Other invoice requirements are set forth in FAR 52.232-25 and

DFARS 252.232-7003.

Contractor shall use the program Wide Area WorkFlow-Receipt and Acceptance (WAWF-RA) for Memo of Shipments (MS). WAWF-RA is a web-enabled application that allows contractors to create and send electronic MS receiving reports and/or invoices to government inspectors/acceptors for approval, thereby eliminating paper distribution of MS.

Invoices for goods received or services rendered under this contract shall be submitted by the contractor for approval into WAWF no earlier than the 10th business day of every month.

10.1. Within seven days of the receipt of the invoice, the COR will review for accuracy.

Inaccurate invoices will be returned to the contractor within seven days for correction.

11. Points of Contact

11.1 Contracting Officer Representative (COR):

Name: Moses Clark Title: IT Business Program Support Analyst Organization: DLA Information Operations (J6TE) Phone: (571) 767-9237 Email: Moses.Clark@dla.mil

11.2 Contracting Officer’s Technical Representative (COTR):

Name: Joseph T. Murphy Title: Support Services Chief, Distribution Organization: DLA Distribution, Corpus Christi, Texas Phone: (361) 961-5101 Email: Joseph.T.Murphy@dla.mil

12. Contractor Alternate Worksite Remote Access Requirements

a. The contractor will ensure that all CFE/PE (hardware and software) required for remote access to DLA networks, systems, applications, and databases meet the minimal configuration requirements set forth in the DLA Virtual Desktop Guide. The guide can be obtain from your COR/COTR or at the following URL https://remote.dla.mil/help/VirtualDesktopInfrastructureUserGuide.pdf.

b. CFE/PE equipment is strictly prohibited from connecting to the DLA Virtual Private Network.

c. All liability for issues and troubleshooting CFE/PE is the responsibility of the equipment owner. The DLA Enterprise Help Desk will not provide support for issues with hardware/software not provided by DLA, including but not limited to CFE/PE hardware, non-DLA networks (e.g., home routers, public hot spots), and non-DLA software compatibility issues with Citrix.

d. DLA Enterprise Help Desk resources will support troubleshooting issues that are not related to the CFE/PE hardware/software, including but not limited to accounts, DLA applications, and server-side issues.

e. CFE/PE’s running on Windows 7, Windows 8/8.1, or Windows 10 can be used to access the Virtual Desktop. Use the Virtual Desktop Guide for additional guidance.

f. It’s recommended that the CFE/PE equipment minimally install:

1) CFE/PE utilize the applicable Security Technical Implementation Guides (STIGs)

/ checklists located at https://iase.disa.mil/stigs/Pages/index.aspx for system operating system. Anti-virus, Anti-Spyware, and Host Based Intrusion Prevention software be installed and the software be updated on a daily basis (i.e. software revisions, virus definitions). That the Host Based Intrusion Prevention Software firewall be configured to permit traffic by exception only, and dropping all other traffic.

2) CFE/PE computers be scanned with the appropriate vulnerability scanner at a minimum of every 15 days and remediate vulnerability findings. Ensure contractor employees possess a current Government issued Common Access Card (CAC) and install Government approved CAC readers and middleware.

g. The Government is not responsible for any costs associated with meeting the above requirements.

13. DOD 8570.01-M, Information Assurance Workforce Improvement Program

The DOD 8570.01-M, Information Assurance Workforce Improvement Program, requires training and certification for IA duties performed. All contract employees performing IA functions shall meet the requirements in accordance with DOD/DLA guidance. Additionally, all contract employees shall be certified in operating systems on any system on which System Administration duties are performed. Proof of certification shall be provided before Privileged access is granted, at time of proposal/resume submission; this includes, but is not limited to, system administration access, network administration access, router/switch access, firewall access, and Intrusion Detection System access. All documentation required for security certification will be maintained by both the Contractor and the Government. All contract employees will have acquired the necessary certification requirements, per the DOD 8570.01, throughout the entire period of performance of the contract requirements. These certification requirements are not based on position title; they are based on duties. Refer to Attachment Y:

8570.01-M Certification Matrix; 8570.01-M Approved Baseline Certifications; and Computing Environment Certification List.

14. eCMRA Language

IAW DLAD 37.103-90(e)(1):

CONTRACTOR MANPOWER REPORTING LANGUAGE FOR CONTRACT

PERFORMANCE WORK STATEMENTS

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for services provided under this contract/purchase order via a 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 any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2014. Contractors may direct questions to the help desk at:

http://www.ecmra.mil.