Attachment_1_PWS_01JUL2015.doc

Performance Work Statement (PWS)

Technology Services Organization (TSO) Information Technology (IT) Services Contract

Vision Statement 1 Introduction

1.1 Background

1.1.1 Technology Services Organization (TSO)

1.2 Scope

1.2.1 Technology Services Organization (TSO)

2 General Information

2.1 Non-Personal Services

2.2 Privacy Act and HIPPA

2.3 Travel/Temporary Duty (TDY)

3 Performance Requirements

3.1 Contractor Performance

3.1.1 Performance Standards and Acceptable Quality Levels

3.1.2 Specific Tasks and Workload Distribution

3.1.3 Labor Reporting

3.1.4 On-Call and Surge Support

3.1.5 Place of Performance and Hours

3.2 General Requirements

3.2.1 Program Management

3.2.2 Post-Award Conference

3.2.3 Program Management Plan

3.2.4 Transition

3.2.5 Management Reviews

3.2.6 Contractor Cost and Performance Reporting

3.2.7 Required Training and Certification

3.2.8 General Requirements Performance Standards and Acceptable Quality Levels

3.2.9 General Requirements Constraints

3.3 High Level Objective (HLO) 1 - Systems Engineering and Integration

3.3.1 HLO1 Objective Tasks

3.3.2 HLO1 Performance Standards and Acceptable Quality Levels

3.3.3 HLO1 Objective Constraints

3.4 HLO2 - Mission Support

3.4.1 HLO2 Objective Tasks

3.4.2 HLO2 Performance Standards and Acceptable Quality Levels

3.4.3 HLO2 Objective Constraints

3.5 HLO3 Systems Operations and Support

3.5.1 HLO3 Objective Tasks

3.5.2 HLO3 Performance Standards and Acceptable Quality Levels

3.5.3 HLO3 Objective Constraints

3.6 HLO4 Cybersecurity

3.6.1 HLO4 Objective Tasks

3.6.2 HLO4 Performance Standards and Acceptable Quality Levels

3.6.3 HLO4 Objective Constraints

3.7 HLO5 Help Desk

3.7.1 HLO5 Objective Tasks

3.7.2 HLO5 Performance Standards and Acceptable Quality Levels

3.7.3 HLO5 Objective Constraints

3.8 Additional/Increased Workload

3.8.1 Navy Pay Modification(PayMod) and Clean Audit Support

3.8.2 TSO GOGOCS IPT Services

4 Security and Safety Requirements

4.1 Personnel Security

4.1.1 Eligibility

4.1.2 Command Access Card (CAC) Eligibility

4.1.3 Security Clearances

4.1.4 Access to, Accountability for, and Safeguarding of Classified Material

4.1.5 IT Levels

4.1.6 Facility Notification

4.1.7 Facility Security Clearance

4.2 Applicable Directives

5 Government-furnished Equipment and Information

Vision Statement Maintain position as THE Marine Corps business system integrator by enhancing customer service and delivering consistent performance (business value) while sustaining a culture focused on people, processes, and technology.

1 Introduction

The TSO provides information technology support for software development, systems engineering, maintenance, and operations of Financial Management (FM) and Human Resource Management (HRM) Business Mission Area (BMA) systems including integrated Pay & Personnel, Financial Management (FM) and Accounting systems in support of the United States Marine Corps (USMC), Department of the Navy (DON) and Department of Defense (DoD). TSO support activities include functional support for systems, studies, assessments, consulting, and program and project management as well as the integration and maintenance of the networks on which supported systems will be operated.

This Performance Work Statement (PWS) includes: 1) PWS Appendix A – Systems & Environment Descriptions, 2) PWS Appendix B – Glossary of Terms, and 3) PWS Appendix C – Constraints.

1.1 Background

1.1.1 Technology Services Organization (TSO)

Mission: The TSO provides development, design, production and maintenance support of information technology systems, particularly pay, personnel and accounting systems, for the Marine Corps as well as DoD components, services and agencies.

The TSO provides software development, systems engineering, and technology support to the United States Marine Corps (USMC) and other select DoD customers including Navy Reserve, Air Force Reserve, Air National Guard and Defense Finance and Accounting Service (DFAS). The TSO operates as a Government-owned, Government-operated, Contractor-supported (GOGOCS) Integrated Product Team (IPT). The TSO GOGOCS IPT is comprised of Government civilians, Contractor employees and active duty Marines. The TSO supports a number of business mission area sponsors within the Marine Corps including the Deputy Commandant, Programs and Resources (P&R) and Deputy Commandant, Manpower and Reserve Affairs (M&RA). The TSO provides systems support for the DFAS, the U.S. Navy, and the U.S. Air Force. Additionally, the TSO provides administrative and IT support to other Marine Corps organizations, further referred to as supported organizations, principally located in Indianapolis, Indiana and Kansas City, Missouri, including Marine Corps Pay Requirements Directorate (MCPRD), Marine Corps Disbursing Operations and Systems Section (MCDOSS), and Marine Corps Pay Reconciliation Team.

The Government expects active participation from all members of the TSO GOGOCS IPT, including prime and sub-contractor personnel. Primary services the TSO GOGOCS IPT performs includes the review, analysis, documentation, design, programming, testing and implementation of change requests. Change requests are principally levied on the TSO through agreements reached with TSO customers, described above, during a Configuration Control Board (CCB) or in conjunction with standalone change requests or system discrepancies. Change requests may result from new or modified functional requirements, initiatives associated with improving system performance, changes due to legislation, mandated regulatory changes, and discrepancy resolution necessary to ensure proper system performance.

Marine Corps BMA Functional Area Managers (FAM), Program Managers, System Owners and Functional Managers continuously generate change requests for the TSO throughout the period of performance. These change requests are intended to provide better service to commanders, management headquarters, small unit leaders, and individual Marines through automation of new entitlements or through business process reengineering (BPR) improvements.

All change requests represent increases or decreases to the TSO workload throughout the period of performance. Assuming a full workload at the start of the period, workload increases stem from a number of sources while the major area of change is found in functional and technical change requests. Change primarily begins with law or legislation (e.g. National Defense Authorization Act (NDAA)) and regulatory, policy and procedural requirements (e.g., Joint Staff, DoD, DON, and Commandant of the Marine Corps (CMC), Warfighters, etc.). Other changes result from BPR efforts and technology advances necessary to improve business and technical efficiencies. Finally, the unpredictable nature of overseas contingencies contributes to the variable workload levied upon the TSO.

1.2 Scope

1.2.1 Technology Services Organization (TSO)

The TSO requires technical and functional Contractor support for a myriad of highly complex, Government-designed and Government-owned enterprise business-critical systems. The TSO GOGOCS IPT provides critical services for a unique blend of Marine Corps enterprise business systems that cut across the spectrum of technologies and platforms. Historically, a wide variety of technical and functional skills and experience levels have been required to support the various programming languages, database platforms, operating systems, hardware, and software.

Historically, the Government’s experience has been that Contractor technical and functional support performed required a balanced mix of experience including senior, middle, and junior technical staff, subject matter experts, consultants, as well as management and administrative staff, all capable of working within the TSO’s GOGOCS IPT. The Contractor is expected to provide resources with the skills and experience necessary to support TSO’s business systems and underlying technologies. The Contractor shall ensure staffing adequate to support fluctuating workload at all locations. A detailed description of each system or environment is provided in PWS Appendix A. TSO supported and supporting systems include:

Enterprise-class Business Systems

· Marine Corps Total Force System Family of Systems

· Marine Corps Total Force System (MCTFS)

· Unit Diary/Marine Integrated Personnel System (UD/MIPS)

· Operational Data Store Enterprise (ODSE)

· Marine Online (MOL)

· W2/W2 Corrections (W2/W2C)

· Document Tracking Management System (DTMS)

· Marine Corps Administrative Analysis Team (MCAAT)

· Marine Cash (MC)

· Management Reports (MNGTRPTS)

· Standard Accounting Budgeting and Reporting System (SABRS)

· Marine Corps Financial Integrated Analysis System (MCFIAS)

· SABRS Management Analysis Retrieval Tool System (SMARTS)

· Program Budget Documentation Database (PBDD)

· Civilian Personnel Information Management System (CPIMS)

· Unfunded Priority List (UPL)

· Current Year Deficiency (CYD) Database

· PORTAL

· Marine Corps Orders Resource System (MCORS)

· Marine Corps Reserve Order Writing System (MROWS)

· Marine Corps Permanent Duty Travel (MCPDT)

· Marine Corps Single Orders Repository (MCSOR)

· Command Legal Action Module (CLAM – formerly MCEAS)

· Navy Reserve Orders Writing System (NROWS)

· Air National Guard Order Writing System (AROWS)

· Air Force Reserve Order Writing System (AROWS-R)

Organization Support Tools

· Business Enterprise System (BES)

· JIRA

· Decision Logic Table-Web (DLT-Web)

· Enterprise Management System (EMS)

· SharePoint (SP)

· TSO Sustainment Environment

The TSO GOGOCS IPT, in cooperation and coordination with the Manpower Information Systems Support Activity (MISSA), and Manpower Information (MI) Systems Division, HQMC (M&RA) as well as the Marine Corps Pay Requirements Directorate (MCPRD) and Resource Fiscal Finance Branch (RFF), HQMC (P&R), is responsible for the facilitation and generation of system enhancements for the above systems.

· MISSA requires functional Contractor support to document system enhancements in the Functional Requirements Document (FRD). The FRD provides for a maintainable standardized reference of MCTFS functionality for training, future design considerations, and integration of new functionality. The FRD provides documentation of business rules upon which MCTFS is built. The FRD is a living document that is in conjunction with every major MCTFS software release. Through the utilization of Decision Logic Tables (DLT), File Descriptions, and other technical documentation, business rules are identified and captured, within the FRD in common English language to make it easily consumable and understandable by the laymen. This includes identifying business rules for each process including a detailed breakout at the basic Type Transaction Code (TTC) level with general business rules defined for called modules. The FRD also documents all generated system advisories as additional general business rules.

· MI Systems Division requires both technical and functional Contractor support spanning the entire spectrum of the MCTFS Family of Systems. Functional support includes, but not limited to, analyzing and developing new requirements for the MCTFS Family of Systems, participation in Joint Application Development efforts, etc. Technical support includes maintaining and enhancing the Command Profile and Manpower Performance Indicator application and other in-house technical initiatives.

· The MISSA requires functional Contractor support to operate the MOL Help Desk. MOL Help Desk support includes training and technical guidance for each of the over 20 Marine Online Modules covering processes such as Leave, Promotion Recommendations, Composite Score Calculations, MOL Security and many others. The MOL Help Desk consolidates and forwards issue solutions and enhancements to the MISSA Government Functional Managers for system improvements.

The TSO, MI Systems Division and P&R Resource Fiscal Finance Branch (RFF) requires functional Contractor support for the Marine Corps travel function and Marine Corps travelers through operation of the consolidated Defense Travel System/Marine Reserve Orders Writing System (DTS/MROWS) Help Desk. The DTS Help Desk provides Tier 1 and Tier 2 support via voice, email and web, to civilian and uniformed Marine (active and reserve) Temporary Additional Duty (TAD) travelers using the Defense Travel System (DTS). Contractor functional support includes assisting Marine Corps Reserve unit travel administrators through Marine Reserve Orders Writing System (MROWS) Help Desk services. Support for the Marine Corps travel function includes training, curriculum development, Staff Assist Visits (SAVs) and travel function monitoring & reporting. DTS & MROWS Help Desk services are performed at the MCITC in Kansas City, Missouri.

2 General Information

2.1 Non-Personal Services

The Government shall not supervise Contractor personnel. Under no circumstances shall the Government assign tasks to or prepare work schedules for an individual Contractor employee. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of or give the perception of personal services. If the Contractor believes that any actions constitute or are perceived to constitute personal services, it shall be the Contractor's responsibility to notify the COR and the Procuring Contracting Officer (PCO) immediately.

2.2 Privacy Act and HIPAA

All services performed relative to the requirements identified in this PWS allow access to unclassified or sensitive information covered by the Privacy Act of 1974 and other DoD and USMC regulations. Some information provided by the Contractor during the application process may be subject to the Health Insurance Portability and Accountability Act (HIPAA).

2.3 Travel / Temporary Duty (TDY)

The Government will determine the need for Contractor travel. Historically the Government has required the Contractor travel at a rate of $100,000 per year. Contractor travel is supported through a Not To Exceed (NTE) Contract Line Item Number (CLIN). The Government anticipates a significant increase in Contractor travel requirements and plans to issue a NTE Travel CLIN on the order of $250,000 per year. Travel to Government or non-Government CONUS facilities will be required and may require additional coordination due to security regulations (i.e. Visitor Requests). Travel to OCONUS facilities and sites is not anticipated. In addition to previously identified Key Personnel travel, the Contractor can expect similar, additional travel requirements for other staff members. All travel requirements (including plans, agenda, itinerary, and dates) shall be pre-approved by the COR (subject to local policy procedures) and are on a cost reimbursable basis. The Contractor shall make necessary travel arrangements for Contractor personnel. Costs for travel shall be billed in accordance with the regulatory implementation of Joint Travel Regulations (JTR), Public Law 99-234 and FAR 31.205-46 Travel Costs.

3 Performance Requirements

Contractor service performance requirements are categorized as General Requirements and High Level Objectives (HLOs) and organized as follows:

1) General Requirements

2) HLO1 System Engineering & Integration

3) HLO2 Mission Support

4) HLO3 Systems Operation & Support

5) HLO4 Cybersecurity

6) HLO5 Help Desk

PWS Appendix C provides a documented listing of TSO GOGOCS IPT constraints. PWS Appendix C’s first tab provides an introduction to the spreadsheet, eight (8) tabs listing TSO sub-organization constraint documents and affected areas, and a final tab that maps constraints to HLO tasks. Constraints associated with tasks will be annotated either directly with the task or in a mapped table (extract from final tab in PWS Appendix C) at the end of each sub-section. PWS Appendix C is not an exhaustive list of TSO GOGOCS IPT constraints, only a sub-set of the most significant constraints to provide Offeror’s context for IPT operations and enable proposal submission and subsequent evaluation. TSO GOGOCS IPT constraints are representative of the TSO’s process maturity and process improvement program. These constraints are evaluated by all members of the IPT and subject to routine improvement opportunities and therefore change quite frequently. The full constraint library will be made accessible to the Contractor, upon award, as part of Government-furnished material..

3.1 Contractor Performance

3.1.1 Performance Standards and Acceptable Quality Levels will be evaluated on established Performance Standards (PS) and associated Acceptable Quality Levels (AQLs). PSs and associated AQLs measure performance for:

· Timely completion of assigned tasks and tickets – PS1, PS3 and PS4

· Quality of assigned task deliverables – PS2

PSs and associated AQLs are identified for General Requirement and HLO tasks in the following table and defined within each sub-section:

PS3 (AQL3A, B, C, D & E)

PS4 (AQL4A, B & C)

3.1.2 Specific Tasks and Workload Distribution

The Contractor will be assigned specific tasks via a JIRA ticket. JIRA is a commercial-off-the-shelf (COTS) issues management tool that the Government has tailored to support the formal assignment of specific tasks to the Contractor and receipt of task deliverables/completion.

The Contractor shall ensure timely and effective management for the distribution of work to Contractor resources and respond to specific task actions in the prescribed timeframe. The Contractor shall provide deliverables and report task completion via JIRA. It is important to note that while JIRA represents the formal tool and method for specific task assignments and deliverable receipts; the SDLC schedules, timelines and processes will dictate the timing of work effort and delivery of work products. Contractor personnel are expected to perform work on more than one change request, discrepancy resolution and/or task at any given time.

The Contractor can expect more than 1500 specific tasks to be assigned annually. Specific tasks are typically associated with Software Development Lifecycle (SDLC) schedule and milestones; however, some specific tasks identify work incrementally (monthly) or for the entire period of performance (annually). Specific tasks, assigned via a JIRA ticket, are used to assign Contractor work for all projects types including:

· Designing, programming and/or testing change requests

· Creating, reviewing, and/or updating documents

· Providing operations and implementation support

· Performing new technology research and analysis

· Providing project management, process improvement and quality assurance activities

The flexibility of JIRA has allowed the TSO to utilize this tool for a large number of business and IT support functions. Additional functions supported using JIRA are described in PWS Appendix C documents.

3.1.3 Labor Reporting

An essential component of the TSO’s project and performance management is a robust metrics collection program. TSO uses a labor reporting system (LRS) to record effort (hours) for all employees against every project/activity the organization performs. Currently the TSO utilizes a COTS software-as-a-service product called Replicon TimeBill. Generically this tool is referred to as “LRS-Web” and is the standard labor reporting and tracking system. In order for TSO to perform sound project and performance management, all TSO GOGOCS IPT personnel are expected to record effort (hours) against assigned projects in LRS-Web at least weekly.

The Contractor shall validate and verify the accuracy of time logged in LRS-Web and ensure the hours match the Contractor’s timekeeping system to coincide with the bi-weekly Government pay period. The Contractor shall ensure sub-Contractors are entering time accurately on a daily basis as well. Instructions for both LRS-Web use and the TSO Labor Reporting Guide are included in PWS Appendix C.

3.1.4 On-Call and Surge Support

TSO supported systems, on an unspecified but recurring basis, as well as the Marine Corps Enterprise Network (MCEN), Marine Corps Information Technology Center (MCITC) & the Marine Corps Enterprise IT Services (MCEITS) where many of the TSO-supported systems are hosted, suffer unannounced/unanticipated periods of disruption. Disruption of these Marine Corps business-critical systems, and the enterprise functions they support, demands immediate resolution. Designated TSO GOGOCS IPT members, both Government and Contractor personnel, will participate in and be available to support “On-call” duties should a service disruption require immediate response and resolution. Identification and designation of on-call personnel is task dependent and delineated within PWS Appendix C constraints. Should a service disruption extend beyond a reasonable period (more than a normal 8-hour work day), TSO Government and Contractor personnel will be expected to both extend (work more than eight (8) hours per day) and adjust work schedules to support service restoration activities. Contractor on-call and surge support is not unique, rather just reflective of an increase in workload and/or adjusted work schedule, and defined as part of the performance requirements in Section 3.

The Contractor will be required to adjust individual work schedules to support operational events and schedules such as software releases/implementations, routine and adhoc maintenance windows, hardware installation, version upgrades and patching. Schedule adjustments may also be required due to site closures at other locations resulting from inclement weather, facility unavailability and federal holidays, furloughs or shutdowns. The Contractor is expected to perform all assigned tasks regardless of required schedule adjustments.

3.1.5 Place of Performance and Hours

3.1.5.1 Place of Performance. Contractor support will be principally required on-site at the Kansas City, MO location; however a limited amount of Contractor support will also be required on-site in other locations. The Government expects the Contractor to hire within the local commuting area and WILL NOT support daily/weekly travel of Contractor personnel to and from the identified work locations. Work locations include:

· Marine Corps Information Technology Center (MCITC) – Kansas City located at 2306 East Bannister Road, Kansas City, Missouri 64131; More than 250 available workstations, spaces and offices.

· BMO Plaza Building located at 135 North Pennsylvania Street, Indianapolis, Indiana 46204; 15 available workstations.

· Wesley Marsh Center, Building 3280 located on Marine Corps Base (MCB) Quantico at 3280 Russell Rd., Quantico, Virginia 22134; 8-10 available workstations.

To facilitate TSO GOGOCS IPT continuity of operations in the event of inclement weather, the Government will provide the Contractor with the equipment/software (laptops/VPN) necessary to support remote access to networks/environments/systems/applications. Additionally, the Government has sufficient IT capacity to accommodate up to ten (10) full-time remotely located Contractor personnel. The Contractor shall coordinate with and receive written approval from the Contractor Officer Representative (COR) prior to onboarding and/or assigning work to any full-time remotely located personnel. Remote locations must be safe and secure locations (i.e. personal residence or Contractor facility) approved for Contractor personnel use.

3.1.5.2 Work Hours. TSO GOGOCS IPT services will be performed during the following hours, by location and/or function:

· The TSO GOGOCS IPT provides services at locations in both the Eastern and Central time zones; TSO COCOCS IPT services shall be performed between the 0600-1800 local, the Government’s core hours are 0900-1500 Eastern time zone and Contractor support is required during these hours. This maximizes the communication, coordination and collaboration opportunities across the TSO GOGOCS IPT.

· TSO GOGOCS IPT services associated with the “24x7” Production Support Section will be provided in three (3) shifts from 0700-1530 (1st Shift), 1500-2330 (2nd Shift) and 2300-0730 (3rd Shift) Central time zone. The weekly schedule begins with 2nd Shift on Sunday. Contractor support of the “24x7” Production Support Section is required during these times.

3.2 General Requirements

3.2.1 Program Management

The Government is responsible for determining cost, schedule, technical performance of the TSO GOGOCS IPT support systems and operations. The Contractor is responsible for meeting performance requirements identified in this PWS and supporting and participating in the TSO GOGOCS IPT.

3.2.2 Post-Award Conference

In accordance with FAR 42.503, a Post Award Conference shall be conducted. The Contractor shall attend and participate in the post-award conference within seven (7) business days of contract award at the Indianapolis work location. The meeting will provide an introduction between the Contractor and Government personnel who will be involved with the contract. Discussions at the meeting shall include technical, management, and security issues, travel authorization, and reporting procedures to include initial report suspense dates for all recurring program, quality assurance and Contractor report requirements. The Contractor shall provide the Program Management Plan.

3.2.3 Program Management Plan (PMP)

The Contractor shall prepare a Program Management Plan (CDRL B001) depicting the Contractor’s activities for managing the services performed to ensure that all scheduled objectives are achieved and quality performance is delivered.

3.2.4 Transition

The Contractor shall submit as a part of its proposal a Transition Plan (CDRL B002) which shall include, but not limited to, transition-in activities, transition-out activities, and staff onboarding. Throughout the Transition-In/Transition-Out periods, it is essential that interruptions or delays to work in progress, that would impact the mission, be minimized. The contractor shall keep the Government fully informed of the status throughout the transition period.

3.2.4.1 Transition-In Activities. Transition ensures the incoming Contractor the opportunity to maximize capture of the existing pool of expertise, develop a thorough understanding of the existing system life-cycle management processes and system requirements, as well as allow for knowledge transfer with the incumbent Contractor. The Contractor shall present the Transition Plan at the post-award kick-off meeting and within five (5) business days of the kick-off meeting, provide a finalized Transition Plan that addresses the migration of assigned workload. All transition-in activities will be based on a transition period of no more than ninety (90) calendar days. The transition shall ensure minimum disruption to TSO GOGOCS IPT operations. The Contractor shall minimize service degradation during and after transition. The Contractor will receive support not only from the Government, but also from the incumbent Contractor who is contractually obligated to support transition activities.

Although specifically identified as Transition-In activities, coordinating and performing facility and Common Access Card (CAC) badge issuance at the Kansas City work location, and monitoring physical security of assigned spaces and visitor access in the Indianapolis work location, will continue throughout the life of the contract for all employees including civilians, contractor and military.

3.2.4.2 Transition-Out Activities. The Contractor shall provide a draft Transition-Out plan for transitioning work from itself to a follow-on incoming Contractor. The draft Transition-Out plan shall address how the Contractor will formally coordinate with the Government and subsequent incoming Contractor management and staff in order to transition services.

3.2.4.3 Staff Onboarding. The Contractor shall have all personnel on boarded (fully staffed) and in place NLT 30 days after award.

3.2.5 Management Reviews (MR)

The Contractor shall schedule, prepare and present monthly Management Reviews (MRs). These reviews will provide a forum for the Contractor, Procuring Contacting Officer (PCO), Contracting Officer Representative (COR) and key Government staff to discuss critical management topics including: Contractor Performance/Personnel Issues, Workload, Process Improvement, Other topics of the Contractor or Government’s. The Contractor shall prepare and submit an agenda NLT two (2) business days prior to, and provide a subsequent memorandum for the record (MFR) (CDRL B003) NLT five (5) business days after, each MR to the COR. MRs will be held at the BMO Building in Indianapolis. The Government will review and accept both MR agenda and MFR, and may choose to add additional agenda topics to be addressed as part of the MR.

3.2.6 Contractor Cost and Performance Reporting

The Contractor shall prepare and deliver to the COR a monthly Contractor Performance, Cost and Status Report (CDRL B004).

3.2.7 Required Training and Certifications

3.2.7.1 Annual Training

The Government does not typically provide Contractors with training, with the exception of DoD- and DoN-mandated information assurance training. The Contractor shall ensure all Contractor personnel complete required annual training as determined by the Government training officer. Contractor personnel assigned to perform DON IT functions shall receive the requisite information assurance, security awareness, and functional competency training as required by their designated level of access and scope of duties.

3.2.7.2 Security Training and Education

The following Government-provided training represents the minimum requirements for security education for all Contractor personnel:

· Indoctrination of personnel upon employment by the DON in the basic principles of security

· Orientation of personnel who will have access to classified information or assignment to sensitive duties (including IT duties) at the time of assignment, regarding command security requirements

· On-the-job training in specific security requirements for the duties assigned

· Annual refresher briefings for personnel who have access to classified information

· Counterintelligence briefings annually for personnel who have access to information classified Secret or above

· Special briefings as circumstances dictate

· Debriefing upon termination of access

Security education requirements are locally governed by TSO-wide constraints C1.2, C1.29, C1.39 and Business Operations Division constraint C8.30 in accordance with PWS Appendix C constraints.

3.2.7.3 IT Certification

Contractor personnel supporting specific Cybersecurity (CY) functions shall obtain the appropriate DoD-approved CY baseline certification (available at http://iase.disa.mil/index2.html) prior to onboarding and being assigned tasks. No waivers will be authorized. Contractor personnel are required to allow applicable certification authority to release certification information to DoD.

Contractor personnel will have up to 6 months to obtain the appropriate Computing Environment/Operating System certification for the functions performed. The Contractor shall ensure Contractor personnel certifications are maintained on the appropriate periodic basis (i.e. annually, every 3 years).

3.2.8 General Requirements Performance Standards and Acceptable Quality Levels The following applies to General Requirement tasks:

3.2.8.1 PS1 – Tasks will be completed by the required completion date IAW applicable PWS Appendix C constraints

3.2.8.2 AQL1A – 95% of tasks completed by the required completion date

3.2.8.3 PS2 – Deliverables will be provided IAW task requirements and applicable PWS Appendix C constraints

3.2.8.4 AQL2A – 10% of task deliverables will be rejected no more than once

3.2.8.5 AQL2B – 5% of task deliverables will be rejected no more than twice

3.2.8.6 AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

3.2.9 General Requirements Constraints. The following matrix maps applicable constraints to General Requirement tasks.

1, 6, 7

3.3 High Level Objective (HLO) 1 - Systems Engineering and Integration

The objective of Systems Engineering and Integration is to develop, maintain, and/or sustain systems based on customer requirements with the expectation that implementation of requirements will satisfy user needs and system performance. The Systems Engineering and Integration objective is applicable to all supported systems (see PWS Appendix A) of varying platforms to include mid-tier, client/server (phasing out) and mainframe. This objective is further described by the following:

Data management, conversion and migration institutes the controls for ensuring the integrity of Marine Corps system data as it relates to its use within the Marine Corps, DON, DoD and Federal business processes. The integrity of converted and migrated data is critical to ensure accuracy and audit compliance with all regulatory and legislative mandates. The development of data structures, such as Data Warehouses, Data Marts, and Databases, includes the conversion (Extract/Transform/Load) and aggregation of data from multiple authoritative data sources (ADS) to enable users to query, report, and analyze across the DoD Enterprise. The TSO engineering, integration and management activities encompass transactional, reporting, and archival of data in databases, data stores and data warehouses on various technology platforms, such as – Oracle, DB2, Adabase and MS SQLServer.

Engineering activities include the analysis, design, development, test and optimization of interfaces; application and presentation layer capabilities; and the interaction with the data layer. The integration of the interfaces, and the application and presentation capabilities, both encompass the engineering of the authentication and authorization of users, session management, load balancing and external communication using DoD information assurance (IA) directives and instructions for application development. TSO supported systems utilize application appropriate programming languages such as COBOL, Natural and Java.

3.3.1 HLO1 Objective Tasks

The Contractor shall:

3.3.1.1 Analyze, review, document, and create size and/or effort estimate for change requests and maintain in the appropriate organization support tools.

3.3.1.2 Analyze, review, create, modify, consolidate and/or refine detailed system design specifications for change requests such as data flow diagrams, flowcharts, structure diagrams and charts, activity models, data models, functional requirement documents and decision logic tables in appropriate organization support tools.

3.3.1.3 Identify, create, update, debug, document, integrate, store, commit and/or compile software source code such as programmer test output, modules, processes, screens, menus, and domain.

3.3.1.4 Coordinate, design, create, and/or document help manual topics, help screens, tutorials, and operating instructions.

3.3.1.5 Design, create, modify, test and/or document interfaces, prototypes and/or proof of concept.

3.3.1.6 Create, modify, document and perform testing activities such as test plans, test cases, test data, test scenarios, test scripts, test environment setup and coordination, automated test conditions for unit testing, system testing, regression/operational testing, integration testing, performance/load testing and test discrepancies.

3.3.1.7 Perform issues/trend/capacity analysis, document and implement approved changes for databases, database schemas, database objects, data structures, and metadata to ensure data integrity.

3.3.1.8 Perform implementation support activities such as pre- and post-implementation planning, configuration management, release builds and instructions, and troubleshooting for all change requests.

3.3.1.9 Perform research, analysis, documentation, and response to Tier 3 Help Desk reported issues.

3.3.1.10 Facilitate, moderate, participate in, and/or document results of Joint Application Development (JAD) sessions.

3.3.1.11 Research, evaluation, documentation, recommendation and/or implementation of OEM vendor recommended upgrades and/or new technologies to improve application capabilities, mitigate risks and anomalies, or generate efficiencies.

3.3.1.12 Identify, analyzes, and report risks (security, functionality, reliability, availability) and perform risk management activities for change requests.

3.3.1.13 Analyze and document impact of critical computer resources and potential risks of change requests.

3.3.2 HLO1 Performance Standards and Acceptable Quality Levels The following applies to HLO1 tasks:

3.3.2.1 PS1 – Tasks will be completed by the required completion date IAW applicable PWS Appendix C constraints

3.3.2.2 AQL1A – 95% of tasks completed by the required completion date

3.3.2.3 PS2 – Deliverables will be provided IAW task requirements and applicable PWS Appendix C constraints

3.3.2.4 AQL2A – 10% of specific task deliverables will be rejected no more than once

3.3.2.5 AQL2B – 5% of specific task deliverables will be rejected no more than twice

3.3.2.6 AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

3.3.3 HLO1 Objective Constraints Objective Constraints The following matrix maps applicable constraints to HLO1 tasks.

3.4 HLO 2 – Mission Support

The Mission Support objective is applicable to all organizational activities, which is to perform the support functions such as Project Management, Financial Management and Economic Analysis which enable a successful, process-mature organization. This objective is further described by the following:

Performing Financial Management and Economic Analysis allow the TSO GOGOCS IPT to identify products, conduct research, document technical and functional requirements, analyze alternatives and prepare supporting Business Case(s) for the use of Commercial-Off-The-Shelf (COTS) products.

Performing Functional and Business Process Improvement allow the TSO GOGOCS IPT to identify, document and/or implement improvement opportunities for Marine Corps business functions by leveraging the associated business systems which automate these functions. This objective supports a myriad of enterprise manpower, financial management, personnel administration and pay functions.

The TSO GOGOCS IPT Software Process Management leverages and follows the Carnegie-Mellon Software Engineering Institute (SEI) Capability Maturity Model Integrated (CMMI)-based organizational Software Process Improvement (SPI) program and the organizational Quality Assurance program used to monitor, collect, measure and improve software development and engineering processes within the TSO.

3.4.1 HLO2 Objective Tasks

The Contractor shall:

3.4.1.1 Facilitate, moderate, participate in and/or document results of meetings such as user acceptance meetings, technical evaluations, boards, architectural discussion groups, software release meetings, and Agile Scrum meetings.

3.4.1.2 Perform recurring project management activities (daily/weekly/monthly) such as track and report effort completed for assigned projects; maintain software change history; monitor and distribute change request inbox for estimation; prepare and maintain release management plans and schedules; maintain quality and timeliness metrics and reports; maintain change management plans; prepare and maintain project plans and baselines; maintain standalone & software release project lists; update Decision Logic Tables (DLTs), Remark and Table Spreadsheets; update execution checklists; update Agile burn down matrices and reports and Work Breakdown Structures (WBS); update completion statistics for configuration items; update Agile Product and Iteration Backlogs; and prepare and update reports, charts, presentations and briefs.

3.4.1.3 Prepare artifacts for, conduct, schedule and/or participate in, formal or informal quality reviews and audits such as SIT/SAT readiness reviews, Post Implementation Reviews (PIRs), Agile Retrospectives, Technical Solution Walkthroughs, Design Peer Reviews, Test Peer Reviews, and Programming Peer Reviews.

3.4.1.4 Research, analyze, identify, create, and document change requests.

3.4.1.5 Analyze, document, disseminate and maintain system architectures such as DoD Architecture Framework (DODAF) operational views (OVs), system views (SVs), and technical views (TVs).

3.4.1.6 Research, prepare and document responses to data calls such as audits, assessments, and headquarter and congressional queries.

3.4.1.7 Provide recommendations for and perform configuration, design, development, testing, management and/or administration of organizational support tools.

3.4.1.8 Perform document management activities such as creation, classification, versioning, control, maintenance, storage, disposal and destruction.

3.4.1.9 Develop content and provide technical and non-technical training such as Agile classes, system and business process “how to” guides, and organizational tool and process guides.

3.4.1.10 Participate in, make recommendations for, and perform continuous process improvement activities such as collection, analysis, evaluation, preparation and publication of process improvement initiatives.

3.4.1.11 Collect, analyze, evaluate and report system and organizational performance results such as the Balanced Scorecard (BSC).

3.4.1.12 Prepare for, create, modify, execute, compile and report results of surveys such as customer satisfaction and PIRs.

3.4.1.13 Perform function point activities such as counting, analyzing and reporting activity results.

3.4.1.14 Prepare for, participate in, and collaborate on process maturity assessments, appraisals and readiness reviews.

3.4.2 HLO2 Performance Standards and Acceptable Quality Levels The following applies to HLO2 tasks:

3.4.2.1 PS1 – Tasks will be completed by the required completion date IAW applicable PWS Appendix C constraints

3.4.2.2 AQL1A – 95% of tasks completed by the required completion date

3.4.2.3 PS2 – Deliverables will be provided IAW task requirements and applicable PWS Appendix C constraints

3.4.2.4 AQL2A – 10% of specific task deliverables will be rejected no more than once

3.4.2.5 AQL2B – 5% of specific task deliverables will be rejected no more than twice

3.4.2.6 AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

3.4.3 HLO2 Objective Constraints. The following matrix maps applicable constraints to HLO2 tasks.

3.5 HLO 3 - Systems Operations and Support

The objective of Systems Operations and Support is to ensure all systems, devices and infrastructure remain operational for all users. This objective includes coordination and collaboration with other hosting/service providers and interface partners such as MCNOSC, MCEITS and Defense Information Systems Agency (DISA). This objective is further described by the following:

All hardware and software resources utilized are patched and known vulnerabilities are remediated. Hardware and software resources include all personal computers as well as mid-tier environments, systems, servers, storage devices, applications, databases, networks and installed software. Software also includes application and database software on Mainframe systems. This objective includes full lifecycle support for the identification, requirements justification, registration, security and audit compliance, procurement, installation, maintenance, removal and disposal of all hardware and software utilized by the TSO and/or supported organizations.

3.5.1 HLO3 Objective Tasks

The Contractor shall:

3.5.1.1 Analyze, identify and document the potential negative impact of operational changes, such as operating system changes, infrastructure changes and interface changes, to existing systems.

3.5.1.2 Analyze and route change requests to affected operational support staff using the appropriate organizational support tool.

3.5.1.3 Conduct storage management activities such as analyzing, planning, and documenting recommendations for all data storage resources.

3.5.1.4 Monitor, report and notify appropriate users/organizations of system status changes within 10 minutes of change.

3.5.1.5 Perform critical computer resource (CCR) management activities such as track, analyze, plan, and document CCR recommendations for all environments.

3.5.1.6 Collect and distribute system access passwords.

3.5.1.7 Monitor, evaluate and report discrepancies in database and application sessions and audit logs.

3.5.1.8 Analyze and coordinate configuration and release management for assigned environments.

3.5.1.9 Perform data conversion and data migration activities.

3.5.1.10 Perform system performance monitoring and tuning activities on all environments such as load balancing, memory and CPU utilization, and/or application and database sessions.

3.5.1.11 Monitor, report and/or resolve anomalies for system processes and associated interfaces such as data loads, FTPs, remote access, user/session management, IIS support on all environments, test and PFIX cycle issues, U&E cycles, Drill payrolls, Reserve Monthly cycles, and SABRS daily and monthly cycles.

3.5.1.12 Plan, monitor and perform backup and recovery activities.

3.5.1.13 Create, document, maintain and/or execute maintenance utilities/scripts.

3.5.1.14 Create, document, maintain and/or implement system configurations such as desktops, servers, software, TSO supported applications, operating systems and/or network device configurations.

3.5.1.15 Provide installation, maintenance and technical support for all TSO utilized technologies defined in PWS Appendix A.

3.5.1.16 Monitor, evaluate and recommend network device changes such as firewall rules, port and protocol changes and HBSS exceptions to service providers such as MCNOSC and DISA.

3.5.1.17 Submit and track OEM vendor trouble tickets for system troubleshooting such as operating systems, database software and/or networks.

3.5.1.18 Prepare and distribute hardware and software to TSO and supported organizations.

3.5.1.19 Track hardware and software inventory in appropriate organizational support tool.

3.5.2 HLO3 Performance Standards and Acceptable Quality Levels The following applies to HLO3 tasks:

3.5.2.1 PS1 – Tasks will be completed by the required completion date IAW applicable PWS Appendix C constraints

3.5.2.2 AQL1A – 95% of tasks completed by the required completion date

3.5.2.3 PS2 – Deliverables will be provided IAW task requirements and applicable PWS Appendix C constraints

3.5.2.4 AQL2A – 10% of specific task deliverables will be rejected no more than once

3.5.2.5 AQL2B – 5% of specific task deliverables will be rejected no more than twice

3.5.2.6 AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

3.5.2.7 PS3 – Assigned tickets will be resolved IAW priority level and applicable PWS Appendix C constraints

3.5.2.8 AQL3A – Priority 0 tickets will be resolved within four (4) hours of receipt and system restored to service

3.5.2.9 AQL3B – Priority 1 tickets will be resolved within twenty-four (24) hours of receipt

3.5.2.10 AQL3C – Priority 2 tickets will be resolved within seventy-two (72) hours of receipt

3.5.2.11 AQL3D – Priority 3 tickets will be resolved within one hundred and sixty eight (168) hours of receipt

3.5.3 HLO3 Objective Constraints. The following matrix maps applicable constraints to HLO3 tasks.

3.6 HLO 4 – Cybersecurity (CY)

The objective of Cybersecurity Support is to assist the Government in the conduct of day-to-day management and coordination of security efforts, based on DoD, USMC, and Navy Information Assurance (IA) policies and procedures. This objective is further described by the following:

CY support provides full lifecycle Certification and Accreditation (C&A) of TSO-supported systems, networks and data through analysis, documentation, review, validation and continuous monitoring in order to achieve and maintain cyber security compliance with all systems’ Authority-to-Connect (ATC) and Authority-to-Operate (ATO). CY support provides security risk management with continuous monitoring of the TSO’s cybersecurity posture via the assessment, tracking, reporting and auditing of security controls, security regulations, vulnerability scanning and remediation, and contingency planning. This objective ensures the confidentiality, integrity and availability of the data stored and processed on TSO supported automated information systems (AIS), while meeting compliancy requirements related to Federal Law, DoD, DoN and USMC policies.

3.6.1 HLO4 Objective Tasks

The Contractor shall:

3.6.1.1 Perform certification and accreditation (C&A) activities.

3.6.1.2 Perform CY audit activities such as source code and system logs analysis; conduct account management; and monitor privileged permissions, administrative accounts, alternate tokens, and security controls.

3.6.1.3 Scan, analyze, research, mitigate and report security findings for information assurance activities.

3.6.1.4 Monitor, audit, report and maintain security compliance for all systems and system components such as operating systems, applications, personal computers, network and network devices, voice and video terminals, databases, servers, and…