SETI_DRAFT_PWS_June_2016.pdf

Enclosure 2d, PWS Page 1 of 27 Pages

10Feb2016/Version 12

PERFORMANCE WORK STATEMENT (PWS)

as of March 9, 2016

Contract Number: To be filled in at award Task Order Number: NA Tracking Number: NA Follow-on to Previous Contract and Task Order Number:

New requirement

1. Contracting Officer’s Representative (COR).

a. Primary COR.

Name: To be filled in at award Organization: DISA Department of Defense Activity Address Code (DODAAC): HC1047

Address: 6910 Cooper Avenue, Ft. Meade, MD 20755 Phone Number:

Fax Number:

E-Mail Address:

b. Alternate COR.

Name: To be filled in at award Organization:

DODAAC:

Address:

Phone Number:

Fax 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 engineering services, expertise, and support in the planning, research, development, implementation, and de-ployment activities for future, proposed, current, and legacy Department of Defense (DoD) and Defense Information Systems Agency (DISA) information technology (IT) capabilities, services, and systems. It will deliver IT engineer-ing 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 vi-sion is to establish information dominance to 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 devel-oping and offering innovative systems and capabilities that collaboratively and securely facilitate information shar-ing and interdependent enterprise services to address joint and coalition warfighter needs. These systems and capa-bilities 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.

Page 2 of 27 Pages

10Feb2016/Version 12

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 implement-ing 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 effi-cient, 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 multiple award, Indefinite-Delivery/Indefinite-Quantity (ID/IQ) task order-type contracts for DoD, DISA and DISA mission partners. SETI provides an overarching streamlined process for order-ing a wide variety of critical end-to-end 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 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.

5A. 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 DoD and 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 entities. Where applicable, the term system can refer to a single system, collection of systems, sub-systems, and systems-of-systems (SoS), together within its environment.

SETI extends the services of this contract to support customers of DISA services in the innovation, adoption, in-teroperability, integration, enhancement, augmentation and delivery of DoD and DISA products, services, and capa-bilities. The services covered under this contract shall be global in reach and all SETI contract holders shall be pre-pared 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 capabilities, systems, solutions and insert and sustain emerging technol-ogies and approaches throughout its lifespan, and address the evolving needs of the mission landscape. The work under SETI will be authorized and more specifically defined in individual Task Orders (TO) and executed by the Contracting Officer (KO).

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. Surge support over the life of any task order issued against SETI will not exceed 100% of the contractor’s total proposed cost/price for the base and all option periods of that task order, excluding any six-month extension of services pursuant to FAR 52.217-8.

• Task Area 1 – Systems Engineering

• Task Area 2 – Design Analysis Engineering

• Task Area 3 – Systems Architecture

• Task Area 4 – Software Systems Design and Development

Page 3 of 27 Pages

10Feb2016/Version 12

• 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

5B. Overall Contract and Task Order Management. The Contractor shall identify a Program Manager and provide contract level program management to ensure successful completion of the overall contract effort. The Contractor shall oversee all contract level activities and provide the leadership and controls necessary to meet deliverable tar-gets, maintain staffing at levels required to satisfy customer requirements, interface directly with Government leads for all supported areas, and exercise control over all assigned task personnel. The Contractor’s program management staff and all program management functions shall be provided at no additional cost to the contract and task orders.

5B.1 Contract Status Report. The Contractor shall submit a quarterly Contract Status Report unless otherwise speci-fied by the Contracting Officer or Contracting Officer Representative. This report shall convey the status of all TOs awarded as of contract inception as well as cumulative contract performance. All relevant billing information shall be included in this report.

5B.2 Required Skills, Disciplines, and Technical Background. Contractor staff shall onboard with the requisite edu-cation, training, skills, and experience necessary to provide support at the TO level. The Contactor shall take active measures to always remain current in staff relevancy in order to provide the full range of technical and engineering expertise, support, and knowledge throughout the SETI contract duration.

5B.3 Personnel Manpower Report. The Contractor shall provide a Personnel Report, on an annual basis listing all personnel under each TO. As personnel changes occur, a revised report is required only for the individual TO affect-ed for Security Background Investigations.

5B.4 Task Order Management. The Contractor shall provide TO level management support to ensure successful completion of each TO. The Contractor shall oversee all task level activities and provide the leadership and controls necessary to meet deliverable targets, maintain staffing at levels required to satisfy customer requirements, interface directly with Government leads for all supported areas, and exercise control over all assigned task personnel.

5B.5 Concept of Operations. The Contractor shall provide a CONOPS document for Government review and ap-proval. The CONOPS lay out the plan for the services to achieve the solution; which addresses all TO functional and administrative activities, roles, and responsibilities. This plan includes deliverables that will result from this work.

5B.6 Task Order Status and Progress Report. The Contractor shall establish, implement, and maintain a TO man-agement system that provides timely, reliable, and verifiable information to the Government. The Contractor’s TO management system shall track the status of each TO from planning to completion, estimate time to complete activi-ties, provide associated milestones, reflect associated risk, record projected and actual resources (cost and person-nel), and summarize technical activities expended on each TO. This information shall be presented in Monthly Sta-tus Reports developed by the Contractor and accepted by the DISA TO level Contracting Officer (KO) or COR.

5B.7 Subcontracts Management Plan (SMP). The Contractor shall be responsible for the management and execution of their subcontractors to include monitoring and assessing subcontractor performance. The Contractor shall imple-ment a Subcontracts Management Plan to include a balanced scorecard approach that provides detailed guidance for subcontract management, including organization, roles, responsibilities, authorities, reporting and evaluation, meth-ods and processes for teammate performance management, and incentive criteria and measurement.

5B.8 Technical Kickoff Meeting. The Contractor shall hold a kickoff meeting at the TO level within 15 days after TO award or unless otherwise specified in the order. At a minimum, the Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule for each effort.

Dates, locations (can be virtual), and agenda shall be specified at least five (5) calendar days prior to the meeting.

The Contracting Officer, COR, and Government Program Manager, shall be invited at a minimum.

5B.9 Quarterly Program Reviews. Quarterly Program Review Meetings shall be conducted with the Government Program Management Representative, designated COR, or Contracting Officer for each Task Order, or unless oth-

Page 4 of 27 Pages

10Feb2016/Version 12 erwise specified in the TO. The review shall address overall program status and provide details regarding technical, programmatic, scheduling, service implementation, completion, operation, administration and management issues dates, locations, agenda, and attendance requirements shall be specified by the appropriate Government representa-tive, at least five (5) calendar days prior to the meeting.

5B.10 Post Award Task Order Meetings / Conferences. Technical meetings, post award orientation conferences, may be necessary to resolve problems and to facilitate understanding of the requirements of the contract and/or of each awarded TO. Records of these meetings/conferences shall be made by the Contractor and submitted to the Government within five business days after conclusion of the meetings/conferences. All costs associated with the attendance at these meetings/conferences shall be at no direct charge to the contract, unless otherwise directed by the Government.

5B.11 Periodic Government Inspections and Quality Control. As applicable to each SETI TO, the Government has the authority to perform inspections and reviews to assure compliance and adherence to DoD and Federal policy, standards, guidelines, and established Industry best practices throughout the TO performance period. The Contractor shall be responsible for taking corrective action based upon the impact and severity of identified risks and weak-nesses.

5B.12 Surge Support. During unanticipated events that results in an increased demand for support services, the Government reserves the right to exercise "surge" option CLINs in accordance with the task order PWS. The Con-tractor shall provide, within 48 hour of request by the government, subject matter experts across all functional task areas, and technical and engineering support for program/project/service acquisitions, for an amount of time to be determined by the government.

5B.13 Contract / Task Order Transitions. The Contractor shall identify those actions, plans, procedures, and time-lines necessary to ensure a smooth transition from the contract and/or the TO start date to full operational or end status by the Contractor. The Contractor shall also identify those actions, plans, procedures, and timelines necessary to ensure a smooth transition-out for the follow-on contractor. The Contractor shall provide a transition plan subject to Government approval. The Contractor shall provide transition information and briefings to the COR prior to ex-piration dates. TOs issued under the IDIQ contact may include transitions in/out requirements.

5B.14 Configuration Management of Engineering Artifacts and Documentation. The Contractor shall collect, cate-gorize and maintain all artifacts or work product created by the contractor or their sub-contractors in a manner con-sistent with DoD and DISA standards for knowledge management.

6. Performance Requirements.

6.1 Task Area 1 – Systems Engineering

The objective of the Systems Engineering (SE) task area is to establish the technical framework for delivering mate-riel capabilities to the warfighter. SE ensures the effective development and delivery of capability through the im-plementation of a balanced approach with respect to cost, schedule, performance, and risk using an integrated, disci-plined, and consistent process. The scope will include system of systems 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.

• Establish roles and responsibilities. Define roles and what each role is responsible for.

• 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

Page 5 of 27 Pages

10Feb2016/Version 12

• 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 alternative

• 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 includ-ing, 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 solu-tions 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 includ-ing, but not limited to:

• 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

Page 6 of 27 Pages

10Feb2016/Version 12

• 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 in-cluding, 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. The Contractor shall assess impact of the originally defined capabilities and interfaces, performance parameter thresholds and objectives, and the overall system when defining and modify-ing 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

• Interfaces are consistent with the program’s configuration management plan

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

• Asses compliance of interfaces among configuration items composing systems or System of Systems (SoS)

• Monitor the viability and integrity of interfaces within a system

• Establish an 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 includ-ing, 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. The Contractor shall manage and execute verification activities and meth-ods as defined in the functional and allocated baselines, and review the results of verification.

Page 7 of 27 Pages

10Feb2016/Version 12

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

• 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. 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 Area 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 inves-tigation.

6.2.1 Subtask 1 – Engineering Assessment. 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 in-teractions with other project or services. The assessment includes current and future needs of the user, customer, and sponsor as well as doctrine, organization, training, materiel, leadership and education, personnel and facilities (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 environ-ment 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 mis-sion/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 deter-mine 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 in-dustry, 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. The Contractor shall research and develop systems, system elements, meth-ods, and constructs to support investigations of systems engineering activities on a limited scale in a similar envi-

Page 8 of 27 Pages

10Feb2016/Version 12 ronment. Pilots/initiatives need evaluation criteria to incorporate future design considerations and determine success and that are made at the end of the pilot/initiative.

The Contractor shall support and/or participate in designing, developing, planning, implementing, running, analyz-ing, 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 academ-ic sources

6.2.3 Subtask 3 – Modeling and Simulation. The Contractor shall conduct Modeling and Simulation (M&S) activi-ties 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, 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 re-sults 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.

Page 9 of 27 Pages

10Feb2016/Version 12

6.3 Task Area 3 – Systems Architecture

The objective for the Systems Architecture task area is to develop integrated enterprise architecture from the enter-prise 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 au-dits/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 da-ta/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. The Contractor shall iteratively review and research published guidance and other sources of information on architectures.

6.3.3 Subtask 3 – Conduct Interviews. The Contractor shall iteratively conduct interviews with subject matter ex-perts, sponsors, and participating organizations prior to and during architecture development.

6.3.4 Subtask 4 – Identify Primitives. 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 en-vironment. 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 doc-ument the architectural results

• Support primitive registration, architecture model construction, architecture markup/coordination, and MBSE automation

• Mature the architecture views throughout the review and approval process

6.3.6 Subtask 6 – Resolve Discrepancies. The Contractor shall resolve/adjudicate all architecture discrepancies dur-ing architecture model development and review processes. The Contractor shall document the actions taken to re-solve and adjudicate the discrepancies and provide a report to the Government.

6.3.7 Subtask 7 – Develop Reference Models. 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. The Contractor shall conduct architecture reviews for externally developed architectures as required by the Government. The Contractor shall record all concerns identified during the architec-ture review.

Page 10 of 27 Pages

10Feb2016/Version 12

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 tech-niques

• 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. The Contractor shall have an understanding of the DoD and the or-ganization (structure, missions, strategies, governance) and the Common Approach to Federal Enterprise Architec-ture (FEA). The Contractor shall participate 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 enter-prise 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 includ-ing, but not limited to:

• 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. The Contractor shall document enterprise systems and ser-vices 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, mo-bility, 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. The Contractor shall provide training in general on MBSE processes to include re-quirements engineering, modeling and simulation using SysML/UPDM, 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 stu-dent.

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 Area 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 coali-tion partner organizations. Focus areas within the Systems Design and Development task area include software en-gineering and software development.

6.4.1 Subtask 1 – Software Engineering. The Contractor shall engineer software designed to meet system needs.

Page 11 of 27 Pages

10Feb2016/Version 12

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 Concept Graphic

• 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 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 Interface Control

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. 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, tele-conferencing, 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 product 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 in-stallation 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 verifica-tion requirements

• Exercise the interfaces and verify that all interfaces are implemented according to the documentation dur-ing 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 engi-neering, and test and evaluation activities

Page 12 of 27 Pages

10Feb2016/Version 12

• Plan, capture and analyze software assurance metrics

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

• Revise current software assurance processes and identify efficiencies

• Provide code review in accordance with applicable STIGs

• All staff shall complete requisite IA training and obtain / maintain professional security certifications

• Validate that the total software functions properly in a real-life or near real-life production environment

• Ensure that the software will fulfill its intended use when placed in its intended environment

• Conduct development testing of SW packages prior to delivery

• Identify software components that do not perform suitably in their intended operating environments based on the established test criteria, or identify problems with the methods, criteria, and/or environment

• Obtain user sign-off upon successful completion of the test and approval of software product baseline

6.5 Task Area 5 – Systems Integration

The objective of the Systems Integration task area is to bring together component subsystems and ensure that those subsystems function as a whole. System elements (including software items, hardware items, manual operations, and other systems, as necessary) are integrated to produce a complete system that will satisfy the system design in the Agency's needs and expectations expressed in the system requirements.

6.5.1 Subtask 1 – System Integration. In support of this area, the Contractor shall perform activities including, but not limited to:

• Develop and apply strategies to integrate the system according to the priorities of the system requirements

• Develop criteria to verify compliance with the system requirements allocated to the system elements

• Verify integration results using well-defined and appropriate criteria, and identify and correct deficiencies

• Develop and apply regression strategies for retesting the system when changes are made

• Verify and ensure consistency and traceability are established between the system design and the integrated system elements

• Demonstrate that the system built complies with the system design and develop and verify a complete set of usable deliverable system elements

• Develop and ensure that all software components shall be integrated, with hardware configuration items, manual operations, and other systems as necessary, into the system

• Develop, maintain and document a set of tests, test cases (inputs, outputs, test criteria), and test procedures for conducting system qualification testing

• Perform successful software integration processes that combines the software units and software compo-nents, producing integrated software items, consistent with the software design

• Develop integration strategies that are consistent with the software design and prioritized software require-ments

• Develop and use verification criteria for software items that ensure compliance with the software require-ments allocated to the items

• Define and align software items with integration strategy

• Develop and apply appropriate test and strategy for re-verifying software items when a change in software units (including associative requirements, design and code) occur

• Develop an integration plan to integrate the software units and software components into the software item

• Integrate all the software units and software components and test as the aggregates are developed in ac-cordance with the integration plan

• Update user documentation as necessary

• Develop and document for each qualification requirement of the software item a set of tests, test cases (in-puts, outputs, test criteria), and test procedures for conducting software qualification testing

• Evaluate the integration plan, design, code, test, test results, end-user documentation and document results

• Verify that the integration activity has not adversely affected the security controls of each individual com-ponent or the overall security posture of the integrated whole

6.5.2 Subtask 2 – System Integration Strategy. The Contractor shall support the development and implementation of the System Integration Strategy. The strategy will include the approach for integrating the graphical user interface, Page 13 of 27 Pages

10Feb2016/Version 12 the business layer, and the data layer and associated components correctly. The strategy shall address all integration tasks, regardless of whether an automated or manual method is recommended.

6.5.3 Subtask 3 – System Integration Planning. The Contractor shall describe in detail the plans and execute the strategy and any changes that need to be made to the strategy. At a minimum, the outcomes of this task shall in-clude:

• Method for determining the order of system integration

• System integration tasks to be performed in order to complete system integration

• Tasks listed in order of required occurrence, including work schedules, timeframes, and all dependencies

• Resource requirements needed to perform each identified task and subtask

• Successful consolidation of the various components, assemblies, and subsystems of a system and successful performance of what the system was intended to do

6.5.4 Subtask 4 – System Implementation Integration. In support of this area, the Contractor shall perform activities including, but not limited to:

• Establish environments to support efficient and effective design, development, testing, knowledge transfer, operation, and maintenance of the Eligibility Determination System (EDS) and integration

• Propose all hardware and software necessary to design, develop, test, operate, and maintain the EDS and integration activities after analysis of what is already available to the Agency

• Ensure that all software applications that support the operation of the EDS and integration activities also support interfaces with other systems, enable workflow, document imaging, management and e-forms

• Produce the hardware and software plan to support an efficient and effective design, development, testing, knowledge transfer, and production environment for the EDS

• Collaborate with the Government on the necessary hardware and software and disaster recovery provisions

• Collaborate with the Government to identify procurement and licensing for proposed software

• Conduct ongoing reviews of the hardware and software performance and reliability

• Ensure that hardware and software requirements identified in the plan meet or exceed performance stand-ards

• Ensure that all software applications that support the operation of the EDS and integration activities are supported in all environments (such as production, development, staging, and test environments)

6.5.5 Subtask 5 – Integration Test. In support of this area, the Contractor shall perform activities including, but not limited to:

• Perform and support testing to ensure the operations and hardware/software are functioning as designed

• Perform system testing to ensure that the implementation of each system requirement is tested for compli-ance and that the system is ready for delivery

• Support and document the results of audits

• Develop the Unit and Integration Test Plan

• Perform and support a software verification process

• Support software and code verification

• Support integration verification

• Document the outputs in accordance with the software documentation management process

• Select, tailor, and use those standards, methods, tools, and computer languages for performing the software implementation process

• Develop and execute plans for conducting activities of the software implementation process

6.5.6 Subtask 6 – Integration and Architectural Design. In support of this area, the Contractor shall perform activi-ties including, but not limited to:

• Support the system conceptual architectural design activity that identifies which system requirement is al-located to which system element(s)

• Support and perform architecture…