Proposed_IDIQ_SOW_Section_C_-_steve.docx

DOCX document 44 KB Posted

Attached to
SUPPORT SERVICES for Acquisition management Systems Federal contract opportunity
Solicitation number
N00421-19-Q-0571
Issued by
Department of the Navy Naval Air Systems Command Naval Air Warfare Center

About this file

This sources sought announcement from the Naval Air Systems Command seeks capabilities statements from businesses interested in providing acquisition management system support services. The required services include application tools operation, development and sustainment support. The level of effort is estimated to be 240,000 labor hours annually across various labor categories including program managers, software developers, computer programmers, quality assurance analysts, systems analysts, and technical writers. Interested businesses must submit a capabilities statement no more than 10 pages in length by September 6th demonstrating relevant experience on similar contracts valued over $27 million, company and staffing resources, and the ability to begin performance by the projected award date. The work will be performed primarily in Patuxent River, Maryland. The incumbent is Precise Systems, Inc. under contract N00421-18-C-0005.

Draft Statement of Work

View the file

Other files for this federal contract opportunity

Other files attached to SUPPORT SERVICES for Acquisition management Systems, newest first.
File Type Posted
Copy_of_Initial_Draft_Labor_Categories_for_IDIQ_effort.xlsx XLSX spreadsheet

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Section C - Descriptions and Specifications

STATEMENT OF WORK

STATEMENT OF WORK (SOW)

for Naval Air Systems Command (NAVAIR) 1.7 Acquisition Management System (AMS) Application Tools Operation, Development and Sustainment Support

1.0 GENERAL INFORMATION

1.1 Background

Air 1.7 is a part of the Air 1.0 Competency at the Naval Air Systems Command (NAVAIR) located at Patuxent River, Maryland. Air-1.7 is responsible for the development, sustainment, management, and oversight of various Acquisition Management System (AMS) tools and software applications deployed command-wide across the NAVAIR Enterprise as well as at select external organizations (e.g. Naval Supply Systems Command, United States Air Force, United States Marine Corps, United States Army, and United States Coast Guard).

1.2 The AMS suite of tools consists of both new software development and sustainment of existing software. AMS standardizes and streamlines common program management and procurement functions. AIR 1.7 requires management and technical support for the operation, development, sustainment, training and management of AMS web-based applications to include Data Visualization of the information gathered. Technologies supporting AMS include custom developed applications such as the Procurement Management Tool (PMT), the Contract Data Requirements List (CDRL) tool, the Common Spend Plan Tool (CSPT) and the Knowledge Management System (KMS). These custom applications leverage workflow products, SharePoint and Visual Studio (.NET) solutions. Management and technical support includes AMS development, AMS requirements analysis, data visualization requirements analysis, user case analysis, design, development, sustainment, testing, training, documentation and implementation of revisions and updates throughout the Software Development Life Cycle (SDLC). The AMS suite of applications tools includes the following: Procurement Management Tool (PMT) Acquisition Plans (AP) Tool, Common Spend Plan Tool (CSPT) the Knowledge Management System (KMS) and the Contract Data Requirements List (CDRL) Tool. Additional Tools under consideration are the Engineering Change Proposal (ECP) Tool, the Programmatic Environment Safety and Occupational Health Evaluation (PESHE) Tool, the “Should Cost” Tool and the Government Furnished Equipment (GFE) Tool as well as other tools that support acquisition. In addition, the AMS suite of applications tools interfaces with various external sources.

2.0 SCOPE

The scope of this contract covers Software, Applications Management and Support Services to include providing application tools operation, development and sustainment support to AIR 1.7 and its respective customers and stakeholders.

2.1 The Contractor shall provide all personnel, incidental materials, and other items (except as specified in the Section 7.0 of this document entitled “Government-Furnished Resources”) and services necessary to perform the tasks defined in this Statement of Work (SOW).

2.2 The SOW for this tasking will utilize the Navy Working Capital Funds (NWCF) type of funding.

2.3 The contractor shall participate in bi-weekly meetings to support the effort/tasking required by this SOW. Tasking will be delegated from the COR/ACOR to the Program Manager and Other Key Personnel at the bi-weekly meeting. Tasking may be delegated more frequently on an ad hoc basis from the COR/ACOR to the Program Managers as deemed necessary.

2.4 The contractor shall coordinate all efforts with the Government Contracting Officer’s Representative (COR) and Technical Point of Contact (TPOC) (or designated alternates-Alternate Contracting Officer’s Representative (ACOR) and Alternate Technical Point of Contact (ATPOC)) to ensure conformance and consistency with contract requirements. The contractor shall provide support, if during contract performance; information systems and technologies identified herein are required to migrate under the Navy Enterprise Resource Planning (ERP) umbrella or transition to other NAVY enterprise solutions. The customer base and technologies supported may change and increase as consolidation efforts continue throughout the Navy.

2.5 Inherently Governmental Functions- No item in this SOW shall be interpreted to have the contractor perform any services that are inherently governmental services or personal services as defined in Federal Acquisition Regulation (FAR) Part 2.101 - (See "Inherently governmental function" and "Personal services contract").

2.6 Business Service Areas/Sub-Service Areas. The Contractor shall perform all of its IT Service Area delivery activities (Table-1), which at a minimum includes the following:

Service Areas - Table 1

Business Service Area
Business Sub-service Area
Summation of Services

Software & Applications Management

Application Tools Operation/ Development/Sustainment

· Technical Design & Development

· Software Development

· Software Operations and Sustainment

· Functional Design/System Specifications

· Production Support

· Life Cycle Support

· Requirements/Systems Analysis

· Requirements Documentation

· Software and Development Documentation

· Software Configuration Management

· Security Compliance

· Security Technical Implementation Guide (STIGs) and STIG Compliance Testing

· Clinger Cohen (OSD Certifications)

· Project Management

· Project Reporting

· Requirements Management

· Test Management

· Research/Studies/Analysis

· Business Requirements Process Improvements

· Technical Consulting Service

· Quality Assurance

· Training

· Training Documentation (both Classroom and Ad-Hoc)

· Help Desk Support

· Technical Writing

· Section 508 Compliancy

· Peer Reviews

· Business Process Management

· Workflows

· Documentation

· Software Testing

· Product Testing

· Reporting

· Software Maintenance

3.0 REQUIREMENTS (CLINs 0001, 0101, 0201, 0301, and 0401)

The following sections outline the AMS specific technical, program management, and support services.

3.1 AMS Technical Services/Requirements

The contractor shall:

3.1.2 Perform AMS software application development and sustainment tasks throughout the Software Development Life-Cycle (SDLC).

3.1.3 Remain current on technological advances relevant to the AMS requirements and capabilities supported and provide documented recommendations on strategic planning for future initiatives that offer cost savings and efficiencies. The contractor shall provide recommendations to sustain and improve existing and new business systems Information Technology requirements.

3.1.4 Perform AMS Data Visualization development and sustainment tasks in support of improved data analytics and analysis to include enhanced program level data presentations that support improved customer review of program data, more timely and complete program evaluations and new business development. The contractor shall provide recommendations to sustain and improve existing Data Visualization Tools such as Tableau, Qlik, Power BI, etc. as well as recommendations on new Data Visualization requirements.

3.1.5 Maintain familiarity with DON and/or NAVAIR policy and concepts including IT consolidation, Functional Area Management (FAM), Navy Networks, Navy Enterprise Licensing agreements, Navy Information Dominance Approval process (NAV-IDAS), and Competency Aligned Organization (CAO).

3.1.6 Comply with Command initiatives including Navy ERP and AIRSpeed; perform in accordance with NAVAIR, DOD, and DON initiatives, standards, policies, and mandates such as Application Portfolio Management, Defense Business Transformation Guidance, Clinger Cohen Act, Federal Information Security Act (FISMA), Web Enablement and 508 Compliance.

3.1.7 Provide functional and operational support and assistance in the development, restructure, and/or revision of AMS applications and technologies; associated training; and reference materials.

3.1.8 Quality Assurance

The contractor shall provide personnel and resources in support of Quality Assurance which includes requirements management, use cases, peer reviews, testing, training and system documentation.

The contractor shall:

a) Assist with department-wide proof reading and composition of inter-department communication, communiqués and command announcements.

b) Provide support to ensure developed software is compliant with Section 508 of the Rehabilitation Act.

c) Provide support to develop software test plans and perform testing for application releases and provide release notes.
d) Perform software testing as required.
e) Work with project leads and software development personnel to identify test scenarios.
f) Provide support to develop and schedule testing scripts as required.
g) Analyze and report test results as required. Test results shall be stored in Team Foundation Server (TFS).
h) Validate that all software is in compliance with Defense Information Systems Agency (DISA) Application Development Security Technical Implementation Guides (STIGs).

3.1.9 Priority Levels and Help Desk Support Response Requirements

The Contractor shall manage service delivery and perform services in accordance with the prioritization schema and incident response requirements as described below:

Priority Levels - Table 2

Priority Level

Definition

Priority Level 1 – Emergency / Urgent - Critical Mission / Business Impact
CRITICAL – Multiple End-User impact with no workaround. The Incident or Problem has caused a complete and immediate work stoppage affecting an entire Unit or Command Group or primary mission/business process or a broad group of End-Users, or a key customer is affected (VIP Support).

Priority Level 2 –Non- Critical Standard Mission / Business Impact

STANDARD – Multiple or single end-user impact with approved workaround. A business process is affected in such a way that certain functions are unavailable to End-Users or a system and/or service is degraded.

During Core Business Hours, the Contractor shall make initial contact with the requestor immediately upon receipt of all trouble ticket/incidents. Priority 1 trouble tickets/incidents shall be acknowledged within thirty (30) minutes of assignment while Priority 2 trouble tickets/incidents shall be acknowledged within sixty (60) minutes of assignment.

3.1.10 Government Technical Environment. The contractor shall develop and sustain the Acquisition Management System using information technologies supported by IT/IM 7.2.2. The 7.2.2 IT/IM environment is dynamic, therefore, the current architecture will evolve over time as new software requirements and technological advances occur. The following is a high-level representation of the current software inventory/architecture

Government Technical Environment - Table 3

Support Area

Current Tool Set

Call Tracking System Software

HEAT, Knowledge Database

Collaboration / Portal

MS SharePoint, LiveLink (Open Text); including COTS Third Party Tools and Bolt-on Software

Configuration Management / Software Life Cycle

Team Foundation Server (TFS)

Data Mining & Visualization Reporting
Tableau, Qlik, Power BI, SQL Server Reporting Services (SSRS), Excel

Databases & Tools Oracle, MS SQL Server

Documentation
MS Office Suite, Adobe Acrobat Professional

Electronic Data Management System (EDMS) and Workflow e.POWER, Hummingbird (Open Text), Nintex

Operating Systems

Windows

Program Management Tools

MS Project Server / MS Project Professional

Remote Access Software
Citrix

Search Engine

Google Search Appliance (GSA), FAST (Microsoft)

Web Development ColdFusion, HTML, XML, jDeveloper, EXT JS Javascript Library, Visual Studio Suite of Tools (.NET), ASP, SharePoint Designer, EXT JS- Sencha, J2EE, Telerik, Powerbuilder/DataWindow .NET, Adobe Creative Suite, Beyond Compare, Dev Express, ASPOSE

Web Based Training
Adobe Connect
Web Server Software
IIS, ColdFusion

3.1.11 The contractor shall:

a) Plan and support Systems Development Life Cycle (SDLC) methodologies which include IT project management and systems engineering utilizing Capability Maturity Model Integration (CMMI) best practices.

b)Support all phases of the software life cycle, including requirements analysis, system and database design/analysis, graphics design, user interfaces, system documentation, software development, peer reviews, testing, implementation, and sustainment. This includes use cases, Software Design Documentation (SDD) and/or redesign of application programs as well as initial coding, revising, testing, documenting, operating and maintaining all custom software and maintaining documented configuration management controls.
c)Perform application configuration management via Team Foundation Server (TFS) or other government agreed upon configuration management tool. TFS or other agreed upon configuration management tool shall provide source code management to include where all software shall be stored, reporting, requirements management, project management (for both agile and waterfall software development methodologies), automated software builds, lab management, testing, and release management capabilities that cover the entire SDLC.
d)Perform requirements management, which includes requirements gathering, analysis, and development of a Software Requirements Specification (SRS) for all development activities.
e)Implement solutions in a wide range of software environments using many different programming tools and languages.
f)Prepare logical database models and store these models in a Team Foundation Server (TFS).
g)Develop, test, and implement queries and reports.
h)Develop, test and implement interface(s) to internal/external systems and databases. All interfaces must be documented in the software design documentation.
i)Construct and sustain internet and intranet web sites using standard technologies as referenced in Table 3, Section 3.1.9.
j)Support search engines within web sites, web applications and commercial software.
k)Provide Help Desk support process(s) for applications developed/supported, to include Priority Levels and Help Desk Support Response Requirements as defined in Section 3.1.8 .
l)All software shall be compliant with Defense Information Systems Agency (DISA) Application Development Security Technical Implementation Guides (STIGs) and the STIGs are applied and/or mitigated. Refer to http://iase.disa.mil/stigs/Pages/index.aspx
m)Provide Department of Defense Information Technology Portfolio Repository – Department of the Navy (DITPR-DON) and DON Application and Database Management System (DADMS) support for Operation and Maintenance (O&M) products and COTS applications. This may include providing support and maintaining information on Last Date Allowed extensions, Unit Identification Code (UIC) Stakeholder Requests and New Version Requests.
n)Provide support for emerging/new technologies and emerging trends within the software development discipline.

3.1.12 Standard Operating Procedures (SOP)

In accordance with Contract Data Requirements Lists (CDRLs) A002 Software Requirements Specification (SRS), A003 Software Design Documentation (SDD), and A004- Database Design Documentation: The contractor shall update/develop SOPs for Application Development and Maintenance that includes a documented description of the development methodologies leveraged to perform development and maintenance tasking for all developed tools within the AMS suite of tools.

3.2 Program Management

The contractor shall:

3.2.1 The contractor shall be responsible for following through on tasks until complete; document or update applicable processes, files, databases, training aids; and provide software tool availability to end users.

3.2.2 The contractor shall provide the status of supported AMS projects and tasks via notification to the COR, ACOR, TPOC and ATPOC of any programmatic or logistics problems and/or resolution of problems immediately upon discovery of the problem(s).

3.2.3 Schedule and attend support meetings and provide input and recommendations as required to resolve issues to achieve contract objectives. This will include but is not limited to taking notes and tracking action items.

3.2.4 Support the customer in the implementation and execution of software requirements identified by the TPOC or ATPOC.

3.2.5 The contractor shall integrate and coordinate all activities required to execute tasking that meets cost, schedule, and performance requirements.

3.2.6 Contractor shall provide a Program Manager, Business Operations and Systems (Program Manager) who shall be responsible for the management and oversight of work performance and contractor personnel. The Program Manager shall:

a)Serve as a POC for customer relations
b)Oversee all program controls are applied to each task area including scheduling, resource allocation, direction, cost quality control, report preparation, establish and maintain records and provide resolution of customer complaints
c)Resolve quality, timeliness and accuracy issues

d) Review Contract Data Requirements List (CDRLs) data deliverables for completeness and quality before submission to the Government

e)Ensure consistent on-board and off-board of personnel, including obtaining Common Access Cards, Completing SAAR-N, Security background checks and seat assignments.
g)Coordinate with all project team members for compliance with program objectives and

validate they are within cost, performance, and schedule requirements.

h)Coordinate utilization of resources across projects
i)Manage project risks and dependencies
j)Evaluate IT strategies and IT software life cycle standards
l)Attend meetings with the COR/ACOR and or TPOC/ATPOC to discuss performance under the awarded contract to include resolution of any issues or challenges.
m)Recommend new and innovative technical solutions to streamline functionality and reduce life cycle costs.

3.2.7 Minor Incident Response

The contractor shall support the incident response process for minor/routine incidents. Minor incidents are those incidents that have limited impact to operations and do not pose a significant impact to customers or threat to DOD data or service delivery. These could include events such as a server or database outage, appliance malfunction, minor malware incidents and network outages. Minor incidents are considered part of core business hours.

3.2.8 Software and Applications Management

The contractor shall provide software development life cycle support for software applications, web applications, websites, and collaboration environments.

3.2.9 Project Analyst/ Project Support Specialist(s)

The contractor shall pursue technologies capable of increasing performance and efficiency which can be economically integrated into current and proposed systems. Contractor personnel shall provide Data Visualization and AMS expertise, based upon their broad knowledge to include emerging trends and techniques as well as their understanding of current and projected DON acquisition policies and procedures.

The Project Analyst/Project Support Specialist(s) shall:

a) Provide a comprehensive, overarching project management approach to ensure costs are controlled, schedules are met, return on investment (ROI) is maximized and business/program objectives are attained.

b) Track actual vs. planned completion dates of tasks and project milestones.

c)Prepare and present project reviews and reports using Team Foundation Server (TFS)
d)Develop and maintain an integrated Plan of Action & Milestones (POA&M).
e)Provide submission of data calls.
f)Research and analyze capabilities of Government Off-The-Shelf (GOTS), Commercial Off-The-Shelf (COTS), and application software packages. Some tasks may require studies to determine the applicability of software to specific functional and/or operational environments. The contractor shall research and analyze next generation software languages, tools, techniques, and methodologies. Others may require contractor review of existing code and software to evaluate maintainability, efficiency and performance. The contractor shall stay abreast of the latest technologies and perform an assessment of products and services and make recommendations for efficiencies.
g)Provide technical management of supporting contractor team members within the following labor categories: Computer Programmer IV; Computer Programmer II; Computer Specialist; Project Support Specialist, Senior; Project Support Specialist; Project Support Specialist, Junior; Technical Writer III; Technical Writer II, Training Specialist I and other contractor support team personnel as well as technical assistance to the training team to include the training material.
h)Ensure all tasks and customer driven issues are documented, responded to and resolved in the appropriate timeframe based on priority in accordance with Section 3.1.8, Table 2.

3.2.10 TRAINING (CLINs 0001, 0101, 0201, 0301 and 0401)

The contractor shall:

3.2.10.1 Provide training on AMS tools and Data Visualization tools to members of the AMS user communities. Training may take several forms during execution of this contract including classroom training, regular/recurring informal training events (e.g., Brown Bag sessions), specialized training for users, video training addressing particular topics or as otherwise requested. The contractor shall develop AMS and Data Visualization course curriculum and training resources (e.g. user guides cue cards etc.) and deliver under Data Item No. A007.

3.2.10.2 Prepare/develop Data Visualization and AMS software applications related documentation such as user manuals, graphics, training guides, brochures, software development plans, requirements documents, requirements traceability matrix, training resources and test/implementation plans. The documentation shall be stored in AIR 1.7 AMS SharePoint Training Center.

3.2.10.3 Develop end user Data Visualization and AMS application guides in government-approved format such as PDF, Microsoft Word and/or on-line HTML help.

3.3 Hours of Operation / Principal Place of Performance / Flextime.

Work in support of this SOW will be performed primarily at Patuxent River, MD. However, the place of performance is not limited to this location due to the evolving, integrated and capability-focused enterprise requirements throughout NAVAIR. The contractor shall ensure the skill set, stability, and continuity of the work force when hiring personnel to ensure the uninterrupted performance of all tasking.

3.3.1 Implementation of a Compressed Work Schedule (CWS) is authorized subject to the limitation outlined in the paragraphs below. Contractor work schedules shall be coordinated with the TPOC 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. If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, the Contractor agrees that any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Furthermore, the Contractor shall comply with the requirements of the Fair Labor Standards Act and particularly with Section 7 regarding compensatory overtime. The CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage when required by the Government.

3.3.2 The Government reserves the right to terminate CWS schedules on a case by case basis or by team if there is evidence of abuse, poor performance, or impacts to project schedules. The Government will provide written notice of a request for CWS termination within two (2) weeks of desired termination. Depending on the situation CWS termination could be temporary or permanent.

3.3.3 The Contractor shall have the overall responsibility of staffing to ensure IT service and support is available during core work hours defined as Monday through Friday from 0700 to 1700 Eastern Standard Time (EST) (excluding Federal holidays). The contractor shall ensure maximum coverage and incident response.

3.3.4 Telework Availability. Telework eligibility will be authorized on a case by case basis, with agreement by the COR in conjunction with TPOC/ATPOC. The contractor shall adhere to all applicable federal laws and regulations. Individual DOD Service guidelines shall be adhered to as well.

3.3.5 Installation Closure. Occasionally local installations (e.g. NAS/PAX River) will be closed unexpectedly due to inclement weather or other reasons. Notification is normally by way of local radio or television (TV) stations. Information concerning other methods of notification will be provided by the Government. 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 their normal start time and the delayed reporting time. Note: NAS/PAX River closures may not coincide with closures for the DC Metro Area.

3.3.6 Occasionally, an installation or activity may be closed on short notice (e.g. building AC stopped working and indoor temperatures are rising to high levels). The contractor will receive direction from the COR regarding whether or not some services will need to be provided during these instances. During installation/activity closure, should there be a need to postpone or cancel some or all services, the COR / ACOR reserves the right to do so with written notice to the Contractor Program Manager. When the Government provides such notice, the Contractor shall immediately stop the work requested and the Government shall not be charged or be expected to pay for services not rendered (i.e. the Government will not pay for services not delivered).

4.0 Reserved

5.0 Other Direct Costs

5.1 Travel / Other Direct Costs (Travel Costs) (CLINs 0003, 0103, 0203, 0303, and 0403)

5.1.1 Other Direct Costs (ODCs) (Travel) are based on a per annum amount. Estimates of all ODC costs shall be compiled and submitted for review and pre-authorization/ approval by the COR in conjunction with TPOC/ATPOC. ODCs shall not include profit/fee.

5.1.2 Costs associated with travel and lodging shall be reimbursed in accordance with the Joint Travel Regulations. The number and types of trips, including the number of personnel traveling, shall be limited to the minimum required to accomplish work requirements and shall be authorized and approved in advance by the COR.

5.2 Material / Other Direct Costs (Material Costs) (CLINs 0004, 0104, 0204, 0304, and 0404)

5.2.1 Other Direct Costs (ODCs) (Material). Estimates of all ODC costs shall be compiled and submitted for review and pre-authorization/ approval by the COR in conjunction with TPOC/ATPOC. ODCs shall not include profit/fee.

5.2.2 The contractor shall provide material or other items which are necessary or integral to the performance of tasking included in this SOW.

5.2.3 All material purchased by the Contractor under this item becomes the property of the Federal Government. Any material remaining after completion of the contract, the cost of which has been reimbursed by the Government, will remain Government property and disposition instructions will be sought from the Procuring Contracting Officer.

5.2.4 Renting or leasing of facilities will not be allowable as a direct charge to this contract.

6.0 Increased Capacity

6.1 Increased Capacity for Service Labor (CLINs 0002, 0102, 0202, 0302, 0402) These CLINs are provided to address an increase to the current estimated ceiling of the base year and the option years if the Government determines a need for up to a 10% increase. Increased Capacity labor support will include the tasking as shown in Paragraph 3.0 and applicable subparagraphs. Increased Capacity is subject to clause H-1 of this contract.

6.2 Increased Capacity for Other Direct Costs (CLINs 0005, 0105, 0205, 0305, 0405) These CLINs are provided to address an increase to the current estimated ceiling of the base year and the option years if the Government determines a need for up to a 10% increase. Increased Capacity ODC support will include the tasking as shown in paragraph 5.0 and applicable subparagraphs. Increased Capacity is subject to the H-1 of the contract.

7.0 GOVERNMENT FURNISHED PROPERTY AND INFORMATION

7.1 All Government furnished information, material and equipment will be specified in accordance with FAR clause 52.245-1. All Government Furnished Property (GFP) and Government Furnished Information (GFI) is the property of the U.S. Government and shall not be transferred by any individual or agency public or private without the express written approval of the Contracting Officer.

7.2 Facilities, Supplies and Services. 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. The workspaces will be available twenty-four hours a day; however core work hours are defined as Monday through Friday from 0700 to 1700 Eastern Standard Time (EST) (excluding Federal holidays).

7.3 Information. The Government will provide the Contractor copies of, or access to, all required directives, publications, and documents, as available.

7.4 Regulatory Documents. A comprehensive list of Navy regulatory documents can be found at the DON Chief Information Officer (CIO) IT Policy and Guidance website, http://www.doncio.navy.mil/. Throughout the life of this contract, if any policy, instruction, or regulation is replaced or superseded, the replacement or superseding version shall apply. The contractor is responsible for researching and complying with any additional regulations applicable to the task areas in which they are involved.

8.0 DATA RIGHTS

8.1 The Government shall have unlimited rights to all application code and data as well as all supporting documentation for any new or modified software developed under this contract in accordance with the DFARS. Additionally, in accordance with CDRL A001 Source Code-the contractor shall provide the Government unlimited enterprise-wide rights to software use at Government installations.

9.0 CDRL Data Submittals (Status Reporting) (CLINs 0006, 0106, 0206, 0306 and 0406)

9.1 Contract Deliverables. The Contractor shall provide the following contract deliverables. All deliverables’ requirements are set forth in each CDRL and this contract. The Contractor shall be responsible for delivering all Data.

CDRL Listing

CDRL
TITLE
A001
IT Source and Related Code
As Required
A002
Software Requirements Specification (SRS)
As Required
A003
Software Design Documentation (SDD)
As Required
A004
Database Design Documentation
As Required
A005
Status Report
Monthly
A006
Funds and Man Hours Expenditure Report
Monthly
A007
Training Support Documents
As Requried

9.2 In accordance with CDRL A005 Status Report-The contractor shall provide a monthly status report to summarize accomplishments during the reporting period and clearly demonstrate that the Performance Requirements Summary (PRS) objectives were satisfied for the reporting period. The report shall also include planned vs. actual task completion to include any milestones, anticipated activity (including anticipated CDRL deliveries) for the next reporting period, lessons learned, risks, outstanding issues, and recommendations.

9.3 In accordance with CDRL A006 Funds and Man Hours Expenditure Report, the contractor shall provide financial resource reporting by CLIN and a listing of contract actions by CLIN and date as follows:

9.4 Cost Plus Fixed Fee (CPFF) CLINs: The contractor shall provide information to include, but not limited to cost details (i.e., Employee Name, Labor Category, Rate, Current and Cumulative Hours & Costs etc.), financial status of cost CLINs (i.e., funding applied, expenses incurred during current reporting period, total expenses to date, amount remaining, etc.) and forecast of funds depletion by CLIN type based on known requirements.

9.5 Cost Reimbursable CLINs: The contractor shall provide information to include, but not limited to cost details (i.e., Traveler’s Name(s), Dates of Travel, Destination, & Purpose for travel; Item/Name, Description, Unit Cost, Number of Units, & Extended Costs for ODC’s/Material, etc.), financial status of cost CLINs (i.e., funding applied, expenses incurred during current reporting period, total expenses to date, amount remaining, etc.) and forecast of funds depletion by CLIN type based on known requirements.

9.6 In summary, the contractor provided status/financial reporting will be in accordance with each CLIN and SubCLIN as follows:

· AMS and Data Visualization Support

· AMS and Data Visualization Training

· Other Direct Costs (Travel)

· Other Direct Costs (Material)

· Technical Data

10.0 SECURITY

10.1 Information Technology Security- The contractor shall ensure compliance with The Department of the Navy (DON) Automated Data Processing (ADP) Security Program outlined in OPNAVINST 5239.1B, or the most current version of this instruction, while performing all tasks under this contract.

10.2 Security Clearance. 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.

10.2.1 Only United States citizens may perform services under this contract. The contractor shall conform to the provisions of the DOD-D-5220.22, ‘National Industrial Security Program,’ and shall obtain security clearances for contractor employees requiring access to classified information and/or entry to controlled areas. Some tasks may require up to Secret level although most work will be unclassified. Contractor personnel shall have the ability to obtain a Secret level clearance if required. All Key personnel shall have, at a minimum, an approved interim Secret clearance within 60 days after contract award. Any person having a security clearance revoked for any reason shall be ineligible to perform under this SOW. The contractor shall educate and brief employees concerning the handling and protection of classified material, and other security measures as described herein in accordance with DODD-5220.22, National Industrial Security Program. The Contractor shall comply with mandates for annual security training.

10.3 System Authorization Access Request (SAAR). All contractor personnel requiring a Common Access Card (CAC) or access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form (OPNAV 5239/14 Jul 2008) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work. On-site contractor employees shall cooperate with Government investigative agencies conducting criminal or administrative investigations.

10.4 Common Access Card (CAC). Eligible contractors shall be issued a Common Access Cards (CAC) by the Government to on-site personnel. The CAC 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 NASPAXRIVINST 5510.15Q, ‘Regulations Governing Admission to the Naval Air Station, Patuxent River and Webster Field, Maryland’ concerning the use and possession of badges. The contractor is responsible for ensuring that all identification badges issued to their employees are returned to the Security Department at the Government site in accordance with NASPAXRIVINST 5510.15Q, following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative.

10.5 Contractor Access. The Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with NASPAXRIVINST 5510.15Q to gain admission to the Naval Air Station, Patuxent River and Webster Field, Maryland.

10.6 Policy Adherence. DOD and DON IA Program outlined in Secretary of the Navy Instruction (SECNAVINST) 5239.3A, ‘DON Information Assurance Policy’ and SECNAV M-5239.1, ‘DON Information Assurance Manual,’ apply to efforts under this contract. Contractor personnel providing services under this contract shall comply with all federal, DOD, DON, and NAVAIR IA policies. The contractor shall comply with SECNAVINST 5510.30B and SECNAV M-5510.30 to assure that the proper security investigation is conducted for those contractor personnel performing services under this contract.

10.7 Classified Spillages. The number of classified spillages on Defense Department information systems continues to rise, resulting in significant costs to NAVAIR, particularly in light of the current resource-constrained environment. To that end, it is incumbent upon the Contractor to pay for the containment, clean up, and remediation of any classified spillage that is the result of the unauthorized disclosure of classified information by any employee of the Contractor working under the provisions of this SOW. Classified data spills occur when classified data is introduced either onto an unclassified information system, to an information system with a lower level of classification, or to a system not accredited to process data of that restrictive category.

10.8 Disclosure of Information. Contractor employees shall not discuss nor disclose any information obtained during the execution of the contract to parties other than the originator of the information, authorized Government personnel, or COR personnel. Improper disclosure of information may be grounds for removal of contractor personnel. A signed non-disclosure agreement (NDA) for each employee scheduled to work on the contract/contract shall be provided to the TPOC and COR before the employee may begin performance on the contract.

10.9 All contractor personnel performing in support of this contract shall complete company sponsored Organizational Conflict of Interest (OCI) training within fourteen (14) calendar days after contract award. NDA requirements are stated in the “Disclosure of Information”, annual Government training may be required.

11.0 Standards of Quality and Timeliness - The Contractor shall have a Contractor managed Quality Assurance Program. The Quality Assurance shall be managed in accordance with attachment J4, Surveillance Activity Checklist (SAC).

12.0 Compressed Work Schedule (CWS)

(a) The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including a 30-minute lunch break), from 0700-1700 each Monday through Friday (except on the legal, Federal Government holidays specified elsewhere). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800 Monday – Friday. Services and staffing shall be provided for each office at least 8 hours per day (during the 8.5 hour workday, which includes the 30-minute lunch break).

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

(c) The Contractor may allow its employees to work a CWS schedule. Flextime workers shall not start earlier than 0600 and not later than 0830. Contractor may not occupy activities spaces without Government personnel present. Core hours of work are from 0700 to 1700 daily. All employees are expected to be available during core hours. Any Contractor that chooses to allow its employees to work a CWS schedule in support of this contract agrees that any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government.

(d) All Contractors shall comply with the requirements of the Fair Labor Standards Act and particularly with Section 7 regarding compensatory overtime. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage when required by the Government.

File details come from the government source that posted it. Updated .