N00421-16-R-0023-0001.pdf

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 respond to questions and make changes accordingly.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 86

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 24-Apr-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-0023

X 9B. DATED (SEE ITEM 11)

10-Apr-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, X 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

24-Apr-2017

CODE

NAVAL AIR WARFARE CENTER AD (PAX)

CODE 2.5.1.5

BLDG 441

21983 BUNDY ROAD

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-0023

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

SECTION A

AMENDMENT 0001:

The purpose of this amendment is to respond to questions with reference to this solicitation, incorporate associated changes, and incorporate additional clauses and provisions..

The following questions were received and changes are hereby incorporated as outlined within each response:

Reference: RFP, Section L-(1), Part B, Paragraph 2.1

Q1: The Past Performance form has a scrolling data entry block for Contract Effort Description on the first page that will be limited to the first 8 lines when printed. This will prevent fully describing the Section L inputs for this element. Can the offeror include the Past Performance form content directly into their Volume 2 proposal for printing and submit the completed PDF electronically with the same information?

A1: Offerors are allowed to include the full “Contract Effort Description” (from the form) in the

Technical Volume 2 within Annex 1. (No change to the solicitation.)

Reference: RFP, Section M, Part B, Paragraph 2.0 PAST PERFORMANCE

Q2: The Magnitude dollar values and labor hours seem excessive for a Small Business Set Aside. A business with 3+ past performance in this range would no longer be small business under this NAICS code.

Would the government consider lowering the Magnitude values to be $6M-$8M per year and 80,000-100,000 hours per year, which would be more reasonable for Small Business prime contracts?

A2: The dollar value under “Magnitude” has been revised to read, “Contract total greater than $40M.

Annual contract value greater than $8M.” A revision is included in Section M. Note: Offerors are reminded that the relevancy of past performance information is a measure of the extent of similarities between service/support efforts and will be assigned as such. The table has been revised in Section M, Part B, paragraph

2.0.

Magnitude:

Dollar value Contract total value greater than $40M. Annual contract value greater than $8M.

Labor hours Removed

Contract term Contracts with a term of five years. Contract with a term of less than three years with a similar annual value and complexity.

Reference: RFP, Section L, Part B, Paragraphs 3.7.2.1 and 3.7.2.2

Reference: RFP, Section C, SOW, Paragraph 20.8, Labor Qualifications

Reference: RFP, Section C, SOW, Paragraph 20.10 LABOR QUALIFICATIONS

Q3: “Computer Scientist, Journeyman” is listed in the hour allocations in Section L but there is not a labor category in Section C. Conversely, there is a “Computer Scientist, Senior” listed in Section C without hours in Section L. The Labor Qualifications table in Paragraph 20.8 lists the labor category qualification as

“Journeyman”. Is the labor category defined in Section C supposed to be “Computer Scientist, Journeyman”?

A3: The Computer Scientist, Senior has been changed to Computer Scientist, Journeyman in Section

C, Paragraph 20.10 under “NON-KEY PERSONNEL”.

Reference: RFP, Section L, Supplies or Services and Prices

Q4: The paragraph describes the listed page counts as “recommended pages”. Is there any penalty for exceeding the recommended page count?

A4: No. (No change to the solicitation.)

Reference: RFP, Section B, Supplies or Services and Prices

Q5: Section B “Supplies and Services or Prices,” Items 0001, 0006, and 0010 each represent a summation (rollup) of the Base and 4 Option Years for LOE Labor (0001), Performance Base Labor (0006), and ODCs (0010). There is no requirement to fill-in information for Items 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0011, 0012, 0013, 0014, 0015, and 0016 because they are Not Separately Priced. Is it true that Section B fill-ins are only required for Items 0001, 0006, and 0010?

A5: Yes. (No change to the solicitation.)

Reference: RFP, Section B, Clause 5252.211-9503

Reference: RFP, Section L, Paragraph 3.7.2.1

Q6: There is a discrepancy between the LOE Total labor hours shown in 3 locations. Location 1: RFP

Page 15, Clause 5252.211-9503 Level of Effort, para (a) lists total hours in the paragraph and in the table as

598,110. Location 2: RFP Page 112, Paragraph 3.7.2.1, the LOE total hours shown is 598,110. Location 3: RFP

Page 113 Non Performance Based table under Paragraph 3.7.2.1, shows the Estimated Total Hours as 598,150.

Would the Government please confirm that the table value of 598,150 is correct?

A6: The table value of 598,150 is correct. The total labor hours have been changed in Section B, NAVAIR Clause 5252.211-9503 and Section L, Part B, paragraphs 3.7.2.1.

Reference: RFP, Section L, Paragraph 3.7.2.2

Q7: There is a discrepancy between the LOE Total labor hours shown in 2 locations. Location 1: Page

113, Paragraph 3.7.2.2, the Government estimate is 73,890. Location 2: Page 115 Performance Based table under Paragraph 3.7.2.2, the Estimated Total Hours listed is 73,850. Would the Government please confirm that the table value of 73,850 is correct?

A7: The table value of 73,850 is correct. The total labor hours have been changed in Section L, Part B, paragraphs 3.7.2.2.

Reference: RFP, Section J, Attachment P6, Item 8

Q8: The Attachment P6 instructions, Contractor item 8 specifies the labor for CLIN 0001 is carried to

Section B. This only applies to the Level of Effort (LOE) hours in the table starting on page 112. There is no mention of CLIN 0006 in the instructions. Should the Offeror complete a separate set of P6 artifacts for the

Performance Based estimate? If not, please provide guidance on how to incorporate CLIN 0006 pricing.

A8: Attachment P6 has been updated to include a spreadsheet for CLIN 0006. The instructions have also been updated with reference to summary sheets.

Reference: RFP, Section C, Paragraph 20.2

Q9: The table shows two lines for Program/Project Analyst, Junior each showing 1 security clearance required. Should the Program/Project Analyst, Junior appear in the table one time and thus require only one secret clearance at the issuance of the Task Order?

A9: The Secret Clearance Information table should only have one (1) Program/Project Analyst, Junior listed. The table in Section C, paragrarph 20.2 has been revised.

Reference: RFP, Section L, Part A, Paragraph 3.0

Reference: RFP, Section L, Part B, Paragraph 2.1

Q10: The Proposal Organization and Page Count table lists the Past Performance Annex 1 to be part of

Section 3, which would be Price and Cost. Section B, Paragraph 2.1 specifies that it is to be included “as

Annex 1 to this Past Performance Volume.” Section B also mentions Annex 1 be provided electronically, which contradicts the table in Paragraph 3.0. Should the table in Paragraph 3.0 be updated to show the Annex 1 as part of Section 2.0, Past Performance? And should Annex 1 be provided in both printed and electronic forms?

A10: Annex 1 has been relocated under Volume 2, 2.0 Past Performance of the “Proposal Organization and Page Count” table in Section L, Part A, paragraph 3.0. Please provide Annex 1 in both printed and electronic forms.

Reference: RFP, Section C, SOW, Paragraph 20.7

Q11: The qualifications substitution chart highlights how higher degrees may be substituted with lower degrees and extra experience. However, for Master’s Degree, it is not clear from this table whether a MS/MA could be replaced with AS/AA and extra experience or extra experience all together. Can candidates qualify for

Senior labor categories with any of the following combinations:

MS/MA + 10 years OR BS/BA + 14 years OR AS/AA + 18 years OR 20 years of experience?

A11: The table in Section C, Paragraph 20.7 has been revised to include substitutions for the Master’s degree. The table has also been updated to include the word “relevant” with reference to work experience in all substitutions.

Reference: RFP, Section C, SOW, Paragraph 20.10 LABOR QUALIFICATIONS

Reference: RFP, Section L, Paragraphs 3.7.2.1 and 3.7.2.2

Q12: Could the Government clarify how many hours are allocated for the Computer Scientist, Senior, SOC 15-1221? The charts in Section L under paragraphs 3.7.2.1 and 3.7.2.2, pages 112-115 do not include this labor category? What is the requirement for this?

A12: The “Computer Scientist, Senior” has been corrected to “Computer Scientist, Journeyman”.

Please refer to Question #3.

Reference: RFP, Section C, SOW, Paragraph 20.7

Q13: Could the Government clarify the experience requirement for the following: Program Manager, Senior (Key), SOC 11-1021 (page 50): RFP states, “Experience must include three (3) years of which must have been in the previous six (6) years, in support of Navy Acquisition management; and a minimum of seven

(7) years supervisory experience. At least eight (8) years of experience in the planning,…” In paragraph 20.7, it states that a SENIOR must have over 10 years of experience; does the Program Manager require 7 years supervisory + 8 years of planning = 15 years?

A13: Section C, Paragraph 20.7 has been changed to include “Note: Specific experience requirements are included under each labor category” to the Junior, Journeyman, and Senior expereince statements. The

“Experience” section of all labor categories under Section C, paragraph 20.10 has been reviewed and appropriate changes have been made to provide clarification with reference to the years of experience required for each category. In addition, where appropriate, “Experience may be concurrent” has been added to the experience section of the category.

Reference: RFP, Attachment P8, Past Performance Information Form, Page 1 “Task/Delivery Order” form field and Page 2 “Demonstrated Systemic Improvement” paragraph form field

Q14: The “Task/Delivery Order” form field and the “Demonstrated Systemic Improvement” paragraph form field are linked together. After inserting text in one form field and moving to a new form field, the text duplicates in each linked form field. This causes the full text of both fields to display in each of the separate form areas. Will the Government provide an updated form without linked fields?

Q14: Attachment P8 has been replaced with a different version of the form.

The following clauses and provisions are hereby incorporate as outlined below:

Section I – FAR clauses added by reference:

52.203-19 – Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements (Jan 2017)

52.222-59 – Compliance With Labor Laws (Executive Order 13673) (Dec 2016)

52.222-60 – Paycheck Transparency (Executive Order 13673) (OCT 2016)

52.222-61 - Arbitration of Contractor Employee Claims (Executive Order 13673) (Dec 2016)

Section K – FAR and DFAR provisions added by reference:

52.203-18 – Prohibition on Contracting with Entities that Require Certain Internal Confidentiality Agreements or Statements - Representation (Jan 2017)

252.225-7003 - Report of Intended Performance Outside the United States and Canada—Submission with Offer

(OCT 2015)

Section K – FAR provision added in full text:

52.222-57 – Representation Regarding Compliance with Labor Laws (Executive Order 13673) (Dec 2016)

Section L – FAR provisions added by reference:

52.222-58 - Subcontractor Responsibility Matters Regarding Compliance with Labor Laws (Executive Order

13673) (Dec 2016)

All other terms and conditions remain unchanged.

BASIC SOLICITATION:

POINTS OF CONTACT

CONTRACT SPECIALIST: SUSANTI BEEBE

TELEPHONE NUMBER: 301-757-3652

EMAIL ADDRESS: susanti.beebe@navy.mil

CONTRACTING OFFICER: MELINDA STANN

TELEPHONE NUMBER: 301-757-0008

EMAIL ADDRESS: melinda.stann@navy.mil

CONTRACTING OFFICER REPRESENTATIVE:

TO BE DETERMINED AT CONTRACT AWARD

SUMMARY

(1) This acquisition is a small business set aside that will result in a Single

Award Indefinite Delivery/Indefinite Quantity (IDIQ) contract.

(2) The Product/Service Code (PSC) for this procurement is D302.

(3) The resulting Single Award IDIQ contract will have an ordering period of five (5) years.

(4) This contract will include cost-plus-fixed-fee (CPFF) and cost reimbursement (non-fee bearing) line items.

(5) Task Orders issued from this contract award will reflect CLINs by Funding type.

(6) The contractor will not be authorized to access any classified information under this contract unless a final DD254 is incorporated.

SECTION B - SUPPLIES OR SERVICES AND PRICES

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) (Oct 2016). For purposes of estimating and establishing a labor cost ceiling for each task order, the following composite rates will be used. These rates are estimates, and invoicing will be based on actual costs incurred. Ceiling for ODCs 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 (SOW 4.1- 4.4)

Labor Category

(* = Key)

Composite Fully Burdened Rates

Year 1 Year 2 Year 3 Year 4 Year 5

03/07/2018-

03/06/2019**

03/07/2019 –

03/06/2020**

03/07/2020 –

03/06/2021**

03/07/2021–

03/06/2022**

03/07/2022 –

03/06/2023**

Program/Project Analyst, Journeyman (Contractor off-site)*

Program/Project Analyst, Junior (Contractor off-site)

Computer Based

Training Specialist, off-site)

Training Specialist, Journeyman (St. Inigoes on-site)

Computer Programmer, Junior (St. Inigoes on-

Senior (Contractor off-

Computer Scientist, Computer Scientist, Computer Systems

Analyst, Senior

(Contractor off-site)

Analyst, Journeyman

(St. Inigoes on-site)

Analyst, Junior

Information Security

Information Security

Computer and

Information Research

Scientist, Journeyman

(Contractor off-site)*

Logistics Analyst, Junior

Logistics Analyst, Manager, Journeyman

(St. Inigoes on-site)*

Program Manager, site)*

Software Engineer, Software Engineer, Subject Matter Expert

(Navy Maintenance

Lead), Journeyman(Contractor off-site)*

Subject Matter Expert

(S1000D IETM Lead)

, Journeyman (St. Inigoes on-site)*

Systems Analyst, Senior

(Contractor off-site)*

Systems Analyst, on-site)

Systems Analyst, Junior

Systems Analyst, Junior

(St. Inigoes on-site)

Logistics Engineer, Technical Writer II, Technical Writer II, Junior (St. Inigoes on-

Training and

Development Specialist , on-site)*

* Indicates Key Personnel (1 Person)

** Dates to be adjusted at contract award

PERFORMANCE BASED (SOW 4.5)

Labor Category

(* = Key)

Composite Fully Burdened Rates

Year 1 Year 2 Year 3 Year 4 Year 5

03/07/2018 –

03/06/2019**

03/07/2019 –

03/06/2020**

03/07/2020 –

03/06/2021**

03/07/2021 –

03/06/2022**

03/07/2022 –

03/06/2023**

Program/Project

Analyst, Journeyman

(Contractor off-

Program/Project

Training

Specialist, Journeyman

Training

Specialist, Journeyman (St.

Inigoes on-site)

Computer

Programmer, Junior

Junior (St.

Journeyman

Senior

Scientist, Junior

Scientist, Journeyman

Senior

Journeyman

Journeyman

(St. Inigoes on-

Junior

Information

Security Analyst, Junior

Security Analyst, Journeyman

Computer and

Research

Scientist, Journeyman

Junior

Journeyman

Manager, Inigoes on-site)*

Program

Manager, Senior

Software

Engineer, Senior

Software

Engineer, Journeyman

Subject Matter

Expert (Navy

Maintenance

Lead), Journeyman

Subject Matter

Expert (S1000D

IETM Lead), Journeyman

(St. Inigoes on-

Senior

Journeyman

Junior

Junior (St.

Logistics

Engineer, Senior

Engineer, Journeyman

Engineer, Junior

Technical Writer

II, Junior

Technical Writer

II, Junior (St.

Training and

Development

Specialist , Inigoes on-site)*

* Indicates Key Personnel (1 Person)

** Dates to be adjusted at contract award

CLAUSES INCORPORATED BY FULL TEXT

5252.211-9503 LEVEL OF EFFORT (COST REIMBURSEMENT) (NAVAIR)(DEC 2012)

(a) The level of effort estimated to be ordered during the term of this contract is 598,150 man-hours of direct labor including authorized subcontract labor, if any. The Contractor shall not, under any circumstances, exceed one hundred (100%) percent of the total level of effort specified in this basic contract. The estimated composition of the total man-hours of direct labor by classification is as follows:

CLIN 0001 Total

Labor Hours 598,150

(b) FAR Clause 52.232-20, "Limitation of Cost" applies to fully funded orders and FAR Clause 52.232-22, "Limitation of Funds" applies to incrementally funded orders. Nothing in this clause amends the rights or responsibilities of the parties hereto under either of those two clauses. In addition, the notifications required by this clause are separate and distinct from any specified in either FAR Clause 52.232-20 or FAR Clause 52.232-22.

(c) In the event that less than one hundred (100%) percent of the established level of effort of the contract/order is actually expended by the end of the performance period, the Government shall have the option of:

(1) Requiring the Contractor to continue performance, subject to the provisions of the FAR Clause 52.232-

20 or 52.232-22, as applicable, until the effort expended equals 100% of the established Level of Effort; or

(2) Effecting a reduction in the fixed fee by the percentage by which the total expended man-hours is less than one hundred (100%) percent of the established Level of Effort.

(d) The Contractor agrees that effort performed in fulfillment of level of effort obligations under this contract shall include only verifiable effort in direct support of the work specified. It shall not include efforts such as work performed in transit to or from an employee's usual workplace, work during lunchtime activities, or effort performed at other non-work locations.

(e) In performing the contract/order, the Contractor may use any reasonable combination of hours for the labor categories in support of section C of this contract/order.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

SECTION C DESCRIPTION

Items 0001, 0002, 0003, 0004, 0005 – The Contractor shall provide SERVICES in accordance with section 4.1 - 4.4 of the Statement of Work (SOW), as detailed in individual task orders. Each task order shall include a SOW that will detail all tasks within the scope of the basic contract that are to be performed.

Items 0006, 0007, 0008, 0009 – The Contractor shall provide SERVICES in accordance with section 4.5 of the

Statement of Work (the Performance Based Statement of Work or PBSOW), as detailed in individual task orders.

Each task order shall included a PBSOW that will detail all tasks within the scope of the basic contract are to be performed.

Items 0010, 0011, 0012, 0013, 0014 – are ODC CLINs related to Travel & Materials provided by the Contractor.

These CLINs are Cost Reimbursable (no fee). TRAVEL shall be provided in accordance with the SOW and

NAVAIR Clause 5252.232-9509. MATERIALs shall be provided in accordance with H Clause 5252.242-9515

“Restriction on The Direct Charging of Material”.

Item 0015 and 0016 – are Data CLINs. The DATA reports shall be furnished in accordance with Exhibit A, DD

Form 1423, Contract Data Requirements Lists (CDRLs), CDRLs A001-A024, and the SOW as required by the individual Task Order.

C4I OPERATIONAL MAINTENANCE & ENGINEERING TRAINING (COMET)

STATEMENT OF WORK (SOW) / PERFORMANCE BASED STATEMENT OF WORK

1.0 BACKGROUND

NAWCAD 4.11.3, Patuxent River, MD, is engaged in the research, development, design, integration, test and evaluation, deployment, training, technical management, and maintenance support for integrated Command, Control, Communications, Computers, and Intelligence (C4I) life-cycle engineering systems supporting various DoD and U.S. Navy sponsors to include

NAVAIR, NAVSEA, and other DoD and Federal organizations. NAWCAD 4.11.3 engineering leverages communications and information systems emerging technologies, advanced interfaces, and innovative information management architectures on a variety of C4I systems and platforms to provide engineering and interactive information products to these clients.

2.0 SCOPE

This contract will leverage NAWCAD 4.11.3’s core capabilities involving C4I engineering and information systems to provide innovative information management architectures relating to interactive information and learning products to support our warfighters. With the constant advancement of C4I warfighting technologies and the constant pressure placed not only on the reliability of the equipment, but also on the effectiveness of the warfighter in utilizing and maintaining this equipment, the contractor shall provide the engineering products, tools and support needed in responding to this environment. This SOW defines specific requirements relating to the in-service engineering and interactive products envisioned under this effort. As a general scope, the following statements encompass the Government’s intentions on this contract:

Analysis of Navy and DoD engineering data processes, policy implementation, and standards compliance requirements, including Maintenance Material Management (3M) processes.

In-service engineering on C4I equipment suites that are found on board U.S. Navy’s surface and subsurface warships involving various communication, weapon and operational mission systems throughout product design, development, deployment and life cycle support.

Design and development of standards-based operations and maintenance engineering data architectures for DoD based C4I equipment.

Design and development of safety improvement product tools using key concept and scenario-based approaches.

Design and development of decision support product tools for installation, operation, maintenance, and safety of technical systems.

Design and development of engineering performance aids and product tools using interactive multimedia.

Development of engineering technical content, including methods and tools for markup, delivery, transformation, and management.

Project estimation, planning, scheduling, and reporting.

3.0 APPLICABLE DOCUMENTS

The following specifications, standards, instructions, and directives are incorporated by reference; the list is not all inclusive. Compliance with the detail, standards, specifications or policy contained in these documents is essential in the performance of this contract. Unless otherwise specified, a reference to a military specification, standard, or handbook, or to an industry standard adopted by DoD, will be to the specific version listed in the DoD Index of

Specifications and Standards in effect at the time task orders are awarded.

3.1 References:

Joint Fleet Maintenance Manual- Rev C Change 1 (COMFLTFORCOMINST 4790.3

Rev C Change 4, 13 OCT 2015)

Planned Maintenance System (PMS): Development of Maintenance Requirement Cards

(MRC), Maintenance Index Pages, and Associated Documentation (MIL-P-24534A, 21

MAR 1991)

Ship's Maintenance and Material Management (3M) Manual (NAVSEAINST 4790.8C, 14 MAR 2013)

Ship’s Maintenance and Material Management (3M) System Policy (OPNAVINST

4790.4E, 31 OCT 2007)

Department of Defense Standard Practice: Reliability-Centered Maintenance (RCM)

Process (MIL-STD-3034A, 29 APR 2014)

Policy for Preparation and Standardization of NAVAIR S1000D IETMs (NAVAIRINST

4120.11A, 10 OCT 2012)

International Specification for Technical Publications utilizing a Common Source

Database (S1000D, Issues 3.0-4.1)

DoN S1000D Technical Manual Quality Assurance Guidance (NSWCCD-20-TR-

2010/01, MAR 2009)

Performance Specification: Manuals, Technical, Quality Assurance Program;

Requirements For (MIL-PRF-85337B, 11 APR 2012)

Interactive Multimedia Instruction Developer’s Guide (CENNAVAVNTECHTRA

INSTRUCTION 1554.1, 27 JAN 14)

Guidance for Acquisition of Training Data Products and Services (Part 1 of 5 Parts), (MIL-HDBK-29612/1A, 31 AUG 2001)

Instructional Systems Development/Systems Approach to Training and Education (Part 2 of 5 Parts), (MIL-HDBK-29612/2A, 31 AUG 2001)

Development of Interactive Multimedia Instruction (Part 3 of 5 Parts), (MIL-HDBK-

29612/3A, 31 AUG 2001)

Glossary for Training (Part 4 of 5 Parts), (MIL-HDBK-29612/4A, 31 AUG 2001)

Advanced Distributed Learning (ADL) Products and Systems (Part 5 of 5 Parts), (MIL-

HDBK-29612/5, 31 AUG 2001)

US Fleet Cyber Command (FCC)/Space and Naval Warfare (SPAWAR) Command Navy

Authorizing Official and Security Control Assessor Risk Management Framework

Process Guide (Version 1.0, 31 AUG 2015)

Risk Management Framework (RMF) for DoD Information Technology (IT), (DODI

8510.01, 12 MAR 2014)

4.0 TECHNICAL REQUIREMENTS

This SOW covers two work areas. The first work area to be covered will require the contractor to provide engineering and analysis of complex DoD based C4I systems relating to and supporting innovative and interactive information and learning tool products. The contractor shall support in-service engineering approaches as it relates to planned maintenance and training covering both currently deployed C4I systems, as well as new and emerging C4I systems still under development. This effort will include the design, development, implementation and training utilizing electronically based engineering processes for maintenance and training techniques on sophisticated military systems. These engineering solutions and interactive products will support the various C4I equipment suites that are found on board U.S. Navy’s surface and subsurface warships, DoD based air platforms and ground systems involving various communication, weapon and operational mission systems. The contractor will also be required to interact with fleet personnel to ascertain not only inputs for the engineering design and development phases of these information and learning tool products, but to also support fleet personnel in their daily duties of in-service engineering and maintenance support for the mission based electronic equipment.

The second work area to be covered by this SOW will require the contractor to produce quarterly logistics maintenance data packages and quarterly tailored logistics packages for C4I equipment covering planned maintenance on systems found on Navy/DoD platforms. These data packages will directly support fleet personnel in their daily shipboard duties of planned maintenance activities covering a wide range of C4I systems based communication and weapon system.

ENGINEERING & ANALYSIS (NON-PERFORMANCE BASED)

4.1 Maintenance Management Development (3M) (CLINs 0003, 0004, 0005)

The contractor shall support the NAVSEA 3M system. The system is used throughout the U.S.

Navy Fleet as part of the in-service engineering, maintenance and reliability of installed C4I equipment by providing engineering management, readiness and reporting procedures for U.S.

Navy equipment suites. This program includes in-service engineering processes and procedures for the Planned Maintenance System (PMS), database generation, user-interface development and modifications, development and reliability for 3M applications, and the development, distribution, and management of PMS technical documentation. The PMS system also provides procedures for scheduling and accounting for PMS tasks on board ships. NAVSEA04RM, Director of Maintenance Engineering holds the Technical Warrant for Reliability-Centered

Maintenance (RCM) policy covering all NAVSEA based efforts that requires all maintenance developers to utilize MIL-STD-3034A methodologies to be NAVSEA RCM certified. NAVSEA requires RCM Level I (Backfit) certification for all personnel who develop, review, or approve changes to currently published maintenance tasks. Classic RCM (Level II) is required for this contract and covers those who develop, review, or approve maintenance requirements on new systems or equipment, or existing systems or equipment being used in a different application or arrangement. Classic RCM analysis is required during ship acquisition and during ship modernization alterations.

4.1.1 The contractor shall analyze PMS logistics packages for 3M systems including equipment maintenance requirements, PMS schedules, feedback reports, configuration change reports, procedural content, parts and material information, and distribution data. The contractor will access the data maintained by NAVSEALOGCEN quarterly in February, May, August, and

November by accessing the NMCI portal. Data analysis will require efficiency in the use of the

Configuration Data Management Database (Open Architecture (CDMD-OA) system), PMS

Management Information System (PMS MIS), and Ships 3M History (Open Architectural

Retrieval System (OARS). Please refers to 4.5 (CDRL A001)

4.1.1.1 The contractor shall provide procedural analysis of changes that may have occurred in

Maintenance Requirement Cards (MRCs) to include updated procedures, warnings, cautions, notes, and Maintenance Index Page (MIP) scheduling changes affecting an MRC. New MRCs will need to be further evaluated to determine ship applicability and schedule impacts. This effort is conducted quarterly. (CDRL A001)

4.1.1.2 The contractor shall determine which MRCs apply to specific ship configurations across the Fleet quarterly. Analysis involves approximately 5 million configuration records, 35,000 distinct MRCs, 2,000 distinct MIPs, covering an estimated 140-160 ships. The contractor shall consider Navy maintenance policies, application of maintenance guidelines, and maintenance audit/inspection criteria. (CDRL A001)

4.1.1.3 As part of the data analysis of the various sources including shipboard data and shore based 3M and Navy Logistics data, the contractor shall be required to develop standardized reports, dashboards and metric reports. (CDRL A001)

4.1.2 The contractor shall develop updates to 3M and Navy Logistics data structures including

Document Type Definitions (DTD) and database schemas. Maintain the PMS procedure content model for MIPs and MRCs using Standard Generalized Markup Language (SGML/XML) DTD and XML Schemas. This includes data transformation scripts using eXtensible Style Language for Transformations (XSLT) for presentation in NAVSEA approved viewers. Required outputs include on screen and printed layouts. The PMS DTD is the authoritative data structure used for storing PMS documents and 3M data. The contractor shall have the ability to adapt to the various presentation methods and approaches listed above. Key technologies include the

Microsoft XML parser. (CDRL A008)

4.1.2.1 The contractor shall install Navy maintenance applications on the Navy Information and

Application Product Suite (NIAPS) and Consolidated Afloat Networks and Enterprise Services

(CANES). This also involves maintaining certification requirements for installation on these networks.

4.1.3 The contractor shall perform software engineering and life-cycle maintenance support for

3M scheduling, viewing, and authoring applications. The contractor shall work with other Navy agencies and third-party software developers to define and implement required interface specifications. (CDRL A002, A003)

4.1.3.1 The contractor shall produce the following deliverables:

Requirement traceability matrices (CDRL A001)

Software requirements documentation (CDRL A002)

Software design descriptions (CDRL A003)

Database design descriptions (CDRL A004)

Software test plans (CDRL A005)

Software test reports (CDRL A006)

Software user manuals (CDRL A007)

4.1.3.2 The contractor shall provide PMS applications development support for the SKED

Maintenance Management and Scheduling System. This is a Fleet-wide (surface and subsurface) system to automate all scheduling and administrative tasks associated with the Navy PMS.

Supporting Fleet Type Commanders (TYCOMs) in Norfolk and San Diego, the contractor shall assist NAWCAD 4.11.3 in providing total development support, including installation, configuration management, implementation of Fleet training, user technical support, business process revisions, and deployment planning. The use of SKED is mandatory for all Navy PMS schedules, including all ships in the Fleet, shore facilities, and intermediate maintenance facilities. The SKED software has been approved for use in Common PC Operating System

Environment (COMPOSE)operating environments, and for use in the Navy Marine Corps

Intranet (NMCI) infrastructure. As this maintenance and management software is utilized and maintained on all ship networks, the contractor shall be required to maintain the various versions of this Government based software. Key technologies include Visual Basic, Microsoft .NET, and SQL Server.

4.1.3.3 PMSViewer is a Fleet-wide Government based distributed software application to display and print all Navy PMS documentation. The software is distributed quarterly on

CD/DVD configurations. NAWCAD 4.11.3 works closely with In Service Engineering Agents

(ISEAs) and Commodity Specialists at Atlantic and Pacific based NAVSEA Logistics Centers

(NAVSEALOGCENs) to define PMS document style requirements conforming to OPNAV

Instruction 4790. The PMSViewer uses XSLT to transform and display MIPs and MRCs provided in XML format. The PMSViewer application has been approved for use in the

COMPOSE operating environments, and for use in the NMCI infrastructure. The contractor shall maintain this software. Key technologies include Visual C++ and Microsoft XML parser.

4.1.3.4 The Navy PMS Editor (NPE) Authoring System is a document authoring system for the

PMS Program. The NPE Authoring System is the principal method used by Commodity

Specialists and ISEAs to author PMS MRCs and MIPs. The software allows authors to create and edit complex engineering and technical documents stored as SGML in a simplified “What

You See Is What You Get” user interface. The system is designed to be NMCI compliant. The contractor shall maintain this software. Key technologies include Visual C++ and Microsoft

XML parser.

4.1.3.5 NAWCAD 4.11.3 is responsible for the maintenance of the PMS DTD. The PMS DTD is the authoritative data structure used for storing PMS documents and 3M data. NAWCAD

4.11.3 works with NAVSEA to ensure the integrity of the DTD and the contractor shall support maintaining the PMS DTD. Key technologies include the Microsoft XML parser.

4.1.4 As authorized by the Navy and as allowed by ship deployment schedules, the contractor shall conduct installation, training, and technical tasking of various 3M, technical manual, and other Navy logistics systems on board the Navy’s surface and subsurface fleet. Tasking may include:

4.1.4.1 Install Navy maintenance applications on the Navy Information Application Product

Suite (NIAPS)and Consolidated Afloat Networks and Enterprise Services (CANES). This also involves maintaining certification requirements for installation on these networks.

4.1.4.2 The contractor shall provide and can expect annually up to 100-125 on-site ship and shore installations, activations, configurations, and training of NAVSEA PMS Logistics applications. These activities must be coordinated with the appropriate fleet authorities and the current shipboard hosting agencies. (CDRL A012)

4.1.4.3 Provide, and report on, troubleshooting support services for PMS applications to meet fleet requirements via phone, e-mail, message or on-site visit. Troubleshooting support may vary based on new product roll out, engineering and software upgrades, or by the class of ship supported, however for estimating purposes, the Government would expect to see no more than

12 on-site requests and approximately 150-250 phone and/or email requests annually. (CDRL

A001)

4.1.4.4 The contractor shall provide shipboard support in both Norfolk, VA, and San Diego, CA as needed. The contractor shall assist NAWCAD 4.11.3 in providing on-site support while the ship is in port for Ship Alterations (SHIPALTs), overhauls or other operational issues.

Maintaining credibility with the crew and responsiveness to the fleet authorities is critical to the success of this effort. The support effort can fluctuate based on fleet needs, ships in port, but response times and deployment to the ships many times can dictate a very narrow window to ensure proper support. The contractor must be prepared to handle surge capacities, response times and the flexibility that recognize the fleet’s deployment needs.

4.1.5 The contractor shall prepare Information Assurance documentation for application

Certification and Accreditation (C&A) of Government software and systems as dictated by specific task orders in accordance with US Fleet Cyber Command (FCC)/Space and Naval

Warfare (SPAWAR) Command Navy Authorizing Official and Security Control Assessor Risk

Management Framework Process Guide. (CDRL A010)

4.2 Software Engineering, Development and Integration (CLINs 0002, 0003, 0004, 0005)

Typical software engineering, development and integration tasks include purchasing and evaluating new software and hardware technologies for innovative and enhanced interactive products and tools. Developing concept of operations, performing requirements analysis, system design, data conversion, development, quality assurance, deployment, and training to meet mission oriented requirements.

4.2.1 The contractor shall evaluate and report on emerging engineering and information technologies including innovative C4I engineering enhancements and technological pursuits, multimedia, user interfaces, technical data markup, and software development tools and techniques and recommend application of new technology for product improvement or cost reduction. In analyzing the benefits of these product improvements and cost reductions, the contractor will be required to maintain and report metrics that will support the benefit of these new tools and techniques. (CDRL A001)

4.2.2 The contractor shall recommend standards-based technical approaches that support Navy or DoD sponsored product development and develop technical specifications and Concepts of

Operations (CONOPS) for automation of engineering processes based on the identified operational and functional performance requirements. (CDRL A001)

4.2.3 The contractor shall conduct detailed user requirements analyses to determine and document business processes, administrative, technical and software engineering support requirements (CDRL A002), and recommend deployment options and strategy. (CDRL A001)

4.2.4 The contractor shall design system architectures and products. Specifically, the contractor shall:

4.2.4.1 Translate client requirements to system design recommendations and provide database design descriptions, user interface layout, wireframes, storyboarding, prototypes and design documentation that support required deployment environments. (CDRL A009)

4.2.4.2 Design automation processes for the creation of technical engineering and performance support data for use in content delivery applications. (CDRL A003)

4.2.4.3 Support component and content reuse as part of software integration, including the following:

4.2.4.3.1 Object, module, or component reuse to enhance deployment flexibility and efficiency in stand-alone, network, and learning management system (LMS) applications. (CDRL A003)

4.2.4.3.2 Reusable content strategies implementing standard markup languages such as XML, S1000D, and SVG for storage in files, relational databases and content management repositories.

Content shall be in conformance with NAVAIR policy and specification guidance or other standards required by NAWCAD 4.11.3 customers. (CDRL A003)

4.2.4.3.3 Transformation and rendering to enable the reuse of content with technologies such as

XSLT and eXtensible Stylesheet Language-Formatting Objects (XSL-FO). (CDRL A003)

4.2.4.3.4 Adoption and adaptation of XML content models to accommodate data structures and documents for the storage, display, and print of data from content delivery and content management systems. (CDRL A003)

4.2.5 The contractor shall define, facilitate, and support data conversion processes for transformation of technical data of various types (e.g., technical manuals, engineering drawings, program data, etc.) to other standards and formats that comply with Navy policy and improve usability and reduce costs. (CDRL A003)

4.2.6 The contractor shall integrate, develop, and maintain software-based solutions and shall use Commercial Off-the-Shelf (COTS) or Government Off-the-Shelf (GOTS) products to the maximum extent possible. In addition to the wide variety of software program tasking mentioned elsewhere in this SOW, the contractor may be required to support a wide variety of additional programming languages, web applications, web services, multimedia, prototyping, markup languages, data repositories, application frameworks, components, installations, and documentation methods as future tasking may require. In the event custom software is required, the contractor shall comply with applicable Navy, NAVAIR, NAVSEA, or other agency software development or purchasing requirements as specified by NAWCAD 4.11.3.

4.2.6.1 Software must be compliant with NMCI requirements, be approved for use in the DoN

Application Database Management System (DADMS), and certified to run on ships’

NIAPS/CANES networks as required. The contractor shall support compliance with DoD

Information Assurance (IA) procedures and develop required documentation and accreditation when required. The contractor shall document and maintain IA artifacts in Enterprise Mission

Assurance Support Service (eMASS). (CDRL A010)

4.2.6.2 In developing new software based products, the contractor shall develop interactive performance solutions to include reference, educational, or training systems with the goal of improving the efficiency and effectiveness of installation, operation, maintenance, and safety tasks. These products may be required to deliver content compliant with specific deployment standards and infrastructures. Content shall also be provided as XML or S1000D as specified by

NAWCAD 4.11.3. (CDRL A008)

4.2.6.3 The contractor shall develop and maintain Shareable Content Object Reference Model

(SCORM) compliant training modules for learning management systems such as Navy

Knowledge Online (NKO) and Marine Corps Aviation Learning Management System

(MCALMS). Some of these products have a requirement to be game-based with a scoring mechanism. These products must run in a stand-alone format (from CD-ROM) or on customer based web sites. (CDRL A008)

4.2.6.4 The contractor shall develop Interactive Electronic Technical Manuals (IETMs) to include building customized IETM content for the NavXML IETM viewer using data transformations, XSLT scripts, and the NavXML Authoring tools. Content may use the

NavXML XML DTD format or the NavXML implementation of S1000D. Other viewers that may be used include the NAVAIR Standard IETM Viewer (NSIV) and NAVSEA standard viewer, LiveContent. (CDRL A008)

4.2.6.5 The contractor shall provide knowledge management (KM) and virtual collaboration subject matter expertise and technical skills. This includes situational awareness of emerging technologies and methodologies in the field of KM. (CDRL A008)

4.2.6.6 The Government will have unlimited rights of software to use, modify, reproduce, release, perform, display, or disclose computer software or computer software documentation in whole or in part, in any manner and for any purpose whatsoever, and to have or authorize others to do so. The Government will own such software rights and any software developed, and the contractor shall deliver all source code, media files, configuration files, and programming documentation developed under this contract, including all ancillary files, required for the

Government to maintain, document, and reproduce the product. (CDRL A008)

4.2.7 Quality Assurance (QA) and Testing: The contractor shall perform quality assurance and testing activities on developed software products and on resultant data outputs. Specifically, the contractor shall:

4.2.7.1 Define and document QA plans including roles, responsibilities, and tools for performing

QA activities and ensuring quality products and services. QA Plans shall include requirements traceability, product version tracking, discrepancy tracking, and resolutions. (CDRL A017)

4.2.7.2 Develop the test plans and procedures necessary to verify the operational and technical parameters of developed and procured software. (CDRL A005)

4.2.7.3 Conduct testing protocols and document the results. Identify and document discrepancies, as well as the actions taken to resolve those discrepancies. (CDRL A006)

4.2.8 The contractor shall use standard content management products, processes, and delivery systems to support deployment requirements as dictated by specific task orders. In addition, the contractor shall be required to support the following content development strategies:

4.2.8.1 Integrate and customize authoring system software to automate the creation of technical engineering and performance support data for use in content delivery applications. (CDRL

A008)

4.2.8.2 Integrate and customize content management tools and repositories to create, reuse, assemble, and publish content to a variety of outputs.

4.2.8.3 Provide publishing workflow management.

4.2.8.4 Integrate or develop software for performance support content creation using

SGML/XML/S1000D and other applicable standards. (CDRL A008)

4.2.8.5 Package performance support content for Sharable Content Object Reference Model

(SCORM) or Learning Management System (LMS) compliance with specified standards and deployment infrastructure. (CDRL A008)

4.2.8.6 Create software user manuals. (CDRL A007)

4.3 Engineering Support (CLINs 0002, 0003, 0005)

The contractor shall support engineering documentation development, review, and distribution of a wide variety of technical and knowledge based documents relating to:

Operations Manuals

Technical Manuals

Maintenance And Repair Manuals

Commercial and Military Equipment Specifications Manuals

Commercial and Military Equipment Policy Manuals

Engineering Drawings

Equipment Alteration Drawings and Specifications

Charts

Maps

Specifically, the contractor shall:

4.3.1 Analyze technical document architectures and standards, training, planning and policy documents. Assess interoperability and implementation across applicable information systems.

(CDRL A001)

4.3.2 Interface with DoD policy activities by reviewing draft documents, participating in planning processes, and recommending language that is consistent with practical and efficient software development practices. (CDRL A001)

4.3.3 Provide test, evaluation and support for implementation or review of DoD, Navy, and international standards initiatives. (CDRL A001)

4.3.4 Analyze information processing requirements relating to automation of maintenance support systems including data collection, documentation, and analysis. (CDRL A001)

4.3.5 Provide engineering inputs to interactive publications development for NAWCAD 4.11.3 and DoD operational communities. (CDRL A001)

4.4 Technical Support (CLINs 0002, 0003, 0004, 0005)

4.4.1 Establish and maintain reliable methods of communication with NAWCAD 4.11.3 to effectively and efficiently transfer information necessary to support the conduct of project and contract-related operations.

4.4.2 Communicate and coordinate with internal and external stakeholders on technical and programmatic issues, and collect feedback.