RFQ 0069.pdf

N6426720Q0069

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Lot Business Intelligence Specialist V

FFP

See Section C for additional specifications

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

PSC CD: R499

NET AMT

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0002 1 Lot Business Intelligence Specialist IV

FFP

See Section C for additional specifications

PSC CD: R499

NET AMT

Section C - Descriptions and Specifications

GENERAL

PERFORMANCE WORK STATMENT

Business Objects Enterprise Analyst / Business Objects Enterprise (BOE) Functional Subject Matter Expert (SME) Support for Commander, Fleet Readiness Centers (COMFRC)

1. INTRODUCTION

FRCSW’s Information Department (Code 7.2) is procuring two analysts to perform both production work and provide training to current personnel in CRS/BOE in order to meet current and future customer demand. This is an immediate need to forestall delay and prevent inefficiencies in this program.

2. BACKGROUND

FRCSW manages a Business Objects Enterprise (BOE) Corporate Reporting System (CRS) to provide timely and accurate Business Intelligence reports from the NAVAIR Depot maintenance System (NDMS) and other applications and data sources to many departments and activities in all FRCs and other parts of the NAVAIR enterprise.

We are the Center of Excellence (COE) for BOE/CRS. In order to maintain and increase the volume and quality of work FRCSW is currently handling, we need to expand our team output and attain a higher level of expertise. We propose to achieve these goals by hiring two Business Objects Enterprise Analysts to help with production tasks and to train staff. These analysts must demonstrate a high level of expertise in a wide variety of information technology environments and their associated toolsets, plus the ability to pass on this expertise to other staff, document their work carefully, and do a professional pass-down of this work.

3. SCOPE

The intent of this Performance Work Statement (PWS) is to support the Information Technology / Information Management (IT / IM) Division at FRCSW North Island located in San Diego, CA. FRCSW is responsible for performing the Manufacturing, Components, F/A-18, E-2/C2 Programs for scheduled overhaul and unscheduled repair of a wide variety of aircrafts. The IT / IM Division of the FRCSW represents the Commanding Officer as the focal point for all automated data processing technical information systems matters, in support of aircraft overhaul and repair.

The objectives of this effort include Business Objects Enterprise Analyst support for current applications that include, but are not limited to, the Naval Air Systems Command (NAVAIR) Depot Maintenance System (NDMS) suite of applications, Business Intelligence (BI), a variety of commercial off-the-shelf (COTS) and custom-developed software and applications (i.e., local initiatives). Support is for FRCSW, FRC Southeast (FRCSE), and FRC East (FRCE) with One NDMS, Single-Site, data convergence, applications initiative and capability maturity model integration (CMMI) efforts.

4. APPLICABLE DOCUMENTS

Document Type No./Version Title Date

DOD

5220.22-M National Industrial Security Program Operating Manual, (NISPOM)

28 Feb

SECNAV

M-5510.36 Information Security Program, 30 Jun 2006 30 Jun 2006

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

24 Feb 2012

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

DOD 5230.24 Distribution Statements on Technical Documents, Change 1, Effective

28 Apr 2016

SECNAV M-5510.30 Personnel Security Program Jun 2006

OPNAVINST M-5510.30 Navy Installation Emergency Management Program 1 Aug 2014

5. REQUIREMENTS

5.0 Requirements

5.1 General Requirements

5.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 Unclassified. The current operating environment required for this contract includes:

Microsoft Windows 10 Microsoft Project 2010 Microsoft Office Professional Plus 2010 Adobe Acrobat XI (Professional) 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.

5.1.2 Work Location and Facilities

5.1.2.1 Work location: It is anticipated that 100 percent of work will be performed at Government site. Government sites include FRCSW North Island, IT / IM Competency, Building 334-3, San Diego, California and/or any outlying buildings, also at FRCSW, San Diego, California. 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.

5.1.3 Contract Status Reporting: The contractor shall provide the following documentation.

5.1.3.1 Monthly Progress and Financial Status Report: The contractor shall provide a progress and financial status report in accordance with the Contract Data Requirement List (CDRL A001). 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.

5.1.3.2 Enterprise-Wide Contractor Manpower Reporting Application (ECMRA) reporting and ECMRA Monthly Expenditure Report (CDRL A002). The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the FRCSW IT / IM Division via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: https://doncmra.nmci.navy.mil.

5.1.4 Work Schedule, overtime, projected / planned leave, holidays and base closures notifications.

5.1.4.1 Work Schedule: The contractor shall work in accordance with the Government’s discretion. The TPOC/ (SME) may require specific working hours for the contractor dependent on the schedule of the various IT/IM programs. Normal hours are eight (8) hours per day, not necessarily Monday through Friday, with the exception of Federal holidays unless told otherwise. Work outside of normal work hours including Federal Holidays, if required, will be discussed with and agreed to by the TPOC/SME.

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

5.1.4.1.1 Overtime: There will be no Overtime. The contractor shall be required to alter hours of operation with short notice. Duration of change to be determined by the Government as needed to meet FRCSW’s mission requirements.

Contractor work schedules shall be coordinated / approved with the TPOC/SME to ensure coverage during critical periods and tasking.

5.1.4.1.2 Flex / Alternate Work Schedule: FRCSW does not have flextime or alternate work schedule plans available. Special shift considerations shall be cleared through the SME in coordination with the TPOC based on FRCSW’s mission requirements.

5.1.4.1.3 Projected / Planned Leave: To mitigate any possible adverse impact to the FRCSW’s mission, contractors shall develop projected / planned leave schedules at least thirty (30) days in advance. The Government reserves the right to request or reject positions being backfilled during absences.

5.1.4.1.4 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 5.1.4.1.5 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, then such holiday shall be observed in accordance with the SME direction.

5.1.4.1.5 Base 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.

5.1.4.1.5.1 Notification of FRCSW is normally by way of local radio or television (TV) stations. Information concerning other methods of notification will be provided by the government. Individuals may call 1-866-269-6590 to obtain base operating status. No price adjustments will be made for any delays resulting from an installation closing. When area radio or TV stations report that an installation has "delayed reporting" until a particular time, the contractor's personnel have until that time to report to work. No price adjustment will be made if the personnel arrive at work between the normal start time and the delayed reporting time.

5.1.4.1.5.2 Mandatory Plant Shutdown may be scheduled/unscheduled throughout the year. Schedule will be provided as soon as it is made available to the Government personnel; no price adjustment will be made.

5.1.5 Other Direct Costs (ODC): ODCs are based on a per annum amount. The TPOC/SME approval shall be obtained prior to the purchase of travel.

5.1.5.1 Travel: Travel will be allowable only when it is essential to the performance of the tasks detailed in Section

5.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 SME shall approve all travel performed in support of this contract prior to the commencement of the travel. SME approval for local travel expenses is required.

Travel may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking might be required. Temporary travel locations may include Patuxent River (Maryland), Jacksonville (Florida) Cherry Point (North Carolina), but this list is provided for planning purposes and not all inclusive as locations may change over the life of the contract.

Travel authorization request(s) shall be prepared in accordance with the sample in Section J, Attachment 2 and submitted no less than five (5) business days prior to travel for SME approval.

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

5.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. The Contractor shall manage its Personnel and Administrative matters and guard against any actions that are of the nature of personal services, or give the perception of personal services.

5.1.8 Transition Strategy: The overall strategy shall be built around maintaining the mission of FRCSW IT/IM Division with minimal impact, not only in terms of timeliness of performance, but also to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the contract, the Contractor shall ensure an orderly transition of responsibilities while minimizing impact to the operation. The Contractor shall submit a Transition Out Plan, to include the minimum elements listed below in accordance with CDRLs A003.

Work Turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.

Quality Assurance. The Contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

Risk Mitigation Strategies. The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

Data/Information Transfer. The Contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

5.2 Security

5.2.1 Citizenship Requirements: Only U.S. citizens may perform under this contract

5.2.2 Investigative Requirements:

All Contractor personnel supporting PWS paragraphs 5.3.1 through 5.3.3 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.

Contractor shall comply with the provisions of the Department of the Navy Information Security Program Manual (SECNAV M-5510.36) Department of the Navy Personnel Security Manual (SECNAV M5510-30) and Department of Defense Personnel Security Program Manual (DOD M-5200.01).

Contractor eligibility and trustworthiness requirements when performing under FRCSW Contract and or task order for contractor personnel not requiring access to any classified material information but requiring access to controlled unclassified information (CUI) or logical access to any government information system will require a favorable completed and adjudicated TIER 3(T3) or a TIER 3 REINVESTIGATION (T3R). Contractors assigned to a NONCRITICAL-SENSITIVE IT LEVEL II PRIVILEDGE, SENSITIVE INFORMATION ACCESS) duties will require a favorably completed and adjudicated TIER 3.

All Contractor personnel supporting PWS paragraph 5.3.1 (BOE Analyst and BOE SME) 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. At time of award, resource(s) slated to support PWS paragraph

5.3.1 may hold an Interim Secret clearance; however, the Secret clearance must be processed and adjudicated. 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.

5.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request

(SAAR-N).

5.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 on their first day of work. SAAR-N form will be provided to the contractor personnel during the time of check-in with the TPOC.

5.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 FRCSW guidance / instructions.

FRCSW Base Security requires the contractor to provide the Visitor Authorization Letter (VAL); Department of the Navy Local Population ID Card/Base Access Pass Registration, SECNAV 5512/1; Navy Region SW NCACS and Non-Affiliated Personnel Vetting Request forms fifteen (15) working days prior to the start of the contract.

The contractor shall submit the VAL on company letterhead to the TPOC. Following information is required for Security to process the contractor personnel: Contract number, Period of Performance, Full name, Citizenship, Social Security Number, Date of Birth, Place of Birth and Current Date of Local Records Check (https://www.nsopw.gov/en-us).

All CACs and identification badges issued to Contractor personnel shall be returned to the TPOC, Information Assurance (IA) Officer, or Government Security Department at the Government site in accordance with TPOC direction 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 TPOC’s direction in how to access the facility.

5.2.3.3 DD-254: The contractor shall comply with security requirements specified in the DD-254 attached to 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 of this contract for approval.

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

5.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 for public release by the appropriate United States government authority. Proposed public releases shall be submitted for approval prior to release through the Fleet Readiness Southwest Public Affairs Office, P.O. Box 357058, San Diego, CA 92135-7058 or 619-545-3415.

5.2.4.3 Loss, Compromised 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 SME, TPOC and Government Cyber Security Office within 24 hours of the incident occurring.

5.2.5 Operations Security (OPSEC):

OPSEC is a five step analytical process (identify critical information; analyze the threat; analyze vulnerabilities;

assess risk; develop countermeasures) that is used as a means to identify, control, and protect unclassified and unclassified sensitive information associated with U.S. national security related programs and activities. All personnel working under this task will at some time handle, produce or process Critical Information or CPI, and therefore all Contractor personnel must practice OPSEC. All work is to be performed in accordance with DoD OPSEC requirements, and in accordance with the OPSEC attachment to the DD254.

Applicable documents are as follows OPNAVINST F3300.53C (Series), Navy Antiterrorism Program, National Security Decision Directive 298 (Series), National Operations Security Program (NSDD) 298, DOD

5205.02 (Series), DOD Operations Security (OPSEC) Program, OPNAVINST 3432.1 (Series), DON Operations Security.

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

5.2.7 Navy Marine Corps Intranet (NMCI) Services. As of 01 October 2015, the Government provides all NMCI services; to include IT related hardware, software, and support, necessary for the performance of this contract/order.

Coordination of these services is to be conducted through the SME.

5.3 Detailed Support. The type of appropriation is Navy Working Capital Funds and it applies to all requirements described in Section 5.3.

The table below is provided to illustrate the current environment that is used and required in the IT/IM Department:

Software, tools, systems, applications, processes, and procedures (i.e., configuration management)

Current versions of: HyperText Markup Language (HTML) programming, JAVA programming, Java Script programming, C++, Procedural Language / Structured Query Language (PL / SQL), SQL*Plus programming, Cold Fusion, SAP Business Intelligence tools (current 4.x or more (Webi, Crystal, Xcelsius, Dashboard)), Crystal Reports and various tools, Quest Shareplex, Quest Foglight/TOAD, Informatica PowerCenter, Oracle database design, installation configuration and administration, Oracle SQL and PL/SQL, Oracle Tools installation, configuration, administration and utilization (Designer, Developer, Discoverer, Reports, etc.), DataWarehouse design, Kimball methodology, Data Load and Data Extraction, Forms and Reports, Internet/Chrome Browsers, UNIX programming, Microsoft Office Suite, Microsoft Outlook, NDMS-Suite of Applications (i.e., Maintenance, Repair and Overhaul ( MRO), Time and Attendance (TAA), Concept of Operations (CONOPS), ENG-16, etc.), Erwin Data Modeling Tool.

Operating Systems (including but not limited to)

All versions of: Windows, all versions of Sun, HP-UX (including V-Class, RP8400s, Superdome, Sunfire and Sunfox) and Veritas Storage Foundation.

Solaris, Red Hat.

Design and Implementation Tools and Architecture

All versions of: Web technology and tools, design and implementation, Oracle technology and tools, Oracle architecture, Business Objects/Universe tools, Dashboard tools, design and implementation, Windows and UNIX Operating Systems, Server Environments and Windows Desktop Environments, Internet Browsers, Data Warehousing, Design Methodology, Configuration Management Methodology and Tools, Project Management Methodology and Tools, and Department of Defense Architecture Framework (DODAF), Kimball, SAP Business Objects/Universe.

Platform Support UNIX and Windows Platforms including Operating Systems, File Systems, System and Application Installation, Administration, Configuration and Maintenance, and Data Archival and Retrieval in system-certified hardware environments, LINIX.

Configuration, Test and Deployment Support

Current versions of: Oracle Application Servers , Oracle Services Oriented Architectures (SOA), WebLogic, Websphere, Microsoft Internet Information Server, JBoss, Apache Tomcat, Apache HTTP, JAVA Application Servers, and Content Management Systems.

5.3.1 Business Objects Enterprise (BOE) Analyst/Business Objects Enterprise Analyst (BOE) Functional Matter Expert(SME) .

The contractor personnel shall assess and optimize the Business Intelligence (BI) environment to support information discovery, integration and sharing with the three FRCs. The contractor personnel shall define measures, metrics, dashboards and support analytical architecture necessary to monitor, manage and support sound decisions for the enterprise data environment. The contractor personnel shall analyze the business processes and develop models for subsequent use; develop data models in support of the various applications required. Further, the contractor personnel shall review documented requirements and present specific design recommendations to address the business and data requirements in terms of viability and impact on existing and new processes. The contractor personnel shall identify required data elements; define associated metadata and sources to support these and any requirements. Furthermore, the contractor personnel must be able to communicate these requirements fluently to Government and other contractor personnel (Knowledge Transfer).

The contractor personnel shall support the Business Objects Enterprise community. Contractor personnel supporting this PWS paragraph must be United States Citizens and at time of award hold a minimum of Secret clearance. Contractor shall have up-to-date training to meet Cybersecurity requirements to include but not limited to Security+ and Certified Business Intelligence Professional in accordance with paragraph 6.0 (Cybersecurity) of Attachment 1 and IAT LEVEL II Requirement.

Specific tasks include:

5.3.1.1 Manage, Maintain and Support Day-to-Day Operations of NDMS, SingleSite, OneNDMS, Data Convergence, Corporate Reporting System (CRS) and Other Initiatives. The contractor shall support development, standardization, testing, and quality assurance and configuration management procedures. Task includes standardization and maintenance of data dictionary, data structures and data repositories. The contractor shall support:

5.3.1.1.1 Business Objects Enterprise Analyst/Business Objects Enterprise (BOE Functional Subject Matter Expert

(SME):

Business Objects Enterprise Analyst shall;

Contribute to all technical aspects of building and maintaining Business Objects data warehouse for Enterprise-wide reporting of NAVAIR Depot Maintenance Systems (NDMS) applications and supplemental data

Create technical specifications for data conversion of Discoverer and Oracle reports to BOE Interface with Data Modeler to build warehouse and tables for supplemental data Review effectiveness of interfaces for accuracy and proper timing with ETL team Develop Universes, and coordinated changes with other Universe Designers Add definitions and source data to all elements of Universes Coordinate efforts with Programmers to write/test scripts for mass data clean-up projects Create, test and monitor reports and charts for local and Enterprise users Research problems using SQL to determine correct source for resolution Process all levels of Life Cycle Management documentation

Business Objects Enterprise (BOE) Functional Subject Matter Expert (SME) shall;

Review functional reporting requirements and translated to technical requirements Assist with assigning and maintaining security access of BOE users Facilitate Center of Excellence Enterprise User group for all FRCs Maintain RUG (Report User Group) list of actions, assigned priorities Produce training materials for Developers and users Train users in Adhoc report development Provide Enterprise-wide customer support and training in the use of BOE reporting and metrics Maintain data dictionary of over 6000 fields used in BOE Reporting Database Represent FRCSW in Corporate requirement meetings

5.3.1.1.2 Testing:

a. Prepares project plan, testing and implementation plans.

b. Establishes test criteria to ensure the most efficient use of the data modeling structure design.

c. Participates in system acceptability testing and implementation.

d. Works closely with the Extract, Transform, Load (ETL) personnel, system administrators, developers (including universe and report writers), application administrators, cybersecurity personnel, functional area specialists to ensure the most efficient system architecture is created and to resolve any problems that may arise.

e. Develop and execute test protocols for technical integration testing to include configuration, updates, patches and changes. Perform test and analyses to support process needs. Maintain technical specifications, assessment documentation, process test plans and any other documentation required.

f. Evaluates test results and initiates corrective action.

g. Support the quality assurance/testing team on integration and system testing activities.

5.3.1.1.3 Development:

a. Develop universes to ensure efficient use of facts and dimension tables.

b. Develop reports and charts to support end user requirements.

c. Develop regression test scripts to validate universes, reports, charts, and dashboards.

5.3.1.1.4 Troubleshooting:

a. Perform data analysis across multiple databases to identify source of data issues.

b. Determine best resolution for data issues and anomalies.

c. Revise ETL mapping specifications and/or stored procedures, as required, or work with ETL personnel for modifications/testing.

d. Revise associated regression tests, as required.

5.3.1.1.5 Management of assigned Projects:

a. Conducts risk and vulnerability assessments; identify vulnerabilities and risks.

b. Ensure Universe, Report, and Dashboard Design follows best practices..

c. Evaluate and provide awareness of security issues to management and ensure sound security principles are reflected in FRCs and Navy’s visions and goals.

d. Provide input to project management on task levels of effort, duration, production implementation dates when requested.

5.3.1.2 Software Development. The contractor shall support software development as tasked, using the configuration management procedures. SingleSite, OneNDMS and data convergence initiatives shall change directions of software development for FRCSW at a moment’s notice. The contractor shall review interfaces, programs, applications, etc., as required, to analyze impact of other applications. The contractor shall:

a. Create and update new interfaces / programs upon receipt of approval from the Configuration Review Board (CRB).

b. Track software trouble incidents per configuration management and trouble tickets.

c. Use above identified tools to perform coding and testing of approved CRB software change proposals, configuration management of source code versions.

d. Ensure documentation updates are complete and accurate.

e. Maintain compliance with NAVAIR, DON and DOD IA requirements and / or policies.

f. Define, document and enforce development standards and best practices, and contribute to operational policies and procedures (i.e., change control management; enhancements).

CDRL A005 – System / Software Process Documentation

5.3.1.3 Knowledge Transfer/Mentoring. The contractor shall provide knowledge transfer/mentoring on day-to-day system development functionality, including but not limited to, software development, coding, new technology, and informal training to the Government developers. The contractor shall:

a. Develop and maintain training material for personnel, including but not limited to, business process procedures. Conduct in-house training to Government personnel.

b. Provide for knowledge transfer and mentor the Government personnel in data business intelligence (BI) best practices.

CDRL A006 – Technical Documentation / Desk Guides / White Papers

5.3.1.4 Document Development Changes. The contractor shall document all development changes, and provide copies of interfaces, programs and documentation to configuration management.

CDRL A005 – System / Software Process Documentation

5.4 Labor Category Definition: See Attachment 3 for PASS Standard Labor Categories.

5.4.1 Certifications.

5.4.1.1 All Application Developers must meet the requirements identified in DoD Directive 8570.01M for Level II Information Assurance Technicians prior to the start of the period of performance and must maintain certification throughout period of performance. Certificate(s) must be provided to the SME / TPOC.

CLAUSES INCORPORATED BY FULL TEXT

C-202-H001 ADDITIONAL DEFINITIONS–BASIC (NAVSEA) (OCT 2018)

(a) Department - means the Department of the Navy.

(b) Commander, Naval Sea Systems Command - means the Commander of the Naval Sea Systems Command of the Department of the Navy or his duly appointed successor.

(c) References to The Federal Acquisition Regulation (FAR) - All references to the FAR in this contract shall be deemed to also reference the appropriate sections of the Defense FAR Supplement (DFARS), unless clearly indicated otherwise.

(d) National Stock Numbers - Whenever the term Federal Item Identification Number and its acronym FIIN or the term Federal Stock Number and its acronym FSN appear in the contract, order or their cited specifications and standards, the terms and acronyms shall be interpreted as National Item Identification Number (NIIN) and National Stock Number (NSN) respectively which shall be defined as follows:

(1) National Item Identification Number (NIIN). The number assigned to each approved Item Identification under the Federal Cataloging Program. It consists of nine numeric characters, the first two of which are the National Codification Bureau (NCB) Code. The remaining positions consist of a seven digit non-significant number.

(2) National Stock Number (NSN). The National Stock Number (NSN) for an item of supply consists of the applicable four-position Federal Supply Class (FSC) plus the applicable nine-position NIIN assigned to the item of supply.

(End of text)

C-204-H001 USE OF NAVY SUPPORT CONTRACTORS FOR OFFICIAL CONTRACT FILES (NAVSEA)

(OCT 2018)

(a) NAVSEA may use a file room management support contractor, hereinafter referred to as "the support contractor", to manage its file room, in which all official contract files, including the official file supporting this procurement, are retained. These official files may contain information that is considered a trade secret, proprietary, business sensitive or otherwise protected pursuant to law or regulation, hereinafter referred to as “protected information”. File room management services consist of any of the following: secretarial or clerical support; data entry; document reproduction, scanning, imaging, or destruction; operation, management, or maintenance of paper-based or electronic mail rooms, file rooms, or libraries; and supervision in connection with functions listed herein.

(b) The cognizant Contracting Officer will ensure that any NAVSEA contract under which these file room management services are acquired will contain a requirement that:

(1) The support contractor not disclose any information;

(2) Individual employees are to be instructed by the support contractor regarding the sensitivity of the official contract files;

(3) The support contractor performing these services be barred from providing any other supplies and/or services, or competing to do so, to NAVSEA for the period of performance of its contract and for an additional three years thereafter unless otherwise provided by law or regulation; and,

(4) In addition to any other rights the contractor may have, it is a third party beneficiary who has the right of direct action against the support contractor, or any person to whom the support contractor has released or disclosed protected information, for the unauthorized duplication, release, or disclosure of such protected information.

(c) Execution of this contract by the contractor is considered consent to NAVSEA's permitting access to any information, irrespective of restrictive markings or the nature of the information submitted, by its file room management support contractor for the limited purpose of executing its file room support contract responsibilities.

(d) NAVSEA may, without further notice, enter into contracts with other contractors for these services. Contractors should enter into separate non-disclosure agreements with the file room contractor. Contact the Procuring Contracting Officer for contractor specifics. However, any such agreement will not be considered a prerequisite before information submitted is stored in the file room or otherwise encumber the government.

C-211-H018 APPROVAL BY THE GOVERNMENT (NAVSEA) (JAN 2019)

Approval by the Government as required under this contract and applicable specifications shall not relieve the Contractor of its obligation to comply with the specifications and with all other requirements of the contract, nor shall it impose upon the Government any liability it would not have had in the absence of such approval.

C-212-W002 COMMERCIAL SUPPLIER AGREEMENTS (NAVSEA) (MAR 2019)

(a) Commercial Supplier Agreement means End User License Agreement (EULA), Terms of Service (TOS), or similar legal instrument or agreement.

(b) Any Commercial Supplier Agreement must be provided in full text as part of a quote or offer without hyperlinks.

(c) The contract/order Schedule and Federal Acquisition Regulation (FAR) 52.212-4, Contract Terms and Conditions—Commercial Items, shall take precedence over any conflicting provisions in a Commercial Supplier Agreement.

(d) If any requirement in the Commercial Supplier Agreement conflicts with Federal law or regulations (see FAR 12.212(a)), the following shall apply:

(i) Any such requirement is unenforceable against the Government.

(ii) Neither the Government nor any Government authorized end user shall be deemed to have agreed to such requirement by virtue of it appearing in the Commercial Supplier Agreement. If the Commercial Supplier Agreement is invoked through an “I agree” click box or other comparable mechanism (e.g., “click-wrap” or “browse-wrap” agreements), execution does not bind the Government or any Government authorized end user to such requirement.

(iii) Any such requirement is deemed to be stricken from the Commercial Supplier Agreement.

(e) Automatic renewals. License Agreements will expire at end of the term identified in the Purchase Order/Contract. Automatic renewals are not permitted and any such provision is void.

(f) Changes to the Commercial Supplier Agreement. Unilateral changes of the Commercial Supplier Agreement are impermissible and any requirement authorizing such changes is unenforceable. Changes must be in writing and executed by both parties to be effective.

(g) Third Part License (Embedded Software).

(i) The Contractor agrees that it has obtained all necessary licenses for the Government for any third party materials (including without limitation all Open Source licenses) provided within the product.

(ii) Contractor agrees that it complies with and shall continue to comply with all of its obligations under Third Party Licenses (including without limitation all Open Source licenses) associated with any third party materials provided within each product.

(iii) To the extent that the Government’s use of the software products licensed herein is in compliance with the Contractor’s Commercial Supplier Agreement, the Government’s use will also be in compliance with any Third Party Licenses.

(h) Audits. In lieu of any audit provisions in the Commercial Supplier Agreement, the Government agrees that, no more than once every twelve (12) months or within a reasonable time after a transfer, the Contractor shall, upon reasonable notice, have the right to require that the Government conduct an internal audit to ascertain and verify the number of licenses in use and to verify that the Government’s use of the product is in conformity with this Agreement. The Government is not required to use any tools provided by the Contractor to conduct the audit and shall not be required to pay for any tools provided by the Contractor to conduct the audit. The results of any such audit shall be kept confidential.

If verification discloses that the Government’s use is not in conformity with this Agreement, the Government agrees to resolve any noncompliance by either removing or correcting the unlicensed installation and use of the software identified by the audit as not in conformity with this Agreement.

(i) Confidentiality. Commercial Supplier Agreements’ terms and the final contract pricing may not be deemed confidential. Other marked confidential information will be appropriately guarded.

(j) Assignment. The Government shall have the right, without the prior written consent of the Contractor or its authorized resellers, to assign, reassign, or transfer software licenses among Government employees or the Government’s rights in the Contractor’s product to any governmental organization that is managed, operated, or controlled by the Government.

Such authorization includes sublicensing, and assignment or transfer among or between authorized users. In the event authorized users are reorganized or restructured such that their responsibilities and operations are transferred to another government agency, the agency shall have the right to assign the affected program licenses to a successor agency. The licensed agency and the successor agency agree to be bound to the Commercial Supplier Agreement as modified. The transferee shall be bound by the license metrics and limitations in this license. Government shall complete any documentation required by the Contractor to facilitate the transfer of this license, and continuation of support shall be the responsibility of the transferee.

For the avoidance of doubt, any assignment or transfer of licenses of the Contractor’s products is also subject to all other terms of the Commercial Supplier Agreement, as well as the Contractor’s policies governing product dependencies and version compatibility. Reassignment does not require that the license be under maintenance or support in order to execute a transfer.

(k) Litigation. Any requirement insisting that the commercial supplier or licensor control any litigation arising from the government’s use of the contractor’s supplies or services is deleted and unenforceable.

(l) Equitable Remedies. Equitable remedies, injunctive relief, and binding arbitration requirements shall not be enforced unless explicitly authorized by agency guidance or statute.

(m) Venue. Any claim or dispute shall be resolved under the Contract Disputes Act and FAR 52.233-1. The forum for resolution of disputes and applicable statutes of limitation shall be governed by federal law.

(n) Applicable law. In accordance with FAR 52.233-4, United States law shall apply to resolve any claim of breach of this contract and such actions shall be handled in the applicable Federal court of jurisdiction.

C-227-H006 DATA REQUIREMENTS (NAVSEA) (OCT 2018)

The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD Form 1423, Exhibit(s) , attached hereto.

(End of Text)

C-246-H001 EXTENSION OF COMMERCIAL WARRANTY (NAVSEA) (OCT 2018)

The Contractor shall extend to the Government the full coverage of any standard commercial warranty normally offered in a similar commercial sale, provided that such warranty is available at no additional cost to the Government. The Contractor shall provide a copy of the standard commercial warranty with the item. The standard commercial warranty period shall begin upon the final acceptance of the applicable material or software.

Acceptance of the standard commercial warranty does not waive the Government's rights under the "Inspection" clause, nor does it limit the Government's rights with regard to other terms and conditions of the contract. In the event of a conflict, the terms and conditions of the contract shall take precedence over the standard commercial warranty.

C-247-H001 PERMITS AND RESPONSIBILITIES (NAVSEA) (DEC 2018)

The Contractor shall, without additional expense to the Government, be responsible for obtaining any necessary licenses and permits for complying with any applicable Federal, State, and Municipal laws, codes, and regulations for shipping and transportation including, but not limited to, any movement over public highways of overweight/over dimensional materials.

Section D - Packaging and Marking

D-211-H001 PACKAGING OF DATA (NAVSEA) (OCT 2018)

Data to be delivered by Integrated Digital Environment (IDE) or other electronic media shall be as specified in the contract.

All unclassified data to be shipped shall be prepared for shipment in accordance with best commercial practice.

Classified reports, data, and documentation shall be prepared for shipment in accordance with National Industrial Security Program Operating Manual (NISPOM), DOD 5220.22-M dated 28 February 2006 incorporating Change 2 dated 18 May 2016.

D-211-H002 MARKING OF REPORTS (NAVSEA) (OCT 2018)

All reports delivered by the Contractor to the Government under this contract shall prominently show on the cover of the report:

(1) name and business address of the Contractor

(2) contract number

(3) sponsor:

(Name of Individual Sponsor)

(Name of Requiring Activity)

(City and State)

D-211-H004 IDENTIFICATION MARKING OF PARTS--BASIC (NAVSEA) (OCT 2018)

For all parts not subject to the marking requirements in DFARS 252.211-7003 – Item Unique Identification and Valuation, marking shall be accomplished in accordance with the following:

(1) Parts shall be marked in accordance with generally accepted commercial practice.

(2) In cases where parts are so small as not to permit identification marking as provided above, such parts shall be appropriately coded so as to permit ready identification.

D-246-H002 WARRANTY NOTIFICATION FOR ITEM(S) 0001-0002 —BASIC (NAVSEA) (OCT 2018)

The Contractor shall apply a permanent warranty notification stamping or marking on each warranted deliverable end item and its container. The notification shall be placed in close proximity to other required stamping or markings so as to be easily readable by personnel. The warranty notification shall read:

THIS ITEM WARRANTED UNDER CONTRACT N6426720TBD TO CONFORM TO DESIGN,

MANUFACTURING, AND PERFORMANCE REQUIREMENTS AND BE FREE FROM DEFECTS IN

MATERIAL AND WORKMANSHIP FOR TBD FROM DATE OF ACCEPTANCE. IF ITEM IS

DEFECTIVE NOTIFY TBD AND PCO.

D-247-H002 PACKAGING OF SUPPLIES—BASIC (NAVSEA) (OCT 2018)

Item(s) 0001-0002- The supplies furnished hereunder shall be packaged in accordance with ASTM-D-3951-15 approved 1 December 2015, Standard Practice for Commercial Packing.

D-247-H004 MARKING AND PACKING LIST(S) – BASIC (NAVSEA) (OCT 2018)

(a) Marking. Shipments, shipping containers and palletized unit loads shall be marked in accordance with ASTM- D-3951-15 approved 1 December 2015, Standard Practice for Commercial Packing.

(b) Packing List(s). A packing list (DD Form 250 Material Inspection and Receiving Report may be used) identifying the contents of each shipment, shipping container or palletized unit load shall be provided by the Contractor with each shipment. When a contract line item identified under a single stock number includes an assortment of related items such as kit or set components, detached parts or accessories, installation hardware or material, the packing list(s) shall identify the assorted items. Where assortment of related items is included in the shipping container, a packing list identifying the contents shall be furnished.

(c) Master Packing List. In addition to the requirements in paragraph (b) above, a master packing list shall be prepared where more than one shipment, shipping container or palletized unit load comprise the contract line item being shipped. The master packing list shall be attached to the number one container and so identified.

(d) Part Identification. All items within the kit, set, installation hardware or material shall be suitably segregated and identified within the unit pack(s) or shipping container by part number and/or national stock number.

D-247-W001 PROHIBITED PACKING MATERIALS (NAVSEA) (OCT 2018)

The use of asbestos, excelsior, newspaper or shredded paper (all types including waxed paper, computer paper and similar hygroscopic or non-neutral material) is prohibited. In addition, the use of yellow wrapping or packaging material is prohibited except where used for the containment of radioactive material. Loose fill polystyrene is prohibited for shipboard use.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government FLEET READINESS CENTER

SOUTHWEST

BLDG 334-3

P.O. BOX 357058

SAN DIEGO CA 92135-7058

Government

0002 Destination Government FLEET READINESS CENTER

SOUTHWEST

BLDG 334-3

P.O. BOX 357058

SAN DIEGO CA 92135-7058

Government

E-246-H013 INSPECTION AND ACCEPTANCE OF DATA (NAVSEA) (OCT 2018)

Inspection and acceptance of all data shall be as specified on the attached Contract Data Requirements List(s), DD Form 1423.

E-246-H016 INSPECTION AND ACCEPTANCE OF F.O.B. DESTINATION DELIVERIES (NAVSEA) (OCT 2018)

Item(s) 0001-0002 - Inspection and acceptance shall be made at destination by a representative of the Government.

E-246-H022 INSPECTION AND TEST RECORDS (NAVSEA) (JAN 2019)

Inspection and test records shall, as a minimum, indicate the nature of the observations, number of observations made, and the number and type of deficiencies found. Data included in inspection and test records shall be complete and accurate, and shall be used for trend analysis and to assess corrective action and effectiveness. The data shall, on request, be identified and made available for on-site review by the Contracting Officer or designated Government representative.

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 5 dys. ADC 1 FLEET READINESS CENTER…