Atch_5_-_Web_Application_Task_Order_0001_SOW__.docx

SP3300-14-R-0001

Attachment 5

STATEMENT OF WORK

FOR

DLA INFORMATION OPERATIONS NEW CUMBERLAND

WEB APPLICATION SUPPORT SERVICES

TASK ORDER 0001

DLA INFORMATION OPERATIONS AT NEW CUMBERLAND, PA

LOCATED AT SUSQUEHANNA, PA

1. SCOPE:

A. DLA Information Operations requires Enterprise Web Application Maintenance Support to provide Advanced Web Application Support in the maintenance and enhancement of existing web applications throughout DLA Distribution and all associated distribution locations. The objective is to utilize on-site contractual support to augment DLA Information Operations at New Cumberland expertise to maintain and/or enhance the existing web applications, rationalize existing systems for consolidation, and troubleshoot and resolve all related programmatic problems that require DLA Information Operations at New Cumberland expertise and reach back to include technical support for all DLA Distribution locations.

B. Advanced Web Application Support – Contacts vendors for warranty issues for both hardware and software. This level of support requires communication with vendors or other Government agencies to accomplish the resolution for the most complex hardware and software issues, locally and at all DLA Distribution sites.

C. Contractor technical support is required to provide application maintenance when problems occur that affect the operations of the DLA Distribution. All changes get processed through the Control Change Board (CCB) to be assigned, by written task, to alter the functionality, look/feel, or reporting process of the tasked program. Application changes will include additional web interface features, streamlining management tools to decrease manual efforts, changing database definitions and structures, modernizing reporting requirements, and other products to meet changes in regulatory requirements. All web applications listed in Section 2.1 WEB Application Support Table are Government developed.

D. Application Rationalization involves reviewing all existing DLA Distribution applications and making determinations to either develop into an enterprise application, consolidate with an existing application or sunset the application. Coordination with functional site users and other application developers is essential.

E. The scope of effort will also include Contractor support to generate new code and update SharePoint 2010 programming.

2. SPECIFIC TASK AREAS:

2.1 APPLICATION MAINTENANCE

2.1.1 Application maintenance support shall be provided on all of the applications listed in the table below. This includes application configuration, troubleshooting and problem resolution Enterprise wide.

WEB Application support Table:

VB.Net C#

ASP.Net /VB.net MS Excel

.Net 4.0 C#

ISP

Employee DB Audits Emp Performance

MSSQL 2008r2 D2B

DDWG

VB.Net

Relies heavily on timely Employee DB (ISP Application) updates Classic ASP

Users have a long standing request for a public interface to this system that is supposedly being addressed by changes to the DSS system, but as of Feb2013 have no update on the status of this.

C#

Navy

Classic ASP

DDJC

DDYJ

DDDE

MS SQL 2008R2

DDSP

**It is estimated during the term of this task order that there will be approximately a 5% variance in the number of web applications listed in the above table.

2.1.2 All user and user group roles must be maintained and updated as necessary to meet user requirements and ensure data security.

2.1.3 The Contractor shall use DLA Distribution’s Distribution Standard System (DSS), data dictionary and schema functionality, which are structured in both IBM DB2 and Computer Associates (CA) Datacom database platforms. DSS is an automated information system that manages all functional business processes of DoD's warehouse operations. These processes include receiving, storage, consolidation, packing, shipping, inventory, inspection, and workload management. The system includes both commercial-off-the-shelf (COTS) software packages and developed application software. DSS operates in an IBM mainframe compatible environment and supports inventory management and workload control functions. It manages the performance of the mainline distribution functions: receipt, stow, pick, pack, and ship. A relational database is maintained to track the quantity and location of depot stock items. Communication is gained through a combination of interfaces, specified transactions, and file transfers.

2.1.4 The Contractor shall test all data and ensure 100% data integrity and error-free load checking on all products provided. Therefore, a constant output, which tests and proves the data output is the same as data retrieved from source shall be available first thing each morning.

2.1.5 Address all issues related to Web-based system performance in accordance with (IAW) the Acceptable Performance Levels (APLs) identified in the Quality Assurance Surveillance Plan (QASP).

2.1.6 The operation documentation shall be modified prior to moving application to production to incorporate any change that may be required.

2.1.7 The Continuation of Operations (COOP) Procedures shall be updated when a change is made that will affect bringing the processing-related programs online at the backup COOP location.

2.1.8 Provide technical support and resolution for software installation and configuration issues.

2.1.9 Trouble tickets shall be input, updated and maintained using the existing Remedy Help Desk software application.

2.1.10 For maintenance resolutions, the Contractor shall notify, in writing, the KO, or designee, and the DLA Information Operations at New Cumberland liaison of the application problem resolution.

2.1.11 Attend meetings with the KO, or COR, to discuss milestones, task status, concerns, and any issues that would impact progress. Discussions may include major projects such as new Enterprise application requirements or existing application changes/upgrades.

2.2 PROGRAM DEVELOPMENT / CHANGE SUPPORT REQUIRMENTS

Development/Change duties apply to all web based applications in support of the DLA Distribution Enterprise. All the development and change requirements below will be completed each time an application is created/changed or upgraded.

2.2.1

A. Identify specifications based on customer requirements, to determine the level of effort required.

a. Requirements Analysis

1. Functional Design: Application purpose, justification, description, and data fields

2. UI Design: Interfaces, Screens, Fonts, Attributes, etc. (Cosmetics) using 508 compliance measures.

3. System Design: Hardware and Software configuration platform baseline and compatibility identification

B. All development and change programming for distribution applications must be within compliance of the Section 508 (handicap-accessibility) laws and code.

C. Work with the customer to get the CCB Approval request composed and sent to the CCB for review.

D. Upon CCB approval, create Conceptual Design: Application/Database/Information-base structure and layout, record definition and layouts, data field definition, end-user interfaces, screens, and drop-down menus, text and graphical issues (fonts, attributes, etc.), etc. Business Rules are defined in accordance with the Customer Requirements. The Contractor shall submit concept and design documentation outlining the database schema and structures, data flow, error-checking, data normalization, security, views, and web reports for approval to the KO, or designee, for approval.

E. Application Development and Coding: Create application software coding. Document the code explaining what the block of code is doing and any other helpful information.

F. Development Testing: Incremental testing during the initial coding and development phases in a non-production/testing environment.

G. Production Testing: Performed after Application Development and Coding phase/step is completed. Testing of the overall integrity of the code in relation to the complete system performance in a staging environment.

H. Customer Acceptance Testing: Testing begins during the Production Testing phase/step. During this phase/step, the customer actually tests the limitations of the products to determine whether it satisfies the requirements and specifications originally identified. The customer has the option of ‘accepting’ or ‘refusing to accept’. Should the customer/end-user ‘refuse to accept’ the application, application development and coding shall resume based upon refined specifications provided by the customer/end-user.

I. Documentation

1. End-User: Overviews and End-User Manuals (Definition and instructions on how to use the application)

2. Functional Administrator/Coordinator: Overviews and Manuals (may be same as or similar to end-user documentation); typically, the purpose of the application, description, data fields used, problem identification, troubleshooting, problem resolution, problem escalation and referral, etc.

3. Technical/Help Desk: Overviews and Manuals for technical support staff; e.g. DBAs (database analysts/administrators), system/server administrators, etc.; typically, the data and database structures, record layouts, field descriptions (length, type, rules, audio/video attributes, etc.), problem identification, troubleshooting, problem resolution, problem escalation and referral, etc.

J. Training and/or Training Plan Package: Training can be delivered in a variety of formats, using a variety of vehicles – e.g. classroom, computer-based training (CBT), video teleconference (VTC), etc., using manuals, videotape, DVD-ROM, CD-ROM, etc. Types of training include end-user, functional administrator/coordinator, and technical/help desk

1. End-User: Training should be focused on the access and use of the application being developed to satisfy mission and job requirements. Training modules should be developed as follows: (1) Application Basic Overview and User Access, (2) Screens – Access and Use (correlation between application use and job/mission requirement). The target audience for this training/training package is application end-users, and functional administrators and coordinators.

2. Functional Administrator/Coordinator: Training should be focused on the purpose and description of the application; data fields used and defined application problem identification, troubleshooting, problem resolution, problem escalation and referral, etc. to satisfy mission and job requirements. Training support areas: Application Overview, Purpose and Description, Record Layouts and Data Fields, Problem Identification, Troubleshooting, and Resolution, Problem Escalation and Referral, etc. The target audience for this training/training package is functional project and team leads, and/or functional administrators and coordinators.

3. Technical/Help Desk (DBA and System/Server Admin): Training should be focused on the purpose and description of the application, data and database structures used and defined, record layouts, field descriptions (length, type, rules, audio/video attributes, etc.), problem identification, troubleshooting, problem resolution, problem escalation and referral, etc. to satisfy mission and job requirements. Training modules should be developed that reflect the aforementioned support areas:

a. Application Overview: Purpose and Description,

b. Data and Database Structures – including record layouts and field descriptions and attributes,

c. Problem Identification, Troubleshooting, and Resolution,

d. Problem Escalation and Referral, etc.

The target audiences for this training/training package are technical and help desk support personnel.

K. Application Deployment: The actual rollout of the application, including distribution and installation of that application.

L. Final Acceptance Testing: Not completed until application development and deployment have been completed. Testing begins during the final stages of application development, and continues through application deployment. During this phase/step, the customer tests the limitations of the products in a full production environment to determine whether it satisfies the requirements and specifications originally identified. The customer/end-user has the option of ‘accepting’ or ‘refusing to accept’. Should the customer/end-user ‘refuse to accept’ the application, application development and coding shall resume based upon refined specifications provided by the customer/end-user. If customer/end-user formally ‘accepts’ the application (signs and dates an acceptance form/contract), on the date/time when the application was accepted, the ‘manufacturer’s’ warranty period for the application begins.

1. Developer signs release forms that the Web application and all associated products are compliant with Section 508, the Mobile Code Policy, internal security requirements, and other DoD, DLA, and DLA Distribution policies.

M. The Contractor shall test all applications on the DLA Distribution Web Development Server after changes are complete prior to production testing on the Staging Server and finally deploying to the 64-bit production environment.

N. The Contractor shall implement the necessary modifications to the server hosted databases in accordance with optimal design for data insert, update and query retrieval performance.

O. The Contractor shall update the Source Code documentation that includes ASP pages, DLLs (source prior to executable) stored procedures, etc. reflecting the application change.

P. The Contractor shall notify the appropriate team leads and respective Program Coordinator, and DLA Information Operations at New Cumberland liaison, when the application development/changes have been completed/resolved and estimated timeframe to migrate solution/resolution into the Production application.

Q. Attend meetings with the KO, or designee, to discuss milestones, task status, concerns, and any issues that would impact progress. Discussions may include major projects such as Enterprise PC replacements, installation, upgrades or software upgrades.

Application Rationalization is an on-going project which evaluates all the functionality of the applications to determine their future uses for DLA Distribution.

2.2.2 The contractor will be tasked with analyzing approximately 60 WEB Applications and providing the Government with the analysis.

Table of Web Applications that need Rationalization:

Security Risk (Classic ASP)

Security Risk (Classic ASP)

Security Risk (Classic ASP)

X

X

Security (Classic Asp)

X

X

X

X

X

X

X

X

X

X

Security (FTP)

Security Risk (Classic ASP)

X

X

Security Risk (Classic ASP)

Security Risk (Classic ASP)

Security Risk (Classic ASP)

X

X

Security Risk (Classic ASP)

X

Classic ASP

Security Risk (Classic ASP)

Security Risk (Classic ASP)

Web-based MRO tracker provides data by distribution depot.

Security (Classic ASP)

Security (FIPS cannot be applied) Conflicts with Apose.Excel

Security (Classic ASP)

Security (Classic Asp)

2.2.3 Working with the business personnel at DLA Distribution Headquarters, DLA Information Operations New Cumberland (IONC) is tasked with determining the future of all applications listed in the above table. Below A though F are the outcomes for the above WEB Applications that are being analyzed.

· Our currents Courses of Action are:

A. Centralize application at DLA (IONC), Roll functionality into DSS or another Enterprise Application. The application has been deemed useful for all sites and the functionality can be rolled into DSS or another Enterprise Application in an agreed upon timeframe. Until that timeframe, the application will be centralized and maintained at DLA IONC. New development requirements will be handled by the J6NIS developers in New Cumberland. J6NIS will assume responsibility for troubleshooting and maintenance with the assistance of the site personnel. The development and maintenance will continue until the functionality is moved into DSS or another Enterprise Application. Once in DSS or another Enterprise Application the application will be sunset.

· Centralize application at DLA IONC, Expand functionality to all DLA Distribution Sites

B. The application has been deemed useful for all sites and expansion to all sites will be completed in an agreed upon timeframe. The application will be centralized and maintained at DLA IONC. New development requirements will be handled by the J6NIS developers in New Cumberland. J6NIS will assume responsibility for troubleshooting and maintenance with the assistance of the site personnel. Level of effort will need to be established and vetted for the new global application between DLA Distribution DLA Logistics Operations (J3)/Customer Support (J4) personnel and J6N personnel before beginning the expansion piece of the application.

· Centralize application at DLA IONC, Sunset application in X number of years.

C. The application has been deemed unique for the location and supports the DLA Distribution Mission. The application will be centralized at DLA IONC. J3/J4 has determined that the application is no longer necessary at the site and will be sunset in an agreed upon timeframe. No new development will be done on the application. Only troubleshooting and repair on the current functionality will be done by the J6NIS developers in New Cumberland.

· Centralize application at DLA IONC, Functionality will remain unique to site

D. The application has been deemed unique for the location and supports the DLA Distribution Mission. The application will be centralized at DLA IONC and all new development requirements will be handled by the J6NIS developers in New Cumberland. J6NIS will assume responsibility for troubleshooting and maintenance with the assistance of the site personnel.

· No centralization, Sunset application in X number of years

E. The application has been deemed unique for the location and centralization of the application is not possible to due latency or response issues. The application also may not support the DLA Distribution Mission Support and does not need to be centrally located. J3/J4 has determined that the application is no longer necessary at the site and will be sunset in an agreed upon timeframe. No new development will be done on the application. Only troubleshooting and repair on the current functionality will be done by the J6NIS developers in New Cumberland.

· No centralization, Functionality will remain unique to site

F. The application has been deemed unique for the location and centralization of the application is not possible to due latency or response issues. The application also may not support the DLA Distribution Mission Support and does not need to be centrally located. For example, the site has developed an application for use by the site Fire Department. The continued development of the application will now reside with the J6NIS developers in New Cumberland.

2.2.4 The Contractor will carry out the following Application rationalization analysis in the following order:

A. Identify all apps, owners, number of users, and availability B. Analyze the code, security, functionality, and status C. Determine if the app has an alternative or should be made Enterprise D. Calculate sustainment, update/migrate, and rewrite costs E. Create decision making criteria F. Weekly meetings and briefs G. Create supporting documents and update week

3. Level of Effort and Labor Categories

4. GENERAL OPERATION CONDITIONS

A. This Section provides general information relating to the conditions of operation and general requirements relating to the Web Application support services performed by DLA Information Operations at New Cumberland, PA located at Susquehanna, PA.

5. PLACE OF PERFORMANCE

A. Work will be accomplished primarily at DLA Distribution Susquehanna, PA 17070 DLA Distribution Susquehanna, New Cumberland, PA.

B. Contractor employees may be required to travel to any site CONUS and OCONUS supported by DLA Distribution as deemed necessary.

C. Travel costs will be paid for in accordance with the Joint Travel Regulations. Receipts for all travel expenses must be provided when the travel voucher is submitted.

D. Offsite electronic work may be authorized by the COR. The frequency of the offsite work shall be determined after performance has commenced.

6. PERIOD OF PERFORMANCE

The period of performance of this Task Order shall commence on or around 25 September 2014 and be completed within 365 calendar days, or as modified. The phase-in period will commence on or around 25 September 2014 and will not exceed 30 calendar days. The period of full performance of the requirements will commence on or around 25 October 2014 and be completed on or around 24 September 2015.

7. CURRENT DUTY HOURS AND ACCESS TO THE HOST INSTALLATION

A. Work will primarily be accomplished at the DLA Information Operations at New Cumberland location Monday through Friday from the hours of 0600-1700 hours.

B. On-call after hours work shall be required as deemed necessary by the COR. Support shall be provided via telephone, on-site, or remotely using Government furnished equipment (GFE), as deemed necessary.

C. At a minimum from 0600-1700 hours Monday through Friday the contractor must have 50% of the FTE's onsite providing support.

8. TRAVEL

Contractor personnel may be required to travel within the continental United States (CONUS) and outside the continental United States (OCONUS) in support of this contract. All travel by Contractor employees shall be authorized by the KO or COR prior to the travel being performed. When travel has been authorized, the Project Manager shall approve and forward travel requests to the COR for Government validation within a minimum of ten (10) working days prior to the travel commencement date. Travel requests shall be in writing and contain the dates, locations, and estimated travel costs. The Contractor shall ensure that all travel is IAW the Joint Travel Regulations (JTR). Reimbursements for transportation costs will be limited to allowable expenses for Government directed travel. The Contractor shall be responsible for any costs incurred as a result of authorized travel which were in excess of that allowed under Federal Acquisition Regulation (FAR) Part 31.205-46 Travel Costs and the appropriate regulations therein

9. PHASE-IN

In order to allow for a smooth and orderly transfer of responsibility for project management, data collection and analytical projects and duties from the incumbent Contractor to the new Contractor, the Contractor shall participate in a period of phase-in during which the incumbent Contractor shall continue to perform the services. This period will commence upon execution of the task order and will continue for a period not to exceed (1) one month, at which time the Contractor shall commence full performance.

Within five (5) calendar days from the date of task order award, the Contractor shall complete the hiring action for the Program Manager. Within 15 calendar days of the date of task order award, the Contractor shall complete all hiring actions for personnel required to perform the requirements of the task order and complete any associated training requirements. The Contractor shall ensure that all new employees are trained and ready to begin working on the first day of full performance.

The Government will provide orientation for all Contracted personnel within the first 30 days of the phase-in period. The orientation will cover topics such as familiarization with operations, facilities location, assigned parking, familiarization with DLA Distribution, and issuance of building passes.

During the phase-in period, the Contractor shall provide a weekly written report to the KO or COR on the status of the tasks required to be completed during this period. Five (5) working days prior to the conclusion of the phase-in period, the Contractor shall provide the KO or COR with a detailed final phase-in report outlining all tasks accomplished.

Below are the projected hours for phase-in by labor category.

10. SECURITY

A. Security Clearance:

The Contractor shall comply with all applicable DoD security regulations and procedures during the performance of this task order IAW 2.6 Security, 2.6 Physical Security, 2.6 A. Personnel Clearance, and 2.6.2 Information System Security. The Contractor shall be required to provide a minimum of IT II eligibility for all personnel requiring access to Government computers and workstations. The Task Order duration is expected to last no longer than twelve (12) months.

11. GOVERNMENT-FURNISHED PROPERTY (GFP), SYSTEMS, TRAINING AND SUPPORT SERVICES

The Government will provide access to resources and information to include Government transactional data systems required in the performance of this PWS.

The Government will furnish training for Contractor personnel on the Government data systems to be used in performance of this PWS.

The Government will provide on-site office space with furniture, to include desktop computer and network printer, office supplies and desk telephone. This office space will be located at DLA Distribution Susquehanna, PA.

At no cost to the Contractor, the Government will furnish the services to be used exclusively to perform the requirements of this contract that include custodial services, refuse and recycling collection, government forms, emergency medical services, police and fire protection, telephone and utilities.

All materials, equipment or supplies (i.e. lift equipment, tools and parts) that contractor personnel will need to perform this requirement at DLA Information Operations at New Cumberland, PA located at DLA Distribution Susquehanna; PA will be furnished by the Government.

The Government will provide all hardware necessary for the Web Application upgrade.

12. CONTRACTOR-FURNISHED EQUIPMENT, MATERIALS, SERVICES, TRAINING

A. Title to contractor-furnished equipment shall remain with the contractor. Contractor furnished equipment shall meet the same safety requirements as those established for government equipment.

B. The Contractor shall furnish supplies not provided by the Government.

C. The Contractor shall provide the training identified below and any other training that is not identified as Government-Furnished but which may be required for Contractor personnel to comply with the contract requirements. The Contractor shall maintain copies of training records for the duration of the contract, designation letters and certificates on site and make them available for the KO or COR to review upon request.

A. COMBATING TRAFFICKING IN PERSONS (CTIP).

B. INFORMATION ASSURANCE (IA).

C. SECURITY TRAINING. The Government will provide the materials necessary for employee training in the following areas:

· Counterintelligence. IAW DoDI 5240.6, Counterintelligence (CI) Awareness and Briefing Program (Training time is 30 minutes or less).

· Operational Security (OPSEC). IAW DoDD 5205.2, DoD Operations Security Program (Training time is 60 minutes or less)

· Antiterrorism Training. IAW DoDD 2000.12, DoD Antiterrorism/Force Protection (AT/FP) Program as directed by the KO or COR (Training time is 60 minutes).

D. INFORMATION ASSURANCE: Contractor personnel performing tasks associated with this PWS that will be performing an IA function shall be trained and certified in accordance with DoD Directive 8570.1 and DoD 8570.1M. IA functions are defined in chapters 3 and 4 of the DoD 8570.1M. Contractor personnel shall be certified at the appropriate IAT II Level in accordance with their designated function (labor category) as demonstrated by possessing one (1) of the authorized certifications listed in Table 2.4.1, IAT Certification Requirements. The Contractor shall identify personnel performing IA functions identified in the PWS prior to that employee commencing any work under this PWS and provide documentation to the KO or COR showing the employee’s certification(s) and certification status. The Contractor shall demonstrate that they have a process to track certification status of employees to ensure certifications are current or to replace departing employees with employees possessing current certifications in a manner that will not cause program interruption. Contractor personnel shall be required to sign the User Access Agreement, Privileged Rules of Behavior, and General Rules of Behavior and non Discloser agreement prior to working on any government system(s).

E. EQUIPMENT OPERATION. This training is required for all Contractor employees who operate motor vehicles, MHE, other equipment with the required licensing, certification, or specialized training. Training includes but is not limited to the requirements identified in CFR Title 29, Part 1910.178; CFR Title 49; American Society of Mechanical Engineers (ASME) B30.13-1996, Storage/Retrieval (S/R) Machines and Associated Equipment; and DLAI 4500.36, Management, Acquisition, and Use of DLA Operating Equipment, Sections E3m and E3n; and Federal, State and Local Laws. Refresher training is required at a minimum of every three years or when warranted in accordance with OSHA, DoD, and manufacturer’s guidance.

F. The Contractor shall provide safety equipment while performing hazardous duties in both the office and warehouse environments. The required safety equipment may include, but is not limited to, safety shoes, glasses, harness, and lanyard.

13. NON-PERSONAL SERVICES STATEMENT

Contractor employees performing services under this order will be controlled, directed, and supervised at all times by management personnel of the contractor. Contractor management will ensure that employees properly comply with the performance work standards outlined in the SOW. Contractor employees will perform their duties independent of, and without the supervision of any Government official or other Defense Contractor. The tasks, duties, and responsibilities set forth in the task order may not be interpreted or implemented in any manner that results in any Contractor employee creating or modifying Federal policy, obligating the appropriated funds of the US Government, overseeing the work of Federal employees, providing direct personal services to any Federal employee, or otherwise violating the prohibitions set forth in parts 7.5 and 37.1 of the FAR. The Government will control access to the facility and will perform the inspection and acceptance of the completed work.

14. GOVERNMENT MANAGEMENT OVERSITE

Government management will provide general instructions on limitations and deadlines. Additional instructions will be provided for any unusual assignments or those that vary from established procedures. The Contractor’s employees will independently carry out the assignments. Completed work will be spot checked by Government management for adherence to procedures, accuracy, and completeness.

15. CONTRACTOR IDENTIFICATION AND COMMUNICATION

A. During performance of the service requirements set forth in this PWS, all Contractor personnel shall introduce themselves or shall ensure they are introduced as Contractor employees and shall display distinguishing badges. Contractor personnel shall also appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

16. PROPERTY ACCOUNTABILITY

The Contractor shall maintain care of all Government-furnished property. At all times during the performance of the contract requirements, title to the mission stock and all other government-furnished property shall remain vested with the Government. In exercising care and custody, the Contractor shall safeguard all Government-furnished property.

The Contractor shall provide the proper protection for material under their custody and control. If there is a loss the Contractor shall immediately notify the KO or COR.

17. LIABILITY FOR GOVERNMENT PROPERTY

The Contractor shall be held financially liable for loss, damage, or destruction of government property caused by negligence, willful misconduct or unauthorized use. The KO or COR will make the pecuniary liability determination when a Contractor’s negligence results in loss, damage, or destruction of Government property.

The Contractor shall:

Notify the KO or COR immediately when it discovers the gain, loss, damage or destruction of government equipment or property.

Conduct an initial search and/or informal investigation into the loss or damage of equipment or property and forward all research data to the KO or COR.

Cooperate in any subsequent investigations.

18. CONTRACTOR MANPOWER REPORTING

The Contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Defense Logistics Agency 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 help desk at: http://www.ecmra.mil.

19. DELIVERABLES

Upon contract award, DLA Information Operations at New Cumberland IT Ops representative(s) will consult with Contractor representatives to provide an overview of current and proposed web application program configurations.

The Contractor shall provide a copy of the Certificate of Liability Insurance to the KO, or designee.

The Contractor shall provide a Quality Control Plan (QCP) to the KO, or designee, within 10 days after contract award. The document shall be updated at least quarterly to reflect any changes in goals, strategies, and circumstances.

The Contractor shall provide weekly status updates to the KO, or designee, to include any issues that would impact completion date of any assigned support tasks.

The Contractor shall, upon request, attend and participate in meetings with KO, or designee, or alternates to discuss required tasks, concerns, and any issues.

Documentation of changes made to resolve any operating problems. Documentation of change made must include:

All source code, including ASP pages, DLLS, Stored Procedures, etc. in all completed/changed application modifications.

All permissions and configurations of each file and/or virtual directory.

All forms with customer approvals, signature verification that applicable policies; i.e. Section 508, Mobile Code, etc. and other requirements were followed and implemented.

Complete ‘application restore’ procedures for COOP/Disaster Recovery, ensuring complete recovery of the application, by system administrators (non-developers).

The Contractor shall provide complete Training Packages on changed applications,…