Subj: CMPRO (Configuration Management Support)
Identification of the agency and the contracting activity, and specific identification
This is a sole source justification. Contracting activity is the Naval Sea Systems Command, Naval Surface Warfare Center, Panama City Division (NSWC PCD), 110 Vernon Avenue, Panama City, FL 32407-7001 (Contracts Department Code 02).
Nature and/or description of the action being approved.
This action will award a firm fixed price purchase order to Complete Logistics Support, Inc. (DUNS: 080638599 / CAGE Code: 7VDF1), 475 Market St., Elmwood Park, NJ, 07407 for custom CMPro application development for the Special Operations Forces, Combat Diving (SOF- CD).
(including the estimated value).
This requirement is for services to develop customized configuration management applications based on CMPro in support of the Special Operations Force Combat, Divers through 30 September 2022.
d requirements personnel. This memo does not authorize acquisition for other requirements. This acquisition will be conducted using simplified acquisition procedures with a total dollar value above micro-purchase levels, but not exceeding the simplified acquisition threshold of
$250,000.00. Delivery of all services will be by 30 September 2022. This purchase will be funded with FY21 Research, Development, Test, and Evaluation (RDT&E) funds.
Identification of the justification rationale and, if applicable, a demonstration of the
service.
10 U.S.C. 2304(c)(1), 10 U.S.C. 2304(d)(1)(B). Only One Responsible Source and No Other Supplies or Services Will Satisfy Agency Requirements FAR 6.302-1(a)(2)(iii)(B).
10 U.S.C. 2304(c) (1) - Only one responsible source and no other supplies or services will satisfy agency requirements, FAR 6.302-1. Special Operations Forces, Combat Diving (SOF-CD) requires support for configuration management of multiple systems. A Statement of Work was drafted and an Analysis of Alternatives was performed in previous years. The vendor, Complete Logistics Support, Inc. (CLS) was found to be most competent and their services have been utilized locally at NSWC-PCD, specifically with Special Operations Forces, Combat Diving.
An extensive Market Research campaign was conducted and SOF-CD found CLS to continue to be best suited to continue supporting the configuration management requirement. SOF-CD Leads have a good working relationship with CLS and the local contractor whom they have been depending upon for configuration management support for multiple years. The current contract will end on 30-September 2021.
As such, the Government does not expect significant savings nor better service through competition but does anticipate significant and unacceptable delays that will negatively impact
interest to award on a sole source basis to Complete Logistics Support, Inc.
A determination by the ordering activity contracting officer that the order represents the best value consistent with FAR 13.106-1(b).
The Contracting Officer has determined that the order represents the best value and results in the lowest overall cost alternative (considering price, special features, administrative costs, etc.) to
A description of the market research conducted among schedule holders and the results or a statement of the reason market research was not conducted.
This requirement will be synopsized on the Commercial Opportunities website at SAM.gov per FAR 5.2. Based on the market research discussed in paragraph 4 above, CLS, Inc. is the only so
Any other facts supporting the justification.
None.
A statement of the actions, if any, the agency may take to remove or overcome any barriers that led to the restricted consideration before any subsequent acquisition for the supplies or services is made.
As stated in paragraph 4 above, CLS, Inc. is the only source that can meet this requirement.
SOW:
STATEMENT OF WORK FOR
CONFIGURATION MANAGEMENT SUPPORT
-
- SCOPE
The Special Operational Forces Combat Diving Rapid Engineering Division (SOF CBDIV RED) Program Office, has a requirement for logistics support. The Contractor shall provide Configuration Management (CM) structure, processes, reporting, data migration, and training for the Contractors configuration management applications and tools. The Contractor shall ensure CM Support will be focused on rapid engineering development processes that are streamlined to be timely and efficient to achieve mission requirements.
-
- Background
All Combat Diving (CBDIV) mission capabilities must be developed through defined and repeatable processes to ensure credibility for fielding and deployment decisions. The CBDIV Middle Tier of Acquisition program is a system of systems designed to provide for the modernization, manufacturing, testing, development, and transition of diving equipment for the combat diver. The Naval Surface Warfare Center Panama City Division (NSWC PCD) serves as the official Engineering Agent (EA) for the CBDIV program. This assigns NSWC PCD as the Design Agent (DA), Acquisition Engineering Agent (AEA), In-Service Engineering Agent (ISEA) and Software Support Activity (SSA) for Combat Diving.
2.0 APPLICABLE DOCUMENTS
None
-
- REQUIREMENTS
The Contractor shall develop specific elements of configuration management, as specified, in support of the SOF CBDIV-RED program office.
-
- Configuration Management Support (CDRL A001)
The Contractor shall perform a variety of complex configuration management, administrative and analytical tasks in support of a contract program, as specified, in support of the SOF CBDIV-RED program office. To include but not limited to the following:
-
-
- CM Continuous Process Improvements :
Research and Assess Current CM Posture.
Conduct gap analysis between as-is and desired future state of the CM process. Define CM Implementation Strategy for New CM Processes.
Utilize Best Practices based on existing CM standards/handbooks, implementations and subject matter expertise
-
-
- CM Administration :
Provide customer interface and serve as liaison to other industry representatives to ensure conformance Maintain and update inventory records.
Participate in special projects as required.
Analyze, explain, and apply laws, regulations, rulings, and procedures pertinent to the work to be performed. Develop plans and monitor tasks to meet contractual/project requirements for assigned program.
Develop and implement efficient procedure for various areas, such as inventory management.
-
-
- Continue Development of Current End-to-End Workflow for Key CM processes and Future State Processes:
Create and establish new CM workflow processes. This includes but not limited to: file naming conventions, work order/inventory processes, IUID label work instructions. Process creations will be on going as program matures.
Product Baseline Establishment workflow
Configuration Change Request (CCR) review and adjudication workflow Configuration Control Board (CCB)
SOF CBDIV RED Prototype Development/Testing/Fielding workflow SOF CBDIV RED Prototype Production/Testing/Fielding workflow
SOF CBDIV RED Accomplishment on individual Project/Work Order/ workflow
-
-
- Continue Development and Implementation of Configuration Control Board (CCB) Capability:
Threshold goal is to implement CCB functionality in CMPRO utilizing CCB existing construct
Forces Combat Diving Rapid Engineering Division CCB construct based on consensus of working groups and support of SOF CBDIV RED leadership.
Include SME Analysis
Develop use cases to formulate CM business rules
Conduct gap analysis between as-is and desired future state Update applicable deliverables
-
- CMPRO Database Administration (CDRL A002)
- CMPRO Improve Current Setup in the Following Areas:
Creating structure Systems/Sub Systems/System of Systems and relationships. Create Program/System/Contract Task Dashboard
Proprietary Group setup with data migration. Inventory Module setup with data migration. Create approved Roles/Control Groups/Steps Create user defined groups
Create document types with business rules for creation/revision and auto number generation. Create categories/platforms
Create workflow routes for current processes.
Create approved menus/accounts/permissions/functions
Create CMPRO User Training Visual Guides For: New User Basic Guide
User Workflow Process Guide User Inventory Process Guide User Work Order Process Guide
-
-
- CMPRO Product Life Cycle Management:
Product Life Cycle Management is not static but ongoing to adapt and grow with the product and its requirements as it goes the appropriate milestones.
Establish milestones with metric reporting requirements on a weekly and monthly basis. These reports should include CMPRO generated reports. These do not require set up or extensive training to run, they are simple and will not take time away from the program set up.
Establish that the current processes that have not been formalized in document form cannot hold up the progress of getting started.
Establish Quarterly review of progress with live run through in CMPRO. Should be no more than 1 hour.
Perform day to day Configuration Management Support as needed for SOF CBDIV RED Systems, Inventory, Documents, Drawings, Change Processes, to include ECPs through CCB.
Ensure Reporting is updated as needed to include CDRL reporting. Support ISEA in Program Dashboard metrics.
Maintain and update processes, workflow in CMPRO.
-
- Progress Reporting (CDRL A003)
The Contractor shall report status and progress on a monthly basis.
-
- NMCI Accounts
In accordance with the requirements of (System Authorization Access Request (SAAR-N) Requirements for Information Technology), the Contractor shall obtain Navy Marine Corps Intranet (NMCI) accounts to provide a Common Access Card (CAC) with a Public Key Infrastructure (PKI) Certificate to employees required to access secure Government websites and databases to perform the duties included in this SOW.
-
- Travel
No travel is anticipated in support of this effort.
-
- Schedule
The Contractor shall adhere to the following Notional timeline schedule:
Planned Accomplishments SOW Ref Task
Completion
3.1
Configuration Management Support
3.1.1
CM Continuous Process Improvements
All QTR
3.1.2
CM Administration
All QTR
3.1.3
Continue Development of Current End-to-End Workflow for Key CM
1st & 2nd QTR
3.1.4
Continue Development and Implementation of Configuration Control
3rd & 4th QTR
3.2
CMPRO Database Administration
3.2.1
CMPRO Improve Current Setup
1st & 2nd QTR
3.2.2
CMPRO Product Life Cycle Management
3rd & 4th QTR
-
- Personnel Requirements
The Contractor shall be responsible for employing personnel having the following levels of education, professional, and technical experience. These qualifications are only a baseline; contractors should strive for technical excellence in personnel by demonstrating experience and qualifications beyond these qualifications. The specialized experience included as part of the required qualifications shall have been obtained in the field of endeavor indicated by the applicable labor categories listed below. The experience indicated in the following labor categories must have been performed during the past five years. In cases requiring experience of more than five years, at least five years of the total experience must be within the past five years. Personnel must have, or be able to, obtain the appropriate security clearance as stated on the DD Form 254. Proof of U.S. citizenship is required to be permitted access to Government installation, aircraft, and ships.
-
-
- Labor Category Qualifications
- At least fifteen (15) years of experience in conducting analytical studies applicable to Configuration Management and Database Administration. Demonstrated ability to conduct studies, analysis, or evaluations of DoD weapon Systems/equipment. Demonstrated experience in the following Configuration Management/ CMPRO Program Support discipline is required:
Creation/Setup/Support
Systems/Sub Systems/System of Systems and parent/child relationships in Life Cycle Management starting at prototyping.
Inventory and Production Module for equipment tracking and reporting. DD1149 and DD1348processes/reporting. Production/System/Model.
Physical Inventory Management.
Baseline creation and management for hardware/software. Audits, business rules and processes.
Process Management business rules, checklists, work instructions, and processes for creation of new creation/change processes workflow routes for hardware/software, and associated documents and drawings from informal requirements to formal vetting requiring ECP/NOR change process in accordance with Program Office requirements.
Program/System/Contract Task Dashboard set up and support for program leadership access at a glance information. Project business rules and processes including related Action Items (AI)/Tasks to include fielded items and work orders.
Contracts business rules and processes for CDRLs/reviews tracking and reporting.
Setup and maintain Roles/Control Groups, Information Groups. Roles/Control Groups, Information Groups, Permissions/Functions/and Menus. Module Permissions and defaults.
Auto number generation formatting for document/drawing/software and related business rules for creation/revision. User training and tailored guidance material for approved processes in CMPRO.
Import Document/Drawing/Software, Part Master/ Part BOM, As-built, Inventory/Vendor
Reports, system reporting, Ad Hoc for tailored, repeatable metrics and reports.
- Education/Certifications:
DAWIA LEVEL I - Configuration Management Log204 Section 306 Defense Acquisition University (DAU) DAWIA LEVEL I - IPT Leadership and Management CLM014 Section 888, DAU
DAWIA LEVEL I ISO 9000:2000 CLE201 Section 888, DAU
DAWIA LEVEL I - Performance Based Logistics Log235 Section 303, DAU
DAWIA LEVEL I - Fundamentals of System Acquisition Management ACQ101 Section 315, DAU Value Based Six Sigma (VBSS) - Green Belt Certificate
CMII Comprehensive Certification (CMIIC) - Institute of Configuration Management LEVEL I The CMII/IPE Model
LEVEL II - Structuring and Managing Requirements LEVEL III Change Challenges and Proven Solutions LEVEL IV The CMII Close Loop Change Processes LEVEL V Operation, Maintenance, & Logistics LEVEL IV CMII Implementation and Application
4.0 GOVERNMENT PROPERTY
None
5.0 DATA DELIVERABLES
Data shall be delivered in accordance with the attached Contract Data Requirements List (CDRL) (DD Form 1423)
6.0 PERIOD OF PERFROMANCE
The period of performance shall be FY22 or 1st October 2021 through 30 September 2022.
7.0 SECURITY
The Contractor shall require access to classified information up to the SECRET level. The Contractor will not be required to generate or store classified information. The requirements of the attached DD 254 apply.
RELEASE OF INFORMATION
Release of information shall be in accordance with Section I, DFARS Clause 252.204-7000, Disclosure of Information.
All technical data provided to the Contractor by the Government shall be protected from public disclosure in accordance with the markings contained thereon. All other information relating to the items to be delivered or services to be performed under this contract shall not be disclosed by any means without prior approval of the appropriate NSWC PCD authority. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or by any other person or entity; publication of technical or scientific papers; advertising; or any other proposed public release. The Contractor shall provide adequate physical protection to such information to preclude access by any person or entity not authorized such access by the Government.
Controlled Unclassified Information (CUI)
Controlled Unclassified Information (CUI) is official information that requires the application of controls and protective measures for a variety of reasons and has not been approved for public release, to include technical information, proprietary data, information requiring protection under the Privacy Act of 1974, and Government- developed privileged information involving the award of contracts. CUI is a categorical designation that refers to unclassified information that does not meet the standards for National Security Classification under Executive Order 13526, but is (a) pertinent to the national interest of the United States or to the important interests of entities outside the Federal Government, and (b) under law or policy requires protection from unauthorized disclosure, special handling safeguards, or prescribed limits on exchange or dissemination.
Minimum Requirements for Access to Controlled Unclassified Information (CUI)
Prior to access, Contractor personnel requiring access to DON controlled unclassified information (CUI) or "user level access to DON or DoD networks and information systems, system security and network defense systems, or to system resources providing visual access and/or ability to input, delete or otherwise manipulate sensitive information without controls to identify and deny sensitive information" contractors must have clearance eligibility, or submit an Electronic Questionnaire for Investigation Processing (SF 86) to NSWC PCD Security for processing and subsequent adjudication by the DoD Consolidated Adjudications Facility.
Minimum Protection Requirements for Controlled Unclassified Information
Security classification guides and unclassified limited documents (e.g., CUI, Distribution Statement Controlled) are not authorized for public release and, therefore, cannot be posted on a publicly accessible webserver or transmitted over the Internet unless appropriately encrypted.
CUI
CUI is a document designation, not a classification. This designation is used by Department of Defense (DoD) and a number of other federal agencies to identify information or material, which although unclassified, disclosure to the public of the information would reasonably be expected to cause a foreseeable harm to an interest protected by one or more provisions of the Freedom of Information Act (FOIA). This includes information that qualifies for protection pursuant to the provisions of the Privacy Act of 1974, as amended. CUI must be marked, controlled and safeguarded in accordance with DoDI 5200.48, CUI
Security of Unclassified DoD Information on Non-DoD Information Systems (DoDI 8582.01) DoD Policy
Adequate security shall be provided for all unclassified DoD information on non-DoD information systems. Appropriate requirements shall be incorporated into all contracts, grants, and other legal agreements with non-DoD entities.
Information Safeguards are applicable to unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems, to the extent provided by the applicable contract, grant, or other legal agreement with the DoD.
Information Safeguards
Unclassified DoD information that has not been cleared for public release may be disseminated by the Contractor, grantee, or awardee to the extent required to further the contract, grant, or agreement objectives, provided that the information is disseminated within the scope of assigned duties and with a clear expectation that confidentiality will be preserved. Examples include:
Non-public information provided to a Contractor (e.g., with a request for proposal).
Information developed during the course of a contract, grant, or other legal agreement (e.g., draft documents, reports, or briefings and deliverables).
Privileged information contained in transactions (e.g., privileged contract information, program schedules, contract- related event tracking).
It is recognized that adequate security will vary depending on the nature and sensitivity of the information on any given non-DoD information system. However, all unclassified DoD information in the possession or control of non- DoD entities on non-DoD information systems shall minimally be safeguarded as follows:
Do not process unclassified DoD information on publically available computers (e.g., those available for use by the general public in kiosks or hotel business centers).
Protect unclassified DoD information by at least one physical or electronic barrier (e.g., locked container or room, logical authentication or logon procedure) when not under direct individual control of an authorized user.
At a minimum, overwrite media that have been used to process unclassified DoD information before external release or disposal.
Encrypt all information that has been identified as CUI when it is stored on mobile computing devices such as laptops and personal digital assistants, compact disks, or authorized removable storage media such as thumb drives and compact disks, using the best encryption technology available to the Contractor or teaming partner.
Limit transfer of unclassified DoD information to subcontractors or teaming partners with a need to know and obtain a commitment from them to protect the information they receive to at least the same level of protection as that specified in the contract or other written agreement.
Transmit e-mail, text messages, and similar communications containing unclassified DoD information 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.
Encrypt organizational wireless connections and use encrypted wireless connections where available when traveling. If encrypted wireless is not available, encrypt document files (e.g., spreadsheet and word processing files), using at least application-provided password protected level encryption.
Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.
Do not post unclassified DoD information to website pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to website pages that control access by user identification and password, user certificates, or other technical means and provide protection via use of transport layer security or other equivalent technologies during transmission. Access control may be provided by the intranet (vice the website itself or the application it hosts).
Provide protection against computer network intrusions and data exfiltration, minimally including:
Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.
Monitoring and control of both inbound and outbound network traffic (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. Prompt application of security-relevant software patches, service packs, and hot fixes.
Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, proprietary, Critical Program Information (CPI), personally identifiable information, export controlled) as specified in contracts, grants, and other legal agreements.
Report loss or unauthorized disclosure of unclassified DoD information in accordance with contract, grant, or other legal agreement requirements and mechanisms.
Do not use external IT services (e.g., e-mail, content hosting, database, document processing) unless they provide at least the same level of protection as that specified in the contract or other written agreement.
Operations Security
Operations Security (OPSEC) is concerned with the protection of critical information: facts about intentions, capabilities, operations, or activities that are needed by adversaries or competitors to bring about failure or unacceptable consequences of mission accomplishment.
Critical information includes information regarding:
Operations, missions, and exercises, test schedules or locations; Location/movement of sensitive information, equipment, or facilities; Force structure and readiness (e.g., recall rosters);
Capabilities, vulnerabilities, limitations, security weaknesses; Intrusions/attacks of DoD networks or information systems; Network (and system) user IDs and passwords;
Movements of key personnel or visitors (itineraries, agendas, etc.); and
Security classification of equipment, systems, operations, etc.
The Contractor, subcontractors and their personnel shall employ the following countermeasures to mitigate the susceptibility of critical information to exploitation, when applicable:
Practice OPSEC and facilitate OPSEC awareness;
Immediately retrieve documents from printers assessable by the public;
Shred sensitive and Controlled Unclassified Information (CUI) documents when no longer needed; Protect information from personnel without a need-to-know;
When promulgating information, limit details to that essential for legitimacy;
During testing and evaluation, practice OPSEC methodologies of staging out of sight, desensitization, or speed of execution, whenever possible.
8.0 DISTRIBUTION LIMITATION STATEMENTS
Technical Documents generated under this Order shall carry the following Distribution Limitation Statements. Word- processing and electronic files shall have the statements included in the file such that the first page of any resultant hard copy shall display the statements. For drawings, the statements shall be as near to the title block as possible without obscuring any detail of the drawing. Additionally, any diskette delivered shall be marked externally with the statements:
DISTRIBUTION STATEMENT D: DISTRIBUTION AUTHORIZED TO DEPARTMENT OF DEFENSE AND US DOD CONTRACTORS ONLY; ADMINISTRATIVE OR OPERATIONAL USE (DATE). OTHER
U.S. REQUESTS SHALL BE REFERRED TO COMMANDING OFFICER, NAVAL SURFACE WARFARE CENTER PANAMA CITY DIVISION, ATTN: CODE E15, 110 VERNON AVENUE, PANAMA CITY, FL 32407-7001.
DESTRUCTION NOTICE - CLASSIFIED INFORMATION, DESTROY IN ACCORDANCE WITH SECNAV M-5510.36, (DON INFORMATION SECURITY PROGRAM) OR DOD 5220.22-M, (NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL). UNCLASSIFIED LIMITED DOCUMENTS, (E.G., FOUO, DISTRIBUTION STATEMENT CONTROL) DESTROY BY ANY METHOD THAT WILL PREVENT DISCLOSURE OF CONTENTS OR RECONSTRUCTION OF THE DOCUMENT
9.0 GOVERNMENT AND CONTRACTOR RELATIONSHIP
- The services to be delivered under this Order are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Order between the Government and the Contractor's personnel. It is, therefore, in the best interest of the Government to afford both parties a full understanding of their respective obligations.
- All Contractor, Subcontractor, and consultant personnel shall wear prominently displayed identification badges at all times when performing work on NSWC PCD property or attending meetings in the performance of this Order. The badge shall contain the individual's name, the company name and logo. When participating in such meetings (e.g., as a speaker, panel member), those individuals in Contractor employ must supplement physical identification (e.g., badges, place markers) with verbal announcements so that it is clear to the assembled group that they are employees of the Contractor, not NSWC PCD employees. In addition, when working on NSWC PCD property, all Contractor, Subcontractor, and consultant personnel shall have signs visible on their desks or at their work sites that clearly state that they are not NSWC PCD employees.
- The Contractor is responsible for supervision of all Contractor personnel assigned to this Order. The Contractor shall exercise ultimate over all aspects of Contractor personnel day-to-day work under this Order including the assignment of work, means and manner of Contractor employee performance and the amount of Contractor supervision
provided. The Contractor shall be ultimately responsible for all aspects of performance under this Order including the work of its Contractor personnel.
Contractor personnel under this Order shall not:
-
- Be placed in a position where they are under the supervision, direction, or evaluation of a Government employee.
- Be placed in a position of command, supervision, administration or control over Government personnel, or over personnel of other Contractors under other NSWC PCD contracts, or become a part of the Government organization.
- Be used in administration or supervision of Government procurement activities.
- Have access to proprietary information belonging to another without the express written permission of the owner of that proprietary information.
- Employee Relationship:
- The services to be performed under this Order do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.
- Rules, regulations, directives and requirements that are issued by the U.S. Navy and NSWC PCD under its responsibility for good order, administration, and security are applicable to all personnel who enter the Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services Order.
- Inapplicability of Employee Benefits: This Order does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.
-
- Payments by the Government under this Order are not subject to the Federal income tax withholdings.
- Payments by the Government under this Order are not subject to the Federal Insurance Contributions Act.
- The Contractor is not entitled to unemployment compensation benefits under the Social Security Act, as amended, by virtue of performance of this Order.
- The Contractor is not entitled to workman's compensation benefits by virtue of this Order.
- The entire consideration and benefits to the Contractor for performance of this Order are contained in the provisions for payment under this Order.
- Notice. It is the Contractor's, as well as, the Government's responsibility to monitor Order activities and notify the Contracting Officer if the Contractor believes that the intent of this clause has been or may be violated.
-
- The Contractor should notify the Contracting Officer in writing promptly, within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this clause. The notice should include the date, nature, and circumstances of the conduct, the name, function and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct, identify any documents or substance of any oral communication involved in the conduct, and the estimate in time by which the Government must respond to this notice to minimize cost, delay or disruption of performance.
-
- The Contracting Officer shall promptly, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:
- confirm the conduct is in violation and when necessary direct the mode of further performance,
- countermand any communication regarded as a violation
- deny that the conduct constitutes a violation and when necessary direct the mode of further performance; or
- in the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor and the date.
C-237-H001 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (NAVSEA) (OCT 2018)
- The Contractor shall report Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the NSWC PCD via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:
-
- W, Lease/Rental of Equipment;
-
- X, Lease/Rental of Facilities;
-
- Y, Construction of Structures and Facilities;
-
- D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;
-
- S, Utilities ONLY;
-
- V, Freight and Shipping ONLY.
- The Contractor is required to completely fill in all required data fields using the following web address https://www.ecmra.mil.
- Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://dod.ecmra.support.desk@mail.mil.
(End of Text)
Clauses:
Section C – Specifications
Minimum Requirements for Access to Controlled Unclassified Information (CUI): Prior to access contractor personnel requiring access to DON controlled unclassified information (CUI) or "user level access to DON or DoD networks and information systems system security and network defense systems or to system resources providing visual access and/or ability to input delete or otherwise manipulate sensitive information without controls to identify and deny sensitive information" contractors must have clearance eligibility or submit an Electronic Questionnaire for Investigation Processing (SF 86) to NSWC PCD Security for processing and subsequent adjudication by the DOD Consolidated Adjudications Facility.
Minimum Protection Requirements for Controlled Unclassified Information: Security classification guides (OPNAVINST 5513 series) and unclassified limited documents (e.g. FOUO Distribution Statement Controlled) are not authorized for public release and therefore cannot be posted on a publicly accessible webserver or transmitted over the Internet unless appropriately encrypted.
Controlled Unclassified Information (CUI): Controlled unclassified information (CUI) is official information that requires the application of controls and protective measures for a variety of reasons and has not been approved for public release to include technical information proprietary data information requiring protection under the Privacy Act of 1974 and Government-developed privileged information involving the award of contracts. CUI is a categorical designation that refers to unclassified information that does not meet the standards for National Security Classification under Executive Order 13526 but is (a) pertinent to the national interest of the United States or to the important interests of entities outside the Federal Government and (b) under law or policy requires protection from unauthorized disclosure special handling safeguards or prescribed limits on exchange or dissemination.
For Official use Only (FOUO) is a document designation not a classification. This designation is used by Department of Defense (DoD) and a number of other federal agencies to identify information or material which although unclassified disclosure to the public of the information would reasonably be expected to cause a foreseeable harm to an interest protected by one or more provisions of the FOIA. This includes information that qualifies for protection pursuant to the provisions of the Privacy Act of 1974 as amended. FOUO must be marked controlled and safeguarded in accordance with DoD 5200.01 Vol. 4 DoD Information Security Program: Controlled Unclassified Information (CUI) February 24 2012
Security of Unclassified DoD Information on Non-DoD Information Systems (DoD 8582.01)
DoD policy: adequate security be provided for all unclassified DoD information on non-DoD information systems. Appropriate requirements shall be incorporated into all contracts grants and other legal agreements with non-DoD entities.
Information Safeguards are applicable to unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems to the extent provided by the applicable contract grant or other legal agreement with the DoD.
Information Safeguards
Unclassified DoD information that has not been cleared for public release may be disseminated by the contractor grantee or awardee to the extent required to further the contract grant or agreement objectives provided that the information is disseminated within the scope of assigned duties and with a clear expectation that confidentiality will be preserved. Examples include:
a. Non-public information provided to a contractor (e.g. with a request for proposal)
b. Information developed during the course of a contract grant or other legal agreement (e.g. draft documents reports or briefings and deliverables)
c. Privileged information contained in transactions (e.g. privileged contract information program schedules contract-related event tracking)
It is recognized that adequate security will vary depending on the nature and sensitivity of the information on any given non-DoD information system. However all unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems shall minimally be safeguarded as follows:
a. Do not process unclassified DoD information on publically available computers (e.g. those available for use by the general public in kiosks or hotel business centers)
b. Protect unclassified DoD information by at least one physical or electronic barrier (e.g. locked container or room logical authentication or logon procedure) when not under direct individual control of an authorized user.
c. At a minimum overwrite media that have been used to process unclassified DoD information before external release or disposal.
d. Encrypt all information that has been identified as CUI when it is stored on mobile computing devices such as laptops and personal digital assistants compact disks or authorized removable storage media such as thumb drives and compact disks using the best encryption technology available to the contractor or teaming partner.
e. Limit transfer of unclassified DoD information to subcontractors or teaming partners with a need to know and obtain a commitment from them to protect the information they receive to at least the same level of protection as that specified in the contract or other written agreement.
f. Transmit e-mail text messages and similar communications containing unclassified DoD information 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)
g. Encrypt organizational wireless connections and use encrypted wireless connections where available when traveling. If encrypted wireless is not available encrypt document files (e.g. spreadsheet and word processing files) using at least application-provided password protected level encryption.
h. Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.
i. Do not post unclassified DoD information to website pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to website pages that control access by user identification and password user certificates or other technical means and provide protection via use of TLS or other equivalent technologies during transmission. Access control may be provided by the intranet (vice the website itself or the application it hosts)
j. Provide protection against computer network intrusions and data exfiltration minimally including:
(1) Current and regularly updated malware protection services e.g. anti-virus anti-spyware.
(2) Monitoring and control of both inbound and outbound network traffic (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.
k. Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g. medical proprietary critical program information (CPI) personally identifiable information export controlled) as specified in contracts grants and other legal agreements.
l. Report loss or unauthorized disclosure of unclassified DoD information in accordance with contract grant or other legal agreement requirements and mechanisms.
m. Do not use external IT services (e.g. e-mail content hosting database document processing) unless they provide at least the same level of protection as that specified in the contract or other written agreement.
Operations Security
Operations Security (OPSEC) is concerned with the protection of critical information: facts about intentions capabilities operations or activities that are needed by adversaries or competitors to bring about failure or unacceptable consequences of mission accomplishment.
Critical information includes information regarding:
- Operations missions and exercises test schedules or locations;
- Location/movement of sensitive information equipment or facilities;
- Force structure and readiness (e.g. recall rosters);
- Capabilities vulnerabilities limitations security weaknesses;
- Intrusions/attacks of DoD networks or information systems;
- Network (and system) user IDs and passwords;
- Movements of key personnel or visitors (itineraries agendas etc.); and
- Security classification of equipment systems operations etc.
The contractor subcontractors and their personnel shall employ the following countermeasures to mitigate the susceptibility of critical information to exploitation when applicable:
- Practice OPSEC and facilitate OPSEC awareness;
- Immediately retrieve documents from printers assessable by the public;
- Shred sensitive and Controlled Unclassified Information (CUI) documents when no longer needed;
- Protect information from personnel without a need-to-know;
- When promulgating information limit details to that essential for legitimacy;
- During testing and evaluation practice OPSEC methodologies of staging out of sight desensitization or speed of execution whenever possible.
Section F - Deliveries or performance
F.O.B.
52.247-34 Destination
Section G
252.232-7003 Electronic Submission of Payment Requests and Receiving Reports (Dec 2018)
252.232-7006 Wide Area Workflow Payment Instructions
Section I – Contract Clauses
52.203-12 Limitation on Payments to Influence Certain Federal Transactions (Oct 2010)
52.204-23-Prohibition on Contracting for Hardware, Software, and Services Developed or Provided by Kaspersky Lab and Other Covered Entities (Jul 2018)
52.204-25 Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment.
52.204-19 Incorporation by Reference of Representations and Certifications (Dec 2014)
52.209-6 Protecting the Government’s Interest When Subcontracting with Contractors Debarred, Suspended, or Proposed for Debarment (Oct 2015)
52.212-4 Contract Terms and Conditions -- Commercial Items (May 2015)
52.227-19 Commercial Computer Software License (Dec 2007)
52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders -- Commercial Items
Preselected:
52.203-19 Prohibition on Requiring Certain Internal Confidentiality Agreements or Statement (Jan 2017)
52.209-10 Prohibition on Contracting with Inverted Domestic Corporations (Nov 2015)
52.233-3 Protest After Award (Aug 1996)
52.233-4 Applicable Law for Breach of Contract Claim (Oct 2004)
Select as Applicable for Set Aside Type:
52.219-6 Notice of Total Small Business Set-Aside NOV 2011
Required:
52.222-50 Combatting Trafficking in Persons (Mar 2015)
52.223-18 Encouraging Contractor Policies to Ban Text Messaging While Driving (Aug 2011)
52.232-33 Payment by Electronic Funds Transfer--System for Award Management JUL 2013
52.232-39 Unenforceability of Unauthorized Obligations (Jun 2013)
52.232-40 Providing Accelerated Payments to Small Business Subcontractors (Dec 2013)
52.243-1 Changes Fixed-Price
52.245-1 Government Property (Jan 2017)
52.245-9, Use and Charges (Apr 2012)
52.246-1 Inspection of Services-Fixed Price (Aug 1996)
252.203-7000 Requirements Relating to Compensation of Former DoD Officials (SEP 2011)
252.203-7002 Requirement to Inform Employees of Whistleblower Rights (Sep 2013)
252.204-7003 Control of Government Work Product (Apr 1992)
252.204-7008 Compliance with Safeguarding Covered Defense Information Controls (Oct 2016)
252.204-7009 Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information
252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting (Oct 2016)
252.204-7015 Notice of Authorized Disclosure of Information by Litigation Support (May 2016)
252.204-7019 Notice of NIST SP 800-171 DoD Assessment Requirements (Nov 2020)
252-204-7020 NIST SP 800-171 DoD Assessment Requirements (Nov 2020)
252.211-7003 Item unique identification and valuation (March 2016)
252.211-7007 Reporting of Government-Furnished Property (Aug 2012)
252.213-7000 Notice to Prospective Suppliers on Use of PPIRS (JUN 2015)
252.225-7048 Export Controlled Items (Jun 2013)
252.232-7010 Levies on Contract Payments (Dec 2006)
252.245-7001, Tagging, Labeling, and Marking of Government-Furnished Property (Apr 2012)
252.245-7002, Reporting Loss of Government Property (Dec 2017)
252.245-7003, Contractor Property Management System Administration (Apr 2012)
252.245-7004, Reporting, Reutilization, and Disposal (Dec 2017)
252.246-7007 Contractor Counterfeit Electronic Part Detection and Avoidance System
252.246-7008 Sources of Electronic Parts
252.247-7023 Transportation of Supplies by Sea (Apr 2014)
52.252-1-Solicitation Provisions Incorporated by Reference (Feb 1998)
52.252-2-Clauses Incorporated by Reference (Feb 1998)
Section K – Representations
52.203-18 Prohibition on Contracting with Entities that Require Certain Internal Confidentiality Agreements or Statements--Representation (Jan 2017)
52.204-19 Incorporation by Reference of Representations and Certifications (Dec 2014)
52.204-24 Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment.
52.204-26 Covered Telecommunication equipment or services—representation (Oct 2020)
52.209-11 Representation by Corporations Regarding Delinquent Tax Liability or a Felony Conviction (Feb 2016)
252.204-7008 Compliance with Safeguarding Covered Defense Information Controls (Oct 2016)
52.212-3 Offeror Representations and Certifications-Commercial Items (Oct 2018
Section L - Instructions Conditions and Notices to Bidders
52.212-1 Instructions to Offerors—Commercial Items (Jan 2017)
52.204-7 System for Award Management (Jul 2013
52.204-13 System for Award Management Maintenance JUL 2013)
52.204-22 Alternative Line Item Proposal (Jan 2017)
52.211-14 Notice of Priority Rating for National Defense Emergency Preparedness and Energy Program Use (Apr 2008)
252.213-7000 Notice to Prospective Suppliers on Use of PPIRS (JUN 2015)
Section M – Evaluation Factors for Award
52.212-2 Evaluation Commercial Items
FAR Part 13 Best value, SPRS past performance, price, and delivery terms
G-232-H002 PAYMENT INSTRUCTIONS AND CONTRACT TYPE SUMMARY FOR PAYMENT OFFICE (NAVSEA) (JUN 2018)
This entire contract is firm fixed price.
(End of Text)
G-232-H005 SUPPLEMENTAL INSTRUCTIONS REGARDING INVOICING (NAVSEA) (JAN 2019)(a) For other than firm fixed priced contract line item numbers (CLINs), the Contractor agrees to segregate costs incurred under this contract/task order (TO), as applicable, at the lowest level of performance, either at the sub line item number (SLIN) or CLIN level, rather than at the total contract/TO level, and to submit invoices reflecting costs incurred at that level. Supporting documentation in Wide Area Workflow (WAWF) for invoices shall include summaries of work charged during the period covered as well as overall cumulative summaries by individual labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of other direct costs (ODCs), materials, and travel, by technical instruction (TI), SLIN, or CLIN level. For other than firm fixed price subcontracts, subcontractors are also required to provide labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of ODCs, materials, and travel invoiced. Supporting documentation may be encrypted before submission to the prime contractor for WAWF invoice submittal. Subcontractors may email encryption code information directly to the Contracting Officer and Contracting Officer Representative (COR). Should the subcontractor lack encryption capability, the subcontractor may also email detailed supporting cost information directly to the Contracting Officer and COR; or other method as agreed to by the Contracting Officer.
(b) Contractors submitting payment requests and receiving reports to WAWF using either Electronic Data Interchange (EDI) or Secure File Transfer Protocol (SFTP) shall separately send an email notification to the COR and Contracting Officer on the same date they submit the invoice in WAWF. No payments shall be due if the contractor does not provide the COR and Contracting Officer email notification as required herein.
(End of Text)
G-242-H001 GOVERNMENT CONTRACT ADMINISTRATION POINTS-OF-CONTACT AND RESPONSIBILITIES (NAVSEA) (OCT 2018)
(a) The Government reserves the right to administratively substitute any of the points of contact listed below at any time.
(b) The contracting officer is the only person authorized to change this contract or orders issued thereunder. The Contractor shall not comply with any order, direction or request of Government personnel - that would constitute a change - unless it is issued in writing and signed by the Contracting Officer or is pursuant to specific authority otherwise included as part of this contract. If, in the opinion of the contractor, an effort outside the existing scope of this contract is requested, the contractor shall promptly comply with the Notification of Changes clause of this contract.
(c) The points of contact are as follows:
(i) The Procuring Contracting Officer (PCO) is:
See page 1, Block 24
(ii) The Contract Specialist is:
Name: Emily Walker
E-mail: emily.n.walker16.civ@us.navy.mil
Phone: 850-896-7811
-
-
-
- The Administrative Contracting Officer (ACO) is:
Not Applicable
(d) The Contracting Officer’s Representative (COR) is the contracting officer’s appointed representative for technical matters. The COR is not a contracting officer and does not have the authority to direct the accomplishment of effort which is beyond the scope of the contract or to otherwise change any contract requirements. An informational copy of the COR appointment letter, which provides a delineation of COR authority and responsibilities, will be provided upon award of this contract.
The Contracting Officer’s Representative (COR) is:
Not Applicable
(e) The Alternate Contracting Officer’s Representative (ACOR) is responsible for COR responsibilities and functions in the event that the COR is unavailable due to leave, illness, or other official business. The ACOR is appointed by the contracting officer; a copy of the ACOR appointment will be provided upon award of this contract.
The Alternate Contracting Officer’s Representative (ACOR) is:
Not Applicable
(f) The Technical Point of Contact (TPOC) is the contracting officer’s representative for technical matters when a COR is not appointed. The TPOC is responsible for technical issues of contract administration, such as providing all items of Government Furnished Information (GFI), Government Furnished Material (GFM) and Government Furnished Equipment (GFE) if specified in the contract as well as the inspection and acceptance of all contract deliverables.
The Technical Point of Contact (TPOC) is:
Name: Jonathan Outlaw
Email: jonathan.outlaw@navy.mil
(g) The Alternate Technical Point of Contact (ATPOC) is responsible for TPOC responsibilities and functions in the event that the TPOC is unavailable due to leave, illness, or other official business.
The Alternate Technical Point of Contact (ATPOC) is:
Not Applicable
(h) The Ombudsman will review complaints from the contractors and ensure that all contractors are afforded a fair opportunity to be considered, consistent with the procedures in the contract.
The Ombudsman is:
Not Applicable
(i) The Authorized Ordering Person(s) for Per-Call Maintenance is responsible for issuing and maintaining records for any per-call orders for remedial maintenance placed under this contract. No per-call order shall be placed outside the scope of this contract and the cumulative total of all orders shall not be in excess of any not-to-exceed amount specified in the contract. Per-call orders shall not, in any way, modify any terms and conditions of the contract.
(j) The Authorized Ordering Person(s) for Per-Call Maintenance is:
Person(s) listed in (f) with approval from persons listed in ( c ) (i) and (ii).
(k) The Contractor's point of contact for performance under this contract is:
Name:
E-mail:
Address: See Block 9
Phone
(End of Text)
G-242-H002 HOURS OF OPERATION AND HOLIDAY SCHEDULE (NAVSEA) (OCT 2018)
(a) The policy of this activity is to schedule periods of reduced operations or shutdown during holiday periods. Deliveries will not be accepted on Saturdays, Sundays or Holidays except as specifically requested by the [Not Applicable]. All goods or services attempted to be delivered on a Saturday, Sunday or Holiday without specific instructions from the Contracting Officer or his duly appointed representative will be returned to the contractor at the contractor’s expense with no cost or liability to the U.S. Government.
(b) The federal Government observes the following holidays:
HOLIDAYS*
New Year's Day
Martin Luther King's Birthday
Presidential Inauguration Day (Washington DC metro area only)
President's Day
Memorial Day
Juneteenth
Independence Day
Labor Day
Columbus Day
Veteran's Day
Thanksgiving Day
Christmas Day
* Except for the Presidential Inauguration Day, if the actual date falls on a Saturday, the holiday will be observed the preceding Friday. If the holiday falls on a Sunday, the observance shall be on the following Monday.
The actual date of observance for each of the above holidays, for a specific calendar year, may be obtained from the OPM website at OPM.GOV or by using the following direct link: https://www.opm.gov/policy-data-oversight/snow-dismissal-procedures/federal-holidays/#url.
(c) Delayed Opening, Early Dismissal and Closure of Government Facilities. When a Government facility has a delayed opening, is closed or Federal employees are dismissed early (due to severe weather, security threat, security exercise, or a facility related problem) that prevents personnel from working, onsite contractor personnel regularly assigned to work at that facility shall follow the same reporting and/or departure directions given to Government personnel. The contractor shall not direct charge to the contract for such time off, but shall follow parent company policies regarding taking leave (administrative or other). Non-essential contractor personnel, who are not required to remain at or report to the facility, shall follow their parent company policy regarding whether they should go/stay home or report to another company facility. Subsequent to an early dismissal, delayed opening, or during periods of inclement weather, onsite contractors should monitor the OPM website as well as radio and television announcements before departing for work to determine if the facility is closed or operating on a delayed arrival basis.
(d) When Federal employees are excused from work due to a holiday or a special event (that is unrelated to severe weather, a security threat, or a facility related problem), on site contractors shall continue working established work hours or take leave in accordance with parent company policy. Those contractor employees who take leave shall not direct charge the non-working hours to the contract. Contractors are responsible for predetermining and disclosing their charging practices for early dismissal, delayed openings, or closings in accordance with the FAR, applicable cost accounting standards, and the company’s established policy and procedures. Contractors shall follow their disclosed charging practices during the contract period of performance, and shall not follow any verbal directions to the contrary. The Contracting Officer will make the determination of cost allowability for time lost due to facility closure in accordance with FAR, applicable Cost Accounting Standards, and the Contractor's established accounting policy and procedures.
(e) If you intend to visit the Contracts Office, it is advised that you call for an appointment at least 24 hours in advance.
(f) The hours of operation are as follows:
AREA FROM TO
NSWC-PCD and/or NEDU 0700 1600*
(g) All deliveries to the Receiving Officer, (See Delivery Schedule, Section F), shall be made Monday through Friday from 0700 to 1600 local time, unless otherwise specified. Deliveries will not be accepted after 1600. No deliveries will be accepted on federal government holidays.
***Note*** Trucks must gain access to the base prior to 1430.
(End of text)
G-242-W001 CONTRACT ADMINISTRATION FUNCTIONS (NAVSEA) (OCT 2018)
(a) In accordance with FAR 42.302(a) all functions listed are delegated to the ACO except the following items to be retained by the PCO:
ALL functions listed will be retained by the PCO.
(b) In accordance with FAR 42.302(b), the following additional functions are delegated to the ACO: None
(End of Text)
L-204-H003 NOTIFICATION OF USE OF NAVY SUPPORT CONTRACTORS FOR OFFICIAL CONTRACT FILES (NAVSEA) (APR 2019)
(a) NAVSEA may use a contractor to manage official contract files hereinafter referred to as "the support contractor", including the official file supporting this procurement. These official files may contain information that is considered a trade secret, proprietary, business sensitive or otherwise protected pursuant to law or regulation, hereinafter referred to as “protected information”. File management services consist of any of the following: secretarial or clerical support; data entry; document reproduction, scanning, imaging, or destruction; operation, management, or maintenance of paper-based or electronic mail rooms, file rooms, or libraries; and supervision in connection with functions listed herein.
(b) The cognizant Contracting Officer will ensure that any NAVSEA contract under which these file management services are acquired will contain a requirement that
(1) The support contractor not disclose any information;
(2) Individual employees are to be instructed by the support contractor regarding the sensitivity of the official contract files;
(3) The support contractor performing these services be barred from providing any other supplies and/or services, or competing to do so, to NAVSEA for the period of performance of its contract and for an additional three years thereafter unless otherwise provided by law or regulation; and,
(4) In addition to any other rights the offeror may have, it is a third party beneficiary who has the right of direct action against the support contractor, or any person to whom the support contractor has released or disclosed Protected Information, for the unauthorized duplication, release, or disclosure of such Protected Information.
(c) Submission of a proposal will be considered as consent to NAVSEA's permitting access to any information, irrespective of restrictive markings or the nature of the information submitted, by its file management support contractor for the limited purpose of executing its file support contract responsibilities.
(d) NAVSEA may, without further notice, enter into contracts with other contractors for these services. Offerors are free to enter into separate non-disclosure agreements with the file support contractor. Contact the Procuring Contracting Officer for contractor specifics. However, any such agreement will not be considered a prerequisite before information submitted is stored in the files or otherwise encumber the government.
(End of Provision)
