024__Performance_Work_Statement_(PWS)_20_April_2017.docx

PERFORMANCE WORK

STATEMENT

Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR)

Support Services For Army Watercraft Systems

19 April 2017

Contents

i

PROGRAM OVERVIEW

SCOPE

The contractor shall provide program management, technical, repair and sustainment 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

Product Director Army Watercraft Systems (PD AWS) has consolidated support for AWS C4ISR assets under the Communication Electronics Command (CECOM) – Logistics and Readiness Center (LRC). 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 synopsis of historical Incident Reports with Resolutions is provided in attachment 001. 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 002. Ongoing efforts and support include configuration management of C4ISR assets across the fleet, and execution of a consistent, centralized, maintenance support process, to service these assets, in support of Army Watercraft C4ISR Systems.

Army Watercraft coordination exists between PD AWS, CECOM, CERDEC, TARDEC, 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.

LCM8 Mod1

SLWT

Trident Pier

BLVR: Fort Belvoir, VA

Support will be required for 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; Alaska and the Alaskan islands; and South East Asia (SEA) and North East Asia (NEA). Home ports and densities of the supported vessels are subject to change.

C4ISR SYSTEM ASSETS

Current C4ISR system assets, by vessel type, can be found in attachments 003 and 004. The information provided in these attachments is the most current available at this time, but variations within vessel classes can be expected as systems are repaired and/or upgraded. Other assets and platforms requiring support may be identified during contract execution. Note: Although the inventory of the LSV-6 is not included in the attachment 0003 content, the contractor is required to provide services to the LSV-6 (the same class as the LSV-1 through LSV-5).

APPLICABLE DOCUMENTS

REGULATIONS, STANDARDS AND HANDBOOKS

The following Regulations, Standards and Handbooks are either referenced directly in the Performance Work Statement (PWS) or are listed due to their general applicability to the requirements of the PWS.

Code of Federal Regulations [CFR], Title 29, Maritime

TECHNICAL MANUALS AND BULLETINS

The following is a list of all existing Technical Manuals and Technical Bulletins for AWS C4ISR systems.

DATA ITEM DESCRIPTIONS

The following is a list of Data Item Descriptions (DIDs) for all Contract Data Requirements List (CDRL’s) of the PWS.

REQUIREMENTS

The Government intends to award a 5 year, Firm Fixed Price (FFP)/Cost-Plus-Fixed-Fee (CPFF)/Cost Reimbursable (CR) Indefinite Delivery Indefinite Quantity (IDIQ) contract for the services and/or supplies described in this PWS.

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

The contractor shall resolve incidents following the Field Maintenance Process (attachment 013) while meeting the specified response timelines according to the Incident Prioritization Table and the AWS Asset Impact Guide (attachment 002, 013). The Contractor is required to provide updates to the incident resolution status in accordance with the SIF Guidelines.

The Government COR may reassign any Incident Report (IR) to activities other than this contract at which time the contractor shall stop work on that Incident Report. The contractor shall be required to ship parts in support of this reassignment. The Government may choose to reassign the Incident Report back to this contract. The Government COR will notify the contractor if this occurs.

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 program manager shall have experience leading cross functional team members, demonstrated successful execution of programs and leadership capabilities associated with PM responsibilities such as defining and communicating project objectives that are clear, useful, and attainable. The PM shall ensure each incident is resolved in accordance with Paragraphs 3.2 and 3.2.1 and use the process outlined in Paragraph 3.2.3.1, Field Maintenance Process Requirements.

The PM shall be the point-of-contact to the Government COR and Government COR representatives, as identified in Paragraph 4. The PM shall maintain timely cognizance of all contractor activities performed under the contract. Responsibilities of the PM shall include meeting with, and reporting progress to, the Government COR as described in Paragraphs 3.1.6, Reports, and 3.1.7, Meetings and Reviews. The PM shall ensure cross-communication within and between team members and tasks and will assign appropriate personnel to each task. The PM shall resolve conflicts with integrated team resources to ensure compliance with contractual requirements. The PM shall inform the Government COR immediately regarding any potential execution impacts to cost, schedule, and/or performance. The PM shall notify the Government COR whenever there are changes to personnel or changes to teaming arrangements. The PM shall ensure that all actions with the Government are coordinated through the COR.

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. A primary responsibility of the PM will be to ensure that the team operates in an integrated and coordinated fashion.

The contractor shall establish a 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 COR at each quarterly IPR and each time there are personnel changes. 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. All team members, including sub-contractors, and vendors, shall meet all of the requirements found in this PWS that are applicable to the function they are assigned. The core management and CFSR staff, as supplemented by proposed non-core CFSRs (further described in paragraph 3.2.2.2), shall be sufficient to process a minimum of 1000 annual average Incident Reports (IRs).

Quality Assurance Management The contractor is required to implement a documented and verified quality assurance management process acceptable to the Government. The contractor shall ensure measurable quality on all products and services provided on this program. The contractor shall provide and maintain an inspection system covering the services under this contract. Complete records of all inspection work performed by the Contractor shall be maintained and made available to the Government during contract performance and for as long afterwards as the contract requires. The Contractor shall flow down all quality requirements to sub-Contractors as they apply to the services under this contract. The Contractor may change the Quality Assurance Management System during the term of the contract as long as a written request is submitted and approved by the Government. The Government has the right to inspect, test and repair services called for by the contract, to the extent practicable at all times and places during the term of the contract. The Contractor shall provide personnel and facilities to support Government’s inspections and audits. (See CDRL F001)

As part of the QA process, the contractor shall ensure that SMEs completely review deliverable documents for accuracy and completeness. Technical deliverables include, but are not limited to, Incident Resolution, specified Field Support tasks, Failure Analysis, and IUID data.

The contractor shall ensure before each IR is closed that all SIF entries have gone through the QA process to ensure they are clear and accurate, use consistent terminology and part names, proper English grammar and correct spellings.

The contractor shall be responsible for correcting each instance of sub-standard workmanship and take appropriate action to prevent any recurrence. The contractor shall monitor all service records to identify trends which may indicate workmanship problems, vessel/environment specific failure causes (power issues, temperature, grounding) or OEM quality problems. If continued workmanship problems are indicated by the service data the contractor shall notify the Government COR and provide a corrective action plan within 10 days. If failures indicate a likelihood of a vessel/environmental issue the contractor shall notify the Government COR. If repeated failures of specific products across a variety of vessels indicate an OEM product quality issue the contractor shall notify the Government COR.

Data Entry Support The contractor shall collect and enter data into the Government data management systems described below.

Single Interface to the Field The CFSR’s shall enter data into the SIF Incident Reporting Module (IRM) in accordance with (IAW) the SIF Guidelines, found in Attachment 002. If for any reason the CFSR cannot enter this data, the contractor shall have a designated representative to enter the remainder of the required data. 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 and completeness of all data entered.

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 Mission Command Support Center (MCSC) /soldier once contact is made with the soldier, update the SIF Worklog daily while working 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 capture as many details as possible to completely convey the current status of the effort, and be free of personal views. The SIF IR Worklog data shall include troubleshooting results, parts requests and deliveries, testing of the completed repair, and all communications with the customer, parts sources, the COR and any designated COR representatives. The data may be entered in the web-based online version of the IRM.

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. Cost data is currently entered into STAMIS which will eventually be superseded by GCSS-ARMY.

The contractor shall deliver STAMIS reports quarterly IAW this paragraph and the attached template (attachment 005) and (CDRL A001).

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

The Government will provide the contractor the necessary hardware and software to enter the STAMIS data at the start of the contract period, which is part of the GFE transfer. The contractor shall be ready to enter data into the STAMIS database within 30 calendar days after delivery of the hardware and software to the contractor.

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. The contractor shall monitor the continuing availability of parts expected to be required to sustain the AWS C4ISR systems for the life of the contract. The contractor shall notify the Government COR when parts are becoming non available. Government COR approval is required for all parts purchases and shipping. The Government will reimburse all approved parts and parts shipping costs. In circumstances where the Government COR does not identify a single source, the contractor will be required to identify sources. Orders less than $3K are not required to have 3 quotes as per FAR 8.405-1(c). Orders above $3K require a minimum of three quotes (if possible).

The contractor shall review planning information regarding fleet requirements, failure data and other essential information, to identify and recommend additional parts to be procured and stocked. The contractor shall provide justification that their recommendations are necessary to facilitate compliance with the Maintenance Action Message DRAFT (MAM) (attachment 006) repair priority timelines. The contractor shall purchase critical parts and tools as approved by the Government COR utilizing the Reorder Point Tool (ROP). Title to such property shall be IAW FAR 52.245-1 “Government Property”. (CDRL B0002)

Primary 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 primary storage facility with a minimum of 8,000 and a maximum of 10,000 square feet of storage space. The facility must be located within 15 miles driving distance of Joint Base Langley/Eustis (JBLE) to support the largest grouping of vessels located at Fort Eustis. 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.

The Government has designated storage facilities at APS-4 and APS-5 which should be used as appropriate to meet Field Maintenance Process timelines. Location of the primary storage facility and any additional storage areas shall be recommended by the contractor and approved by the Government COR prior to any transfer of GFE.

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, CFSR, or vessel site as required.

The contractor shall be required to receive GFE in accordance with CDRL A0002 following contract award. These assets shall be unpacked, inventoried, tested if required as time is available throughout this PoP. A sample list of parts in storage can be found in attachment 007. The contractor shall transfer (to include inventorying, packing and shipping) the assets from their storage facilities to other locations world-wide.

The contractor shall pack, ship and track parts to support field maintenance or other Government use. The contractor shall use the Government COR approved distribution process (already in place) and will use a shipping method that will support Government timelines for resolving field maintenance problems. The contractor will require Government COR 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/received at 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. The contractor shall ensure the Government is not overcharged for any additional visits or parts and services required to correct the faulty workmanship.

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

At the end of this contract the contractor shall ship all GFE equipment to the location which will be provided by the COR. (CDRL A002)

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.(CDRL B001)

Item Unique Identification (IUID) For commercial items costing in excess of $5k the contractor shall be required to support IUID labeling. For these parts the contractor shall provide serial number information to the Government. The contractor is not responsible for registering the items in the IUID registry but will be required to print a durable tag with an image provided by the Government and apply the tag to the item. (CDRL C001)

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

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 in accordance with (IAW) OMB NO. 0702-0120. The contractor is required to completely fill in all the information in the format using the following web address: https://cmra.army.mil. The required information includes: (1) Contract Number; (2) Fiscal Year (FY that the work was performed); (3) Order Number (Delivery Order, Task Order, or Purchase Order Number); (4) Requiring Activity Unit Identification Code; (5) Command (Command of the Requiring Activity that would be performing the mission if not for the contractor); (6) Contractor Name; (7) Total Invoiced Amount (the total dollar amount invoiced during the fiscal year, at the Delivery Order and/or Task Order level. This is the responsibility of the contractor); (8) Questions about Contract Performance (Contractors: Indicate if the contract/order includes the above services); (9) Government Supervision (Are the contractor personnel subject to relatively continuous supervision and control by a Government employee or officer); (10) Government’s Tools and Equipment (Does the Government furnish the principal tools and equipment needed for contract performance); (11) Government Facility (Are some or all of the contractor employees provided with a workspace in a Government facility for use on a regular basis?); (12) Contracting Officer (First Name, Last Name, Phone Number, and Email); (13) Contracting Officers Representative (COR)/Contracting Officers Technical Representative (COTR) (First Name, Last Name, Phone Number, and Email); (14) Contractor (First Name, Last Name, Phone Number, and Email); (15) Location Information (Federal Supply Code (FSC), City of Installation or Services, State, Zip, and Country); (16) Direct Labor Hours; (17) Direct Labor Dollars; (18) Fund Cite. As part of its submission, the contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending 30 September of each Government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor’s systems to the secure web site without the need for separate data entries for each required data element at the web site. The specific formats for the XML direct transfer may be downloaded from the web.

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. The contractor shall report changes to the initial baseline, percent completion, as well as task notes outlining any changes to the schedule. (CDRL D001). A detailed template for the monthly report can be found in Attachment 009.

Weekly Meeting Agenda The contractor shall deliver a Weekly Meeting Agenda one day prior to Weekly Meetings and will include the following: agenda, deliveries due per task, three-week projection, CFSR activities, action items, issues, critical parts inventory, repair or disposal status (including Defense Reutilization Management Organization (DRMO) coordination) and any other items requiring Government attention. A separate email with purchases spreadsheet will be provided to the Government COR only. (CDRL E001) Attachment 012. Include the Weekly Meeting Agenda for each weekly meeting (See 3.1.7.4 below).

Meetings and Reviews Meetings and reviews shall require attendance. These meetings and reviews will be held at locations specified by the contract.

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 one 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.(CDRLs E003 and E004) 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 COR approval. (CDRLs E003/E004) Program (SOW MEETING) The contractor shall attend a Start-of-Work (SOW) meeting at a time and location specified by the Government (normally at the contractor facility). Attendees shall include all prime contractor personnel supporting the program and major sub-contractors. The Program SOW meeting 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 entire integrated team and a discussion of the initial funded tasks and projected schedule. The Government will provide an agenda no less than 5 working days prior to the Program weekly meeting.

In-Process Reviews (IPRs) The contractor shall attend these meetings accordingly. The contractor shall also have personnel directly supporting the program in attendance at each review. Action Items (AI) will be assigned and Courses of Action (COA) may be discussed during these meetings.

Program IPRs/Management Meetings IPRs/Management Meetings are held each quarter. The timing shall be modified as required and may also be scheduled with short notice. The first IPR will be held approximately three months after the Start of Work Meeting at a location to be determined by the Government. Program IPRs can be expected to last two to three days. The Government will provide its topics for these IPRs one week prior and by the contractor PM to the Government COR one week prior.

The content for the Management Meeting will be financials and Government and Contractor discussion topics. The IPR will include summary charts per task including the task description, accomplishments, schedule, risk, cost, and associated graphics/charts. Discussion will also cover action items for the complete team. The Government COR will provide a draft agenda within ten working days prior to each IPR. The contractor shall respond with a completed agenda and completed briefing content to the Government not less than 4 work days prior to the start of the IPR (CDRL E002). Other specific data requirements to be included in the IPR Agenda are shown in the sample agenda for the Program IPR (Attachment 011).

Weekly Meetings The contractor shall support weekly meetings determined by the Government COR. The attendees will be determined by the Government COR and recommendations will be made by the contractor as to who they recommend attend. These will normally be held telephonically but may take place at a location designated by the Government COR. Action Items (AI) will be assigned and Courses of Action (COA) may be discussed during these meetings. The contractor shall deliver an Agenda for each weekly meeting (CDRL E001).

Program Weekly Meetings A Program weekly meeting will be held each Wednesday at 10am, unless previous approval or guidance has been provided by the Government COR. Program meetings will typically be done via teleconference and will last 1-3 hours. The contractor PM will review the near-term schedule and far-term schedule impacts, critical parts status, activities of the CFSRs, the progress of each task deliverable (three week projection), and review open action items. (See Attachment 012, Weekly Meeting Agenda Template)

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.(CDRL D002)

AWS C4ISR Technical Support AWS C4ISR technical support shall include the following: corrective, preventive and On-Condition Cyclic Maintenance (OCCM) support, specialized support for military exercises and operations, failure analysis, C4ISR equipment installation, reconfiguration or removal of C4ISR equipment, and configuration management. The contractor shall develop a technical support team structure for the execution of all tasks described in this section. The requirements for each of these tasks are identified in the following paragraphs.

Field Service Manager The Field Service manager shall be the single focal point for all CFSR activities. In conjunction with the PM, the Field Service Manager 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 Field Service Manager shall ensure cross-communication & collaboration among the following personnel: PM, other program team members, CFSRs, and other SMEs as required.

The Field Service Manager 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 Field Service Manager shall task other program team members to work with Non-Core CFSRs and obtain necessary parts/materiel to expedite resolution of incidents.

The Field Service Manager shall maintain awareness of all IRs to effectively communicate current status, as directed, in a timely manner. The Field Service Manager shall have the capability to effectively communicate COA’s 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 manner. The Field Service Manager shall communicate IR information accurately and expeditiously when required.

Contractor Field Service Representatives (CFSR) The contractor shall retain CFSR personnel with overall system-level expertise pertaining to the C4ISR assets installed on each vessel/platform. The supported vessels/platforms are identified in Paragraph 1.3. The contractor shall subcontract when necessary specific expertise and certifications that are not available except from OEMs or their factory-authorized agents for the resolution of incidents related to C4ISR assets which are identified in Attachments 003 and 004. 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. CFSRs may perform the following: corrective and preventive maintenance, On Condition Cyclical Maintenance (OCCM) support, operational/specialized support, C4ISR equipment installation, reconfiguration or removal of equipment, and configuration management.

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 meet all commercial and military deployment requirements.

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, and in-processing and out-processing at designated times and locations. Accommodations may replicate a field environment. The Contractor shall promptly process any required applications to host nations for visas, country clearances and work permits to perform sustainment services in that nation.

When on-site, CFSRs shall maintain the ability to access support from other SMEs using telephone, email or other communication means to assist in resolving incidents. The contractor shall ensure that the CFSRs adhere to the Field Maintenance Process (attachment 013), the Field Maintenance Prioritization Matrix (included in the SIF Guidelines, Attachment 002).

All personnel assigned to the effort shall meet the contract security requirements as defined in paragraph 7 of this PWS and the DD 254 form (attachment 014).

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 C4ISR assets installed on AWS vessels and platforms to maximize the capability to resolve multiple incidents at one site in one visit.

The contractor team shall maintain qualified Core CFSRs to respond to a minimum of five IRs at the same time at multiple locations without reliance on service providers who are not part of this contract. Exceptions will be coordinated with the Government COR to facilitate scheduling of training. The contractor shall maintain at least one qualified Core CFSR at Kuwait Naval Base as well as Yokohama North Dock Japan. The CFSR at Kuwait Naval Base may be required to provide support at other locations within the South West Asia theater. The contractor shall ensure Core CFSRs maintain the required certifications and credentials to perform services worldwide. The contractor shall maintain a staff of Core CFSR's willing to deploy in support of missions within a hostile environment.

Core CFSRs shall have the 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. If reassignment of an IR is required, the Field Service Manager will be the POC until reassignment of the IR is complete.

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 or to support a surge/increase in the volume of incidents or when other CFSR’s are not available.. A Non-Core CFSR also may be used to minimize travel time and expenses.

CFSR Qualifications The contractor shall ensure that qualified CFSRs are employed upon contract award. The CFSR team shall possess the experience, training, and available certifications 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 of 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 and to ensure accurate and complete incident information is recorded/entered in the SIF Worklog. 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 C4ISR assets listed in Attachments 003 and 004.

CFSRs must be trained and certified on the related C4ISR systems at contract award and will remain current on these certifications throughout the length of the contract. The contractor shall develop, deliver, and update a plan to manage and maintain the CFSR staff skills, proficiency, and certifications. The contractor shall maintain a CFSR training and certification record. This will include current and future training requirements and the training schedule. The information required by this paragraph shall be provided to the Government at each IPR.

CFSR Apprentice Program The contractor shall develop an Apprentice Program that allows for training as it relates to C4ISR sustainment. This is for CFSR development only. No other key personnel positions should this entail. There has historically been a limited pool of CFSR's with the C4ISR sustainment skillset and by development of this program the Government can ensure there is an adequate number of technicians to provide the increased level of support required for the C4ISR Sustainment Program.

Customer Service Representation The contractor shall be responsible to ensure that all CFSR team personnel, including those of subcontractors and vendors, interact with the 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, and that any questions will be required to be reported to the Contract Officer Representative (COR).

The contractor shall document in the SIF Worklog any communication, including telephonic communication that any contractor representatives have with any vessel/customer representatives.

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 Watercraft support personnel will use the Maintenance Action Message DRAFT (MAM), as guidance to initiate an incident report (IR). All CFSRs shall follow the Field Maintenance Prioritization Matrix (included in Attachment 002), unless otherwise directed by the Government COR, 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 the incident IAW the SIF Guidelines shown in Attachment 002.

All CFSRs shall meet the field repair time requirements. An incident shall be assigned a CFSR and the incident POC be contacted within twelve (12) hours of receipt of the IR. The CFSR shall 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. For HIGH priority incidents the CFSR shall provide on-site support to all Continental United States (CONUS) and Hawaii service calls within 48 hours of IRM notification and all incidents outside of the Continental United States ([OCONUS] excluding Hawaii) within 72 hours of IRM notification. For MEDIUM priority incidents the CFSR shall provide on-site support to all incidents within 10 calendar days of IRM notification. For LOW priority incidents the CFSR shall provide on-site support within 30 calendar days of IRM notification.

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, the Contractor is required to notify the Government that they are moving forward with a resolution. For travel and parts over $1,000, approval from the Government COR or designated representative is required to ensure expenditure of funds are consistent with contract requirements. The Contractor shall notify the Government by email and enter the data into the IRM for the Government 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 before departure, then as new developments occur, or at a minimum weekly if there have not been new developments, 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 CFSR shall attach a copy of the completed digital version of the Standard Field Service Report (minus signatures if unable to include them) to the SIF Worklog. The Standard Field Service Report Template is provided at Attachment 015. The completed CFSR and Customer signed version of the Standard Field Service Report shall also be attached to the SIF Worklog if it is separate from the completed digital version.

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, equipment, and parts needed to accomplish repairs. The contractor is required to maintain accountability of these tools issued to each technician and to provide this inventory each week to the Government as part of the Weekly Meeting. The Government will provide tool sets as Government-Furnished Tools (GFT) at the SOWM, as identified in Attachment 0016. Additional tools/equipment shall be purchased as required.

Specialized Support The contractor will 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.

Notification will be provided by the Government to the contractor for potential support requirements within 10 days of when AWS-CSB is made aware of the upcoming event, so the contractor can properly prepare for exercise support, 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 install, test, tag, remove or reconfigure previously installed C4ISR equipment on Army Watercraft platforms at locations worldwide. Recovered items shall be inventoried, packed, and shipped to their warehouse for potential reuse or turned in to a Defense Reutilization and Marketing Office (DRMO) facility as directed by the Government COR.

The contractor will be required to provide support to multiple maintenance/upgrade support tasks at various locations throughout the world, at any given time, as is done in support of any IR. An RTEP will be provided if the support required is outside the IR resolution process. Natural disaster is an example. The above exercises will be on an IR basis, not RTEP.

Configuration Management The DoD Risk Management Frame-work (RMF) 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…