Docstoc

N65236-10-R-0012 Draft PWS.doc - SPAWAR E-Commerce Central

Document Sample
N65236-10-R-0012 Draft PWS.doc - SPAWAR E-Commerce Central Powered By Docstoc
					SECTION C – DESCRIPTION/SPECS/WORK STATEMENT

SPECIFICATIONS/STATEMENT OF WORK/PERFORMANCE WORK STATEMENT
Work under this contract shall be performed in accordance with the following description/ specifications/
statement of work (SOW) which herein shall be referred to as Performance Work Statement (PWS):

1.0           PURPOSE

1.1           BACKGROUND

The mission of the Space and Naval Warfare Systems Engineering Center Atlantic (SSC-LANT) is to provide
quality full-service systems engineering and acquisition to rapidly deploy capabilities to the Naval, Joint and
National Warfighter through the development, test, evaluation, production and fielding of sustainable,
survivable, and interoperable Command, Control, Communications, Computers, Intelligence,
Surveillance, Reconnaissance (C4ISR), Information Operations (IO), and Space capabilities that enable
knowledge superiority. The intent of this contract is to plan, develop, deploy and maintain Security, Law
Enforcement and Business Automation Information Sharing Solutions for customers within the Department of
the Navy (DON), Department of Defense (DOD), federal, state, and local government agencies located in both
Contiguous United States (CONUS) and Outside Contiguous United States (OCONUS).

1.2           SCOPE

The Contractor shall provide services required for the Security, Law Enforcement and Business
Automation Information Sharing systems identified in Section 1.1 above utilizing the applications, tools,
and automation features listed in Section 3. Work shall be performed in the following areas:

      1.   PROGRAM MANAGEMENT (Para 3.2) (5%)
      2.   SYSTEMS ENGINEERING (Para 3.3) (15%)
      3.   SOFTWARE ENGINEERING (Para 3.4) (25%)
      4.   INFORMATION ASSURANCE Para 3.5) (10%)
      5.   TECHNICAL SUPPORT (Para 3.6) (10%)
      6.   SYSTEM IMPLEMENTATION (Para 3.7) (20%)
      7.   TESTING AND EVALUATION (Para 3.8) (10%)
      8.   LIFECYCLE LOGISTICS SUPPORT (Para 3.9) (5%)

The Contractor shall perform tasking in accordance with individual task orders (TOs) issued by SSC-
LANT. Each TO shall reference one or more of the technical areas listed above, and define the objectives,
scope, individual sub-tasks and deliverables as required. No work will commence on a specific tasking
until the individual TO has been approved and officially issued by the designated SSC-LANT Government
Procuring Contracting Officer (PCO).

NOTE: Work performed in Iraq and Afghanistan may be required.

2.0           APPLICABLE DOCUMENTS (AND DEFINITIONS)

All work shall be accomplished using best commercial practices and current acceptable industry
standards. The applicable references and standards invoked will vary within individual tasks and will
be specifically called-out in each task order. In accordance with Defense Acquisition Policy changes,
maximum utilization of non-Governmental standards will be made wherever practical. Where
backward compatibility with existing systems is required, selected interoperability standards will be
used. For purposes of bidding, the following documents are not exclusive; however, all contractors
shall be able to meet those cited when applicable to the task order.




                                                                                                                  1
2.1          REQUIRED DOCUMENTS

The following documents are part of this PWS and are mandatory for use. Unless otherwise specified,
the document’s effective date of issue is the date on the request for proposal. Additional applicable
documents may be included in specific task/delivery orders.

Security and Information Assurance Directives, Instructions and Manuals

       Document Number                          Title
a.     OPNAVINST 5510.1H                        Department of the Navy Information and Personnel
                                                Security Program Regulation
b.     DoDD 8500.1                              DoD Directive – Information Assurance
c.     DoDI 8500.2                              DoD Instruction – Information Assurance (IA)
                                                Implementation
d.     OPNAVINST 5510.16                        Department of the Navy Information Security Program
                                                Regulations
e.     DoD 8570.01-M                            DoD Manual – Information Assurance Workforce
                                                Improvement Program
f.     SECNAVINST 5510.30                       DoN Regulation – Personnel Security Program
g.     OPNAVINST 5239.X                         Department of the Navy Information Systems Security
                                                (INFOSEC) Program
h.     DoD 5220.22-M                            DoD Manual – National Industry Security Program
                                                Operating Manual (NISPOM)
i.     DoDD 5220.22                             DoD Directive – National Industrial Security Program
j.     DoDD 8570.1                              DoD Directive – IA Training, Certification, and Workforce
                                                Management
k.     DoD 5200.2-R                             DoD Regulation – Personnel Security Program


2.2          GUIDANCE DOCUMENTS

The following documents are part of this PWS and are to be used as guidance. Unless otherwise
specified, the document’s effective date of issue is the date on the request for proposal. Additional
applicable documents may be included in specific task/delivery orders.

Security and Information Assurance Directives, Instructions and Manuals

         Document Number                              Title
a.       OPNAVINST 5530.13                            Department of the Navy Physical Security Instruction for
                                                      Conventional Arms, Ammunitions, and Explosives
                                                      (AA&E) (Latest Edition)
b.       MCO P5530.14                                 Marine Corps Physical Security Program Manual (Latest
                                                      Edition)
c.       Director of Central Intelligence             Physical Security Standards for Sensitive
         Directive 6/9                                Compartmented Information Facilities (SCIF)
d.       Director of Central Intelligence             Protecting Sensitive Compartmented Information Within
         Directive 6/3                                Information Systems




                                                                                                                 2
National Fire Protection Association (NFPA)
      Document Number                     Title
a.    NFPA 70                             National Electrical Code
b.    NFPA 72                             National Fire Protection Alarm Code
c.    NFPA 730                            Guide for Premises Security
d.    NFPA 731                            Standard for the Installation of Electronic Premises Security
                                          Systems
e.    NFPA 780                            Lightning Protection Code
f.    NFPA 1221                           Standard for the Installation, Maintenance, and Use of
                                          Emergency Services Communications Systems, latest
                                          version

American National Standards Institute (ANSI)
      Document Number                     Title
a.    ANSI X3.4                           American National Standard Code for Information
                                          Interchange (ASCII)
b.    ANSI/IA-RP 12.6                     Installation of Intrinsically Safe Systems in Class I
                                          Hazardous Locations

Underwriter’s Laboratories, Inc. (UL)
      Document Number                     Title
a.    UL-294                              The Standard of Safety for Access Control System Units
b.    UL-639                              The Standard of Safety for Intrusion Detection Units
c.    UL-1076                             National Industrial Security Systems
d.    UL-2050                             The Standard of Safety for Proprietary Alarm Units

Software Development
      Document Number                     Title
a.    ISO/IEC -9000                       International Organization for Standardization, Quality
                                          Management Principles
b.    ISO/IEC 12207                       Information Technology – Software Life Cycle Processes
c.    ISO/IEC 15288                       Systems Engineering – System Life Cycle Processes
d.    ISO/IEC 15939                       Software Engineering – Software Measurement Process
e.    ISO/IEC 14764                       Information Technology – Software Maintenance
f.    ISO/IEC 15408                       Information Technology – Security Techniques. Evaluation
                                          criteria for IT security
g.    EIA/IEEE J-STD-016                  Information Technology Software Life Cycle Processes
h.    IEEE/EIA 12207                      Software Life Cycle Processes

Military Standards/Handbooks
      Document Number                     Title
a.    MIL-HBK-419                         Grounding, Bonding, and Shielding for Equipment and
                                          Facilities
b.    MIL-HBK-1013.1A                     Electronic Security System Specifications and
                                          Requirements

SPAWAR Systems Center Atlantic
      Document Number                     Title
a.    SPAWARINST 4720.1                   SPAWAR Shore Installation Process Handbook (SIPH)
                                          (Latest Edition)
b.    SPAWARINST 4200.5                   Contractor Performance Assessment Reporting System
                                          (CPARS) (Latest Edition)

                                                                                                          3
Electronic Industries Alliance
      Document Number                        Title
a.    EIA-568-568A                           Commercial Building Telecommunications Wiring
                                             Standards
b.    EIA-569                                Commercial Building Standard for Telecommunications
                                             Pathways and Spaces
c.    EIA-606                                Administration Standard for the Telecommunications
                                             Infrastructure of Commercial Buildings
d.    EIA-STD-232-E                          Interface Between Data Terminal Equipment and Data
                                             Communication

Specifications
      Document Number                        Title
a.    SEIWG-ICD-0101                         Command and Control Display Equipment (CCDE)
                                             Information Interchange using XML
b.    TASS-ICD-001, Latest Revision          Interface Control Document for Control of Pan-Tilt
                                             Mounts, Cameras, and Other Devices, SEWIG
c.    TASS- ICD-002, Latest Revision         Generic Device Interface Control Document using XML,
                                             SEIWG
d.    SEIWG-005A                             Interface Specification, RF Data Transmission Interfaces
                                             for DoD Physical Security Systems, dated 21 October 1985

Unified Facilities Criteria (UFC)
      Document Number                        Title
a.    Unified Facilities Criteria (UFC) 4-   DoD Minimum Antiterrorism Standards for Buildings
      010-01                                 (Latest Edition)


b.    UFC 4-020-01                           DoD Security Engineering Facilities Planning Manual
                                             (Latest Edition)
c.    UFC 4-021-01                           Design and O&M: Mass Notification Systems (Latest
                                             Edition)
d.    UFC 4-021-02NF                         Security Engineering Electronic Security Systems, with
                                             Change 1 (Latest Edition)
e.    UFC 4-022-01                           Security Engineering: Entry Control Facilities / Access
                                             Control Points (Latest Edition)

Miscellaneous
      Document Number                        Title
a.    OPNAVINST 11010.20D                    Facilities Projects Manual
b.    NAVSEA OP-5                            Ammunition and Explosives Ashore Safety Regulations for
                                             Handling, Storing, Production, Renovation, and Shipping
c.    NAVORD OP-3565                         Radio Frequency Hazards to Ordnance Personnel and Fuel
                                             Technician Manual
d.    NAVFACINST 11010.44                    Department of the Navy Shore Facilities Planning Manual
e.    EM 385 1-1                             U.S. Army Corps of Engineers Safety and Health
                                             Requirements Manual (Latest Edition)
f.    29CFR1910                              Occupational Safety and Health General Industry Standards
                                             and Interpretations (Latest Edition)
g.    29 CFR 1926                            Occupational Safety and Health Construction Standards and
                                             Interpretations




                                                                                                         4
2.3                  SOURCE OF DOCUMENTS

Information on obtaining copies of Federal Specifications may be obtained from General Services
Administration Offices in Washington, DC, Seattle, San Francisco, Denver, Kansas City, MO., Chicago, Atlanta,
New York, Boston, Dallas and Los Angeles.

Copies of military specifications may be obtained from the Commanding Officer, Naval Supply Depot, 3801
Tabor Avenue, Philadelphia, PA 19120-5099. Application for copies of other Military Documents should be
addressed to Commanding Officer, Naval Publications and Forms Center, 5801 Tabor Ave., Philadelphia, VA
19120-5099.

All other commercial and industrial documents can be obtained through the respective organization’s website.

3.0                  PERFORMANCE REQUIREMENTS

The following paragraphs list all required support tasks that shall be required throughout the contract life. The
contractor shall provide necessary resources and knowledge to support the listed tasks. Specific objectives shall
be dependent on the base contract and the task order (TO) written against the base contract. The contractor
shall complete all required tasks while controlling and tracking performance and goals in terms of costs,
schedules, and resources.

3.1.                 RELEVANT EXPERIENCE

3.1.1          Programs and Initiatives
The contractor shall provide support in the development, implementation and support of Security, Law
Enforcement and Business Automation information sharing systems for the DoD and federal, state, local
government agencies. The requirements for this contract vary in scope, magnitude and complexity and will
vary from minor additions to an existing security operations center to the design and development of a national
level, enterprise-wide, large-scale information sharing system. These Security, Law Enforcement and Business
Automation information sharing systems will be integrated collections of a variety of sub-system types and
capabilities including but not be limited to the following:

            a.       Emergency Management/Response Systems;
            b.       Data and Information Systems including Database and Enterprise Search;
            c.       Business Information Technology Systems/Services;
            d.       Enterprise Infrastructure Solutions, Tools and Network Infrastructure;
            e.       Computer-Aided Dispatch Systems;
            f.       Geospatial Information & Services (GIS) data development and system integration;
            g.       Incident Management Systems;
            h.       Situational Awareness and Common Operational Pictures (COPs) and Dashboards;
            i.       Complex Event Processors / Anomaly Detection Systems;
            j.       Information Analysis and Decision Making Systems;
            k.       Decision Support Tools; and
            l.       Data Fusion, Entity Resolution, and other Analytical Tools.


3.1.2    Examples of Types of Systems to be Developed/Maintained Under this Contract
The following four Security and Law Enforcement Information Sharing systems are listed as examples of the
type of work to be performed under this contract. These projects may or may not be handled under this
contract. This list is not meant to be exhaustive; rather, it is designed to provide a further understanding of the
type of work to be performed.

       a.        Example System #1
                 Navy Emergency Management Response System (NERMS) has been deployed and is operational.
                 NERMS has three fully-integrated system components: (1) Records Management System (RMS), the
                 enterprise web portal centrally hosted for access by all Navy fire, police, and Emergency Medical
                 Services (EMS) personnel and their commands worldwide; (2) Computer-Aided Dispatch (CAD),
                 provides dispatchers with visual display, automated incident tracking capabilities, and increased
                 dispatching capability with extended geographic coverage; and (3) Mobile Data Terminals (MDTs),

                                                                                                                      5
     provides CAD capabilities to field personnel in emergency response vehicles, response unit
     communication with dispatch centers, and real-time input to the records management application.
     NERMS is fully-integrated, scalable, and expandable, supporting Navy police, firefighters, and EMS at
     Navy shore locations worldwide.

b.   Example System #2
     Department of Homeland Security (DHS) Common Operational Picture (COP) has been deployed and
     is operational. The COP requirement was designed to consolidate disparate data into one common
     database to improve situational awareness and reduce threats. The result was a substantial increase in
     situational awareness, time savings, and reduced threats. The COP was designed to consolidate
     disparate types of data and geospatial elements into one common database and provide an operational
     picture to assist in managing an incident or situation, to facilitate collaborative planning and decision-
     making among federal, state, and local organizations thus improving situational awareness, saving
     time, and reducing threats. The COP design process leveraged Commercial off-the-Shelf (COTS) and
     Government off-the-Shelf (GOTS) technologies to minimize the expense associated with a fully
     customized solution. The COP is a web-enabled application and is hosted by existing agency hardware
     and platforms. The COP applies the following COTS and GOTS software and operating systems:
     Oracle database (DB), Java, JavaScript, HyperText Markup Language (HTML), Environmental
     Systems and Research Institute (ESRI), and Integrated Common Analytical Viewer (iCAV), to name a
     few.

c.   Example System #3
     Homeland Security Information Network (HSIN) has been deployed and is operational.
     The HSIN requirement was to develop a common network platform for gathering, fusing, analyzing
     and reporting information related to potential terrorist and other threats to the U.S. It also serves as the
     Department of Homeland Security network for operational information sharing and collaboration to
     maintain situational awareness, as well as monitoring response and recovery efforts resulting from
     terrorist, natural and human caused disasters. HSIN is an overarching system that collects and shares
     information with military services, federal, state and local government agencies including local police
     and fire departments.

d.   Example System #4
     Transportation Security Administration (TSA) Knowledge Management System (KMS) is in the
     developmental stage. The requirement for the KMS system is to shorten the time it takes to maintain
     the TSA “watch log” or collection of known information. We expect to improve efficiency through
     improved data structures, an increase in system performance and new collaborative tools. The TSA
     KMS provides a platform for information gathering, logging, and tracking, converting that raw
     information into usable information products, and automating workflow. Along with tracking Request
     for Information (RFI) actions and responses, the KMS maintains static lists of current threats, people,
     airports and items of interests with manual references. The KMS capability minimizes the amount of
     hands on manual functions used within TSA.

e.   The contractor shall have experience in dealing with interfaces to embedded systems, such as data
     extraction, data insertion, etc. The contractor shall modify existing interfaces for legacy systems, or
     re-engineer new interfaces for existing or planned systems. This could involve converting legacy
     applications to completely different standards based upon architecture. The contractor may be required
     to re-engineer front-end processors and programs to convert data from one form to another. The
     contractor shall develop requirements for all interface work or review interface documentation to
     determine the suitability of the identified interface for the planned application.




                                                                                                               6
3.2.         PROGRAM MANAGEMENT

3.2.1          Program Support
The contractor shall be required to work closely with the government project manager and provide support at
the sponsor level and at the contract level. As directed in task orders, coordination of meetings, preparing
budget drills, developing agenda items, attending high-level meetings, generating minutes, and tracking action
items may be required. Other support may require the contractor to recommend policies, doctrine, tactics, and
procedures at the federal, state, and local levels, by giving past expert opinion or using analysis of actual
outcomes. Program support may require significant coordination and interfacing with various DoD and non-
DoD activities located in CONUS and OCONUS. The ultimate objective is ensuring that the government’s
requirements are met on schedule and within budget.

3.2.2         Program Support Documentation
The Program Manager (PM) shall be responsible for ensuring that all Program Management Contract
Deliverables (CDRL A001) are tracked and submitted on time throughout the life of contract. The following
are typical documents:
      Statement of Work or Performance Work Statement
      Cost Estimation
      Meeting Agenda and Minutes
      Plans of Action and Milestone
      Work Breakdown Structure (WBS)
      Various Program Acquisition related documents: Mission Needs Statement (MNS), Capability
         Production Documentation (CPD), Operational Requirements Document (ORD), etc.

3.2.3        CMMI Process Documentation
The contractor shall also develop, maintain, and deliver (CDRL A022) project-required documentation and
equipment using the standardized CMMI® processes. The government realizes that projects range in size and
complexity. Not all projects will require all plans cited in this document. Some projects may require all plans,
but minimal content. When the Contractor assists the government in the development of various project plans,
SPAWAR management is the authorizing authority for determining which plans to complete for each project.
Contractor tasking may include assisting the government with the development of Project Management Plans
(PMP), Project Requirements Plan (PRP), Installation Design Plan (IDP), Risk Management Plan (RMP),
Configuration Management Plan (CMP), or other project required documents – in hard copy or electronic
formats.
The PMP serves as the initial project scope document and tasking agreement between SPAWAR Systems
Center Atlantic (SSC-LANT) and the funding sponsor. The signed PMP becomes a reference document used to
aid the Contractor with the development of other project related documents. PMP content includes a brief
description of the task, background leading up to the requirement for tasking, identification and definition of
the roles and responsibilities of project participants – including organizational chart, identifying high level
scheduling, identifying the base project monitor and control categories; i.e. design, engineer, procure,
implement, training, life-cycle support and an addendum that defines the process of project baseline and
requirement change to include any related forms. The Contractor shall use the PMP to aid in the development
of project proposals, cost estimates, and schedules.
The Project Requirements Document (PRD) shall include a brief description of the task, background leading up
to the requirement for tasking, identification, and definition of the roles and responsibilities of project
participants, the organizational chart, identification of high level scheduling, identification of the base project
monitor and control categories; i.e. design, engineer, procure, implement, training, life-cycle support and an
addendum that defines the process of project baseline and requirement change to include any related forms. In
some instances, the government may provide a PRD to the Contractor to use in development of a proposal, cost
estimate and schedule. The government may task the Contractor to conduct site surveys and develop PRDs,
proposals, cost estimates and schedules. The Contractor shall develop the PRD per SPAWAR Systems Center
Atlantic Shore Installation Process Handbook. Where a PRD is provided to the Contractor and utilized as the
basis for issuance of tasking, the Government shall specify the PRD in the PWS and therefore, the specified
PRD shall be binding scope along with the PWS for the awarded Delivery Order. In cases where the PRD is
developed after award of a Task Order and not specified in the PWS, the PRD shall become a reference
document to be used by the Contractor for the performance and delivery of other project deliverables.


                                                                                                                   7
The System/Software Requirements Document (SRD) is a compilation of the functional requirements of a
system(s) or software for a project. This document can be used within the PRD.
The Risk Management Plan (RMP) identifies potential problems before they occur, so that risk handling
activities may be planned and invoked as needed across the lifecycle to mitigate adverse impacts on achieving
objectives. The Contractor shall develop an overarching Contract RMP. This plan will be used as the basis for
Risk Management activities performed under each Delivery Order. In execution of each Task Order, the
Contractor shall use the approved RMP to document and report risks to cost, schedule (critical paths) and
performance. Task Order risks shall be reported per section 5.0 Contract Data Requirements in this PWS.

The Configuration Management Plan (CMP) establishes and maintains the integrity of work products using
configuration identification, configuration control, configuration status accounting, and configuration audits.
The contractor shall use the IDP to identify the configuration items and develop the CMP.

3.2.4          Performance Work Statement
The PWS identifies and describes the contractor’s tasking. The approved PWS becomes part of the Task Order.
The SSC LANT DOCOR will issue the PWS to the contractor who shall prepare and provide a formal cost
estimate to the SSC-LANT DOCOR within 15 business days from receipt of PWS for routine Task Orders and
within 7 business days for urgent Task Orders. If the contractor does not respond within the specified amount
of time, their proposal will not be evaluated against other competing offer or’s proposals. The government
realizes that projects range in size and complexity, therefore, SSC-LANT reserves the rights to allow the
contractor additional time beyond that stated herein to prepare and submit formal proposals. In those cases,
special instructions concerning the amount of time in business days that the contractor has to respond with a
proposal will be provided in the request for proposals.


3.3.         SYSTEMS ENGINEERING SUPPORT

The Contractor shall provide the following system engineering support to design, develop and deploy new
Information Sharing solutions. The solutions may be stand alone or may require integration into existing
systems. The Contractor shall deliver Systems Engineering Documentation (CDRL A023) as called specified in
the task orders.

3.3.1        Requirements Development and Assessment
             a. Generate and establish system , functional and performance requirements; perform reviews
                and provide written assessments of system and subsystem level technical specifications,
                studies, test plans and procedures, test reports and related design documents as required by the
                TO.
             b. Assess the use of information sharing technologies that provide records management,
                document repositories, and collaboration for system (i.e. Microsoft SharePoint and Oracle
                universal content manager as well as domain specific systems for security, law enforcement
                and emergency management).
             c. Assess the availability and suitability of existing technology to satisfy system upgrade.
                performance objectives. Assessments shall utilize COTS and GOTS to the maximum extent
                possible.
             d. Assess the use of Geospatial tools that integrate with commonly used databases such as
                Oracle and MS SQL Server.
             e. Analysis of Alternatives (AoA) activities.

3.3.2         Architecture Development
The contractor shall develop and deliver architecture products to support the assessment, development, fielding
and use of information sharing systems.




                                                                                                                  8
3.3.3        Design Services
The contractor shall provide engineering and related services such as but not limited to the following:
             a. design to usability specifications;
             b. develop system improvements;
             c. evaluate human and system interfaces to resolve interoperability discrepancies and issues;
             d. perform performance investigation and analysis to determine causes of failures and
                malfunctions and potential areas of redesign and improvement; and
             e. design new integrated systems of systems

3.3.4        Systems Engineering and Systems Engineering Management Documentation
The contractor shall develop and deliver documentation such as but not limited to System or Software
Requirements Reviews (SRR), Preliminary Design Reviews (PDR) and Critical Design Reviews (CDR), Test
and Evaluation Master Plans (TEMP), Systems Engineering Plans (SEP), and Systems Engineering
Management Plans (SEMP).

3.3.5          Modeling & Simulation
The contractor shall use models, including emulators, prototypes, and simulators to support making managerial,
technical, strategic, or tactical decisions on the system design and as a way to reduce costs associated with the
design and development of new or enhanced capabilities. Modeling and simulation shall be used during
usability testing to support human system integration activities as needed.

3.4          SOFTWARE ENGINEERING

Software engineering includes the design, development, documentation, and maintenance of software to support
a specific government requirement and is the greatest single component of this contract. Software will be
developed for multiple hardware and software platforms, including but not limited to x86 and VM’s running
both Windows and Linux/Unix, mobile devices such as iphone and android, and proprietary embedded
processors and operating systems. Utilization of certified software and computer personnel shall also be
required. The lead contractor (prime and/or subcontractor) that is responsible for leading software development
efforts shall define a software development approach appropriate for the computer software effort to be
performed under each task. The approach shall be documented in a Software Development Plan (SDP). The
contractor shall follow this SDP for all computer software to be developed or maintained under this effort. At a
minimum, the SDP shall meet the following criteria:

3.4.1        Software Development Plan (SDP) (CDRL A003)

3.4.1.1      The SDP shall be initially delivered to the government no later than (NLT) 30 days after task order
award but no later than commencement of software activity. No specific format is required; the document is
content driven. Subject to review, the SDP shall be placed under configuration control after it has been
approved by the government. The document shall be resubmitted for review and government approval when
periodic updates are performed subsequent to process improvement reviews.

3.4.1.2      The SDP shall document all processes applicable to the system to be acquired, including the
Primary, Supporting, and Organizational life cycle processes as defined by Institute of Electrical and
Electronics Engineers (IEEE) and the Electronic Industries Association (EIA) (IEEE/EIA) Std. 12207 as
appropriate.

3.4.1.3        The SDP shall define the offeror’s proposed life cycle model and the processes used as a part of
that model. In this context, the term “life cycle model” is as defined in IEEE/EIA Std. 12207.0. The SDP shall
describe the overall life cycle and shall include primary, supporting and organizational processes based on the
work content of this solicitation. In accordance with the framework defined in IEEE/EIA Std. 12207.0, the SDP
shall define the processes, the activities to be performed as a part of the processes, the tasks which support the
activities, and the techniques and tools to be used to perform the tasks. Because IEEE/EIA Std 12207 does not
prescribe how to accomplish the task, the offeror must provide this detailed information so the Navy can assess
whether the offeror’s approach is viable.




                                                                                                                9
3.4.1.4       The SDP shall contain the information defined by IEEE/EIA Std. 12207.1, section 5.2 (generic
content) and the Plans or Procedures in Table 1 of IEEE/EIA Std. 12207.1. The content of the SDP shall be
tailored to contain only the sections that are applicable to the tasks defined in the Task Order. If any
information item is not relevant to either the system or to the proposed process, that item is not required.

3.4.1.5        The SDP shall adhere to the characteristics defined in section 4.2.3 of IEEE/EIA Std. 12207.1, as
appropriate. In all cases, the level of detail shall be sufficient to define all software development processes,
activities, and tasks to be conducted which will allow the use of the SDP as the full guidance for the developers.
In accordance with section 6.5.3b of IEEE/EIA Std. 12207.1, information provided must include, at minimum,
specific standards, methods, tools, actions, reuse strategies, and responsibilities associated with development
and qualification including safety and security.

3.4.2         Software Support Services
The contractor shall provide software engineering and development support services for components of the
systems and equipment as required by the TO. Software development tasks may be awarded to modify,
enhance, or upgrade existing systems. Systems/products will range from client-server applications, employing
interactive and batch processes, to customized web-based solutions, operating in a standalone or in very large
scale enterprise distributed environments. Information Sharing is about building user interfaces that allow
collaborative real time access to data from a variety of sources, feeds, interfaces, and applications, supporting
those user interfaces with the appropriate database structures, and with them serving up the right information to
the right people at the right time. This is done by heavy use of data analysis, data fusion, data maintenance,
system administration, data format conversion; the proper handling of user, license and information rights
management; and strong authoritative data source/data authenticity management.

The contractor shall be knowledgeable and experienced in developing, upgrading, documenting, and
implementing software. The contractor shall be capable of developing software requirements, designing
specifications, implementing individual software components, and providing the following software related
documents: test plans, deployment impact statements, and risk assessments. The contractor shall also be
familiar with SSC-LANT Software Development Plans (SDP), be able to define embedded computer resource
requirements for system development and life cycle maintenance, construct programming guides, and develop
test and operation manuals. The contractor shall participate in the design review meetings, technical reviews,
and conferences and presentations to provide system design expertise. IT system specifications, technical
reports, and hardware and software documentation shall be produced following the standards referenced in this
contract. The contractor shall document the scope of the end products to be produced. The contractor shall
develop top level software architectures, to include Service Oriented Architectures (SOA). In general, the
software design will be modular in nature.

3.4.2.1 The contractor shall complete all software development activities in accordance with the Software
Engineering Institute CMMI Level 3 processes. The contractor shall deliver all software modules, including
both source code and executables to SSC-LANT.

3.4.2.2 The contractor shall have demonstrated expertise in the design, development, and implementation of
static web sites, dynamic web sites, enterprise portals, information sharing systems, common operational
pictures, records management systems and GIS systems. They should have demonstrated experience with
Oracle, MS SQL Server and MS Access databases – HTML, Cold Fusion, ASP, Java, JavaScript, C++, C#,
COM, IIS, Iplanet, .NET, J2EE, XML, ebXML, SOAP, UDDI, XSL, WSDL and other W3C/OASIS open
architecture standards.

3.4.2.3 The contractor shall have experience with DOD and Federal Cross Domain Solutions (CDS).

3.4.2.4 If the government does not provide it as GFI, the contractor shall develop and deliver software
functional requirements specification. This will include the functional and business process requirements,
which include process definition, data models and process functional requirements as well as a test plan for
functional verification of the requirements during the build process. These requirements shall include
functional methodology documentation. The methodology shall include data sources, information flow,
calculations, expected outputs (reports), and any external interfaces. In addition, the requirements shall include
descriptions of the graphical user interface (GUI) requirements, including diagrammed screen layouts and
screen functions. The contractor shall participate in an Integrated Product Team (IPT) comprised of multi-
functional stakeholders to transform stakeholder needs, expectations, constraints, and interfaces into customer

                                                                                                                10
requirements. Contractor user requirements development efforts shall include, but are not limited to, the
following:
        a. Given customer requirements, create requirements which are feasible, refined and elaborated to the
        point that they support the development of product and product component requirements for the
        product life cycle.
        b. Establish and maintain product and product component requirements that are based on the customer
        requirements.
        c. Allocate the requirements for each product component.
        d. Analyze existing systems and capabilities for their ability to meet component needs. Identify
        interface requirements for each component.
        e. Analyze and validate requirements and ensure that a definition of required functionality is
        developed.
        f. Establish and maintain operational concepts and associated scenarios.
        g. Establish and maintain a definition of required functionality.
        h. Analyze derived requirements to ensure that they are necessary, sufficient and testable. Develop a
        test plan along with each requirement.
        i. Analyze requirements to balance stakeholder needs and constraints.
        j. Verify that requirements meet all stated systems specifications and comply with pertinent policies
        and regulations. Validate requirements to ensure the resulting product will perform as intended in the
        user’s environment using multiple techniques as appropriate.
        k. Establish and maintain the plan for performing the requirements development process.
        l. Place designated work products of the requirements development process under appropriate levels
        of configuration management.
        m. Identify and involve the relevant stakeholders of the requirements development process as planned.
        n. Monitor and control the requirements development process against the plan and take appropriate
        corrective action.
        o. Objectively evaluate adherence of the requirements development process and the work products and
        services of the process against its process description, standards and procedures, and address
        noncompliance.

3.4.2.5 If the government does not provide it as GFI, the contractor shall develop a software specification which
shall include a detailed functional summary for each module, accuracy and validity requirements, timing,
flexibility, security requirements, screen formats for each input function, input data sources, processing
requirements, outputs, interface requirements, data flow, and proposed programming languages.

3.4.2.6 If the government does not provide it as GFI, the contractor shall develop a system database
specification which shall include: organization of the database by record structure, field tables, storage
requirements, and record linkages.

3.4.2.7 If the government does not provide it as GFI, the contractor shall develop a system hardware
requirements specification which details the type and number of hardware resources required to meet the
operational need.

3.4.2.8 For each module the contractor shall develop preliminary module design, and evaluate capability to
meet design goals and to integrate with existing or planned systems. Audit trails, transaction logging and
recovery and definition of failure and error recovery requirements and capabilities shall be conducted.

3.4.2.9 The contractor shall conduct development testing that includes verifying the system performance in
accordance with the approved test plan in a laboratory environment. The contractor shall also assist SSC-
LANT and their sponsors in performing Operational and Acceptance Testing of the fully integrated solution.

3.4.3        INFORMATION TECHNOLOGY REQUIREMENTS

3.4.3.1       Enterprise Software Initiative (ESI) /SmartBuy (ESI/Smart Buy)
The contractor shall ensure commercial software procurements for which ESI/SmartBuy agreements are in
place are either utilized or waived. Specific requirements will be evaluated/approved by the government prior
to issuance of task order.




                                                                                                              11
3.4.3.2       Section 508 Compliance
The contractor shall ensure that all software procured and/or developed is compliant with Section 508 of the
Rehabilitation Act of 1973, 26 CFR Part 1194. In accordance with FAR 39.204, this requirement does not
apply to contractor acquired software that is incidental to the task, software procured/developed to support a
program or system designated as a National Security System (NSS) or if the product is located in spaces
frequented only by service personnel for maintenance, repair or occasional monitoring of equipment.

3.4.3.3        Registration of DoN Applications
The contractor shall ensure that no Functional Area Manager (FAM) disapproved applications are integrated,
installed, or operational on Navy networks. The contractor shall ensure that all databases that use database
management systems (DBMS) designed, implemented, and/or hosted on servers and/or mainframes supporting
Navy applications and systems be registered in the DoN and Database Management System (DADMS) and are
FAM approved. All integrated, installed, or operational applications hosted on Navy networks must also be
registered in DADMS and approved by the FAM. All systems supported shall be registered within the DoD IT
Repository (DITPR). Specific Requirements will be evaluated/ approved by the Government prior to issuance
of task order.

3.4.3.4     Registration of DoN Networks and Servers
The contractor shall ensure that all networks, servers, or associated devices procured and/or connected to a
Navy network complete DADMS registration and receive FAM approval. Specific requirements will be
evaluated/approved by the Government prior to issuance of task order.

3.4.3.5      SAHRAP SPAWAR CIO approval for purchase/lease/rental for new or upgraded server or
application hosting service
Server/Application Hosting Review and Approval Process (SAHRAP) is applicable for any server or
application hosting procurement connecting to a Navy network CONUS Ashore. The contractor shall ensure
compliance with SPAWAR(CIO) Policy Memo, SPAWAR Implementation of SAHRAP of 9 Aug 09 for any
servers procured connecting to a Navy network that do not meet an exemption. NSS and Top Secret (TS)
networks are exempt. Specific requirements will be evaluated/approved by the Government prior to issuance of
task order.

3.4.3.6   IT Architecture, Information Assurance and Federal Information Security Management Act
(FISMA) The contractor shall provide the following support according to task order:

3.4.3.6.1    Ensure that no production systems are operational on any RDT&E network.

3.4.3.6.2    Follow DoDI 8500.2 of 6 Feb 2003 when deploying, integrating, and Implementing IT capabilities.

3.4.3.6.3   Migrate all ASHORE production systems to the Navy, Marine Corps Internet (NMCI)
environment where available.

3.4.3.6.4    Work with government personnel to ensure compliance with all current Navy IT & IA policies,
including those pertaining to CARS.

3.4.3.6.5  Follow SECNAVINST 5239.3A of 20 Dec 2004 & DoD 8500.2 of 6 Feb 2003 prior to integration
and implementation of IT solutions or systems.

3.4.3.6.6     Support security/Information Assurance requirements definition by identifying controls to be put
in place for the identified systems and networks.

3.4.3.6.7    Recommend processes for maintaining and enforcing security/Information Assurance for identified
systems, networks and applications in support of security engineering.

3.4.3.6.8    Ensure that the certification and accreditation (C&A) requirements and processes are documented
in accordance with DODI 8510.1 in support of security engineering delivering Section 3 of the Systems
Security Authorization Agreement (SSAA), System Identification Profile (SIP), and Plan of Actions and
Milestones (POA&M).



                                                                                                                 12
3.4.3.6.9   Ensure that requirements are coordinated to ensure all pertinent, regulatory IA policies are
complied with.

3.4.3.6.10 Ensure that all SSAAs and associated accreditation support documentation are in compliance with
current Chairman of the Joint Chiefs of Staff Instruction (CJCSI), DoD, DON and SPAWAR mandates and
regulations in support of security engineering as it relates to the SSAA.

3.4.3.6.11 Any task orders which required portal or website development for Navy or Marine Corps will
require OPNAV N6 waiver approval in accordance with CNO 042205Z OCT 06, NAVY PORTAL - WEBSITE
INVESTMENT MORATORIUM.

3.4.3.6.12 Wireless data service or service with strong authentication, non-repudiation, and personal
identification when accessing a DoD Information System - The contractor shall ensure that all wireless local
area network (LAN) traffic shall be protected, at a minimum, by a Federal Information Processing Standards
(FIPS) 140-2 certified device that authenticates and encrypts at Layer 2 of the Open Systems Interconnection
(OSI) model. The contractor shall comply with DoDD 8100.2 and ASD (NII) memorandum dated 2 June 2006
when implementing Wireless Local Area Network (WLAN) Device systems. All WLAN traffic must be
compliant with 802.11i standards and meet WiFI Protected Access-2 (WPA-2) certification.

3.4.4       Data Rights

The Government shall have unlimited data rights to all data developed under this contract unless specified
differently at the task order level. If not specified in a task order, all software development, source code,
documentation, etc., under contract tasking shall become government property and cannot be resold, licensed or
otherwise distributed commercially. All software licenses and equipment/material warranties, guarantees etc.
for software and equipment/material purchased for the government under contract tasking shall be registered to
SSC-LANT.

3.5          INFORMATION ASSURANCE

Information Assurance (IA) includes tasks which the contractor shall perform to protect and defend information
and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-
repudiation. This includes providing for restoration of information systems by incorporating protection,
detection, and reaction capabilities.

The contractor shall be required to mitigate vulnerabilities found by running scans in accordance with local IA
policy. The contractor shall present a final report detailing all vulnerabilities have been mitigated prior to
completion of Pre-Installation Test and Checkout (PITCO). System remediation shall not impact system
functionality.

3.5.1        Information Assurance Training and Certification
In accordance with clause 252.239-7001, contractor personnel performing IA functions shall meet all
information assurance (IA) training, certification, and tracking requirements prior to accessing DoD information
systems. Personnel tracking information, which includes subcontractor personnel, shall be included in the
monthly contract status report.

3.5.2      Design Changes
Any equipment/system installed or integrated into Navy platform shall meet the IA requirements as specified
under DODI 8500.2.




                                                                                                              13
3.5.3         Defense Information Assurance Certification Accreditation Process (DIACAP).
Background: DoD Information Assurance Certification and Accreditation Process (DIACAP) guidance
document, signed and dated November 28, 2007 will replace the DoD Information Technology Security
Certification and Accreditation Process (DITSCAP). SSC-LANT will use DIACAP and requires that computer
operating systems and networks (at a minimum) are accredited. The accreditation boundary shall be defined by
the appropriate Service level Designated Approval Authority (DAA).
The DIACAP process has four phases: Phase 1 - Definition, Phase 2 -Verification, Phase 3 - Validation, and
Phase 4 - Post Accreditation. SSC-LANT shall perform the roles and responsibilities of the Certifying
Authority Agent (CAA). The CAA, SSC-LANT DOCOR and Contractor will work together to complete Phase
1. Accreditation boundaries for Information Assurance (IA) requirements shall be identified and included in the
design, acquisition, installation, operation, upgrade, or replacement of systems that fall within the defined
accreditation boundary. All systems shall be assigned a Mission Assurance Category. The Contractor shall
support Mission Assurance Category definition and assist the CAA in resolving requirements interpretation.
Confidentiality controls shall be defined by the sensitivity of the information processed by the system. SSC-
LANT will define this information sensitivity to determine confidentiality controls. The contractor shall
support Phase 2 efforts to develop all required documentation (SSAA/DIPs) and the SPAWAR DOCOR will
provide Project Management, oversight and interpretation to the contractor, who with the SPAWAR DOCOR
shall liaison with the CAA throughout the Phase 2 process. The Contractor shall support the CAA to complete
Phase 3 process including CT&E, request for Interim Authority to Operate, SIP or IA risk mitigation that results
from CT&E findings, subsequent System Test and Evaluation (ST&E), request for Authority to Operate (ATO)
and IA risk mitigation that results from ST&E findings. Risk mitigation shall be performed by the Contractor
who is responsible for ensuring the system is hardened to the latest DISA Gold Disk and IA Retina Scans
requirements at the time of CT&E and ST&E. The Contractor shall support the SPAWAR DOCOR in
providing general support information to the system owner, the individual sites Information Technology
stakeholders, who are responsible for Phase 4, adhering to Life-Cycle IA policy and performance of Life-Cycle
IA measures.
The Contractor shall develop a Plan of Action and Milestones (POA&M) that addresses major milestones for
each system that will undergo DIACAP in accordance with task order.


3.6          TECHNICAL SUPPORT

3.6.1         Material and Equipment research
The contractor shall research available material and equipment to integrate with the operational environment, as
described in the site survey report.

3.6.2          Material and Equipment supply support
The Contractor shall procure systems, equipment and material in accordance with the TO. Acquisition selection
factors shall include price, availability, reliability, and supportability within current supply system. The
contractor shall provide all support data and cost estimates necessary to justify a fair and reasonable price per
item procured. The contractor shall have an adequate accounting system to track all items and the acquisition
status per task order and per item. Unless otherwise noted, all items procured by the contractor shall be stored
at the contractor’s facilities and transported by the contractor as directed in each task order. If required, the
contractor shall be responsible for generating material reports for the base contract summary report and for each
awarded TO. Deliverable documentation shall vary and be specified per in each TO, if applicable.

3.6.3         Maintenance
This type of work entails, at a minimum, the following: maintenance, overhaul, troubleshooting, and repair of a
system and/or equipment. Maintenance support work may involve traveling. Contractor personnel shall be
highly experienced in electronic systems and familiar with the proposed system, unless otherwise stated in the
task order. The contractor shall develop in accordance to task order an O&M plan, system administration plan,
and system administration guide for preventative and corrective maintenance. The contractor shall carry out
performance monitoring as specified in the task order.




                                                                                                              14
3.6.4         Help Desk/Customer Support
The contractor shall set up a help desk according to industry best practices in accordance with each task order.
The help desk will assist the system users with technical related issues to assure customer service. The help
desk will strive to ensure customer satisfaction, respond to requests for support within published time frames,
request feedback for opportunities for improvement, regularly review and monitor established performance
indicators.

The contractor shall develop a Service Level Agreement (SLA) which details policies and procedures for how
the help desk operates. The SLA should include methods of contact, hours of operation, and responsibilities of
those making requests.

The contractor shall develop a Standard Operating Procedure (SOP) that details how to delineate the authority,
processes for deployment, and roles and responsibilities. This will be a living document based on current assets
available and will be updated as needed to reflect emerging and expanding capabilities.

3.6.5    Assessments

The Contractor shall develop and deliver Assessment Reports (CDRL A024) and shall perform assessments as
specified in task orders. Examples might include but will not be limited to:
               a. analyzing the implementation of emergency management, public safety, security, and law
                  enforcement information sharing systems and equipment in terms of impact and performance
                  and comparing that with user needs, requirements documents or specifications.
               b. research and development for information sharing technology exploration.
               c. policy research and analysis as it relates to information sharing.

3.6.6          Technical Field Support
The Contractor shall provide appropriate expertise at customer sites to support a wide range of C4ISR activities
related to information sharing solutions in accordance with the TO.


3.7          SYSTEM IMPLEMENTATION

3.7.1        Site Surveys, Analysis, and Reports
The contractor shall perform comprehensive assessments through site surveys to establish detailed project
requirements. The Contractor shall analyze and document all resultant findings from site surveys performed;
identify all deliverable tasks and subtasks; identify any prerequisite tasks that are to be provided by others or
government furnished; identify all relevant stakeholders names, affiliation and roles and responsibilities;
identify interfaces with specific systems/subsystems; identify procurement, installation, logistics, maintenance,
and training needs; and contain relevant drawings, photos and/or depictions of project related aspects.
Logistics shall include identification of on-site work space, on-site storage space, and on-site shipping and
receiving requirements. The Contractor may be tasked to transform site survey reports into a site specific PRD.
Within ten (10) working days of the completion of the site survey of each task or TO, the Contractor shall
submit a detailed Site Survey Report (CDRL A004) to the SPAWAR Atlantic Project Engineer (PE) and COR.
Include a 10-working day minimum Government review period for all deliverables.


3.7.2         System Integration Design
While the majority of the deliverables under this contract are expected to be software solutions which exist in
the IT realm, at times they will have to be supported by hardware which must be integrated into an existing
physical facility. For both software and hardware tasks, the Contractor shall develop and deliver a design for
system integration (CDRL A025) using various technical requirements, specifications, and drawing documents
to support system integration. When required, drafting support shall be required to support the documentation.
Cost, risks, constraints, and schedules shall be considered. Documentation will be required in accordance with
each task order. Documentation may include but is not limited to the following:




                                                                                                               15
3.7.2.1       Installation planning and design documents provide the detailed plan for system design,
integration, and installation. They include installation design; system interfaces, roles and responsibilities, and
establishes an agreement with the site for the work to be performed. These documents will vary depending on
the system, integration and site complexity and the users’ requirements. The two examples below are neither an
exhaustive list nor will they apply to each task order.

             a. The Base Electronics System Engineering Plan (BESEP) is the basis or preliminary technical
             reference governing installations of physical electronics facilities or portions of the facilities. The
             BESEP normally includes a listing of components to be installed, shows preliminary design of the
             installation, describes the functions and required interface with existing or planned systems, and
             when finished provides an authoritative engineering plan and major equipment/material list
             necessary for determining final design specifications. If required, the Contractor shall develop the
             BESEP in accordance with Navy standard and Combat ID Systems Policy and Procedures for
             Base Electronic Systems Engineering Plans (BESEP) and Facility Requirements Supplement
             (FRS).

             b. The Installation Design Package (IDP) is the drawing package detailing the proposed physical
             installation, which includes, but is not limited to, fabrication details, moving of equipment,
             integration, and all materials provided by Contractor and government. IDPs are based upon
             approved, final BESEPs and guidance documents that utilize good engineering practices and state-
             of-the-art techniques. Drawings, data and other work products shall be completely and thoroughly
             checked and reviewed by the Contractor for technical accuracy and completeness. If required, the
             Contractor shall develop the IDP in accordance with SSC LANT Drawing Standard in accordance
             with referenced “COMPNAVSPAWARINS Shore Installation Process Handbook," latest version,
             with emphasis on "Appendix Q – Installation Design Plan (IDP) Development."

3.7.3        System Test Plan
The Contractor shall develop and deliver a System Test Plan (CDRL A026) which describes the plan to
introduce the new capability into the existing environment with acceptable risk. Based on the type of work
required by the task order, this plan may take on a variety of forms. Software updates will be required to be
accomplished on representative development and/or test servers before moving to production. For systems
integrating hardware, a PITCO shall be required. This shall include, but is not limited to, installation tests and
systems tests for system validation for all system performance requirements. The PITCO may be conducted at
Government facilities, Contractor facilities, or a project site. PITCO provides a level of confidence that the
equipment/system that will be delivered for installation is fully operational. The cost-effectiveness and
necessity for a PITCO is dependent upon the demonstrated level of quality of the system/equipment providers
and the potential cost that would be incurred to replace defective equipment found during installation. The
SPAWAR DOCOR shall specify within each DO if a PITCO is required and specify all applicable equipment
and systems to be tested.

PITCO Acceptance Test Plan (ATP). The PITCO ATP is a document that is used by the Contractor and
SPAWAR DOCOR to document that the new system/equipment has been properly configured and/or integrated
prior to installation, has been tested, and is ready for shipment to the installation site. The PITCO ATP will
contain sufficient detailed testing to fully exercise the system’s or equipment’s capabilities to the extent
possible within the PITCO test environment. The ATP document shall include the names of the installation and
site personnel that participated in the ATP along with places for signatures/initials that certify that the testing
was satisfactorily completed. PITCO ATPs shall be developed in accordance with referenced SPAWAR
Systems Center Atlantic Shore Installation Process Handbook. The Contractor shall develop the PITCO ATP
and submit to the SPAWAR DOCOR who will review, provide changes and identify final testing requirements.

The contractor shall conduct System Operational and Verification Testing (SOVT) prior to live operation of the
system.

At a minimum, the test plan shall specify what will be tested, who will accomplish the testing, where the test
will take place, how long the test is expected to take, the procedure to be followed, the acceptance criteria, and
will list any special conditions that must be met including outside dependencies such as GFI or GFE that must
be available.



                                                                                                                 16
3.7.4         System Integration
The Contractor shall develop and deliver System Integration Plan (CDRL A027). The Contractor shall perform
system integration in accordance with an approved system integration design, system test plan, and system
integration plan. Throughout the process the Contractor shall submit other system integration deliverables as
required by task orders. System Integration support functions and deliverables may include but are not limited
to the following:

             a.   Identify the key technical requirements for the integration.
             b.   Recommend the best approach for performing the integration.
             c.   Identify the various support elements required to complete the integration.
             d.   Develop the best procedures for end-to-end integration and per task order.
             e.   Determine required interfaces with installation site personnel including planning, staging of
                  equipment, site access, coordination of daily installation activities with site operational
                  activities, access/ installation/test/acceptance liaison points of contact, and other necessary
                  interfaces.
             f.   Plan for and facilitate Government inspection of integration progress.
             g.   Submit a plan for integration of all systems and subsystems using industry best practices
                  including a proposed detailed milestone schedule for system stand up, delivery of training
                  materials, and training sessions for users of the system, using the SSC LANT Site/Project
                  Management Plan for format and guidance.
             h.   Perform the required fabrication, assembly, and installation tasks.
             i.   Analyze the integration process and its effectiveness and recommend solutions for resolving
                  deficiencies identified during inspections.
             j.   Collect data to determine schedule compliance and provide installation status reports.
             k.   Complete and deliver associated as-built drawings and technical data packages.

3.7.5        System Delivery/ Deployment

For systems which are to be delivered after integration, the contractor shall prepare a system
delivery/deployment plan (CDRL A028) according to task order and follow it in the delivery of the systems to
end users.


3.8          TESTING AND EVALUATION

3.8.1        Test and Evaluation Documentation

The Contractor shall develop and deliver Test and Evaluation Documentation (CDRL A029) as specified in task
orders such as but not limited to Test and Evaluation Master Plans (TEMP), System Operational Verification
Tests (SOVT) and Acceptance Test Plans (ATP)

3.8.2        Functional Test and Evaluation

The Contractor shall perform functional test and evaluation primarily for the purposes of verification,
throughout the systems and software development process as specified in task orders.

3.8.3        Operational Test and Evaluation

The Contractor shall perform operational test and evaluation primarily for the purposes of validation as
specified in task orders.

3.8.4        Information Security/Assurance Test and Evaluation

The Contractor shall perform information security/assurance test and evaluation as part of the DIACAP process
throughout the systems and software development process as specified in task orders.




                                                                                                                17
3.9          LIFECYCLE LOGISTICS SUPPORT

The contractor shall apply engineering and analytical disciplines required to implement life-cycle (acquisition)
logistics as a multi-functional technical management discipline associated with the experimental development,
design, development, test, production, fielding, sustainment, and improvement modifications of cost effective
systems that achieve the warfighter’s peacetime and wartime readiness requirements. The principal objectives
of lifecycle (acquisition) logistics are to ensure that support considerations are an integral part of the system’s
design requirements, that the system can be cost effectively supported through it life-cycle, and that the research
and development facilities and infrastructure elements necessary to the design, development, initial fielding, and
operational support of the system are identified, developed, acquired, and supported.

3.9.1        ILS Documentation

The contractor shall develop Integrated Logistics Support (ILS) documentation according to the task order
which will include life cycle cost estimate documentation, life cycle planning, and training guides and manuals.

3.9.2        Perform Level of Repair Analysis (LORA)

The contractor shall develop a LORA as specified in task orders which details maintenance planning over
the life cycle of the system. The LORA should include tracking and maintaining requirements testability,
reliability, and maintainability.

3.9.3        Training

The contractor shall be able to apply the engineering and analytical disciplines required to ensure that the
warfighter and technical support community is provided with adequate instruction including applied exercises
resulting in the attainment and retention of knowledge, skills, and attitudes regarding the platforms, systems,
and warfighting capabilities they operate and maintain. In this capacity the contractor shall develop training
materials and shall perform training of system users at all levels through a wide variety of training mediums
which shall include but not be limited to:
               a. product manuals, user’s guides, and troubleshooting guides as both standard written
                    documents and interactive documentation (i.e. with features such as flash);
               b. development and delivery of web enabled course content; and
               c. traditional classroom based instructor led training

3.9.4        Performance Monitoring

The contractor shall develop a system performance monitoring plan as specified in task orders which details the
methods by which performance will be monitored over the life cycle of the system. The system performance
data gathered will feed into the overall system operations and maintenance plan to support both preventative
and corrective maintenance actions.


4.0          CONTRACT ADMINISTRATION

4.1          Contract Liaison

The contractor shall assign a technical single point of contact, also known as the Program Manager (PM) who
shall work closely with the government Contracting Officer, Contracting Officer’s Representative (COR), and
the Task Order Contracting Officer’s Representative (DOCOR). The PM shall be ultimately responsible for
ensuring that the contractor’s performance meets all government contracting requirements within cost and
schedule. The PM shall have the requisite authority for full control over all company resources necessary for
contract performance. The PM shall have authority to approve task order proposals in emergent situations.
Responsibilities shall also include, but not be limited to, the following: personnel management; management of
government material and assets; and personnel and facility security. In support of open communication, the
Contractor shall have, unless otherwise directed, monthly meetings with the COR and periodic reviews with the
Project Engineer (PE).



                                                                                                                18
4.2           CONTRACT MONITORING AND MAINTENANCE

During urgent situations, the contractor shall have processes established in order to provide all necessary
resources and documentation any time during the day in order to facilitate a timely TO award or modification.
The contractor shall be responsible for providing any required support documentation in a timely manner so as
to not disrupt the contract award process.

4.2.1        Contract Administration Documentation
Various types of contract administration documents are required throughout the life of the contract. At a
minimum, the contractor shall provide the following documentation in accordance with each TO:

4.2.1.1        Contract and Task Order Status Report
Contract and Task Order Status Reports (CDRL A014) shall be developed and submitted monthly and/or
weekly depending on the requirements of each TO and the COR. The prime contractor shall be responsible for
collecting, integrating, and reporting all subcontractor reports.

(a)    Monthly, Contract – A monthly contract status report shall be provided to the COR. Due on the 10 th of
each month, the report shall include, as a minimum, the following items and data:
1.     period of performance
2.     period of reporting
3.     the Not-to-Exceed (NTE) contract amount and the funds received to date balance
4.     list all contract level Modifications, date of modification, sentence summary, and if applicable, list the
       total modification funding amount
5.     list total labor hours expended (current and cumulative) per company
6.     list total labor cost (current and cumulative) per company
7.     list total Other Direct Costs (ODCs) expended (current and cumulative) per company
8.     list total Travel expended (current and cumulative) per company
9.     list total Material expended (current and cumulative) per company
10.    list total Fee expended (current and cumulative) per company
11.    list total contract ceiling amounts: labor hours, costs, fee, and total NTE
12.    list total remaining contract ceiling amounts: labor hours, costs, fee, and total NTE
13.    list all TOs written against the basic contract (annotate TOs being submitted as a monthly report,
       completion dates and those completed)
14.    under a separate cover due to the sensitivity of information, list of personnel and their associated
       company who worked on the contract, their burdened hourly rate, and the number of labor hours billed
       (current and cumulatively). If applicable, IAW clause 252.239-7001, the personnel list shall specify
       those individuals who are IA trained and certified.

(b)       Monthly, TO – A monthly TO status report shall be provided to the applicable government Project
Engineer or DOCOR. Commencing one full month after the TO award date, TO status reports shall be posted
no later than the 10th of each month. For every active TO, the monthly progress report shall include, as a
minimum, the following items and data:
1.        TO Number & Title
2.        period of performance
3.        period of reporting
4.        the Not-to-Exceed TO amount and the funds received to date balance
5.        list all TO level Modifications, date of modification, sentence summary, and if applicable, list the total
          modification funding amount
6.        list total labor hours expended (current and cumulative) per company
7.        list total labor cost (current and cumulative) per company
8.        list total Other Direct Costs (ODCs) expended (current and cumulative) per company
9.        list total Travel expended (current and cumulative) per company
10.       list total Material expended (current and cumulative) per company
11.       list total Fee expended (current and cumulative) per company
12.       list total TO ceiling amounts: labor hours, costs, fee, and total NTE
13.       list total remaining TO ceiling amounts: labor hours, costs, fee, and total NTE
14.       list quantity of hours charged per employee (current and cumulative)
15.       list of all companies that have charged to the TO, the company’s charging period, and the cost, the
          total number of hours charged (current and cumulative)

                                                                                                                 19
16.      Estimated total cost to complete; noting shortages or overages
17.      Identification when obligated costs have exceeded 75% of the amount authorized (Note: Identifying
         cost overruns in the monthly status reports does not preclude a Contractor from the 75% notification
         requirement in clause H-344 or for immediate notification to the government when all funds have been
         expended prior to work being completed on a task order
18.      Summary of work performed (includes meeting specified milestones and action items; identification of
         new problems areas including technical issues, cost increases or schedules slippage; status of
         previously identified problems; listing of all CDRL ordered and status of deliverables; effort to be
         completed during next reported period


(f)       Data Calls – As required, a status report shall be emailed to the TO Originator and the COR within six
working hours of the request. All information provided shall be the most current. Cost and funding data shall
reflect real-time balances. Report shall account for all planned, obligated, and expended charges and hours.
The report shall include, as a minimum, the following items and data:
1.        Percentage of work completed (by contract and task order level)
2.        Percentage of funds expended (by contract and task order level)
3.        Updates to the POA&M and narratives to explain any variances
4.        List of personnel (by location, security clearance, quantity)

4.2.1.2       Task Order Closeout Report
Every Task Order (TO) shall require a closeout report (CDRL A015), which is due no later than 30 days after
the TO completion date. The Report shall be submitted electronically as an e-mail attachment; hard copies are
required only upon request. Government compatible Microsoft Office Package software shall be used and the
form shall be easy to follow. The report shall include, as a minimum, the following information:

(a)       Financial data – Breakdown of all costs (labor, travel, material, fee) per invoice, all key personnel that
were utilized/charged on the job, specify all work yet to be charged, all remaining funds, and balances available,
if any, for return (de-obligation), etc.

(b)      Deliverable status – Percentage job complete, any outstanding issues, CDRL status, list of any
items/services under workmanship/manufacturer warranty, etc.

(c)      Government Property – All Contractor-acquired Property and Government-furnished Property
provided on TO shall either be consumed or returned to the government. A final TO Inventory list shall be
required accounting for all TO government property. Contractor shall incorporate information and receipts
obtained from the initial disposition inventory list. For property being returned, the contractor shall include on
the inventory list the following minimum information: part numbers, NSN nomenclature, quantity, and
condition of each item (i.e., Condition A, F, etc.). Paperwork validating official receipt by government is
required for returned items.

4.2.1.3 Contractor’s Manpower Report
Twice in a calendar year, the contractor shall submit a Contractor’s Manpower Report (CDRL A016) to the
COR IAW the TO. Data shall be submitted for all active service task orders. For contracts with multiple active
orders, data shall be a roll-up of all orders under each contract. Data on orders placed by other contracting
activities on SSC LANT contracts shall not be reported. At a minimum, the following information shall be
reported:

a.       Date of Report
b.       Contract number
c.       Contractor Name and Cage Code
d.       Name, Phone and Email Address of Contractor Employee Submitting Report
e.       Associated Task Order(s) Number(s)
f.       Predominant Product Service Code (PSC) reflecting services provided. Definitions of PSCs are
available at http://www.loc.gov/contracts/PSC.html
g.       The Following Information By Locations Shown on Exhibit X
         1.         Estimated number of direct Full Time Equivalents (FTEs) under contract during timeframe
         covered by the report (including applicable Subcontractors).
         2.         Estimated total annual salary of FTEs.


                                                                                                                 20
Notes:
1.       Direct FTEs are those employees and subcontractor employees whose salary is allowable as a direct
cost as defined by FAR 2.101 and DCAAP 7641.90. For fixed price orders, contractors shall apply the same
reasoning to determine direct FTEs.

2.       Estimated annual salary includes all income that would be reported in Block 1 of Internal Revenue
Service (IRS) Form W-2.

3.        Locations are defined as where contractor and sub-contractors perform the work. For temporary
offsite duty of less than six months, location is the employee’s normal permanent worksite. The CONUS
locations on Exhibit X are Metropolitan Statistical Areas (MSAs) as defined in OMB BULLETIN NO. 08 – 01.
Hostile areas are defined as within the countries of Iraq or Afghanistan. Other is defined as not located within
any of the other areas listed.

4.2.1.4      Contractor Census Report
In accordance with Clause 952.225-0005, work performed in Iraq or Afghanistan requires a monthly report
(CDRL A017) that the contractor shall submit to the KO.


4.3          Earned Value Management (EVM)

As determined by the government at task order level, the contractor shall have an Earned Value Management
System (EVMS) that complies with ANSI/EIA-748 in accordance with DFARS 252.242-7001 and 252.242-
7002; however, the government will not formally accept the contractor’s management system (no compliance
review). Any EVM data reporting requirements such as the Contract Performance Report (CPR), Integrated
Master Schedule (IMS), and Contract Funds Status Report (CFSR) shall be specified at the task order level.
The EVMS shall be capable of the following:

4.3.1        Relate resource planning to schedules and technical performance requirements

4.3.2        Integrate technical performance, cost, schedule, and risk management

4.3.3         Provide the integrated management information to plan the timely performance of work, budget
resources, account for costs, and measure actual performance against plans and by Work Breakdown Structure
(WBS) elements in accordance with MIL-HDBK-881A. The contractor shall be able to sort, report, and
account for tasking and expenditures by the WBS elements assigned in the TO. The EVMS shall have the
capability to predict, isolate, and identify variances and the factors causing the variances.


5.0          QUALITY ASSURANCE

5.1            QUALITY ASSURANCE SYSTEM
Upon contract award, the Prime contractor shall have and maintain a quality assurance system that meets
contract requirements and program objectives while ensuring customer satisfaction and quality
products/process. The quality system shall be documented and contain procedures, planning, and all other
documentation and data necessary to provide an efficient and effective quality system based on their internal
auditing system. The quality system shall be made available to the government for review at both a program
and worksite services level during predetermined visits. Existing quality documents that meet the requirements
of this contract may continue to be used. The Contractor shall also require all subcontractors to possess a
quality assurance and control program commensurate with the services and supplies to be provided as
determined by the Prime’s internal audit system. The Government reserves the right to disapprove the
Contractor’s and/or subcontractor’s quality system or portions thereof when the quality system(s) fails to meet
contractual requirements at either the program or worksite services level. The Government reserves the right to
participate in the process improvement elements of the contractor’s quality assurance plan as needed. At a
minimum, the contractor’s quality system shall meet the following key criteria:




                                                                                                             21
         Establish capable processes;
         Monitor and control critical product and process variations;
         Establish mechanisms for feedback of field product performance;
         Implement and effective root-cause analysis and corrective action system; and
         Continuous process improvement.


5.2           QUALITY MANAGEMENT PROCESS COMPLIANCE

At a minimum, due to existing program requirements, the quality system for all services provided under this
contract shall conform to the standards of Software Engineering Institute’s Capability Maturity Model (CMM)
and/or Capability Maturity Model Integration (CMMI) in the relevant profession, trade, or field of endeavor.
The Prime Contractor shall be CMMI SE/SW Level III appraised at their local facility at time of contract award
by an independent Standard CMMI Appraisal Method for Process Improvement (SCAMPI) assessment. The
Contractor shall provide evidence of said certifications upon request. The documented quality system shall be
used to ensure that the end product of each task conforms to contract requirements whether produced by the
Contractor or provided by approved subcontractors or vendors. The quality system shall provide for control
over all phases of the various types of tasks, from initial manning and material ordering to completion of final
tasking, before offering to the government for acceptance as specified in this contract or task orders PWS. All
services shall be rendered according to the documented quality system and directly supervised by individuals
qualified in the relevant profession or trade.

5.3           QUALITY CONTROL

Unless otherwise directed, the Contractor is responsible for all quality control inspections necessary in the
performance of the various tasks as assigned and identified by the respective WBS, POA&M or procedural
quality system document. The Government reserves the right to perform any inspections deemed necessary to
assure that the Contractor provided services, documents, and material meet the prescribed requirements and to
reject any or all services, documents, and material in a category when nonconformance is established.

5.4           QUALITY MANAGEMENT DOCUMENTATION

In support of the contract’s Quality Assurance Surveillance Plan (QASP), and Contractor Performance
Assessment Reporting System (CPARS) the contractor shall provide the following documents: Cost and
Schedule Milestone Plan (CDRL A018) submitted 10 days after Task Order award, and Contractor CPARS
Draft Approval Document (CDAD) Report (CDRL A019) submitted monthly.


6.0           DOCUMENTATION AND DELIVERBALES

6.1           CONTRACT DATA REQUIREMENT LISTINGS (CDRLs)

The following CDRL listing identifies the data item deliverables required under this contract and the applicable
section of the PWS for which they are required. Section J includes the DD Form 1423s that itemize each CDRL
required under the base contract. The contractor shall establish a practical and cost-effective system for
developing and tracking the required CDRLs generated under each task.


 CDRL #        Description                                                      PWS
                                                                                Reference Paragraph
 A001          Program Management Report -- General                             3.2.1
 A002          Integrated Master Schedule                                       3.2.2
 A003          Software Development Plan (SDP)                                  3.4
 A004          Site Survey Report                                               3.7.1
 A005          Base Electronics System Engineering Plan (BESEP)                 3.7.2.1
 A006          Project Support Agreement (PSA)                                  3.7.2.1
 A007          Engineering Design Plan (EDP)                                    3.7.2.1
 A008          Installation Design Package (IDP)                                3.7.2.1
 A009          SSC ATLANTIC Site/Project Management Plan                        3.7.3.5
                                                                                                             22
 CDRL #       Description                                                       PWS
                                                                                Reference Paragraph
 A010         Installation status reports                                       3.7.3.11
 A011         As-Built drawings                                                 3.7.3.12
 A012         Installation Plan                                                 3.7.3.13
 A013         Recommended support equipment, progress and any other             3.7.3.13
              reports
 A014         Task Order/Contract Status Reports                                4.2.1.1
 A015         Task Order Closeout Reports                                       4,2,1,2
 A016         Contractor’s Manpower Report                                      4.2.1.3
 A017         Contractor Census Report                                          4.3.1.4
 A018         Cost and Schedule Milestone Plan                                  5.4
 A019         Contractor CPARS Draft Approval Document (CDAD)                   5.4
              Report
 A020         OCONUS Deployment Reports                                         9.2
 A021         Small Business Participation Goals Report                         12.0
 A022         CMMI Project                                                      3.2.3
 A023         Systems Engineering Documentation                                 3.3
 A024         Assessment Reports                                                3.6.5
 A025         System Integration Design                                         3.7.2
 A026         System Test Plan                                                  3.7.3
 A027         System Integration Plan                                           3.7.4
 A028         System Delivery/Deployment Plan                                   3.7.5
 A029         Test and Evaluation Documentation                                 3.8.1

6.2          ELECTRONIC FORMAT

Under routine circumstances, the deliverables shall be provided electronically by email; hard copies are only
required if requested by the government. To ensure information compatibility, the contractor shall guarantee all
deliverables (i.e., CDRLs), data, correspondence, and etc., are provided in a format approved by the receiving
government representative. All data shall be provided in an editable format compatible with SSC LANT
corporate standard software configuration as specified below. Contractor shall conform to SSC LANT
corporate standards within 30 days of contract award unless otherwise specified. If the source file was created
with a file format not specified below, the original source files shall be provided as well.


              Deliverable                                Software/Formats to be used
 a.           Word Processing                            Microsoft Word
 b.           Technical Publishing                       PageMaker/Interleaf/SGML/
                                                         MSPublisher
 c.           Spreadsheet/Graphics                       Microsoft Excel
 d.           Presentations                              Microsoft PowerPoint
 e.           2-D Drawings/ Graphics/Schematics          Vector (CGM/SVG)
              (new data products)
 f.           2-D Drawings/ Graphics/Schematics          Raster (CALS Type I,
              (existing data products)                   TIFF/BMP, JPEG, PNG)
 g.           Scheduling                                 Microsoft Project
 h.           Computer Aid Design (CAD) Drawings         AutoCAD/Visio
 i.           Geographic Information System (GIS)        ArcInfo/ArcView

NOTE: All software versions shall be compatible to those currently being used by the Government.




                                                                                                             23
6.3          INFORMATION SYSTEM

6.3.1        Electronic Communication
The contractor shall have broadband Internet connectivity and an industry standard email system for
communication with the government. The contractor shall be capable of Public Key Infrastructure client side
authentication to DOD private web servers. Unless otherwise specified, all key personnel on contract shall be
accessible by email through individual accounts during all working hours.

6.3.2         Information Security
The contractor shall provide adequate security for all unclassified DoD information passing through non-DoD
information system including all subcontractor information systems utilized on contract. Unclassified DoD
information shall only be disseminated within the scope of assigned duties and with a clear expectation that
confidentiality will be preserved. Examples of such information include the following: non-public information
provided to the contractor, information developed during the course of the contract, and privileged contract
information (e.g., program schedules, contract-related tracking).

6.3.2.1      Safeguards
The contractor shall protect government information and shall provide compliance documentation validating
they are meeting this requirement. The contractor and all utilized subcontractors shall abide by the following
safeguards:

6.3.2.1.1     Do not process DoD information on public computers (e.g., those available for use by the general
public in kiosks or hotel business centers) or computers that do not have access control.

6.3.2.1.2    Protect information by at least one physical or electronic barrier (e.g., locked container or room,
login and password) when not under direct individual control.

6.3.2.1.3    Sanitize media (e.g., overwrite) before external release or disposal.

6.3.2.1.4      Encrypt all information that has been identified as controlled unclassified information (CUI) when
it is stored on mobile computing devices such as laptops and personal digital assistants, or removable storage
media such as thumb drives and compact disks, using the best available encryption technology.

6.3.2.1.5  Limit information transfer to subcontractors or teaming partners with a need to know and a
commitment to at least the same level of protection.

6.3.2.1.6     Transmit e-mail, text messages, and similar communications using technology and processes that
provide the best level of privacy available, given facilities, conditions, and environment. Examples of
recommended technologies or processes include closed networks, virtual private networks, public key-enabled
encryption, and Transport Layer Security (TLS). Encrypt organizational wireless connections and use
encrypted wireless connection where available when traveling. If encrypted wireless is not available, encrypt
application files (e.g., spreadsheet and word processing files), using at least application-provided password
protection level encryption.

6.3.2.1.7     Transmit voice and fax transmissions only when there is a reasonable assurance that access is
limited to authorized recipients.

6.3.2.1.8      Do not post DoD information to Web site pages that are publicly available or have access limited
only by domain or Internet protocol restriction. Such information may be posted to Web site pages that control
access by user identification or password, user certificates, or other technical means and provide protection via
use of TLS or other equivalent technologies. Access control may be provided by the intranet (vice the Web site
itself or the application it hosts).

6.3.2.1.9    Provide protection against computer network intrusions and data exfiltration, minimally including
the following:

(1) Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.



                                                                                                                 24
(2) Monitoring and control of inbound and outbound network traffic as appropriate (e.g., at the external
boundary, sub-networks, individual hosts) including blocking unauthorized ingress, egress, and exfiltration
through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-
based security services.

(3) Prompt application of security-relevant software patches, service packs, and hot fixes.

6.3.2.1.10 As applicable, comply with other current Federal and DoD information protection and reporting
requirements for specified categories of information (e.g., medical, critical program information (CPI),
personally identifiable information, export controlled).

6.3.2.1.11 Report loss or unauthorized disclosure of information in accordance with contract or agreement
requirements and mechanisms.

6.3.2.2      Compliance
The contractor shall include in their quality processes procedures that are compliant with information security
requirements.


7.0           SECURITY

        Document Number                    Title
  a.    DoD 5220.22-M                      DoD Manual – National Industry Security Program Operating
                                           Manual (NISPOM)
  b.    DoDD 5220.22                       DoD Directive – National Industrial Security Program
  c.    DoD 5200.2-R                       DoD Regulation – Personnel Security Program
  d.    DoDD 8500.1                        DoD Directive – Information Assurance
  e.    DoDI 8500.2                        DoD Instruction – Information Assurance (IA) Implementation
  f.    SECNAVINST 5510.30                 DoN Regulation – Personnel Security Program

7.1           ORGANIZATION

The classification will be defined in the task order. If classified the following applies:

In addition to meeting the security requirements in contract clause “Security Requirements”, the contractor shall
have an operational security program in strict compliance with the National Industrial Security Program Operating
Manual (DoD 5220.22-M) and SSC LANT security directives at time of award. Clearance is required to access
and handle classified and personal personnel material, attend program meetings, and/or work within restricted
areas unescorted. Cleared personnel reduce impact to the facility by eliminating shutdown of classified
operations in the affected spaces and by eliminating the requirement for site personnel to escort the Contractor
personnel. In some cases, depending upon approval by the Government base or facility commander, work
performed in secure spaces may not require personnel with a security clearance.

7.2           FACILITY CLEARANCE

The contractor shall have at the time of Contract Award and prior to commencement of classified work, a Top
Secret (TS) facility clearance with SCI access as determined by the task order.

7.3           PERSONNEL

The Contractor shall conform to the provisions of DOD 5220.22M, SECNAVINST 5510.30, and the Privacy
Act of 1974. The Contractor shall employ personnel that possess and can maintain appropriate security
clearances at the appropriate level(s). At a minimum, the contractor shall validate that the background
information provided by their employees is correct. Cost to meet these security requirements is not directly
chargeable to task order.

The majority of personnel associated with this contract shall possess a Top Secret (TS) clearance. Some of the
individual task orders issued against this contract shall require personnel having higher clearance levels such as
TS with SSBI. At the Government’s request, on a case-by case basis, TS clearances that consist of a Single
Scope Background Investigation (SSBI) shall be eligible for access to Sensitive Compartmented Information
                                                                                                                25
(SCI). These programs/tasks include, as a minimum, contractor personnel having the appropriate clearances
required for access to classified data as required. Prior to starting work on the task, contractor personnel shall
have the required clearance granted by the Defense Industrial Security Clearance Office (DISCO) and shall
comply with IT access authorization requirements. In addition, contractor personnel shall possess the
appropriate IT level of access for the respective task and position assignment as required by DoDD 8500.1,
Information Assurance and DoDI 8500.2, Information Assurance (IA) Implementation. Any future revision to
the respective directive and instruction shall be applied to the TO level as required. Contractor personnel shall
handle and safeguard any unclassified but sensitive and classified information in accordance with appropriate
Department of Defense security regulations. Any security violation shall be reported immediately to the
respective Government Project Manager. Foreign national employees employed in their home countries shall
meet equivalent host nation security requirements.

7.3.1        Control of Contractor Personnel

7.3.1.1      Site Security. The contractor shall comply with site security regulations. All persons engaged in
work while on Government property shall be subject to inspection of their vehicles at any time by the
Government, and shall report any known or suspected security violations to the Security Department at that
location. Individuals supporting these efforts shall comply with the latest security regulations applicable to the
government facility installation.

7.3.1.2       Accessing IT Systems. If contractor personnel require access to any Navy IT system or resource
at SSC LANT (directly or indirectly), the contractor personnel assigned to the contract shall be required to
obtain a Common Access Card (CAC) with Public Key Infrastructure (PKI) for access to Department of
Defense facilities and websites. In addition, a hardware solution and software (e.g., ActiveGold) is required to
securely read the card via a personal computer. Prior to receipt of a CAC, all contractor personnel shall be
required to complete the mandatory annual IA training and submit a signed System Authorization Access
Request Navy (SAAR-N) form to the contract’s specified Contracting Officer’s Representative (COR).

7.3.1.3       Accessing Navy Enterprise Resources Planning (ERP) Management System. Contractor
personnel assigned to perform work under this contract may require access to Navy Enterprise Resource
Planning (Navy ERP) System. Prior to accessing any Navy ERP System, contractor personnel shall contact the
applicable NMCI Assistant Customer Technical Representative (ACTR) and obtain an NMCI account. ACTRs
can be found on the NMCI Homeport website at: https://nmcicustomerreporting/CTR_Lookup/index.asp Once
an NMCI account has been established, the contractor shall submit a request for Navy ERP access and the role
required via the Contracting Officers Representative, Delivery Order Contractor Officer Representative or Task
Order Manager (COR/DOCOR/TOM) to the Competency Role Mapping POC. The COR/TOM will validate
the need for access, ensure all prerequisites are completed, and with the assistance of the Role Mapping POC,
identify the Computer Based Training requirements needed to perform the role assigned. Items to have been
completed prior to requesting a role for Navy ERP include: Systems Authorization Access Request (SAAR-N),
DD Form 2875, Oct 2007, Annual Information Assurance (IA) training certificate and SF85P.

(a)           For this procedure, reference to the COR shall mean the PCO for contracts that do not have a
designated COR. For directions on completing the SF85P, the contractor is instructed to consult with their
company’s Security Manager. In order to maintain access to required systems, the contractor shall ensure
completion of annual IA training, monitor expiration of requisite background investigations, and initiate re-
investigations as required.

(b)            For DoD Information Assurance Awareness training, contractor shall use this site:
http://iase.disa.mil/index2.html. DIRECTIONS (Subject to Change): On the right side under "IA Training:"
select "IA Training Available Online". On the next page select the frame with "DoD Information Assurance
Awareness". When the next page comes up, select "Launch DoD Information Assurance Awareness.

7.3.2         IT Position Categories
In accordance to DoDD 8500.2, SECNAVINST 5510.30, and applicable to unclassified DoD information
systems, a designator shall be assigned to certain individuals that indicates the level of IT access required to
execute the responsibilities of the position based on the potential for an individual assigned to the position to
adversely impact DoD missions or functions. As defined in DoD 5200.2-R and SECNAVINST 5510.30, the IT
Position categories include:
      IT-I (Privileged)
      IT-II (Limited Privileged)

                                                                                                                26
         IT-III (Non-Privileged)

Note: The term IT Position is synonymous with the older term Automated Data Processing (ADP) Position (as
used in DoD 5200.2-R, Appendix 10).

 Investigative requirements for each category vary, depending on the role and whether the individual is a U.S.
civilian contractor or a foreign national. The Contractor PM shall assist the Government Project Manager or
COR in determining the appropriate IT Position Category assignment for all contractor personnel. All required
SSBI, SSBI Periodic Reinvestigation (SSBI-PR), and National Agency Check (NAC) adjudication shall be
performed in accordance with DoDD 8500.2 and SECNAVINST 5510.30. IT Position Categories shall be
determined based on the following criteria:

7.3.2.1       IT-I Level (Privileged) - Positions in which the incumbent is responsible for the planning,
direction, and implementation of a computer security program; major responsibility for the direction, planning
and design of a computer system, including the hardware and software; or, can access a system during the
operation or maintenance in such a way, and with a relatively high risk for causing grave damage, or realize a
significant personal gain. Personnel whose duties meet the criteria for IT-I Position designation require a
favorably adjudicated SSBI or SSBI-PR. The SSBI or SSBI-PR shall be updated a minimum of every 5 years.

7.3.2.2       IT-II Level (Limited Privileged) - Positions in which the incumbent is responsible for the-
direction, planning, design, operation, or maintenance of a computer system, and whose work is technically
reviewed by a higher authority at the IT-II Position level to insure the integrity of the system. Personnel whose
duties meet the criteria for an IT-II Position require a favorably adjudicated NAC.

7.3.2.3       IT-III Level (Non-privileged) - All other positions involved in computer activities. Incumbent in
this position has non-privileged access to one or more DoD information systems/applications or database to
which they are authorized access. Personnel whose duties meet the criteria for an IT-III Position designation
require a favorably adjudicated NAC.

7.3.3        Security Training
The contractor shall educate employees on the procedures for the handling and production of classified material
and documents, and other security measures as described in the PWS in accordance with DoD 5220.22M.

7.3.4          Disclosure of Information
Contractor employees shall not discuss or disclose any information provided to them in the performance of their
duties to parties other than authorized Government and contractor personnel who have a "need to know". Any
information or documentation developed by the contractor under direction of the government shall not be used
for other purposes without the consent of the government KO.

7.3.5          Visit Request
Contractor’s request for visit authorization shall be submitted to the COR and in accordance with DoD Manual
5220.22M, Industrial Security Manual for Safeguarding Classified Information not later than one (1) week prior
to visit. For visitation to SPAWARSYSYCEN Atlantic, Charleston, SC, a visit request shall be forwarded via
Space and Naval Warfare Systems Center Atlantic, P.O. Box 190022, North Charleston, SC 29419-9022, Attn:
Security Office, for certification of need to know by the specified COR/DOCOR. For visitation to all other
govt. locations, Visit Request documentation shall be forwarded directly to the on-site facility’s security office
(to be identified at task order level) via /copy shall be forwarded to the Task Order COR.

7.4           DATA HANDLING AND USER CONTROLS

7.4.1        Data Handling
At a minimum, the contractor shall handle all data received or generated under this contract as For Official Use
Only (FOUO) material. Any classified information received or generated shall be handled in accordance with
the attached DD Form 254 and in shall be in compliance with all applicable PWS references and to other
applicable Government policies and procedures that include DOD/Navy/SPAWAR.

7.4.2        Effective Use of Controls
The contractor shall screen all electronic deliverables or electronically provided information for malicious code
using DoD approved anti-virus software prior to delivery to the Government. The contractor shall utilize
appropriate controls (firewalls, password protection, encryption, digital certificates, etc) at all times to protect

                                                                                                                  27
contract related information processed, stored or transmitted on the contractor’s and Government’s
computers/servers to ensure confidentiality, integrity, availability, authentication and non-repudiation. This
includes ensuring that provisions are in place that will safeguard all aspects of information operations pertaining
to this contract in compliance with all applicable PWS references.


8.0          GOVERNMENT FURNISHED PROPERTY AND INFORMATION

8.1            As defined in FAR Part 45, Government-furnished property (GFP) is property in the possession
of, or directly acquired by, the Government and subsequently furnished to the contractor for performance of a
contract. In accordance to FAR clause 52.245-1, the contractor, shall adhere to the requirements for the
following areas: Property management, Use of Government property, Government-furnished property, Title to
Government property, Contractor plans and systems, System analysis, Contractor Liability, Equitable
adjustment, Contractor inventory disposal, Abandonment of Government property, and Communication.
Specifically, contractors shall not take receipt or transfer custody of any government property without
possessing contractual authority and having the proper paperwork; i.e., Requisition and Invoice/Shipping
Document (DD1149). Unless otherwise directed, disposition of government property shall be in accordance to
local contract clause C-314. GFP shall be identified at task order level.

8.2            As specified in FAR Part 7.105, Government-furnished information (GFI) includes manuals,
drawings, and test data that is provided to contractor for performance of a contract. Certain information (e.g.,
technical specifications, maps, buildings designs, schedules, etc.) shall required addition controls for access and
distribution. Unless otherwise specified, all GFI distribution and inventory shall be tracked. GFI shall be
identified at task order level

8.3           Unless otherwise specified, all government property and information shall be returned to the
designated government representative upon completion of contract or applicable task order. Final GFP/GFI
reporting shall be included in the TO Closeout Report (CDRL A004). All contractor personnel shall be
responsible for following proper GFP/GFI procedures and correcting any problems noted by the government
property administrator. Non-compliance with the contract’s GFP/GFI terms and conditions shall negatively
affect the yearly Contractor Performance Assessment Reporting System (CPARS) rating.

9.0          TRAVEL

9.1           The majority of the work under this contract shall be performed at SSC-LANT (Contractor and
Government facilities). Travel shall be performed in accordance with local contract clause H-350. In support
of various tasks, the contractor shall be prepared and required to travel, at a minimum, to the following
locations:
         1)        Washington, DC ;
         2)        Norfolk, VA ;
         3)        Charleston, SC ; and
         4)        Other federal, state, and local government agencies CONUS and OCONUS as required.

9.2           As specified in each Task order, the contractor shall be required to travel to locations outside the
Continental limits of the United States (OCONUS) both shore and afloat. Commencing one week following
issuance of any Task Order which requires contractor personnel to travel OCONUS (to include Hawaii and
Alaska), the contractor shall submit OCONUS Deployment Reports (CDRL A020). Contractor employees who
deploy to locations that require immunizations shall do so in accordance with Department of Defense
Instruction (DoDI) 6205.4, Department of the Navy (DON), and Space and Naval Warfare Systems Center
Atlantic Instruction (SPAWARSYSCENLANTINST) 12910.1.

9.3        Some travel shall require a Letter of Authorization (LOA). As noted in DFARS PGI 225.7402-3, a
LOA is necessary to enable a contractor employee to process through a deployment processing center; to travel
to, from, and within a theater of operations; and to identify any additional authorizations and privileges. As
required by task order, the contractor shall initiate a LOA for each prospective traveler. The contractor shall use
the Synchronized Predeployment & Operational Tracker (SPOT) web-based system, at
http://www.dod.mil/bta/products/spot.html, to enter and maintain data with respect to traveling/deployed
personnel, and to generate LOAs. When necessary and if in the Government’s interest, the contractor may also
initiate a LOA request to provide an official traveler access to Government facilities and to take advantage of

                                                                                                                28
travel discount rates in accordance with Government contracts and/or agreements. All privileges, services, and
travel rate discount access are subject to availability and vendor acceptance. LOAs shall be signed/approved by
the Contracting/Ordering Officer for the contract/order who is registered in the SPOT system.

9.4       Work to be performed at Specified Mission Destinations, as defined in the latest SSC LANT OCONUS
Deployment Guide (located in website:
https://cne.spawar.navy.mil/portal/page/portal/CNE_CORP_INFO_2/OCONUS%20Deployment%20Guide) , is
subject to all relevant contract clauses, as well as the requirements set forth in the aforementioned guide. The
contractor shall be able to meet all clause and guide requirements 35 days prior to travel within the applicable
specified destinations. When deployment to a Specified Mission Destination is necessary, the contractor shall
be responsible for processing applicable deployment packages for its personnel in accordance with the SSC
LANT OCONUS Deployment Guide. Access to the SSC LANT OCONUS Deployment Guide website will be
provided to the offerors after award.

Reimbursement of Travel Costs will be made as follows:

(a) Contractor Request and Government Approval of Travel

Any travel under this contract must be specifically requested in writing, by the contractor prior to incurring any
travel costs. If this contract is a definite or indefinite delivery contract, then the written Government
authorization will be by task/delivery orders issued by the Ordering Officer or by a modification to an issued
task/delivery order. If this contract is not a definite or indefinite delivery contract, then the written Government
authorization will be by written notice of approval from the Contracting Officer’s Representative (COR). The
request shall include as a minimum, the following:

         (1) Contract number
         (2) Date, time, and place of proposed travel
         (3) Purpose of travel and how it relates to the contract
         (4) Contractor’s estimated cost of travel
         (5) Name(s) of individual(s) traveling and;
         (6) A breakdown of estimated travel and per diem charges.

(b) General

          (1) The costs for travel, subsistence, and lodging shall be reimbursed to the contractor only to the
extent that it is necessary and authorized for performance of the work under this contract. The costs for travel,
subsistence, and lodging shall be reimbursed to the contractor in accordance with the Federal Acquisition
Regulation (FAR) 31.205-46, which is incorporated by reference into this contract. As specified in FAR
31.205-46(a) (2), reimbursement for the costs incurred for lodging, meals and incidental expenses (as defined in
the travel regulations cited subparagraphs (b)(1)(i) through (b)(1)(iii) below) shall be considered to be
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 travel as set forth in the following:

                 (i) Federal Travel Regulation prescribed by the General Services Administration for travel in
the contiguous 48 United States;

                 (ii) Joint Travel Regulation, Volume 2, DoD Civilian Personnel, Appendix A, prescribed by
the Department of Defense for travel in Alaska, Hawaii, The Commonwealth of Puerto Rico, and the territories
and possessions of the United States; or

                  (iii) Standardized Regulations, (Government Civilians, Foreign Areas), Section 925,
“Maximum Travel Per Diem Allowances in Foreign Areas” prescribed by the Department of State, for travel in
areas not covered in the travel regulations cited in subparagraphs (b)(1)(i) and (b)(1)(ii) above.

          (2) Personnel in travel status from and to the contractor’s place of business and designated work site or
vice versa, shall be considered to be performing work under the contract, and contractor shall bill such travel
time at the straight (regular) time rate; however, such billing shall not exceed eight hours per person for any one
person while in travel status during one calendar day.

(c) Per Diem

                                                                                                                 29
         (1) The contractor shall not be paid per diem for contractor personnel who reside in the metropolitan
area in which the tasks are being performed. Per diem shall not be paid on services performed at contractor’s
home facility and at any facility required by the contract, or at any location within a radius of 50 miles from the
contractor’s home facility and any facility required by this contract.

          (2) Costs for subsistence and lodging shall be paid to the contractor only to the extent that overnight
stay is necessary and authorized in writing by the Government for performance of the work under this contract
per paragraph (a). When authorized, per diem shall be paid by the contractor to its employees at a rate not to
exceed the rate specified in the travel regulations cited in FAR 31.205-46(a)(2) and authorized in writing by the
Government. The authorized per diem rate shall be the same as the prevailing locality per diem rate.

          (3) Reimbursement to the contractor for per diem shall be limited to payments to employees not to
exceed the authorized per diem and as authorized in writing by the Government per paragraph (a). Fractional
parts of a day shall be payable on a prorated basis for purposes of billing for per diem charges attributed to
subsistence on days of travel. The departure day from the Permanent Duty Station (PDS) and return day to the
PDS shall be 75% of the applicable per diem rate. The contractor shall retain supporting documentation for per
diem paid to employees as evidence of actual payments, as required by the FAR 52.216-7 “Allowable Cost and
Payment” clause of the contract.

(d) Transportation

         (1) The contractor shall be paid on the basis of actual amounts paid to the extent that such
transportation is necessary for the performance of work under the contract and is authorized in writing by the
Government per paragraph (a).

          (2) The contractor agrees, in the performance of necessary travel, to use the lowest cost mode
commensurate with the requirements of the mission and in accordance with good traffic management principles.
When it is necessary to use air or rail travel, the contractor agrees to use coach, tourist class or similar
accommodations to the extent consistent with the successful and economical accomplishment of the mission for
which the travel is being performed. Documentation must be provided to substantiate non-availability of coach
or tourist if business or first class is proposed to accomplish travel requirements.

         (3) When transportation by privately owned conveyance (POC) is authorized, the contractor shall be
paid on a mileage basis not to exceed the applicable Government transportation rate specified in the travel
regulations cited in FAR 31.205-46(a)(2) and is authorized in writing by the Government per paragraph (a).

         (4) When transportation by privately owned (motor) vehicle (POV) is authorized, required travel of
contractor personnel, that is not commuting travel, may be paid to the extent that it exceeds the normal
commuting mileage of such employee. When an employee’s POV is used for travel between an employee’s
residence or the Permanent Duty Station and one or more alternate work sites within the local area, the
employee shall be paid mileage for the distance that exceeds the employee’s commuting distance.

          (5) When transportation by a rental automobile, other special conveyance or public conveyance is
authorized, the contractor shall be paid the rental and/or hiring charge and operating expenses incurred on
official business (if not included in the rental or hiring charge). When the operating expenses are included in
the rental or hiring charge, there should be a record of those expenses available to submit with the receipt.
Examples of such operating expenses include: hiring charge (bus, streetcar or subway fares), gasoline and oil,
parking, and tunnel tolls.

         (6) Definitions:

(i) “Permanent Duty Station” (PDS) is the location of the employee’s permanent work assignment (i.e., the
building or other place where the employee regularly reports for work.

                  (ii) “Privately Owned Conveyance” (POC) is any transportation mode used for the movement
         of persons from place to place, other than a Government conveyance or common carrier, including a
         conveyance loaned for a charge to, or rented at personal expense by, an employee for transportation
         while on travel when such rental conveyance has not been authorized/approved as a Special
         Conveyance.

                                                                                                                 30
                  (iii) “Privately Owned (Motor) Vehicle (POV)” is any motor vehicle (including an
         automobile, light truck, van or pickup truck) owned by, or on a long-term lease (12 or more months)
         to, an employee or that employee’s dependent for the primary purpose of providing personal
         transportation, that:
                            (a) is self-propelled and licensed to travel on the public highways;
                            (b) is designed to carry passengers or goods; and
                            (c) has four or more wheels or is a motorcycle or moped.

                  (iv) “Special Conveyance” is commercially rented or hired vehicles other than a POC and
         other than those owned or under contract to an agency.

                    (v) “Public Conveyance” is local public transportation (e.g., bus, streetcar, subway, etc) or
         taxicab.

                   (iv) “Residence” is the fixed or permanent domicile of a person that can be reasonably
         justified as a bona fide residence.


EXAMPLE 1: Employee’s one way commuting distance to regular place of work is 7 miles. Employee drives
from residence to an alternate work site, a distance of 18 miles. Upon completion of work, employee returns to
residence, a distance of 18 miles.

        In this case, the employee is entitled to be reimbursed for the distance that exceeds the normal round
trip commuting distance (14 miles). The employee is reimbursed for 22 miles (18 + 18 - 14 = 22).


EXAMPLE 2: Employee’s one way commuting distance to regular place of work is 15 miles. Employee drives
from residence to an alternate work site, a distance of 5 miles. Upon completion of work, employee returns to
residence, a distance of 5 miles.

         In this case, the employee is not entitled to be reimbursed for the travel performed (10 miles), since the
distance traveled is less than the commuting distance (30 miles) to the regular place of work.


EXAMPLE 3: Employee’s one way commuting distance to regular place of work is 15 miles. Employee drives
to regular place of work. Employee is required to travel to an alternate work site, a distance of 30 miles. Upon
completion of work, employee returns to residence, a distance of 15 miles.

        In this case, the employee is entitled to be reimbursed for the distance that exceeds the normal round
trip commuting distance (30 miles). The employee is reimbursed for 30 miles (15 + 30 + 15 - 30 = 30).


EXAMPLE 4: Employee’s one way commuting distance to regular place of work is 12 miles. In the morning
the employee drives to an alternate work site (45 miles). In the afternoon the employee returns to the regular
place of work (67 miles). After completion of work, employee returns to residence, a distance of 12 miles.

        In this case, the employee is entitled to be reimbursed for the distance that exceeds the normal round
trip commuting distance (24 miles). The employee is reimbursed for 100 miles (45 + 67 + 12 - 24 = 100).


EXAMPLE 5: Employee’s one way commuting distance to regular place of work is 35 miles. Employee drives
to the regular place of work (35 miles). Later, the employee drives to alternate work site #1 (50 miles) and then
to alternate work site #2 (25 miles). Employee then drives to residence (10 miles).

       In this case, the employee is entitled to be reimbursed for the distance that exceeds the normal
commuting distance (70 miles). The employee is reimbursed for 50 miles (35 + 50 + 25 + 10 - 70 = 50).




                                                                                                                    31
EXAMPLE 6: Employee’s one way commuting distance to regular place of work is 20 miles. Employee drives
to the regular place of work (20 miles). Later, the employee drives to alternate work site #1 (10 miles) and then
to alternate work site #2 (5 miles). Employee then drives to residence (2 miles).


9.5     The following CENTCOM & Joint Contracting Command – Iraq/Afghanistan (JCC-I/A) Special
Requirements apply to all work to be performed in either Iraq or Afghanistan:


952.222-0001, PROHIBITION AGAINST HUMAN TRAFFICKING, INHUMANE LIVING
CONDITIONS, AND WITHHOLDING OF EMPLOYEE PASSPORTS (AUG 2009)

(a) All contractors (“contractors” refers to both prime contractors and all subcontractors at all tiers) are
reminded of the prohibition contained in Title 18, United States Code, Section 1592, against knowingly
destroying, concealing, removing, confiscating, or possessing any actual or purported passport or other
immigration document, or any other actual or purported government identification document, of another person,
to prevent or restrict or to attempt to prevent or restrict, without lawful authority, the person’s liberty to move or
travel, in order to maintain the labor or services of that person, when the person is or has been a victim of a
severe form of trafficking in persons.

(b) Contractors are also required to comply with the following provisions:

(1) Contractors shall only hold employee passports and other identification documents discussed above for the
shortest period of time reasonable for administrative processing purposes.

(2) Contractors shall provide all employees with a signed copy of their employment contract, in English as well
as the employee’s native language that defines the terms of their employment/compensation.

(3) Contractors shall not utilize unlicensed recruiting firms, or firms that charge illegal recruiting fees.

(4) Contractors shall be required to provide adequate living conditions (sanitation, health, safety, living space)
for their employees. Fifty square feet is the minimum acceptable square footage of personal living space per
employee. Upon contractor’s written request, contracting officers may grant a waiver in writing in cases where
the existing square footage is within 20% of the minimum, and the overall conditions are determined by the
contracting officer to be acceptable. A copy of the waiver approval shall be maintained at the respective life
support area.

(5) Contractors shall incorporate checks of life support areas to ensure compliance with the requirements of this
Trafficking in Persons Prohibition into their Quality Control program, which will be reviewed within the
Government’s Quality Assurance process.

(6) Contractors shall comply with international laws regarding transit/exit/entry procedures, and the
requirements for work visas. Contractors shall follow all Host Country entry and exit requirements, including
requirements for visas and work permits.

(c) Contractors have an affirmative duty to advise the Contracting Officer if they learn of their employees
violating the human trafficking and inhumane living conditions provisions contained herein. Contractors are
advised that contracting officers and/or their representatives will conduct random checks to ensure contractors
and subcontractors at all tiers are adhering to the law on human trafficking, humane living conditions and
withholding of passports.

(d) The contractor agrees to incorporate the substance of this clause, including this paragraph, in all
subcontracts under his contract.
.
                                                     - End -




                                                                                                                   32
952.223-0001, REPORTING KIDNAPPINGS, SERIOUS INJURIES AND DEATHS (MAR 2009)

Contractors shall notify the Contracting Officer, as soon as practicable, whenever employee kidnappings,
serious injuries or deaths occur.

Report the following information:
Contract Number:
Contract Description & Location:
Company Name:
Reporting party -
         Name:
         Phone number:
         e-mail address:
Victim -
         Name:
         Gender (Male/Female):
         Age:
         Nationality:
         Country of permanent residence:
Incident -
         Description
         Location
         Date and time
Other Pertinent Information:

                                                      - End -


952.225-0001, ARMING REQUIREMENTS AND PROCEDURES FOR PERSONAL SECURITY
SERVICES CONTRACTORS AND FOR REQUESTS FOR PERSONAL PROTECTION (FEB 2010)

(a) General. Contractor and its subcontractors at all tiers that require arming under this contract agree to obey
all laws, regulations, orders, and directives applicable to the use of private security personnel in Iraq and
Afghanistan, including U.S. CENTCOM, United States Forces – Iraq (USF-I) and United States Forces –
Afghanistan (USFOR-A) Commander orders, instructions and directives. Contractors will ensure that all
employees, including employees at any tier of subcontracting relationships, who will seek individual
authorization to be armed under the provisions of this contract (requests for blanket authorization for groups or
organizations will not be approved), comply with the contents of this clause and with the requirements set forth
in the following:

(1) DODI 3020.50, Private Security Contractors (PSCs) Operating in Contingency Operations;
(2) DODI 3020.41, Program Management for Acquisition and Operational Contract Support in Contingency
Operations;
(3) DFARS 252.225-7040, Contractor Personnel Supporting a Force Deployed Outside the United States;
(4) Class Deviation 2007-O0010, Contractor Personnel in the United States Central Command Area of
Responsibility
(5) USFOR-A, FRAGO 09-206, Outlines Management of Armed Contractors and Private Security Companies
Operating in the Combined Joint Operating Area - Afghanistan (CJOA-A)
(6) USF-I OPORD 10-01, Annex C, Appendix 13
(7) U.S. CENTCOM Message, USCENTCOM Policy and Delegation of Authority for Personal Protection and
Contract Security Service Arming of DoD Civilian Personnel and Contractors for Iraq and Afghanistan, dated
23 Dec 2005
(8) U.S. CENTCOM Message, Modification to USCENTCOM Civilian and Contractor Arming Policy and
Delegation of Authority for Iraq and Afghanistan, dated 07 Nov 2006
(9) U.S. CENTCOM Message, Modification 3 to USCENTCOM Civilian and Contractor Arming Policy and
Delegation of Authority in Iraq and Afghanistan, dated 09 Jun 2009

(b) Required Government Documentation. An O-6 or GS-15 (or above) from the unit requesting the
contractor security shall provide a description of the following to the arming approval authority via the

                                                                                                               33
contracting officer representative (COR) in sponsoring each individual request for arming (under paragraph (c)
below:

(1) The specific location where the PSC employee will operate;
(2) The persons and/or property that require protection;
(3) The anticipated threat;
(4) The requested weapon type(s), including serial number when possible;
(5) The reason current security/police forces are unable to provide adequate protection; and
(6) Verification, under paragraph (e) below, that background checks have been conducted and that no records
were found of convictions or other acts that should be known to the arming authority.

(c) Required Contractor Documentation. Contractors and their subcontractors at all tiers that require arming
approval shall provide to the arming approval authority via the COR consistent documentation (signed and
dated by the employee and employer as applicable) for each of their employees who will seek authorization to
be armed under the contract as follows:

(1) Weapons Qualification/Familiarization. All employees must meet the weapons qualification requirements
on the requested weapon(s) established by any DoD or other U.S. government agency, Law of Armed Conflict
(LOAC); Rules for the Use of Force (RUF), as defined in the U.S. CENTCOM Policy, dated 23 December
2005; and distinction between the above-prescribed RUF and the Rules of Engagement (ROE), which are
applicable only to military forces.

(2) Completed DD Form 2760 (or equivalent documentation) for each armed employee, indicating that the
employee is not otherwise prohibited under U.S. law from possessing the required weapon or ammunition.

(3) Written acknowledgement by the individual of the fulfillment of training responsibilities and the conditions
for the authorization to carry firearms. This document includes the acknowledgement of the distinctions
between the ROE applicable to military forces and RUF that control the use of weapons by DoD civilians, DoD
contractors and PSCs.

(4) Written acknowledgement signed by both the armed employee and by a representative of the employing
company that use of weapons could subject both the individual and company to U.S. and host nation
prosecution and civil liability.

(5) A copy of the contract between the contractor’s company and the U.S. Government that verifies the
individual’s employment and addresses the need to be armed.

(6) One (1) copy of a business license from the Iraqi or Afghani Ministry of Trade or Interior;

(7) One (1) copy of a license to operate as a PSC (or a temporary operating license) from the Ministry of
Interior;

(d) The contractor will submit to the COR a communications plan that, at a minimum, sets forth the following:

(1) The contractor’s method of notifying military forces and requesting assistance where hostilities arise,
combat action is needed or serious incidents have been observed;

(2) How relevant threat information will be shared between contractor security personnel and U.S. military
forces; and

(3) How the contractor will coordinate transportation with appropriate military authorities.

(e) Prior to requesting arming approval, the contractor will submit to the COR an acceptable plan for
accomplishing background checks on all contractor and subcontractor employees who will be armed under the
contract. The contractor shall, at a minimum, perform the following (which will be specifically addressed in its
plan and which will be documented and furnished to the COR upon completion):

(1) Use one or more of the following sources when conducting the background checks: Interpol, FBI, Country
of Origin Criminal Records, Country of Origin U.S. Embassy Information Request, CIA records, and/or any
other records available;

                                                                                                              34
(2) Verify with USF-I or USFOR-A, as applicable, that no employee has been barred by any commander within
Iraq or Afghanistan; and

(3) All local nationals and third country nationals will voluntarily submit to full biometric enrollment in
accordance with theater biometric policies within 60 days of their arming request. While biometric collection
and screening is voluntary, CORs will immediately notify the arming approval authority of any individuals who
do not meet this requirement and any arming authorization will be revoked until all requirements are met.

(f) Penalties for Non-Compliance. Failure of contractor or subcontractor employee(s) to comply with the
laws, regulations, orders, and rules (including those specified herein) governing the use of force, training,
arming authorization, and incident reporting requirements may result in the revocation of weapons authorization
for such employee(s). Where appropriate, such failure may also result in the total revocation of weapons
authorization for the contractor (or subcontractor) and sanctions under the contract, including termination.

(g) Criminal and Civil Liability. Arming of contractor or subcontractor employees under this contract may
subject the contractor, its subcontractors, and persons employed by the same, to the civil and criminal
jurisdiction of the U.S. and Host Nation. “Host Nation” refers to the nation or nations where services under this
contract are performed.

(h) Lapses in Training or Authorization. Failure to successfully retrain an employee who has been properly
authorized to be armed under this contract within twelve (12) months of the last training date will constitute a
lapse in the employee’s authorization to possess and carry the weapon. All unauthorized employees will
immediately surrender their weapon and authorization letter to the contractor and will remain unarmed until
such time as they are retrained and newly approved by the arming authority. Additionally, the arming
authority’s authorization letter is valid for a maximum of twelve (12) months from the date of the prior letter
(unless authorization is earlier invalidated by a lapse in training).

(i) Authorized Weapon & Ammunition Types. Unless DCDRUSCENTCOM (or a designee) expressly
provides otherwise, all arming requests and authorizations for contractor or subcontractor employees under this
contract shall be limited to U.S. Government-approved weapons and ammunition. Notwithstanding Host
Nation laws or regulations that would allow use of heavier weapons by contract security/PSC, all DoD security
service / PSC contractors must have weapons approved by DCDRUSCENTCOM (or a designee) before use.
This restriction applies to all weapons in the possession of contractor employees, even if such weapons are
required for personal protection. The following weapons and ammunition are currently authorized by the U.S.
Government for use in Iraq and Afghanistan:

(1) The M9, M4, M16, or equivalent (e.g. .45 CAL, AK-47).
(2) The M9 or equivalent sidearm will be the standard personal protection weapon unless other weapons are
specifically requested and approved.
(3) U.S. government Ball ammunition is the standard approved ammunition.

(j) Requirements for Individual Weapons Possession. All employees of the contractor and its subcontractors
at all tiers who are authorized to be armed under this contract must:

(1) Possess only those U.S. Government-approved weapons and ammunition for which they are qualified under
the training requirements of section (c) and subsequently authorized to carry;
(2) Carry weapons only when on duty or at a specific post (according to their authorization);
(3) Not conceal any weapons, unless specifically authorized;
(4) Carry proof of authorization to be armed. Employees not possessing such proof will be deemed
unauthorized and must surrender their weapon to their employer; and
(5) IAW USCENTCOM G.O. #1, consumption of alcohol in Iraq or Afghanistan is prohibited. In the event of
a suspension or an exception to G.O. #1, employees shall not consume any alcoholic beverage while armed or
within eight (8) hours of the next work period when they will be armed. There are no circumstances under
which a person will be authorized to consume any alcoholic beverage when armed for personal protection.




                                                                                                               35
(k) Weapons/Equipment Restrictions and Responsibilities. Unless otherwise provided, the U.S. Government
will not provide any weapons or ammunition to contractors, their subcontractors, or any employees of the same.
The Contractor will provide all weapons and ammunition to those employees that will be armed under the
contract. The contractor and its subcontractors at all tiers will also provide interceptor body armor, ballistic
helmets, and the Nuclear, Biological, and Chemical (NBC) protective masks to those employees that require
such equipment in the performance of their duties.

(l) Rules for the Use of Force (RUF). In addition to the RUF and ROE training referenced in paragraph (c),
the contractor and its subcontractors at all tiers will monitor and report all activities of its armed employees that
may violate the RUF and/or otherwise trigger reporting requirements as serious incidents. Prompt reporting
demonstrates a desire by the contractor and its subcontractors to minimize the impact of any violations and,
therefore, will be given favorable consideration. Violations of the RUF include, though are not limited to:

(1) Taking a direct part in hostilities or combat actions, other than to exercise self-defense;
(2) Failing to cooperate with Coalition and Host Nation forces;
(3) Using deadly force, other than in self-defense where there is a reasonable belief of imminent risk of death
or serious bodily harm;
(4) Failing to use a graduated force approach;
(5) Failing to treat the local civilians with humanity or respect; and
(6) Detaining local civilians, other than in self-defense or as reflected in the contract terms.

(m) Retention and Review of Records. The Contractor and all subcontractors at all tiers shall maintain records
on weapons training, LOAC, RUF and the screening of employees for at least six (6) months following the
expiration (or termination) of the contract. The Contractor and its subcontractors at all tiers shall make these
records available to the Contracting Officer or designated representative, at no additional cost to the
government, within 72 hours of a request.

(n) Contractor Vehicles. Vehicles used by contractor and subcontractor personnel in the course of their
security duties shall not be painted or marked to resemble U.S./Coalition or host nation military and police force
vehicles.

(o) Quarterly Reporting. The prime contractor will report quarterly (i.e. NLT 1 January, 1 April, 1 July and 1
October for each quarter of the calendar year) to the Contracting Officer responsible for this contract, and any
other organization designated by the Contracting Officer, the following information under this contract:

(1) The total number of armed civilians and contractors;
(2) The names and contact information of its subcontractors at all tiers; and
(3) A general assessment of the threat conditions, adequacy of force numbers, and any problems that might
require a change to force levels. Note: this information is in addition to the information the contractor promises
to immediately provide under the communications plan referenced at paragraph (d).

                                                        (End)


952.225-0002, ARMED PERSONNEL INCIDENT REPORTS (JAN 2010)

(a) All contractors and subcontractors in the United States Forces-Iraq (USF-I) or United States Forces-
Afghanistan (USFOR-A) theater of operations shall comply with and shall ensure that their personnel
supporting USF-I or USFOR-A forces are familiar with and comply with all applicable orders, directives, and
instructions issued by the respective USF-I or USFOR-A Commanders relating to force protection and safety.

(b) IRAQ: Contractors shall provide all incidents and use of weapons firing incidents to the USF-I Contractor
Operations Cell (CONOC) as soon as practical, based upon the situation, and submit a written report to
CONOC within 4 hours. The initial report shall include the name of the company, location of the incident, time
when the incident occurred, a brief description of the events leading up to the incident, and a company point of
contact. A follow-up, comprehensive written report shall be provided to the CONOC within 96 hours of the
incident. Reports shall be submitted to CONOC at: mncic3conoc@iraq.centcom.mil; DSN 318-435-2369;
Iraqna 0044 203 286 9851 or 0044 203 239 5894; or Skype: MNCICONOC.


                                                                                                                  36
(c) AFGHANISTAN: Contractors shall immediately report all incidents and use of weapons through their
Contracting Officers Representative (CORs) who will notify the Contracting Officer. Contracting Officers are
responsible to notify the PARC-A Chief of Operations and the JOC @ USFOR-A (JOC SHIFT DIRECTOR,
DSN: 318-237-1761) Information should include: the name of the company, where the incident occurred, time
when the incident occurred, a brief description of the events leading up to the incident, and a point of contact for
the company. The PARC-A Chief of Operations in coordination with the JOC will issue guidance for further
reporting requirements.

(d) Contractors shall provide first aid and request MEDEVAC of injured persons, and remain available for U.S.
or Coalition response forces, based upon the situation. In the event contractor personnel are detained by U.S. or
Coalition Forces, prolonged detention due to lack of proper identification can be alleviated by contractor
personnel possessing on their person information that includes the contractor’s name, the contract number, a
contractor management POC, and the phone number of the CONOC/JOC Watch.

                                                       (End)


952.225-0003, FITNESS FOR DUTY AND MEDICAL/DENTAL CARE LIMITATIONS (APR 2010)

(a) The contractor shall perform the requirements of this contract notwithstanding the fitness for duty of
deployed employees, the provisions for care offered under this section, and redeployment of individuals
determined to be unfit. Contractor personnel who deploy for multiple tours, for more than 12 months total must
be re-evaluated for fitness to deploy. An examination will remain valid for 15 months from the date of the
physical. The contractor bears the responsibility for ensuring all employees are aware of the conditions and
medical treatment available at the performance location. The contractor shall include this information and
requirement in all subcontracts with performance in the theater of operations.

(b) The contractor shall not deploy an individual with any of the following conditions unless approved by the
appropriate CENTCOM Service Component (ie. ARCENT, AFCENT, etc.) Surgeon: Conditions which prevent
the wear of personal protective equipment, including protective mask, ballistic helmet, body armor, and
chemical/biological protective garments; conditions which prohibit required theater immunizations or
medications; conditions or current medical treatment or medications that contraindicate or preclude the use of
chemical and biological protective’s and antidotes; diabetes mellitus, Type I or II, on pharmacological therapy;
symptomatic coronary artery disease, or with myocardial infarction within one year prior to deployment, or
within six months of coronary artery bypass graft, coronary artery angioplasty, or stenting; morbid obesity
(BMI >/= 40); dysrhythmias or arrhythmias, either symptomatic or requiring medical or electrophysiological
control; uncontrolled hypertension, current heart failure, or automatic implantable defibrillator; therapeutic
anticoagulation; malignancy, newly diagnosed or under current treatment, or recently diagnosed/treated and
requiring frequent subspecialist surveillance, examination, and/or laboratory testing; dental or oral conditions
requiring or likely to require urgent dental care within six months’ time, active orthodontic care, conditions
requiring prosthodontic care, conditions with immediate restorative dentistry needs, conditions with a current
requirement for oral-maxillofacial surgery; new onset (< 1 year) seizure disorder, or seizure within one year
prior to deployment; history of heat stroke; Meniere’s Disease or other vertiginous/motion sickness disorder,
unless well controlled on medications available in theater; recurrent syncope, ataxias, new diagnosis (< 1year)
of mood disorder, thought disorder, anxiety, somatoform, or dissociative disorder, or personality disorder with
mood or thought manifestations; unrepaired hernia; tracheostomy or aphonia; renalithiasis, current; active
tuberculosis; pregnancy; unclosed surgical defect, such as external fixeter placement; requirement for medical
devices using AC power; HIV antibody positivity; psychotic and bipolar disorders. (Reference: Mod 10 to
USCENTCOM Individual Protection and Individual/Unit Deployment Policy, Annex Q to USF-I OPORD 10-
01, FRAGO 897 to CJTF-82 OPORD 07-03, PPG-Tab A: Amplification of the Minimal Standards of Fitness
for Deployment to the CENTCOM AOR).

(c) In accordance with military directives (DoDI 3020.41, DoDI 6000.11, CFC FRAGO 09-1038, DoD PGI
225.74), resuscitative care, stabilization, hospitalization at Level III (emergency) military treatment facilities
and assistance with patient movement in emergencies where loss of life, limb or eyesight could occur will be
provided. Hospitalization will be limited to emergency stabilization and short-term medical treatment with an
emphasis on return to duty or placement in the patient movement system. Subject to availability at the time of
need, a medical treatment facility may provide reimbursable treatment for emergency medical or dental care
such as broken bones, lacerations, broken teeth or lost fillings.


                                                                                                                 37
(d) Routine and primary medical care is not authorized. Pharmaceutical services are not authorized for routine
or known, routine prescription drug needs of the individual. Routine dental care, examinations and cleanings
are not authorized.

(e) Notwithstanding any other provision of the contract, the contractor shall be liable for any and all medically-
related services or transportation rendered. In accordance with OUSD(C) Memorandum dated 4 June 2008, the
following reimbursement rates will be charged for services at all DoD deployed medical facilities. These rates
are in effect until changed by DoD direction.

(1) Inpatient daily rate: $2,041.00. Date of discharge is not billed unless the patient is admitted to the hospital
and discharged the same day.

(2) Outpatient visit rate: $195.00. This includes diagnostic imaging, laboratory, pathology, and pharmacy
provided at the medical facility.

                                                        (End)


952.225-0004, COMPLIANCE WITH LAWS AND REGULATIONS (JAN 2010)

(a) The Contractor shall comply with, and shall ensure that its employees and its subcontractors and their
employees, at all tiers, are aware of and obey all U.S. and Host Nation laws, Federal or DoD regulations, and
Central Command orders and directives applicable to personnel in Iraq and Afghanistan, including but not
limited to USCENTCOM, Multi-National Force and Multi-National Corps operations and fragmentary orders,
instructions, policies and directives.

(b) Contractor employees shall particularly note all laws, regulations, policies, and orders restricting authority
to carry firearms, rules for the use of force, and prohibiting sexual or aggravated assault. Contractor employees
are subject to General Orders Number 1, as modified from time to time, including without limitation, their
prohibition on privately owned firearms, alcohol, drugs, war souvenirs, pornography and photographing
detainees, human casualties or military security measures.

(c) Contractor employees may be ordered removed from secure military installations or the theater of
operations by order of the senior military commander of the battle space for acts that disrupt good order and
discipline or violate applicable laws, regulations, orders, instructions, policies, or directives. Contractors shall
immediately comply with any such order to remove its contractor employee.

(d) Contractor employees performing in the USCENTCOM Area of Responsibility (AOR) may be subject to
the jurisdiction of overlapping criminal codes, including, but not limited to, the Military Extraterritorial
Jurisdiction Act (18 U.S.C. Sec. 3261, et al) (MEJA), the Uniform Code of Military Justice (10 U.S.C. Sec. 801,
et al)(UCMJ), and the laws of the Host Nation. Non-US citizens may also be subject to the laws of their home
country while performing in the USCENTCOM AOR. Contractor employee status in these overlapping
criminal jurisdictions may be modified from time to time by the United States, the Host Nation, or by applicable
status of forces agreements.

(e) Under MEJA, a person who engages in felony misconduct outside the United States while employed by or
accompanying the Armed Forces is subject to arrest, removal and prosecution in United States federal courts.
Under the UCMJ, a person serving with or accompanying the Armed Forces in the field during a declared war
or contingency operation may be disciplined for a criminal offense, including by referral of charges to a General
Court Martial. Contractor employees may be ordered into confinement or placed under conditions that restrict
movement within the AOR or administratively attached to a military command pending resolution of a criminal
investigation.

(f) Contractors shall immediately notify military law enforcement and the Contracting Officer if they suspect
an employee has committed an offense. Contractors shall take any and all reasonable and necessary measures
to secure the presence of an employee suspected of a serious felony offense. Contractors shall not knowingly
facilitate the departure of an employee suspected of a serious felony offense or violating the Rules for the Use
of Force to depart Iraq or Afghanistan without approval from the senior U.S. commander in the country.

                                                        (End)

                                                                                                                   38
952.225-0005, MONTHLY CONTRACTOR CENSUS REPORTING (MAR 2009)

Contractor shall provide monthly employee census information to the Contracting
Officer, by province, for this contract. Information shall be submitted either
electronically or by hard-copy. Information shall be current as of the 25 th day of each
month and received by the Contracting Officer no later than the first day of the following
month. The following information shall be provided for each province in which work
was performed:

(1) The total number (prime and subcontractors at all tiers) employees.
(2) The total number (prime and subcontractors at all tiers) of U.S. citizens.
(3) The total number (prime and subcontractors at all tiers) of local nationals (LN).
(4) The total number (prime and subcontractors at all tiers) of third-country nationals
(TCN).
(5) Name of province in which the work was performed.
(6) The names of all company employees who enter and update employee data in the
Synchronized Predeployment & Operational Tracker (SPOT) IAW DFARS
252.225-7040 or DFARS DOD class deviation 2007-O0010.

                                                      - End -


952.225-0006, CONTRACT DELIVERY REQUIREMENTS (MAR 2009)

(a) REQUIRED DELIVERY DATE:

(b) CONTRACTOR DELIVERY LOCATION:

(c) POINT-OF-CONTACT RESPONSIBLE FOR INSPECTION & ACCEPTANCE:
Name:
Phone No.: email:

(d) FINAL DELIVERY DESTINATION:

(e) POINT-OF-CONTACT AT FINAL DESTINATION:
Name:
Phone No.: email:

(f) REQUIRING ACTIVITY:

                                                     - End –




952.225-0007, MANDATORY SHIPPING INSTRUCTIONS (IRAQ) (FEB 2010)

(a) United States Forces Iraq, Deputy Commanding General Advisory and Training (USF-I DCG A&T), is
required to track supplies and materiel shipped into Iraq. Prompt notification of shipment movements and
compliance with information requirements will assist in providing advance notice to the point of entry for all
inbound shipments.

(b) The “Customs Levy Exemption Form” will be reviewed by a Government of Iraq Representative. If the
shipment qualified for a levy exemption, the “Customs Levy Exemption Form” will be stamped and emailed
back to the contractor. The stamped form must accompany every shipment for which a levy exemption is
desired.


                                                                                                           39
(c) Upon contract award, the contractor/consignor shall provide the necessary logistical information required
by USF-I DCG A&T / J4.

STEP 1:

-- Upon contract award go to the following JCCS website:
-- https://www.rebuilding-iraq.net/

STEP 2:

-- Select the “Logistics” and then the “Customs” radio buttons.
-- Select and complete the “Customs Levy Waiver Form”.

STEP 3:

--Email the (1) completed “Customs Levy Exemption Form”, (2) a copy of the front page of the signed contract;
and (3) the pages from the contract that describe the required supplies, equipment or end product to USF-I DCG
A&T /J4 (Logistics) at Usf-i.j4.MMDMOVE@IRAQ.CENTCOM.MIL and Customs Officials at
CMDbattlebox@iraq.centcom.mil, DSN: 318-485-2594/6224 Commercial: 713-970-6140 (Rings in Iraq)
within 7 days of shipping.

--The “Customs Levy Exemption Form” will be reviewed by a Government of Iraq representative. If the
shipment qualifies for a levy exemption, the “Customs Levy Exemption Form” will be stamped and emailed
back to the contractor. The stamped form must accompany every shipment for which a levy exemption is
desired.

--Complete a Form DD-250 form, Material Inspection and Receiving Report, and provide it and the invoice for
the shipment with the cargo.

--Commercial Air Shipments require (1) airway bills and (2) the “Customs Levy Exemption” form to be
emailed to the USF-I J4 org box at Usf-i.j4.mmdmove@iraq.centcom.mil. Ensure that all shipping labels have
USF-I and ATTN: Agility.

(d) It is the contractor’s responsibility to provide all the requested information in sufficient time to allow
coordination of required delivery. Failure to comply with these instructions may result in delaying the arrival of
supplies and materiel at their final destinations.

(e) Once material is shipped, the Contractor shall notify USF-I J4, within two business days, at the following
email address: Usf-i.j4.mmdmove@iraq.centcom.mil.

                                                      (End)


952.225-0009, MEDICAL SCREENING AND VACCINATION REQUIREMENTS FOR LOCALLY
HIRED EMPLOYEES (JAN 2010)

(a) Contractors, and subcontractors at any tier shall ensure and provide satisfactory evidence that all locally
hired employees, including Local National (LN), Third Country National, and U.S. employees, working on
military have been screened for and do not currently have active tuberculosis (TB).

(1) Contractors may utilize a testing method of either a chest x-ray or TB skin test (TST).

(i) Chest x-rays shall be taken and TSTs administered within 90 days prior to the start of employment.

(ii) Screening may be performed either by a licensed medical provider from the local economy or by
contractors’ licensed medical staffs. Contractors shall maintain medical screening documentation and make it
available to the Contracting Officer upon request.

(2) TB screening documentation shall be provided to the responsible Base Defense Operations Center (BDOC)
prior to issuance of base access badges.

                                                                                                                  40
(b) Contractor employees, including subcontractors at any tier, who work in positions where they are working
with food or water production and distribution, shall have current Typhoid and Hepatitis “A” (full series)
vaccinations, in addition to the TB tests required above.

(c) At least the first inoculation in the Hepatitis “A” series must be given prior to the start of employment, with
continuation and completion of the inoculation series. Once the complete Hepatitis “A” vaccination series is
completed, it does not have to be repeated.

(1) The Typhoid inoculation must be completed within two years prior to the date of employment in the food
and water service capacity. The Typhoid vaccination requires a booster immunization every three years.

(2) Proof of individual employee vaccinations shall be provided to the Contracting Officer and COR proof that
their employees and their subcontractor (at any tier) employees have received the above vaccinations. The
contractor shall maintain their employees’ vaccination records for examination by the Contracting Officer. The
contractor shall ensure that their subcontractors at any tier maintain their respective employees’’ vaccination
records for examination by the Contracting Officer.

                                                         (End)


952.225-0011, GOVERNMENT FURNISHED CONTRACTOR SUPPORT (APR 2010)

The following is a summary of the type of support the Government will provide the contractor, on an “as-
available” basis. In the event of any discrepancy between this summary and the description of services in the
Statement of Work, this clause will take precedence.

                                   U.S. Citizens Accompanying the Force

            APO/FPO/MPO/Postal Services            DFACs                              Mil Issue Equip
            Authorized Weapon                      Excess Baggage                     MILAIR
            Billeting                              Fuel Authorized                    MWR
            CAAF                                   Govt Furnished Meals               Resuscitative Care
            Controlled Access Card (CAC)/ID Card   Military Banking                   Transportation
            Commissary                             Military Clothing                  All
            Dependents Authorized                  Military Exchange                  None


                                 Third-Country National (TCN) Employees

            APO/FPO/MPO/Postal Services            DFACs                              Mil Issue Equip
            Authorized Weapon                      Excess Baggage                     MILAIR
            Billeting                              Fuel Authorized                    MWR
            CAAF                                   Govt Furnished Meals               Resuscitative Care
            Controlled Access Card (CAC)/ID Card   Military Banking                   Transportation
            Commissary                             Military Clothing                  All
            Dependents Authorized                  Military Exchange                  None


                                        Local National (LN) Employees

            APO/FPO/MPO/Postal Services            DFACs                              Mil Issue Equip
            Authorized Weapon                      Excess Baggage                     MILAIR
            Billeting                              Fuel Authorized                    MWR
            CAAF                                   Govt Furnished Meals               Resuscitative Care
            Controlled Access Card (CAC)/ID Card   Military Banking                   Transportation
            Commissary                             Military Clothing                  All
            Dependents Authorized                  Military Exchange                  None


                                                         (End)




                                                                                                                41
952.225-0013, CONTRACTOR HEALTH AND SAFETY (FEB 2010)

(a) Contractors shall comply with all National Electrical Code (NEC 2008), Specifications as outlined, and MIL
Standards and Regulations. All infrastructure to include, but not limited to, living quarters, showers, and
restrooms shall be installed and maintained in compliance with these standards and must be properly supported
and staffed to ensure perpetual Code compliance, prevent hazards and to quickly correct any hazards to
maximize safety of those who use or work at the infrastructure (NEC Table 352.20). Specifically, the use of
magnetic ballasts in lighting for new construction or replacement of existing magnetic ballasts during
refurbishment, alterations or upgrades with new magnetic ballasts is prohibited. The government has the
authority to enter and inspect contractor employee living quarters at any time to ensure the prime contractor is
complying with safety compliance standards outlined in the 2008 National Electric Code (NEC).

(b) The contractor shall correct all deficiencies within a reasonable amount of time of contractor becoming
aware of the deficiency either by notice from the government or a third party, or discovery by the contractor.
Further guidance on mandatory compliance with NFPA 70: NEC 2008 can be found on the following link
http://www.nfpa.org.

                                                       (End)



10.0          GOVERNMENT FACILITIES
As specified in each Task order, Government facilities (i.e., office space, computer hardware/software, or lab
space) will be provided to those labor categories that would otherwise adversely affect the work performance if
they were not available on-site. All Contractor personnel with supplied government facilities shall be located at
SSC-LANT. Note: The burdened labor rate for those contractor personnel designated as "government site"
shall include overhead costs allocable to government site work, consistent with the contractor's established
accounting practices.


11.0          CONTRACTOR FACILITIES
A significant portion of Task orders issued under this contract will require close liaison with the government.
The Contractor shall be prepared to establish a local facility within a thirty (30)-mile radius of SSC LANT.
Close proximity allows for proper COR/DOCOR maintenance duties. The contractor’s facility is not necessary
for the exclusive use of this contract and can be utilized on a shared basis. For proposal estimating purposes, the
Contractor shall have at least 2,500 sq ft for use on this contract; however, no more that 1,000 sq ft shall be used
for admin purposes.” The Charleston local facility shall include sufficient physical security to protect
government assets. The Contractor’s facility shall meet all location and size requirements as specified 30 days
after contract award. Facility space shall include offices, conference rooms, lab work, and a staging area for
materials and equipment.



12.0         SAFETY ISSUES

The Contractor shall be responsible for ensuring the safety of all company employees, other working personnel,
and Government property. The Contractor is solely responsible for compliance with the Occupational Safety
and Health Act (OSHA) (Public Law 91-596) and the resulting standards, OSHA Standard 29 CFR 1910
(general), 1915 (shipboard/submarine) and 1926 (shore), and for the protection, safety and health of their
employees and any subcontractors assigned to the respective task orders under this contract. It is the
Contractor’s sole responsibility to make certain that all safety requirements are met and are documented as part
of their quality management system.


            Performance at government facilities
For performance of work at government facilities, the Contractor shall adhere to the following requirements:

(a)    If performance of any work under this contract is required at a SSC LANT facility or any other
government facility, the Contractor shall contact the applicable local government office (for SSC-LANT,
                                                                                                                 42
contact Code 8.1) with cognizance over safety and environmental requirements prior to performance of ANY
work under this contract. The purpose of contacting the Safety and Environmental Office is to obtain and
become familiar with any local safety regulations or instructions and to inform the local Safety Officer of any
work taking place on base. Safety and Occupational Health personnel cannot assume a regulatory role relative
to oversight of the contractor safety activities and performance except in an imminent danger situation.
Administrative oversight of contractors is the primary responsibility of the Contracting Office and/or the
Contracting Officer's designated representative.

(b)      Contractors are responsible for following all safety and health related State and Federal statutes and
corresponding State, Federal and/or Navy regulations protecting the environment, contractor employees, and
persons who live and work in and around contractor and/or federal facilities.

(c)       Contractors shall monitor their employees and ensure that they are following all safety regulations
particular to the work areas. Contractors shall ensure that their employees (i) wear appropriate safety equipment and
clothing, (ii) are familiar with all relevant emergency procedures should an accident occur, and (iii) have access to a
telephone and telephone numbers, to include emergency telephone numbers, for the SSC-LANT facility where work
is performed.

(d)       Contractor shall immediately report any accidents involving government or contractor personnel
injuries or property/equipment damage to the contracting officer and COR. Additionally, the Contractor is
responsible for securing the scene and impounding evidence/wreckage until released by the contracting officer.

12.1          SAFETY EQUIPMENT

All personnel safety equipment required to perform work under this contract shall be provided by the Contractor
and must be in satisfactory working order. Personal safety equipment shall include, but not be limited to --
hard-hats, safety shoes, safety gloves, goggles, hearing protection, non-flammable clothing for hot work
personnel, gas/oxygen detectors for confined spaces, face shields, and other types of safety equipment required
to assure a safe work environment and compliance with applicable federal, state and local safety regulations.

12.2          SAFETY TRAINING

The Contractor shall be responsible to train all personnel that require safety training. Specifically, where
Contractors are performing work at Navy shore installations, that requires entering manholes or underground
services utility the Contractor shall provide a qualified person as required in 29 CFR 1910 or 29 CFR 1926 or as
recommended by the National Institute for Occupational Safety and Health (NIOSH) Criteria Document for
Confined Spaces. Also, when contractors are required to scale a tower, all applicable personnel shall have
Secondary Fall Protection and Prevention training.


13.0           SMALL BUSINESS PARTICIPATION GOALS – TBD pending Market Survey
The Contractor shall submit a semi-annual report demonstrating their progress in meeting their small business
participation goals as outlined in their Small Business Participation Data (submitted during the solicitation
phase, Section L) and incorporated as an Attachment in the contract award. This report entitled, Small Business
Participation Goals Report (CDRL A021), shall initially be submitted 6 months after contract award and semi-
annually throughout contract performance. The Administrative and/or Procuring Contracting Officer’s
assessment results shall be reflected in the CPARS rating for each performance period. Data submitted in this
report shall also correspond to the CPARS data submission and performance periods. NOTE: This report is
separate from the requirements of the Small Business Plan. *To be completed at time of contract award.


[END OF PWS]




                                                                                                                   43

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:3/27/2013
language:English
pages:43