HC1047-17-R-0001.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 24 Mar 2017

X

A

X B

X C

D

EX

X

G

F 90 - 101

102 - 122 X H 123 - 131 carlen.l.capenos.civ@mail.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 131

(If other than Item 7)

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.

HC1047 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 2 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 conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

CARLEN L. CAPENOS 301-225-4508

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 10

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

11 - 38 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

40 - 42 X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 43 - 57 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 58 - 61 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

62 - 88

PART II - CONTRACT CLAUSES

DISA/CONTRACTS-NCR

6914 COOPER AVE

FORT MEADE MD 20755-7090

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

22 Feb 2017

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

HC1047-17-R-0001

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 Lot

SETI - FFP

FFP

Fixed Price (FP). All Variations. This CLIN applies to all variations of contract types under fixed price.

Period of Performance is five year base period (Contract Years 1 through 5).

FOB: Destination

NET AMT

0002 Lot SETI - Cost Reimbursable

COST

Cost Reimbursable (CR). All Variations. This CLIN applies to all variations of contract types of Cost Reimbursable.

ESTIMATED COST

0003 Lot SETI - Time and Materials

T&M Time and Materials (T&M). All variations. This CLIN applies to all variations of contract types of Time & Materials.

Period of Performance is five year base period (Contract Years 1 through 5)

TOT ESTIMATED PRICE

CEILING PRICE

0004 Lot Other Direct Costs (ODC)

COST

Other Direct Costs. Cost Reimbursable.

ODCs must be purchased in accordance with the Contractor's approved Purchasing System, as applicable. ODCs may be purchased from General Service Administration (GSA) Schedules or Enterprise Software Initiative (ESI), if available and authorized by the Contracting Officer. ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved in writing by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31.

Period of Performance is five year base period (Contract Years 1 through 5).

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.

0005 Lot Travel

COST

Travel in support of PWS. No profit shall be paid on purchases or on travel made under this CLIN. DCAA approved burden rates are authorized. Travel must be incidental to the work being performed under this contract. All travel must be pre-approved in writing by the COR prior to the Contractor incurring the cost.

Travel shall be in accordance with FAR Subpart 31.205-46.

External Agency Ordering Fee

FFP

1% Fee. See 52.216-9000.

0007 1 Each Minimum Guarantee

FFP

The minimum may be invoiced for and paid after the attendance of the Kick-Off meeting and the delivery and acceptance of the SCRM and the Cyber Security Threat Plan.

1001 Lot

OPTION SETI - FFP

FFP

Fixed Price (FP). All Variations. This CLIN applies to all variations of contract types under fixed price.

Period of Performance is five year option period (Contract Years 6 through 10).

1002 Lot OPTION SETI - Cost Reimbursable

COST

Cost Reimbursable (CR). All Variations. This CLIN applies to all variations of contract types of Cost Reimbursable.

1003 Lot OPTION SETI - Time and Materials

T&M Time and Materials (T&M). All variations. This CLIN applies to all variations of contract types of Time & Materials.

Period of Performance is five year option period (Contract Years 6 through 10)

1004 Lot OPTION Other Direct Costs (ODC)

COST

Other Direct Costs. Cost Reimbursable.

ODCs must be purchased in accordance with the Contractor's approved Purchasing System, as applicable. ODCs may be purchased from General Service Administration (GSA) Schedules or Enterprise Software Initiative (ESI), if available and authorized by the Contracting Officer. ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved in writing by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31.

Period of Performance is five year option period (Contract Years 6 through 10).

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.

1005 Lot OPTION Travel

COST

Travel in support of PWS. No profit shall be paid on purchases or on travel made under this CLIN. DCAA approved burden rates are authorized. Travel must be incidental to the work being performed under this contract. All travel must be pre-approved in writing by the COR prior to the Contractor incurring the cost.

Travel shall be in accordance with FAR Subpart 31.205-46.

OPTION External Agency Ordering Fee

FFP

1% Fee. See 52.216-9000.

9999 Lot Surge

COST

The Government may require surge support of task orders during the base or any option period and surge modifications will be in-scope to provide increased support for the defined task areas of the PWS. Surge support is OPTIONAL and is not a guarantee. If the Government determines that an increased quantity of support is required for the task areas defined in the PWS, the Government reserves the right to exercise the Surge Option unilaterally.

The Contracting Officer will provide written notice to the Contractor at least 30 calendar days prior to any unilateral exercise of the Surge Option. In the event the Government does elect to exercise the Surge Option, surge support will be realigned under new or existing CLINs for the relevant task areas identified in the PWS, and an equal amount will be deducted from the Surge CLIN not-to-exceed amount. Surge support will be provided at the same labor rates proposed and found fair and reasonable at time of contract/task order award for the applicable period of performance.

This Surge Option will not be used to increase the ceiling of the SETI base contracts, but the Surge Option may be included in task orders issued under the SETI base contracts at the discretion of the Ordering Contracting Officer.

Period of Performance is Contract Years 1 through 10.

SECTION B

B1. MAXIMUM CONTRACT CEILING AND MINIMUM CONTRACT GUARANTEE

(a) Maximum. The maximum Contract ceiling value of all Contracts in this multiple award procurement is established at $7.5 Billion dollars.

(b) Minimum. The minimum guaranteed award amount for this Indefinite-Delivery, Indefinite-Quantity (ID/IQ) Contract is $500 dollars per Contractor for the full term of the Contract. The exercise of the option period does not re-establish the Contract minimum.

(c) The Government has no obligation to issue Task Orders to the Contractor beyond the amount specified in paragraph (b). Once the conditions of paragraph (b) have been met, the Contractor continues to be afforded fair opportunity, as per FAR 16.505(b)(1), to compete for Task Orders issued through the expiration of the ID/IQ Contract or termination of the Contractor's ID/IQ Contract, whichever occurs first, unless an exception to fair opportunity applies or unless the Contractor is placed in dormant status as detailed below.

B2. SERVICE CONTRACT LABOR STANDARDS (SCLS) GENERAL EXEMPTION

The ID/IQ Contract labor categories are considered bona fide executive, administrative, professional labor and are exempt from the SCLS if used to perform the type of professional IT services within the scope of this Contract. The ID/IQ Contract does not include wage determinations or SCLS clauses.

B3. TASK ORDER CONTRACT TYPES

SETI is a Multiple Award Task Order Contract (MATOC). It is an ID/IQ Contract for Department of Defense Systems, Engineering, Technology and Innovation technology service-based requirements that allows the use of most Contract types in Task Orders. Task Order Contract types permitted include FAR 16.2 Fixed-price Contracts;

FAR 16.3 Cost-Reimbursement Contracts; FAR 16.4 Incentive Contracts; and FAR 16.601 Time-and-materials.

Task Orders may also incorporate FAR 17.1 Multi-year Contracting and FAR 17.2 Option periods procuring

Commercial-items or Non-commercial items. These Contract types can be used individually or in combination within a single Task Order comprising multiple Contract Line Item Numbers (CLINs).

B4. FIXED PRICE (FP) LABOR RATES

The Fixed Price Labor Rates proposed represent the Offeror’s fully-burdened fixed price hourly labor rates for each skill classification for work performed at Government sites and work performed at Contractor sites. These rates provided in the pricing template will be used as ceiling labor rates for pricing of all labor proposed under future fixed priced Task Orders issued under this ID/IQ Contract. At time of award, the Contractor’s FP labor rates will be incorporated into the Contract.

B5. TRAVEL PRICING (ALL ORDER TYPES)

Contractor personnel may be required to travel to support the requirements of this Contract as stated in individual Task Orders (TOs). Local travel and travel outside of the local area may be required both in the Contiguous United States (CONUS) and Outside the Contiguous United States (OCONUS). For those TOs requiring travel, the Contractor shall include estimated travel requirements in the proposal as required by the OCO. Travel shall not commence without written consent in accordance with instructions in the TO.

If authorized in the Task Order, travel will be reimbursed at actual cost in accordance with the limitations set forth in FAR Subpart 31.205-46, Travel Costs. Profit shall not be applied to travel costs. To the extent authorized by the Task Order, Contractors may apply indirect costs to travel in accordance with the Contractor’s usual accounting practices consistent with FAR 31.2. The OCO must identify a not-to-exceed travel ceiling under a separate CLIN on the Task Order.

B6. OTHER DIRECT COSTS (ODCs) (ALL ORDER TYPES) ODCs may consist of software, materials, and Task Order-related items that are incidental to the services being performed. The cost of general-purpose items required for the conduct of the Contractor’s normal business operations will not be considered an allowable ODC in the performance of this Contract. Profit is not allowed on ODCs for any Task Order; however, applicable burdens are allowed in accordance with Contractor’s accounting practices. If applicable, the OCO must identify a not-to-exceed ODC ceiling under a separate CLIN on the Task Order.

B7. WORK OUTSIDE THE CONTIGUOUS UNITED STATES (OCONUS)

Task Orders issued under this ID/IQ may require performance outside the Contiguous United States (CONUS).

CONUS means the 48 contiguous States and the District of Columbia. Any additional applicable clauses for OCONUS work may be added to the Task Orders.

OCONUS includes:

1. Outside the United States and its territories, and

2. NON-FOREIGN OCONUS AREA. The states of Alaska and Hawaii, the Commonwealths of Puerto Rico and the Northern Mariana Islands, Guam, and U.S. territories and possessions.

It is anticipated that there may be Task Orders under this Contract for work outside the United States. The Contractor will be compensated for work performed OCONUS pursuant to the Task Order, including any applicable Status of Forces Agreements (SOFA). Standard references for OCONUS pricing include:

The U.S. Department of State’s Bureau of Administration, Office of Allowances, (https://aoprals.state.gov/) publishes quarterly report indexes of living costs abroad, per-diem rate maximums, quarter’s allowances, hardship differentials, and danger pay allowances for Contractors to follow when proposing on OCONUS efforts. No allowances, other than those listed by the U. S. Department of State, shall be allowed on Task Orders.

The Department of State Standardized Regulations (DSSR) are the controlling regulations for allowances and benefits available to all U.S. Government civilians assigned to foreign areas; however, for Task Orders issued under the ID/IQ Contract, Contractor civilians assigned to foreign areas shall not exceed the allowances and benefits in the DSSR as well.

For OCONUS Task Orders where costs are not specifically addressed in the DSSR, the Government will reimburse the Contractor for all reasonable, allowable, and allocable costs in accordance with FAR 31, Contract Cost Principles and Procedures.

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

as of 16 February, 2017

Contract Number:

Task Order Number:

Tracking Number:

1. Contracting Officer’s Representative (COR).

a. Primary COR. (To be filled in at award)

Name:

Organization:

DODAAC:

Address:

Phone Number:

E-Mail Address:

b. Alternate COR. (To be filled in at award)

Name:

Organization:

DODAAC:

Address:

Phone Number:

E-Mail Address:

2. Contract Title. Systems Engineering, Technology & Innovation (SETI)

3. Background. The Systems Engineering, Technology and Innovation (SETI) Contract vehicle will provide a suite of information technology (IT) engineering services, expertise, and support in the planning, research, development, integration, and implementation activities for future, proposed, current, and legacy Department of Defense (DoD) and Defense Information Systems Agency (DISA) IT capabilities, services, and systems. It will deliver complex IT engineering support services throughout the entire acquisition lifecycles of DoD and DISA solutions, systems, and system components.

DISA serves as DoD’s combat support Agency responsible for delivering, operating, and assuring a critical array of technical capabilities and enterprise systems and services to the Warfighter, among which include command and control (C2), information sharing, and global net-centric enterprise information infrastructure. DISA’s primary vision is to establish information dominance for our DoD and mission partners in order to secure and defend the nation.

DISA’s first strategic objective is to successfully evolve the Joint Information Environment (JIE). It involves developing and offering innovative systems and capabilities that collaboratively and securely facilitate information sharing and interdependent enterprise services to address joint and coalition Warfighter needs. These systems and capabilities need to be efficient, responsive, interoperable, and must seamlessly interface with services and capabilities across the Department. The result is for DISA to provide valuable, dependable, robust capabilities and services for authorized users to connect with any device, anytime, from anywhere on the globe.

The second strategic objective is for DISA to effectively deliver Joint Command and Control (JC2) and leadership support; involving copiously developing a gamut of JC2 capabilities that are essential for planning and implementing joint, interagency, and multinational operations such as the Future Mission Network (FMN). DISA delivers C2 and information sharing capabilities and leverages them as a force-multiplier to our nation’s leaders both within and outside the Department.

DISA’s third strategic objective is to operate and assure the enterprise. This involves delivering and operating efficient, responsive, innovative, and resilient cyber and network systems, capabilities, and processes that are capable of handling dynamic situations in response to shifts in DoD’s defense posture and augmenting Warfighters’ needs.

DISA’s final strategic objective involves optimizing its investments within a resource-constrained environment. This involves taking full advantage of resources to deliver cost-effective services and capabilities without compromising quality, and promoting established processes and policies that facilitate the agile adoption and integration of future technology. DISA is also synchronizing its efforts to support the dynamic nature of DoD’s defense posture to achieve information dominance within an evolving environment.

4. Objectives. The objective of the SETI Contract vehicle is to provide quality engineering and technical support, services, and products globally under a multiple award, Indefinite-Delivery/Indefinite-Quantity (ID/IQ) Task Order Contract for DoD, DISA, and DISA mission partners. SETI provides an overarching streamlined process for ordering a wide variety of critical IT engineering performance-based services while ensuring consistency and maximum opportunity for competition. It is a crucial vehicle for enabling the Agency to address the growing and dynamic engineering and technical needs of today’s and tomorrow’s Warfighter in a more streamlined and cost-effective approach. SETI promotes the delivery of innovative systems and capabilities using mature and emerging technologies and standards in order to achieve and improve towards a collaborative, adaptive, secure, expeditious, and interoperable enterprise information environment.

5. Scope. SETI offers an array of research and development, and critical technical disciplines core to engineering, delivering, and maintaining DoD and DISA IT products and capabilities. It encompasses legacy, current, and future DoD and DISA capabilities, services, systems, and systems-of-systems (SoS) throughout the acquisition and system engineering lifecycle. SETI spans the entire spectrum of DISA mission areas supported by the various Combatant Commands, Services, Agencies (CC/S/As) and DISA Directorates and Offices. SETI is available for use by all DoD mission partners. Where applicable, the term ‘system’ can refer to a single system, collection of systems, sub-systems, and SoS, together within its environment.

SETI extends the services of this Contract to support customers of DISA services in the Innovation, adoption, interoperability, integration, enhancement, augmentation and delivery of DoD and DISA products, services, and capabilities. The services covered under this Contract shall be global in reach and all SETI Contract holders shall be prepared to provide services and deliverables worldwide.

With the pace of change, fully anticipating how technical requirements and individual programs will evolve over the life of the Contract vehicle is impossible. SETI intends to remain current and continue to provide the full range of engineering support and services to deliver innovative capabilities, systems, solutions; to insert and sustain emerging technologies and approaches throughout its lifespan; and to address the evolving needs of the DISA mission space.

The work under SETI will be authorized and more specifically defined in individual Task Orders (TO) and executed by the Ordering Contracting Officer (OCO).

The Government may require surge support during the base or any option period of any Task Order issued against SETI, and surge modifications will be within the scope of the Contract and provide increased support for the defined task areas of the Task Order PWS.

• Task Area 1 – System Engineering

• Task Area 2 – Design Analysis Engineering

• Task Area 3 – Systems Architecture

• Task Area 4 – Software Systems Design and Development

• Task Area 5 – Systems Integration

• Task Area 6 – Systems Test and Evaluation

• Task Area 7 – Systems Deployment and Life-cycle Engineering

• Task Area 8 – Special Systems Engineering Requirements

6. Performance Requirements.

6.1 Task 1 – Systems Engineering.

The objective of the Systems Engineering (SE) task area is to establish the technical framework for delivering materiel capabilities to the Warfighter. SE ensures the effective development and delivery of capability through the implementation of a balanced approach with respect to cost, schedule, performance, and risk using an integrated, disciplined, and consistent process. The scope will include SoS to the fullest extent possible and wherever applicable.

6.1.1 Subtask 1 – Technical Planning. In support of this area, the Contractor shall perform activities including, but not limited to:

• Develop, maintain and execute the program’s Systems Engineering Plan (SEP)

• Provide key technical inputs and ensure SEP alignment to other program plans

• Define the scope and objectives of the technical effort

• Identify constraints and risks.

• Divide the program scope and objective into discrete elements

• Identify technical reviews and audits as well as their timing

• Establish and maintain schedules and costs

• Prepare and update planning documentation

• Scale SE processes based on the scope and complexity of the program/system

• Identify areas for potential tailoring of artifacts and reviews

6.1.2 Subtask 2 – Decision Analysis. In support of this area, the Contractor shall perform activities including, but not limited to:

• Review requirements and assumptions to establish the overall decision context

• Frame/structure the decision in terms of supporting program/project objectives

• Identify methods and tools to be used in the analyses

• Develop decision criteria (objectives and measures), criteria weight, and associated rationale

• Identify and track assumptions

• Develop prototypes and proofs of concept to demonstrate the feasibility of various alternatives

• Identify and define alternatives to be evaluated

• Analyze and assess alternatives against the service or program criteria

• Synthesize results determining the suitability of solutions/courses of action

• Analyze sensitivities, outside influences to the program or service

• Develop decision briefing with action/implementation plan(s)

• Make appropriate recommendation(s) to decision maker as expected/requested

6.1.3 Subtask 3 – Technical Assessment. In support of this area, the Contractor shall perform activities including, but not limited to:

• Establish event-driven technical plans

• Identify appropriate measures and metrics, including how, when and where the data will be gathered

• Identify performance measures to assess program health, technical progress and end-to-end performance

• Conduct analyses to determine risk and to develop risk mitigation strategies

• Conduct assessments of technical maturity, process health and stability, and risk

• Propose changes in the technical approach to address risk mitigation activities

• Advise the Government Program Manager regarding the technical readiness of the program

• Provide independent subject matter experts (SMEs) for reviews and audits

6.1.4 Subtask 4 – Requirements Management. In support of this area, the Contractor shall perform activities including, but not limited to:

• Establish and maintain a Requirements Traceability Matrix (RTM)

• Prepare Business Case Analyses (BCAs) that support IT investment decisions

• Prepare and/or support the development of Initial Capabilities Documents (ICDs) and non-material solutions in Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy (DOTMLPF-P) Change Recommendations (DCR)

• Prepare and/or support the development of an Analysis of Alternatives (AoAs)

• Support Initial Technical Reviews (ITRs) and Alternative System Reviews (ASRs)

• Prepare and/or support the development of Capabilities Development Documents (CDDs) and Capability Production Documents (CPDs)

6.1.5 Subtask 5 – Risk Management Process. In support of this area, the Contractor shall perform activities

• Risk Identification

• Risk Analysis

• Risk Mitigation Planning

• Implement Risk Mitigation Plan

• Risk Tracking

6.1.6 Subtask 6 – Configuration Management (CM). In support of this area, the Contractor shall perform activities including, but not limited to:

• Configuration Management Planning and Management

• Configuration Identification

• Configuration Change Management

• Configuration Status Accounting

• Configuration Verification and Audit

6.1.7 Subtask 7 – Technical Data Management. In support of this area, the Contractor shall perform activities including, but not limited to:

• Identify data requirements

• Acquire data

• Receive, verify, and accept data

• Use and exchange data

6.1.8 Subtask 8 – Interface Management. In support of this area, the Contractor shall assess the impact of the originally defined capabilities and interfaces, performance parameter thresholds and objectives, and the overall system when defining and modifying interfaces. The Contractor shall develop the program’s interface management plan that:

• Documents the system's internal and external interfaces and their requirement specifications

• Identifies preferred and discretionary interface standards and their profiles

• Provides justification for selection and procedure for upgrading interface standards

• Describes the certifications and tests applicable to each interface or standard

• Ensures interfaces are consistent with the program’s configuration management plan

In support of this area, the Contractor shall be responsible for interface management including, but not limited to, the following key tasks throughout the life cycle:

• Define and establish interface specifications

• Assess compliance of interfaces among configuration items composing systems or systems-of-systems

• Monitor the viability and integrity of interfaces within a system

• Managing the interface management plan

6.1.9 Subtask 9 – Requirements Analysis. In support of this area, the Contractor shall perform activities including, but not limited to:

• Define a capability that links the needs of the users to the system to be designed and developed

• Define a system that meets users’ mission requirements within specified cost and schedule constraints

• Provide insight into the interactions among various functions to achieve a set of balanced requirements based on user objectives

• Analyze user requirements and translate user needs into basic functions

• Develop a quantifiable set of performance requirements

• Define each function that the system is required to perform

• Define implementation constraints (stakeholder requirements or solution limitations)

• Translate performance requirements into specific system technical design requirements and functions

6.1.10 Subtask 10 – Implementation Support. In support of this area, the Contractor shall perform activities including, but not limited to:

• Identify and analyze constraints imposed on the design solution

• Develop, design and implement prototypes and solutions

• Analyze candidate system element design and implementation solutions

• Identify fabrication and quality procedures

• Obtain or acquire access to materials and tools required to build system elements

• Obtain external system elements as applicable

• Build system elements

• Determine system elements’ functionality against specified product quality characteristics

• Document fabrication and production issues and associated corrective actions

• Deliver implemented system elements for integration and subsequent verification

6.1.11 Subtask 11 – Verification Process. In support of this area, the Contractor shall manage and execute verification activities and methods as defined in the functional and allocated baselines, and review the results of verification.

In support of this area, the Contractor shall perform activities including, but not limited to:

• Demonstration

• Examination

• Analysis

• Test

6.1.12 Subtask 12 – Validation Process. In support of this area, the Contractor shall perform activities including, but not limited to:

• Support the validation process throughout the lifecycle

• Develop and perform early program-validation activities

• Validate the initial product baseline

• Conduct validation operational testing on a production-representative system in an operationally realistic environment

6.1.13 Subtask 13 – Transition Process. In support of this area, the Contractor shall oversee all transition plans and activities required to install or deploy the end-item system and enable system elements to perform in their operational environment. The Contractor shall conduct and lead all engineering efforts to correct deficiencies found during transition. Transition activities vary based on life-cycle phase, program scale, and system complexity. The end-item system may need to be integrated with other systems in the operational environment based on the defined external interfaces. In this case, the Transition process is performed in conjunction with the Integration and Interface Management processes for a smooth transition.

6.2 Task 2 – Design Analysis Engineering.

The objective of the Design Analysis Engineering task area is to analyze and refine requirements using various methodologies throughout the life-cycle of the system. Focus areas within the Design Analysis Engineering task area include engineering assessment, pilots and initiatives, modeling and simulation, and systems analysis and investigation.

6.2.1 Subtask 1 – Engineering Assessment. In support of this area, the Contractor shall assess the systems engineering activity or problem in the context and operational environment in which the solution will be embedded.

This comprehensive viewpoint enables the ability to develop and apply solutions that consider all aspects of a problem, their relationships, and interactions with other projects or services. The assessment includes current and future needs of the user, customer, and sponsor as well as DOTMLPF and technical issues. This task area requires a very high-level of skill and breadth and depth of senior expertise to assess the technical domain and solution space, designs, and architecture.

In support of this area, the Contractor shall perform activities including, but not limited to:

• Identify the nature and sources of uncertainty, lack of effective control, and complexity in their environment and then select and apply appropriate strategies for managing or mitigating their impacts

• Analyze and understand a customer’s enterprise or cross-agency environment in the context of customer and stakeholder needs and challenges, formulate and adjust plans and steps needed in effectively providing unique and effective perspectives, enhance enterprise integration, identify challenges, recognize mission/operational gaps, mitigate risks, and ensure delivery

• Recommend the use of mature and advanced technologies and methodologies to assess the soundness of technical requirements and/or solutions; review compatibility among new and legacy systems; and determine extensibility and scalability for future changes in scope and requirements

• Provide recommendations in the areas of technical planning and evolution management or modernization of Government enterprises

• Provide knowledge on emerging technologies, along with concept and approaches from academia and industry, to ensure that all aspects of the problem are considered

• Provide recommendations regarding the transformation and adoption of services and products

6.2.2 Subtask 2 – Pilots and Initiatives. In support of this area, the Contractor shall research and develop systems, system elements, methods, and constructs to support investigations of systems engineering activities on a limited scale in a similar environment. Pilots/initiatives shall include evaluation criteria to incorporate future design considerations and determine success and that are made at the end of the pilot/initiative.

In support of this area, the Contractor shall support and/or participate in designing, developing, planning, implementing, running, analyzing, assessing, and terminating pilots/initiatives with their Government partners and other staff as assigned on a wide range of systems during the performance of this Contract.

In support of this area, the Contractor shall perform activities including, but not limited to:

• Plan and prepare pilots/initiatives

• Conduct pilots/initiatives

• Test and evaluate pilots/initiatives

• Analyze results and provide recommendations

• Research, use and leverage best technology already available within Government, commercial and academic sources

6.2.3 Subtask 3 – Modeling and Simulation. In support of this area, the Contractor shall conduct Modeling and Simulation (M&S) activities to support decision-making processes used in delivering materiel capabilities to the Warfighter.

In support of this area, the Contractor shall perform activities including, but not limited to:

• Develop, maintain and execute M&S strategies

• Define the scope and objectives of the technical effort

• Identify constraints and risks

• Establish schedules and costs

• Scale systems engineering processes to the scope and complexity of the system

• Identify methods and tools to be used in the analyses, to include recurring technology assessment

• Develop, deliver, validate and verify, and maintain and execute various classes of models

• Develop, deploy, host, maintain, deliver and train users for complex models used as decision support tools

• Develop decision criteria (objectives and measures), criteria weight, and associated rationale

• Identify and develop metrics to quantify measures of effectiveness for given M&S studies

• Develop and present information and decision briefings with action/implementation plans based on the results of M&S studies

6.2.4 Subtask 4 – System Analysis and Investigation. The Contractor shall analyze and investigate existing systems potentially available to meet requirements.

In support of this area, the Contractor shall perform activities including, but not limited to:

• Analyze proposed and existing systems and services to identify problems and concerns

• Predict the impacts of proposed changes

• Identify and document dependencies, functionality, interoperability and performance of systems

• Investigate problems or potential problems, and recommend possible solutions

• Employ specialized tools to analyze system performance data for specific system domains

• Develop, provide, support and maintain testing artifacts

• Develop custom tools, analytics, or configurations for performance monitoring and analysis tools

• Coordinate root cause assessments and develop proposals to solve problems

• Develop plans and proposals for selecting, acquiring or building, and deploying system instrumentation tools

• Perform system instrumentation activities

• Review, document and assess the effectiveness of the security model of a system under investigation

• Assess system compliance with relevant system security policies, procedures, guidance, and best practices

• Propose system mitigations, fixes, and enhancements to address security concerns

Unless explicitly stated in the Task Order award, the Government will retain unlimited usage rights to analysis tools, algorithms, and all other intellectual property developed as part of work on this and all other PWS task areas.

6.3 Task 3 – Systems Architecture.

The objective for the Systems Architecture task area is to develop integrated enterprise architecture from the enterprise level down through the solution level and across solution level architectures. The scope of the task includes, but is not limited to, the development of the architecture, ensuring conformance to standards, and performing audits/assessments of the architectures and associated systems. The Contractor shall use the Department of Defense Architecture Framework (DoDAF), and/or other framework(s), as specified by the Government.

6.3.1 Subtask 1 – Develop Architectures. In support of this area, the Contractor shall perform activities including, but not limited to:

• Develop reference, enterprise and solution level architectures

• Adhere to Government-specified style guides and approved taxonomies

• Develop and document the design of critical links in the DoDAF architecture model formats, to include the linkage between models and related architectures. The Contractor shall reuse existing architecture data/views to minimize development cost and schedule, and maintain configuration control of architectural artifacts and the underlying models.

6.3.2 Subtask 2 – Research Documentation. In support of this area, the Contractor shall iteratively review and research published guidance and other sources of information on architectures.

6.3.3 Subtask 3 – Conduct Interviews. In support of this area, the Contractor shall iteratively conduct interviews with subject matter experts, sponsors, and participating organizations prior to and during architecture development.

6.3.4 Subtask 4 – Identify Primitives. In support of this area, the Contractor shall review primitives (e.g., performers, systems, system functions, activities, information exchanges) identified while researching documentation and conducting interviews to determine whether or not these primitives exist within the Government designated enterprise architecture tool environment. If the primitives do not exist, the Contractor shall propose the primitives to the Government for approval.

6.3.5 Subtask 5 – Scope and Assemble Primitives into Architecture Views. In support of this area, the Contractor shall perform activities including, but not limited to:

• Collect, organize, correlate, and store the architecture data required for architecture development and document the architectural results

• Support primitive registration, architecture model construction, architecture markup/coordination, and Model-Based Systems Engineering (MBSE) automation

• Mature the architecture views throughout the review and approval process

6.3.6 Subtask 6 – Resolve Discrepancies. In support of this area, the Contractor shall resolve/adjudicate all architecture discrepancies during architecture model development and review processes. The Contractor shall document the actions taken to resolve and adjudicate the discrepancies and provide a report to the Government.

6.3.7 Subtask 7 – Develop Reference Models. In support of this area, the Contractor shall review existing reference models and suggest modifications to the Government. Upon approval of suggested changes by the Government, the Contractor shall implement changes.

6.3.8 Subtask 8 – Maintain Architectures. In support of this area, the Contractor shall perform activities including, but not limited to:

• Maintain and update architecture baselines for enterprise-level and solution architectures

• Establish and/or maintain configuration control of all architecture artifacts

• Create an Architecture Standardization SOP for creating/maintaining enterprise and solution architectures

• Load all architecture baselines, artifacts, data, and documentation into the architecture repository

• Update enterprise architecture entries in the applicable architecture repositories

6.3.9 Subtask 9 – Review Architectures. In support of this area, the Contractor shall conduct architecture reviews for externally developed architectures as required by the Government. The Contractor shall record all concerns identified during the architecture review.

6.3.10 Subtask 10 – Analyze Architectures. In support of this area, the Contractor shall perform activities including, but not limited to:

• Perform analysis of architecture projects by using graphical, statistical, document, and model-based techniques

• Support a team approach that uses the enterprise architecture to evaluate functional, performance, technical, and operational requirements for gaps and redundancies

• Develop and support development of use cases

6.3.11 Subtask 11 – Architecture Governance. In support of this area, the Contractor shall have an understanding of the DoD and the organization (structure, missions, strategies, governance) and the Common Approach to Federal Enterprise Architecture (FEA). The Contractor shall participate as a member in the Government's enterprise configuration control and governance processes to develop and maintain the Enterprise Architecture.

6.3.12 Subtask 12 – Enterprise Engineering Support. In support of this area, the Contractor shall perform activities including, but not limited to:

• Provide specialized technical analysis, and engineering and implementation support for enterprise and sub-enterprise engineering efforts

• Provide technical expertise in transitioning key technologies and initiatives from solution architectures to implementation and develop implementation/transition plans

• Utilize DoD strategies and guidance to translate capability objectives and design solutions into an enterprise design

• Use established architectures and systems engineering processes

• Provide engineering and technical expertise and support for the needs of business processes

• Deliver detailed design specifications, technical papers, reports, analyses, recommendations, and other documentation required to describe and implement enterprise services

6.3.13 Subtask 13 – Business Process Support. In support of this area, the Contractor shall perform activities

• Review architectures from a process or operations perspective

• Assess IT operations challenges, recommend new business rules, and enable resource allocation decisions

• Apply knowledge of applicable standards and best practices

• Provide operational architecture artifacts to support requirements proposals

6.3.14 Subtask 14 – Capabilities and Services Mapping. In support of this area, the Contractor shall document enterprise systems and services from a capabilities engineering perspective. The Contractor shall document and model the capabilities and services delivered by C2, networking, security, cloud computing, data center/virtualization, network operations, mobility, unified communications, and other domain systems utilizing MBSE and other architectural modeling and documentation techniques approved by the Government.

6.3.15 Subtask 15 – Training. In support of this area, the Contractor shall provide training in general on MBSE processes to include requirements engineering, modeling and simulation using tools such as; SysML/UPDM (Systems Modeling Language for Unified Profile for United States Department of Defense Architecture Framework and United Kingdom Ministry of Defence Architecture Framework), designing and architecture development, and ITSM Service Design, in order to develop/build models representing organizational and DoD IT capabilities. The courses shall be complete with training materials, a presentation package, and one or more textbooks per student.

6.3.16 Subtask 16 – Technical Writing and Document Support. The Contractor shall provide technical writing and document support to include all the tasks identified under Architecture and Design.

6.4 Task 4 – Software Systems Design and Development.

The objective of the Software Systems Design and Development task area is to design, develop, sustain, synchronize and modernize systems to meet the needs of the nation’s Warfighters, national level leaders, and mission and coalition partner organizations. Focus areas within the Systems Design and Development task area include software engineering and software development.

6.4.1 Subtask 1 – Software Engineering. In support of this area, the Contractor shall engineer software designed to meet system needs.

In support of this area, the Contractor shall perform activities including, but not limited to:

• Conduct initial planning activities

• Prepare a Concept of Operations (CONOPS)

• Develop a DoDAF OV-1 High Level Operational Model

• Develop a Software Quality Assurance (SQA) Plan

• Prepare a Software Supportability Plan (SSP)

• Conduct software requirements analysis

• Define performance measures/metrics and method of calculation

• Decompose software configuration items (CIs) into functional capabilities or objects

• Conduct Software Requirements Review (SWRR)

• Conduct preliminary software design activities, including design methodology, and report on preliminary results

• Evaluate software and interface requirements, environment constraints, and design constraints

• Integrate capabilities with available mandatory, shared and functional enterprise services, as appropriate

• Develop, maintain, and use an Open System Management Plan to support an open systems approach

• Develop enhancements to the core framework in accordance with advisory board guidance, modernization, sustainment and synchronization goals

• Develop Software Design Description (SDD), Interface Design Description (IDD) and Initial Capabilities Document (ICD)

• Conduct a Preliminary Design Review (PDR)

• Document required design changes on change control documents before updating design documents

• Submit any necessary change requests, and implement the appropriate changes upon Government approval

• Conduct a Critical Design Review (CDR)

6.4.2 Subtask 2 – Software Development. In support of this area, the Contractor shall develop and deliver software to meet user needs in various environments, from collaborative software in the office space (e.g., enterprise email, instant messaging, teleconferencing, and workflow management) to software deployment at the tactical edge of the digital battlefield.

In support of this area, the Contractor shall perform activities including, but not limited to:

• Translate the Government-approved detailed design of a unit into executable code and develop software components that meet the design specifications and requirements with minimal defects

• Iteratively integrate software builds until final software solution is achieved

• Independently review and walkthrough source codes for quality assurance

• Compile the code, perform source code review, and correct the compiled code for any deviations

• Perform code complexity analysis using a code complexity measurement tool

• Develop supporting products such as training materials, user and maintenance manuals, online help, and installation and conversion software

• Conduct initial software test planning activities at project start-up

• Conduct more detailed test planning activities during the software requirements specification process

• Determine the appropriate types and levels of tests, overall testing strategy and required testing tools

• Review software requirements to ensure that they are well-formed, verifiable and testable

• Identify all interfaces to other units and determine if other units are available when needed or if unit stubs must be written

• Incrementally assemble the discrete software or support software elements into a top-level system-of-interest that is consistent with the software architectural design and that will meet defined software verification requirements

• Exercise the interfaces and verify that all interfaces are implemented according to the documentation during integration tests

• Propose changes to the baseline high-level design in accordance with the change management process

• Perform integration testing using the test cases defined in the test procedures

• Demonstrate end-to-end operational capabilities when the complete software is available

• Conduct the Test Readiness Review (TRR) for acceptance testing

• Provide management, oversight, and execution of the Information Assurance (IA) program, security engineering, and test and evaluation activities

• Plan, capture, and analyze software assurance metrics

• Develop and implement a “dashboard” that will provide live metrics from code review of all…