N66001-17-R-0011 FINAL.pdf

CODE

(Hour)

PAGE(S)

until 08:00 AM local time 16 May 2017

X

A X B X C

D

EX

X G F 76 - 89

90 - 105 X H 106 - 111 kayla.garcia@navy.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

1 111

(If other than Item 7) N66001

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N66001 8. ADDRESS OFFER TO

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

Section L conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

KAYLA L. GARCIA 619-553-5727

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 6

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

7 - 21 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 24 - 29 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 30 - 45 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

46 - 74

PART II - CONTRACT CLAUSES

SPAWAR SYSTEMS CENTER PACIFIC

KAYLA L. GARCIA, CODE 22560

KAYLA.GARCIA@NAVY.MIL

53560 HULL STREET

SAN DIEGO CA 92152-5001

SEE CLAUSE L-349

ELECTRONIC SUBMISSION

HTTPS://E-COMMERCE.SSCNO.NMCI.NAVY.MIL/

CA 619-553-5727

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.

1300592767

5. DATE ISSUED

13 Apr 2017

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N66001-17-R-0011

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 Lot Engineering Services

CPFF

Base period of two years. Provide services in accordance with the Statement of Work, Section C, as specified in individual task orders.

FOB: Destination

PURCHASE REQUEST NUMBER: 1300592767

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002 Lot Other Direct Costs (ODC)

COST

Base period of two years. ODC including but not limited to travel, materials, and equipment.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

0003 Lot Data-Base Period-Not Separately Priced

0004 Lot OPTION Engineering Services

CPFF

Option period of three years. Provide services in accordance with the Statement of Work, Section C, as specified in individual task orders.

FIXED FEE

TOTAL EST COST + FEE

0005 Lot Other Direct Costs (ODC)

COST

Option period of three years. ODC including but not limited to travel, materials, and equipment.

OPTION

0006 Lot OPTION Data-Option Period-Not Separately Priced

CLAUSES INCORPORATED BY FULL TEXT

5252.216-9200 PAYMENT OF FIXED FEE (COMPLETION TYPE) (JAN 1989)

***This clause shall be used in completion type task orders.***

FIXED FEE: $*. The Government shall make payment to the Contractor when requested as work progresses, but no more frequently than biweekly, on account of the fixed fee, equal to ** percent of the amounts invoiced by the Contractor under the “Allowable Cost and Payment” clause hereof for the related period, subject to the withholding provisions of paragraph (b) of the “Fixed Fee” clause. In the event of discontinuance of the work in accordance with clause of this contract entitled “Limitation of *** the fixed fee shall be redetermined by mutual agreement equitably to reflect the diminution of the work performed; the amount by which such fixed fee is less than, or exceeds payments previously made on account of fee, shall be paid, or repaid by, the Contractor, as the case may be.

* To be completed upon award of the contract

** To be determined at the Task Order level. The allowable fee percentage will be negotiated at the Task Order level, and shall not exceed the percentage proposed at the basic contract level

*** To be determined at the Task Order level.

(End of clause)

5252.216-9204 LEVEL OF EFFORT--FEE ADJUSTMENT FORMULA (MAR 1994)

***This clause shall be used in term/level-of-effort task orders.***

(a) Subject to the provisions of the “Limitation of Cost” or “Limitation of Funds” clause (whichever is applicable to this contract), it is hereby understood and agreed that the fixed fee is based upon the Contractor providing the below listed number of staff-hours of direct labor, hereinafter referred to as X, at the estimated cost and during the term of this contract specified elsewhere herein:

[Contracting officer insert number of estimated direct labor staff hours]

CLIN Total Staff-hours of Direct Labor (X)

The Contractor agrees to provide the total level of effort specified above in performance of work described in Sections “B” and “C” of this contract. The total staff-hours of direct labor shall include subcontractor direct labor hours for those subcontractors identified in the Contractor’s proposal as having hours included in the proposed level of effort.

(b) Of the total staff-hours of direct labor set forth above, it is estimated that [Contracting officer insert number of estimated direct staff hours identified as competitive (uncompensated overtime) hours] staff-hours are competitive time (uncompensated overtime). Competitive time (uncompensated overtime) is defined as hours provided by personnel in excess of 40 hours per week without additional compensation for such excess work. All other effort is defined as compensated effort. If no amount is indicated in the first sentence of this paragraph, competitive time (uncompensated overtime) effort performed by the contractor shall not be counted in fulfillment of the level of effort obligations under this contract.

(c) Effort performed in fulfilling the total level of effort obligations specified above shall only include effort performed in direct support of this contract and shall not include time and effort expended on such things as local travel from an employee’s residence to their usual work location, uncompensated effort while on travel status, truncated lunch periods, or other time and effort which does not have a specific and direct contribution to the tasks described in Section B.

(d) It is understood and agreed that various conditions may exist prior to or upon expiration of the term of the contract, with regard to the expenditure of labor staff-hours and/or costs thereunder which may require adjustment to the aggregate fixed fee. The following actions shall be dictated by the existence of said conditions:

(1) If the Contractor has provided not more than 105% of X or not less than 95% of X, within the estimated cost, and at the term of the contract, then the fee shall remain as set forth in Section B.

(2) If the Contractor has provided X-staff-hours, within the term, and has not exceeded the estimated cost then the Contracting Officer may require the Contractor to continue performance until the expiration of the term, or until the expenditure of the estimated cost of the contract except that, in the case of any items or tasks funded with O&MN funds, performance shall not extend beyond 30 September. In no event shall the Contractor be required to provide more than 105% of X within the term and estimated cost of this contract. The fee shall remain as set forth in Section B.

(3) If the Contractor expends the estimated cost of the contract, during the term of the contract and has provided less than X staff-hours, the Government may require the Contractor to continue performance, by providing cost growth funding, without adjusting the fixed fee, until such time as the Contractor has provided X staff-hours.

(4) If the Contracting Officer does not elect to exercise the Government’s rights as set forth in paragraph (d)(2) and (d)(3) above, and the Contractor has not expended more than 95% of X staff-hours, the fixed fee shall be equitably adjusted downward to reflect the diminution of work.

(5) Nothing herein contained shall, in any way, abrogate the Contractor’s responsibilities, and/or the Government’s rights within the terms of the contract provision entitled “Limitation of Cost” or “Limitation of Funds” as they shall apply throughout the term of the contract, based upon the total amount of funding allotted to the contract during its specified term.

(e) Within 45 days after completion of the work under each separately identified period of performance hereunder, the Contractor shall submit the following information in writing to the Contracting Officer with copies to the cognizant Contract Administration Office and DCAA office to which vouchers are submitted:

(1) The total number of staff-hours of direct labor expended during the applicable period.

(2) A breakdown of this total showing the number of staff-hours expended in each direct labor classification and associated direct and indirect costs.

(3) A breakdown of other costs incurred.

(4) The Contractor’s estimate of the total allowable cost incurred under the contract for the period.

In the case of a cost under-run, the Contractor shall submit the following information in addition to that required above:

(5) The amount by which the estimated cost of this contract may be reduced to recover excess funds and the total amount of staff-hours not expended, if any.

(6) A calculation of the appropriate fee reduction in accordance with this clause.

All submissions required by this paragraph shall include subcontractor information, if any.

(f) SPECIAL INSTRUCTION TO THE PAYING OFFICE REGARDING WITHHELD FEE

Fees withheld pursuant to the provisions of this contract, such as the withholding provided by the “Allowable Cost and Payment” and “Fixed Fee” clauses, shall not be paid until the contract has been modified to reduce the fixed fee in accordance with paragraph (d) above, except that no such action is required if the total level of effort provided falls within the limits established in paragraph (d) above.

5252.216-9218 MINIMUM AND MAXIMUM QUANTITIES (JUL 1989)

As referred to in paragraph (b) of the “Indefinite Quantity” clause of this contract, the contract minimum quantity is a total of $100,000 divided by the number of contract awardees. The maximum quantity is the total estimated amount of the contract. The maximum quantity is not to be exceeded without prior approval of the Procuring Contracting Officer.

5252.232-9200 ALLOTMENT OF FUNDS (JAN 1989)

*** This clause shall be used in incrementally funded task orders.***

(a) This contract is incrementally funded with respect to both cost and fee.

(b) The amounts presently available and allotted to this contract for payment of fee, as provided in the Section I clause of this contract entitled “Fixed Fee”, are as follows:

[Contracting officer under “Items” insert the item numbers for which incremental funding is provided and under “Allotted to Fixed Fee” insert the amount of incremental funding allocated to fixed fee]

ITEM(S) ALLOTTED TO FIXED FEE

(c) The amounts presently available and allotted to this contract for payment of cost, subject to the Section I “Limitation of Funds” clause, the items covered thereby and the period of performance which it is estimated the allotted amount will cover are as follows:

[Contracting officer under “Items” insert the item numbers for which incremental funding is provided, under “Allotment of Cost” insert the amount of incremental funding allocated to total estimated cost, and under “Period of Performance” insert date by which funding expended]

ITEM(S) ALLOTTED TO COST PERIOD OF PERFORMANCE

(d) The parties contemplate that the Government will allot additional amounts to this contract from time to time by unilateral contract modification, and any such modification shall state separately the amounts allotted for cost and for fee, the items covered thereby, and the period of performance the amounts are expected to cover.

Section C - Descriptions and Specifications

STATEMENT OF WORK

Title: Information Operations (IO) and Meteorology and Oceanography (METOC) Engineering Services and Software Development

1.0 SCOPE

This effort provides engineering services to include software development, testing, integration and documentation of Information Operations (IO) and Meteorology and Oceanography (METOC) systems in support of Program Executive Office (PEO) Command, Control, Communications, Computers, Intelligence (C4I) programs and SSC- Pacific Projects. This effort supports providing METOC and IO capabilities to the United States Navy (USN), United States Marine Corps (USMC), Joint, and Coalition Forces engaged in supporting Department of Defense (DoD) operations worldwide, both ashore and afloat, for customers including SPAWAR, PEO C4I and PMW-120.

1.1 BACKGROUND

Space and Naval Warfare Systems Center Pacific (SSC Pacific) has a vision of being the Nation’s pre-eminent Technical Leader for integrated Command, Control, Communications, Computers and Intelligence (C4I) needs of the Navy. The Navy’s C4I systems are vital to the goal of achieving and maintaining Information Dominance. A key pillar of Information Dominance is Battlespace Awareness. SSC Pacific provides solutions for many systems that contribute to Battlespace Awareness, including IO and METOC. Battlespace awareness consists of three key environments: Information, Physical and Threat. The threat environment is addressed by Intelligence Surveillance and Reconnaissance (ISR) systems that are largely supported by systems operating at security levels outside the scope of this contract. The Information environment is addressed by IO systems and the Physical environment by METOC systems. Under this construct, SSC Pacific supports and assists with the planning, development, integration, maintenance, and operation of systems which enable future synergy and seamless integration of IO and METOC information across the Navy’s C4I systems.

Commander, Naval Meteorology and Oceanography Command (COMNAVMETOCCOM) has the mission to collect, interpret, and apply global atmospheric and oceanographic data and information in support of strategic, operational and tactical warfare and US human assistance/disaster relief (HA/DR) missions. As such, COMNAVMETOCCOM directly supports the operational intelligence, surveillance, and reconnaissance missions of the nation’s deployed forces and provides around-the-clock operational oceanographic and meteorological support to the U.S. Navy, other U.S. Government agencies, and elements of the armed forces of allied nations. This support consists of running regularly-scheduled, large physical environment numerical global forecast models for ships, aircraft, and other forces throughout the DoD. Greater emphasis on preparation for and reaction to regional conflicts and the littoral threat has resulted in a greatly increased demand for high-resolution coupled-model meteorological guidance and forecasts, as well as oceanographic support to tactical coastal operations.

The primary Program of Record for the Navy’s C4I Enterprise afloat METOC capability is the Naval Integrated Tactical Environmental System Next Generation (NITES-Next). NITES-Next is a software-centric program that provides capabilities to order, process, store, and analyze METOC data and information products. NITES-Next provides users the ability to assess the impact of present and forecasted atmospheric, surface, and oceanographic METOC conditions on warfighter operations, weapon systems and sensor systems, and allows the display and visualization of tailored METOC products. NITES-Next provides METOC data and products to METOC units, mission planning systems, Joint Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) systems, sensor systems, and decision support systems. NITES-Next is comprised of net-centric capabilities that interoperate within the DoD Information Enterprise Architecture (IEA) to provide METOC capabilities to the USN, USMC, Joint, and Coalition Forces engaged in supporting DoD operations worldwide, both ashore and afloat.

NITES-Next is responsible for the timely transition of METOC Tactical Decision Aids, along with other applications from Research and Development and current operations, into a DoD IEA-compliant integration environment. The NITES-Next software design allows for integration with other METOC and non-METOC common architectures. NITES-Next provides significant improvements over the previously fielded systems by meeting the requirements of Joint, net-centric warfighting. Net-Centric warfighting takes place in a highly-variable physical environment, which requires achievement of accurate characterization and assessment of specific operational impacts.

The Navy’s IO and METOC programs must continue to evolve as new systems are deployed which rely on the crucial data and decision aids they provide. These programs must also evolve with changing infrastructure and network architectures. An increasing number of afloat platforms are being deployed with Consolidated Afloat Networks and Enterprise Services (CANES). CANES delivers systematic refreshes of both hardware and software and all applications residing on CANES are required to participate in Application Integration Events prior to being fielded. This requires regular software development and integration by IO and METOC systems prior to each new CANES release. In addition to CANES-equipped ships, IO and METOC systems must be engineered to operate on a wide variety of other platforms.

2.0 REFERENCE DOCUMENTS

The following documents were used in the development of this Statement of Work (SOW) and may be incorporated for individual delivery/task orders. Nothing in the documents however, shall supersede applicable laws and regulations, unless a specific exemption has been obtained. The Contractor’s solution shall comply with current documentation, standards and guidance as outlined in each task order.

a. DoD 5220.22-M, DoD Manual – National Industrial Security Program Operating Manual

b. NISPOM) dtd 28 Feb 06

c. DoDI 5220.22, DoD Instruction – National Industrial Security Program dtd 18 Mar 11

d. DoD 5200.02-R, DoD Regulation – Personnel Security Program dtd Jan 87

e. DoDI 6205.4, Department of Defense Instruction, Immunization of Other Than U.S. Forces (OTUSF) for

Biological Warfare Defense dtd 14 Apr 2000

f. DoDI 8500.01, DoD Instruction – Cybersecurity dtd 14 Mar 14

g. DoDI 8510.01, DoD Instruction – Risk Management Framework (RMF) for DoD Information Technology

(IT) dtd 12 Mar 14

h. DoDD 8570.01, DoD Directive – Information Assurance Training, Certification, and Workforce

Management dtd 15 Aug 04

i. DoD 8570.01-M , Information Assurance Workforce Improvement Program dtd 24 Jan 12

j. SECNAV M-5239.2, DON Information Assurance Workforce Management Manual dtd 17 Jun 2010

k. SECNAV M-5510.30, Secretary of the Navy Manual – DoN Personnel Security Program dtd 6 Oct 2006

l. SECNAVINST 5239.3B, DoN Information Assurance Policy, 14 Jun 09

m. SECNAVINST 5510.30, DoN Regulation – Personnel Security Program dtd 30 Jun 06

n. SPAWARINST 3432.1, SPAWAR Instruction – Operations Security (OPSEC) Policy dtd 2 Feb 05

o. OPNAVINST 3432.1 (Series), DON Operations Security dtd 29 Aug 95

p. SPAWARINST 4440.12, Management of Operating Materials and Supplies (OM&S), Government

Furnished Property (GFP), Contractor Acquired Property (CAP), Property, Plant and Equipment (PP&E), and Inventory dtd 10 Mar 11

q. SPAWARINST 5721.1B, SPAWAR Section 508 Implementation Policy, 17 Nov 09

r. NAVSUP P-723, Navy Inventory Integrity Procedures, dtd 19 April 2000

s. NIST SP 800-Series, National Institute of Standards and Technology Special Publications 800 Series –

Computer Security Policies, Procedures, and Guidelines dtd Dec 90

t. ISO 9001, Quality Management Systems, Requirements, version 9001:2015

u. ISO/IEC/IEEE 15288, Systems and software engineering – System life cycle processes, version

15288:2015

v. ISO/IEC/IEEE 15288.1, Standard for Application of Systems Engineering on Defense Programs, 15 May

w. ISO/IEC/IEEE 15288.2, Standard for Technical Reviews and Audits on Defense Programs, 15 May 2015

x. IEEE Std 12207-2008, Systems and Software Engineering – Software Life Cycle Processes, 2008

y. EIA-748, Earned Value Management (EVM) Systems dtd 5 Sep 13

z. Form I-9, OMB No. 115-0136, US Department of Justice, Immigration and Naturalization Services, Form

I-9, OMB No. 115-0136 – Employment Eligibility Verification dtd 21 Nov 91

aa. DoDM 5200.01, DoD Manual – Information Security Program Manual dtd 24 Feb 12

bb. DoDD 5205.02E, DoD Directive – Operations Security (OPSEC) Program dtd 20 Jun 12

cc. DoD 5205.02-M, DoD Manual – Operations Security (OPSED) Program Manual dtd 3 Nov 08

dd. DoDD 8140.01, Cyberspace Workforce Management dtd 11 Aug 15

ee. SECNAV M-5239.2, CON Cyberspace Information Technology and Cybersecurity Workforce

Management and Qualification Manual dtd Jun 16

ff. SECNAVINST 4440.34, Secretary of the Navy Instruction – Implementation of Item Unique Identification within the DoN, dtd 22 Dec 09

gg. SECNAVINST 5239.19, Incident Response, dtd Mar 08

hh. SECNAVINST 5239.20A, DON Cyberspace IT Cybersecurity, dtd 10 Feb 16

ii. SECNAVINST 5239.3C, DON Cybersecurity Policy, dtd 2 May 16

jj. DON CIO Memorandum, Acceptable Use of Department of the Navy Information Technology (IT), dtd 12

Feb 16

kk. COMUSFLTFORCOM/COMPACFLTINST 6320.3A, Commander US Fleet Forces

Command/Commander US Pacific Fleet Instruction, Medical Screening for US Govt Civilian Employees, Contractor Personnel, and Guests prior to embarking Fleet Units, of 7 May 13

ll. Navy Telecommunications Directive (NTD 10-11), System Authorization Access Request (SAAR)- Navy

3.0 PERFORMANCE REQUIREMENTS

The Contractor shall perform the following tasks, as specified at the task order level.

3.1 BATTLESPACE AWARENESS

3.1.1 SYSTEMS ENGINEERING

The Contractor shall provide engineering, manufacturing, software and operational systems support as required by applicable task orders. Support includes, systems evaluations, design analysis, and hardware/software maintenance using documented processes such as the Capability Maturity Model Integrated (CMMI) processes to ensure the quality and maintainability of designated systems. The Contractor shall also:

- Provide recommendations for achieving goals and objectives by identifying and analyzing potential program risks, track events, prepare impact statements and assessments, identify and recommend technical solutions and alternatives and assess the results.

- Review and evaluate reports, plans, specifications, technical documentation, and design disclosure documentation.

- Participate in Integrated Product Teams (IPTs) such as the METOC Fleet Collaborative Team, ISR Future Capability Team (FCT).

- Track and assess how external programs, such as CANES, will impact METOC or Information Operations Programs.

- Provide architecture, system, and software engineering and design support to METOC and IO Programs as defined in individual task orders.

3.1.1.1 Enterprise Architecture Support

As defined in applicable task orders, the Contractor shall provide Department of Defense Architecture Framework (DoDAF) systems and subsystem definition support.

3.1.1.2 Modeling and Simulation Support

As defined in applicable task orders, the Contractor shall provide project level Modeling and Simulation (M&S) support to include, but not be limited to, virtual M&S, M&S data extraction and analysis, and generation of test data/script/reports. The Contractor shall provide M&S updates and maintenance.

3.1.1.3 Development Support

As defined in applicable task orders, the Contractor shall provide engineering, manufacturing, software and operational systems development support, including systems evaluations, design analysis, and hardware/software development using documented processes such as the Agile Development and CMMI to ensure the quality and maintainability of designated systems.

3.1.1.4 Fleet Engineering Support

As defined in applicable task orders, the Contractor shall provide fleet engineering support which may include:

- On call, on-site technical services on equipment/systems to provide site survey, development, integration, troubleshooting, checkout, repair and test of communications and information network systems worldwide, as specified in individual task orders.

- Development, validation and maintenance of drawing packages, drawing trees, "As-Built" drawings, and block diagrams.

3.1.2 TECHNICAL SUPPORT

The Contractor shall map System Requirements identified in each task order to existing or new software configuration items that have been developed by the Government and those that require new development by the Contractor.

3.2 BATTLESPACE AWARENESS SOFTWARE

3.2.1 SOFTWARE DEVELOPMENT

The Contractor shall define a software development approach appropriate for the software design and development effort to be performed under this contract. This approach shall be documented in a Software Development Plan (SDP) (see DID No. DI-IPSC-81427A for required format and content). Once defined, the Contractor shall follow this SDP for all computer software to be developed or maintained under this contract.

The SDP shall define the offeror’s proposed life cycle model and the processes used as a part of that model. In this context, the term “life cycle model” is as defined in IEEE/EIA Std. 12207.0. The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of this contract.

In accordance with the framework defined in IEEE/EIA Std. 12207.0, the SDP shall define the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks. Because IEEE/EIA Std. 12207 does not prescribe how to accomplish the task, the offeror must provide this detailed information so the Government can assess whether the offeror’s approach is viable.

The SDP shall contain the information defined by IEEE/EIA Std. 12207.1, section 5.2.1 (generic content) and the Plans or Procedures in Table 1 of IEEE/EIA Std. 12207.1. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include, as a minimum, specific standard, methods, tools, action, strategies, and responsibilities associated with development and qualification.

The Contractor’s software engineering approach shall afford opportunities for input and oversight by the Government.

3.2.1.1 SOFTWARE DESIGN

The Contractor shall perform software design, development, and verification functions and shall deliver computer software end items and required documentation to support METOC software development and capability improvements. This effort shall include the following items.

-The Contractor shall develop software products to meet the requirements specified at the task order level.

- In the event the Contractor changes program baseline software, the Contractor shall ensure that all program requirements are met by successfully passing testing administered using the approved test procedures for the accepting program.

-For any changes to the development approach, the Contractor shall provide notification to the Government via a report IAW applicable task order requirements. The report shall outline the agreed-upon way forward in the development of software products under this SOW. As required at the task order level, the Contractor shall update their SDP for implementing requirements.

-The Contractor shall provide testable software as outlined at the task order level. The Contractor shall deliver executable acceptance tests for each software delivery. The Government will approve the acceptance tests to confirm the software is ready for Government testing. The Contractor shall develop a plan IAW applicable task order requirements showing how the Contractor will fully implement all requirements prior to the start of Government system integration events.

-The Contractor shall use a Government-approved software repository to make available to the Government all of the source code and all associated supporting documentation required to build, install, and configure delivered software IAW applicable task order requirements.

- The Contractor shall provide support to the SSC Pacific integration and test teams during integration and requirements testing in the Government test facilities.

-The Contractor shall provide support to the Government test teams during major test events, to include but not limited to CANES testing and end-to-end testing. Work shall be performed at Government test facilities.

-The Contractor shall participate in cross-pillar coordination meetings at Government invitation (e.g. between PEO C4I, PMW 120 and SSC Pacific Information Operations and Intelligence, Surveillance and Reconnaissance Divisions). The Contractor shall participate in weekly working group meetings led by SSC Pacific as required at the task order level.

-The Contractor shall review and provide comments on material developed by the Government to document the Contractor-developed software. This material includes but is not limited to information for design, installation, and user guides, as required at the task order level.

-The Contractor shall address software problems captured in System Problem Reports (SPRs) during Government software testing and resolve those to the satisfaction of the Government.

-The Contractor shall attend Government design reviews and provide presentation material as required at the task order level.

-The Contractor shall work with SSC Pacific and requiring customers including PMW 120 Information Assurance (IA) and Human Systems Interface (HSI) teams to ensure that software development activities meet the Government security requirements as defined in each task order, optimize user workflow, and reduce user workload and error.

The IA effort includes implementing the Defense Information Systems Agency (DISA) Application Security Development Security Technical Implementation Guide (STIG).

-The Contractor shall develop software products using a common development environment as specified by the SSC Pacific Software Integration Team.

-The Contractor shall develop and maintain Software Component Documents detailing the architecture, software components, design rationale, appropriate Unified Modeling Language (UML) diagrams, external and internal interfaces, data flows, data structure, and databases that are interfaced. The Contractor shall provide input to design documentation for system changes and follow the approved format provided by the receiving program. This deliverable will also include the Contractor’s schedule for document development and updates IAW the applicable task order.

-The Contractor shall participate in the METOC and IO Local Change Configuration Board (LCCB), when providing software development support for NITES-Next as required at the task order level.

3.2.1.2 AGILE DEVELOPMENT

When directed by task order the Contractor shall employ Contractor-tailored agile software development processes to meet the NITES-Next requirements and shall deliver Open Geospatial Consortium (OGC) compliant, Geospatial Information and Services-METOC products accessible through the Ozone Widget Framework (OWF). The Contractor shall develop software using current development STIG as approved by the Government IA Manager.

Where applicable, products shall meet interoperability certification standards as outlined in Joint Interoperability Test Command (JITC) Interoperability Process Guide 2.0.

The Contractor-developed software shall meet METOC requirements as specified at the task order level and verified by SSC Pacific test team.

As required by individual task orders, the Contractor shall maintain prioritized backlogs with point estimates for each of the following categories:

• Requirement

• HSI

• Bug

• Enhancements

• Infrastructure

• Other

3.2.2 SYSTEM ARCHITECTURE

The Contractor shall provide input to the overall baseline for METOC and IO. The baseline for NITES-Next defines the system architecture and includes:

• System-Wide Design Decisions

• Department of Defense Architecture Framework views

• Allocation of System Requirements to Software Components

• Additional system design information – system data flow diagram, deployment diagram, functional architecture diagram.

3.3 GENERAL

The Contractor shall provide technical and program management support services of the overall development efforts to include project planning, project execution, and project control. The Contractor shall provide technical and management services that enable rapid development and deployment of new capabilities for IO and METOC related systems.

The Contractor shall develop, maintain, and monitor cost, schedule, software development, and metrics and present the status of these metrics at all programmatic/design/technical reviews and working group meetings, as required by applicable task orders. This support will also include reviews and meetings, task order award briefs, software maintenance and upgrade support IAW applicable documents. Additionally, the Contractor shall provide training and logistics support including identifying software changes, update and install software to meet training environment requirements, and configuration management, IAW applicable documents.

4.0 GOVERNMENT FURNISHED INFORMATION, PROPERTY AND EQUIPMENT

Government Furnished Information (GFI), Government Furnished Property (GFP), and Government Furnished Equipment (GFE) will be specified at the task order level; use and disclosure language will apply as specified at the task order level.

5.0 TRAVEL

Travel will be specified at the task order level.

6.0 OTHER

6.1 SECURITY

The nature of tasks within this contract requires access to SECRET information and shall not exceed the SECRET level. This effort will be unclassified and at the Secret level; therefore, the Contractor will be required to provide individuals with security clearances at the appropriate classification levels, as specified in individual task orders.

Some tasks will require Secret Internet Protocol Router (SIPRnet) Network access at Government labs. For Contractor personnel supporting onsite Government lab testing, additional security training may be required by the Government prior to having access to Government computers. Individual task orders may also require contract personnel to be North Atlantic Treaty Organization (NATO) briefed by their company facility security officer in order for Contractor personnel to have access to SIPRnet

Anti-Terrorism/Force Protection (AT/FP) briefings are required for all personnel (Military, DOD Civilian, and Contractor) per OPNAVINST F3300.53C. Contractor employees must receive the AT/FP briefing annually. The briefing is available at https://atlevel1.dtic.mil/at/, if experiencing problems accessing this website contact ssc_fortrav@navy.mil.

All software will be developed using current development STIG as approved by the Government IA Manager.

Where applicable, products shall meet interoperability certification standards as outlined in Joint Interoperability Test Command (JITC) Interoperability Process Guide 2.0.

As required by National Industrial Security Program Operating Manual (NISPOM) Chapter 1, Section 3, contractors are required to report certain events that have an impact on: 1) the status of the facility clearance (FCL); 2) the status of an employee's personnel clearance (PCL); 3) the proper safeguarding of classified information; 4) or an indication that classified information has been lost or compromised. Contractors working under SSC Pacific contracts will ensure information pertaining to assigned contractor personnel are reported to the Contracting Officer Representative (COR)/Technical Point of Contact (TPOC), the Contracting Specialist, and the Security's COR in addition to notifying appropriate agencies such as Cognizant Security Agency (CSA), Cognizant Security Office (CSO), or Department Of Defense Central Adjudication Facility (DODCAF) when that information relates to the denial, suspension, or revocation of a security clearance of any assigned personnel; any adverse information on an assigned employee's continued suitability for continued access to classified access; any instance of loss or compromise, or suspected loss or compromise, of classified information; actual, probable or possible espionage, sabotage, or subversive information; or any other circumstances of a security nature that would affect the contractor's operation while working under SSC Pacific contracts.

6.2 OPERATIONS SECURITY (OPSEC)

OPSEC is a five step analytical process (identify critical information; analyze the threat; analyze vulnerabilities;

assess risk; develop countermeasures) that is used as a means to identify, control, and protect unclassified and unclassified sensitive information associated with U.S. national security related programs and activities. All personnel working under this task will at some time handle, produce or process Critical Information or CPI, and therefore all personnel must practice OPSEC. All work is to be performed in accordance with DoD and OPSEC requirements and in accordance with the OPSEC attachment to the DD254.

6.3 PLACE OF PERFORMANCE

The below percentages represent estimates of the amount of work to be performed at each location over the life of this contract. Specific requirements will be specified in individual task orders.

50% SSC Pacific, San Diego, CA 50% Contractor’s facility

6.4 CONTRACTING OFFICER REPRESENTATIVES (COR)

The COR will be identified by task order for the projects and/or programs they support as outlined in

SPAWARINST 4240.1.

6.5 CYBER SECURITY/ INFORMATION ASSURANCE (IA) WORK FORCE

All cybersecurity functions to be performed under this contract will be identified in H-1 and at the task order level.

Task orders will specify, as applicable, Cybersecurity Workforce category, level, training, and certification requirements for Contractor personnel with privileged access working in cybersecurity technical environments, cybersecurity management personnel with significant cybersecurity tasks, Computer Network Defense Service Providers (CND�SPs), and cybersecurity systems architects and engineers. Task orders with cybersecurity functions will include a requirement for the Contractor to report cybersecurity certification status and compliance.

6.6 REPORTS, DATA AND DELIVERABLES

The Contractor shall provide reports, technical data, and computer software deliverables in accordance with the Contract Data Requirements List (CDRL), DD Form 1423, as specified in individual task orders.

All classified deliverables shall be protected and handled in accordance with standard security practices and procedures.

5252.216-9217 DELIVERY/TASK ORDER PROCEDURES (SEP 2014)—ALTERNATE II

The order procedures below are provided for informational purposes only. The actual procedures (including response times) may vary according to individual order circumstances.

(a) Multiple Award Contract (MAC) Ordering Procedures. It is anticipated that each competitive order will be placed in accordance with the following procedures:

In accordance with FAR 16.505(b)(2)(i)(F), the Government may set aside the competition for orders for small business concerns should the Government determine that the “rule of two” applies (see FAR 19.502-2). If there is only one small business awarded a prime MAC contract (along with large business MAC awardees), then the contracting officer also reserves the right to noncompetitively award an order to that small business concern.

(1) Requirements Documentation. Upon identification of a requirement, the cognizant technical code will develop a draft Performance Work Statement (PWS)/Statement of Work (SOW) and other requirements documents (e.g., Contract Data Requirements List (CDRL)) consistent with the technical requirements of this contract and the specific effort. Both level-of-effort (term) and completion type orders may be issued under this contract. Each order will include the order type deemed appropriate by the Government.

(2) Draft RFP*. The contract specialist will issue a draft Request for Proposals (RFP) to all MAC contractors** which will include, at a minimum, the draft PWS/SOW, anticipated CDRL data items, and the anticipated selection procedures for the order. Contractors are strongly encouraged at this stage to ask questions pertaining to the draft RFP, such as regarding the Government’s evaluation strategy, and to provide comments that could potentially help the Government improve the procurement. The time allotted for the submission of questions and/or comments is typically 2 to 5 business days.

*The Government may choose to skip the “Draft RFP” step altogether. In those instances, however, the contractors will still be allowed a question and answer period which will be identified in the RFP.

**Since correspondence is conducted via email, all MAC awardees are strongly encouraged to provide more than one email address to the Government to ensure that multiple contractor POCs receive the Government’s emails. The Government reserves the right to not include large business prime contractors on correspondence relating to orders set aside for small business.

The Government desires more than one offeror to submit a proposal for each order. Contractors are strongly encouraged to provide a preliminary decision as to whether or not they intend to submit a proposal in response to the final RFP. Should a contractor decide not to submit a proposal for the order, the Government may request the contractor to provide documentation to the Government indicating the reason(s) why no proposal is being submitted.

Additionally, the contractor is strongly encouraged to indicate if additional time to respond to the final RFP would cause the contractor to submit a proposal, and if so, how much additional time would be required. This initial propose/no-propose decision is strongly encouraged and is due no later than the deadline for questions and/or comments in response to the draft RFP.

(3) Final RFP. After the submission time for questions/comments in response to the draft RFP has expired, the Government will issue a final RFP which will contain the finalized requirements documents and selection procedures for the order. All eligible MAC awardees, even those that conveyed intent to not propose, will receive the final RFP. If there were any questions submitted during the draft RFP phase, at the Government’s discretion, pertinent questions and answers (properly sanitized of proprietary information) will be distributed to all eligible MAC contractors along with the final RFP. The time allotted for the submission of proposals is typically 5 to 10 business days.

Contractors that provided an intent-to-propose at the draft RFP stage, and then subsequently decide NOT to submit a proposal, are strongly encouraged to provide the same level of detail as identified above regarding why they are choosing not to submit a proposal. Any subsequent propose/no-propose decision that conflicts with the initial propose/no-propose decision are strongly encouraged to be submitted to the Government as early as possible.

(4) Source Selection Procedures. For a given order, the selection procedures will be based on a best value process, whether allowing for a tradeoff process (see FAR 15.101-1) or a low price/cost, or lowest price technically acceptable process (see FAR 15.101-2); however, in accordance with FAR 16.505(b)(1)(ii), FAR 15.3 will not apply. Each RFP will provide instructions to the MAC contractors as to the specific procedures for responding to the RFP and describe what information shall be presented to the Government in order to be considered for award of the order. The Government reserves the right to clarify certain aspects of one or more of the proposals, without contacting all offerors, unless such communication is used to materially alter the technical or cost elements and/or otherwise revise the proposal.

(5) Evaluation and Award. The Government will evaluate proposals and make award based on the evaluation criteria set forth in the final RFP. Once an offeror’s proposal has been selected for award, a DD Form 1155 will be executed by the Contracting Officer and sent to the contractor via e-mail or facsimile as notice to begin work. The contractor is cautioned that no work is to be started prior to receipt of a properly signed and executed DD Form 1155, Order for Supplies/Services, or other authorization by the Contracting Officer.

Within a reasonable amount of time (usually within 1 business day) after order award, the name of the awardee and the total value of the order will be provided to all MAC contractors.

(b) Non-Competitive Ordering Procedures. It is anticipated that each order awarded to a single award contractor, or to a MAC contractor when a Contracting Officer-approved exception at FAR 16.505(b)(2)(i)(A) through (F) applies, or when making a Contracting Officer-approved award to a small business as outlined above, will be placed in accordance with the following procedures:

(1) Requirements Documentation. Upon identification of a requirement, the cognizant technical code will develop a draft PWS/SOW and other requirements documents (e.g., CDRL) consistent with the technical requirements of the effort. Both level of effort (term) and completion type orders may be issued under this contract.

The PWS/SOW will include the order type deemed appropriate by the Government.

After both parties have reached agreement regarding the technical requirements of the PWS/SOW, the contractor and the Contracting Officer’s Representative (COR) shall sign and date the final document to signify their common understanding of the order requirements.

(2) Cost Estimate*. Typically within 1 to 5 business days after signing the PWS/SOW, the contractor will submit to the contract specialist and the COR/COR Support Manager (CSM) a complete cost estimate. The cost estimate shall contain the following information to enable the Contracting Officer to make a determination of cost/price reasonableness:

(i) Individually listed labor categories, direct labor hours, and unburdened hourly labor rates for each labor category. Unless proposing a new labor category not listed in the basic contract, all proposed labor categories should either exactly match, or be mapped to the labor categories identified in the basic solicitation.

(ii) Other Direct Cost (ODC) cost information shall include identification of: 1) material

(consumable and non-consumables) purchase description and amount; 2) summary of travel costs to include identification of number of travelers, destination, and duration for each trip and 3) other direct costs not separately identified.

(iii) Actual indirect rates used and note their application.

(iv) Show totals for individual cost elements, as well as the overall total for hours, estimated cost, and cost plus fee. Identify the average hourly labor rate for the overall proposal (computed by dividing total fully burdened labor cost by total labor hours).

(v) If applicable, subcontractor costs, names of subcontractor(s) and type of subcontract(s).

(vi) For proposed personnel, identify the fully burdened hourly labor rate inclusive of all applicable indirect costs and fee.

*These cost estimate elements apply to both competitive and non-competitive orders.

(3) Cost Evaluation and Award. Once the Contracting Officer has reviewed and accepted the contractor’s cost estimate, a DD Form 1155 will be executed by the Contracting Officer and sent to the contractor via e-mail or facsimile as notice to begin work.