Draft_PWS.docx

Performance Work Statement

Date: 16 October 2018

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

Scope This Performance Work Statement (PWS) supports the mission of Naval Air Systems Command (NAVAIR) to maintain fleet production readiness by satisfying a requirement for integrated Program Management Office (PMO) and Functional Manager (FM) support. This support operates independently from system developers and system integrators responsible for delivering Information Technology (IT) products to the command. The PWS also supports Department of Navy (DoN), Headquarters Marine Corps (HQMC), United States Fleet Forces Command (USFF), and Program Executive Office – Enterprise Information Systems (PEO-EIS) IT initiatives which align with NAVAIR PMO IT objectives or supports command level fleet readiness initiatives. This requirement fosters an integrative conduit of Enterprise IT support services including IT strategic planning, acquisition program management, Business Process Reengineering (BPR), IT lifecycle management, and integrated logistics support. This PWS elicits support for functional management governance of NAVAIR IT Initiatives and focuses on enterprise level program management for the NAVAIR Strategic Vision SV2020 Initiatives and the Aviation Logistics Enterprise (ALE) inclusive of the following Commodity Lines: Product Data Management (PDM) and Product Lifecycle Management (PLM), Tactical Maintenance and Operations (TMO), Data Warehouse and Decision Support, and Enterprise Services and Infrastructure. Additional management governance support will include the Marine Aviation Logistics – Enterprise IT (MAL-EIT) Family of Systems (FoS) and the Naval Operational Business Logistics Enterprise (NOBLE) Family of Programs including the Naval Aviation Maintenance System (NAMS).

This PWS provides for integrated lifecycle management activities for Project, Program and Portfolio Management; IT Management and Strategy; IT Compliance; Cybersecurity; Aviation Logistics; BPR; Requirements Management and Analysis; Testing and Evaluation; Systems Engineering; Data Modeling and Analysis; Integrated Product Support; Business Analysis; Systems Implementations; Facilitation; and Training. Definitions and acronyms are contained at Appendix A. Personnel supporting this PWS shall have a working knowledge of Organizational, Intermediate, and Depot (O, I&D) levels of Maintenance and Naval Aviation Maintenance Automated Information Systems (AIS).

Applicable Documents

2.1 Department of Defense specifications

2.1.1 DoD 5220.22-M, National Industrial Security Program Operating Manual, (NISPOM) 28 Feb 2006.

2.1.2 SECNAV M-5510.36, Information Security Program, 30 Jun 2006.

2.1.3 DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 (enclosure 3 pages 11-18) 24 Feb 2012.

2.1.4 DoD 5400.7-R, Freedom of Information Program Chapter 3 (pages 31-42) Sep 1998.

2.1.5 DoDD 5230.24 Distribution Statements on Technical Documents, Change 1, Effective 28 Apr 2016.

2.1.6 SECNAV M-5510.30 Personnel Security Program Jun 2006.

2.1.7 OPNAVINST 3440.17A Navy Installation Emergency Management Program, 1 Aug 2014.

2.1.8 DoDI 5000.75 Business System Requirements and Acquisition

2.2 Industry Documents

2.2.1 International Organization for Standards (ISO) Standard-9001-2015 Requirements

3.1 General Requirements

3.1.1 Compatibility

The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government IT environment through the security classification of Secret. The current operating environment required for this contract includes:

· Microsoft Windows 10

· Microsoft Project 2010

· Microsoft Visio 2010

· Microsoft Office Professional Plus 2016

· Adobe Acrobat XI (reader)

· Internet access The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall maintain state-of the-art virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with NAVAIR 6.8.4. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with NAVAIR 6.8.4 during working hours whether at Contractor work site or on travel.

3.1.2 Work Location and Facilities

3.1.2.1 Work location

Approximately 10 percent of work will be performed at Government site and 90 percent of work will be performed at Contractor site. Government sites include NAVAIR 6.8.4, Marine Corps Air Wings (MAWs), and United States Fleet Forces (USFF) Command. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks.

3.1.2.2 Physical Facilities

The Contractor shall maintain facilities located within a ten (10) miles radius of the Patuxent River Air Station, MD and within a twenty (20) mile radius of the Naval Station Norfolk, VA to facilitate close coordination with U.S. Fleet Forces (USFF) and other fleet activities and have accommodations for working groups with 30 participants. Contractor shall maintain a SECRET facility clearance.

3.1.2.3 Test Facilities

The Contractor shall maintain a standalone test environment at their facilities located at the Patuxent River Air Station, MD and the Naval Station Norfolk, VA to enable developmental testing support and prototyping, training, and Independent Verification and Validation of systems. The Contractor shall provide an inventory of available equipment and provide the types of developmental testing and prototyping support, Independent Verification and Validation (IV&V) and training these test environments can support.

3.1.2.4 Meeting and conference room support

In support of the tasking outlined in this PWS, the Contractor shall have the capability to host and conduct meetings at the classification levels up to _______with the capacity to support a minimum of 8 persons.

The conference room should hold a minimum of 8 persons. The conference room shall contain sufficient equipment to conduct meetings with presentations. Therefore, the facility shall have projectors and/or TV displays, computer(s) with compatible software as required in Paragraph 3.1.1 and telephone(s). This support shall be provided at Patuxent River, MD. and Norfolk, VA.

3.1.3 Contract Status reporting

The contractor shall provide the following documentation.

3.1.3.1 Monthly Progress and Financial Status Report (CDRL XXXX) The contractor shall provide a progress and financial status report in the Monthly Status Report in accordance with the Contract Data Requirement List (CDRL). The report shall include work accomplished since submittal of the last report, both monthly and cumulative man-hour labor costs expended by labor category and material and travel costs.

3.1.4 Work Schedule to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure.

3.1.4.1 Work Schedule

The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including a 30-minute lunch break), from 0800 to 1630 each Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800, Monday –Friday.

3.1.4.1.1 Compressed Work Schedule (CWS)

CWS is an alternative work schedule to the traditional five 8.5-hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period: eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.

The Contractor, with agreement by the COR/ACOR, may allow its employees to work a CWS schedule. If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage when required by the Government. If agreement to implement the CWS schedule is reached with the COR, the overall schedule must be provided and approved. Key contractor personnel, at the discretion of the COR, may not be allowed to work a CWS schedule even if the remaining employees are permitted to do so.

3.1.4.1.2 Holidays

The Government observes the following holidays:

· New Year’s Day, January 1

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

· President’s Birthday, the third Monday in February

· Memorial Day, the last Monday in May

· Independence Day, July 4

· Labor Day, the first Monday in September

· Columbus Day, the second Monday in October

· Veteran’s Day, November 11

· Thanksgiving Day, the fourth Thursday in November

· Christmas Day, December 25 With the exception of the events in section 3.1.4.1.3 below, the contractor is permitted to observe the above Holidays in accordance with its corporate policy. In the event any of the above holidays occur on a Saturday or Sunday, or CWS alternate Friday, then such holiday shall be observed in accordance with COR direction.

3.1.4.1.3 Installation Closure

When Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility performing non-mission essential work in support of such Federal employees shall follow their parent company’s policies While generally contractor personnel may not perform work on-site at a Government facility without supervision from Federal personnel, in very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential.

3.1.4.1.4 Overtime

Overtime cannot be charged directly to the contract unless first approved in writing by the Chief of the Contracting Office.

3.1.5 Other Direct Costs

ODCs are based on a per annum amount. The COR/ACOR approval shall be obtained prior to the purchase of any material or travel expenses.

3.1.5.1 Travel

Travel will be allowable only when it is essential to the performance of the tasks detailed in Section 3.3. Reimbursement for travel performed shall be in accordance with the Department of Defense Joint Travel Regulation (http://www.defensetravel.dod.mil/site/travelreg.cfm). The COR shall approve all travel performed in support of this contract prior to the commencement of the travel. COR approval for local travel expenses is required. Travel may include general and administrative expenses but shall not include profit. Temporary travel to OCONUS locations in support of program tasking may be required. If required, temporary travel locations include Norfolk, VA, Patuxent River, MD, San Diego, CA, and Cherry Point, NC. This list is not all inclusive as locations will be identified in the specific task order. Travel authorization request shall be submitted no less than 3 business days prior to travel for COR approval.

3.1.5.2 Material

Prior written approval of the COR shall be required for all purchases of materials over $2500. If the contractor’s proposal includes a list of materials with associated prices, then the (COR/ACO/PCO as applicable) acceptance of the contractor’s proposal shall constitute written approval of those purchases. Any material provided by the contractor is subject to the requirements of the Federal Acquisition Regulation (FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable Department of the Navy regulations and instructions. All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Other Direct Charges may include general and administrative expenses but shall not include profit.

The costs of general purpose business expenses required for the conduct of the contractor’s normal business operations are not an allowable direct cost in the performance of this contract. General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies.

3.1.6 Subcontractors

Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this PWS shall flow down to subcontractors providing support under this contract.

3.1.7 Management of Contractor Personnel

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. The contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services

3.2 Security

3.2.1 Citizenship Requirements

Only U.S. citizens shall perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

a. The individual's name, date and place of birth, position title, and current citizenship.

b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

c. A statement of the unusual expertise possessed by the applicant.

d. A statement that access will be limited to a specific Government contract (specify contract number).

e. A statement that the Contractor has obtained an export license for the information required to perform the contract.

3.2.2 Investigative Requirements

Unclassified: All Contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAV M-5510.30. All Contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the Office of Personnel Management. The Contractor shall submit a request for personnel security investigation to the Government Security Office. The Government Security Office shall initiate the Contractor’s Electronic Questionnaire for Investigations Processing (eQIP)), shall do a preliminary screening of the Contractor’s eQIP for suitability and derogatory information. The Contractor employee shall provide all requested information pursuant to the Privacy Act of 1974. The Government Security Office may deny the Contractor access to Government facilities and information and may prohibit the Contractor from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the Contractor’s eQIP. In such cases, the Contractor employee may not perform on the Contract.

Classified: All Contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the Contract’s DD-254, Contract Security Specification. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N).

3.2.3.1 SAAR-N

All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work. Instructions for processing the SAAR-N forms are available at:

http://www.c7f.navy.mil/Portals/8/documents/SAAR-N%20Completion%20Instructions.pdf?ver=2016-07-12-201116-883.

SAAR-N forms shall be submitted to the Contracting Officer’s Representative (COR), Government Technical Point of Contact (TPOC), or to the assigned Government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.2.3.2 Command Access Cards (CAC) / Local Badges

Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to NAVAIR security requirements. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the NAVAIR security office following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative. The Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with facility and security requirements to work in the Government building space.

3.2.3.3 DD-254

The contractor shall comply with security requirements specified in the DD-254, Attachment X, in Section J of this contract. Information or data that the contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as “For Official Use Only”. Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the TPOC/COR of this contract for approval.

3.2.4 Information Security

If the work is performed at the Contractor’s facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with DoD 5220.22-M (NISPOM), and SECNAV M-5510.36. If the work is performed at the Government’s facility, the Contractor shall comply with facility and security requirements to work in the Government building space.

3.2.4.1 Marking

All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program Security Classification Guidance

3.2.4.2 Public Release

No information pertaining to this contract shall be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved in accordance with DFARS 252.204-7000.

3.2.4.3 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC and Government Security Office within 24 hours of the incident occurring.

3.2.5 Operations Security (OPSEC)

The contractor shall comply with activity OPSEC program instructions, guidance and contribute to organization-level OPSEC efforts. The contractor will include OPSEC as part of its ongoing security awareness program and take all required activity OPSEC training. The contractor will protect identified critical information, sensitive unclassified information and activities, which, if divulged, could further compromise classified or sensitive information or operations, or degrade the planning and execution of operations performed by the RO and contractor in support of the mission.

While performing aboard NAVAIR or NAVAIR sites, the contractor shall comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts. Include OPSEC as part of its ongoing security awareness program and take all required Agency training. Be responsive to the Supporting OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the RO and contractor in support of the mission.

3.2.6 Anti-Terrorism Force Protection and Emergency Management The work performed on this contract is not Emergency Essential in accordance with OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives. Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government Officials direct curtailment of operations to “Mission Essential Only”. All Contractor personnel assigned to a Government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.

3.2.7 Program Unique Requirements

This PWS solicits professional engineering services that directly support the mission and production readiness for NAVAIR SV 2020, ALE, MAL-EIT and other Naval Aviation Maintenance and Logistics IT initiatives. The Contractor shall display master knowledge of Naval Aviation and Logistics IT programs, with a specific understanding of NAVAIR 6.8 functional management, functional requirements and functional certification process. An in-depth knowledge of the IT software acquisition lifecycle is required and must be demonstrated in areas to include Defense Business Systems (DBS) business process reengineering, problem statement development, analysis of alternatives, identification of program performance metrics, project planning, capability and functional requirements, systems engineering, testing, implementation, cybersecurity and information assurance, sustainment and operations, and data analysis.

The Contractor shall have a complete understanding of current NAVAIR Commodity Line projects and systems as well as IT initiatives that will deliver full lifecycle weapon systems to the warfighter. Further, the Contractor shall display a full understanding of the logistics and maintenance capabilities to the functional Naval Aviation Support Process (NASP), ALE, NAMS and related NOBLE concepts including associated IT infrastructure, business rules, reporting strategies, sustainment requirements and business processes.

The Contractor shall be familiar with DoD, DoN, and NAVAIR policy and concepts including but not limited to: Federal Information Security Modernization Act (FISMA), Financial Improvement and Audit Readiness (FIAR), National Institute of Standards and Technology (NIST) standards, Risk Management Framework (RMF) for DoD IT, Cyberspace Workforce Management, Federal Information System Controls Audit Manual (FISCAM), Functional Area Management (FAM), OPNAV N4 Program of Record (PoR) Strategy and other IT Enterprise Initiatives, Program/Budget initiative System for Information Technology (PBIS-IT), Navy Enterprise Licensing agreements, Navy Information Dominance Approval process (NAV-IDAS), BPR and Competency Aligned Organization (CAO). An understanding of these policies and concepts will be required to ensure the stability and continuity of the workforce when hiring personnel and during execution of this PWS.

The Contractor shall comply with Command and DoN Initiatives such as legacy application reduction, program of record strategy and data center consolidation. These shall be performed in accordance with DoD, DoN, NAVAIR, and other applicable SYSCOM policies, standards, and mandate.

In order to demonstrate maturity and quality in process management, the contractor is expected to possess – at a minimum – an active certification by the International Organization for Standard (ISO) for 9001:2015 Quality Management or later.

The contractor shall perform as a “Covered Government Support Contractor" (See DFARS 252.227-7013 and DFARS 225.227-7025) which means the contractor furnishes independent and impartial advice or technical assistance directly to the Government in support of the Government’s management and oversight of a program or effort rather than to directly furnish an end item or service.

3.3 Detailed Support

This section provides the detailed support to be provided by the contractor.

3.3.1 Program Management

The Contractor shall provide project management support to manage the cost, schedule, and performance of this effort in accordance with industry best practices. The Contractor shall assign a single point of contact, also known as the Program Manager (PM), who shall work closely with the Government lead. This PM shall be a Project Management Professional (PMP) accredited by the Program Management Institute. The PM shall be ultimately responsible for ensuring that the Contractor’s performance meets all Government contracting requirements within cost, schedule (to include a fully Integrated Master Schedule and Resource Capacity Plan), and performance. Responsibilities include: personnel management; management of Government material and assets, and personnel and facility security. In support of open communication, the Contractor shall have, unless otherwise directed, monthly meetings with the Government technical lead. The PM shall attend program/project reviews, and other meetings of interest and importance to manage the overall effort in support of the PMO initiative, as well as providing input to programmatic and execution processes. The PM and their Contractor’s organization shall exhibit demonstrated experience in the establishment of a PMO and working experience which successfully manages and executes the portfolio of projects within the PMO. The PM is also responsible to generate the Contractor’s progress, Status and Management Report, the Conference Agenda, and the Conference Minutes.

The Contractor shall also assist the Government in the execution of aviation maintenance and related IT program management functions to include identifying program scope, defining objectives and developing the course of action to achieve defined acquisition milestones. This work is accomplished in accordance with DoD Instruction 5000.02 and 5000.75 requirements including all phases of the Business Capability Acquisition Cycle (BCAC) for business systems requirements and acquisition. The Contractor shall demonstrate a working knowledge for the five BCAC phases as described below:

· Capability Need Identification.

· Business Solution Analysis.

· Business System Functional Requirements and Acquisition Planning.

· Business System Acquisition, Testing and Development.

· Capability Support.

The Contractor shall have a firm grasp of the dynamic nature of NAVAIR’s IT initiatives and goals and will bolster established management expectations with proven project planning, organizational structure, team building, and effective control mechanisms. Efforts include:

· Integrate with Government program management office to successfully support each phase of the project life cycle utilizing proven management tools to evaluate and ensure software vendor projects are on time and within budget.

· Provide necessary discipline and rigor within the realm of Program and Project Management, and apply essential concepts, processes, and techniques in the management of large-scale programs and the delivery of successful IT projects.

· Provide acquisition management support required to establish Business Systems Category II and III Programs of Record (POR) and move the maintenance community in the direction of enterprise, net-centric, IT solutions.

· Assist in establishing and managing Integrated Product Teams (IPTs) to achieve defined acquisition milestones through the coordinated delivery of defined products and processes.

· Provide Functional Sponsorship support to the Defense System Acquisition Framework. Assist in the development of DBS integrated plans, processes and documentation.

· Support the Government’s DBS requirements management process which includes stakeholder identification, and requirements definition, development, testing, production, deployment and sustainment.

· Assist in the development of the management plan and associated Project, Program and Portfolio (PPP) documentation (quality management plan, risk management plan, communications plan, etc.) which are utilized to execute the effort.

· Assist in the development and provide support for the iterative change control process including assessment and documentation. Derive the Work Breakdown Structures (WBS) using approved requirements and other management planning/reporting methods/documentation, such as, milestone charts, work packages, and associated tasks

· Prepare for and help the Government execute program defined Program Management Reviews (PMRs) such as Preliminary Design Reviews (PDRs), Critical Design Reviews (CDR), Test Readiness Reviews (TRR) and Release Readiness Reviews (RRR) and Sprint reviews with system developers/integrators when requested by the Government.

3.3.1.1 Project Monitoring and Control

Throughout the project life cycle, the contractor shall measure progress against plans, conduct reviews, conduct quality audits, and provide regular project updates and status reports in accordance with the deliverables schedule. The contractor shall manage the cost, schedule, risk(s)/issue(s), and resource plans; realign and add resources, as necessary.

· The contractor shall perform requirements management and change control throughout the execution of the contract commencing with requirements identification and proceeding through design, development, integration, test and sustainment. This requirements management shall be accomplished using a scalable solution such as the Dynamic Object-Orientated Requirements System (DOORS).

· The contractor shall prepare corrective action plans when performance does not meet established parameters or is outside of the variance thresholds established during the planning phase.

· The contractor shall participate in and provide input to activities required to identify and resolve risks, issues, and internal/external dependencies.

· The contractor shall report the project management metrics to the Government and report on variances during progress meetings and in monthly status reports, in accordance with the deliverables schedule.

· The contractor shall be responsible for a task order contract work breakdown structure (CWBS) that reflects task order work to be performed under this PWS to at least level 3, as defined by program release baselines.

· The contractor shall use the CWBS to develop an Integrated Master Schedule (IMS) which aligns with PMO project schedules that reflects / addresses all PMO and FM support requirements, and shall allocate resources (staff, facilities, and equipment) to each CWBS element.

· The contractor shall develop a Resource Capacity Plan balancing personnel and demand. The Plan shall consider all resources required to deliver PMO and FM support activities that meet short, medium, and long-term requirements. The Resource Capacity Plan shall identify any potential capacity related risks/issues likely to arise and justifies resource needs; resource increases, decreases, etc.

3.3.1.2 IT Strategy

The Contractor shall support IT strategy development that aligns with the guidance and initiatives set forth by SV2020, ALE, the Logistics IT Executive Committee (LOG IT EXCOMM), and other Echelon I and II level initiatives. This includes developing Aviation Maintenance and related Logistics IT Strategic Plans and IT Roadmaps to support defined strategies. The Contractor shall provide project / program oversight support of IT Strategy execution and assist in the planning, development, documentation and implementation of IT plans and strategies to include:

· Develop IT strategy with clear alignment to business mission and objectives that provides a clear way forward for Maintenance Information Systems (MIS) afloat and ashore.

· Analyze gaps between current state and desired future state.

· Assist with developing IT strategies, IT governance, programs, and processes to transition the Aviation Maintenance IT community to more efficient enterprise systems that are more closely integrated/aligned with supply and financial capabilities.

· Evaluate command level initiatives, IT governance, policy and compliance support, and internal IT/Information Management (IM) department business processes to align aviation maintenance requirements with the OPNAV Program Objective Memoranda (POM) process.

· Facilitate the implementation of IT/IM solutions that enables the success of major command initiatives, such as, but not limited to, Business Process Reengineering, Data Center Consolidation, FIAR compliance, Cloud Computing, Application Rationalization and Enterprise Resource Planning (ERP), Activity Based Costing/Management and AIRSpeed. These IT/IM solutions are designed to facilitate improved management effectiveness, enhanced productivity and increased efficiency.

3.3.1.3 IT Portfolio Management

The Contractor shall design, implement and operate, after Government review and approval, an Enterprise Portfolio PMO process by which the Government can continually and consistently evaluate, select, prioritize, budget, plan and manage IT investments. In addition, the contractor shall:

· Assist with the development, implementation, and management of IT Portfolio Management processes.

· Participate in the development of various documents to ensure that Enterprise Portfolio processes are fully integrated and supportive of mission requirements.

· Conduct investment analysis and make recommendations regarding whether investments in IT are aligned to the command’s strategic/business plan and priorities.

· Conduct analysis of Aviation Maintenance Programs and Initiatives and submit draft recommendations, briefs, formal presentations and plan of action documents for approval by senior leadership.

· Ensure the implementation of new functional capabilities and user requirements aligns to the vision of an enterprise-wide integrated IT solution.

3.3.1.4 Project Planning and Support Management

The Contractor shall provide both administrative support and subject matter expertise in the gathering of information for the preparation and development of presentations to support team meetings, management reviews, logistics team reviews, audits and other requests for presentation/briefing information. Specially, the Contractor shall:

· Track command action items from internal/external sources and coordinate with appropriate action officers and other directorates, echelons II/III and industry partners to ensure dissemination of information as appropriate and track progress through completion.

· Provide support in the preparation, scheduling and documentation of logistics meetings to include but not be limited to Tactical Maintenance and Operations (TMO), Product Lifecycle Management (PLM) and Product Data Management (PDM) Program Management Reviews (PMRs), Naval Aviation Logistics Command Management Informational System (NALCOMIS) IPT, and Fleet Guidance Team (FGT) reviews, modification review meetings, maintenance engineering logistics reviews, critical parts reviews, affordable readiness initiatives, logistics documentation reviews, data calls, and conference calls or other directed program meetings, conferences, teleconferences, or technical coordination meetings or reviews.

· Review and analyze draft Government instructions, notices, technical documents, and manuals; provide recommendations and prepare documents for Government review and approval.

· Manage technical and business processes such as acquisition planning, financial reporting, engineering, solution fielding, strategic and operational planning, engineering, training, operations, risk assessment, and customer support. Processes shall be in accordance with the user’s guidelines.

· Prepare presentations, charters, analysis, recommendations, correspondence, and plans of action and milestones. Preparation and development of presentations will range in scope from detailed in-house briefings to Senior Executive briefings outside the supported organization.

· Develop schedules and implementation plans that identify defined deliverables and project milestones, parallel and interdependent tasks where required, technical approaches and a description of anticipated solution results.

· Provide administrative support for fleet maintenance initiatives, programs and directorate to include managing calendars and travel requirements, tracking training requirements, scheduling meetings, performing command specific data calls, and ordering required program supplies.

3.3.1.5 Risk Management

The Contractor shall develop and execute a risk management program that consists of Risk Planning; Risk Identification; Risk Analysis and Risk Control. The contractor shall be responsible for updating the periodic inputs and updates to Risk Radar based upon direction from the Government project managers. The Contractor shall establish processes such as risk qualification and quantification and maintain tools such as Risk Radar in support of the Government Risk Management function. The contractor will participate in project reviews to evaluate the risks inherent in assigned projects/programs. The Contractor shall:

· Assist the Government in verifying the risks associated with projects using reliable performance measurements baselines which include the entire scope of work, are consistent with project schedules, and have adequate resources assigned.

· Assess the risk of implementing DoD and DoN policies on the execution of Naval Aviation maintenance and the management of maintenance information systems.

· Perform qualitative analysis of risks/conditions and recommend prioritizing their effects on Project objectives, as well as measuring the probability and consequences of risks and evaluating their impact on Project execution. Support the Government in the execution and maintenance of a Risk Management Program including the maintenance of a risk review schedule, execution of portfolio level risk reviews, preparation of a risk watch list, and the identification of cross-program/enterprise-level risks.

· Follow a disciplined methodology for conducting thorough program/project risk assessments and prepare documentation containing the assessed prioritized risks.

· Manage the day to day execution of Risk Exchange management efforts, including registration of new users.

· Provide risk inputs for the monthly NAVAIR 6.8.4 project reviews.

3.3.1.6 Configuration Management

The Contractor shall support configuration management initiatives utilizing commercial best practices and tools. In support of this function the Contractor shall:

· Establish guidelines and practices for the operation of Configuration Control Board (CCB) upon Government approval. Prepare associated configuration management policies and procedures for Government review and approval.

· Evaluate software vendors’ compliance with established CM policies and procedures. Ensure CM plans, CM charters, and documentation libraries align with PMO requirements.

· Support the implementation and maintenance of project CM processes. Support services shall also include implementation and operation services for CM (or program related) software tools.

· Ensure a managed discipline is in place to identify the proposed or implemented configuration of a system at discrete points in time.

· Ensure software vendors systematically record and trace changes to all system components (conceptual and physical). The Contractor shall use Government provided tools for controlling changes and ensure, throughout the lifecycle, that CM items can be verified by the PMO via auditing and reporting.

3.3.1.7 Financial Management

The Contractor shall assist in preparing and updating mandated financial management documentation for presentation to NAVAIR leadership and / or higher authority. The Contractor shall

· Use the Planning, Programming, Budgeting, and Execution (PPBE) process to identify required funding allocations for all program / project operations.

· Provide inputs to the Program Objectives Memorandum (POM) process and draft supporting documents such as the ALE Acquisition Workbook which provides the financial funding forecast requirements with the associated tasking to realize the total ALE implementation and sustainment.

· Assist in preparing and updating mandated financial management documentation for presentation to the Program Office and/or higher authority.

· Assist with NAVAIR fiscal management through the use of tools such as the Common Spend Plan Tool (CSPT) and the Ordnance Programs Optimization Model (OPOM).

· Assist in the development of and deliver documentation such as fiscal year spend plan, Economic Analyses (EA), various budget exhibits, reports, and Program Office Estimates (POE). Example documentation includes detailed project business case analyses (BCAs), IT Purchase Requests (ITPR), Return on Investments (ROI), and calculation of project payback periods.

· Review and recommend updates to governing directives for Naval Aviation Enterprise (NAE) IT budget development, submission, and execution to include PBIS-IT submissions.

· Evaluate Maintenance Information Systems for compliance with FIAR requirements and identify process changes required to incorporate FIAR requirements into existing and future IT maintenance solutions.

3.3.1.8 Facilitation and Training

The Contractor shall provide a wide range of facilitation support services. The Contractor shall facilitate strategic planning, decision support and other facilitation services as required by the Government. The Contractor shall:

· Design, develop and execute, once approved by the Government, end user training, “train the trainer” training, On-the-Job training, and web-based training approaches for team building and performance measurement, as well as, the following areas within this PWS: Information Technology, Business Improvement and Business Analytics.

· Support the following Education and Training activities: strategy development; definition of training requirements and standards; courseware development / procurement; evaluation and test; conduct the training; and training reinforcement and follow up.

· Provide Aviation Maintenance and Logistics IT training support to systems such as the Marine Expeditionary Pack Up Kit (EPUK).

3.3.1.9 System Documentation

The Contractor shall develop, update and / or review required Naval Aviation and Logistics system requirements and testing documentation throughout the lifecycle. The Contractor shall be responsible for preparing higher level capability and functional level documentation for Government approval. System level (i.e., lower level technical documentation) will be the responsibility of the software vendor and reviewed by the Contractor to ensure software vendor requirements and test artifacts effectively align with and support the Government’s functional requirements. Findings will be reported to the Government for remediation. Documentation may include Project Charters, Problem Statements, and Functional Requirements Document (FRD), Requirements Traceability Matrix (RTM), Software Requirements Specifications (SRS), software test cases, software tests plans, test scenarios, test reports, Software User’s Manuals (SUM), Installation plans and Operating Manuals. This lower level system documentation shall be delivered as System Documentation specified and required in the individual Task Orders. Documentation may also consist of various briefs and/or materials presented or discussed at reviews.

In addition, the Contractor shall provide:

· Technical editor, writing and illustration services to include technical documentation preparation, coordination and pre- and post-publication activities.

· Support the development of the style, format and preparation of illustrations associated with NAVAIR, federal and military specifications, standards, ad hoc publications, handbooks and other technical / non-technical documentation.

· Graphic design support for PMO briefs, strategic plans and related documentation. The Contractor’s illustrator personnel shall possess good communication skills to interface with technical and non-technical personnel.

3.3.2 Lifecycle Logistics

The Contractor shall provide planning, development, implementation and management support for a comprehensive, affordable and effective systems support strategy within Total Life Cycle Systems Management to include:

· Support Lifecycle Logistics encompassing acquisition (design, develop, test, produce and deploy), sustainment (operation and support) and disposal.

· Provide acquisition (design, develop, test, produce and deploy), sustainment (operation and support) and disposal support efforts for Total Lifecycle Logistics of IT systems.

· Provide lifecycle logistics support to design/maintain/improve readiness, improve affordability and minimize logistics footprint. The Contractor shall support efforts to improve readiness and affordability, while minimizing logistics footprint for Total Lifecycle Logistics.

· Perform various supportability analyses and support program efforts to integrate acquisition, logistics and supply to ensure superior product support processes that focus on affordability and operational effectiveness. The Contractor shall support the integration of acquisition, logistics and supply by employing standard product support processes and supportability analyses, focusing on affordability and operational effectiveness.

· As part of an individual / portfolio program acquisition strategy, the Contractor shall develop an effective system / product support strategy that addresses and documents lifecycle affordability considerations. The Contractor shall support the development of an effective system/product support strategy that addresses and documents lifecycle affordability as part of an individual/portfolio program acquisition strategy.

· Develop/support/maintain/perform all logistics support element processes including Maintenance Planning and Management; Training and Training Support; Technical Data; Sustainment Engineering; Design Interface; and Product Support Management.

· Support Maintenance and Logistics concepts such as Condition Based Maintenance Plus (CBM+), Reliability Centered Maintenance (RCM), Maintenance Repair and Overhaul (MRO), Supply Chain Management, Preliminary Industrial Assessment(s), Core Logistics Analysis and Source of Repair Analysis efforts.

· The results and recommendations for all Total Life Cycle Systems Management planning, analysis, development and implementation shall be provided in Logistical Documentation as specified in the individual Task Orders.

3.3.3 Business Process Improvement

The Contractor shall assist in the planning, implementation and the supporting of transformation initiatives. The Contractor shall utilize DoD and industry best practices in developing strategies, programs, and processes to support the business process transformation of legacy Naval Aviation and Logistics IT systems to future enterprise IT solutions.

The Contractor shall perform detailed research and analysis and provide written reports, for Government review and approval, focusing on acquisition and information technology commercial best business practices. The initiatives shall include, but are not limited to, replacement of Naval Tactical Combat Support System (NTCSS), future logistics enterprise initiatives, Business Process Reengineering (BPR), Theory of Constraints (TOC), Just-in-Time, Lean Six Sigma, Airspeed, and Balanced Scorecard. The results of this research and analysis shall be provided in Business Process Improvements as specified and required in the individual Task Orders.

3.3.3.1 Business Transformation

The Contractor shall assist the Government in the planning, implementation and support of DoN logistics enterprise business transformation initiatives, to include:

· Perform detailed analysis of maintenance, supply, and other logistics IT systems, business processes and requirements.

· Assess ability of current IT…