SOW_for_follow-on_steve.docx

DOCX document 72 KB Posted

Attached to
Support services for acquisition management systems tools
Solicitation number
N00421-16-R-0047
Issued by

About this file

draft statement of work

View the file

On GovTribe

Work with this file

  • 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

SOW

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, 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 In particular, the tools being developed for the AMS standardize and streamline common program management and procurement functions. Specifically, a centralized AMS data site is provided to access applications that are necessary for the management and execution of procurements and requirements. AIR 1.7 requires management and technical support for the operation, development, sustainment, training and management of AMS web-based applications and the technologies supporting acquisition management to include custom developed applications such as workflow products, SharePoint solutions and Visual Studio (.NET) solutions. Included in this management and technical support should be managing and implementation of the Software Development Life Cycle (SDLC) for AMS development, application and database program requirements analysis, user case analysis, as well as design, development, testing, training and implementation of revisions, updates, and additions to the AMS tools and/or software and the documentation that supports these efforts. At present the AMS suite of applications tools either includes or will shortly include the following: Procurement Management Tool (PMT), Acquisition Plans (AP) Tool, Command Spend Plan Tool (CSPT) and the Contract Data Requirements List (CDRL) Tool. Additional Tools under consideration are the Engineering Change Proposal (ECP) Tool and the Government Furnished Equipment (GFE) Tool as well as other tools that support acquisition.

2.0 SCOPE

The scope of this contract covers Software and Applications Management and Support Services to include providing application operation, development and sustainment support to AIR 1.7 and its respective customers and stakeholders (including Joint Information Technology projects and Navy Enterprise Applications).

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 task defined in this Statement of Work (SOW). No tasking in support of this SOW will be used to procure any inherently governmental or personal services.

2.2 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 NAVY enterprise portals. The customer base and technologies supported may change and increase as consolidation efforts continue throughout the Navy.

2.3 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.4 Business Service Areas/Sub-Service Areas. The Contractor shall perform all of its IT Service Area delivery activities (Table-1) under the guidance of the Government and in close cooperation/coordination with all other relevant IT service providers (as defined by the Government). This cohesive working relationship will ensure successful ongoing day-to-day service delivery for all Contractor IT Service Area and corresponding sub-service areas, 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 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, 0002, 0003, 0101, 0102, 0103, 0201, 0202, 0203, 0301, 0302, 0303, 0401, 0402 and 0402)

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 Applications Development and Sustainment services tasks for the Acquisition Management System (AMS) and all related Program Management Acquisition tools under the AIR 1.0 technical authority in a manner as to ensure a high quality of continuity of services and effective utilization of resources as defined within this SOW. Additionally, all systems shall be sustained in such a manner as to ensure system, application and data availability to customers.

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 Maintain familiarity with DON and/or NAVAIR policy and concepts including but not limited to IT consolidation, Functional Area Management (FAM), Navy Networks, Navy Enterprise Licensing agreements, Navy Information Dominance Approval process (NAV-IDAS), and Competency Aligned Organization (CAO). An understanding of these policies and concepts is required to ensure the stability and continuity of the work force when executing this contract.

3.1.5 Comply with Command initiatives such as, but not limited to, Navy ERP and AIRSpeed and perform in accordance with NAVAIR, DOD, and DON initiatives, standards, policies, and mandates such as Application Portfolio Management, Defense Business Transformation Guidance, Navy Enterprise Application Developer’s Guide (NEADG), Clinger Cohen Act, Federal Information Security Act (FISMA), Web Enablement and 508 Compliance. The contractor shall ensure that any tools that will be hosted by NMCI, Continuity of Services Contract (COSC), Next Generation Enterprise Network (NGEN) or run on these workstations are certified for NMCI, COSC, and NGEN and comply with NMCI, COSC and NGEN policy.

3.1.6 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.7 Quality Assurance

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

The contractor shall:

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

b) Ensure developed software is compliant with Section 508 of the Rehabilitation Act.

c) Develop software test plans and perform testing for application releases and provide release notes.
d) Perform application load testing as required.
e) Work with project leads and development personnel to identify load test scenarios.
f) Develop and schedule load testing scripts as required.
g) Analyze and report results of load testing as required. Test results shall be stored in a government designated repository.
h) Validate all software is in compliance with Security Technical Information Guide (STIG) requirements.

3.1.8 Priority Levels and Tier II Support Response Requirements In providing its respective IT services, the Contractor shall manage service delivery and perform its 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.9 Government Technical Environment. The contractor shall develop 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 Oracle WebCenter Suite, MS SharePoint, LiveLink (Open Text); including COTS Third Party Tools and Bolt-on Software

Configuration Management / Software Life Cycle

StarTeam, Caliber RM, Silk Test, LoadRunner, Team Foundation Server

Data Mining & Reporting 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

Web Based Training
Adobe Connect
Web Server Software
IIS, ColdFusion

3.1.10 The contractor shall:

a) Plan and support Systems Development Life Cycle (SDLC) methodologies which include IT project management and systems engineering utilizing 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 should provide source code management (where all software should be stored), reporting, requirements management, project management (for both agile and waterfall), 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)Coordinate / facilitate and attend customer meetings.
g)Prepare logical database models and store these models in a government defined repository.
h)Develop, test, and implement queries and reports using government defined reporting tools.
I)Provide interface(s) to internal/external systems and databases. All interfaces must be documented in the software design documentation.
j)Construct and sustain internet and intranet web sites using standard technologies as referenced in Table 3, Section 3.1.9.
k)Support search engines within web sites, web applications and commercial software in support of customer requirements.
l)Provide Tier 2 Help Desk support for applications developed/supported.
m)Ensure all software is compliant with Defense Information Systems Agency (DISA) Application Development Security Technical Information Guides (STIGs) and the STIGs are applied and/or mitigated.
n)Provide DON Application and Database Management System (DADMS) support for Operation and Maintenance (O&M) products and COTS applications, which may include providing support and maintaining information on Last Date Allowed extensions, Unit Identification Code (UIC) Stakeholder Requests and New Version Requests.
o)Provide support for emerging/new technologies and stay abreast of emerging trends within the application development discipline.
p)Perform all production application maintenance or deployments before core business hours or after core hours, unless written government approval has been received. Contractor shall perform and schedule maintenance in coordination with the Government.

3.1.11 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 and include description of 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 Allocate sufficient resources in order to efficiently and effectively meet the objectives of each task in a timely manner; be responsible for following through on tasks until completion; document or update any applicable processes, files, databases and/or training aids; and ensure availability to end users.

3.2.2 Maintain effective communications with government and other program office personnel to keep them informed on the status of supported AMS projects and tasks. Notify government personnel either in writing or verbally of any programmatic or logistics problems and/or resolutions of problems immediately upon discovery of such problem(s).

3.2.3 Schedule, lead, attend, participate in and/or support meetings providing input and making recommendations as may be required to resolve issues and/or achieve AMS objectives taking note and tracking action items resulting therefrom.

3.2.4 Support the Government in achieving the implementation and execution of AMS requirements identified by the TPOC or ATPOC.

3.2.5 In performing this Statement of Work, the contractor shall successfully integrate and coordinate all activities required to execute tasking that meets cost and schedule constraints and performance requirements. This includes but is not limited to software integration with other data sources required for the integration of the Acquisition Management System with data warehouses as required to support all AMS customer requirements .

3.2.6 Provide a working level Program Manager who shall be responsible for management and oversight of work performance and personnel for this contract.

The working level Program Manager shall:

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

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

e)Ensure consistent on-board and off-board of personnel
f)Ensure standard communication and processes with the contract and within each supported organization
g)Coordinate with project managers to ensure all projects are within cost, performance, and schedule
h)Coordinate effective utilization of resources across projects
i)Manage project risks and dependencies
j)Consult with government management on IT strategies and IT software life cycle standards
k)Manage strategic improvements and efficiencies
l)Attend meetings with the COR/ACOR or TPOC/ATPOC to discuss performance under the awarded contract to include resolution of any AMS performance issues or challenges

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, network outage, and General Service (GENSER) SECRET and below level spillages. 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 Acquisition Management Systems (AMS) applications, web applications, websites, and collaboration environments.

3.2.9 Project Management/Senior Project Support Specialist

The contractor shall perform project management functions. 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 AMS expertise, based upon their broad knowledge and understanding of emerging trends and techniques.

The contractor Project Manager shall:

a)Provide a comprehensive, overarching project management approach to ensure that 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 using such management tools as TFS, etc.
d)Prepare/develop Plan of Action & Milestone’s (POA&M).
e)Provide timely submission of ad hoc data calls.
f)Research and analyze Government Off-The-Shelf (GOTS), COTS, and proprietary application software packages oriented toward information technology and management. 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, performance, and adherence to standards. 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 over software developers, systems analysts, quality assurance testers, help desk support, trainers and other team personnel.
h)Ensure that all tasks and customer driven issues are documented and are responded to and resolved in the appropriate timeframe based on priority.

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. Work is planned to be performed when the Government is not closed for recognized holidays, inclement weather, or other unexpected reasons.

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. Additionally, 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 As an enterprise-wide service provider, the Government provides services to customers 24 hours per day/365 days per-year. The Contractor is tasked by AIR 1.7 with 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). Alternative support scheduling may be requested by the contractor and will be approved by the COR as required. 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, 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 (e.g. Ad Hoc telework may be authorized by the COR). During installation/activity closure-should there be a need to postpone or cancel some or all services, the Government reserves the right and/or the option to do so with written notice. 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).

3.3.7 The contractor shall identify Essential Personnel. The COR will approve contractor identified Essential Personnel. In the event that natural or man-made events (i.e. catastrophic weather, changes in Force Protection Condition, etc.) result in restricted access to the government installation, access may be limited to “Essential Personnel” only. In the event of such an occurrence, various local media mechanisms will be used to broadcast that only Essential Personnel are to report. Essential Personnel should contact the TPOC or ATPOC and report if required.

3.3.8 Government AMS Points of Contact.

The Contracting Officer Representative (COR), Alternate COR (ACOR), Government Technical Point of Contact (TPOC), and Alternate TPOC (ATPOC) for this effort are identified as follows:
Primary COR:ACOR
Stephen J. WeberValerie Carpenter
Phone: (301) 737-4104Phone: (301) 737-4043

Email:stephen.weber@navy.mil

TPOC: Joshua Colliflower Phone: (301) 737-3651 Email:joshua.colliflower@navy.mil

4.0 TRAINING (CLINs 0004, 0104, 0204, 0304 and 0404)

The contractor shall:

4.1 Provide training on the various AMS tools to members of the tool user communities. Training may take several forms during execution of this contract including, but not limited to, 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 course curriculum and training resources (e.g. user guides cue cards etc.).

4.2 Prepare/develop AMS software applications related documentation such as user manuals, training guides, brochures, software development plans, requirements documents, requirements traceability matrix, training resources and test/implementation plans. The documentation shall be stored in the appropriate government approved repository.

4.3 Plan, recommend, design, develop, coordinate, document and maintain graphics and technical writing support for AMS items such as customer pamphlets, documents, training resources and presentations.

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

5.0 Travel / Other Direct Costs (Travel Costs) (CLINs 0005, 0007, 0009, 0011, 0105, 0107, 0109, 0111, 0205, 0207, 0209, 0211, 0305, 0307, 0309, 0311, 0405, 0407, 0409, and 0411)

5.1 Other Direct Costs (ODCs) (Travel) are based on a per annum not-to-exceed 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.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 authorized and approved in advance by the COR.

6.0 Material / Other Direct Costs (Material Costs) (CLINs 0006, 0008, 0010, 0012, 0106, 0108, 0110, 0112, 0206, 0208, 0210, 0212, 0306, 0308, 0310, 0312, 0406, 0408, 0410, and 0412)

6.1 Other Direct Costs (ODCs) (Material) are based on a per annum not-to-exceed 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.

6.2 The contractor shall provide material or other items which are necessary or integral to the performance of tasking included in this SOW in accordance with NAVAIR clause 5252.242-9515 Restriction on the Direct Charging of Material.

6.3 All material purchased by the Contractor under this item becomes the property of the Federal Government.

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

7.0 GOVERNMENT FURNISHED PROPERTY AND INFORMATION

7.1 All GFP and 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 In accordance with Clause 5252.245-9500 Government Property for the Performance of this contract (NAVAIR) (May 2012), Government Property is identified for use under this contract.

7.3 Facilities, Supplies and Services. Contractors performing on-site support will be provided access to workspaces, telephone phones, 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.4 Information. The Government will provide the Contractor copies of, or access to, all required directives, publications, and documents, as available. The Government will also provide necessary, available, and reasonable access to personnel.

7.5 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. 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 0013, 0113, 0213, 0313 and 0314)

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

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:

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.

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.

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

· AMS Support

· AMS 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. Upon contract start date, all Key personnel shall have, at a minimum, an interim Secret clearance. On a case by case basis, Interim security clearances will be allowed, not to exceed 10 months unless authorized by the TPOC and in accordance with the interim clearance. 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 Identification Badges. Contractor 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 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” section (section 8.9); annual Government training may also be required.

11.0 CONTRACT DELIVERABLE REQUIREMENTS LIST

11.1 Contract Deliverables. The contractor shall provide the following contract deliverables. All deliverables must meet professional standards and the requirements set forth in each CDRL and this contract. The contractor shall be responsible for delivering all end items specified unless otherwise directed by the COR / TPOC. Contractor format is acceptable for this effort.

CDRL Listing – Table 4

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

12.0 MINIMUM LABOR QUALIFICATIONS

12.1 The contractor shall be responsible for employing personnel having the following levels of education, professional, and technical experience. These qualifications are only a baseline; contractors should strive for technical excellence in personnel by demonstrating experience and qualifications beyond these qualifications.

The specialized experience included as part of the required qualifications shall have been obtained in the field of endeavor indicated by the applicable labor categories listed below. The experience indicated in the following labor categories must have been performed during the past five years. In cases requiring experience of more than five years, at least five years of the total experience must be within the past five years. Key personnel are those who will be performing in Key Labor Categories listed below.

Personnel must have, or be able to obtain the appropriate security clearance as stated on the DD Form 254. Proof of U.S. citizenship is required to be permitted access to Government installation, aircraft, and ships.

Note: All required experience for all labor categories may have been obtained concurrently. All degrees shall be obtained from an accredited college or university.

12.2 DEFINITIONS

As used in the minimum personnel qualification descriptions for this contract, the terms indicated shall be defined or their meaning qualified as follows:

academic year - a full or complete year of study at a junior college, college, university, or other academic institution toward which at least 30 semester hours or 45 quarter hours of undergraduate study, or 18 semester hours or 27 quarter hours of postgraduate study, were completed.

accredited institution - a post-secondary educational institution (junior college, college, university, technical trade, or professional school) which was approved by an accrediting agency listed as nationally recognized by the U.S. Department of Education.

accredited program - an educational program or course of study offered by a post-secondary educational institution which was approved by an accrediting agency listed as nationally recognized by the U.S. Department of Education.

degree - an academic title conferred by an educational institution upon completion of a unified course of study; if not otherwise qualified, the term shall mean a degree at the bachelor’s, master’s, or doctoral levels only.

engineering or engineering discipline - when used in relation to educational or work experience requirements, “engineering” shall mean any of the following specific subjects, disciplines, or areas of work experience only: aerospace, civil, computer, electrical, electronics, industrial, mechanical or nuclear engineering.

experience and years of experience- When used in relation to requirements for past participation in professional work or employment activities, “experience” shall mean full-time (on the basis of a standard forty hour work week) participation, at least one-half of which time was spent performing qualifying functions as practitioner or employee. When used in relation to requirements for a particular term or period of participation, “years of experience” shall mean full, productive years of participation. Productive years are work years of fifty-two weeks reduced by reasonable amounts of time for holiday, annual, and sick leave. If participation was part-time, or if less than one-half of the standard work week was spent performing qualifying functions, the actual time spent performing qualifying functions may be cumulated to arrive at full years (or years and months) of experience. For example, only the actual number of full days (or full-day equivalents) of duty or drills completed during a year of military reserve participation, or in other qualifying part-time employment or practice may be cumulated toward years of experience. Qualifying part-time experience performed in addition to other full-time qualifying employment during the same period of time may be cumulated on a full-time equivalent basis and added to the full-time experience to satisfy a total experience requirement.

postgraduate degree - a master’s, Ph.D., or other professional degree for which completion of an undergraduate curriculum for receipt of a bachelor’s degree was a prerequisite.

technical rating - completion of a U.S. Navy electronic technology related B or C school for Cryptologic Technician Technical (CTT), Electronic Technician (ET), Electronic Warfare Technician (EW), Fire Controlman (FC), or Information Systems Technician (IT) or the equivalent from another branch of service.

12.3 The contractor shall provide qualified personnel who are capable of assuming their duties at contract inception. Training for contractor personnel will be at the contractor’s expense. All training must be coordinated with the COR/ACOR in conjunction with TPOC/ATPOC to ensure compliance with contract requirements and schedules.

12.3.1 In addition to the knowledge, skills and abilities outlined below, all personnel must be knowledgeable of and proficient using Microsoft (MS) Office products to include: PowerPoint, Word, Excel, and Outlook. Experience with MS Project/project management methodologies and tools, Team Foundation Server (TFS) and experience working on a software development team is preferred for all labor categories. Programmers/Developers that have experience with Portal/ Collaboration (e.g. Share Point), Visual Studio Suite of Tools (e.g. .Net & the other Tools Listed in Table 3, Section 3.1.9), Database Management systems, MS Windows server architecture, are preferred.

12.3.2 All personnel shall present themselves professionally and have effective communication skills both written and oral. The ability to interface with others and discuss (and/or transpose) technical requirements in non-technical terms/user friendly language to enable understanding by all team members is required.

Labor Category & Education/Experience/Training – Table 5

Labor Category
Job Description
Education requirement
Experience/ training

Program Manager, Business Operations and Systems

(KEY)

Key = 1 FTE

Acts as the overall lead, manager and administrator for the contracted effort in support of aircraft subsystems, ACAT III-IV programs, AAPs, or information/acquisition systems. Serves as the primary interface and point of contact with Government program authorities and representatives on technical and program/project issues. Oversees contractor personnel program/project operations by developing procedures, planning and directing execution of the technical, programming, maintenance and administrative support effort and monitoring and reporting progress. Manages acquisition and employment of program/project resources and controls financial and administrative aspects of the program/project with respect to contract requirements.
BS or BA degree in engineering, computer science, business, or information systems. ALLOWABLE SUBSTITUTION: Eight (8) years of combined undergraduate education and experience performing Project systems management.
At least five (5) years of experience in engineering management and/or information/acquisition systems to include two (2) years of supervision of a project in: 1) systems engineering and/or 2) information/acquisition systems. Preferred two years software development experience.

Labor Category & Education/Experience/Training – Table 5 (Cont’d)

Labor Category
Job Description
Education requirement
Experience/ training

Software Engineer, Senior

(KEY)

Key = 1 FTE

Responsible for the detailed design, implementation, and testing of subsystems and system components. A Senior SE is able to build a wide variety of software subsystems and components efficiently and effectively, given only a requirements specification and constraints. A Senior SE is able to develop and sustain these subsystems and software components in complex, multi-vendor, multi-platform environments.
BS or BA degree in an Engineering or Computer Science Field. ALLOWABLE SUBSTITUTION: Fifteen (15) years of combined undergraduate education and experience performing the foregoing functions can be substituted for a BS or BA degree.
At least ten (10) years of experience in an Engineering/Computer Science Field.

Project Analyst

(KEY)

Key = 1 FTE

Applies project principles to investigate, analyze, plan, design, develop, implement, test, or evaluate military weapon systems to include acquisition support systems. Reviews and prepares project and technical analyses, reports, change proposals, and other technical documentation. Applies project experience to perform functions such as system integration, configuration management, quality assurance testing, or acquisition and resource management. Analyzes designs, develops, implements, tests, or evaluates automated data processing software related to engineering or functional requirements of military weapon systems, associated support systems, or management information systems. As the project manager for the contracted effort, ensure project procedures and controls are followed, manage manning and staffing project efforts, and lead problem resolution efforts. Interfaces with system or program contractors, vendors, and Government representatives regarding the technical aspects of the programs/projects.
BS or BA degree in engineering, computer science, business, or information systems. ALLOWABLE SUBSTITUTION: Six (6) years of combined education and experience performing the foregoing functions can be substituted for a BS or BA degree.
At least three (3) years of experience in software development.

Labor Category & Education/Experience/Training – Table 5 (Cont’d)

Labor Category
Job Description
Education requirement
Experience/ training

Systems Analyst

Non-key = 1 FTE

This is the start of the file's text. The full file is on GovTribe.

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