N00421-16-R-0059_Amendment_0001_-_Modification.pdf
PDF 994 KB Posted
- Attached to
- AIR-4. 11, N00421-16-R-0059 Technical and Engineering Services (TES) supporting AD-4. 11. 3
- Solicitation number
- N00421-16-R-0059
About this file
N00421-16-R-0059 Amendment 0001 - Modification
View the file
Other files
Show all 40
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83)
Prescribed by GSA
FAR (48 CFR) 53.243
The purpose of this amendment is to modify the solicitation and provide answ ers to Industy's questions submitted betw een 01 December
2017 and 13 December 2017.
1. CONTRACT ID CODE PAGE OF PAGES
U 1 75
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 14-Dec-2017
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00421-16-R-0059
X 9B. DATED (SEE ITEM 11)
30-Nov-2017
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE
RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN
REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
14-Dec-2017
CODE
NAVAL AIR WARFARE CENTER AD
CODE 2.5.1.3, BLDG 433, 47060 LILJENCRANTZ RO
PATUXENT RIVER MD 20670
N00421 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
N00421-16-R-0059
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION A - SOLICITATION/CONTRACT FORM
The following have been added by full text:
AMENDMENT #0001
Changes made to Solicitation N00421-16-R-0059 and responses to questions from industry via Amendment 0001 are outlined below. The proposal due date and time have not changed; all submissions shall be in accordance with
Block 9 of the Solicitation coverpage.
Questions and Answers
Q1: Due to the length and complexity of the SOW, and to ensure offerors have the space to thoroughly address each required element of the PWS/SOW Approach (per Section 1.1.1) and fully demonstrate the offeror’s understanding and capabilities, can the Government increase the respective page count from 30 pages to 40 pages for Section 1.1.1 (Understanding of the Work PWS/SOW Approach)?
A1: The page limit has been increased from 30 to 40 pages in Section L, L-1, Content of Proposals, Part A, 3.0
Proposal Content and Volumes, paragraph 3.3, volume 1, Section 1.1.1 (Understanding of the Work PWS/SOW
Approach) as of Amendment 0001.
Q2: On page 125, under 5252.209-9513 ORGANIZATIONAL CONFLICT OF INTEREST INSTRUCTIONS
(SERVICES) (NAVAIR)(JUN 1993), sub-clause (a) states, “In accordance with FAR 9.507-1, the potential conflict of interest for this solicitation in the Contracting
Officer's judgment would involve any prime contractor, subcontractor, co-sponsor, parties to a joint venture, consultant or other legal entity (1) who because of activities or relationships is unable to render impartial assistance or advice to the Government, or (2) whose objectivity in performing the contemplated contract work is or might otherwise be impaired, or (3) who has an unfair competitive advantage in regards to [Insert description of weapons system involved and contractor activities that are suspect, i.e., drafting specifications, planning requirements etc.].”
Will this sub-clause be completed upon award? If not, can the Government provide a description of weapons systems/activities of concern to permit an OCI review?
A2: 5252.209-9513 ORGANIZATIONAL CONFLICT OF INTEREST INSTRUCTIONS
(SERVICES)(NAVAIR)(JUN 1993), sub-clause (a) has been updated in Section L as of Amendment 0001.
Q3: On page 125, under 5252.209-9513 ORGANIZATIONAL CONFLICT OF INTEREST INSTRUCTIONS
(SERVICES) (NAVAIR)(JUN 1993), sub-clause (e) states, “Along with responses to this solicitation, offerors must either (1) submit the following information concerning any existing or planned contracts with, or interests in, the suppliers and/or equipment identified in Attachment [Insert attachment number]; ….”.
Can the Government confirm the reference attachment is Attachment 4, or provide the correct attachment number?
A3: 5252.209-9513 ORGANIZATIONAL CONFLICT OF INTEREST INSTRUCTIONS
(SERVICES)(NAVAIR)(JUN 1993), sub-clause (e) has been updated in Section L as of Amendment 0001.
Q4: Are you using the 2010 SOC definitions or the 2018 SOC definitions?
A4: The Government confirms use of the 2010 SOC definitions.
Q5: Can the offeror adjust formulas in Attachment P6 and P7 spreadsheets to ensure compliance with DCAA disclosures and estimating practices? For example, overhead is not being applied to direct labor plus fringe, and FCCM is a required field and when entered with zero the Grand Total Cost does not carry down.
A5: The offeror may adjust formulas in Attachment P6 and P7 spreadsheets to ensure compliance with DCAA disclosures and estimating prices.
Q6: Within the RFP, the requirement is to propose approximately 40 percent of the level of effort for each labor category at Government site and approximately 60 percent at the contractor site. Most offerors have different indirect rates for Government and contractor facilities along with a very specific disclosed practice for utilizing a Government-site cost center. A single individual, such as a Program Manager, can only be aligned to one cost center. Can the government confirm that the intent of providing our cost per RFP instructions is to assist in developing composite rates to support the new task order issuance process, and that during execution an individual will only be required to be billed in one cost center as per DCAA compliance requirements?
A6: The Government acknowledges that the intent of the Contractor providing fully burdened composite rates is to develop estimated labor ceilings to support new task order issuance and during execution. However, an individual will only be required to be billed in one cost center as per DCAA compliance requirements.
Q7: Who is the incumbent contractor?
A7: Please refer to Section L, L-1, Content of Proposals, Part B, 3.0 Volume 3: Price/Cost Proposal, 3.5
Government Furnished Information, subparagraph 3.5.4.
Q8: The current SCA Labor Category Qualifications do not list any education, certification, or experience requirements. From which source should the SCA Labor Category Qualification requirement for education, certification, and experience be derived?
A8: SCA Labor Category Qualifications have been mapped to the Office of Management and Budget’s (OMB)
Standard Occupational Classification (SOC).
Q9: The RFP only included off-site hours for the two new labor categories (Information Security Analyst
Junior and Engineer Junior), which changes the Government/Contractor site split to 39%/61%. This differs from the stated split of 40%/60% in Section 3.1.2.1. Can the percentages in Section 3.1.2.1 be updated, or can the hours for junior LCATS be adjusted to reflect the stated 40%/60% split?
A9: Section C, 3.0 REQUIREMENTS, paragraph 3.1.2, subparagraph 3.1.2.1 has been updated to reflect a split of
39%/61% between work performed at Government sites and work to be performed at the Contractor site as of
Amendment 0001.
Q10: For the Past Performance volume, it is not clear whether contracts that do not adhere explicitly to the magnitude relevancy factors provided will be considered in the evaluation. How will contracts exceeding the specified $100 million threshold be evaluated?
A10: The government will consider all contracts provided.
Q11: Are the 2 pages for each key resume in addition to the 10 page limit for the Workforce section?
A11: The Government confirms the 2 pages are for each Key Personnel resume in addition to the 10 page limit for the workforce section.
Q12: The planned award date is October 2018, but three dates provided in Section F under Delivery
Information all reference CLINs commencing earlier in 2018. Can the Government update the dates provided in Section F to fall within the anticipated periods of performance?
A12: Delivery Dates in Section F have been updated to fall within the anticipated periods of performance as of
Q13: There are multiple references to PWS/SOW Section 3.3.6. However, Section 3.3.6 does not exist in the
RFP. References include both performance-based tables on page 4 and both performance-based tables on page 121. Can the Government please confirm that Section 3.3.6 does not exist in the PWS/SOW and references to section 3.3.6 in the performance-based tables on page 4 and both performance-based tables on page 121 are in error?
A13: PWS/SOW Section 3.3.6 does not exist and has been removed from both (Performance Based) Section B, Composite Fully Burdened Rate tables and Section L, L-1, Content of Proposals, Part B, 3.0 Volume 3: Price/Cost
Proposal, paragraph 3.5.2 tables as of Amendment 0001.
Q14: There are multiple references to Section 3.3.1, “Concept and Technology Development,” that do not align with the updated “Requirements Decomposition” title on page 27 of the PWS. These references include
Section 1.1.1.1 on page 111 of the PWS; the Relevancy Factors table on page 129 of the PWS; the Quality
Standards table on page 5 of the QASP attachment; and the Quarterly Evaluation table on page 15 of the
QASP attachment. Can the Government adjust the RFP to address the inconsistency?
A14: The RFP has been revised to replace “Section 3.3.1, “Concept and Technology Development” with
“Requirements Decomposition” in Section L, L-1, Content of Proposals, Part B, 1.0 VOLUME 1: TECHNICAL, paragraph 1.1, subparagraph 1.1.1.1, Section M, M-1 Evaluation Factors For Award (Services), PART B, paragraph
2.0 Past Performance Relevance Factors Table, Attachment 8 – QASP, Enclosure (1): Quality Standards – In-
Service Engineering by PWS (Level of Effort) Table, and Attachment 8 – QASP, Enclosure (4): Surveillance
Activity Checklist – Level of Effort & Performance Based Table.
Q15: Several areas of the RFP reference that PWS/SOW sections 3.3.3 (System Integration and Life-Cycle
Support) and 3.3.5 (Cybersecurity) will be executed against CLINS 0008-0014 (completion CLINS).
However, the LCAT listing provided in Section L for pricing does not reflect LCATs normally associated with Systems Integration, Life Cycle Support or Cybersecurity work. Can the government evaluate if those
CLIN references are as intended or if the right LCATs are included in the LOE tables provided?
A15: The labor categories have been revised as shown in the B-1 Estimated Rates Performance Based OFF-SITE and ON-SITE tables, Attachment P6, Attachment P7, and Section L, L-1, Content of Proposals, Part B, 3.0 Volume
3: Price/Cost Proposal, paragraph 3.5.2 tables as of Amendment 0001.
Q16: On page 83, Clause 5252.228-9501 Liability Insurance (NAVAIR) (MAR 1999) paragraph (d) requires:
(d) Aircraft public and passenger liability: $200,000 per person and $500,000 per occurrence for bodily injury, other than passenger liability; $200,000 per occurrence for property damage. Passenger bodily injury liability limits of $200,000 per passenger, multiplied by the number of seats or number of passengers, whichever is greater.
A16: Clause 5252.228-9501 Liability Insurance (NAVAIR) (MAR 1999) paragraph (d) has been updated in Section
H to reflect a removal of all values.
Q17: Section L requires each volume to be submitted in a separated binder, with tabs. The table provided appears to indicate Annexes be bundled in separate binders as well. Can the Government please confirm if a separate binder is requested for each annex, or should it be provided in the same binder as the corresponding volume for the annex.
A17: The Government requires a separate binder be used for each annex.
Q18: The RFP does not provide a requirement for an acronym list. Is an acronym list desired? If so, can provisions be made in the instruction such that the acronym list does not count against provided page limitations.
A18: Section L, L-1, Content of Proposals, Part A, Paragraph 3.2 has been updated to include acronym lists not counting towards the page limit.
Q19: The labor categories for Program/Project Analyst Journeyman and Senior both require a degree in a technical discipline. Given the function outlined for these labor categories, would the Government consider adding “Business Administration or a related Business field” as an acceptable degree for these two labor categories?
A19: “Business Discipline” has been added to both the Program/Project analyst Journeyman and Senior labor categories in Section C, PWS/SOW, paragraph 3.4.12(p) and paragraph 3.4.12(q) as an acceptable degree as of
Q20: Will the Government allow 10 pt. font for tables and graphics?
A20: As stated in Section L, Part A General Instructions, 2.0 Proposal Format, paragraph 2.1, Graphs and Tables shall be presented in no smaller than a 10 pt. font.
Additional Changes made by the Government:
1) Section B: Added B-2 Fee text for Non-Performance Based (Level of Effort) and Performance Based
(Completion) fee.
2) Section C, 3.0 REQUIREMENTS, paragraph 3.1.2, subparagraph 3.1.2.1 has been updated to reflect work performed at NAS Patuxent River at 4% as of Amendment 0001.
3) Section C: Business Discipline definition has been added to Section C, PWS/SOW, 3.0 Requirements, 3.4
Labor Category Definition, 3.4.5 Degree Majors, 3.4.5.3.
4) Section J: P3 (reference) was deleted.
5) Section J: Attachment P4 is updated to include additional instructions and an additional tab for contractor input of fee per hour and fee percentage.
6) Section J: Attachment P6 is revised to include additional labor categories under Completion CLINs 0008-0014
7) Section L: L-1, Content of Proposals, Part B, 3.0 Volume 3: Price/Cost Proposal, paragraph 3.3.3, subparagraph
3.3.3.1, 3.3.3.2, and 3.3.3.3 have been added.
8) All NAVAIR Clauses have been updated to full-text.
9) Section L: Clause 52.233-2, code 2.1.5.3 has been changed to 2.5.1.3.
10) Section M, M-1 Evaluation Factors For Award (Services), PART B, paragraph 2.0, is revised to include updated language pertaining to Past Performance evaluations.
SECTION B - SUPPLIES OR SERVICES AND PRICES
The following have been added by full text:
B-2 FEE
Non-Performance Based (Level of Effort) - For non-performance based level of effort tasks the composite rates from B-1 will be used to develop the total estimated cost plus fixed fee. Fixed fee will be calculated based on fee per hour. The fee per hour is the total fee proposed for all periods divided by the total number of hours for all periods (830,400). The non-performance based fee per hour is $_______.
Performance Based (Completion) - For performance based (completion) tasks the composite rates from B-1 will be used to develop the total estimated cost plus fixed fee. Fixed fee will be calculated based on the percentage of total fee proposed for all periods divided by the total proposed cost for all periods. The performance based (completion) fee percentage is _____%.
The following have been modified:
B-1 ESTIMATED RATES
B-1 ESTIMATED AND NEGOTIATED LABOR RATES
This language is designed for use in conjunction with H-2 Issuance of Orders Using Streamlined Procedures
NAVAIR 5252.216-9540 (Variation) (Jul 2017). The below rates consist of composite fully burdened rates for each key and non-key labor categories, inclusive of fee. Fully burdened rates are defined as direct labor rates plus all applicable burdens, to include indirect rates, fee, and subcontractor pass-through costs where applicable. The rates below will be utilized when developing estimated labor ceilings for task orders by using the estimated hours per labor category multiplied by the composite rate. Invoicing will be based on actual costs incurred. Ceiling for Other
Direct Costs will be priced in accordance with the Government Estimate. Orders crossing multiple years will be estimated by the Government using the composite rates for each year in proportion to the period of performance of the order.
Non-Performance Based (PWS/SOW 3.3.1-3.3.5) OFF-SITE
COMPOSITE FULLY BURDENED RATES (regardless of clearance or whether or not Key) Labor Category Year 1 Year 2 Year 3 Year 4 Year 5
OFF-SITE (Contractor Facility)
10/29/2018-
10/30/2019**
10/29/2019-
10/30/2020**
10/29/2020-
10/30/2021**
10/29/2021-
10/30/2022**
10/29/2022-
10/30/2023**
Program/Project Analyst, Journeyman Program/Project Analyst, Senior Computer Programmer I (SCA) Computer Programmer II (SCA) Computer Programmer III (SCA) Drafter/CAD Operator II (SCA)
Electrical and Electronic Engineering Technician
(Electronics Technician Maintenance III) (SCA)
Electrical Engineer, Senior Mechanical Engineer, Senior Administrative Assistant (SCA) Information Security Analyst, Junior Information Security Analyst, Journeyman Information Security Analyst, Senior Logistician, Journeyman Manager/Operations Manager, Senior (Project Manager) Computer Network Architect, Journeyman Computer Network Architect, Senior Software Developer, Senior (Software Engineer, Senior) Computer Systems Analyst, Journeyman Computer Systems Analyst, Senior
Engineer, Junior (Systems Engineer) Engineer, Journeyman (Systems Engineer) Engineer, Senior (Systems Engineer) Software Developer, Senior (Systems Specialist) Technical Writer (Technical Writer II) (SCA)
** Dates to be adjusted at contract award (SCA) Service Contract Act
Non-Performance Based (PWS/SOW 3.3.1-3.3.5) ON-SITE
Labor Category Year 1 Year 2 Year 3 Year 4 Year 5
ON-SITE (St. Inigoes, MD)
10/29/2018- 10/30/2019**
10/29/2019- 10/30/2020**
10/29/2020- 10/30/2021**
10/29/2021- 10/30/2022**
10/29/2022- 10/30/2023**
Program/Project Analyst, Journeyman Program/Project Analyst, Senior Computer Programmer I (SCA) Computer Programmer II (SCA) Computer Programmer III (SCA) Drafter/CAD Operator II (SCA)
Administrative Assistant (SCA) Information Security Analyst, Journeyman Information Security Analyst, Senior Logistician, Journeyman Manager/Operations Manager, Senior (Project Manager) Computer Network Architect, Journeyman Computer Network Architect, Senior Software Developer, Senior (Software Engineer, Senior) Computer Systems Analyst, Journeyman Computer Systems Analyst, Senior Engineer, Journeyman (Systems Engineer) Engineer, Senior (Systems Engineer) Software Developer, Senior (Systems Specialist) Technical Writer (Technical Writer II) (SCA)
Performance Based (PWS/SOW 3.3.5) OFF-SITE
Labor Category Year 1 Year 2 Year 3 Year 4 Year 5
OFF-SITE (Contractor Facility) 10/29/2018-
10/30/2019**
10/29/2019-
10/30/2020**
10/29/2020-
10/30/2021**
10/29/2021-
10/30/2022**
10/29/2022-
10/30/2023**
Program/Project Analyst, Journeyman Program/Project Analyst, Senior Computer Programmer I (SCA) Computer Programmer II (SCA) Computer Programmer III (SCA) Drafter/CAD Operator II (SCA)
Administrative Assistant (SCA) Information Security Analyst, Journeyman Information Security Analyst, Senior Logistician, Journeyman Manager/Operations Manager, Senior (Project Manager) Computer Network Architect, Journeyman Computer Network Architect, Senior Software Developer, Senior (Software Engineer, Senior) Computer Systems Analyst, Journeyman Computer Systems Analyst, Senior Engineer, Journeyman (Systems Engineer) Engineer, Senior (Systems Engineer) Software Developer, Senior (Systems Specialist) Technical Writer (Technical Writer II) (SCA)
Performance Based (PWS/SOW 3.3.5) ON-SITE
Labor Category Year 1 Year 2 Year 3 Year 4 Year 5
ON-SITE (St. Inigoes, MD) 10/29/2018-
10/30/2019**
10/29/2019-
10/30/2020**
10/29/2020-
10/30/2021**
10/29/2021-
10/30/2022**
10/29/2022-
10/30/2023**
Program/Project Analyst, Journeyman Program/Project Analyst, Senior Computer Programmer I (SCA) Computer Programmer II (SCA) Computer Programmer III (SCA) Drafter/CAD Operator II (SCA)
Administrative Assistant (SCA) Information Security Analyst, Journeyman Information Security Analyst, Senior Logistician, Journeyman Manager/Operations Manager, Senior (Project Manager) Computer Network Architect, Journeyman Computer Network Architect, Senior Software Developer, Senior (Software Engineer, Senior) Computer Systems Analyst, Journeyman Computer Systems Analyst, Senior Engineer, Journeyman (Systems Engineer) Engineer, Senior (Systems Engineer) Software Developer, Senior (Systems Specialist) Technical Writer (Technical Writer II) (SCA)
SECTION C - DESCRIPTIONS AND SPECIFICATIONS
The following have been modified:
STATEMENT OF WORK
Section C - Descriptions and Specifications
Items 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008, 0009, 0010, 0011, 0012, 0013, and 0014– The contractor shall provide services in accordance with the Section C, Performance Work Statement (PWS)/Statement of Work
(SOW). Contract services shall be performed in accordance with the Performance Work Statement (PWS)/Statement of Work (SOW) as detailed in individual task orders. The task order Performance Work Statement
(PWS)/Statement of Work (SOW) will detail tasks that fall within the scope of the basic contract.
Items 0015, 0016, 0017, 0018, 0019, 0020, and 0021– The contractor shall provide ODCs in accordance with the
Section C , Performance Work Statement (PWS)/Statement of Work (SOW) and Clause H-1 5252.242-9515
Restriction On The Direct Charging Of Material (Variation) (Nov 2017) and 5252.232-9509 Travel Approval and
Reimbursement Procedures (NAVAIR)(OCT 2013).
Item 0022– The data to be furnished hereunder shall be in accordance with Exhibit A, DD Form 1423, Contract
Data Requirements List (CDRL), and the Section C, Performance Work Statement (PWS)/Statement of Work
(SOW).
Performance Work Statement (PWS)/ Statement of Work (SOW) for Technical Engineering Services
(TES)
1.0 SCOPE
The Ship & Air Integrated Warfare (SAIW) Division, Naval Air Warfare Center Aircraft Division (NAWCAD)
4.11.3, provides engineering and technical services to support the advanced research and development, systems engineering, and life-cycle support of electronics, communications, and information systems. These services are provided in response to tasking from Department of Defense (DoD), and other U.S. Government organizations.
Efforts span the entire systems and equipment life cycle from initial needs assessment to sustainment and disposal.
The SAIW Division is the lead design agent, organic Lead System Integrator (oLSI), and product manager to various DoD and Department of Homeland Security (DHS) sponsors for the integration (work associated with the rapid development, design, procurement, production, and installation of a system or change to a system, where system could represent a rapid prototype supporting proof of concept, initial production units, full rate production units, or fielded units), test, production, and support of the various systems detailed below. Many of these systems involve operational development due to the warfighter’s rapid response requirements. The SAIW Division is integrally involved in the design, production, and support of the end items. This Performance Work Statement
(PWS)/Statement of Work (SOW) includes advanced research and development support, engineering and technical support, quality management support, cybersecurity services, and technical management support of final end item products. The scope of this effort encompasses rapidly developed engineering designs for end products intended for immediate warfighter operational use, and may include C5ISR systems, subsystems and components of strategic and tactical airborne, land-based, and mobile, sea-based surface and sub-surface platforms. The following are representative of the programs, systems, and technology areas to which the requested engineering and technical services may be applied:
Military and commercial radio communication systems
Information and computer network systems
Command and control systems
Automatic identification technology systems
Integrated document management systems
Multimedia systems
Embedded and stand-alone sensors systems
Unmanned Aerial Systems
Cyber security solutions
2.0 APPLICABLE DOCUMENTS
2.1 DoD Specifications
2.1.1 DoD 5220.22 National Industrial Security Program Operating Manual
2.1.2 DoDD 8140.01 Cyberspace Workforce Management
2.1.3 DoDI 8500.01 Cybersecurity
2.1.4 DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT)
2.1.5 DoDD 5230.24 Distribution Statements on Technical Documents
2.2 DoD Standards
2.2.1 Joint Technical Architecture (JTA)
2.2.2 DoD Standard Practice for System Safety (MIL-STD-882E, May 2012)
2.2.3 MIL-STD-31000A, Technical Data Packages
2.2.4 MIL-STD-100G, Engineering Drawing Practices
2.3 Other Government Documents
2.3.1 Federal Communications Commission (FCC)
2.3.2 NAVSEA Source Approval Request (SAR) for Ships’ Critical Safety Items
2.3.3 SECNAV Manual M-5216.5, Department of the Navy Correspondence Manual
2.3.4 OPNAVINST 4790.4E, Ship's Maintenance And Material Management (3-M) System Policy Naval
Systems Engineering Guide, October 2004
2.3.5 Electronic Industries Alliance (EIA) 632 Standard- Processes for Engineering a System
2.3.6 DoD 5220.22-M, National Industrial Security Program Operating Manual
2.3.7 OPNAVINST 3432.1A, Operations Security Plan
2.3.8 NAVSEA 0900-LP-095-2010, Ship Construction Tests and Trials Manual
2.3.9 NAVSEA 0900-LP-095-6010, Planning Guide Total Ship Test Program for Ship Production
2.3.10 DAO 201-39, Radio Frequency Management
2.3.11 NAWCADINST 5510.1A, NAVAIRWARCENACDIV Information, Personnel and Industrial Security
Program Manual
2.3.12 NAVAIRINST 3960.4C, Project Test Plan Policy And Guide For Testing Air Vehicles, Air Vehicle
Weapons, And Air Vehicle Installed Systems
2.3.13 NAVAIRINST 4355.19D, Systems Engineering Technical Review Process
2.3.14 NAVAIRINST 5239.3, NAVAIR Information Assurance Workforce Improvement Program
2.3.15 NAWCADINST 7320.1B, NAVAIRWARCENACDIV Property Management Process for Minor Property and Class 3 and Class 4 Plant Property
2.3.16 CNSSI 1253 Security Categorization and Control Selection for National Security Systems
2.3.17 CNSSI 4009 Committee on National Security Systems (CNSS) Glossary
2.3.18 Federal Information Security Management Act (FISMA) Title III
2.3.19 FIPS 199 Standards for Security Categorization of Federal Information and Information Systems
2.3.20 ICD 503: Intelligence Community Information Technology Systems Security Risk Management
Certification and Accreditation
2.3.21 NIST SP 800-30 Guide for Conducting Risk Assessments
2.3.22 NIST SP 800-34 Contingency Planning Guide for Federal Information Systems
2.3.23 NIST SP 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems: A
Security Life Cycle Approach
2.3.24 NIST SP 800-53 Assessing Security and Privacy Controls in Federal Information Systems and
Organizations
2.3.25 NIST SP 800-53A Assessing Security and Privacy Controls in Federal Information Systems and
Organizations
2.3.26 NIST SP 800-59 Guideline for Identifying an Information System as a National Security System
2.3.27 NIST SP 800-60 Guide for Mapping Types of Information and Information Systems to Security Categories
2.3.28 NIST SP 800-137 Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations.
2.3.29 NAVAIR SWP4000-001 Cyber Risk Assessment Methodology Standard Work Package
2.3.30 NAVAIR SWP-726-007 RMF Step 1
2.3.31 NAVAIR SWP-726-008 RMF Step 2
2.3.32 NAVAIR SWP-726-009 RMF Step 3
2.3.33 NAVAIR SWP-726-010 RMF Step 4
2.3.34 NAVAIR SWP-726-005 RMF Step 5
2.4 Industry Documents
2.4.1 American National Standards Institute (ANSI)
2.4.2 Society of Mechanical Engineering (ASME) Standards
2.4.3 Association of Public-Safety Communications Officials – International (APCO) – Standards
2.4.4 Electronic Components Industry Association (ECIA), (e.g. Recommended Standards RS Series)
2.4.5 European Telecommunications Standards Institute (ETSI)
2.4.6 Institute of Electrical and Electronic Engineers (IEEE)
2.4.7 International Standards Organization (ISO)
2.4.8 International Telecommunications Satellite Organization (ITSO)
2.4.9 International Telecommunications Union (ITU), formerly the CCITT
2.4.10 National Institutes of Standards and Technology (NIST)
2.4.11 Telecommunications Industry Association (TIA)
2.4.12 ASME Y14.100-2013, Engineering Drawing Practices
3.0 REQUIREMENTS
3.1 General Requirements
3.1.1 Compatibility
The Contractor shall maintain the capability to prepare documents and software packages compatible with the
Government IT environment through the security classification specified on the DD254 (Attachment 2). The current operating environment required for this contract includes:
Microsoft Windows 10
Microsoft Project 2010
Microsoft Office Professional Plus 2010
Adobe Acrobat XI (reader)
Internet access
The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall maintain state-of the-art virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with the SAIW Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the SAIW Division during working hours whether at Contractor work site or on travel.
3.1.2 Work Location and Facilities
3.1.2.1 Work Location: Approximately 39 percent of work will be performed at Government sites and 61 percent of work to be performed at Contractor site. Government site(s) include NAS Patuxent River
(4%), and Webster Field Annex, St Inigoes, Maryland (35%). Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks. The geographic location of the
Contractor’s primary facility with respect to NAWCAD 4.11.3, NAS Patuxent River, Webster Field
Annex is not dictated, but an office location within a fifty (50) mile driving distance of the
Government Program Office location at NAWCAD 4.11.3, NAS Patuxent River, Webster Field
Annex, St Inigoes, Maryland is mandatory.
3.1.2.2 Meeting and Conference Support: The Contractor shall have the capability to locate and secure conference room facilities for conducting meetings at a classification level up to Secret. The conference room should hold a minimum of ten (10) persons and have VTC capability (non-GFE).
The conference room shall contain sufficient equipment to conduct meetings with presentations. The conference room shall have projectors and/or TV displays, computer(s) with compatible software as required in Paragraph 3.1.1 and telephone(s). The conference room location shall be within a fifty
(50) mile driving distance of the Government Program Office location at NAWCAD 4.11.3, NAS
Patuxent River, Webster Field Annex, St. Inigoes, maryland is mandatory.
3.1.2.3 Industrial Support Facilities: The Contractor shall provide sufficient industrial space on an indirect cost basis, for the storage, integration, and testing of electronic equipment and systems associated with assigned projects. The Government estimates that approximately 6,000 square feet are required at contract award and that up to 15,000 square feet will be required during contract execution. The space shall be configured to meet requirements for receiving, material receipt inspection, equipment testing, storage awaiting buildup, a buildup area (including foundation, cabinet, and cable buildup), storage awaiting integration and testing, and storage of completed systems. The space shall be capable of sustaining a controlled environment consistent with the storage, assembly, and operation of electronic equipment. The contractor shall have an approved Property Management System and adequately protect Government property. The Contractor shall furnish and equip the facility to meet requirements. The Contractor’s industrial support facility shall be within a fifty (50) mile driving distance of the Government Program Office location at NAWCAD 4.11.3, NAS Patuxent River, Webster Field Annex, St Inigoes, Maryland. Cost of the facility shall not be a direct cost to the
Government. The Government will not take possession of the facility at contract termination.
3.1.2.4 Government Spaces: The Government has the ability to provide approximately 36 spaces (34 Term and 2 Completion FTE) at it’s St. Inigoes facility to support this effort.
3.1.3 Contract Status Reporting
3.1.3.1 Monthly Progress and Financial Status Report: The Contractor shall provide a progress and financial status report in accordance with the Contract Data Requirement List. (CDRL A005)
The report shall include work accomplished since submittal of the last report, both monthly and cumulative man-hour labor costs expended by labor category and material and travel costs. The purpose of this report is to provide the SAIW Division with the current financial status of the contract at the Contract Line Item Number (CLIN) and TO levels. When applicable, this report shall include prior year(s) expenditures.
3.1.3.2 Reserved.
3.1.3.3 Technical Progress Reports: The Contractor shall prepare and deliver a technical progress report as a supplement to each Standard Form 1034 presented for payment. (CDRL A017)
3.1.3.4 Segregation of Costs and Invoices Requirements: To support invoice reviews, the Contractor shall report costs in the prescribed format. (CDRL A026)
3.1.3.5 Project/TO Report: The Contractor shall provide a report after completing the requirements of each
TO, as well as for the overall contract. (CDRL A021)
3.1.3.6 Travel Reporting and Monitoring: The Contractor shall report all travel costs in the monthly status report, and shall monitor all travel costs to ensure each TO is not exceeded. (CDRL A003)
3.1.4 Work Schedule to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure.
3.1.4.1 Work Schedule: The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including a 30-minute lunch break), from 0730 to 1600 each Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to start as early as
0600/0630 and end as late as 1800, Monday –Friday.
3.1.4.1.1 Compressed Work Schedule (CWS): CWS is an alternative work schedule to the traditional five
8.5 hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period of time: eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as
8.5 hours (which includes a 30-minute lunch) and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.
The Contractor may allow its employees to work a CWS schedule provided the requirements of this PWS/SOW are met. If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage when required by the
Government. The overall schedule must be provided to the ACOR/COR.
3.1.4.1.2 Holidays: The Government observes the following holidays:
New Year’s Day, January 1
Martin Luther King’s Birthday, the third Monday in January
President’s Birthday, the third Monday in February
Memorial Day, the last Monday in May
Independence Day, July 4
Labor Day, the first Monday in September
Columbus Day, the second Monday in October
Veteran’s Day, November 11
Thanksgiving Day, the fourth Thursday in November
Christmas Day, December 25
With the exception of the events in section 3.1.4.1.3 below, the contractor is permitted to observe the above
Holidays in accordance with its corporate policy.
3.1.4.1.3 Installation Closure: When Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility in support of such Federal employees shall follow their parent company’s policies.
While generally contractor personnel may not perform work on-site at a Government facility without oversight from
Federal personnel, in very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant
Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential.
3.1.4.1.4 Overtime: Overtime cannot be charged directly to the contract unless first approved in writing by the Chief of the Contracting Office.
3.1.5 Other Direct Costs (ODCs): The COR and Contracting Officer approval shall be obtained prior to the purchase of any material in accordance with NAVAIR Clause 5252.242-9515 Restrictions on the
Direct Charging of Material (Variation)(Nov 2017) or travel expenses in accordance with NAVAIR
Clause 5252.232-9509 Travel Approval and Reimbursement Procedures (NAVAIR)(OCT 2013).
3.1.5.1 Travel: Travel will be allowable only when it is essential to the performance of the tasks detailed in
Section 3.3. Reimbursement for travel performed shall be in accordance with the Department of
Defense Joint Travel Regulation (http://www.defensetravel.dod.mil/site/travelreg.cfm) and NAVAIR
Clause 5252.232-9509 Travel Approval and Reimursement Procedures (NAVAIR)(OCT 2013). The
COR shall approve all travel performed in support of this contract prior to the commencement of the travel. Travel may include general and administrative expenses, but shall not include profit.
Temporary travel to other locations in support of program tasking is required. If required, temporary travel locations include CONUS and OCONUS locations. These lists are not all inclusive as locations may change over the life of the contract. (CDRL A003)
3.1.5.1.1 CONUS: CONUS locations may include, but are not limited to, St. Inigoes, MD, Newport, VT, Weslaco, TX, McAllen, TX, Rio Grande City, TX, Brackettville, TX, Uvalde, TX, Zapata, TX, Laredo, TX, Alamogordo, NM, Blaine, WA, Eureka, MT, Harrisburg, PA, Norfolk, VA, Mayport, FL, St Louis, MO, Hood River, OR, Tucson, AZ, San Diego, CA, Quantico, VA, Washington, D.C., Dallas, TX, Detroit, MI, Jacksonville, FL and Tampa, FL.
http://www.defensetravel.dod.mil/site/travelreg.cfm
3.1.5.1.2 OCONUS: OCONUS locations may include, but are not limited to, Sasebo, Japan, Aguadilla, Puerto Rico, and other countries in Europe, the Middle East, Asia, and Africa. OCONUS travel shall be conducted IAW DFAR clause 252.225-7040, and the requirements set forth in the TO.
3.1.5.1.3 Synchronized Pre-Deployment & Operational Tracker (SPOT) and Letter of Authorization
(LOA): The Contractor may travel in U.S. Central Command locations. In accordance with Clauses
252.225-7040 and 5152.225-5908, SPOT enables the validation of Contractors authorized to accompany the Force (CAAF), (i.e. Contractor personnel associated with specific contracts and subcontracts), their authorization and eligibility for access to specific DoD facilities, and their eligibility for specific Government-Furnished Support (GFS). The Contractor shall initiate a Letter of Authorization (LOA) for each prospective traveler. The Contractor shall use the SPOT link, https://spot.dmdc.mil to enter and maintain data with respect to traveling/deployment personnel and to generate LOAs.
3.1.5.1.4 Local Travel Reimbursement: Reimbursement of personal travel to-and-from NAWCAD 4.11.3, NAS Patuxent River, Webster Field Annex and the Contractor’s facility and the surrounding area, by the Contractor or subcontractor located within 50 miles of the base, shall not be authorized.
3.1.5.2 Material: All incidental materiel purchases will be approved per the clause "Restriction on the
Direct Charging of Material (NAVAIR 5252.242-9515 Variation) (Nov 2017)" Any material provided by the Contractor is subject to the requirements of the Federal Acquisition Regulation
(FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable
Department of the Navy regulations and instructions. All materials not depleted during the performance of this contract shall become Government property upon completion of this contract.
The Contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Other Direct Charges may include general and administrative expenses but shall not include profit.
The costs of general purpose business expenses required for the conduct of the Contractor’s normal business operations are not an allowable direct cost in the performance of this contract.
General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies.
3.1.6 Subcontractors: Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this PWS/SOW shall flow down to subcontractors providing support under this contract.
3.1.7 Management of Contractor Personnel: The Government shall neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual
Contractor employees. The Contractor shall manage its employees and shall not perform any actions that are of the nature of personal services, or give the perception of personal services.
3.1.8 Transition Strategy: The overall strategy shall be built around maintaining the mission of the
SAIW program/ division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the contract, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The Contractor shall submit a Transition Out Plan, to include the minimum elements listed below in accordance with CDRL A049.
https://spot.dmdc.mil/
3.1.8.1 Work Turnover: The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the contract to the successor company.
Establish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.
3.1.8.2 Quality Assurance: The Contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.
3.1.8.3 Risk Mitigation Strategies: The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.
3.1.9 Quality Management: (CLINS 0008-0014) The Contractor shall develop, implement, document, and maintain a quality management system to ensure conformance with contractual requirements and the specific quality and performance requirements of specific TOs to be issued under this contract. The quality management system should meet the intent of the American
National Standards Institute/American Society for Quality (ANSI/ASQ) ISO 9001:2008, and/or equivalent governing body. Regardless of the standards that are applied, the Contractor’s quality approach should be clearly defined and recognize the need to focus on customer satisfaction, defect prevention over inspection, management responsibility and continuous improvement.
(CDRL A042)
3.1.9.1 Inspection System Plan (ISP): The Contractor shall submit an Inspection System Plan (ISP) for approval no later than 15 days after the first TO is issued.) (Performance-Based CLIN 0008)
(CDRL A039)
3.1.9.2 Planning Review: The Contractor shall conduct a thorough review of TO quality requirements to identify the controls, processes, skills, fixtures, tools, and test equipment needed to ensure product quality. The planning review shall also update inspection and testing techniques, instrumentation, and manufacturing methods and processes. Standard program data (test results, defects/failures identified, calibration results, etc.) that may be required by the Government to compile trend evaluation shall be available upon request. (Performance-Based CLIN 0008)
3.1.9.3 Quality Management Plan: The Contractor’s Quality Management Plan (QMP) should address all areas of work to be performed under the contract resulting from this solicitation to include hardware and software systems engineering, integration and installation, configuration management, logistics and Contractor’s method for monitoring and reporting on the identified metrics. A formal and final QMP shall be deliverable under the first TO issued, with updates and changes as needed in follow on TOs. (CDRL A042) (Performance-Based CLIN 0008)
3.1.9.4 Process Documentation: All processes used to fabricate, assemble, modify, install, deploy, and test products shall be documented and updated. These written procedures and work instructions shall be made available to the employees required to perform the specific task. All procedures and work instructions shall be consistent with the Contractor’s quality management system and provided to the Government as a deliverable. (CDRL A001) (Performance-Based CLIN 0008)
3.1.10 Technical Direction Letters (TDLs): When necessary, technical direction or clarification concerning the details of specific tasks set forth in the contract and TOs shall be given through issuance of written Technical Direction Letters (TDLs). TDLs will not, in any manner, alter the scope of the contract. For further direction see Clause 5252.242-9502 Technical Direction (May
2011) in Section H.
3.1.11 Quality Surveillance and Performance Standards: The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables as provided in the Quality
Assurance Surveillance Plan (QASP)/Contract Surveillance Plan (CSP) Attachment (8).
The Government will evaluate Contractor performance in the areas of Quality of Product or
Service, Schedule, Cost Control, Business relations, Management, Utilization of Small business, and other areas in accordance with the procedures and criteria established in the QASP/CSP.
3.1.12 Government Furnished Property (GFP)/Government Furnished Information (GFI): Any
GFI listed in this contract or resulting TOs will be provided to the Contractor within 5 days after award. Additional GFI such as training, and documentation requiring Contractor review, analysis, and updating will be provided throughout the contract period of performance. Disposition of GFI will be made at contract completion. Contractor must have an approved Property Management
System.
3.2 Security
3.2.1 Citizenship Requirements: Only U.S. citizens may perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:
a. The individual's name, date, and place of birth, position title, and current citizenship.
b. A statement that a…
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.