Attachment_1_-_PWS_NSW_IESS_Support_-_KMW_MOD_10_AUGUST.docx

DOCX document 49 KB Posted

Attached to
Enterprise Integrated Electronic Security System
Solicitation number
H92240-15-T-0081
Issued by

About this file

Revised Attachment 1 PWS

View the file

Other files

File Type Posted
Amendment_0002.doc DOC document
Questions_ _Answers_14_Aug.docx DOCX document
Attachment_4_-_Price_List_v2.xlsx XLSX spreadsheet
Attachment_2_-_Past_Performance_Information_Form.doc DOC document
H92240-15-T-0081_Amendment_0001.pdf PDF
H92240-15-T-0081_Final.pdf PDF
Attachment_3_-_Past_Performance_Report_Form.doc DOC document
Attachment_11_-_Wage_Determination_San_Diego.PDF PDF
Attachment_4_-_Price_List_11_Aug.xlsx XLSX spreadsheet
Attachment_7_-_DD254_IESS.doc DOC document
Attachment_5_-__QASP_NSW_IESS_Support.doc DOC document
Attachment_10_-_Wage_Determination_VA.PDF PDF
Attachment_13_-_Wage_Determination_Stennis.PDF PDF
Attachment_8_-_NSW_IESS_Equipment_11_Aug.xlsx XLSX spreadsheet
Attachment_1_-_PWS_NSW_IESS_Support_-_Final.docx DOCX document
Attachment_9_-_PWS_NSW_IESS_Modernization_-_Final.docx DOCX document
Attachment_6_-__QASP_Matrix_NSW_IESS_Support.doc DOC document
Questions_ _Answers_11_Aug_v2.docx DOCX document
Attachment_12_-_Wage_Determination_Homestead.PDF PDF
Attachment_14_-_Wage_Determination_Hawaii.PDF PDF
Questions_ _Answers_11_Aug_afternoon.docx DOCX document
H92240-15-T-0081_11_Aug.doc DOC document
Attachment_9_(Rev_1.0)_-_PWS_NSW_IESS_Modernization_(Revised).docx DOCX document
Attachment_13_-_Wage_Determination_Stennis.PDF PDF
Attachment_11_-_Wage_Determination_San_Diego.PDF PDF
Attachment_12_-_Wage_Determination_Homestead.PDF PDF
Questions_ _Answers.docx DOCX document
Attachment_14_-_Wage_Determination_Hawaii.PDF PDF
Attachment_10_-_Wage_Determination.PDF PDF
Attachment_4_-_Price_List.xlsx XLSX spreadsheet
H92240-15-T-0081_30_July.doc DOC document
Attachment_2_-_Past_Performance_Information_Form.doc DOC document
Attachment_7_-_DD254_IESS.doc DOC document
Attachment_5_-__QASP_NSW_IESS_Support.doc DOC document
Attachment_3_-_Past_Performance_Report_Form.doc DOC document
Attachment_6_-__QASP_Matrix_NSW_IESS_Support.doc DOC document
West_Coast_IESS_Agenda_11-12_JUNE_15_(REV_1).docx DOCX document
NSW_East-West_Coast_IESS_Equipment_List_-_Count.docx DOCX document
East_Coast_IESS_Agenda_8-9_JUN_15_(REV_1).docx DOCX document
Questions_v2_29_May.docx DOCX document
Questions_26_May.docx DOCX document
REQUEST_FOR_INFORMATION_-_NSW_Attachment_to_Interested_Parties_-_Final.docx DOCX document
NDA.docx DOCX document
Show all 43

On GovTribe

Work with this file

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

Text version

PERFORMANCE WORK STATEMENT

NAVAL SPECIAL WARFARE COMMAND

INTEGRATED ELECTRONIC SECURITY SYSTEM (IESS)

SUPPORT

1.0 INTRODUCTION

Naval Special Warfare Command (NAVSPECWARCOM) Force Programs Office is responsible for the physical security and force protection of personnel assigned to its headquarters command and subordinate activities. General physical security is enabled by Access Control Systems (ACS), Close-circuit televisions (CCTV), and Intrusion Detection Systems (IDS). Collectively, these systems form an integrated electronic security system (IESS) capability designed to detect unauthorized intrusion into secured areas and control access of personnel, buildings, and interior spaces.

Naval Special Warfare (NSW) is developing an enterprise plan to standardize and connect disparate ACS, CCTV, and IDS systems across its enterprise that meet appropriate Federal, State, and Local regulations as well as Industry standards. This plan targets the standardization and integration of IESS capabilities among major East and West commands. This plan also extends IESS support to other stateside and overseas locations. In support of this effort, NSW requires contractor support to sustain continuous operations for NSW’s enterprise IESS. The primary places of performance shall include, but is not limited to, the following locations: San Diego, CA; Virginia Beach, VA; Oahu, HI; Stennis, MS; and Homestead, FL. Contractor may be required to travel to CONUS/OCONUS locations in performance of duties. The specific place(s) of performance will be identified in each Task Order Performance Work Statement.

2.0 OBJECTIVE

Provide technical services for the life-cycle support of NSW IESS systems across its enterprise to include: initial modernization, preventive maintenance, software/firmware updates, configuration management, unscheduled maintenance/repair, repairable equipment repair, end-of-life replacement, equipment/material inventory management, emergency maintenance, and special projects. The installed systems will be modified as needed over the period of performance of the contract in order to continue to provide a fully functional system that meets all current security and operational requirements. These systems must enable and enhance physical and electronic security measures designed to protect NSW people, information, and infrastructure.

3.0SCOPE
3.1NSW requires comprehensive maintenance services to ensure continuous operation and sustained functionality of all NSW IESS systems, to include their hardware and software components. The Contractor shall provide the personnel, management, materials, and equipment (not otherwise provided by the Government) necessary to maintain, repair, or replace IESS systems at various NSW locations. This includes:
3.1.1Providing scheduled preventative maintenance services to the existing security system.
3.1.2Documenting the system layout and connectivity, and providing complete configuration management of the system(s) throughout the life of the contract.
3.1.3Providing unscheduled service call response for minor system maintenance and repair (non-emergency) which may occur between scheduled preventative maintenance visits.
3.1.4Providing emergency repair/sustainment services, as necessary, to the existing security system.
3.1.5Providing services for Special Projects, to include the addition and modification of components to the security system as required during the lifetime of the contract.
3.1.6Ensuring that the system meets all security and safety guidance and requirements of this contract.
3.2NSW currently uses a combination of Lenel OnGuard, Lenel Picture Perfect, and Continental Access products for access control. CCTV capability is enabled through a combination of Pelco, Sony, Panasonic, Verint, TruVision, Bosch, and Intellex video management products. Digital Monitoring Products (DMP) components provide IDS support across all sites. These systems provide IESS protection for over 60 buildings, (Attachment 8 – NSW IESS Equipment List) NSW wide.
3.3The contractor shall ensure that components are compatible and interoperable when doing maintenance or replacements. The scope of this service includes associated equipment and hardware such as electronic door strikes, magnetic locks, panic/crash bars, strobe lights & switches, legacy emergency backup batteries, controller units and enclosures, and control & power wiring for the system. Communication infrastructure such as conduit and wiring as well as secondary power infrastructure such as uninterrupted power supply (UPS) and battery backups are considered a part of the system under this scope of work. The contractor will be responsible for maintenance and repair of all additional components added during the course of the performance period(s). Doors in the facility that do not have security devices on them are excluded from the scope. The contractor shall ensure data is protected at all times during the lifecycle of IESS systems. The contractor shall provide maintenance and support to keep IESS systems operable 24-hours per day.
4.0REFERENCES

The following references are required as applicable. In addition, the contractor will comply with applicable Federal, State, and Local regulations as well as Industry standards.

Document
Title
a.
DOD 5220.22M
DoD National Industrial Security Program Operating Manual
b.
DOD 5200.8R
DoD Physical Security Program
c.
DoDM 5200.01 Volumes 1-4
DoD Information Security Program
d.
SECNAVINST 5510.36A
DoN Information Security Program Instruction
e.
OPNAVINST 5100.23G
Navy Occupation Safety and Health Program Manual
f.
OPNAVINST 5530.13C
Physical Security Instruction for Conventional Arms, Ammunition, and Explosives
g.
OPNAVINST 5530.14E
Navy Physical Security and Law Enforcement Manual

5.0 SPECIFIC REQUIREMENTS

5.1 General Requirements

5.1.1 The contractor shall perform life cycle support activities for the sites/facilities and equipment at any operating location for NSW. Summary tasks include: initial modernization, preventive maintenance, software/firmware updates, configuration management, unscheduled maintenance/repair, repairable equipment repair, end-of-life replacement, equipment/material inventory management, emergency maintenance, and special projects. Decisions related to these tasks shall be guided by threat assessments, appropriate risk mitigation measures, and economic return on investment.

5.1.2 The contractor shall supply all parts, labor, materials, equipment, tools, consumables, supervision, and other resources necessary to accomplish all tasks.

5.1.3 Contractor personnel assigned under this contract shall be certified by the security system software manufacturer in that system’s design and installation, configuration, and operation and administration.

5.2 Initial Modernization

5.2.1 Assessment – Initial modernization applies to any hardware or software that is broken beyond repair or outdated and no longer supportable, where time critical replacement is needed. Immediately upon contract award, the contract awardee will be issued a task order to perform an assessment of the IESS components at NSWG-4 and NWSG-10 in Little Creek, VA to determine what will be required within these initial modernization services. Based on the results of the assessment, the vendor shall submit a modernization quote to the Government within 10 days of contract award.

5.2.2 Once the modernization quote has been negotiated with the Government, a task order will be issued for the modernization. Upon task order award, the contractor shall acquire, install, integrate, and test the hardware or software.

5.3 Preventive Maintenance

5.3.1 A Preventive maintenance (PM) action is an inspection or test to ensure every integrated component works according to the manufacturer’s specifications. Preventive maintenance also includes cleaning, adjusting, and servicing system components to ensure they are in optimal operational condition. PM services shall include all consumable parts, labor, and expenses.

5.3.2 The contractor shall develop a Preventive Maintenance Plan (PMP). Upon government approval, the contractor shall execute preventive maintenance actions in accordance with the plan. Subsequent review and updates of the preventive maintenance plan shall be performed quarterly and submitted to the COR for approval.

5.3.3 The contractor shall notify the government on necessary repairs, additions or modifications to the security system discovered during PM. If the government choses to replace or add equipment, this shall be accomplished as an unscheduled maintenance/repair.

5.3.4 Software/Firmware Updates

5.3.4.1 Firmware releases by the manufacturer for any system hardware shall be installed within 30 calendars days of firmware release date (not necessarily coinciding with other scheduled maintenance services). Software patches, updates, and new releases for all installed software on all IT equipment shall be installed and the systems tested for stability and correct operations during all Preventative Maintenance services. Under no circumstances shall installed software on security system equipment be allowed to exceed the 30 days to provide the most current updates or security patches.

5.3.4.2 The contractor is responsible for ensuring that the operating systems (OS), anti-virus programs, and all installed applications (security system software and accessory software including office productivity and photo manipulation) are kept up-to-date with current updates, security patches, and similar. These updates shall occur during the next regularly scheduled preventative maintenance visit. The contractor shall notify the COR in the event that the next preventative maintenance visit in not within 30 days from release of updates, patches, or similar.

5.3.4.3 Preventative Maintenance shall include a Software Support Agreement with the integrated security system software manufacturer. All necessary licenses shall be included in the agreement. The Contractor must be an authorized representative of the integrated security system software and must be fully trained and certified to operate and maintain that system. The Software Support Agreement shall include software patches and installation of such within one month of release (not necessarily coinciding with other scheduled maintenance services).

5.3.4.4 Security Managers shall be trained when software has been updated, at the time of the upgraded software installation.

5.3.4.5 Security Technical Implementation Guide (STIG) Requirements. All computer equipment, operating systems, applications, and peripheral devices installed to support this system must meet any applicable STIG requirements (http://iase.disa.mil/stigs/index.html). The contractor must ensure that all proposed equipment and systems meet all current STIG requirements to the satisfaction of the Government prior to procurement and/or installation.

5.3.5 Configuration Management

5.3.5.1Configuration Management (CM) tasks are implicit to the successful completion of PM services under this contract. The contractor shall maintain equipment configuration audits and provide necessary updates to the government Representative(s) as changes occur, so that CM information remains continuously up-to-date. Configuration Management services shall include producing updated records for: installed equipment; equipment power sources; equipment operation and maintenance manuals; warranty information; and up-to-date as-built drawings of the security device locations and power/data communications cabling pathways on a (government-provided) layout plan of the facility. Updated CM documents shall be provided to the government no later than 30 days after receipt of the original artifacts from the Government.award.
5.3.5.2Configuration Management Equipment List: The CM system shall be supported by an electronic organization tool (Microsoft Excel spreadsheet is acceptable) of the contractor’s design that contains, at a minimum: equipment name, Make, Model, Manufacturer, serial number if applicable, location physically installed, door or area supported, alarm modes, associated (linked) equipment, and capability information (for example, resolution and aperture of a camera, or mounting type and field-of-view for a PIR). The contractor shall validate and maintain an inventory of all system software, software versions, software license information, and system and security patches as part of configuration records. This information may be stored in the integrated security system rather than a separate electronic tool, but must be able to be easily retrieved and saved in electronic (PDF or XLS) format (i.e., a full reporting function must exist). CM equipment lists shall be provided within 30 days of contract award and not more than 15 calendar days following the completion of any system change or work which alters the inventory.
5.3.5.3Configuration Management Drawings: The contractor shall maintain as-built drawings of the security system updates provided not more than 15 days following completion of system changes. If as-built drawings are not available, the contractor shall create system drawings. Project and facility drawing documentation shall be maintained in AutoCAD .dwg format. As-builts drawings shall include, at a minimum, equipment type, location, and label data. CM drawings shall be provided within 30 days of contract award and not more than 15 calendar days following the completion of any system change or work which alters the inventory. Drawings are controlled items and shall be managed for configuration management and program sustainability.

5.3.5.4 The contractor shall inventory other supporting documentation. Where technical documentation is missing on key systems and components, the contractor shall contact the manufacturer or vendor to obtain an electronic copy of technical documentation and deliver it to the government for posting.

5.3.5.5 The CM information maintained is sensitive and considered For Official Use Only (FOUO), and as such shall be maintained only on protected IT systems. Protected IT systems are defined as systems or storage locations that require authentication or need-to-know credentials for access. All information produced under this contract is developed exclusively for the use of the government and remains the property of the government. The contractor may have one copy of as-built drawings at the contractor’s local office and one copy on-site. Although drawings are unclassified, they are not for distribution without the written approval of the COR. The contractor shall account for all drawings created or copied. At the termination or expiration of this contract, the contractor shall deliver all (and not retain) CM materials to the site Security Manager(s) or follow-on contractor via an acceptable transfer medium. The contractor shall destroy all drawings no longer accurate or required according to COMNAVSPECWARCOMINST 5210.1.

5.3.5.6 The government will use HP Records Manager (formerly HP TRIM), or similar database to archive all inventory records, as-built drawings, and other supporting documentation.

5.4 Unscheduled Maintenance/Repair

5.4.1 The contractor shall perform corrective or unscheduled maintenance. Unscheduled maintenance/repair refers to maintenance and repair tasks of a minor nature. This can involve contractor labor to resolve issues or include repairs to or replacement of IESS system components in order to bring the system back to full normal operation. The contractor or the government may identify unscheduled maintenance/repair. The COR will assign a priority and required completion date to the work. The contractor shall install, integrate, and test any equipment that is replaced or repaired and returned to service. Work shall be performed during normal operation times on Monday – Friday, no holidays or over-time is permitted.

5.4.2 Repairable Equipment Repair

5.4.2.1 Repairable equipment is any hardware component that can be economically repaired and returned to service. The government will not accept refurbished equipment in exchange for a repair. If the hardware cannot be repaired it shall be replaced. The contractor shall accomplish equipment repair under the guidelines of unscheduled maintenance/repair.

5.4.2.2 For equipment under warranty, the contractor shall obtain all services required to have repairable equipment repaired and returned to the service or to the government’s inventory of spares.

5.4.2.3 For equipment that is not under warranty and is determined to be economically feasible to repair, the contractor shall be responsible for the obtaining the services required to have the repairable equipment repaired and returned to service or inventory.

5.4.3 End-of-Life Replacement

5.4.3.1 End-of-life replacement is the replacement of any hardware or software that is: broken beyond repair, outdated and no longer supportable (i.e. repairs or upgrades) by the manufacturer, no longer interoperable with the system it is a part of, or no longer has the capacity to meet system requirements (e.g. server processor, storage, or RAM). The contractor shall accomplish end-of-life replacement under the guidelines of unscheduled maintenance/repair.

5.4.3.2 The contractor shall develop a Technical Refresh Plan (TRP). Upon government approval, the contractor shall execute technical refresh maintenance actions in accordance with the plan. Subsequent review and updates of the technical refresh plan shall be performed quarterly and submitted to the COR for approval.

5.4.4 Equipment/Material Inventory Management

5.4.4.1 The government will own and store any equipment and material inventories. The contractor shall manage site inventory of equipment and material spares. The contractor shall determine high- and low-level inventory needs based on usage trends. The contractor shall use a Microsoft Excel to manage this inventory and will record: stock number, nomenclature (Common Name), quantity on hand, low-level quantity, high-level quantity, expiration date (if applicable), reorder date, and received date.

5.4.4.2 The contractor shall develop the initial equipment/material inventory and submit to the COR for approval. Subsequent verification and updates to equipment/material inventories shall be performed quarterly and submitted to the COR for approval.

5.4.4.3 The contractor shall manage equipment and material warranties. The contractor shall cite in the monthly status report equipment or materials approaching warranty expiration and warranties expired. For example, most batteries have a three year warranty. As the contractor replaces batteries, the contractor shall mark the battery with a purchase date in order to track battery warranty.

5.4.4.4 The contractor shall not include any contractor consumables as part site inventory. Examples of contractor provided consumables are: electrical tape, cleaning rags, brushes, etc. Approved consumables for site inventory are such items as cleaners, lubricants, fuses, and lamps.

5.5 Emergency Maintenance

5.5.1 Emergency maintenance is any activity that requires immediate action to prevent loss of equipment or mission critical function. Emergency maintenance services shall include all troubleshooting and repair or replacement of all covered equipment. The contractor shall accomplish emergency maintenance as directed by the COR. The contractor shall accomplish emergency maintenance under the guidelines of unscheduled maintenance/repair.

5.5.2 For emergencies that will result in the loss of equipment or mission critical function for which there is no remedial work around, the contractor shall respond within two hours of being notified by the COR. For all other emergencies, the contractor shall respond within 24 hours of being notified by the COR.

5.6 Special Projects

5.6.1 The government anticipates the need to add, remove or modify equipment in existing IESS systems over the course of the contract. Examples of special projects include: adding buildings or doors to be covered by ACS; replacement of motion sensor with exit card readers; relocation of controller enclosures and interface components; migration of ACS database to upgraded ACS control computers; ACS database software upgrades required to maintain system warranty; installation of additional PIR motion sensors or other IDS components; upgrading controller cards required for ACS database software compatibility; installation of additional fixed or PTZ cameras to CCTV network; or replacement of CCTV multiplexers, controllers, and/or NVR to increase capabilities.

5.6.2. Upon request by the government, the contractor shall prepare a quote with estimates of hardware/software costs and labor hours to complete such an installation and provide to the COR within 10 calendar days of the government request. The COR shall review and approve all special projects. The Contracting Officer shall issue a task order to the contract before any upgrade or modification project begins.

5.6.3 The contractor shall follow the requirements for configuration and inventory management in the execution of these special projects.

5.6.4 The contractor shall install, integrate, and test any equipment that is included as part of the project.

6.0 SECURITY REQUIREMENTS

6.1 Security will be in accordance with the attached DD254. Contractor team individual(s) supporting this task will be U.S. citizens cleared at the Secret level at the start of the task

6.2 The contractor shall insure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for verifying security clearances and indoctrination of visitors, for controlling access to restricted areas, for protecting government property, and for the security of automated and non-automated management information systems and data are fulfilled. The contractor's management system shall prevent unauthorized disclosure of classified and sensitive unclassified information. The government shall be immediately notified if any security incident or any indication of a potential unauthorized disclosure or compromise of classified or sensitive unclassified information.

6.3 The contractor shall provide security management support. Typical efforts include, but are not limited to, performing classified document control functions, classified materials inventories, program access requests, preparing and monitoring personnel indoctrination and debriefing agreements, and maintaining and using security-related databases.

7.0 GOVERNMENT FURNISHED INFORMATION

7.1 The government will furnish all exiting system and equipment configuration and inventory artifacts after award of this contract.

7.2 The government will furnish access to the HP Records management system.

7.3 The government will provide a list of contacts to approve requests for work outside of normal working hours, gain access to restricted areas, or permission to perform life cycle support activities that may affect the day-to-day operations of the facility within ten days of contract award. All requests and authorizations must be in writing, preferably email, and summarized in the monthly report.

8.0 GOVERNMENT FURNISHED MATERIAL/EQUIPMENT

8.1 There may be occasions where the government will purchase and provide materials and equipment. The government will notify the contractor by email when this occurs.

8.2 The government will dispose of non-repairable or non-reusable equipment (e.g., cameras, DVD recorders, control panels, etc.) in accordance with local policies and procedures.

8.3Government furnished information, material, and equipment will be handled IAW FAR Part 45, DFAR Part 245, and the applicable contract clauses.
9.0GOVERNMENT FURNISHED TRANSPORTATION

9.1 The COR will coordinate any Government-provided transportation to geographically remote or inaccessible Government sites such as San Clemente Island. CA.

9.2 The COR will arrange military airlift flights and/or barges to outlying post and training facilities not accessible by land.

10.0 CONTRACTOR FURNISHED MATERIAL/EQUIPMENT

10.1 The Contractor shall furnish all material and equipment required in the execution of this contract. This shall include items such as: software; software licenses; hardware; and materials/equipment ancillary to the installation, operation, maintenance, and access to IESS system components. The also includes any necessary lifting equipment (e.g., scissor lift) required to complete these tasks.

10.2 The contractor shall use the following software tools to support activities under this contract: Microsoft Office suite, Microsoft Project, Microsoft Visio, and AutoCAD. It is the contractor’s responsibility to maintain compatibility with the government systems.

11.0 TRAVEL REQUIREMENTS

11.1 The government seeks to have technical support personnel reside within the area where work is to be performed under this contract. Therefore, the government does not anticipate a need for contractor personnel to travel.

11.2 Should travel become necessary, the contractor shall submit an email request, to the COR, for coordination and approval; prior to initiating any travel plans. All travel claims shall reference the e-mail, letter or phone call that granted approval. Failure to gain prior approval may result in disallowance of invoiced travel costs.

12.0 DELIVERABLES

The contractor shall make the following deliverables:

Section
Deliverable
Method of Delivery and Due Date
5.3
Preventive Maintenance Plan
· Initial Plan delivered under Task Order

· Updates due the first business day of each quarter thereafter

· Planned changes summarized in monthly status report

· Delivered as email attachment

5.3
Configuration Management Equipment Lists
· Initial Audit delivered within 30 days under Task Orderof receipt of existing artifacts

· Due 15 calendar days following any system change or alteration

· Due the first business day of each quarter thereafter

· Changes summarized in monthly status report

· Final Audit due 30 days before the end of contract

· Delivered on CD

5.3
Configuration Management (As-Built) Drawings
· Initial Audit delivered within 30 days under Task Orderof receipt of existing artifacts

· Due 15 calendar days following any system change or alteration

· Due the first business day of each quarter thereafter

· Changes summarized in monthly status report

· Final Audit due 30 days before the end of contract

· Delivered on CD

5.3
Technical Documentation
· Initial Audit delivered within 30 days under Task Orderof receipt of existing artifacts

· Due 15 calendar days following any system change or alteration

· Due the first business day of each quarter thereafter

· Changes summarized in monthly status report

· Final Audit due 30 days before the end of contract

· Delivered on CD

5.4
Technical Refresh Plan
· Initial Plan delivered under Task Order

· Updates due the first business day of each quarter thereafter

· Planned changes summarized in monthly status report

· Delivered as email attachment

5.4
Equipment / Material Inventory
· Initial Inventory delivered under Task Order

· Due the first business day of each quarter there after

· Changes summarized in monthly status report

· Final Inventory due 30 days before the end of contract

· Delivered as email attachment

NA
Monthly Status Report
· Delivered as email attachment

· Content to include:

· Preventive Maintenance performed

· Configuration Audits performed

· As-built Drawings updated

· Technical Documentation updated

· Unscheduled/Repair Maintenance performed

· Repairable Equipment repaired

· End-of-Life Replacements

· Equipment/Material Inventory Management

· Emergency Maintenance performed

· Other notable on-site support activities

· Due the fifth business day of each month

14.0
Contractor Manpower Report
· Delivered online at http://www.ecmra.mil

· Due annually NLT 31 October and/or at contract completion

13.0 OTHER CONDITIONS AND REQUIREMENTS

13.1 Normal working hours for this contract shall fall between the hours of 6:00 AM to 6:00 PM Monday-Friday. The contractor shall schedule employees to assure availability during normal working hours.

13.2The contractor shall obtain prior approval from the COR or, in emergencies, from the on-site government contact before working outside of normal working hours, weekends, or holidays.
14.0CONTRACTOR MANPOWER REPORTING

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for Naval Special Warfare Command via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil.

15.0 QUALITY ASSURANCE (QA)

The Government shall evaluate the Contractor’s performance under this contract using the methods of surveillance specified in the Quality Assurance Surveillance Plan (QASP). The Government shall record the surveillance observations. When an observation indicates defective performance, the Government representative shall request the Contractor representative to initial the recorded observations.

The following items have been identified for surveillance in accordance with the QASP: Modernization Plan; Modernization; Preventive Maintenance Plan; Preventative Maintenance; Repair and Replacement; Configuration Management Equipment Lists; Configuration Management (As-Built) Drawings; Technical Documentation; Technical Refresh Plan; Equipment / Material Inventory; and Monthly Status Report.

16.0 COR AND POINT OF CONTACT

The Contracting Officer’s Representative (COR) is Mr. Ken Warburton, N01FP, who can be reached at (619) 537-1230 or via email at kenneth.warburton@navsoc.socom.mil. He serves as the point-of-contact for this effort.

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