N0018919RQ015_N0018919RQ015_-_Draft_PWS.docx

PERFORMANCE WORK STATEMENT (PWS)

Naval Supply Command (NAVSUP) & Naval Sea Systems Command (NAVSEA) Supply and Logistics Business Process Analysis

1.0 INTRODUCTION: Naval Supply Command (NAVSUP) and Naval Sea Systems Command (NAVSEA) Contractor Support Services (CSS) needs under this contract will include: Consulting expertise to assist NAVSUP and NAVSEA to analyze current supply chain/logistics initiatives and develop a NAVSUP and NAVSEA Strategic Direction to improve business performance, to include a focus on the Maritime Outfitting Spares and Allowancing processes (here after referred to as Spares process). Contractor must utilize industry proven methodology and tools (e.g., value chain mapping, commercial investment strategy, value engineering, and kaizen-like events). The contractor will then develop the functional business requirements necessary to modernize the NAVSEA and NAVSUP Spares process.

2.0 BACKGROUND: NAVSUP is working with NAVSEA to lead Business Process Reengineering (BPR) efforts to improve Navy’s Maritime Spares processes. Currently, the Navy relies on legacy systems to execute portions of the Spares processes. The legacy systems are at or near the end of the sustainable service life. To ensure sustained support to the Fleet, NAVSUP and NAVSEA and require contractor support services to conduct business process reengineering of Spares processes. This initiative will leverage a select team of expert contractors – supply chain functional architects to a) conduct ethnographic research and review and analyze the Spares processes, b) support NAVSUP and NAVSEA in developing optimized business processes, and c) document the business requirements for each optimized process that supports NAVSUP and NAVSEA’s mission to design, build, deliver, and maintain ships and systems on-time and on-cost. The contractor will conduct BPR to improve the NAVSUP and NAVSEA Spares solutions and identify process functional gaps in “As-Is” processes. Analysis will leverage capabilities that provide NAVSUP and NAVSEA improved supply chain business processes and functional requirements for on-time delivery of ships through increased velocity and accuracy of spares and allowancing. The assessment will include analysis across different aspects of current Spares processes, seeking to optimize operations through identification of process functional gaps, pain points and root causes. The BPR will include identification of high-level business processes (HLBP) and sub processes that may be modernized. This effort is designed to optimize the information technology footprint currently comprised of numerous IT systems and better position NAVSUP and NAVSEA for transition and integration of a modernized Spares processes.

2.1 Requiring Organization: The organization requiring the services outlined in this Performance Work Statement (PWS) is:

NAVSUP BSC

5450 Carlisle Pike PO Box 2010 Mechanicsburg, PA 17055

2.2 Project Description: This initiative will support NAVSUP and NAVSEA efforts to optimize Spares processes and increase integration with other logistics business processes and initiatives. The project will leverage the functional capabilities and business processes to improve the effectiveness of the Navy’s business operations and supply chain initiatives. The modernized Spares processes will focus on improving Spares delivery systems in support of Fleet readiness.

3.0 SCOPE: The goal of this PWS is to obtain contractor support services to provide the following:

· Research of the “As-Is” Spares (including Allowancing as aforementioned) processes; evaluation of supply chain initiatives; observations of and interviews with subject matter experts (SME), end users; and identifying the list of processes to be reviewed and analyzed.

· Identification of internal and external stakeholders impacted by Spares processes (e.g., SPAWAR, NAVAIR, NAVSUP, Fleet, and TYCOMs).

· Business process analysis that identifies the high-level business processes and sub processes for the current spares and associated supply chain (logistics) processes.

· Discovery and documentation of process pain points and process functional gaps.

· Identification of external processes impacting the overall Spares processes (i.e., configuration management and allowance development).

· Consolidate the Business Requirements from the “As-Is” Spares processes, the Pain Points and process functional gaps into a “To-Be” process map.

· Transition support.

4.0 DIRECTIVES: Contractor shall comply with the following directives:

· Federal Information Security Modernization Act of 2014 (“FISMA”)

· DoD Directive 5400.11, DoD Privacy Program, 29 October 2014

· DoD Directive 8000.01, Management of the DoD Information Enterprise, 17 March 2016 (incorporating Change 1 July 2017)

· DoD Directive 8140.01, Cyberspace Workforce Management, 11 August 2015 (incorporating Change 1, 31 July 2017)

· DoD Instruction 4161.02, Accountability and Management of Government Contract Property, 27 April 2012 (incorporating Change 1, 29 September 2017)

· DoD Instruction 8320.07, Implementing the Sharing of Data, Information, and Information Technology (IT) Services in the Department of Defense, 3 August 2015 (incorporating Change 1, 5 December 2017)

· DoD Instruction 8500.01, Cybersecurity, 14 March 2014

· DoD Instruction 8510.01, Risk Management Framework (RMF) for DoD Information Technology, 12 March 2014 (incorporating Change 2, 28 July 2017)

· DoD Instruction 8582.01 Security of Unclassified DoD Information on Non-DoD Information Systems 6 June 2012 (incorporating Change 1, 27 October 2017)

· DoD 5400.11-R, Department of Defense Privacy Program, 14 May 2007

· DoD 8500.01, Information Assurance, 24 October 2002

· DoD Manual 8570.01-M, Information Assurance Workforce Improvement Program, 19 December 2005 (incorporating Change 4, 10 November 2015)

· SECNAV Instruction 5211.5E, Department of Navy Privacy Program, 28 December 2005

· SECNAV Instruction 5239.3C, DON Cybersecurity Policy, 2 May 2016

· SECNAV Instruction 5510.30B, DON Personnel Security Program Instruction, 6 October 2006

· SECNAV Manual M-5239.2, DON Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification Manual, 27 June 2016

· SECNAV Manual M-5510.30, Department of the Navy Personnel Security Program, 1 June 2006

· CJCSI 6211.02B--Defense Information System Network (DISN): Policy Responsibilities and Processes of 31 July 2003

· DoD Public Key Infrastructure (http://iase.disa.mil/pki-pke)

· ISO/IEC/IEEE 12207:2017(E) First edition 2017-11 - ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes

· ANSI/EIA 649.B-2011 – Configuration Management Standard.

· ANSI/EIA 836-2010 – Configuration Management Data Exchange and Interoperability.

· Federal Risk and Authorization Management Program (“FedRAMP”)

· Department of Defense Cloud Computing Security Requirements Guide, Version 1, Release 3, dated 6 March 2017, or the version and release number in effect when cloud services are provided.

· All applicable Security Requirements Guides, Security Technical Implementation Guides, and National Security Agency security configuration guides in effect when cloud services are provided.

· Common Criteria for Information Technology Security Evaluation, Part 3: Security Assurance Components, April 2017, Version 3.1, Revision 5, CCMB-2017-04-003; or the version and revision number in effect when the cloud services are provided.

· NIST SP 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems, February 2010, includes updates as of 5 June 2014

· NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations, April 2013, includes updates as of 22 January 2015

· NIST SP 800-53A Revision 4, Assessing Security and Privacy Controls in Federal Information Systems and Organizations, December 2014, includes updates as of 18 December 2014

· ISO/IEC 19770-1:2017 – Information Technology – IT Asset Management – Part 1: IT Asset Management Systems - Requirements

· ISO/IEC 19770-2:2015 - Information Technology -- Software Asset Management -- Part 2: Software Identification Tag

· ISO/IEC 19770 Series - Information Technology

· A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Sixth Edition

5.0 REQUIREMENTS/TASKS: The contractor shall be obligated contractually to perform every requirement in this PWS. Not every performance requirement has a related standard expressed in this document. In such cases, the performance standard is either inherent in the requirement or performance is to be in accordance with standard commercial practice. Per DFARS 211.106, contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

5.1 Business Process Analysis Services: The contractor shall:

· Focus on business process re-engineering of the Spares processes and the development and recommendation of the technical course of action for spares.

5.1.1 Support NAVSUP and NAVSEA SMEs and other end users by developing a deeper understanding of NAVSUP and NAVSEA supply chain requirements and conducting a proven process analysis methodology to evaluate the business value of current (or discovered) NAVSEA business process and IT modernization initiatives. Identify current initiatives proposed by NAVSEA program changes, business process reviews, and sub-business processes. Business analysis methodology will identify business requirements that address problems, pain points, root causes and process functional gaps. Analysis shall be documented in the NAVSEA-identified Business Process Management (BPM) Repository.

The Spares and other supply chain BPRs will streamline the complex supply/logistics processes, thereby improving productivity, increasing quality, decreasing waste, and allow NAVSUP and NAVSEA to become more agile and effective. Contractor business process analysis methodology and tools will support the roles of business process engineer and business analyst; and enable them to better understand business processes, events, workflows and data using proven modeling techniques.

5.1.2 Compile business process requirements of the NAVSUP and NAVSEA Spares and other supply chain processes to identify the processes, policies, tools, and technologies. This includes Interim Support focused on all activities leading to Material Support Date for Maritime (and Aviation) materials.

5.1.3 Identify application pain points, root causes and process functional gaps that limit NAVSEA spares performance and opportunities for innovation to improve acquisition performance. Pain points, root causes and process functional gaps include poor performing business processes, missing capabilities, difficult to use or poor user interfaces.

5.1.4 Document the supply chain pain points, root causes and process functional gaps with enough specificity and detail to ensure business rules, roles, applications and processes are thoroughly and accurately represented. This will assist in identifying potential ‘quick wins’ for implementation.

5.1.5 Support NAVSUP and NAVSEA SME and end users through a process to identify and define the high-level business processes (HLBP) and the individual sub-processes that make up the current Spares processes.

5.1.6 Conduct stakeholder analysis and maintain the Stakeholder Register.

5.1.7 Develop BPR that identifies the processes to improve and streamline Spares support to the Program Managers, NAVSEA, NAVSUP and the Fleet.

5.1.8 Develop a business process and IT integration plan to ensure that impacts to NAVSUP of revised Logistics Support, Spares or Acquisition processes or IT programs at NAVSEA are captured and documented.

5.2 Transition Support Services (Transition - Phase Out): Contractor shall provide a plan to ensure that at the end of the period of performance, the government will be able to maintain all project deliverables. The contractor will provide the government with documentation to provide for knowledge transfer for maintenance of the various deliverables associated with this initiative. This will provide government resources with enough understanding of methodology and processes used to develop these artifacts, so that the government can maintain them as living documents.

6.0 DELIVERABLES: The contractor will provide all applicable deliverables identified in 6.1 through 6.8 below:

6.1 Monthly Status Report: Status reports will be sent electronically to the Technical Assistant (TA) and Contracting Officer’s Representative (COR) within ten (10) days following the end of the monthly period documenting the performance on the contract. The monthly status report will include the following elements:

· Resources by name

· Date project/task received

· Status of work with accomplishments documented

· Percentage of project/task completed

· Estimated date of project/task completion

· Any issues/problems encountered or possible and recommended solutions

· Changes to the Project Management Plan (PMP) to include roles and responsibilities and schedule changes

· Identify any Government dependencies that are overdue which impact schedule or performance

· Evaluate performance and determine adequacy of staffing.

6.2 Monthly Travel Reports: If applicable, travel reports will be sent electronically to the TA and COR. Travel reports will include: destination, dates of travel, subjects discussed, and any issues/problems encountered and recommended solutions.

6.3 Project Management Plan:

· Document will outline the project scope; inputs and outputs; Draft and Final Project Charter; a preliminary schedule of actions and milestones.

· Process Scope Statement

· Assumptions, dependencies, and constraints

· Key milestones

· Process inputs and outputs

· Kaizen Schedule changes: The supply chain architecture (SCA) team will post any changes to the spares Kaizen schedule as a result of any new discovery identified for HLBP or individual sub-processes during Kaizen events.

6.4 Initial Pain Points / Root Cause / Gaps: Identify pain points, root causes, and process functional gaps through the initial analysis of the sub-processes of spares.

6.5 Business Requirements Document: Deliver the business requirements document after each Kaizen event that identifies a clearly defined business requirement. The structure and content of the business requirements document must include sufficient specificity and detail and will be agreed upon by the Technical Assistant and the contractor. It may include the following elements:

· Process Scope Statement

· Assumptions, Dependencies, and Constraints

· Key Milestones

· As Is Business Process Information

· Business Process Pain Points

· Quick Wins documentation

· To Be Business Requirements

· To Be Process map with Policy Associations

· Process Inputs and Outputs

· Key Performance Indicators & Reports

· Data Decision Map

· Business Rules Decision Map

6.6 Technical Requirements Documentation:

6.6.1 Deliver the technical requirements document after the completion of the entire spares process.

6.6.2 Deliver the MSD processes End to End from Interim Support to disposal. This would include but not limited to Interim Support process to MSD calculations then from MSD to Disposal for maritime and aviation process maps for NAVSUP.

6.6.3 Deliver an integration enhancement report to NAVSUP and NAVSEA. This would include but not limited to how a new IT system would improve each commands existing processes that support spares and MSD support.

6.6.4 Deliver the technical requirements document after the completion of the selected processes.

6.7 Stakeholder Register: Through consultation with stakeholders, create stakeholder register that captures: name, organization, location, and contact information. Register will include the stakeholders’ role in the Navy spares, allowancing, and supply chain initiative process.

6.8 Transition Documentation: Documentation on the processes used to develop and maintain initiative deliverables to include:

· Business Process Management (BPM) Repository

· Business Requirements Document(s) for the spares process(s)

· Human Center Design (HCD) Role based documentation

· Business process As-Is and To-Be models

· Program Management Plan (PMP)

· Scope Statement

· Stakeholder Register for spares, allowancing, and supply chain initiatives

· Relevant Navy supply / logistics policies

7.0 INSTRUCTIONS: Unless stated otherwise, the following instructions apply to all deliverables:

· All versions of the deliverables required by contract will be delivered electronically to the COR and/or the COR’s designee and will be subject to Government review and approval.

· Deliverable due dates will consider the review periods described below.

· Draft deliverables will be reviewed and feedback and/or requested changes provided within 7 business days (unless otherwise specified).

· Government reserves the right to request a formal review session with the contractor during these timeframes and may request that the contractor make changes to any version of a deliverable.

· Government will review and approve or reject all final versions of all deliverables within 7 business days of receipt (unless otherwise specified).

· If any deliverable is rejected, the contractor will be notified within the specified time periods and will have 7 calendar days to rework the deliverable and resubmit for Government approval. All changes to any version of a deliverable and/or deliverable outline will be approved by the COR. If more than the specified number of calendar days is required for Government review and approval, the COR will inform the contractor of the need for an extension within the initial review period.

· Contractor shall prepare and submit the deliverables on or before the required due date to the COR or designee via email. For deliverables that are not documents the contractor will submit a description of the deliverable and any associated documentation or descriptive information. In no case will any deliverable be received by the Government less than 21 calendar days prior to the end of the Period of Performance.

· Rejection of any deliverable by the Government does not excuse the contractor from meeting the baseline due dates for any other deliverables.

7.1 Place of Performance: Primary area of support will be at the contractor facility or NAVSEALOGCEN, Mechanicsburg, PA or NAVSEA, Navy Yard, Washington DC. The contractor may work remotely at the contractor facility, home or at authorized travel locations with prior approval of the TA. The contractor, when working at government facilities, will follow applicable base policy for reporting to work during severe weather and base closure.

7.2 On-Boarding Process: All contractor resource onboarding documents must be submitted via the prime contractor. An employee is “productive” upon completion of the following items:

Note (1): Invoicing by the contractor will begin as of the commencement of services and no reimbursement will be paid by the Government for efforts expended during the on-boarding process.

8.0 PERIOD OF PERFORMANCE. The contractor shall provide support under this PWS from date of award for 12 months with one 12-month options.

9.0 TRAVEL: The contractor may be required to travel within the CONUS. Travel must be in accordance with FAR 31.205-46. All travel must be pre-approved in writing by the COR prior to the actual travel and funded in the contract prior to any travel expenses being incurred. Travel will not exceed 7% of the total contract award.

Travel requests will be submitted electronically (email) with contract number referenced in the subject. Text must include name, from/to destination, dates, purpose and estimated cost.

The contractor is responsible for making all needed arrangements for their personnel. Contractor use of privately owned and company vehicles will be required for non-reimbursable travel between various facilities and to other locations such as suppliers/vendors in the performance of the contract.

OCONUS (overseas) travel will not be required for this order.

9.1 Travel Policy: The Government will reimburse the contractor for allowable travel costs incurred by the contractor in performance of this PWS and determined to be in accordance with FAR subpart 31.2, subject to the following provisions:

· Travel required for tasks assigned under this contract will be governed in accordance with rules set forth for temporary duty travel in FAR 31.205-46.

· Invoices will include actual costs experienced.

· The Contractor is not authorized to perform any travel that is not in conjunction with this contract.

· It is the Department of the Navy (DON) policy not to allow a charge of profit or fee on reimbursable items.

· The Government will make no reimbursements for a contractor’s local travel.

· In no instance will the contractor exceed the amount specified in the contract for travel expenses.

9.2 Travel Other. Travel, subsistence, and associated labor charges for travel time are authorized whenever a task assignment requires work to be accomplished at a temporary alternate worksite. Travel performed for personal convenience will not be reimbursed.

9.3 Air/Rail Travel. In rendering the services, the contractor will be reimbursed for the actual costs of transportation incurred by its personnel not to exceed the cost of economy class rail, or plane fare, to the extent that such transportation is necessary for the performance of the services hereunder and is authorized by the Contracting Officer’s Representative (COR). Such authorization by the COR will be indicated in the order or in some other suitable written form.

9.4 Per Diem. Per Diem for travel on work assigned under this PWS will be reimbursed consistent with company policy, but not to exceed the amount authorized in the FTR and/or JTR. Per diem does not apply for travel 12 hours or less.

10.0 SECURITY: This clause does not apply to non-U.S. Nationals (foreign nationals) who are contactor employees performing work overseas. The clause is applicable to the United States Nationals living in the U.S. or overseas who are performing work on a Navy contract. The investigation of a non-U.S. national at a foreign location must be consistent with a NACI, to the extent possible, and include a fingerprint check against the FBI criminal history database, an FBI investigations file (name check) search, and a name check against the terrorist screening database. Also, the above cited reference notes that Foreign Nationals may not be granted CAC Credentials until completion of their investigation and not in the interim.

Per DoD 5200.2-R, DoD Components must initiate and ensure completion of a background investigation before applying the credentialing standards to a non-U.S. national at a foreign location. The background investigation must be favorably adjudicated before a CAC can be issued to a non-U.S. national at a foreign location. The type of background investigation may vary based on standing reciprocity treaties concerning identity assurance and information exchanges that exist between the U.S. and its allies or agency agreements with the host country.

SUPTXT204-9400(7-18) Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information Technology (IT) Systems or Protected Health Information (JUN 2018) Executive Order 13467, Reforming Processes Related to Suitability for Government Employment, Fitness for Contractor Employees, and Eligibility for Access to Classified National Security Information, and Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The 5 CFR 32 part 157 in concert with DoD Manual 1000.13, Vol 1, implements the Federal Standards.

10.1 Applicability: This text applies to all DoD sponsored individuals who require CAC eligibility (or login and P/W if acceptable per contract) for: Physical access to DoD facilities or non-DoD facilities on behalf of DoD; Logical access to information systems (whether on site or remotely); or remote access to DoD networks that use only the CAC logon for user authentication, or access to sensitive and protected information. This applies to the Office of the Secretary of Defense, the Military Departments, the Office of the Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands, the Office of the Inspector General of the DoD, the Defense Agencies, the DoD Field Activities, and all other organizational entities within the DoD (hereinafter referred to collectively as the "DoD Components").

Each contractor employee providing services at a Navy Command under this contract is required to obtain a Department of Defense Common Access Card (DoD CAC). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.

10.2 Access to Federal Facilities: Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this text will require a DoD CAC. When access to a base, facility or activity is required contractor employees will in-process with the Command's Security Manager upon arrival to the Command and will out-process prior to their departure at the completion of the individual's performance under the contract.

10.3 Start-up Period: All contractor resource onboarding documents must be submitted via the prime contractor. The prime contractor will make all necessary preparations to assume full responsibility for productive performance as of the performance start date. Definition of "productive":

Note (1): Invoicing by the contractor will begin as of the commencement of the performance period of services, and no reimbursement will be paid by the Government for efforts expended during the start-up period.

10.4 Access to DoD IT Systems: In accordance with SECNAV M-5510.30, contractor employees who require access to DON or DoD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAV M-5510.30, includes positions which require access to sensitive information. Sensitive information includes information protected under the Privacy Act, to include Protected Health Information (PHI). All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity's Command Information System Security Manager (ISSM)/Information Assurance Manager (IAM).

Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) or T5 or T5R equivalent investigation, which is a higher-level investigation than the National Agency Check with Law and Credit (NACLC)/T3/T3R described below. Due to the privileged system access, an investigation suitable for High Risk national security positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1 and must be trained and certified on the Operating System or Computing Environment they are required to maintain.

Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee's duties, such employees will in-process with the Navy Command's Security Manager and Information System Security Manager (ISSM)/Information Assurance Manager (IAM) upon arrival to the Navy command and will out-process prior to their departure at the completion of the individual's performance under the contract. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N; therefore, the government employee with knowledge of the system/network access required or the COR will sign the SAAR-N as the "supervisor".

The SAAR-N will be forwarded to the Command's Security Manager at least 30 days prior to the individual's start date. Failure to provide the required documentation at least 30 days prior to the individual's start date may result in delaying the individual's start date.

When required to maintain access to required IT systems or networks, the contractor will ensure that all employees requiring access complete annual Cyber Awareness) training and maintain a current requisite background investigation. The Contractor's Security Representative will contact the Command Security Manager for guidance when reinvestigations are required.

10.5 Interim Access: The Command's Security Manager may authorize issuance of a DoD CAC and interim access to a DON or DoD unclassified computer/network upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received, and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.

10.6 Denial or Termination of Access: The potential consequences of any requirement under this text including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors will plan ahead in processing their employees and subcontractor employees. The contractor will insert this text in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.

10.7 Contractor’s Security Representative: The contractor will designate an employee to serve as the Contractor's Security Representative. Within three work days after contract award, the contractor will provide to the requiring activity's Security Manager and the Contracting Officer, in writing, the name, title, address and phone number for the Contractor's Security Representative. The Contractor's Security Representative will be the primary point of contact on any security matter. The Contractor's Security Representative will not be replaced or removed without prior notice to the Contracting Officer and Command Security Manager.

10.8 Background Investigation Requirements and Security Approval Process for Contractors Assigned to National Security Positions or Positions Sensitive Duties: Navy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. Contractor employees under this contract are recognized as Non-Critical Sensitive [ADP/IT-II] positions when the contract scope of work require physical access to a federally controlled base, facility or activity and/or requiring access to a DoD computer/network, to perform unclassified sensitive duties. This designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably completed NACLC or T3 or T3R equivalent investigation to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The investigation consists of a standard NAC and an FBI fingerprint check plus law enforcement checks and credit check. Each contractor employee filling a non-critical sensitive or IT-II position is required to complete:

· SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product)

· Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

· Original Signed Release Statements

Failure to provide the required documentation at least 30 days prior to the individual's start date will result in delaying the individual's start date. Background investigations will be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period. The Contractor's Security Representative will contact the Command Security Manager for guidance when reinvestigations are required.

Regardless of their duties or IT access requirements ALL contractor employees will in-process with the Command's Security Manager upon arrival to the command and will out-process prior to their departure at the completion of the individual's performance under the contract. Employees requiring IT access will also check-in and check-out with the Navy Command's Information Systems Security Manager (ISSM)/Information Assurance Manager (IAM)Manager. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The SAAR-N will be forwarded to the Navy Command's Security Manager at least 30 days prior to the individual's start date. Failure to provide the required documentation at least 30 days prior to the individual's start date will result in delaying the individual's start date.

The contractor will ensure that each contract employee requiring access to IT systems or networks complete annual Cyber Awareness training and maintain a current requisite background investigation. Contractor employees will accurately complete the required investigative forms prior to submission to the Command Security Manager. The Command's Security Manager will review the submitted documentation for completeness prior to submitting it to the Office of Personnel Management (OPM); Potential suitability or security issues identified may render the contractor employee ineligible for the assignment. An unfavorable determination is final (subject to SF-86 appeal procedures) and such a determination does not relieve the contractor from meeting any contractual obligation under the contract. The Command's Security Manager will forward the required forms to OPM for processing. Once the investigation is complete, the results will be forwarded by OPM to the DoD Central Adjudication Facility (CAF) for a determination.

If the contractor employee already possesses a current favorably adjudicated investigation, the contractor will submit a Visit Authorization Request (VAR) via the Joint Personnel Adjudication System (JPAS) or a hard copy VAR directly from the contractor's Security Representative. Although the contractor will take JPAS "Owning" role over the contractor employee, the Navy Command will take JPAS "Servicing" role over the contractor employee during the hiring process and for the duration of assignment under that contract. The contractor will include the IT Position Category per SECNAV M-5510.30 for each employee designated on a VAR. The VAR requires annual renewal for the duration of the employee's performance under the contract.

10.9 Background Investigation Requirements and Security Approval Process for Contractors Assigned to or Performing Non-Sensitive Duties: Contractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc. ...) and who require physical access to publicly accessible areas to perform those duties will meet the following minimum requirements:

· Must be either a US citizen or a US permanent resident with a minimum of 3 years’ legal residency in the United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DoD instruction) and must have a favorably completed National Agency Check with Written Inquiries (NACI) or T1 investigation equivalent including an FBI fingerprint check prior to installation access.

· To be considered for a favorable trustworthiness determination, the Contractor's Security Representative must submit for all employees each of the following:

· SF-85 Questionnaire for Non-Sensitive Positions

· Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

· Original Signed Release Statements

The contractor will ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or T1 equivalent investigation or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM. Failure to provide the required documentation at least 30 days prior to the individual's start date may result in delaying the individual's start date.

* Consult with your Command Security Manager and Information Systems Security Manager (ISSM)/Information Assurance Manager (IAM) for local policy when IT-III (non-sensitive) access is required for non-US citizens outside the United States.

(End of Clause)

DoD 8570.01-M Information Assurance Workforce Improvement Program.

No Additional IA Certification required.

· To meet the IAWF category, the contractor is required to obtain the following IA certification: IA Technical (IAT) Level II (Security +)

· Computing Environment Certification: SAP BASIS with Oracle as a database, asymmetric parallel processing and platform administration, SAS development and platform administration 9.4, Extract, Transform and Load (ETL) Server.

The Contractor will ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor will meet the applicable information assurance certification requirements, including:

1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M

2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.

(a) Upon request by the Government, the Contractor will provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

(b) Contractor personnel who do not have proper and current certifications will be denied access to DoD information systems for performing information assurance functions.

Proof of the above indicated IA baseline certification is to be provided for all applicable contractor personnel prior to time of engagement. In addition to the IA certificate, active enrollment and participation in the certification maintenance program must be established prior to contract award to ensure the appropriate access can be secured by contractor resources. All required DoD-approved Information Assurance (IA) baseline certifications must be current at the contract period start date; there is no “grace” period to obtain these certificates. Applicable computing environment certifications must be completed within 6 months of start date. Contractor Clause DODI 8570.01-M: C2.3.9. Contractor personnel supporting IA functions in Chapters 3, 4, 10, and 11 will obtain the appropriate DoD-approved IA baseline certification prior to being engaged. Contractors have up to 6 months to obtain the rest of the qualifications for their position outlined in AP3.T1. The contracting officer will ensure that contractor personnel are appropriately certified. Additional knowledge transfers on local or system procedures may be provided by the DoD organization receiving services. Baseline certificates site:

https://iase.disa.mil/iawip/Pages/iabaseline.aspx.

Questions and additional information requirements may be addressed by contacting the NAVSEA Information Systems Security Manager (ISSM). Certification will be forwarded to:

TBD

11.0 Government Furnished Equipment: The government will provide work facilities to the on-site contractor. The government will provide computer hardware and software required and access to local telephones with voicemail and long-distance access when the contractor is acting on behalf of the government. NAVSEA will provide all equipment, tools and servers used to maintain software and host these applications.

12.0 Qualifications/Experience:

The contractor resource(s) must either be able to obtain interim access due to a favorable review of the investigative questionnaire and advance favorable fingerprint results or be able to obtain access due to a current favorably adjudicated investigation to enable the contractor to start performance immediately upon the period of performance start date.

The contractor personnel assigned to this project will have the following critical skills:

· In depth functional knowledge of NAVSEA Organization to include experience working in NLSC.

· In depth knowledge of DoD Supply Chain and related logistics processes to include performance metrics.

· Proven ability to write and communicate at an executive level.

· During the first one hundred eighty days of performance, the Contractor will make no substitutions of key personnel unless the substitution is necessitated by illness, death, or termination of employment. The Contractor will notify the Contracting Officer within 15 calendar days after the occurrence of any of these events and provide any necessary information. After the initial 180-day period, the Contractor will submit the information to the Contracting Officer at least 15 days prior to making any permanent substitutions for any contractor personnel. No personnel substitutions will be executed without Government approval by the COR.

The Contractor will provide a detailed explanation of the circumstances necessitating the proposed substitutions, complete resumes for the proposed substitutes, and any additional information requested by the Contracting Officer. All proposed substitutes must have qualifications that are equal to or higher than the qualifications required of the person to be replaced.

13.0 Non-Disclosure Agreement: The Business Sensitive Information Non-Disclosure Agreement is required for this order. Refer to DFARS 252.204-7000, Disclosure of Information, and DFARS 252.204-7003, Control of Government Personnel Work Product.

14.0 Clauses:

14.1 Section 508 Compliance: Section 508 of the Rehabilitation Act requires Federal agencies to make their electronic and information technology accessible to people with disabilities. This applies to all Federal agencies when they develop, procure, maintain, or use electronic and information technology. All electronic and information technology (EIT) procured through this contract must meet the applicable accessibility standards specified in 36 CFR 1194.2, unless an agency exception to this requirement exists. Any agency exceptions applicable to this contract are listed below. The standards define Electronic and Information Technology, in part, as “any equipment or interconnected system or subsystem of equipment, that is used in the creation, conversion, or duplication of data or information.” The standards define the type of technology covered and set forth provisions that establish a minimum level of accessibility. The application section of the standards (1194.2) outlines the scope and coverage of the standards. The standards cover the full range of electronic and information technologies in the Federal sector, including those used for communication, duplication, computing, storage, presentation, control transport and production. This includes computers, software, networks, peripherals and other types of electronic office equipment.

14.2 Privacy Act: During performance of this order, the contractor may have access to Privacy Act data. Should this occur, the contractor will safeguard all privacy information, and ensure this data is accessed and maintained in accordance with applicable laws and regulations. If access occurs, FAR 52.224-1 and 52.224-2 apply.

14.3 Ownership: The Government will have unlimited rights under this agreement to all information and materials furnished by the contractor performing work under this PWS. This will include documentation thereof, reports and listings and all other items pertaining to the work and services pursuant to this agreement. The Government has the right to inspect the work and will have access to, and the right to make copies of the above-mentioned items. All digital files, data and other items generated in performance of this effort will become the property of the Government.

14.4 Enterprise-wide Contractor Manpower Reporting Application (ECMRA): The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for NAVSEA Business Intelligence (BI) Analysis and SAS via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

1) W, Lease/Rental of Equipment;

2) X, Lease/Rental of Facilities;

3) Y, Construction of Structures and Facilities;

4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;

5) S, Utilities ONLY;

6) V, Freight and Shipping ONLY.

The contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data will be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil.

15.0 Points of Contact:

15.1 Technical Assistant (TA)

15.2 Contracting Officer Representative/ Certify Official/Acceptor for Invoices: