Draft_SOW_AWS_20160720_V2.docx

DRAFT STATEMENT OF WORK (SOW)

Support Services For Army Watercraft Systems - C4ISR Sustainment Branch

(AWS-CSB)

203 JulNov 20164

Contents Contents

ii

PROGRAM OVERVIEW

SCOPE

The contractor shall provide program management, technical and technical documentation support services for Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) assets and suites of equipment installed on Army Watercraft System (AWS) vessels and platforms. This includes current and future C4ISR equipment, and all associated assets, installed on AWS vessels/platforms positioned worldwide.

BACKGROUND

TACOM has consolidated support for AWS C4ISR assets under the Communication Electronics Command (CECOM) – Integrated Logistics Support Center (ILSC). This support structure has been in place since 2008 and features centralized management of field support using uniform processes and continued analyses to improve the readiness of the fleet. A key element of the centralized-management approach is the use of the Army’s Single Interface to the Field (SIF) database. An overview of the SIF can be found in Attachment 1. Ongoing efforts and support include configuration management of C4ISR assets across the fleet, execution of a consistent, centralized maintenance support process to service these assets, expertise for Tactical Satellite Communications (TACSAT) and Communications Security (COMSEC), software support and Information Assurance (IA), testing and logistic/technical documentation support for Army Watercraft C4ISR Systems.

Army plans for Watercraft include coordination between TACOM, CECOM-ILSC, Space and Naval Warfare Systems Command (SPAWAR), Naval Surface Warfare Center Carderock Division NSW-CCD, NSW-Philadelphia, Watercraft Inspection Branch (WIB), Army Sustainment Command (ASC) and other support organizations to modernize and maintain the current fleet.

SUPPORTED VESSELS/PLATFORMS

Vessels to be supported under this effort include but are not limited to: Landing Craft, Utility 2000 (LCU 2000); Logistics Support Vessels (LSV); 128-Foot Large Tug (LT 128); Landing Craft, Mechanized 8 Modification 1 (LCM8 Mod1); Landing Craft, Mechanized 8 Modification 2 (LCM8 Mod2); Small Tug 900 (ST 900); Barge Derrick (BD); Causeway Ferry (CF); Floating Causeway (FLT); Modular Warping Tug (MWT); Fuel Barge (BG); and Roll-On/Roll-Off (RO/RO) discharge facilities (RRDF). Additionally, support may be required for the Harbormaster Command and Control Center (HCCC) and the Maneuver Support Vessel (Light) (MSV(L)).

DENSITY AND LOCATIONS:

The current density and home port locations of presently supported vessels are shown in Table 1.

Table 1. Army Watercraft Density and Locations. Add MWT

LCM8 Mod1

SLWT

Trident Pier

BLVR: Fort Belvoir, VA

Support will be required for the vessels when they are in port and underway, as necessary. Other repair locations include, but are not limited to, Middle Eastern locations such as Bahrain, Dubai, Qatar, Oman, and UAE; Mediterranean locations such as Sicily, Crete, Spain and Azores Islands; Caribbean locations such as Puerto Rico and Haiti; and Alaska and the Alaskan islands. Home ports and densities of the supported vessels are subject to change.

REQUIREMENTS

The Government intends to award an Indefinite Delivery Indefinite Quantity (IDIQ) contract for the services and/or supplies described in this PWS. The List of Contract Line Item Numbers (CLINs), appended to the end of this PWS, provides an abstract of the ordering schema. The Government may choose to initiate and fund any, all, or none of these tasks (with the exception of the guaranteed minimum specified in the Request for Proposal), at any time within the overall period of performance of the basic contract. The task(s) will be further defined, if necessary, if/when the requirement is initiated by the Government, at which time a Request for Task Execution Plan (RTEP) will be issued by the Procuring Contracting Officer (PCO). The Contractor shall then provide a Task Execution Plan (TEP), to include its technical approach, cost/price, and schedule, within 5 working days, unless additional time is provided in the RTEP. Performance or delivery is authorized ONLY by the issuance of subsequent Task/Delivery Orders signed by the PCO. Attachment 2 shows the number of incidents over the past 4 years.

In many instances throughout this PWS, the Contractor is required to recommend and/or provide information to the Government for prior approval. In these instances, the Contractor may be required to provide this information in both its initial proposal, and from time to time, as required or requested by the Government, throughout the life of the contract. If granted approval, such approval shall only come from the PCO, Contracting Officer’s Representative (COR), or designated representative (any such designation shall be provided to the Contractor in writing).

PROGRAM MANAGEMENT

Program Manager The contractor shall identify a Program Manager (PM) who will have primary responsibility for ensuring implementation of the PWS and coordinating the activities of all sub-contractors and vendors (including original equipment manufacturers [OEMs]). The PM shall be the point-of-contact to the Government COR and COR representatives, as identified in Paragraph 4, who maintains timely cognizance of all contractor activities performed under the program. Responsibilities of the PM shall include meeting with, and reporting progress to, the Government as described in Paragraphs 2.1.7, Reports, and 2.1.8, Meetings and Reviews. The contractor shall ensure cross-communication within and between team members and tasks and will assign appropriate personnel to each task. The PM shall adjust staffing, as required, to address increasing and decreasing workloads and to ensure continuous/non-interrupted support services. The PM shall request Government approval for all proposed changes in personnel or team structure and ensure that all tasks are integrated across team member’s proficiency levels. The PM shall resolve conflicts with integrated team resources to ensure compliance with schedules. The PM shall inform the Government immediately regarding any potential execution impacts to cost, schedule, and/or performance. The PM shall also ensure that all formal actions with the Government shall take place through the PCO or COR, to include submission of contract deliverables and acknowledgement of Government comments and approvals for deliverables.

Integrated Team Performance of the work efforts described in this PWS will require organizations and personnel with a diverse array of experience and qualifications and a thorough knowledge of all equipment types requiring support. The contractor shall organize its team to most efficiently meet program requirements while ensuring that organizational boundaries are seamless and transparent to the Government. A primary responsibility of the PM will be to ensure that the team operates in an integrated and coordinated fashion.

The contractor shall establish the complete team structure that will support the contract (subcontractors and vendors) in a logical manner, for each major task area. The contractor will maintain an organization chart that clearly identifies areas of responsibility and key personnel and update and provide to the Government as necessary. Resumes of all personnel (PM, Contractor Field Service Representatives [CFSRs], Subject Matter Experts [SMEs]) who will support this contract will be submitted for Government review/approval. SMEs are defined as individuals who possess the highest level of expertise in performing a specialized job, task, or skill within the contractor’s team. SMEs shall be made available to support the Government and other team members as required. All team members, including sub-contractors, vendors, etc., shall meet all of the requirements found in this PWS that are applicable to the function they are assigned by the PM to provide.

Any changes to proposed teaming arrangements and contract staffing are subject to the prior approval of the Government. The Government reserves the right to prohibit any team member or other entity from participation in support of this program for any reason, at any time, and require reassignment of personnel as needed. The contractor shall provide all necessary support while proposed staff changes are under review or in the event of Government-directed prohibitions.

Quality Assurance Management The contractor shall establish and implement a quality assurance (QA) process to ensure measurable quality on all products and services provided on this program.

As part of the QA process, the contractor shall ensure that SMEs completely review deliverable documents for technical accuracy and completeness. This review shall not only cover the documentation developed under the contract, but also may cover the existing documentation used as source data. Changes to existing documentation/source data recommended by the SMEs will be vetted and approved by the Government prior to incorporation. The contractor shall submit a Certificate of Technical Accuracy with each technical deliverable developed under this contract. Technical deliverables include, but are not limited to, all Technical Documentation, Failure Analysis, Item Unique Identification (IUID), Engineering Change Proposal (ECP) data, Deficiency Report (DR) data, Database Design Description and the Enterprise Database Management System (EDBMS). The certificate will state that the document/system being submitted is technically accurate and shall be signed by the appropriate SMEs and the contractor Program Manager. The SMEs signing the Certificate of Technical Accuracy shall have the necessary expertise to assess the technical accuracy of the entire content of the document or other product.

Risk Management The contractor shall document and implement a method for identifying and managing risks. Risk management shall be an ongoing effort performed as a part of this program. Risk management will include identifying and describing the risk, providing a method for categorizing the severity of the risk and the probability of occurrence. Proposed strategies shall be developed to address each significant risk.

Data Entry Support The contractor shall collect and enter data into multiple data management systems and will provide reports on these data systems, quarterly and at any time as required by the Government.

Single Interface to the Field The contractor shall enter all data into the SIF Incident Reporting Module (IRM This requirement includes, but is not limited to, parts data to include part numbers and serial numbers; warranty data; labor data to include labor costs and hours for all members of the contractor's team involved in repair; travel data to include costs and hours and any Other Direct Costs (ODCs) associated with repairs. The contractor shall ensure the accuracy of all data entered IAW the SIF Guidelines. The Government does not approve labor hours associated with tracking duplicate information in a separate database (with the exception of STAMIS).

The data entered into the SIF must also comply with the timelines annotated in the SIF Guidelines. The contractor shall verify and update all data entered by the Support Operations Center (SOC)/soldier once contact is made with the soldier, update the Work Info tab daily while resolving the incident remotely or on-site and weekly while the ticket is in "pending" status, update the Status of the ticket as it changes, provide any "time tracking" data as it occurs and ensure that all required data is complete and accurate prior to resolving the ticket. The data must be clear and concise and be free of personal views and hearsay. The data may be entered in the web-based online version of the IRM or the offline client version. Data entered into the offline client shall be uploaded onto the server each day.

If the Government decides to use a different database system for collection, tracking and analysis of field support data, the requirements in this section shall also apply to the new database.

Standard Army Management Information System (STAMIS) The contractor shall enter cost data for materiel procurement, personnel, travel and pertinent data from the SIF/IRM into STAMIS. Pertinent data includes, but is not limited to, vessel hull number, unit data, repaired asset and replacement assets. The contractor shall develop nomenclature for assets without National Stock Numbers and document business rules for the development of this nomenclature.

The contractor shall develop and deliver STAMIS reports quarterly IAW this paragraph.

The contractor will include the following data broken out by Major Army Command (MACOM): total parts cost, total labor cost, total travel cost, and overhead.

Materiel Management In support of mission readiness, the contractor shall be required to acquire, store, package, ship and manage parts and other materiel required for the repair and maintenance of AWS C4ISR systems.

Acquisition The contractor shall be required to procure parts and other materiel for the life of the contract. In circumstances where the Government does not identify a single source, the contractor will be required to identify sources. When there are multiple sources available a minimum of three (if possible) quotes shall be obtained and the parts/materiel procured from the source which provides the best value to the Government shall be utilized. At the request of the Government, the contractor shall provide the quotes to the COR for review and/or approval.

The contractor will review Government-provided planning information regarding future parts installation, Reorder Point Analysis, fleet requirements, failure data and other essential information, to identify and recommend additional parts to be procured and stocked. The contractor shall purchase critical parts and tools as approved by the Government in order to maintain the proper stockage level. Title to such property shall be IAW FAR 52.245-1 “Government Property”.

A separate Cost Reimbursable CLIN will be established for parts/tools only.

Storage Facility The Contractor shall be required to store GFE, acquired parts, and other materiel required for sustainment of AWS C4ISR systems and components. The Contractor shall provide a minimum of 3000 and a maximum of 12K cubic feet of storage space. The facility shall be available immediately upon contract award, with access for Government personnel during normal business hours without notice. The stored assets must be available and ready for immediate distribution at all times.

Location of the facility (or facilities if multiple sites are planned) shall be recommended by the Contractor, but must be approved by the COR prior to any movement of parts and supplies.

Materiel Handling Materiel handling shall include receiving and storing parts and other materiel, receiving faulty parts from the field and shipping to the OEM and/or a Government appointed facility, receiving repaired parts and returning to stock, and packing and shipping parts to the Operations and Maintenance contractor.

The contractor shall be required to receive materiel from other Government-identified sources at any time following contract award. These assets shall be unpacked, inventoried, tested if required, and ready for use within 10 working days of receipt. The contractor shall transfer (to include inventorying, packing and shipping) the assets from their facilities to other locations as directed by the Government.

The contractor shall pack, ship and track parts to support field maintenance or other Government use. The contractor shall establish and use a Government-approved distribution process and will use a shipping method that will support Government timelines for resolving field maintenance problems. The contractor will require Government approval for all parts distribution.

The contractor shall maintain records of all shipped assets (the date the asset is shipped, tracking information and the date the asset is delivered to its destination). This information shall be made available to the Government upon request.

The contractor shall maintain warranty data associated with all assets in storage and/or procured during the length of the contract whether procured by the prime contractor, support contractors and/or vendors/OEMs.

See Paragraph 6 of this PWS for further guidance regarding the handling of Government Furnished Property (GFP).

Reporting The contractor shall maintain a complete inventory of all parts (on-hand, distributed, acquired) and report monthly on all assets acquired, shipped, repaired, returned, and stored including dates and costs for each.

Item Unique Identification (IUID) The contractor may be required to add IUID conforming labeling to all qualifying items and enter IUID data into the IUID Registry and SIF database. When requested to do so by the Government, the contractor shall assess the inventory to determine those parts that require labeling. The contractor shall then supply a TEP that will include the cost and schedule for developing the required drawings and for tagging the assets.

Reports The contractor shall provide reports in the format and frequency as identified below. The contractor may be required to adjust report format and content as directed by the Government.

Army Contractor Manpower Reporting System The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor will report all contractor manpower (including subcontractor manpower) required for performance of this contract.

Quarterly Reports The contractor shall deliver Quarterly reports five work days prior to each Quarterly Review to allow the Government sufficient time to review. This will include summary charts per task including the task description, accomplishments, schedule, cost, graphics/charts, as well as any other items included in the agenda for the Quarterly In-Process Review Meeting.

Monthly Reports The contractor shall deliver Monthly reports on the 10th of each month for the previous calendar month, unless authorized to adjust due to holiday, etc. This will include status of deliverables, updated comprehensive Master Schedule (baseline and variations in MS Project electronic format), narrative summary of work efforts (performance), funding narrative and separate spreadsheet with details (all cost data by task). The Master Schedule shall include all contractually-required data items and action items. Changes to the initial baseline shall be noted. The schedule shall include personnel assigned to each task and the level of effort associated with each task. Percent complete will also be maintained as well as task notes outlining any changes to the schedule.

Weekly Reports The contractor shall deliver Weekly Reports one day prior to Weekly Meetings and will include the following: agenda, deliveries due per task, three-week projection, CFSR activities, action items, issues, and any other items requiring Government attention.

Meetings and Reviews Meetings and reviews shall require the presence of key personnel supporting the program. These meetings and reviews will be held at locations specified by the Government.

Administrative Support for Meetings and Reviews The contractor shall provide administrative support to document key discussion points and action items from each meeting. Minutes and action items shall be delivered within three working day following the completion of each meeting. The contractor will submit minutes including: dates, attendees, agenda, topically-organized minutes, and a spreadsheet table, capable of being sorted, of action items including date of action, suspense date of action, action designee, topic of action, and description of action.

The contractor shall provide weekly emails capturing any teleconferences with the customer, and cc the Government on ALL correspondence between the prime contractor, its sub-contractors, and any other entities deemed necessary by the Government.

The contractor shall consider action items as required deliverables. Action items are not associated with specific requirements already identified in the PWS, such as maintenance response times or document deliverables, but are expected to be programmatic or surge-related tasks that will be within the scope of the PWS. Suspense dates identified for action items during meetings and reviews are contractually binding. Modifications to the suspense dates will only be made with Government approval.

Program (SOWM) The contractor shall attend a Start-of-Work meeting (SOWM) at a time and location specified by the Government. Attendees shall include all prime contractor personnel supporting the program and key sub-contractor and vendor personnel. The Program SOWM shall be held within one to three weeks of contract award with the location and date to be identified by the Government. The meeting will be two to three days in duration, and will include an introduction of the contractor’s integrated team and a discussion of the initial funded tasks and projected schedule. The Government will provide an agenda no less than two working days prior to the Program SOWM.

In-Process Reviews The contractor shall attend and provide information specified by the Government to support these meetings accordingly. The contractor shall also have personnel directly supporting the program in attendance at the reviews as determined necessary by the Government.

Program IPRs IPRs will be held quarterly, beginning approximately three months after the Program SOWM at a location to be determined by the Government. Program IPRs can be expected to last two to three days, and will be modified as required and on short notice. The Government will provide a generic agenda for these IPRs. Content/Discussion topics that shall be presented by the PM to the Government representatives in attendance will be formatted in PowerPoint and Excel. Discussion details of the content/support of each task, schedule, funding, risks and action items for the complete team will be included in the IPR. The Government will provide agenda changes five working days prior to the IPRs.

Task IPRs Task IPRs will be held for each active task, as required by the Government. The Government will determine the location, content and duration of Task IPRs, as needed.

Weekly Meetings (WMs) The contractor shall support weekly meetings (WMs) on dates and with personnel determined by the Government. These normally will be held telephonically but may take place at a location designated by the Government.

Program WMs A Program WM will be held each Wednesday at 10am, unless previous approval or guidance has been provided by the Government to readjust. Program meetings will typically be done via teleconference and will last 1-2 hours. The contractor PM will review the near-term schedule and far-term schedule impacts, activities of the CFSRs, the progress of each task deliverable (three week projection), and review open action items.

Task WMs There will be task WMs as required or identified in each task section of this PWS. The location and duration to include content discussion topics will be conveyed in each specific task section.

Management Meetings Up to eight management meetings will be held during the contract period at a location to be determined by the Government. They may be held via teleconference, net meeting, and/or face-to-face meeting. Normally, management meetings will be one day in duration and are coupled with Quarterly IPR’s. Topics to be discussed include schedule, metrics, funding, and program progress.

Other Meeting Requirements Select contractor personnel may be required to attend monthly AWS C4ISR Integrated Product Team (IPT) meetings with the AWS community. No administrative support will be required. The venue will typically be a teleconference of approximately two hours in length. Content and discussion topics will be determined.

On occasion, contractor attendance will be required at other meetings that will be identified by the Government.

AWS C4ISR TECHNICAL SUPPORT

AWS C4ISR technical support shall include, but not be limited to, corrective, preventive and On-Condition Cyclic Maintenance (OCCM) support; specialized support for military exercises and other operations; failure analysis; C4ISR equipment installation, reconfiguration or removal; configuration management; Deficiency Report and Engineering Change Proposal development and evaluation and training. The contractor shall develop a technical support team structure to support the execution of all tasks described in this section. The requirements for each of these tasks are identified in the following paragraphs.

Contractor Field Service Representatives The contractor shall retain CFSR personnel with overall system-level expertise with the C4ISR assets installed on each vessel/platform. Reference attachment 3 for the CFSR to asset matrix requirement to ensure all assets are covered, and subject to change. The supported vessels/platforms are identified in Paragraph 1.4. The contractor shall subcontract as necessary to obtain specific expertise and certifications that are not available except from OEMs or their factory-authorized agents for the C4ISR assets on this program. These assets are subject to change throughout the contract. The contractor shall be responsible for ensuring the availability of appropriate technical expertise throughout the life of the contract.

A CFSR is defined as any contractor that provides support to the Government to address reported incidents by phone, email, or on-site in the field. CFSRs also may perform corrective and preventive maintenance; On Condition Cyclical Maintenance (OCCM) support; specialized support; C4ISR equipment installation, reconfiguration or removal of equipment; DR/ECP support; configuration management and training.

CFSRs shall provide expedient, efficient and effective support to the Army Watercraft community. The contractor shall ensure that the CFSR designated to respond to each Incident Report (IR) possesses the appropriate qualifications for repairing the failed equipment to minimize/eliminate the need to send multiple CFSRs to perform repairs.

CFSRs shall be prepared to provide support for incidents occurring on vessels in port, in transit, and worldwide. The contractor shall ensure that any CFSR traveling to support vessels overseas is pre-certified to meet commercial and military deployment requirements, to include the Army’s Combat Readiness Center (CRC) training certification, passport availability, country clearances, and coordination with various military commands pre- and post-deployment.

When on-site, CFSRs shall maintain the ability to access support from other SMEs using telephone, email or other communications means to assist in resolving incidents. All personnel assigned to the effort shall meet the contract security requirements as defined in paragraph 7 of this PWS.

The following three paragraphs describe the role and requirements for the CFSR team, including: the CFSR Coordinator, Core CFSRs and Non-Core CFSRs.

Lead CSFR Coordinator/CONUS and OCONUS The CFSR Coordinator shall be the single focal point for all CFSR activities. In conjunction with the PM, the CFSR Coordinator ensures workload balance is maintained among CFSRs and assesses multiple tasks and priorities to ensure optimum utilization of CFSR resources to accomplish assigned tasks. The CFSR Coordinator shall ensure cross-communication & collaboration among the following personnel: PM, other program team members, CFSRs, and other SMEs as required.

The CFSR Coordinator shall ensure that there is a Core CFSR assigned to each incident to design/implement a resolution and track progress from beginning to end (assignment to resolution). The CFSR Coordinator may be required to coordinate between the Core CFSRs and other program team members to task Non-Core CFSRs and to obtain necessary parts/materiel to resolve incidents.

The CFSR Coordinator shall maintain awareness of all IRs to effectively communicate current status, as directed, in a timely manner. The CFSR Coordinator shall have the capability to effectively communicate with Department of Defense (DoD) civilian personnel, Army Watercraft crew members, IR POCs, and subcontractor and OEM representatives, and must be fluid in their ability to provide clear and concise information in a legible/audible way. The CFSR Coordinator shall have authority to report directly to the COR and COR representatives to communicate IR information accurately and expeditiously as required.

Core CFSRs A Core CFSR is defined as a full-time CFSR dedicated to the AWS C4ISR Support contract. Each Core CFSR shall be trained in the operation and maintenance of several of the C4ISR assets installed on AWS vessels and platforms to maximize the capability to resolve multiple incidents at one site in one visit.

The contractor shall retain a minimum of five Core CFSRs. Each Core CFSR is responsible to execute the tasks listed in Paragraph 2.2.1 and use the process outlined in Paragraph 2.2.2.1, Field Maintenance Process Requirements.

Core CFSRs shall have responsibility for an incident from assignment to resolution. If a Non-Core CFSR is required, the Core CFSR assigned the incident will coordinate with the POC designated in the IR and the Non-Core CFSR through resolution.

Non-Core CFSR Support A Non-Core CFSR is any service provider other than a core CFSR that may be assigned to perform the tasks of a CFSR.

A Non-Core CFSR is used when a core CFSR does not possess the skills, qualifications and/or certifications required to repair specific C4ISR assets. A Non-Core CFSR also may be used to minimize travel time & expenses and to support a surge/increase in the volume of incidents and/or CFSR tasks.

CFSR Qualifications The contractor shall ensure that qualified CFSRs, approved by the Government, are employed and available upon contract award to support internal coordination, and to provide field support immediately following the Program SOWM meeting. The CFSR team shall possess the experience, training, and certifications required for supporting all C4ISR assets, both current and future, for the duration of the contract.

All CFSR team personnel shall possess an Associate’s degree in electronics technology or related field, or a minimum of three years’ experience with C4ISR systems (maritime preferred). In addition, all CFSR team personnel supporting radio/radar operations and maintenance must possess the following FCC licenses: Global Maritime Distress Safety System (GMDSS) Operator Maintainer License and Radiotelephone General Operator License. All CFSRs are responsible for ensuring that Occupational Safety and Health Administration (OSHA) standards (Code of Federal Regulations [CFR], Title 29, Maritime) for safety are met. CFSRs shall possess the written and oral communication skills needed to meet the reporting and coordination requirements of the PWS. The contractor shall ensure that the CFSR team includes personnel currently trained licensed and/or certified according to OEM requirements for repairing, installing, removing, configuring and supporting all assets, including, but not limited to Raytheon and Thrane & Thrane equipment and others as stipulated..

CFSRs must be trained and certified on the related C4ISR systems at contract award and remain current on these certifications. The Government is not responsible for the cost of training or labor hours associated with required training/certification for the AWS C4ISR systems/equipment.

Customer Service Representation The contractor shall be responsible to ensure that all CFSR/technical team personnel, including those of subcontractors and vendors, interact with Army Watercraft community in a professional manner and dress in a manner appropriate to the working environment, and to fully understand the delineation between contractor and Government, and customer/contractor.

Corrective Maintenance Support The contractor shall provide field maintenance support for C4ISR assets installed in Army Watercraft vessels and platforms, both in port and underway at locations worldwide.

Field Maintenance Process Requirements The Army field personnel will use the Maintenance Action Message (MAM) TACOM #MA10-002, issued 14 October 2009, as guidance to initiate an incident report (IR). All CFSRs shall follow the Field Maintenance Process and the Field Maintenance Prioritization Matrix, unless otherwise directed by the Government, to affect field repair. As part of the Field Maintenance Repair process, all CFSRs shall use the SIF database/Incident Reporting Module (IRM) to record data regarding the progress and actions used to resolve an incident.

All CFSRs shall meet the field repair time requirements. A CFSR must contact the incident POC within twelve (12) hours of receipt of the IR, assess the incident and attempt to resolve the issue remotely. In the event the issue cannot be resolved remotely, the CFSR shall provide on-site support to all Continental United States (CONUS) and Hawaii service calls within 48 hours and all outside the Continental United States ([OCONUS] excluding Hawaii) service calls within 72 hours.

The guideline used to initiate repairs, subject to change by the Government, is as follows: for travel or parts with a cost of less than $1,000.00 the Contractor will only notify the Government, and for travel and parts $1,000.00 or more, COR or designated representative review is required to ensure expenditure of funds are consistent with contract requirements. The Contractor shall notify the Government by email and log an update into the IRM for the COR or designated representative to review the best recommended methodology to support the repair, before contractor execution.

For each incident requiring on-site repair, the Contractor shall provide repair personnel with the required experience, certification, training and/or licensing for work required to resolve the system/equipment problem. If the problem is not resolved in the first visit, the CFSR shall contact the incident POC at least weekly and as new developments occur to provide an update on any pending parts, delays in completing repair, and provide an estimated completion date until the ticket is resolved. Before departing a site at the completion of all planned activities, the CFSR shall provide a signed copy of a standardized field service report to a vessel representative when the work is completed or if a return visit is required.

The Contractor shall update the SIF/IRM with any changes in status and upload them within one working day of their occurrence. The Contractor shall ensure that STAMIS and the SIF/IRM are updated with all required data. All open tickets shall be tracked during a weekly meeting with the Government until closure.

Tools and Parts for Field Maintenance Each CFSR shall travel with and/or ship the tools, test equipment, and parts needed to accomplish repairs, based on the symptoms of the incident. The Government is not responsible for the purchase of tools required to support the program.

Preventive Maintenance Support The contractor may be required to perform periodic and or usage based maintenance tasks. This support will be further defined if/when this task is initiated by the Government; at which time an RTEP will be issued by the PCO. These maintenance services are defined in the vessel's Technical Manuals The contractor shall support the Government by collecting and documenting equipment usage records to support future planning and repairs.

On-Condition Cyclic Maintenance Support The contractor may be required to provide OCCM support. This support will be further defined if/when this task is initiated by the Government; at which time an RTEP will be issued by the PCO.

OCCM support is technical assistance provided generally before and/or after a vessel receives OCCM at a shipyard. Each vessel is sent to a shipyard for OCCM approximately every three years. OCCM ensures that the vessel is in sound working condition and any upgrades are incorporated. Some of the OCCM services, such as: power washing, sanding, arc welding, and spray painting, can adversely affect the C4ISR equipment. The OCCM support may be requested to document the impact of the OCCM on the C4ISR equipment.

While conducting OCCM support, the contractor shall witness, assist and conduct functional tests on the C4ISR assets as tasked and develop an OCCM Report. The OCCM Report shall include: a completed functional test checklist, a summary assessment of C4ISR assets and a description of preservation activities performed. The OCCM checklist contains a list of functional checkout procedures to be performed on each piece of equipment. The Summary Assessment will include a list of non-functioning assets, software versions and (non) compliance with baseline and any critical defects found with the C4ISR assets (including cables, etc.). The preservation activities performed are the CFSR’s list of steps that were taken to preserve internal/external assets during OCCM.

The contractor may be required to cover, preserve, prepare, or otherwise protect C4ISR cables and equipment from damage incidental to power washing, sand blasting, exposure to the sun/environment, and other activities commonly performed during OCCM shipyard work.

The contractor may be required to repair defective C4ISR assets on vessels as they are exiting OCCM facilities. All personnel proposed to perform this service are subject to the same technical qualification requirements defined above for CFSRs.

Specialized Support The contractor may be required to support exercises and/or missions for CONUS and OCONUS locations. These events include peacetime efforts, humanitarian relief and wartime engagements.

Exercises are used to test the deployment of vessels/units into an austere environment without benefit of fixed seaports, such as using Joint Logistics Over-the-Shore (JLOTS) capabilities to provide a trained and ready JLOTS/ Reception, Staging and Onward movement (RSO) force to the Warfighter to facilitate transformational concepts. C4ISR support is required during initial staging of vessels, soldiers arriving, event execution and post-event activities.

The contractor shall provide Specialized Support as directed by the COR within 5 days to support a mission, and within 60 days in advance of an exercise, to ensure commercial and military deployment requirements are met, to include CRC, passport availability, country clearances, and coordination with Military Operational Commands pre- and post-deployment.

The contractor shall ensure that materiel, training and personnel are available. The materiel should be focused on parts with the most common and highest failure rate. CFSRs shall be able to provide assistance to soldiers as needed for training and technical support. Required support personnel include CFSRs (for rotational ability) who also have access to supplemental SME support and in-theater OEM support, as required.

While providing Specialized Support, the contractor may be required to deploy to a theater or region and fall under the control of one or more Military Operational Commands. When operating under such an arrangement, the CFSR will fulfill contractual obligations as well as associated administrative actions as required, to include conforming to that organization's reporting and accountability processes, as well as in-processing and out-processing at designated times and locations.

Failure Analysis The contractor may be required to provide failure analysis support. This support will be further defined if/when this task is initiated by the Government; at which time an RTEP will be issued by the PCO.

Required failure analysis support tasks may include but are not limited to: collecting, organizing and analyzing failure data concerning C4ISR equipment; identifying other sources of maintenance information concerning C4ISR equipment used on Army Watercraft vessels/platforms; identifying frequent failure modes; investigating and determining the underlying causes of frequent failure modes; recommending design changes or equipment replacements to reduce failures and providing recommended changes to Preventive Maintenance, Checks and Services (PMCS) that enhance system reliability.

Specific tasks, schedule and reporting requirements will be specified in the RTEP.

The contractor shall prepare and submit failure rate analysis reports on IR’s as requested and per the RTEP.

C4ISR Equipment Installation, Reconfiguration, or Removal The contractor may be required to install C4ISR equipment on Army watercraft platforms at locations worldwide. In association with this, or separately, the contractor also may be required to remove or reconfigure previously installed C4ISR equipment on Army watercraft platforms at locations worldwide. Specific tasks, schedule and reporting requirements will be specified in the RTEP.

Configuration Management The contractor shall identify and track the baseline configuration of the C4ISR systems for each platform as changes occur or new components are added. The baseline configurations of the C4ISR systems are defined by their requirements, source code, executable programs, data files, hardware and associated documentation. Due to the various distribution locations and densities, configuration management planning for the C4ISR hardware and software components is critical in maintaining accurate configurations for current and future Army Watercraft vessels and platforms. The densities and locations for each type of vessel are listed in Paragraph 1.4.

The DoD Information Assurance Certification and Accreditation Process (DIACAP)-compliant software for AWS ViaSat mail (VMail), Windows Standard Automated Logistics Tool Set (WinSALTS) and Electronic Charting System (ECS) computers have been baselined and certified. Each fielded vessel will be required to upgrade to this new baseline and configuration data must be maintained in order to track which vessels have been updated.

The AWS C4ISR software will also require quarterly updates to apply Information Assurance Vulnerability Assessment (IAVA) patches to the software. This quarterly update will require software configuration management to insure each vessel is updated with the most recent software versions. The contractor shall verify that the most current software versions reside on each platform during maintenance visits, or as directed by the Government. The contractor shall record software version information in the SIF database.

The contractor shall report all C4ISR configuration changes as a result of CFSR actions. When directed by the COR, the contractor shall complete vessel-wide inventories within ten (10) working days to record all C4ISR assets and information. The contractor shall be required to report configuration changes and inventory data to the Government for evaluation within five (5) working days of vessel/platform visit. When directed by the COR, this report will not be required and all data will be input into the SIF database, to include any data previously recorded.

The contractor shall be required to participate in configuration reviews. The contractor shall be required to audit the data and review for accuracy before submitting variances to the Government for evaluation. Subsequent to this process step the contractor shall be required to assist the Government, as required, to develop configuration management documentation.

Deficiency Reports/Engineering Change Proposals The DR documents assets that require modification/replacement due to capability/functionality problems. The ECP documents the recommended modifications/replacements with justification, cost assessment, and an implementation and sustainment approach. The contractor shall provide data to support the development or review of DRs/ ECPs as tasked by the COR within ten (10) working days for up to five (5) DRs/ECPs in parallel. Tasks the contractor may be required to perform include, but are not limited to, the following:

· Provide data for Deficiency Reports IAW SOP No. AWS-SEP-01: Product Quality Deficiency Report (PQDR) Procedures for Army Watercraft.

· Review ECPs prepared by other activities for completeness and accuracy

· Prepare and submit ECPs as directed.

Training The Contractor may be required to conduct C4ISR systems and equipment training. This support will be further defined if/when this task is initiated by the Government, at which time an RTEP will be issued by the PCO.

The Contractor may be required to have field service personnel conduct informal training for AWS crew members on-site and/or on-board AWS vessels, expected primarily at the locations identified in Table 1 of paragraph 1.4. Locations will be identified in the RTEP.

The Contractor may be required to have instructors to conduct formal or informal classroom training at Government facilities. The instructors shall possess the knowledge, skills and experience necessary to conduct the specified courses.

The Contractor may be required to provide facilities for training.

For each instance of training conducted by the Contractor, the Contractor may be required to administer post training testing and to report the level of proficiency attained by the students. The Contractor shall be required to distribute Government-provided course evaluation sheets to the students, collect the completed evaluation sheets from the students, and deliver the evaluation sheets to the Government. Specific tasks, schedule and reporting requirements will be specified in the RTEP.

Other Technical Support Requirements The contractor also may be required to prepare technical studies, plans, white papers, analyses and collect data. Specific tasks, schedule and reporting requirements will be specified in the RTEP.

Informal Training The contractor may be required to develop informal operator and maintainer training packets in MS PowerPoint format. The informal training packets will assist trainers in the on-board, or classroom administration of, operator and/or maintenance training. The packets shall be developed based on the target audience MOS. The informal training packets should enable shorter training time frames than the formal training packets. The contractor shall develop and deliver these informal training packets IAW this paragraph.

CONTRACTING OFFICER’S REPRESENTATIVE

The Contracting Officer's Representative (COR) is a Government official appointed in writing via a Designation of COR letter, signed by the PCO. The COR provides technical direction, clarification and guidance with respect to the contract specifications and the PWS. The COR is the technical and programmatic liaison between the contractor and the PCO and is responsible for ensuring satisfactory performance and timely delivery as set forth in the contract. The roles, responsibilities, limitations and duties of the COR are set forth in the Designation of COR letter; a copy of which will be provided to the contractor at time of award.

TRAVEL

Costs for transportation may be based upon mileage rates, actual costs incurred, or a combination thereof, provided the method used results in a reasonable charge. Travel costs will be considered reasonable and allowable only to the extent that they do not exceed on a daily basis, the maximum per diem rates in effect at the time of the travel. The Joint Travel Regulations (JTR), while not wholly applicable to contractors, shall provide the basis for the determination as to reasonable and allowable. Maximum use is to be made of the lowest available customary standard coach or equivalent airfare accommodations available during normal business hours. Sharing of rental cars shall be done to the maximum extent possible for the purpose of minimizing travel costs. All necessary travel meeting the above criteria shall be reviewed in advance by the COR or technical lead and reimbursed at JTR rates. Exceptions to these guidelines shall be approved by the Contracting Officer or his/her designee.

CARE OF CONTRACTOR-HELD GOVERNMENT FURNISHED PROPERTY

The Contractor shall take reasonable measures to maintain all Government-Furnished Property (GFP) to ensure its functionality when used, and to prevent loss and damage to all GFP while being moved, handled, disassembled, inspected, repaired, modified, or reassembled IAW FAR 52.245-1.

SECURITY

The security requirements for this task are set forth on…