PDSS_Performance_Work_Statement_16Mar16.doc

PERFORMANCE WORK STATEMENT

FOR

POST DEPLOYMENT SOFTWARE SUPPORT (PDSS)

IN SUPPORT OF THE

PROGRAM EXECUTIVE OFFICE

ENTERPRISE INFORMATION SYSTEMS (PEO EIS)

PRODUCT DIRECTOR ARMY HUMAN RESOURCE SYSTEMS (PD AHRS)

INSTALLATION SUPPORT MODULES (ISM) AND

RANGE FACILITY MANAGEMENT SUPPORT SYSTEM (RFMSS)

16 March 2016

1.0 BACKGROUND/MISSION: The Program Executive Office Enterprise Information Systems (PEO EIS) provides infrastructure and information management systems to the Army. The PEO EIS is a pivotal Information Technology (IT) enabler within Department of Defense (DoD) and the Army, responsible for implementing Enterprise Infrastructure, Backbone Communications, and Business and Warfighting IT Systems. Its mission is to enable information dominance by developing, acquiring, and deploying enterprise-wide, network-centric information management and communications to meet the Army’s current and future mission requirements. To that end, PEO EIS’s Army Human Resource Systems (AHRS) organization supports the Army’s mission, strategic goals, and objectives by providing software programs that enhance selected business processes associated with managing and operating major Army installations, camps, and posts worldwide.

2.0 REQUIREMENT: This requirement is to provide Post Deployment Software Support (PDSS) and directed software enhancements to existing software for the Product Director Army Human Resource Systems (PD AHRS) Installation Support Modules (ISM) system and Range Facility Management Support System (RFMSS). By means of these two products – ISM and RFMSS, PEO EIS PD AHRS systems interface and provide services to the US Army Active, US Army National Guard, US Army Reserve, US Marine Corps and US Navy installations worldwide. The Office of the PD AHRS deployed automated systems are:

2.1 Installation Support Modules (ISM): The ISM web based system consists of four standard, custom-developed automation applications packaged into functional modules that integrate day-to-day Army Installation business practices and processes. Three of the ISM modules support human resources business functions (In/Out Processing, Transition Processing and Personnel Locator); while the fourth module (Central Issue Facility) supports logistical business functions associated with management and accountability of Organizational Clothing and Individual Equipment. The ISM system is currently operational at Army installations throughout Continental United States (CONUS) and Outside the Contiguous United States (OCONUS) to enhance installation management by automating selected installation support functions. The ISM system is web-based and the software operates over a Transmission Control Protocol/Internet Protocol (TCP/IP) network using the World Wide Web (WWW) family of protocols, including Hypertext Transfer Protocol (HTTP). The Web/Application servers receive user requests from the browsers, have the requests processed by the database server, and then send the request results back to the users. Oracle Web Logic 11g R2 is used to provide HTTP connections and Oracle Container for Java 2 Enterprise Edition (J2EE) (OC4J) service. Data exchanges between the browsers and the Web/Application servers are handled via Secure Sockets Layer (SSL). The ISM middle tier has been virtualized using Oracle VM server for Sun SPARC, which provides the ability to create Logical Domains (LDOMs), a Solaris native VM technology. The database and Web/Application servers are located at Fort Belvoir, VA and Fort Huachuca, AZ. Oracle’s Data Guard is used to keep both databases in synch, providing an environment that allows for an enterprise view of data worldwide. The Business Intelligence (BI) Publisher server are used for monitoring and reporting purposes. Network and Systems Management (NSM) for the ISM system is provided under a separate contract and is called the AHRS service desk and includes a 24/7 Help Desk.

2.2 Range facility Management Support System (RFMSS): The RFMSS system is a web-based intranet application with a single application/database server located at the installation level. The RFMSS application provides a standard, integrated system to efficiently assist installation commanders in providing training support for units and schools to manage valuable training lands and ranges at CONUS and OCONUS United States Army, Army National Guard, US Army Reserve, United States Marine Corps (USMC) and US Navy installations/bases. The RFMSS system provides an automated means for units to schedule training areas and firing ranges; allows range control personnel to schedule airspace; and also provides automation to fire desk operations. RFMSS supports all major range management processes including: range and training area scheduling; unit and range control approval process; automation of range firing desk operations; airspace scheduling; automated warning of safety, scheduling and/or environmental conflicts; graphic and textual display of current range status; and production of range, training area and airspace utilization reports. The RFMSS application was written using Microsoft .NET and its database uses Oracle 11g. Additionally, RFMSS has a centralized web server located at the Fort Belvoir NEC computer facility which enables units and schools to reserve range and training area assets as much as three years in advance. The RFMSS system is currently deployed to 146 Army installations (41 Active Army, 44 Army Reserves, 61 USARNG), 12 Marine Corps bases and 50 Navy bases. The NSM for the RFMSS system is provided by a separate contract and is the AHRS service desk and includes a 24/7 Help Desk.

3.0 TYPE OF CONTRACT: This will be a Firm Fixed Price Contract type.

4.0 PERFORMANCE OBJECTIVES, GOALS AND OUTCOMES:

4.1 Overall Objectives

4.1.1 Personnel: The Offeror shall provide a proper skill mix, experience and required number of qualified personnel to accomplish the scope and mission of the project as defined in this PWS. The Offeror shall provide all necessary qualified personnel and supplies to accomplish the work described within this PWS.

4.1.2 Facilities: The Contractor shall provide all required office space, furniture and communication (voice, data) capabilities for the personnel performing on the task order. The facilities must comply with all appropriate DoD and U.S. Army Information Assurance directives and regulations that govern Information Technology software development.

4.1.3 Organizational Process: The Contractor must provide sufficient internal controls, management oversight and technical skills to accomplish the work described in this PWS. The Government requires the Contractor to be familiar with the U.S. Army and DoD organizations and functions, as well as have a keen understanding of current and future Army and DoD IT Architecture and Infrastructure. The Contractor must be capable of rapidly responding to changes associated with the emerging and dynamic DoD and Army environments.

4.1.4 Information Assurance: The Contractor must ensure and certify that all personnel supporting the efforts in this PWS meet the security designation requirements of IT and IT-related positions as outlined in Army Regulation 25-2:

· Information Technology (IT) Level III for those with non-privileged access, or limited privileged access, without system administration functions,

· IT Level II for personnel with limited privileged access plus limited system administration functions,

· IT Level I for personnel with full privileged system administration access.

This project is unclassified, however; the data in the ISM and RFMSS systems are sensitive and must be safeguarded accordingly. All contractor personnel working on this requirement must meet the minimum security designation requirement of Level II (as defined in AR 25-2) and shall have a minimum of favorable completion of a current National Agency Check (NAC) within 180 days of contract award and initiation of a Single Scope Background Investigation (SSBI) and favorable review of SF 85P (Questionnaire For Public Trust Positions), SF 86 (Questionnaire For National Security Positions. Assignment of personnel to the project prior to completion of an investigation is prohibited unless approved in advance by the PEO EIS PD AHRS Security Manager. An unfavorable investigation or failure to obtain a security clearance may be grounds for not assigning a contractor employee to this contract or may be grounds for removal of an employee from the contract. Work on this project may require that contractor personnel have access to Privacy and other sensitive information. Contractor personnel shall adhere to the Privacy Act, Title 5 of the United States Code, section 552a and applicable DOD and US Army rules and regulations.

4.1.5 All Contractor personnel are required to have a SECRET Clearance. All contractor personnel working on this contract must meet the minimum security designation requirement of Level III (as defined in AR 25-2) and shall have a minimum of a favorable National Agency Check and favorable review on Standard Form 85P and Supplemental Questionnaire. For IT Level II, contractor personnel must have a National Agency Check with Local Agency (NACLC) and Credit Checks. For IT Level I, contractor personnel must have a favorable completion of a current National Agency Check (NAC) within 180 days from contract award and initiation of a Single Scope Background Investigation (SSBI) and favorable review on SF 85P (Questionnaire For Public Trust Positions), SF 86 (Questionnaire For National Security Positions. Assignment of personnel to the project prior to completion of an investigation is prohibited unless approved in advance by the PEO EIS PD AHRS Security Manager. An unfavorable investigation or failure to obtain a security clearance may be grounds for not assigning a contractor employee to this contract or may be grounds for removal of an employee from the contract. Work on this project may require that contractor personnel have access to Privacy and other sensitive information. Contractor personnel shall adhere to the Privacy Act, Title 5 of the United States Code, section 552a and applicable DOD and US Army rules and regulations.

4.1.6 All contractor personnel must create an Army Training & Certification Tracking System (ATCTS) account. For those that fall within IT Level I-III, they must meet the minimum IT required training, baseline certification, and computing environment certification in order to be granted access to the system(s). For those that fall within the Information Assurance Manager (IAM) I-III, they must meet the minimum IAM required training and baseline certification. All personnel within the IT or IAM level must meet these qualifications upon award of the contract.

The Government shall provide a .mil email account for official email to qualified contractor personnel. They will have an Enterprise account (@mail.mil) as their main means of email communication and an Army Knowledge Online (AKO) account (@us.army.mil). The Enterprise email accounts will be processed through the PD AHRS office. The AKO accounts will be sponsored by the PD AHRS Information Assurance Manager (government).

4.1.7 Identification and handling of Personally Identifiable Information (PII): Contractor must ensure that no PII is stored on contractor equipment, nor at contractor’s facilities. Contractor must ensure that all personnel are trained on proper handling of PII to include reporting requirements.

4.1.8 Disclosure of Information: The contractor shall not release to anyone outside the contractor’s organization any information, unclassified or classified, regardless of medium (e.g. film, tape, document, etc.), pertaining to any part of this contract or any program related to this contract, unless: (1) the Contracting Officer gives prior written approval; or (2) the information is otherwise in the public domain before the date of release. Request for approval shall identify the specific information to be released, the medium to be used, and the purpose for the release. The Contractor shall submit its request to the Contracting Officer at least 45 days before the proposed date for the release. The Contractor shall agree to include a similar requirement in each subcontract under this contract. Subcontractors shall submit request for authorization to release through the prime Contractor to the Contracting Officer.

4.2 Performance Requirements: The Contractor must research and review all documentation (see attachment) to attain sufficient understanding of the existing ISM and RFMSS applications and architecture to completely satisfy all the requirements in this PWS. The Offeror’s proposal must be sufficiently detailed for the Government to assess the technical merit. The Contractor shall provide technical services to include project management, risk management, analysis, design, code development, documentation, database design and development, database conversion, testing, quality assurance, configuration management, physical security, information assurance, deployment, post deployment support, and customer support to include a Tier 2 Helpdesk. Every effort should be made to use commercial off the shelf products where feasible.

4.3 Programmatic Requirements

4.3.1 Ensure availability of ISM and RFMSS services to end users remains at or above current levels. System Availability and System Up-time will be at 95 %, Help Desk Trouble Ticket Rate at 95 %, this is the percent of overall total trouble tickets received to date vs percent of overall total trouble tickets actually closed. Security patches, at 99 %, these are security patches applied as required.

4.3.2 Comply with applicable Army and Department of Defense directives.

4.3.3 Meet performance measures required by the Government. See Table 1 in this PWS.

4.3.4 Establish an organizational capability to transition the RFMSS application to a DISA DECC in accordance with Army Data Center Consolidation Plans.

4.3.5 Establish an organizational capability to address requirements contained in the ISM and RFMSS Functional Description Documents and address future requirements as they evolve.

4.3.6 Establish a process to quickly respond to requests for change to the existing software.

4.3.7 Ensure that PD AHRS personnel receive regular, scheduled information on progress and issues in the form of monthly progress reports/briefings, and immediate notification of extraordinary events.

4.3.8 The Contractor must provide personnel with an understanding of the Risk Management Framework (RFM) in order to ensure the PD AHRS automated systems obtain the proper Authority to Operate. The Contractor must support security risk analyses and engineering for security accreditation for the PD AHRS systems.

4.4 Post Deployment System Support (PDSS) Requirements

4.4.1 The Contractor shall provide measurably responsive 24/7 support, as required, second level help desk support via web and phone access (historically, this 24/7 support has been required approximately once a month). The AHRS service desk (under separate AHRS contract) provides the first level of help desk for the ISM and RFMSS users worldwide. When the AHRS service desk cannot resolve the user issue it will be elevated to the second level help desk operated by the ISM/RFMSS software development contractor.

4.4.2 Capture and track status of all Trouble Tickets (TT), Software Trouble Reports (STR), Engineering Change Proposals (ECPs) and System Change Requests (SCR).

4.4.3 Expeditiously resolve trouble tickets elevated from the AHRS service/help desk or from independent testing.

4.4.4 As the second level help desk, ensure that the first level help desk is informed of the status of trouble tickets on a regular basis.

4.4.5 Provide Government real time access to the details of all trouble tickets (including tracking back to the originating AHRS service desk trouble ticket), System Trouble Reports, and Software Change Requests, etc.

4.4.6 Develop and field Interim Change Packages (ICPs) in response to emergency Trouble Tickets or time sensitive regulatory changes.

4.4.7 Work with the AHRS service desk personnel to maintain current:

Continuity of Operations (COOP)

Help Desk Functionality

Physical Release Management

Operational Trouble Ticket resolution

4.4.8 Work with the PD AHRS Configuration Management contractors to maintain Configuration Management (CM) and Release management (RM) on all ISM/RFMSS environments.

4.4.9 Work with the PD AHRS Information Assurance specialist to ensure the ISM and RFMSS systems meet the information assurance security standards prescribed by Army and DoD regulations and directives.

4.4.10 Work with the PD AHRS ISM and RFMSS Test Team (IRTT) personnel to ensure that all change packages are tested prior to fielding.

4.4.11 Maintain full operability of the current web based environment for the ISM system and the server-based and web-based environments for the RFMSS system.

4.4.12 Provide support to PD AHRS personnel for normal fielding and/or training activities.

4.5 System Change Package Requirements

4.5.1. The Government intends to issue System Change Packages (SCP) containing fixes to code, and/or implementation of Configuration Control Board approved Engineering Change Proposals (ECPs) which introduce new functions or features each year of the contract for the ISM and RFMSS systems. The Government will determine the exact number of (SCPs) per year (up to two SCP’s per year) based on coordination with the Configuration Control Board and input from the Software Developers. The Government will provide final approval of the list of STRs and SCRs for each package.

4.5.2 Improve the ISM and RFMSS applications efficiency, accuracy, and ease of use.

4.5.3 Provide technical expertise supporting software administration in the deployment of major upgrades to Oracle Application Server, and Sun Solaris and in the development of system patches to address Information Assurance Vulnerability Alert (IAVA), Oracle CPUs and Solaris patches.

4.5.4 Rapidly address any urgent issues that are identified, either via IAVA, regulatory change, or critical system defect, by developing emergency Interim Change Packages. Regular IAVA’s are implemented quarterly. Historically, there have been 4 - 6 emergency IAVAs that need immediate action that require an out of cycle patch.

4.5.5 Work with the PD AHRS ISM and RFMSS Test Team (IRTT) personnel to ensure that all SCPs are tested prior to fielding.

4.5.6 Work with the PD AHRS Configuration Management team member to maintain configuration management of both ISM and RFMSS systems. The Contractor shall develop, update and/or maintain the Configuration Management Plan. The plan shall be delivered 30 calendar days after contract award and as required thereafter.

4.5.7 Work with the PD AHRS Information Assurance specialist to ensure the ISM and RFMSS systems meet the information assurance security standards prescribed by Army and DoD regulations and directives.

4.5.8 Consistently apply relevant standards and metrics to increase efficiency and reduce process variation.

4.5.9 The contractor shall support the Government to identify system enhancements required for AHRS ISM/RFMSS systems to attain compliance with virtualization requirements associated with ADCCP.

4.5.10 Maintain new virtualized environment consistent with current contract support in terms of IA patching.

4.5.11 Comply with currently defined PWS and Statement of Objective SOO associated with Contract defined for contract: TBD after award.

4.5.12 The contractor shall develop, update and/or maintain the Software Requirement Specification (SRS) document. The contractor shall deliver the SRS document 30 calendar days before software testing is to begin. The Contractor shall submit SRS with each software test plan. Documentation is to be provided in electronic form.

4.5.13 The contractor shall develop, update and/or maintain the Software Test Report (STR) document. The Contractor shall deliver a draft STR to the Contracting Officer Representative (COR) prior to the start of Software Qualification Testing (SQT). The contractor shall deliver the STR document 30 calendar days after software test completion. The Contractor shall submit STR with each version release. Documentation is to be provided in electronic form.

4.5.14 The contractor shall develop, update and/or maintain the System Computer Operator Manual (SCOM). The contractor shall deliver the SCOM at Government request, as required thereafter. Documentation is to be provided in electronic form.

4.5.15 The contractor shall develop, update and/or maintain the Database Design Documents. The contractor shall deliver the system Database Design Documents at Government request, as required thereafter. Documentation is to be provided in electronic form.

4.5.16 The contractor shall develop, update and/or maintain the System Version Document. The contractor shall deliver the System Version Document draft five calendar days before deployment of each version release. Documentation is to be provided in electronic form.

4.5.17 The contractor shall develop, update and/or maintain the System Design Document. The contractor shall deliver the System Design Document at Government request, as required thereafter. Documentation is to be provided in electronic form.

4.5.18 The contractor shall develop, update and/or maintain the system Interface Design Documents. The contractor shall deliver the system Interface Design Documents four weeks after deployment. Documentation is to be provided in electronic form.

4.5.19 The contractor shall develop, update and/or maintain the BI Publisher Guide. The contractor shall deliver the BI Publisher Guide seven calendar days before deployment and due to the customer the Friday before deployment. Documentation is to be provided in electronic form.

4.5.20 The contractor shall develop, update and/or maintain the AHRS Architecture Framework Documents. The contractor shall deliver the AHRS Architecture Framework Documents 45 calendar days after contract award date, as required thereafter. Documentation is to be provided in electronic form.

4.5.21 The contractor shall develop, update and/or maintain the Security Features Users Guide. The draft Security Features Users Guide shall be submitted to the COR one week before deployment; due to customer the Friday before deployment. Unless otherwise specified, the Government will have a maximum of 10 business days from the end of the performance period or design change to review, make comments and request changes.

4.5.22 CDRL Deliverables for Section 4.5

Configuration Management Plan, CDRL MIL-STD-3046 Software Requirement Specification, CDRL DI-IPSC-81433

Software Test Report, CDRL DI-IPSC-81440 Not 1

System Computer Operator Manual, CDRL DI-MGMT-80368 Database Design Document, CDRL DI-MGMT-81070

System Version Document, CDRL DI-MGMT-80749 System Design Document, CDRL DI-MISC-80749

Interface Design Document, CDRL DI- MGMT-81070

BI Publisher Guide, CDRL DI- MGMT-81070

AHRS Architecture Framework Documents, CDRL DI- MGMT-81644B

Security Features Users Guide, CDRL DI-MCCR-81349

5.0 PERIOD OF PERFORMANCE: The period of performance for this effort shall be one 12 month base period and six 6-month option periods.

6.0 PLACE OF PERFORMANCE: All work shall be performed at the contractor’s facility. The Government anticipates having to meet at the facility for such reasons as on-site quality assurance inspections, task order in-progress reviews, and other applicable surveillance and monitoring activities. The contractor shall provide a suitable computer facility to house the Government Furnished Equipment (GFE) developmental and internal testing servers and comply with Department of Defense (DoD), and Army Information Assurance (IA) directives and regulations. The contractor's site must be established such that the contractor's personnel are able to participate in on-site meetings within two hours of notice.

7.0 PERFORMANCE STANDARD:

Table 1

Acceptable

Unsatisfactory 100% Random Inspection Demonstration Reports

Acceptable

Unsatisfactory 100% Random Inspection/Verify Demonstration Technical Reviews Document Effort Test Readiness Review

8.0 DELIVERABLES/DELIVERABLE SCHEDULE: The Contractor shall provide the deliverables identified in the Contract Data Requirements List (CDRLs) associated with this PWS. Contractor shall adhere to applicable information provided in CDRLs. All deliverables shall be submitted to the COR, unless otherwise agreed upon. Unless otherwise specified, the Government will have a maximum of 10 working days from the end of the performance period or design change to review, make comments and request changes. The contractor will also have a maximum of 10 working days from the day comments are received to incorporate all changes and submit the final design to the Government. All days identified below are intended to be workdays unless otherwise specified. Documentation is to be provided in electronic form.

The Contractor shall accomplish the performance standard date(s) shown in Appendix A, Performance Summary Deliverables.

8.1 Project Management Plan: The contractor shall prepare a Project Management Plan describing the technical approach, organizational resources and management controls to be employed to meet the cost, performance and schedule requirements for this effort. The Project Management Plan shall detail the key activities and milestones, distance learning technology, allocation of staff and other resources necessary for the successful completion of this effort. The COR shall receive the revised Project Management Plan in both hard copy and electronic form, Microsoft Word. Based on the Project Management Plan, the COR will provide approval to move forward on activities planned. The contractor shall request prior approval on all activities not included in the plan or any modifications to the plan after approval has been given.

The contractor shall develop, update and/or maintain the Project Management Plan. The Project Management Plan shall be submitted within 90 calendar days after contract award. Due quarterly thereafter.

8.2 Monthly Reports: The contractor shall document the efforts performed at the completion of each task in a detailed Monthly Status Report due on or before the 20th of each Month. The status report shall include, at a minimum:

8.2.1 Monthly Status Report: Reporting requirements for the monthly status reports will be outlined at the initial Post Briefing meeting. The report shall include, but not be limited to:

· Program status, to include objectives met, work completed and work outstanding

· Notable achievements

· Issues or obstacles impeding progress and recommended solutions

· Status of deliverables/milestones

· Issues and resolutions

· Resource planning/status

· Topics or issues identified by the government COR

· Description of work completed and plans for next month

· Summarize the efforts of each primary task in the Government PWS

· Work Breakdown Schedule

· Meeting Minutes

8.2.2 Monthly Financial Report: Reporting requirements for the financial reports will be outlined at the initial Post Award Briefing meeting the report shall include, but not be limited to:

· Current Budget Cost

· ODC progress/costs

· Schedule

· Invoices

8.2.3 Work Breakdown Schedule: The contractor shall develop, update and/or maintain the Work Breakdown Schedule. The contractor shall deliver the work breakdown on every Monday of each week, or unless otherwise stated by the Government.

8.2.4 Meeting Minutes: The contractor shall develop, update and/or maintain the Meeting Minutes. The contractor shall deliver the Meeting Minutes NLT five calendar days after Monthly Status Report meeting and after any bi-weekly status reports or meetings.

8.3 Final Report: The contractor shall submit a final report to the COR 10 business days prior to contract expiration date. The report will summarize objectives achieved, significant issues, problems and recommendations to improve the process in the future.

8.4 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.

8.5 General Acceptance Criteria: General quality measures, as set forth below, will be applied to each work product received from the contractor under this PWS.

· 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 PWS.

· File Editing ‑ All text and diagrammatic files shall be editable by the Government.

· 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.

· Timeliness ‑ Work Products shall be submitted on or before the due date specified in this PWS or submitted in accordance with a later scheduled date determined by the Government.

8.6 Quality Assurance: The contractor shall develop, update and/or maintain quality control plan. The quality control plan shall be delivered to Government at the Post Award Briefing meeting, then as required thereafter. The COR will review, for completeness, preliminary or draft documentation that the Contractor submits, and may return it to the Contractor for correction. Absence of any comments by the COR will not relieve the Contractor of the responsibility for complying with the requirements of this work objective. Final approval and acceptance of documentation required herein shall be by letter of approval and acceptance by COR. The Contractor shall not construe any letter of acknowledgment of receipt material as a waiver of review, or as an acknowledgment that the material is in conformance with this PWS. Any approval given during preparation of the documentation, or approval for shipment shall not guarantee the final acceptance of the completed documentation.

8.9 CDRL Deliverables for Section 8.0

Project Management Plan, CDRL DI-MGMT-80004 Monthly Status Report, CDRL DI-MGMT-80368A Work Breakdown Schedule, CDRL DI-MISC-80711

Meeting Minutes, CDRL DI-ADMIN-81505 Final Report, CDRL DI-ADMIN-81505

Quality Control Plan, DI-MISC-80711

9.0 GOVERNMENT FURNISHED EQUIPMENT AND GOVERNMENT FURNISHED PROPERTY INFORMATION:

9.1 The Government will provide Government Furnished Equipment (GFE) to include developmental and internal testing servers for this Contract including the required hardware and Commercial Of-The-Shelf (COTS) software licenses for these two applications. The contractor shall provide a suitable computer facility to house the GFE developmental and internal testing servers.

9.2 The contractor must submit requests for replacement of GFE to the COR for processing and approval. Such requests must specify the reason for the replacement request. The Government will not reimburse the contractor for any GFE purchased prior to written approval by the Government.

9.3 The Government may provide Government Furnished Property (GFP), in accordance with FAR Part 45 the transfer of GFP will be recorded on the Scheduled Government Furnished Property (SGFP) pdf form found at http://dodprocurementtoolbox.org/site/detail/id/26 .

9.4 At the request of the Government, or at completion of this effort, the Contractor shall immediately return any GFE or GFP, including any equipment, specialized or off-the-shelf software, and all other property provided by the Government for the Contractor to use to complete this effort.

9.5 Physical Security: The contractor shall be responsible for safeguarding all GFE and GFP provided for contractor use. At the end of normal duty hours and/or after normal duty hours, all Government facilities, equipment and materials must be secured.

10.0 ANTITERRORISM/OPERATION SECURITY

10.1 Anti-Terrorism (AT) Level I Training: All ccontractor personnel requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within three calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The Contractor shall submit certificates of completion for each affected Contractor employee to the COR or to the Contracting Officer, if a COR is not assigned, within four calendar days after completion of training by all personnel. AT Level I awareness training is available at the following website: https://jkodirect.jten.mil/.

10.2 Anti-Terrorism (AT) Awareness Training for Contractor Personnel Traveling Overseas: All United States based contractor personnel and all associated sub-contractors personnel shall comply with Government provided Area of Responsibility (AOR) specific AT awareness training as directed by AR 525-13. Specific AOR training content is directed by the Combatant Commander with the unit Anti-Terrorism Officer (ATO) being the local point of contact.

10.3 Access and General Protection/Security Policy and Procedures: All contractor personnel and all associated sub-contractors employees, with an area of performance within an Army controlled installation, facility or area shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor and all associated sub-contractors employees, shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA, and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

10.4 Threat Awareness Reporting Program: Contractor Employees who require access to Government Information Systems must be registered in the ATCTS at commencement of services, and must successfully complete, per AR-381-12, the DoD Threat Awareness and Reporting Program (TARP) prior to access to the Information System. Contractor personnel shall receive annual TARP training by a Counterintelligence (CI) or other designated trainer as specified.

10.4 Security Requirements: Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

11.0 GENERAL CONTRACTING INFORMATION:

11.1. Contractor Manpower Reporting Requirements: The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for the performance of services provided under this contract including all items and services listed under all the line items 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. Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil.

The information below is not to be included in contract performance work statements

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

Contractors for other than Army components can visit https://cmra.army.mil/Login.aspx to review user manuals and gain an understanding about the data fields that will be included in the reporting structure that is hosted at http://www.ecmra.mil/

11.2 Wide Area Work Flow (WAWF): WAWF is the preferred method to electronically process vendor request for payment. This application allows DOD vendors to submit and track Invoices and Receipt/Acceptance documents electronically. Contractors electing to use WAWF shall (i) register to use WAWF at https://wawf.eb.mil and (ii) ensure an electronic business point of contact (POC) is designated in the System for Award Management (SAM) http://www.sam.gov immediately after award of this contract/order. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

11.3 Post Award Briefing

11.3.1 Within five business days of award, the Contractor shall conduct a Post Award Briefing for the Government. The intent of the briefing is to initiate the communication process between the Government and Contractor by introducing key task participants and explaining their roles, reviewing communication ground rules, and assuring a common understanding of subtask requirements and objectives.

11.3.2 The Post Award Briefing will be held at the Government's facility or another designated location and the date and time will be mutually agreed upon by both parties.

11.3.3 The completion of this briefing will result in the following:

11.3.4 Introduction of both Contractor and Government personnel performing work under this Task Order.

11.3.5 The Contractor shall demonstrate confirmation of their understanding of the work to be accomplished under this PWS.

11.4 Transition In: The Contractor shall develop and provide a Transition-In plan at award of contract. The Contractor shall propose a draft Transition-In Plan as part of the Offeror’s proposal and a finalize Transition-In Plan for the migration of current systems and operations within 10 calendar days of contract award. The Contractor shall conduct a 30 calendar days Transition-In period. The transition shall ensure minimum disruption to vital Government business. The Contractor shall develop the Transition-In plan documentation IAW CDRL listed in paragraph 11.6 below. The Contractor shall ensure no service degradation during and after transition. The Contractor shall develop a Transition-In plan, at a minimum, the following shall be included:

· An overview of the transition effort.

· A Work Breakdown Structure (WBS) with milestones and tasks.

· Description of activities to transition.

· Transition of Government Furnished Equipment (GFE)/ Government Furnished Information (GFI).

· Transition knowledge and information from key Contractor personnel.

· Transition knowledge and information regarding risk or problem areas.

· Direct observation of tasks currently performed on the existing contract.

· Familiarizing personnel with all requirements and procedures.

· Selection of trained and experienced personnel.

· A detailed explanation of potential transition-in period problems and how the Contractor shall address those potential problems.

· The Contractor shall inventory all items of GFE, along with the COR.

· Hardware architecture, operations, and transition baseline documentation.

· Software development environment.

· Software management environment, requirements and Configuration Management (CM) environment.

· Production environment.

· Documentation.

· Inventory.

· Inspections.

· CACs/Badges/ITA Badges.

· FEDEX accounts.

11.5 Transition Out: The Contractor shall develop and provide a Transition-Out plan NLT 60 calendar days prior to contract expiration date. The Transition-Out plan shall facilitate the accomplishment of a seamless transition from the incumbent to an incoming Contractor. The Contractor shall conduct a 30 calendar days Transition-Out period. The Contractor shall develop the Transition-Out plan documentation IAW CDRL listed in paragraph 11.6 below. The Contractor shall identify and coordinate with the incoming successful Offeror and Government personnel to transfer knowledge regarding the following:

· Project management processes.

· Points of contact.

· Location of technical and project management documentation.

· Status of ongoing technical initiatives.

· Appropriate Contractor to Contractor coordination to ensure a seamless transition.

· Transition of key personnel.

· Identify WBS and milestones.

· Identify actions required of the Government.

· Establish and maintain effective communication with the incoming Contractor for the period of the transition via weekly status meetings.

· Transition knowledge and information from key Contractor personnel.

· Transition knowledge and information regarding risk or problem areas.

· The Contractor shall inventory all items of GFE, along with the incumbent and the COR and be prepared to accept the GFE and set up the lab expeditiously at place of performance.

· Hardware architecture, operations, and transition baseline documentation.

· Software development environment.

· Software management environment, requirements and Configuration Management (CM) environment.

· Production environment.

· Documentation (all final documentation in versions shall be received via CDs or DVDs (i.e WORD, PDF, VISIO, EXCEL, PROJECT, etc)).

· Inventory.

· Inspections.

· CACs/Building Badges/ITA Data Center Badges.

· FEDEX accounts.

11.6 CDRL Deliverables for Section 11.0 Army Contractor Manpower Reporting System, CDRL PAL-080-05 Post Award Briefing Meeting, CDRL DI-MISC-80711 Transition In Plan, CDRL DI-ADMN-81505

Transition Out Plan, CDRL DI-ADMN-81505

12.0 DISCLOSURE OF INFORMATION

12.1 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.

12.2 The contractor shall agree to assume responsibility for protecting the confidentiality of Government records, which are not public information. Each contractor employee 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.

13.0 LIMITED USE OF DATA

13.1 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 interest of the Government and/or others.

13.2 Contractor and/or 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 authorize Government personnel or upon written approval of the Contracting Officer. The contractor shall 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 which provides for greater rights to the contractor.

14.0 PRODUCTIVE DIRECT LABOR HOURS: The contractor shall only charge the Government for Productive Direct Labor Hours and are defined as those hours expended by Contractor personnel in performing work under this PWS. This does not include sick leave, vacation, Government or contractor holidays, jury duty, military leave, or any other kind of administrative leave.

14.1 Contractor Interfaces: The Contractor and/or their subcontractors may be required as part of the performance of this effort to work with other Contractors working for the Government. Such other Contractors shall not direct this Contractor and/or their subcontractors in any manner. Also, the Contractor and/or their subcontractors shall not direct the work of other Contractors in any manner. The Government shall establish an initial contact between the Contractor and other Contractors and shall participate in an initial meeting at which the conventions for the scheduling and conduct of future meetings/contacts will be established.

14.2 Work Hours: The Contractor shall support services coverage between the core hours of 8:00 AM - 4:00 PM, Eastern Time, 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 at all times maintain an adequate work force 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 is essential. The COR and the Contractor must mutually agree upon all deviations to this schedule not mentioned herein.

14.3 Authorized holidays for contract personnel performing work at a Government site shall correspond with Government holidays. The Contractor is not required to perform services on the holidays as follows:

Recognized Holidays:

New Year’s Day

Labor Day

Martin Luther King Jr.’s Birthday Columbus Day

President’s Day

Veteran’s Day

Memorial Day

Thanksgiving Day

Independence Day

Christmas Day

14.4 Payment for Unauthorized Work: The Contractor will not receive payments for any unauthorized supplies and/or services or for any unauthorized changes to the work specified herein. This includes any services performed by the Contractor at their own volition or at the request of an individual other than a duly appointed Contracting Officer. Only a duly appointed Contracting Officer is authorized to change the specifications, terms, and conditions under this effort.

14.5 Installation Closures: Announcements of installation closures will be made in the following manner: during normal duty hours, notification will be given through normal chain of command; during non-duty hours, notification will be made through the Office of Personnel Management (OPM) website, local radio, and television channels.

15.0 Contractor Employees: Contractor personnel shall present a neat appearance and be easily recognized as contractor employees by wearing a Security Identification Badges at all times while on Government premises. When Contractor personnel send e-mail traffic, attend meetings, answer phones, and work in other situations where their status is not obvious to third parties they must identify themselves as such to avoid creating the impression that they are government employees.

16.0 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.

17.0 Other Direct Costs / Travel

17.1 Other Direct Costs (ODC’s): ODC’s may be required for this task. Potential ODC’s include travel. All ODC’s will be at cost, no fee included. After award, all ODC’s shall receive government COR approval prior to Contractor’s performance. ODC’s are limited to $2,500, in the event that ODC’s are required over the $2500 threshold, and the items are not on the contractors schedule, the contractor will provide to the COR market analysis documentation for all items that are required to be procured, that have an extended price of $2,500.00 or greater. This information will be provided to the Contracting Officer to make a final determination on procuring the item(s).

17.2 Travel: The contractor shall be reimbursed for actual transportation costs, no fee included, and travel allowances of contractor employee in accordance with FAR 31.205-46 governing travel performed as directed by the contract not to exceed $40,000.00. All travel shall be pre-approved, by the COR, prior to travel. Such transportation costs will not be reimbursed in an amount greater than the cost of, and time required for, coach class scheduled air or ground travel by the most expeditious route, unless coach air or ground travel is not available. All travel itineraries must be approved by PD AHRS. The government shall provide traveling contractor personnel a “Contractor Letter of Identification.” The Contractor shall be reimbursed for non-local travel to provide support at a Government site or other site as may be specified and approved by the COR under this effort.