ITLifecyclePWS_FINAL_05Feb2016_(1).docx

Performance Work Statement for IT Logistics Systems Life Cycle Support Services

Naval Air Systems Command (NAVAIR) Aviation Readiness & Resource Analysis Competency (AD 6.8.4) Naval Air Warfare Center Aircraft Division (NAWCAD)

Table of Contents

1.0 BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 PERFORMANCEREQUIREMENTS

4.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, & SERVICES

5.0 CONTRACTOR FURNISHED ITEMS & SERVICES

6.0 SECURITY

7.0 GENERAL INFORMATION

8.0 DELIVERABLES & DELIVERY SCHEDULE

9.0 PERFORMANCE REQUIREMENTS SUMMARY……………………………………….26

10.0 PROGRAM SECURITY…………………………………………………………………...28

11.0 PERSONNEL QUALFICATIONS………………………………………………………...31

APPENDIX A – LISTING OF SAMPLE SYSTEMS/APPLICATIONS………………………..46

APPENDIX B – DEFINITIONS & ACRONYMS

APPENDIX C – NAVY UNIQUE REQUIREMENTS…………………………………………..50

1.0 BACKGROUND

This Performance Work Statement (PWS) supports the mission of NAVAIR 6.8.4 by providing resources to support internal customers across NAVAIR and external customers in planning, acquisition, and sustainment of Naval Aviation Integrated logistics and industrial support packages and enterprise analysis and planning. NAVAIR 6.8.4 delivers and sustains existing systems and develops new information technology (IT) solutions. This includes many types of services such as applications, networks, data base and data warehousing capabilities.

As part of its mission NAVAIR 6.8.4 is responsible for the definition of authoritative logistics and industrial data sources, and the development and implementation of Naval Aviation product data, item identification and logistics configuration management standards, processes and policies which includes a consolidated set of IT solutions that deliver full lifecycle weapon system logistics and maintenance capabilities via the Naval Aviation Support Process (NASP). Services performed as part of this contract will support all six top level business areas of the NASP. They are: Acquisition, In-Service Support, Wholesale Supply, Depot Maintenance, Fleet Maintenance and retail Supply, and Fleet Operations.

NAVAIR 6.8.4 delivers IT logistic capabilities via a net centric, shared data environment that supports shore based afloat and expeditionary operations, weapon systems and enterprise systems by providing connectivity, data management, data warehousing, data mining, and functional application support. A representative listing of applications and systems are included in Appendix A, Applications/Systems.

1.1 Scope:

This requirement is for Information Technology (IT) Logistics Life Cycle Support for NAVAIR 6.8.4 and its customers. Services include Monthly Financial and Status Reporting; IT Requirements Analysis and Management; Risk Analysis and Management; IT Systems Engineering; IT Design and Development; Test and Evaluation; Quality Control; Data Analysis; Information/Cybersecurity; IT Training; Configuration Management; and IT Operations and Maintenance.

1.2 Description of Services/Supplies:

The contractor shall provide fully trained and certified personnel (in accordance with DoDD 8570.01) to support the scope listed in section 1.1 above.

In addition to supporting all systems/applications in Appendix A, contractors should understand that the information systems and technologies identified herein may be integrated with other systems or retired during the period of performance of this contract. Additionally, the customer base and technologies supported will change and may increase as redundant system consolidations occur and modernization efforts are realized. These events will result in modifications to Appendix A during the life of the contract.

The Contractor shall provide all personnel, equipment, tools, computer technology, materials, supervision, and other items and non-personal services necessary to perform the tasks defined in the PWS; except as specified in Paragraph 4, Government-Furnished Property, Equipment, and Services.

2.0 APPLICABLE DOCUMENTS

The documents included in Appendix C are incorporated herein by reference and made a part of any resulting contract with the same effect as if set forth in full text. Unless otherwise noted elsewhere in the resultant contract, the version of the listed documents in effect on the effective date of the contract shall apply.

3.0 Performance Requirements.

The contractor shall be familiar with DoD, DoN and/or NAVAIR policy and concepts including but not limited to IT consolidation, Functional Area Management (FAM), Navy Networks, Navy Enterprise Licensing agreements, Navy Information Dominance Approval process (NAV-IDAS), and Competency Aligned Organization (CAO). An understanding of these policies and concepts will be required to ensure the stability and continuity of the work force when hiring personnel and during execution of this Performance Work Statement.

The contractor shall display expert knowledge of Naval Aviation Maintenance Logistics, specifically Aircraft, Engine & Maintenance Data. In addition, specific development/maintenance knowledge is required and must be demonstrated in the wide variety of operating system software, utilities, and development applications listed in Appendix A along with an expert level knowledge and capabilities of database design, software development, implementation, operation and maintenance at a minimum with Teradata, Hadoop, SQL Server, Sybase, Cognos, Oracle and Qlikview.

The contractor shall comply with Command initiatives such as legacy application reduction, and shall be performed in accordance with DOD, DON and NAVAIR initiatives, standards, policies, and mandates such as Application Portfolio Management, Defense Business Transformation Guidance, Navy Enterprise Application Developer’s Guide (NEADG), Clinger Cohen Act, Federal Information Security Act (FISMA), Web Enablement, and 508 Compliance. Any systems/applications or tools that will reside on NMCI, Continuity of Services Contract (COSC), Next Generation Enterprise Network (NGEN) or run on these workstations must be certified for NMCI, COSC, NGEN and comply with NMCI, COSC and NGEN policies.

3.1 Data Rights.

The Government will have unlimited rights to all application code and data as well as all supporting documentation for any new or modified software developed under this contract. Additionally, the contractor shall provide the Government unlimited enterprise-wide rights to software used at Government installations.

3.2 Management

The Contractor shall provide a dedicated full time manager who shall be responsible for management and oversight of work performance and personnel for this contract.

The contractor shall:

a) Ensure adequate program controls and repeatable processes are applied to each task area including scheduling, resource allocation, direction, cost quality control, report preparation, establishing and maintaining records and resolution of all issues

b) Resolve quality, timeliness and accuracy issues

c) Review Contract Data Requirements List (CDRLs) for quality before submission to the Government

d) Ensure consistent on-board and off-board processing of personnel

e) Ensure standard communication and processes for each supported organization

f) Coordinate with each project manager to ensure all projects are within cost, performance, and schedule

g) Coordinate effective utilization of resources across projects

h) Manage project risks and dependencies with the performance work statement and within each supported organization

i) Consult with project managers and Government management on IT strategies and IT software life cycle standards

j) Manage long term improvements and efficiencies within the task order

k) Attend status updates with COR/ACOR, TPOC/ATPOC, providing updates on position vacancies, project schedules, issues, and project risks.

l) Attend meetings as required with the COR/ACOR or TPOC/ATPOC to discuss performance under the award or resolution of any performance issues or challenges.

This manager is not delegated any inherently Governmental authority.

The Contractor shall provide a Program Management Plan IAW DI-MGMT-81797 (CDRL A001).

3.3 Monthly Status and Financial Reporting

The Monthly Status Report includes, at a minimum, status for each project being worked; including technical progress made; schedule status; a monthly metrics assessment; identified risks including probability, impact and mitigation recommendations; projects and/or deliverables funded and date they were funded including type of funding and expiration; travel conducted, meetings attended including action items and outcomes; equipment/materials procured and excess equipment/materials if any. The Monthly Financial Status Report (MSR) is intended to report on cost, schedule, and performance against Performance Work Statement (PWS) requirements, providing information at the individual project level. As such, it will identify task expenditures, planned versus actual, funding compared to ceiling, labor categories and actual versus planed hours at the individual project level.

The contractor shall provide Monthly Status Report IAW DI-MGMT-80368A (CDRL A002) and Monthly Financial Report IAW DI-FNCL-80331A (CDRL A003).

3.4 IT Acquisition Lifecycle Requirements Analysis

The Contractor shall assist in the improvement and execution of Acquisition Lifecycle Planning Requirements Management, analysis, tracking and traceability process(s). Requirement activities shall be planned, tracked and reported within a NAVAIR 6.8.4 approved automated tool. The contractor shall follow NAVAIR 6.8.4 configuration management and change management policies, practices and procedures including providing a requirements traceability structure for Government review and approval.

The contractor shall provide Analysis Results Report(s) IAW DI- MISC-80508B (CDRL A004).

3.5 IT Acquisition Lifecycle Risk Management

The Contractor shall perform Acquisition Risk management and assessment activities for all NAVAIR 6.8.4 acquisition programs, systems/applications. Risk management activities shall include risk identification, tracking in a NAVAIR 6.8.4 automated tool, evaluation, prioritization, and mitigations. The Contractor shall review, improve and provide recommendations for Government review/approval to enhance NAVAIR 6.8.4’s Acquisition Risk Management program. The Contractor shall perform tradeoff analysis utilizing Cost as an Independent Variable (CAIV) principle. The Contractor shall utilize a disciplined methodology for conducting thorough program/project risk assessments. The Contractor shall produce documentation containing the assessed and prioritized risks including probability and impacts. The Contractor shall also document potential and practical mitigation plans for each of the major risks uncovered during the risk assessment.

The contractor shall provide Risk Assessment(s) IAW DI-MGMT-81809 (CDRL A005).

3.6 Federal Information System Controls Audit Manual (FISCAM)

The Contractor shall provide IT support for tasks and activities related to FISCAM processes. FISCAM is consistent with National Institute of Standards and Technology’s (NIST) guidelines for complying with the Federal Information Security Modernization Act of 2014 (FISMA). This requires federal agencies to develop, document, and implement agency-wide programs to ensure information security. At a minimum the Contractor shall perform the following:

Participate in FISCAM assessment meetings. Provide technical expertise on system procedures in response to FISCAM auditors or assessment team questions. Participate in walkthroughs of system procedures with assessors and auditors. Participate and support testing of FISCAM controls. Update system documentation and/or system procedures in response to FISCAM Corrective Action Plans (CAPs).

The Contractor shall provide IT System Program Documentation IAW DI-IPSC-80942 (CDRL A006).

3.7 IT Systems Engineering (SE)

3.7.1 The contractor shall provide support for IT Systems Engineering phases for NAVAIR 6.8.4 Aviation Logistics IT systems/applications and tools. The contractor shall provide support for the following IT System Engineering activities: Planning including Schedule; Technical Performance Measures/Metrics; Requirements including translation of operational needs and capabilities into effective solutions; Change Processes; System/application design; Development based on Government reviewed/approved design and industry best practices; Technical Readiness Reviews; Unit and integration Testing; Implementation of Government approved systems/applications and tools; Operation and Maintenance of IT Logistics systems/applications and tools. The contractor shall gather and analyze, design, develop, test and implement requirements for the continued integration of legacy IT Logistics systems as well as support modernization efforts for systems/applications and tools. The contractor shall support Information Assurance/Cyber Security compliance and mitigations throughout the SE process as well as Navy Functional Area Manager (FAM) compliance, migrations, consolidations and system retirements.

3.7.2 The Contractor shall support planning, requirements management, interface management, risk management, configuration management, technical data management, technical assessment and decision analysis for NAVAIR 6.8.4 IT Logistics systems/applications and tools.

3.7.3 The Contractor shall develop enterprise artifacts for DoD Architecture Framework (DoDAF) views and artifacts for the reference model to include but not limited to the following: OV-1, OV-2, OV-3, OV-4, OV-5a, OV-5b, SV-1, SV-4, SV-6, SVC-06, Stdv-1, and StdV-2. The contractor shall research and develop artifacts for the Reference Model to include: AV-1, AV-2, CV-2, DIV-2, OV-6a, OV-6c, SV-2, SV-5, SV-6 based on the current SV-1

3.7.4 The Contractor shall support the development of new and improvement of existing documents including technical / functional management plans / configuration management documents, version description documents, data dictionaries and manuals, end-user manuals, system engineering plans and other IT system/application required documentation. The Contractor shall also participate in program technical and functional reviews and audits for NAVAIR 6.8.4 systems/applications, programs and projects.

The Contractor shall provide IT System Program Documentation IAW DI-IPSC-80942 (CDRL A006).

3.8 IT Systems Requirements Management

3.8.1 The Contractor shall provide program and system requirements definition and analysis support including translation from functional (the end user can statements) into technical design and system specifications. The Contractor shall facilitate requirements definition sessions and reviews of processes and products. The Contractor shall provide requirements management traceability support. The Contractor shall document and maintain detailed functional requirements relative to the solution. The Contractor shall trace requirements to target system functionality. As part of the traceability analysis, the Contractor shall correlate each functional requirement against the ability of the target system to meet overall functional requirements. The analysis shall indicate the degree of compliance with the functional requirements. The contractor shall include calculations using Government reviewed/validated and approved algorithms, data elements and authoritative data sources. The contractor shall support integration of legacy systems/applications, system/application fixes, system/application upgrades, enhancements, modifications and for NAVAIR 6.8.4 modernization efforts. The contractor shall record, update and track all requirements in a NAVAIR 6.8.4 approved automated tool.

3.8.2 The contractor shall provide support to establish requirements for gathering data from authoritative sources; identifying and updating interfaces to provide a near real time update and feed of data for all NAVAIR IT Logistics data repositories/warehouses. The contractor shall gather, identify, document and track in a NAVAIR 6.8.4 approved automated tool all NAVAIR 6.8.4 system/application requirements, including algorithms; recommending authoritative sources. The contractor shall compare new/updated algorithms with algorithms currently used, ensuring consistency and identifying discrepancies.

3.8.3 The contractor shall analyze and provide assessments of the NAVAIR 6.8.4 IT Logistics systems/application’s documented functional, technical and system requirements for clarity, potential problems, risks, and feasibility concerns.

3.8.4 The contractor shall work with end-users and other stakeholders to define, document and track in a NAVAIR 6.8.4 approved automated tool Agile and Hybrid development effort requirements for clarity, potential problems, risks and feasibility.

The Contractor shall provide IT System Program Documentation IAW DI-IPSC-80942 (CDRL A006).

3.9 Gap/Data Analysis

The contractor shall provide support for NAVAIR 6.8.4 IT Logistics systems/applications and tools by conducting research and analysis to assess the differences between requirements and IT Logistics systems functions and capabilities. The Contractor shall conduct research and analysis to validate data, data elements, database views and schemas in IT Logistics systems and ensure the data and all data characteristics meet applicable specifications and requirements. Using Information from the Gap/Data Analysis, the Contractor shall conduct lessons learned analysis and document findings.

The Contractor shall provide Gap/Data Analysis Results/Recommendations IAW DI-MISC-80508B (CDRL A007).

3.10 System/Application and Interfaces, Design and Development

3.10.1 The contractor shall provide support for NAVAIR 6.8.4 IT Logistics systems/applications and tools by gathering existing diagrams on the infrastructure; update data flow diagrams recommending data flow; and ensure there is an accurate inventory of IT components required to implement the proposed design (i.e. gap analysis).

3.10.2 The contractor shall identify and develop detailed standardized specifications for screens, Web pages, files, and reports. Once the design is approved by the Government Program/Project lead, the contractor shall begin code updates per the Government approved POA&M.

3.10.3 The contractor shall provide support in data warehouse design methodology; data warehouse design best practices; development techniques for analytical applications; performance tuning; partitioned primary indexes; encryption; transactional processing; data management principles; network management; industry best practices for effective and efficient database queries; and troubleshooting techniques.

3.10.4 Once the NAVAIR 6.8.4 IT Logistics systems/applications or interface requirements are approved by the Government Program Manager, the contractor shall develop the schedule using industry best practices for system/software design and development. Efforts will include initial system/application design, system/application development, mobile applications design/development, interfaces design/development, code enhancement/modification/updates, test, and implementation processes. The contractor shall develop a Plan of Action and Milestones (POA&M) to fourth level tasks for Government review/approval.

3.10.5 Once the NAVAIR 6.8.4 IT Logistics systems/applications Government approval is received for the POA&M, efforts and all tasks associated with the approved POA&M will begin. The contractor shall provide program/project reviews per the Government approved POA&M including at a minimum: overall status of cost, scope and schedule; actual versus planned progress; actual versus planned expenditures; risks assessment; risk mitigations; quality control efforts; change management status; next steps and any other relevant information.

3.10.6 If/when there are requests for changes and/or modifications to previously approved requirements the contractor shall use the Software Change Request (SCR) process including documenting the changes in the NAVAIR 6.8.4 approved automated tool for Configuration Control Board (CCB) Government review/approval.

3.10.7 If/when the changes to previously approved requirements are approved by the Government Program Manager/CCB, the contractor shall develop new or update existing schedules using industry best practices for system/software design and development. Efforts will include initial system/application design, system/application development, mobile applications design/development, interfaces, code enhancement/modification/updates, test, and implementation processes. The contractor shall develop a Plan of Action and Milestones (POA&M) to fourth level tasks for Government review/approval.

3.10.8 The contractor shall research, investigate and provide pros/cons for the Government program/project manager to review/approve for the use of one of the following software development methodologies: Agile, Hybrid, Prototyping, Incremental, Spiral or Waterfall.

The Contractor shall provide IT System Program Documentation IAW DI-IPSC-80942 (CDRL A006). The Contractor shall provide Computer Software products and documentation, compiled and uncompiled code IAW DI-IPSC-81488 (CDRL A008). The Contractor shall provide Plan of Action and Milestones IAW DI-MGMT-81117 (CDRL A009).

3.11 Test and Evaluation

3.11.1 For integration of legacy systems or for research for new NAVAIR 6.8.4 solutions, the contractor shall perform unit testing, system and integration testing as required after modifications have been completed. Items being tested shall not be modified until the final modification review is conducted and approved by the 6.8.4 Government project lead and stakeholders.

3.11.2 The contractor shall develop Test Plans for all approved software and hardware changes related to legacy system integration and/or new NAVAIR 6.8.4 solutions.

3.11.3 When updating, improving, or enhancing existing NAVAIR 6.8.4 systems the contractor shall perform unit testing, system and integration testing as required when code modifications have been completed and approved by the Government.

3.11.4 The contractor shall develop Test Plans for all approved system/application, software, interface and hardware changes related to updating, improving, or enhancing existing NAVAIR 6.8.4 systems.

The Contractor shall provide Test and Evaluation documentation IAW DI-NDTI-81284 (CDRL A010).

3.12 Quality Assurance/Validation

3.12.1 The contractor shall follow their Quality Control Plan and implement quality assurance when developing new or when updating, improving, or enhancing existing NAVAIR 6.8.4 systems. Quality Assurance will ensure that the deliverables and products meet the requirements, specifications and intended purposes to ensure delivery of quality products. The contractor shall use automated tools to test

3.12.2 The contractor shall perform unit testing, system and integration testing as required for fixes, upgrades, and modifications. The contractor shall inform the Government before testing begins.

3.12.3 The contractor shall develop and maintain Test Plans for all Government approved software and hardware changes.

3.12.4 Once customer acceptance testing is complete and all issues are resolved to the Government program/project manager’s satisfaction; and upon Government final approval, the contractor shall begin implementation of the tested and approved item(s).

The Contractor shall provide Test and Evaluation documentation IAW DI-NDTI-81284 (CDRL A010).

3.13 Cyber Security (CS)/Information Assurance (IA)

3.13.1 Cyber Security/IA shall include activities related to the entire field of IA (availability, identification and authentication, confidentiality, integrity, nonrepudiation), and include economic considerations with respect to selection of techniques, processes, and emerging industry trends in the application of CS/IA technologies, processes, and procedures as they relate to NAVAIR 6.8.4 IT Logistics systems/applications. The contractor shall assure compliance with all DoD/DON CS/IA policies and relevant guidance and approval requirements/processes as they relate to security certification and accreditation guidelines for NAVAIR 6.8.4 systems/applications in development, test, integration and operational/production environments.

3.13.2 The contractor shall support CS/IA standards, such as, DoD Information Assurance Certification and Accreditation Process (DIACAP), Department of Defense Risk Management Framework (DODRMF), Clinger Cohen Act (CCA) Compliance, Federal Information Security Management Act (FISMA) compliance and system inventory requirements. In addition, adherence to Office of Management and Budget (OMB), National Security, Chairman of the Joint Chiefs of Staff, Department of Defense and Service guidance is required. The Contractor shall support analyses for NAVAIR 6.8.4 IT Logistics systems/applications from a security or vulnerability perspective.

3.13.3 The contractor shall provide classified and unclassified programs, systems and networks security compliance actions as mandated by information assurance vulnerability management (IAVM) notices, bulletins, and other documentation, support security requirements definition, provide Navy Validator and certification reports, and reports on certification and accreditation IA requirements and status per Government approved POA&M.

The Contractor shall provide Information Assurance/Cyber Security documentation IAW DI-MGMT-82002 (CDRL A011).

3.14 Configuration Management (CM)

3.14.1 The contractor shall adhere to the NAVAIR 6.8.4 Configuration Management Plan, Software and System Change Management Processes.

3.14.2 The contractor shall maintain integrity of all products utilizing commercial best practices and tools. This support shall include updating CM plans, policies, and procedures documents, building and maintaining documentation libraries, and updating guidelines and practices after Government review and approval.

3.14.3 CM support services shall also include implementation and operation services for CM (or program related) software tools. The Contractor shall ensure a managed discipline is in place to identify the as proposed (to-be) and implemented configuration (initial baseline for new items) of a system at discrete points in time. The Contractor shall systematically record and trace changes to all system components (conceptual and physical) including configuration identification, control, status accounting and audits. The Contractor shall use the NAVAIR 6.8.4 approved CM tools for controlling and tracking changes and who made the changes, building of software releases including storage of compiled and uncompiled code, Government identified configuration items, and all Performance Work Statement related documents. The Contractor shall, throughout the lifecycle, ensure CM items can be verified by the Government via auditing and reporting.

The Contractor shall provide Configuration Management Documentation IAW DI-MGMT-80858C (CDRL A012).

3.15 Operations and Maintenance

3.15.1 The contractor shall provide operations and maintenance support to include System, Database and Application/software administration, System, Database and Application/software security including System, Database and Application/software tools and utilities identified in Appendices B & C.

3.15.2 Database administration includes but is not limited to the following tasks and activities:

· Install, configure and upgrade databases and associated software tools

· Plan for and deploy database upgrades and migrations in coordination with Government project leads and other service providers

· Tune and optimize queries, processes, and databases

· Implement database file organization and parameter settings

· Automate and manage monitoring activities

· Define, configure and manage allocation groups and priority scheduler for throttling run-away queries and processes

· Develop, monitor, update database backup and recovery processes as directed by the Government program/project lead and test database backup and recovery processes per Government approved schedule

· Perform database capacity planning and growth analysis that includes calculating disk space requirements for database tables and indexes

· Monitor and record database space and notify Government POC when 65% capacity is reached

· Monitor and record utilization and provide input to health reports

· Manage and maintain performance with associated utilities and notify the Government POC (associated program/project) when issues are found

· Provide coordination, management, and performance of application and database patches and upgrades associated with DoD, DoN, Information Assurance, and Functional Area Manager policies, directives, and mandates, ensuring Government approval is received prior to implementation of patches and upgrades.

· Collaborate with the Application/software, web and server administrators to resolve any issues that may arise during the planning and execution of installations and configuration changes

· Design, manage, monitor and maintain database access for all database accounts

· Support database user accounts (creation, maintenance and removal)

· Produce, manage, and maintain database disaster recovery plan and update to reflect changes

· Document proper startup, shutdown, backup, recovery, database creation, database configuration in Operations Procedure Manuals

3.15.3 Application/software, web and server administration includes but is not limited to the following tasks and activities:

· Conduct Security Assessments in accordance with NIST SP 800-30 and harden in accordance with STIGs and National Security Agency (NSA) Security Recommendation Guide (SRG) policies

· Provide support for Cyber Security (CS)/ Information Assurance (IA) compliance efforts to maintain Authority To Operate (ATO)

· Collaborate with the database administrators to resolve any issues that may arise during the planning and execution of installations and configuration changes

· Ensure that all tasks and customer issues are documented in NAVAIR 6.8.4 approved automated tool

· Maintain Privileged Access Authorization for required personnel

· Resolve vulnerabilities identified through system scans.

· Plan and execute new application deployments.

· Follow code promotion processes for moving code from development/test/staging/production environments as required.

· Provide file and system security management, log analysis, and statistical report generation as required.

· Provide Tier 2 and 3 Help Desk support for NAVAIR 6.8.4 applications

· Provide new features implementation and management of de-supported features

· Configure, create and manage all environments as approved by the Government

· Administer physical and virtual servers with a large variety of operating systems

· Administer a large variety of systems/applications (representative list: Cognos Business Intelligence, QlikView, ColdFusion, SLICwave, LiveLink, AppDynamics, NetVault, StarTeam,.NET, Java, JavaScript, WSUS, xHTML, PHP, ASP, CGI, CGS, SSL, SSH, and SFTP)

· Perform installations, upgrades, configuration, tuning and sustainment of web and application servers in compliance with FAM, cyber security (CS) and IA policies and regulations

3.15.4 Transition Planning. The Contractor shall support legacy transition planning and implementation. Support shall include various analysis and assessments such as business process gap- fit assessments and analysis of alternatives.

3.15.5 Retirement Planning. The Contractor shall conduct various analysis and assessments, provide recommendations and support overall system retirement planning. The Contractor shall support and execute system retirement activities in accordance with all legal and regulatory requirements. The Contractor shall provide Technical Report-Study/Services Documentation/IT Retirement Documentation

3.15.6 Data Conversion / Migration. The Contractor shall conduct planning and perform data validation in preparation for data conversion. The Contractor shall support data conversion and data movement from legacy or other systems to the target application and/or an archived or data warehouse system. The Contractor shall perform data validation and reconciliation of transitioned data.

3.15.7 Web Support. The Contractor shall provide Web Services support. Contractor support shall include assisting in the design, development, maintenance and operation of web sites and applications in accordance with mandatory security / compliance requirements. The Contractor shall provide Request for Engineering or Technical Assistance Documentation/Web Support.

The contractor shall provide Operations and Maintenance reports IAW DI-MISC-80508B (CDRL A013). The contractor shall provide Technical Reports/Services IAW DI-MISC-80508B (CDRLs A014).

3.16 Security: Operational Security (OPSEC) for Off-site

If applicable, the contractor shall implement and maintain a facility level OPSEC program to protect controlled unclassified information to be used by the contractor off-site during the performance on this contract. Contract data requirements list (CDRL) and data item description (DID) attached. The OPSEC plan shall be submitted to NAVAIR and ACC-NJ within 90 days of contract award for acceptance and approval Contractor shall mail preliminary draft OPSEC Plan in MS Word 6.0 (or later) on Compact Disc and hard copy to: Commander, Attn: 7.4.3, B463 Unit 10, 22514 McCoy Road, Patuxent River, MD 20670-1457. The final plan is due 45 days after Government approval (NAWCAD 7.4.3) of draft. While performing aboard NAVAIR sites, the contractor shall comply with the provisions of OPNAVINST 3432.1 for Operations Security; at all other sites, the contractor shall comply with the local command and/or program OPSEC plan(s).

The Contractor shall provide OPSEC plan IAW DI-MGMT-80934C (CDRL A015).

3.17 System Documentation.

The Contractor shall develop new and update existing DoD, DoN and NAVAIR required system documentation throughout the IT lifecycle. Documentation may include but is not limited to preliminary and detailed application designs, Initial Capabilities Document (ICD), Capability Development Document (CDD), Operational Requirements Document (ORD), requirements traceability matrices (RTM), System / Subsystem Design Document (SSDD), Software/System Requirements Specifications (SRS), System Engineering Plans (SEPs), , Interface Management Descriptions (IMD), User Interface Design Descriptions (UIDD), Database Design Description (DBDD), Entity Relationship Diagrams (ERDs), Data Dictionaries (DDs), software tests plans, test scenarios, test reports, acceptance test descriptions, Software User’s Manuals (SUM), Installation plans Computer Programmer Manuals (CPM), and Operators Procedure Manuals (OPM). Documentation may also consist of various briefs and/or materials presented or discussed at reviews.

The Contractor shall provide IT System Program Documentation IAW DI-IPSC-80942 (CDRL A006).

3.18 Training

3.18.1 The Contractor shall provide technical analysis reviews and recommendations in support of NAVAIR IT Logistics systems training. This includes classroom, computer-based instruction, videotape, distance learning, and other forms of instruction to augment other training programs and systems.

3.18.2 The Contractor shall develop presentations and other training materials. Provide training instructors and training materials, to include electronic media, and computer based training (CBT) to train end users in support of NAVAIR IT Logistics systems. The Contractor shall develop training plans as specified.

The Contractor shall provide IT Training Documentation and media IAW DI-MISC-80508B (CDRL A016).

3.19 Transition Tasks

The contractor shall develop a Transition-Out Plan that shall facilitate the accomplishment of a seamless transition from the incumbent to incoming contractor/Government personnel at the expiration of the contract. The contractor shall provide a Transition-Out Plan NLT sixty (60) days prior to expiration of the contract. The contractor shall identify how it shall coordinate with the incoming and or Government personnel to transfer knowledge regarding the following:

j. Transition Out Plan shall include, but is not limited to:

7. Orientation phase and program to introduce Government personnel, programs, and users to the contractor’s team, tools, methodologies, and business processes

Upon receipt of Government approval of the Transition-Out Plan, the contractor shall execute.

The Contractor shall provide Transition Out Plan IAW DI-MISC-80508B (CDRL A017).

3.20 Quality Control Plan

The contractor shall develop and implement procedures to identify, prevent and ensure non-recurrence of defective services and software. The contractor’s quality control program shall be a plan that ensures the contractor is adhering to the terms and conditions of the contract and how the contractor plans to maintain accountability including any sub-contractor effort performed in conjunction with this PWS.

The contractor shall provide Quality Control Plan IAW DI-FED-STD-368A (CDRL A019).

4.0 Government Furnished Property, Equipment, Information and Services

The Government reserves the right to provide Government Furnished Equipment, information on an as needed basis.

4.1 Safeguarding Software Licenses and Intellectual Property

The Contractor shall identify, prior to award of the contract to the best of its ability, noncommercial and commercial technical data and computer software that it intends to deliver with restrictions on the Government's right to use, release or disclose such identified technical data and/or computer software (see DFARS 252.227-7017). The Government further requires that the Contractor identify, prior to award of affected Task Order(s), background inventions that will be embodied in items, components, processes, technical data, computer software or computer software documentation developed or delivered under the Task Order. To identify such technical data, computer software and background inventions, the Contractor shall submit the following three lists:

a. Noncommercial Computer Software and Technical Data.

The Government desires appropriate rights in all noncommercial technical data and noncommercial computer software developed or delivered under each Task Order. The Contractor shall identify all asserted restrictions on the Government's license rights in such data and software, pursuant to paragraph (e) of the clauses at DFARS 252.227-7013 ('7013) and DFARS 252.227-7014 ('7014). The '7013 and the '7014 clauses shall govern the format and content of the Contractor's assertions of software and data restrictions for each Task Order. The Contractor may combine the '7013(e) and the '7014(e) post-award lists into a single list, as long as the technical data items can be clearly distinguished from the computer software items. The Contractor shall submit the post-award assertions to the Contracting Officer as soon as practicable before the scheduled delivery of the relevant data and/or software. The Contract shall update the post-award assertions as necessary during performance of the contract to ensure that the list is accurate before making final delivery of data or software.

b. Commercial Computer Software and Technical Data.

The Contractor shall identify all asserted restrictions on the Government's license rights in commercial computer software and commercial technical data. To identify such restrictions, the Contractor shall submit a Commercial Restrictions List, dated and signed by an official contractually authorized to obligate the Contractor, as an attachment to the affected Task Order. The format of the Commercial Restrictions List shall be substantially same as the format set forth in DFARS 252.227-7017(d).

The Commercial Restrictions List shall include the assertions of the Contractor's sub-Contractors or suppliers or potential sub-Contractors or suppliers. For each entry in the Commercial Restrictions List which indicates that the asserted rights category is a special license or the license customarily provided to the public, the Contractor shall attach to the Commercial Restrictions List a copy of such license, except that if any particular license is identified as applying to more than one such entry, only one copy of that license need be provided. The Contractor shall update the Commercial Restrictions List as necessary during performance of the contract to ensure that the list is accurate before making final delivery of data or software.

c. Delivery of Noncommercial Computer Software and Technical Data.

Unless expressly otherwise stated in the Task Order, the Contractor's deliveries of noncommercial technical data shall include physical delivery of the digital version of that technical data. The Contractor's deliveries of noncommercial computer software shall include physical delivery of a digital version of both the executable code and the annotated source code. This includes noncommercial data/software that was developed exclusively at private expense. As used in this paragraph, "physical delivery" means submission to the Government.

4.3 Contractor Acquired Material/Property

Any purchased material shall become the property of the Government upon acceptance under the TO in accordance with the “Government Property” clauses in the basic contract and shall be accounted for and maintained pursuant to that clause. Software integrity shall be maintained by the Contractor within the licensing agreement of the producer until such software is delivered to the Government, or otherwise disposed of in accordance with Government direction. The Contractor shall document the transfer of the materials in the monthly status report and appropriate Government documentation. The Contractor shall obtain advance approval for the purchase of material from the COR/ACOR and TPOC/ATPOC. The Contractor shall not purchase any software or IT equipment on behalf of NAVAIR in support of this contract without a NAVAIR Command Information Officer (CIO) assigned “IT” approval.

For all material requirements greater than $15,000, concurrence must be obtained from the TPOC/ATPOC and approval must be obtained from the COR/ACOR/PCO prior to purchase. The contractor shall provide at least 3 vendor quotations as a part of the approval process for purchases greater than $15,000 (CONUS).

5.0 CONTRACTOR FURNISHED ITEMS & SERVICES

Except for those items specifically stated to be Government Furnished Property, the Contractor shall furnish everything required to perform contract requirements. Any purchased material shall be in accordance with the “Government Property” clause in Section H and I of the solicitation/contract and shall be accounted for and maintained pursuant to those clauses. Software integrity shall be maintained by the Contractor within the licensing agreement of the producer until such software is delivered to the Government, or otherwise disposed of in accordance with Government direction.

6.0 SECURITY

6.1 Personnel Security Requirements: Contractor personnel performing IT sensitive duties are subject to investigative and assignment requirements. The Contractor will initiate the appropriate level of security clearance background investigation to result in issuance of up to a Top Secret security clearance, if required. Information gathered, developed, analyzed, and produced under this PWS remains the property of the US DoD and shall be protected from unauthorized or inadvertent modification, disclosure, destruction, or use. Prior to the arrival of any Contractor employee to commence work under this contract at any Government site, the Contractor must provide advance notice to the Government for visitor control purposes and verification of security clearance.

DoD Information Assurance regulations requires active duty military, DoD civilian, DoD consultants, and support Contractor personnel requiring access to and performing work on DoD sensitive automated information systems (AISs) to be assigned to positions which are designated at one of three sensitivity levels (IT – I, IT – II, or IT – III). These designations equate to Critical Sensitive and Non-Critical Sensitive positions. The employing Contractor will ensure individuals assigned to these sensitive positions have completed a System Authorization Access

Request (SAAR), OPNAV 5239/14 (Rev 09/2011), and/or other appropriate access request forms as prescribed by the individual DoD agency. Personnel requiring access to ISs to fulfill their duties must possess the required favorable security investigation, security clearance, or formal access approvals, Information Assurance Training and fulfill any need-to-know requirements.

The work to be performed under this contract as delineated in the DD Form 254, Attachment No. 02, involves access to and handling of classified material up to and including SECRET.

The Government retains the right to request removal of Contractor personnel, regardless of prior clearance or adjudication status, whose actions while assigned to this contract conflict with the interests of the Government. The reason for removal will be fully documented in writing by the Contracting Officer.

6.2 Physical Security: The Contractor shall be responsible for safeguarding all Government property provided for their use. At the end of each work period, all Government facilities, equipment, and materials shall be secured. The Contractor shall establish and implement methods to ensure keys issued are not lost, misplaced, or used by unauthorized persons. The Contractor shall not duplicate any keys issued by the Government.

6.3 Non-Disclosure Agreements. In the performance of the contract, the contractor may have access to non-public proprietary information. The contractor shall require that any employee performing services under the contract a Non-Disclosure Agreement (NDA). The NDA shall acknowledge the contractor and employees’ duties and promise to comply with those obligations. A copy of the executed NDA shall be provided to the PCO and Government COR.

7.0 GENERAL INFORMATION

7.1 Hours of Operation / Principal Place of Performance.

Work in support of this PWS shall be primarily performed at Patuxent River, MD, with a small percentage (approximately 10%) which may be located in Lakehurst, NJ; Norfolk, VA; Cherry Point, NC; Fort Worth, TX; and San Diego, CA. However, the place of performance is not limited to the above locations due to the evolving, integrated and capability-focused requirements throughout NAVAIR.

The contractor shall ensure the stability and continuity of the work force when hiring personnel and executing this Performance Work Statement. The contractor shall at all times maintain a highly skilled professional work force for the uninterrupted performance of all defined tasks.

7.1.2 Normal daily coverage for contractor support services consists of coverage for Core Business Hours. When critical system failures or other emergencies occur the contractor will work with the Government representative to make advance arrangements to provide support during Core Extended Hours and/or Critical Systems Extended Hours. Currently hours of support are as follows:

a) Core Business Hours are defined as Monday through Friday from 0700 to 1700 ET with the exception of non-east coast locations which would use their time zone (excluding Federal holidays).

b) Core Extended Hours are defined as Monday through Friday from 1701 to 2000 ET with the exception of non-east coast locations which would use their time zone (excluding Federal holidays).

c) Critical Systems Extended Hours are defined as Monday through Friday from 2001 to 0659 ET with the exception of non-east coast locations which would use their time zone and Saturday, Sundays and Federal holidays from 0000 to 2359.

The Government is willing to consider alternative support scheduling, as long as; the contractor ensures maximum coverage and incident response.

7.1.2.1 Contractor work schedules shall be coordinated with the Technical Point of Contact/Alternate Technical Point of Contact (TPOC/ATPOC) to ensure: 1) coverage during critical periods, coverage for operational projects, and critical tasking, 2) coordination of tasks involving other contractors, and 3) security compliance for buildings/areas where access is controlled.

7.1.2.2 Compressed Work Schedule (CWS) is not authorized without prior approval by the COR and TPOC for each specific task area. CWS will only be authorized if there is no impact to services or staffing requirements. The contractor will comply with NAVAIRINST 12620.1 dated October 23, 2012, Compressed Work Schedule.