N66001-17-R-0128.pdf
PDF 817 KB Posted
- Attached to
- Technical and Engineering Support Federal contract opportunity
- Solicitation number
- N66001-17-R-0128
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| RFP Attachment 5 - Small Business Commitment Sheet.docx | DOCX document | |
| RFP Attachment 2 - Rate Sheet.xlsx | XLSX spreadsheet | |
| RFP Attachment 3 - Desired Personnel Qualifications.docx | DOCX document | |
| N66001-17-R-0128 Q and A.docx | DOCX document | |
| RFP Attachment 7 - Reference Information Sheet.docx | DOCX document | |
| RFP Attachment 1 - DD254.pdf | ||
| N66001-17-R-0128-0001.pdf | ||
| RFP Attachment 6 - Org Exp Matrix.docx | DOCX document | |
| RFP Attachment 4 - Past Performance Questionnaire.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CODE
(Hour)
PAGE(S)
until 05:00 PM local t ime 28 Apr 2017
X
A X B X C
D
EX
X G F 78 - 90
91 - 107 X H 108 - 113 eric.pomroy@navy .mil
RATING PAGE OF PAGES
7. ISSUED BY
(Date)
IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.
Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)
Prescribed by GSA FAR (48 CFR) 53.214(c)
1 113
(If other than Item 7) N66001
15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO
AND
ADDRESS SIGN OFFER (Type or print)
OF
OFFEROR
AMENDMENT NO. DATE
15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS
IS DIFFERENT FROM ABOVE - ENTER
SUCH ADDRESS IN SCHEDULE.
18. OFFER DATE
1. THIS CONTRACT IS A RATED ORDER
UNDER DPAS (15 CFR 700)
2. CONTRACT NO.
N66001 8. ADDRESS OFFER TO
9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in
CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and
Section L conditions contained in this solicitation.
10. FOR INFORMATION
CALL:
A. NAME (NO COLLECT CALLS)
ERIC R. POMROY 619-553-3428
11. TABLE OF CONTENTS
SOLICITATION/ CONTRACT FORM
SUPPLIES OR SERVICES AND PRICES/ COSTS
2 - 6
X I CONTRACT CLAUSES
DESCRIPTION/ SPECS./ WORK STATEMENT X
PACKAGING AND MARKING
7 - 24 J LIST OF ATTACHMENTS
INSPECTION AND ACCEPTANCE
DELIVERIES OR PERFORMANCE
26 X K REPRESENTATIONS, CERTIFICATIONS AND
OTHER STATEMENTS OF OFFERORS
CONTRACT ADMINISTRATION DATA 27 - 32 X
SPECIAL CONTRACT REQUIREMENTS
OFFER (Must be fully completed by offeror) 33 - 44 X M
L INSTRS., CONDS., AND NOTICES TO OFFERORS
EVALUATION FACTORS FOR AWARD
NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.
is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.
13. DISCOUNT FOR PROMPT PAYMENT
(See Section I, Clause No. 52.232-8)
14. ACKNOWLEDGMENT OF AMENDMENTS
(The offeror acknowledges receipt of amendments
AMENDMENT NO. DATE
to the SOLICITATION for offerors and related documents numbered and dated):
FACILITY
12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period
SOLICITATION, OFFER AND AWARD
X
(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)
PART I - THE SCHEDULE
26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE
EMAIL:TEL: (Signature of Contracting Officer)
CODE CODE
B. TELEPHONE (Include area code) C. E-MAIL ADDRESS
AWARD (To be completed by Government)
19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION
22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:
10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)
23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM
24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE
PART IV - REPRESENTATIO NS AND INSTRUCTIO NS
PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS
45 - 76
PART II - CO NTRACT CLAUSES
SPAWAR SYSTEMS CENTER PACIFIC
ERIC POMROY, CODE 22550
ERIC.POMROY@NAVY.MIL
53560 HULL STREET
SAN DIEGO CA 92152-5001
SEE CLAUSE L-349
ELECTRONIC SUBMISSION
CA
619-553-3428
FAX:
TEL:
FAX:
TEL:
NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".
SOLICITATION
6. REQUISITION/PURCHASE NO.5. DATE ISSUED
29 Mar 2017
4. TYPE OF SOLICITATION
SEALED BID (IFB)
NEGOTIATED (RFP)
[ X ]
3. SOLICITATION NO.
N66001-17-R-0128
Section B - Supplies or Services and Prices
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
0001 1 Lot Engineering Services
CPFF
Provide services in accordance with the Performance Work Statement (see Section C) as specified in individual task orders.
FOB: Destination
ESTIMATED COST
FIXED FEE
TOTAL EST COST + FEE
0002 1 Lot Other Direct Costs (ODC)
COST
ODC including but not limited to travel, material, and equipment in support of
CLIN 0001
0003 Lot CDRLs
1001 1 Lot OPTION Engineering Services
CPFF
Provide services in accordance with the Performance Work Statement (see Section C) as specified in individual task orders.
FIXED FEE
TOTAL EST COST + FEE
1002 1 Lot Other Direct Costs (ODC)
COST
ODC including but not limited to travel, material, and equipment in support of
CLIN 1001
OPTION
1003 Lot OPTION CDRLs
CLAUSES INCORPORATED BY FULL TEXT
5252.216-9200 PAYMENT OF FIXED FEE (COMPLETION TYPE) (JAN 1989)
***This clause shall be used in completion type task orders.***
FIXED FEE: $ *. The Government shall make payment to the Contractor when requested as work progresses, but no more frequently than biweekly, on account of the fixed fee, equal to ** percent of the amounts invoiced by the Contractor under the “Allowable Cost and Payment” clause hereof for the related period, subject to the withholding provisions of paragraph (b) of the “Fixed Fee” clause. In the event of discontinuance of the work in accordance with clause of this contract entitled “Limitation of *** the fixed fee shall be redetermined by mutual agreement equitably to reflect the diminution of the work performed; the amount by which such fixed fee is less than, or exceeds payments previously made on account of fee, shall be paid, or repaid by, the Contractor, as the case may be.
*To be completed upon contract award.
**To be determined at the Task Order level. The allowable fee percentage will be negotiated in individual Task Orders and shall not exceed the negotiated percentage at the basic contract level.
***To be determined at the Task Order level.
(End of clause)
5252.216-9204 LEVEL OF EFFORT--FEE ADJUSTMENT FORMULA (MAR 1994)
***This clause shall be used in term/level-of-effort type task orders.***
(a) Subject to the provisions of the “Limitation of Cost” or “Limitation of Funds” clause (whichever is applicable to this contract), it is hereby understood and agreed that the fixed fee is based upon the Contractor providing the below listed number of staff-hours of direct labor, hereinafter referred to as X, at the estimated cost and during the term of this contract specified elsewhere herein:
[Contracting officer insert number of estimated direct labor staff hours]
CLIN Total Staff-hours of Direct Labor (X)
The Contractor agrees to provide the total level of effort specified above in performance of work described in Sections “B” and “C” of this contract. The total staff-hours of direct labor shall include subcontractor direct labor hours for those subcontractors identified in the Contractor’s proposal as having hours included in the proposed level of effort.
(b) Of the total staff-hours of direct labor set forth above, it is estimated that zero (0) staff-hours are competitive time (uncompensated overtime). Competitive time (uncompensated overtime) is defined as hours provided by personnel in excess of 40 hours per week without additional compensation for such excess work. All other effort is defined as compensated effort. If no amount is indicated in the first sentence of this paragraph, competitive time (uncompensated overtime) effort performed by the contractor shall not be counted in fulfillment of the level of effort obligations under this contract.
(c) Effort performed in fulfilling the total level of effort obligations specified above shall only include effort performed in direct support of this contract and shall not include time and effort expended on such things as local travel from an employee’s residence to their usual work location, uncompensated effort while on travel status, truncated lunch periods, or other time and effort which does not have a specific and direct contribution to the tasks described in Section B.
(d) It is understood and agreed that various conditions may exist prior to or upon expiration of the term of the contract, with regard to the expenditure of labor staff-hours and/or costs thereunder which may require adjustment to the aggregate fixed fee. The following actions shall be dictated by the existence of said conditions:
(1) If the Contractor has provided not more than 105% of X or not less than 95% of X, within the estimated cost, and at the term of the contract, then the fee shall remain as set forth in Section B.
(2) If the Contractor has provided X-staff-hours, within the term, and has not exceeded the estimated cost then the Contracting Officer may require the Contractor to continue performance until the expiration of the term, or until the expenditure of the estimated cost of the contract except that, in the case of any items or tasks funded with O&MN funds, performance shall not extend beyond 30 September. In no event shall the Contractor be required to provide more than 105% of X within the term and estimated cost of this contract. The fee shall remain as set forth in Section B.
(3) If the Contractor expends the estimated cost of the contract, during the term of the contract and has provided less than X staff-hours, the Government may require the Contractor to continue performance, by providing cost growth funding, without adjusting the fixed fee, until such time as the Contractor has provided X staff-hours.
(4) If the Contracting Officer does not elect to exercise the Government’s rights as set forth in paragraph (d)(2) and (d)(3) above, and the Contractor has not expended more than 95% of X staff-hours, the fixed fee shall be equitably adjusted downward to reflect the diminution of work.
(5) Nothing herein contained shall, in any way, abrogate the Contractor’s responsibilities, and/or the Government’s rights within the terms of the contract provision entitled “Limitation of Cost” or “Limitation of Funds” as they shall apply throughout the term of the contract, based upon the total amount of funding allotted to the contract during its specified term.
(e) Within 45 days after completion of the work under each separately identified period of performance hereunder, the Contractor shall submit the following information in writing to the Contracting Officer with copies to the cognizant Contract Administration Office and DCAA office to which vouchers are submitted:
(1) The total number of staff-hours of direct labor expended during the applicable period.
(2) A breakdown of this total showing the number of staff-hours expended in each direct labor classification and associated direct and indirect costs.
(3) A breakdown of other costs incurred.
(4) The Contractor’s estimate of the total allowable cost incurred under the contract for the period.
In the case of a cost under-run, the Contractor shall submit the following information in addition to that required above:
(5) The amount by which the estimated cost of this contract may be reduced to recover excess funds and the total amount of staff-hours not expended, if any.
(6) A calculation of the appropriate fee reduction in accordance with this clause.
All submissions required by this paragraph shall include subcontractor information, if any.
(f) SPECIAL INSTRUCTION TO THE PAYING OFFICE REGARDING WITHHELD FEE
Fees withheld pursuant to the provisions of this contract, such as the withholding provided by the “Allowable Cost and Payment” and “Fixed Fee” clauses, shall not be paid until the contract has been modified to reduce the fixed fee in accordance with paragraph (d) above, except that no such action is required if the total level of effort provided falls within the limits established in paragraph (d) above.
5252.216-9218 MINIMUM AND MAXIMUM QUANTITIES (JUL 1989)
As referred to in paragraph (b) of the “Indefinite Quantity” clause of this contract, the contract minimum quantity is a total of $10,000 per contract awardee. The maximum quantity is the total estimated amount of the contract. The maximum quantity is not to be exceeded without prior approval of the Procuring Contracting Officer.
The combined/overall ceiling for all awardees under this Multiple Award Contract is $***DETERMINED AT TIME OF AWARD***; however, no MAC awardee can exceed the value of its contract maximum quantity.
5252.232-9200 ALLOTMENT OF FUNDS (JAN 1989)
*** This clause shall be used in incrementally funded task orders.***
(a) This contract is incrementally funded with respect to both cost and fee.
(b) The amounts presently available and allotted to this contract for payment of fee, as provided in the Section I clause of this contract entitled “Fixed Fee”, are as follows:
[Contracting officer under “Items” insert the item numbers for which incremental funding is provided and under “Allotted to Fixed Fee” insert the amount of incremental funding allocated to fixed fee]
ITEM(S) ALLOTTED TO FIXED FEE
(c) The amounts presently available and allotted to this contract for payment of cost, subject to the Section I “Limitation of Funds” clause, the items covered thereby and the period of performance which it is estimated the allotted amount will cover are as follows:
[Contracting officer under “Items” insert the item numbers for which incremental funding is provided, under “Allotment of Cost” insert the amount of incremental funding allocated to total estimated cost, and under “Period of Performance” insert date by which funding expended]
ITEM(S) ALLOTTED TO COST PERIOD OF PERFORMANCE
(d) The parties contemplate that the Government will allot additional amounts to this contract from time to time by unilateral contract modification, and any such modification shall state separately the amounts allotted for cost and for fee, the items covered thereby, and the period of performance the amounts are expected to cover.
Section C - Descriptions and Specifications
PERFORMANCE WORK STATEMENT
PERFORMANCE WORK STATEMENT (PWS)
for the
Enterprise Communications and Networks Division 55300 Space and Naval Warfare Systems Center, Pacific
1.0 SCOPE:
The contractual support requirements of the Enterprise Communication and Networks Division (Code 55300), include technology insertion, software and systems engineering, modeling and simulation, installation and testing, and integrated logistics in support of communications, information technology, and other Command, Control, Communications, Computers, and Intelligence (C4I) efforts. To meet these overall mission responsibilities, support is required for these capabilities in the areas of Systems Engineering; Enterprise Architecture (EA), and a Systems of Systems approach to technical development; knowledge of the requirements definition process; technical knowledge in development of communications/networks equipment and system design and development; knowledge of installation practices for ship/shore sites; Human Systems Integration (HSI) techniques and Technical Writing.
An understanding of Joint and Coalition environment; technical specifications; design products for component / system/ ship / shore applications; issue papers to address technical issues based on requirements, standards, specifications and best practices; and a teaming solutions approach to problem solving.
Some examples of these areas are Nuclear Command, Control, and Communications (NC3), Common Submarine Radio Room (CSRR), Submarine Operating Authority (SUBOPAUTH), Command and Control Official Information Exchange (C2OIX), Minimum Essential Emergency Communications Network (MEECN), NOVA Information Exchange Terminal (NIXT), Low Band Universal Communications System (LBUCS) and OCONUS Navy Enterprise Network (ONE-Net), Navy Enterprise Network (NEN), Network System Administration (SYSADMIN), Undersea Enterprise Network (UEN), Forward Deployed Energy and Communications Outposts (FDECO), Optical Communications, Interoperable Communications Technical Assistance Program (ICTAP), and Homeland Security Operational Experiments.
Other agencies/activities outside the United States Navy, supported by Space and Naval Warfare Systems Center (SSC) Pacific, Code 55300, are NATO, the United States Air Force, Army, Marine Corps, Coast Guard Transportation Command (USTRANSCOM), Special Operations Command (USSOCOM), STRATCOM HQ, the Defense Advanced Research Projects Agency, National Security Agency (NSA), and the Department of Homeland Security.
2.0 APPLICABLE DOCUMENTS:
2.1 DoD 5000.01, “The Defense Acquisition System”, 12 May 2003
2.2 Dod 5000.02, “Operation of the Defense Acquisition System”, 8 December 2008
2.3 Guidebook for Performance-Based Services Acquisition (PBSA) in the Department of Defense, December
2.4 SPAWAR “Shore Installation Process Handbook”, Version 3.0, 19 October 2009
2.5 EIA-632, Processes for Engineering a System, January 1999
2.6 SECNAVINST 5000.2C, Implementation and Operation of the Defense Acquisition System and the Joint
Capabilities Integration and Development System, 19 November 2004.
2.7 IEEE Standard for Software Project Management Plans (IEEE 1058-1998), 8 December 1998
2.8 DoD Architecture Framework (DoDAF), version 2.0, May 2009
2.9 Guidebook for Acquisition of Naval Software Intensive Systems, Ver 1.0, dtd September 2008
2.10 ISO/IEC 15288:2008(E) (IEEE Std 15288-2008) Systems and Software Engineering – System Life Cycle
Process dtd 01 February 2008
2.11 IEEE Std 829-2008 Standard for Software and System Test Documentation, 18 July 2008
2.12 ISO/IEC 12207:2008(E)/IEEE Std 12207-2008 System and Software Engineering – Software Life Cycle Processes dtd 01 February 2008
2.13 Software Development Plan (Template), TM-SPP-02, V2.0, dtd 05 April 2005
2.14 Software Engineering Institute, Capability Maturity Model Integration (CMMI) Version 1.1 for System
Engineering, Software engineering, Integrated Product and Process Development, and Supplier Sourcing, CMU/SEI-2002-TR-012, dtd March 2002
2.15 Software Engineering Institute, Capability Maturity Model Integration (CMMI) for Services, Version 1.2, Improving Processes for Better Services, CMU/SEI-2009-TR-001, dtd February 2009
2.16 EIA 748-B, “Earned Value Management Systems”, June 2007
2.17 ASN RD&A Memorandum, “DON Policy on Digital Product/Technical Data, 23 October 2004
2.18 DoD 8570.01M, IA Work Force Improvement Program Manual, with Change 2, 04/20/2010
2.19 SECNAV Manual 5510.30, Department of Navy Personnel Security Program, June 2006
2.20 SECNAV Manual 5510.36, Department of Navy Information Security Program, June 2006
2.21 DOD 5200.01 Volumes 1 through 4, DOD Security Program, 24 February 2012
2.22 DOD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), 28 February 2006 with Change 1 28 March 2013
2.23 OPNAVINST F3300.53C, Navy Antiterrorism Program
2.24 National Security Decision Directive 298, National Operations Security Program (NSDD) 298, 22 January
2.25 DOD 5205.02, DOD Operations Security (OPSEC) Program, 3 November 1988
2.26 OPNAVINST 3432.1, DON Operations Security, 4 November 2011
2.27 SPAWARINST 3432.1 (Series), Operations Security Policy, 02 February 2005
2.28 DoD 8500.1 Cyber Security Program, 14 March 2014
Additional documents will be referenced in individual task orders as required.
3. TECHNICAL REQUIREMENTS:
3.1. Management Support
3.1.1. Integrated Product Team (IPT) Support
The contractor shall work with IPT lead and members to identify and prioritize tasks for the team; review progress;
participate in meetings; review, track and process action items; and provide assessments of the capabilities and deficiencies of the systems and vendors under review.
3.1.2. Program and System Management Support
The contractor shall support program and development efforts including assessing current and future system and software project requirements, analyzing changes and situations and developing, and proposing or recommending tentative approaches and solutions using a variety of tools, techniques, or processes. The contractor shall provide input to the analysis, identification, specification, and tracking of business opportunities. The contractor shall provide input for the preparation and presentation of briefing material and development of various program, system and business development documents. The contractor shall provide milestone support for major project efforts, facilitate and document project team activities, and provide input for business process modeling and reengineering.
Documentation produced or modified shall be maintained in the electronic folders resident on the local area network.
3.1.3. Technical and Management Reviews
The contractor shall attend technical and management support reviews and related meetings. Examples are design reviews, process and issues resolution meetings, reviews of program status, system/subsystem requirements and critical design, various plans (test description, test case, test results), test readiness, and meetings to define and update schedules and task estimates.
3.1.4. Project Planning and Oversight
The contractor shall provide project-related planning documents and perform oversight of the planned tasks subject to government review and approval.
3.1.5. Program Management Documents
The contractor shall provide program oversight documents, such as a management plan, plan of action and milestones, schedule and work breakdown structure. Participate in technical and programmatic reviews and meetings. Submit progress and status reports.
3.1.6. Risk Management
The contractor shall provide technical, cost, and schedule risk assessment.
3.2 Engineering Support
3.2.1. Software Engineering Support
The contractor shall perform systems evaluations, requirements reviews, or trade studies to determine where changes might be recommended to correct deficiencies, achieve cost savings, and/or improve operations. In support of this effort, the contractor shall provide product evaluations, security engineering, maintainability and reliability requirements, algorithms and protocols, and concept of operations.
3.2.2. Systems Engineering Support
The contractor shall perform systems evaluations, requirements reviews or trade studies to determine where changes might be recommended to correct deficiencies, achieve cost savings, and/or improve operations. In support of this effort, the contractor shall provide product evaluations, security engineering, maintainability and reliability requirements, algorithms and protocols, and operational concepts.
3.2.3. Modeling and Simulation Support
The contractor shall provide project level Modeling and Simulation (M&S) support to include, but not be limited to virtual M&S, M&S data extraction and analysis, and generation of test data/script/reports. The contractor shall provide M&S updates and maintenance.
3.2.4. Development Support
The contractor shall provide engineering, manufacturing, software and operational systems development support, including systems evaluations, design analysis, and hardware/software development using a documented processes such as the Capability Maturity Model, Integrated (CMMI) to ensure the quality and maintainability of designated systems.
3.2.5. Fleet Engineering Support
The contractor shall provide fleet engineering including on-call, on-site technical services on equipment/systems to provide site survey, development, installations, integration, troubleshooting, checkout, repair and test of communications and information network systems worldwide, as specified in individual task orders. The contractor shall develop, validate, and maintain drawing packages, drawing trees, “As-Built” drawings, and block diagrams using computer aided design software compatible with existing formats.
3.2.6. Test and Evaluation Support
The contractor shall investigate, design, code, implement and test enhancements to system support hardware/software. Test support shall include development, quality assurance, production, and postproduction testing of hardware/software to determine operational readiness, compliance to requirements, security posture, and effectiveness. The contractor may operate and maintain the test and evaluation facilities. The contractor shall perform systems validation (hardware/software) testing, repair, and modification and checkout prior to integration to ensure quality and operational availability to meet system security and readiness objectives. The contractor shall generate test systems, test procedures, test plans and test reports. The contractor shall develop System Operation and Verification Test (SOVT) packages and perform the SOVT to ensure satisfactory system operation, availability and readiness.
3.3 Integrated Logistics Support
The contractor shall perform Integrated Logistics Support planning and life cycle support, technical data support, training support, implementation support, supply support and configuration management. The contractor shall establish and keep current a maintainable program, including an implementation concept.
3.3.1. Data Management
The contractor shall perform data management activities. Examples of data management activities are consolidating, merging, correcting, revising, updating, incorporating comments, formatting, and maintaining a project technical library.
3.3.2. Configuration Management
The contractor shall perform configuration management activities. Examples of configuration management activities are identification of entities to be placed under configuration control, and assignment of a project-unique identifier to a Computer Software Configuration Item (CSCI) and each additional entity to be placed under configuration control, including documentation.
3.3.3. Configuration Status Accounting
The contractor shall record, update, and report the configuration status of all entities. The contractor shall maintain configuration records and master copies of delivered software end items for the duration of the contract. The contractor shall include, as applicable, the current version/revision/release of each entity, a record of changes to the entity being placed under project-level or higher configuration control, and the status of problem/change reports affecting the entity.
3.3.4. Technical Publication Support
The contractor shall develop and validate equipment/manufacturer technical manuals, and technical manual supplements to support operations. Delivery format for the publications developed may include Computer Based Training (CBT) and Interactive Electronic Technical Manuals (IETMs) or other electronic formats as specified in the task order.
3.3.5. Training Support
The contractor shall develop formal training course materials for both the organizational level and maintenance level. All course materials required for instruction for each course shall be developed and validated by the contractor. Delivery format for the developed training material may be in any format to include CBT, IETM or electronic format as specified in the task order. The contractor shall develop and conduct job skills-type training for systems/equipment following systems/equipment installations
3.3.6. Warehouse and Inventory Control Support
The contractor shall provide on-site services for equipment/systems. The contractor shall establish and maintain warehousing and inventory controls, using government-approved computer-based application software programs for all program material and equipment.
3.4 Interoperable Communications Technical Assistance
The contractor shall provide interoperable communications technical assistance to regional, state and territorial, tribal and local public safety organizations for the prevention of, response to, and recovery from terrorism and all hazardous events, particularly those involving chemical, biological, radiological, nuclear, and explosive incidents.
3.5 Homeland Security Operational Support
The contractor shall provide Subject Matter Experts (SMEs) to plan, conduct, assess, and report on experiments focused on homeland security techniques and technologies operating in real-world and exercise environments.
SMEs shall be cleared to conduct this task at the Sensitive Compartmented Information (SCI) classification level.
3.6 Software Engineering Approach
The contractor shall define a software development approach appropriate for the computer software effort to be performed under this contract. This approach shall be documented in a Software Development Plan (SDP) (see DID No. DI-IPSC-81427A for required format and content). Once defined, the contractor shall follow this SDP for all computer software to be developed or maintained under this contract.
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 contract.
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 Government can assess whether the offeror’s approach is viable.
The SDP shall contain the information defined by IEEE/EIA Std. 12207.1, section 5.2.1 (generic content) and the Plans or Procedures in Table 1 of IEEE/EIA Std. 12207.1. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include, as a minimum, specific standard, methods, tools, action, strategies, and responsibilities associated with development and qualification.
The contractor’s software engineering approach shall afford opportunities for input and oversight by the Government.
4.0 CYBERSECURITY COMPLIANCE
Cybersecurity (which replaced the term Information Assurance (IA)) is defined as prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. Contractor personnel shall perform tasks to ensure Navy applications, systems, and networks satisfy Federal/DoD/DON/Navy cybersecurity requirements.
4.1 CYBER IT AND CYBERSECURITY PERSONNEL
(a) The Cyberspace workforce elements addressed include contractors performing functions in designated Cyber IT positions and Cybersecurity positions. In accordance with DFARS Subpart 239.71, DoDD 8140.01, SECNAVINST
5239.20A, and SECNAV M-5239.2, contractor personnel performing cybersecurity functions shall meet all cybersecurity training, certification, and tracking requirements as cited in DoD 8570.01-M prior to accessing DoD information systems. Proposed contractor Cyber IT and cybersecurity personnel shall be appropriately qualified prior to the start of the contract performance period or before assignment to the contract during the course of the performance period.
(b) The contractor shall be responsible for identifying, tracking and reporting cybersecurity personnel, also known as Cybersecurity Workforce (CSWF) and Cyber IT workforce personnel. Although the minimum frequency of reporting is monthly, the task order can require additional updates at any time.
(c ) Contractors that access Navy IT shall also follow guidelines and provisions documented in Navy Telecommunications Directive (NTD 10-11) and are required to complete a System Authorization Access Request (SAAR) – Navy form.
When a contractor requires logical access to a government IT system or resource (directly or indirectly), the required CAC will have a Public Key Infrastructure (PKI). A hardware solution and software (e.g., ActiveGold) is required to securely read the card via a personal computer. Pursuant to DoDM 1000.13-M-V1, CAC PKI certificates will be associated with an official government issued e-mail address (e.g. .mil, .gov, .edu). Prior to receipt of a CAC with PKI, contractor personnel shall complete the mandatory Cybersecurity Awareness training and submit a signed System Authorization Access Request Navy (SAAR-N) form to the contract’s specified COR. Note: In order for personnel to maintain a CAC with PKI, each contractor employee shall complete annual cybersecurity training. The following guidance for training and form submittal is provided; however, contractors shall seek latest guidance from their appointed company Security Officer and the SSC Pacific Information Assurance Management (IAM) office:
1. For annual DoD Cybersecurity/IA Awareness training, contractors shall use this site:
https://twms.nmci.navy.mil/. For those contractors requiring initial training and do not have a CAC, contact the SSC Pacific IAM office at phone number (619)992-5211 or e-mail questions to ssc_pac_iatraining@navy.mil for additional instructions. Training can be taken at the IAM office or online at http://iase.disa.mil/index2.html.
2. For SAAR-N form, the contractor shall use OPNAV 5239/14 (Rev 9/2011). Contractors can obtain a form from the SSC Pacific IAM office at or from the website: https://navalforms.documentservices.dla.mil/. Digitally signed forms will be routed to the IAM office via encrypted e-mail to roc@spawar.navy.mil.
(d) Contractor personnel with privileged access will be required to acknowledge special responsibilities with a Privileged Access Agreement (PAA) IAW SECNAVINST 5239.20A.
4.2 DESIGN, INTEGRATION, CONFIGURATION OR INSTALLATION OF HARDWARE AND
SOFTWARE
The contractor shall ensure any equipment/system installed or integrated into Navy platform will meet the cybersecurity requirements as specified under DoDI 8500.01. The contractor shall ensure that any design change, integration change, configuration change, or installation of hardware and software is in accordance with established DoD/DON/Navy cyber directives and does not violate the terms and conditions of the accreditation/authorization issued by the appropriate Accreditation/Authorization official. Contractors that access Navy IT are also required to follow the provisions contained in DON CIO Memorandum: Acceptable Use of Department of the Navy Information Technology (IT) dtd 12 Feb 16. Use of blacklisted software is specifically prohibited and only software that is registered in DON Application and Database Management System (DADMS) and is Functional Area Manager (FAM) approved can be used as documented in para 5.2.2. Procurement and installation of software governed by DON Enterprise License Agreements (ELAs) – Microsoft, Oracle, Cisco, Axway, Symantec, ActivIdentity, VMware, Red Hat, NetApp, and EMC shall be in accordance with DON CIO Policy and DON ELAs awarded.
4.3 CYBERSECURITY WORKFORCE (CSWF) REPORT
DoD 8570.01-M and DFAR’s PGI 239.7102-3 have promulgated that contractor personnel shall have documented current cybersecurity certification status within their contract. The contractor shall develop, maintain, and submit a CSWF Report as applicable at the task order level. IAW clause DFARS 252.239-7001, if cybersecurity support is provided, the contractor shall provide a Cybersecurity Workforce (CSWF) list that identifies those individuals who are IA trained and certified. Utilizing the format provided at the task order level , the prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor personnel. See applicable DD Form 1423 for additional reporting details and distribution instructions. Contractor shall verify with the COR or other government representative the proper labor category cybersecurity designation and certification requirements.
5.0 INFORMATION TECHNOLOGY (IT) SERVICES REQUIREMENTS
This paragraph only applies to IT contracts. Information Technology (IT) is defined as any equipment or interconnected system(s) or subsystem(s) of equipment, that is used in the automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data of information by the agency. IT includes computers, ancillary equipment, peripherals, input, output, and storage devices necessary for security and surveillance. Electronic and Information technology (EIT) is IT that is used in the creation, conversion, or duplication of data or information. EIT includes: telecommunication products, such as telephones; information kiosks; transaction machines; World Wide Web sites; multimedia (including videotapes); and office equipment, such as copiers and fax machines.
5.1 INFORMATION TECHNOLOGY (IT) GENERAL REQUIREMENTS
When applicable, the contractor shall be responsible for the following:
• Ensure that no production systems are operational on any RDT&E network.
• Follow DoDI 8510.01 of 12 Mar 2014 when deploying, integrating, and implementing IT capabilities.
• Migrate Navy Ashore production systems to the NMCI environment where available.
• Work with government personnel to ensure compliance with all current Navy IT & cybersecurity policies, including those pertaining to Cyber Asset Reduction and Security (CARS).
• Follow SECNAVINST 5239.3B of 17 June 2009 & DoDI 8510.01 of 12 Mar 2014 prior to integration and implementation of IT solutions or systems.
• Register any contractor-owned or contractor-maintained IT systems utilized on contract in the Department of Defense IT Portfolio Registry (DITPR)-DON.
• Only perform work specified within the limitations of the contract/task order.
5.2 ACQUISITION OF COMMERCIAL SOFTWARE PRODUCTS, HARDWARE, AND RELATED
SERVICES
This paragraph only applies to the purchasing/hosting of commercial software. Contractors recommending or purchasing commercial software products, hardware, and related services supporting Navy programs and projects shall ensure they recommend or procure items from approved sources in accordance with the latest DoN and DoD policies.
5.2.1 DON ENTERPRISE LICENSING AGREEMENT/DOD ENTERPRISE SOFTWARE INITIATIVE
PROGRAM
Pursuant to DoN Memorandum – Mandatory use of DoN Enterprise Licensing Agreement (ELA) dtd 22 Feb 12, contractors that are authorized to use Government supply sources per FAR 51.101 shall verify if the product is attainable through DoN ELAs and if so, procure that item in accordance with appropriate ELA procedures. If an item is not attainable through the DoN ELA program, contractors shall then utilize DoD Enterprise Software Initiative (ESI) program (see DFARS 208.74) and government-wide SmartBuy program (see DoD memo dtd 22 Dec 05). The contractor shall ensure any items purchased outside these programs have the required approved waivers as applicable to the program. Software requirements will be specified at the task order level.
5.2.2 DON APPLICATION AND DATABASE MANAGEMENT SYSTEM (DADMS)
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 DoN Application 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. No operational systems or applications will be integrated, installed, or operational on the RDT&E network.
5.3 SECTION 508 COMPLIANCE
This paragraph only applies to IT contracts. The contractor shall ensure that all software recommended, procured, and/or developed is compliant with Section 508 of the Rehabilitation Act of 1973, 26 CFR Part 1194 and pursuant to SPAWARINST 5721.1B of 17 Nov 2009. 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.
5.4. SOFTWARE DEVELOPMENT/MODERNIZATION AND HOSTING
This paragraph only applies to software development and modernization. The contractor shall ensure all programs utilizing this contract for software development/ modernization (DEV/MOD), including the development of IT tools to automate SSC Pacific business processes are compliant with DON Information Management/Information Technology (DON IM/IT) Investment Review Process Guidance requirements. Contractors shall neither host nor develop IT tools to automate SSC Pacific business processes unless specifically tasked within the task order or contract. The contractor shall ensure IT tools developed to automate SSC Pacific business processes will be delivered with full documentation and source code, as specified at the task order level, to allow non-proprietary operation and maintenance by any source. The contractor shall ensure all programs are submitted with proof of completed DEV/MOD certification approval from the appropriate authority in accordance with DON policy prior to task order award. *Note must be listed on Investment Review Board (IRB) approved list.
5.5 INFORMATION SECURITY
Pursuant to DoDM 5200.01, 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.
The contractor shall disseminate unclassified DoD information within the scope of assigned duties and with a clear expectation that confidentiality is 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).
5.6 IT POSITION CATEGORIES
Pursuant to DoDI 8500.01, DoD 8570.01-M, SECNAVINST 5510.30, SECNAV M-5239.2, and applicable to unclassified DoD information systems, a designator is 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, SECNAVINST 5510.30 and SECNAV M-5510.30, three basic DoN IT levels/Position categories exist:
• IT-I (Privileged access)
• IT-II (Limited Privileged, sensitive information)
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 Single-Scope Background Investigation (SSBI)/Tier 5, SSBI Periodic Reinvestigation (SSBI-PR)/Tier 5R, and National Agency Check (NAC)/Tier 3R adjudication will be performed Pursuant to DoDI 8500.01 and SECNAVINST 5510.30.
Requests for investigation of contractor personnel for fitness determinations or IT eligibility without classified access are submitted by SPAWAR/SSC Atlantic/SSC Pacific Security Office, processed by the OPM, and adjudicated by DOD CAF. IT Position Categories are determined based on the following criteria:
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 adjudication of Single Scope Background Investigation (SSBI)/Tier 5 or SSBI-PR/Tier 5R. The SSBI/Tier 5 or SSBI-PR/Tier 5R is updated a minimum of every 5 years. Assignment to designated IT-I positions requires U.S. citizenship unless a waiver request is approved by CNO.
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 adjudication of a Position of Trust National Agency Check with Law and Credit (PT/NACLC)/Tier 3R. Assignment to designated IT-II positions requires U.S. citizenship unless a waiver request is approved by CNO.
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 adjudication of a Position of Trust National Agency Check with Written Inquiries (PT/NACI).
6.0 REPORTS, DATA AND DELIVERABLES
Reports, technical data, and computer software delivery requirements shall be specified through use of a Contract Data Requirements Lists, DD From 1423, at the individual delivery/task order level.
The contractor shall provide hardware/prototype deliverables as specified in individual delivery/task orders.
All classified deliverables shall be protected and handled in accordance with standard security practices and procedures.
7.0 INFORMATION ASSURANCE (IA)/CYBERSECURITY WORKFORCE (CSWF)
All IA/CSWF functions to be performed under this contract will be identified at the task order level in the performance work statement. Task order performance work statements will specify, as applicable, IA/CSWF category, level, training, and certification requirements for contractor personnel with privileged access working in IA/CSWF Technical (IAT) environments, IA/CSWF Management (IA/CSM) personnel with significant IA/CSWF tasks, Computer Network Defense Service Providers (CND-SPs), and IA/CSWF Systems Architects and Engineers (IASAEs). Task orders with IA/CSWF functions will include a requirement for the contractor to report IA/CSWF certification status and compliance.
8.0 SECURITY REQUIREMENTS
The nature of some of the tasking on this contract will requires access to Secret information. The work performed by the Contractor will include access to unclassified and up to Top Secret/incidental Sensitive Compartmented Information (SCI) data, information, and spaces. The Contractor will be required to attend meetings classified up to Top Secret/SCI level, have access to Communications Security (COMSEC) equipment, and access the Secure Internet Protocol Router Network (SIPRNet), the Joint Worldwide Intelligence Communications System (JWICS), and the NSAnet. The contractor shall be North Atlantic Treaty Organization (NATO) briefed and complete the derivative classification training prior to being granted access to SIPRNet/JWICS/NSAnet; training is provided by the facility security officer. National Agency Check with Local Agency Checks and Credit Check (NACLC) will be completed for a Secret Clearance.
Contractor personnel assigned to this effort who require access to SCI data and spaces must possess a current SSBI with ICD 704 eligibility (which replaced DCID 6/4 eligibility).
If foreign travel is required, all outgoing Country/Theater clearance message requests shall be submitted to Commanding Officer, Attn: Foreign Travel Team, Space and Naval Warfare Systems Center Pacific, 53560 Hull Street, Building 27, 2nd Floor -Room 206, San Diego, CA 92152 for action. A Request for Foreign Travel form shall be submitted for each traveler, in advance of the travel, to initiate the release of a clearance message at least 30 days in advance of departure.
Each Traveler must also submit a Personal Protection Plan and have a Level 1 Antiterrorism/Force Protection briefing within one year of departure and a country specific briefing within 90 days of departure. Anti- Terrorism/Force Protection (AT/FP) briefings are required for all personnel (Military, DOD Civilian, and contractor) per OPNAVINST F3300.53C. Contractor employees must receive the AT/FP briefing annually. The briefing is available at Joint Knowledge Online (JKO): https://jkodirect.jten.mil (prefix): course number: US007; title: Level 1 Anti-terrorism Awareness Training, if experiencing problems accessing this website contact ssc_fortrav@navy.mil.
Forward a copy of the training certificate to the previous email address or fax to (619) 553-6863.
Sere 100.2 Level A code of conduct training is also required prior to Oconus travel for all personnel. Sere 100.2 Level A training can be accessed at http://jko.jfcom.mil (recommended), https://jkodirect.jten.mil/atlas2/faces/page/login/login.seam, recommended course: prefix: J3T: course #: A-US1329, for civilian, military, and contractors. Personnel utilizing this site must have a CAC. A Sere 100.2 Level A training disk can be borrowed at the SSC Pacific Point Loma Office or Old Town Campus Office. Specialized training for specific locations, such as SOUTHCOM human rights, or U.S. forces Korea entry training, may also be required;
SSC Pacific security personnel will inform you if there are additional training requirements.
Finally, EUCOM has mandated that all personnel going on official travel to the EUCOM AOR must now register with the Smart Traveler Enrollment Program (STEP).
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it.