microsoft word - pd08312018172137 · web viewperformance work statement (pws) for navy erp...
TRANSCRIPT
Performance Work Statement (PWS) for Navy ERP Technical Support Services (NETSS) IDIQ
Navy ERP (SAP) Program of Record DRAFT – 13Dec18
1.0 Introduction. The objective of this PWS is to provide integrated system sustainment and infrastructure upgrade support services for the entire Navy ERP (SAP) environment and to obtain contract services to sustain and enhance Navy ERP (SAP).
2.1 Background. Navy Enterprise Resource Planning (ERP) is an SAP-based system and is the Department of the Navy’s (DON) financial and supply information technology system of record. Deployment implementations have concluded and the Program is now in its sustainment phase, although efforts continue to expand and improve functionality. NAVSUP Business Systems Center (BSC) is designated to provide sustainment services, including lifecycle management, stabilization, optimization and audit readiness.
2.2 Requiring Organization. The organization requiring the services outlined in the Performance Work Statement (PWS) is:
NAVSUP Business Systems Center 5450 Carlisle Pike Building 409 Mechanicsburg, PA 17055
2.3 Project Description. The purpose of this PWS is to obtain contract services to sustain and enhance Navy ERP (SAP). There are two main facets of this PWS; firm- fixed requirements and cost-plus requirements. These include: incidents and production issue resolution (based on root cause analysis, HEAT ticket analysis, and various other requests/analysis); interface management processes; system assessments (e.g., performance, compliance); changes based on business process efficiencies and prevailing industry standards; compliancy with business industry standards (e.g. Standard Financial Information Structure (SFIS), Defense Logistics Management Standards (DLMS), Joint Interoperability Testing Command (JITC); technical refreshes; technical software and hardware upgrades; functional upgrades; prevailing emerging technologies; training processes and support; audit functions; data modelling; data archiving; and other Navy ERP (SAP) Governance approved sustainment and enhancement requirements.
3.1 Scope. The scope of services is grouped into three main categories below: Overall Support requirements, firm-fixed requirements and cost-plus requirements. The goal of this PWS is to obtain contractor support services to provide the following:
3.2 Navy ERP (SAP) Program of Record (POR) Overall Support Requirements. The scope of the Navy ERP (SAP) POR Overall Support is to provide integrated system
sustainment and infrastructure upgrade support services for the entire Navy ERP (SAP) environment. Details of task assignments, deliverables, documentation, applicable standards, etc., will be represented in the appropriate sections throughout this PWS. The Overall Support requirements shall be applicable to the firm-fixed and cost-plus POR requirements.
o Navy ERP (SAP) POR Enhancements Components and Utilitieso Navy ERP (SAP) POR Enhancement Services and Processes
3.3 Firm-fixed Core POR Requirements. The scope of the Core POR requirements is services categorized as a “must-have” and a level of effort requirement. The services are categorized in the list of task areas identified below and are further subdivided into sub-task areas. Specific details of task assignments, deliverables, documentation, applicable standards, etc., will be represented in the appropriate sections throughout this PWS.
o Navy ERP (SAP) Program of Record (POR) Support□ Sustain POR Systems□ Tier III Service Desk□ Business Intelligence and Data Warehousing□ Technical Management Support□ Data Management Processes and Support□ Interface Management Processes and Support□ Training Processes and Support
o Navy ERP (SAP) POR Enhancements□ Navy ERP (SAP) POR Enhancement Services and Processes□ Navy ERP (SAP) POR Enhancement Tasks and
Responsibilities□ Navy ERP (SAP) POR Enhancements Prioritization Criteria
o Task Order Support□ Configuration Management Compliance□ Resource Management□ Mentoring and Knowledge Transfer□ Transition Support
3.4 Technical Operations. The scope of the technical operations identifies work to be executed in the areas of technical operations sustainment, Engineering Change Proposal (ECP) support, and special projects support. Technical Operations requirements are included in the list of task areas identified below:
□ General system operations,□ Batch Job Operations,□ Operations Coordination,□ Release management,□ Transport Management,□ Regression Testing and Quality assurance (QA),□ Technical infrastructure support,
□ SAP BASIS administration,□ Program Tool Technical administration, and□ Cyber Security.
3.5 Cost-Plus Requirements. The scope of the cost-plus requirements is to provide services categorized as additional or above the Core POR requirements and include the list of task areas identified below:
□ Program of Record (POR) Supporto In support of or to augment the Core POR team mentioned
in section 3.1□ Technical or Functional Upgrades□ Platform Migrations□ Data Archiving□ Training, Mentoring, and Knowledge Transfer□ Business Process Optimization Tools□ Navy ERP (SAP) Governance-approved Sustainment
and Enhancement Projects
4.1 Directives: Contractor shall comply with the following directives:o Federal Information Security Modernization Act of 2014 (“FISMA”)o DoD Directive 5400.11, DoD Privacy Program, 29 October 2014o DoD Directive 8000.01, Management of the DoD Information Enterprise, 17
March 2016 (incorporating Change 1 July 2017)o DoD Directive 8140.01, Cyberspace Workforce Management, 11 August
2015 (incorporating Change 1, 31 July 2017)o DoD Instruction 4161.02, Accountability and Management of Government
Contract Property, 27 April 2012 (incorporating Change 1, 29 September 2017)o DoD Instruction 8320.07, Implementing the Sharing of Data, Information, and
Information Technology (IT) Services in the Department of Defense, 3 August 2015 (incorporating Change 1, 5 December 2017)
o DoD Instruction 8500.01, Cybersecurity, 14 March 2014o DoD Instruction 8510.01, Risk Management Framework (RMF) for DoD
Information Technology, 12 March 2014 (incorporating Change 2, 28 July 2017)
o DoD Instruction 8582.01 Security of Unclassified DoD Information on Non-DoD Information Systems 6 June 2012 (incorporating Change 1, 27 October 2017)
o DoD 5400.11-R, Department of Defense Privacy Program, 14 May 2007o DoD 8500.01, Information Assurance, 24 October 2002o DoD Manual 8570.01-M, Information Assurance Workforce
Improvement Program, 19 December 2005 (incorporating Change 4, 10 November 2015)
o SECNAV Instruction 5211.5E, Department of Navy Privacy Program, 28 December 2005
o SECNAV Instruction 5239.3C, DON Cybersecurity Policy, 2 May 2016o SECNAV Instruction 5510.30B, DON Personnel Security Program Instruction,
6 October 2006
o SECNAV Manual M-5239.2, DON Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification Manual, 27 June 2016
o SECNAV Manual M-5510.30, Department of the Navy Personnel Security Program, 1 June 2006
o CJCSI 6211.02B--Defense Information System Network (DISN): Policy Responsibilities and Processes of 31 July 2003
o DoD Public Key Infrastructure (http://iase.disa.mil/pki-pke)o ISO/IEC/IEEE 12207:2017(E) First edition 2017-11 - ISO/IEC/IEEE
International Standard - Systems and software engineering -- Software life cycle processes
o ANSI/EIA 649.B-2011 – Configuration Management Standard.o ANSI/EIA 836-2010 – Configuration Management Data Exchange and
Interoperability.o Federal Risk and Authorization Management Program (“FedRAMP”)o Department of Defense Cloud Computing Security Requirements Guide,
Version 1, Release 3, dated 6 March 2017, or the version and release number in effect when cloud services are provided.
o All applicable Security Requirements Guides, Security Technical Implementation Guides, and National Security Agency security configuration guides in effect when cloud services are provided.
o Common Criteria for Information Technology Security Evaluation, Part 3: Security Assurance Components, April 2017, Version 3.1, Revision 5, CCMB- 2017-04-003; or the version and revision number in effect when the cloud services are provided.
o NIST SP 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems, February 2010, includes updates as of 5 June 2014
o NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations, April 2013, includes updates as of 22 January 2015
o NIST SP 800-53A Revision 4, Assessing Security and Privacy Controls in Federal Information Systems and Organizations, December 2014, includes updates as of 18 December 2014
o ISO/IEC 19770-1:2017 – Information Technology – IT Asset Management – Part 1: IT Asset Management Systems - Requirements
o ISO/IEC 19770-2:2015 - Information Technology -- Software Asset Management-- Part 2: Software Identification Tag
o ISO/IEC 19770 Series - Information Technologyo A Guide to the Project Management Body of Knowledge (PMBOK® Guide)
- Sixth Edition
5.1 Requirements/Tasks: Per DFARS 211.106, contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify
themselves as contractor employees in telephone conversations and in formal and informal written correspondence.
The contractor shall be obligated contractually to perform every requirement in this performance work statement. Not every performance requirement has a related standard expressed in this document. In such cases, the performance standard is either inherent in the requirement, or performance is to be in accordance with standard commercial practice.
5.2 Navy ERP (SAP) Program of Record (POR) Support. The objective of this task is to provide integrated system sustainment and infrastructure upgrade support services for the entire Navy ERP (SAP) environment. Sections 5.2, 5.3, and 5.5 shall comply with this section.
5.2.1 Navy ERP (SAP) Components and Utilities include:ERP Central Component (ECC), Supply Chain Management (SCM), Supplier Management Relationship (SRM), Netweaver Portal (NEP), Gateway (Fiori), Screen Personas, NetWeaver Business Client (NWBC), Master Data Governance (MDG),WebMethods, SAP BusinessObjects Business Intelligence (BI), BusinessObjects Data Services (BODS), cProjects, Risk Management Framework (RMF), Governance Risk, Audit and Compliance (GRC), SAP Solution Manager and Global Templates,SAP HANA,SAP HANA Sidecar, SAP Web IDE,SAP Cloud Platform Integration/HCI,SAPUI5 Development, Attunity Gold Client, Custom Code Analysis and Business Process Optimization tools, Archiving tools, Ancile uPerform, and SAP Learning Solutions (LSO), System Architect (SA), and other system tools.
5.2.1.1 The Navy ERP (SAP) services and processes include:5.2.1.1.1 Sustain POR Systems5.2.1.1.2 Tier III Service Desk5.2.1.1.3 Business Intelligence and Data Warehousing5.2.1.1.4 Cross-Team Integration5.2.1.1.5 Technical Operations Management5.2.1.1.6 Data Management Processes and Support:
□ Data Maintenance, Data Governance, Data Quality, Data Architecture, Data Modelling and Meta Data, Data Services, Data Analysis, Data Reporting, Data Migration, Data Distribution, and Data Archiving
5.2.1.1.7 Interface Management Processes and Support5.2.1.1.8 Training Processes and Support5.2.1.1.9 Supply Processes and Support
□ Supply Master Data, Order Fulfillment, Allowancing, Procurement/Materials Management, Inventory Management,
Warehouse Management, and Supply Chain Management (Planning)
5.2.1.1.10 Financial Processes and Support□ Funds Management, Controlling, Sales
and Distribution, Grants/Finance, Project Systems, Asset Management, and Workforce Management
5.2.1.1.11 Business Process Optimization5.2.1.1.12 User Management and Roles Security
Processes and Support5.2.1.1.13 Technical Processes (RICE, Middleware,
etc.) and Support5.2.1.1.14 Custom Code Analysis5.2.1.1.15 Audit and Compliance Processes and Support5.2.1.1.16 Cost Estimation Processes (ROM) and Support5.2.1.1.17 Integrated Master Schedule (IMS) Updates5.2.1.1.18 Identity Management5.2.1.1.19 Audit and Compliance Processes5.2.1.1.20 Cost Estimation (ROM)
5.2.2 All deliverables shall be completed using a Government-approved format.5.2.3 All electronic correspondence shall be communicated using the
Government-approved and secured email account (for BSC 98’s Tier 3 – it is the Navy.mil email address).
5.2.4 All Navy ERP (SAP)-related work shall be performed on Government Furnished Equipment (GFE) to comply with Navy Information Assurance regulations and guidance.
5.2.5 All Navy ERP (SAP)-related documents shall be stored and maintained within Government-approved databases / documentation repositories.
5.2.6 All Navy ERP (SAP)-related documents and deliverables shall be provided in an editable format for future revisions by Government personnel.
5.2.7 The Contractor shall provide the Government with electronic access to All Navy ERP (SAP)-related documents and deliverables, including access to printable reports, metrics containing raw data and formulas, etc…
5.2.8 All Navy ERP (SAP)-related documents and deliverables shall be subject to Government review and approval.
5.2.9 All Navy ERP (SAP) processes shall be performed in accordance with Navy, DoD, and SAP guidance, best practices and standardized approaches.
5.2.10 The Record Management System shall be housed in a government- approved databases / documentation repositories and include, but not be
limited to, the following types of documents: white papers, status reports, audit reports, agendas, presentation materials, and minutes.
5.2.11 The Contractor shall provide meeting minutes for all Navy ERP (SAP) related tasks and meetings. Meeting minutes shall be provided to the applicable Government Team Leads and the Technical Assistant (TA) no later than one week (7 calendar days) after the meeting occurrence.
5.2.12 The Contractor shall follow Navy ERP (SAP)’s established standards and procedures of the following: Project Management, Requirements Management, Resource Management, Configuration Management, Change Management (review and approval), Release Management and Standards, Development Standards, etc…
5.2.13 The Contractor shall follow the Navy ERP (SAP)’s established standards and procedures throughout every stage of the software lifecycle (Plan, Analyze, Design, Build, Test, Integration, Deployment, and Post Production Support).
5.2.14 The contractor shall meet with the NAVSUP BSC Code 98 Department Leadership, TA, COR and other designated government personnel periodically, as required, to receive work prioritization, review progress and accomplishments, discuss and resolve problems, evaluate performance and determine adequacy of staffing.
5.2.15 FRDS Development. The objective of this subtask is to update and develop Functional requirement documentation according to the following:
5.2.15.1 Meet the NAVSUP BSC Code 98 documentation standard5.2.15.2 Refine FRDS requirements through facilitation SME
& Process Owner sessions, joint application development sessions, or one-on-one meetings and interviews for Government review
5.2.15.3 Include Internal and External Interface requirements5.2.15.4 Include Information Assurance (IA) impacts/requirements5.2.15.5 Include User Management (UM) / roles
impacts/requirements5.2.15.6 Include requirements for error handling or unexpected
system/data conditions5.2.15.7 Include System Resource Requirements (hardware impacts
and performance considerations)5.2.15.8 Identify/Propose potential solution alternatives, and review
functional impacts with Process Owner and Functional SME for potential additional enhancements and other changes
5.2.15.9 Identify Training requirement impacts5.2.15.10 Establish and deliver Requirements Traceability Matrices5.2.15.11 Include analysis of required changes to other
objects impacted by the change to the primary object5.2.16 WBS Development & Execution. Participate in Work Breakdown
Structure (WBS) definition and execution:
5.2.16.1 Provide the Government with estimated completion dates based on team capacity bandwidth and based on prioritization for each software development life cycle phase to meet deadline for completion of the WBS
5.2.16.2 Meet estimated completion dates for each assigned WBS task unless special circumstances approved by the TA permit missing the completion date
5.2.16.3 Follow current Release Management Processes5.2.16.4 Technical Specification Creation. Create related Technical
Specifications (e.g. TDS, TFS, HLDs) which:□ Perform proper unit testing of
technical changes□ Document technical
design considerations / changes
5.2.17 Development. Create applicable Code and Configuration which:5.2.17.1 Support Configuration Management5.2.17.2 Are efficient (do not contain unnecessary looping
and/or internal data tables)5.2.17.3 Provide sufficient performance based on existing
database table indexes5.2.18 Create Test Plans. Create/Update related Test Plans which:
5.2.18.1 Map to each requirement in the approved FRDS5.2.18.2 Include both positive and negative test conditions5.2.18.3 Address error handling and atypical system/data conditions5.2.18.4 Include performance stress testing as applicable
(dependent on prioritization/availability of Space and Naval Warfare System Center Atlantic team)
5.2.18.5 Build test data while maintaining database integrity5.2.18.6 The test events must comply with appropriate requirement
design specifications, business rules and standards.5.2.18.7 Follow the established process to review and approve
the test plans5.2.18.8 Execute Test Plans. Execute applicable Test Plans &
Test Cases (Unit, System, Functional, Interface, Regression, Performance, Integration and/or Interoperability)
5.2.18.9 Generate necessary test data and transactions in the applicable test environments to exercise applicable data values and known scenario
5.2.18.10 Coordinate Functional testing with selected end users in test environment as applicable
5.2.18.11 Work with Developers to satisfactorily resolve bugs found during testing
5.2.18.12 Document test results within the appropriate tools via following the established testing process / procedures
5.2.18.13 Coordinate with Quality Assurance Team to accomplish Regression Test to assist with and/or create test data,
troubleshoot errors during test execution and update Automated Tests
5.2.18.14 Update task management system, such as HP Quality Center, with the appropriate testing status to status and detail of test event
5.2.19 Migration. Prepare New/Revised Software Modules for Production Environment Migration:
5.2.19.1 Prepare functional migration package with supporting documentation to Navy ERP Core POR and other essential teams for Approval and scheduling of Production migration
5.2.19.2 Prepare technical migration documents, transport and migration installation instructions for migrating related code package to the production environment
5.2.19.3 Resolve questions regarding functional and technical package(s) including transports
5.2.19.4 Provide Sustainment and Process Owner with Summary Release Notes of applicable functional changes with details of end user impacts
5.2.19.5 Provide a release implementation plan detailing how the solution should be implemented, if there are any Job Scheduling considerations, time constraints, data clean up, communications, external partner considerations.
5.2.19.6 Identify impacts to associated Enterprise Job Aides and local Job Aides for requisite nomenclature/screenshot updates
5.2.20 Provide Post-Production Support.5.2.20.1 Validate transports and code changes were correctly
installed to allow for enhanced code and functionality usage (IAW documented migration instructions)
5.2.20.2 Perform post-maintenance/migration window operational checkpoints in the production environment to verify continued system operations for Batch Job processing and expected program execution within the required time threshold
5.2.20.3 Participate in Process Owner/Business Process Analysis (BPA) conference calls/meetings to assist in addressing BPA questions as needed after migration of new/revised code
5.2.20.4 Analyze and document related operational problems from functional changes in existing system processes, interrelationships, interfaces, and data, identify solutions and take corrective action as appropriate to maintain continued Automation Information System (AIS) operation.
5.2.20.5 Coordinate workload and problem solution deliveries with interface partners, to include Defense Logistics Agency (DLA) Transaction Services, DLA Logistics Information Services/Integrated Data Environment, other Sustainment sites, and the Build teams
5.3 Firm-fixed Core POR Requirements. In addition to following section 5.1, the objective of this task is to provide integrated system sustainment and infrastructure upgrade support services for the entire Navy ERP (SAP) environment.
5.3.1 Sustain POR Systems Tasks and Responsibilities. The objective of this subtask is to provide support of system sustainability, continuity, and integrity. In performance of this TO, the Contractor shall provide and coordinate support with, which includes all of the requirements listed in section 5.0, section 5.1 and requirements listed below:
5.3.1.1 Resolving corrective maintenance and repair defects (e.g., analyze issues; develop, test and deploy solutions; and provide post-production support) to meet service level times/requirements (SLT) and/or key release milestones in production.
5.3.1.2 Provide POR Service Review Status Reports, other metrics. Resolve issues related to data integrity, data quality, data migration, data conversion, training, roles, user management, interface connectivity, security, etc…
5.3.1.3 Monitoring and maintain integration and accurate data exchanges between ECC, BI, SCM, SRM, GRC, IDM, MDG, Gateway, and related Navy ERP (SAP) components.
5.3.1.4 Support and maintain system integration processes, activities, etc.
5.3.1.5 Analyze the impact of vendor-required or -recommended, SAP OSS notes, SAP patches, and NetWeaver plug-ins on NAVY ERP (SAP).
5.3.1.6 Implement and maintain Design Changes and Engineering Change Proposals (ECPs) to resolve, change, or improve technical and functional requirements.
5.3.1.7 Supporting system refreshes and upgrades for Navy ERP(SAP) and subcomponents to meet policy changes aligned with Navy, DoD, and SAP guidance.
5.3.1.8 Support roadmap to HANA, configuration, table verification and mapping, and cross-team coordination.
5.3.1.9 Support Attunity Gold Client Software or equivalent implementation and sustainment.
5.3.1.10 Providing support for Navy ERP (SAP)-related document creations and revisions prior to Development Phase including: Standard Operating Procedures (SOPs), Functional Requirements Design Specifications (FRDSs), Desk Guides, etc
5.3.1.11 Providing support for all phases of master and transactional data lifecycles by following related policies/procedures, implementing appropriate technologies, frameworks, and utilities to ensure system continuity and stability.
5.3.1.12 Supporting all phases of interface lifecycle management by following related policies and procedures and ensure system continuity, stability, and auditability.
5.3.1.13 Supporting interface reconciliation and error resolution by following related procedures (where applicable, creating new procedures) to assure that data exchanges are accurate and auditable.
5.3.1.14 Coordinating and provide continuous support regarding maintenance activities (e.g., scheduled and unscheduled patches, SAP Online SAP Support Notes (OSS), fixes, and/or releases) with BSC and BSC-recommended stakeholders (e.g., Government and Contractor functional and technical teams/sub-teams).
5.3.1.15 Provide support to/perform Navy ERP (SAP) system closings, period closings (e.g., month-end, year-end and year- start activities).
5.3.1.16 Support financial auditability and system compliance requirements in accordance with guidance, policies, and standards (e.g., SFIS, DLMS, JITC).
5.3.1.17 Perform reviews of changes to business processes and data and evaluate and document changes for architecture impact.
5.3.1.18 Maintaining Test Plan (Regression Test Plans and Functional Test Plans (RTPs/FTPs)) revisions prior to moving out of Unit test and into Regression/Quality test and validation.
5.3.1.19 Preparing weekly individual personnel status reports containing accomplishments, achievements, and issues to Government team leads.
5.3.1.20 Provide POR Service Review Status Reports, other metrics
5.3.2 Tier III Service Desk Support Tasks and Responsibilities. The objective of this subtask is to provide maintenance and issue resolution for Navy ERP (SAP) components and utilities including: ECC, BI, SCM, SRM, NetWeaver Portal; Gateway (Fiori); NWBC, BOE, ScreenPersonas, IDM, MDG, Web IDE, HCI, and other related Navy ERP (SAP) components. In performance of this TO, the Contractor shall provide and coordinate support with, which includes:
5.3.2.1 Service Requests (e.g., Readiness Support Center (RSC) HEAT). Resources are to follow current and approved HEAT Ticket Service Level Targets.
5.3.2.2 Detailed assessments of key issues to the Government POR Teams and Government POR Director.
5.3.2.3 Defects, Break/Fixes, Maintenance Items, Action Items, Design Changes (RFC), Engineering Change Proposals (ECP), including providing specific requirements and feedback.
5.3.2.4 Data Service Requests, Ad Hoc Requests, Functional Maintenance Requests, and Projects.
5.3.2.5 Operations and Maintenance Tasks5.3.2.6 Conducting thorough and comprehensive testing (positive,
negative, stress, regression) while adhering to Navy ERP (SAP) based on requirements, policies, and procedures.
5.3.2.7 Production Cutover, Deployment, and Post-Production Support, including documenting actions in HEAT/QC and providing reports/metrics.
5.3.2.8 Technical Support and System Monitoring.5.3.2.9 Software support for applications, utilities, and components.5.3.2.10 Interface Error Resolution and Maintenance5.3.2.11 SAP Workflow and incidents, including the involvement
of third party providers (e.g., SAP, network service providers).
5.3.2.12 Create transports and migrate code/configuration/functionality through the Navy ERP (SAP) landscape.
5.3.2.13 Resolve and report all Batch Process failures in a timely manner to ensure data exchanges between Navy ERP (SAP) and partner systems are accurate, while complying with audit requirements.
5.3.2.14 Resolving, developing, testing, documenting actions in HEAT/QC, and implementing solutions for sustainment modifications, software releases, and fixes (scheduled and unscheduled).
5.3.2.15 Create new and/or maintain existing Standard Operating Procedures (SOPs) in order to address service incident tickets in a standardized and consistent manner and transfer knowledge.
5.3.2.16 Providing and coordinating support activities and maintaining close integration with Government with Government, including creating and distributing appropriate communications for various Navy ERP (SAP) stakeholders (e.g., Program Management Office (PMO), Financial Management Office (FMO), SSC-LANT, Navy ERP (SAP) Tier II, Enterprise Business Offices (EBOs), Item Managers, Navy ERP (SAP) Tier III Functional and Technical Teams, and system partners).
5.3.2.17 Creating and providing report/metrics for HEAT ticket assignments, resolutions, resolution times, SOPs utilized, etc…for entire incident/problem life cycle. Resources are to follow current and approved HEAT Ticket Service Level Targets.
5.3.2.18 Creating and providing report for monitoring services associated with the ongoing health checks, status reporting, and problem management of Navy ERP (SAP) support activities to ensure production issues are resolved effectively and
efficiently and within Navy ERP (SAP)’s established Service Level Targets (SLTs).
5.3.2.19 Provide updated task and workload tracking/management system(s) as the Navy ERP (SAP) environment evolves.
5.3.2.20 Provide Business Operations and Business Optimization Metrics/reports (WKLY).
5.3.2.21 Conduct bi-weekly deep dive of operations topics (e.g., tickets, interface metrics) meetings.
5.3.2.22 Conduct content reviews/walk-throughs, including “as-is” processes and “to-be” processes for all system and documentation changes.
5.3.3 Business Intelligence and Data Warehousing Support Tasks and Responsibilities. The objective of this subtask is to provide reporting capabilities and intuitive BI interfaces, which enables users to explore data without extensive training. Responsibilities include: data management, data warehousing, data marts management, and data deliveries. In performance of this TO, the Contractor shall provide and coordinate support with, which include:
5.3.3.1 Make efficient and effective use of current and future BI/Business Warehouse (BW) data architecture principals implementing a data warehouse that references and incorporates layered scalable architecture principals of SAP. This BI/BW data architecture should include layers containing differing levels of granularity.
5.3.3.2 Persistent staging area5.3.3.3 Data warehouse5.3.3.4 Architected data marts5.3.3.5 Operational data store5.3.3.6 Support the current BI/BW process chains and meta-chains.5.3.3.7 Automate the validation and ‘checkout’ process to ensure
data consistency, which is focused on process chains, data loads, and/or manual data loads.
5.3.3.8 Maintain the Navy ERP (SAP) financial dashboard (e.g. obligations rate, unliquidated obligations, and Intermediate Document (IDoc) errors).
5.3.3.9 Monitor and mitigate process chain collisions.5.3.3.10 Include performance testing and an assessment of cross-
component impacts (e.g., an ECC change which will degrade BI performance or cause data to be omitted from reports) for sustainment modifications and sustainment enhancements.
5.3.3.11 Develop, test and release solutions following Navy ERP (SAP)’s established management processes, checks, and plans for each software release.
5.3.3.12 Define and implement a rigorous technology assessment and planning process in order to address any gaps that Navy ERP (SAP) BI solution may have.
5.3.3.13 Provide BI training to end users, as required.5.3.3.14 Implement a standard security, metadata,
administration, portal integration, object model, and query engine.
5.3.3.15 Provide a robust way to search, capture, store, reuse, and publish metadata objects (e.g., dimensions, hierarchies, measures, and performance metrics) and report layout objects.
5.3.3.16 Maintain the SAP software developer’s kit for creating BI applications, integrating them into a business process, and/or embedding them in another application.
5.3.3.17 Assign and track events or tasks allotted to specific users, based on predefined business rules.
5.3.3.18 Provide the ETL of data and information from other Government (DoD and non-DoD) partners.
5.3.3.19 Develop BI processes necessary to affect Schemas and establish the logic, design, mapping, and transfer of data from sources.
5.3.3.20 Identify authoritative sources, issues and barriers to accessing data sources, and make recommendations on a governance structure, and establish methods for ensuring data quality.
5.3.3.21 Maintain an Information Lifecycle Management (ILM) Archiving Strategy that enables more complex criteria for storage management without replication.
5.3.3.22 Maintain Standard Operating Procedures (SOPs) for BI activities at all levels.
5.3.3.23 Maintain and develop the Federation between the multiple portals
5.3.3.24 Enhance the existing reporting functionality and suggest new capabilities / enhancements in an effort to improve performance, operation, etc…
5.3.3.25 Maintain Business Intelligence packages for the various Navy ERP (SAP)’s BI Portals and provide future capability to integrate with Fiori Launchpad.
5.3.3.26 Maintain the data warehouse that supports operative data analysis by means of the operational data store. This data should be updated to an operational data store on a continual basis or at short intervals and be available for read and for operative analysis including all the changes to the data.
5.3.3.27 Automate the data mart processes aligned with schemas, organize data into separate tiers according to specified policies, and automate data migration from one tier to another based on those criteria.
5.3.3.28 Conduct planning and analysis services, associated research, process development and implementation, and configuration of the BI application based on user requirement.
5.3.3.29 Establish mechanisms for queries; build queries; design and build dashboards and Cubes; and train users in the logic, processes, flows, and use of the system.
5.3.3.30 Provide a wide array of reporting styles (e.g., financial, operational, and performance dashboards).
5.3.3.31 Perform and report routine BI report utilization analysis to review the effectiveness of the current reports. A comparison of expected versus current shall be compared against report requirements and utilization requirements developed by the Contractor during report design requirements analysis.
5.3.4 Technical Management Support Tasks and Responsibilities. The objective of this subtask is to provide technical and functional system support in order to improve system performance and reduce operating costs. In performance of this TO, the Contractor shall provide and coordinate support with, which include:
5.3.4.1 Overall Technical Management Support5.3.4.1.1 Review Navy ERP (SAP)’s current state to
identify and recommend software/hardware enhancements, upgrades, and system optimizations to improve performance and reduce operating costs.
5.3.4.1.2 Research and analyze current and prospective hardware, software, Commercial Off-The-Shelf (COTS) tools, and applications for feasibility.
5.3.4.1.3 Perform root cause analyses and apply corrective actions for business processes.
5.3.4.1.4 Support technical and functional system enhancements, reporting, and conversions.
5.3.4.1.5 Provide direct assistance with software lifecycle improvements, including: configuration management, documentation management, data architecture, business processes management, functional / technical processes management, and training.
5.3.4.1.6 Support interface management processes, including: Interface Mapping Diagrams (e.g., SV-1, SV-6), Interface Control Agreements (ICAs), Memorandum of Agreements/Understanding (MOAs/MOUs), creation, migration, testing, validations, maintenance, data mappings, monitoring, and error resolution.
5.3.4.1.7 Provide direct assistance with BODS performance improvements, including: hardware, software, configuration, coding, and script writing.
5.3.4.2 RICE & Middleware5.3.4.2.1 Provide technical project summaries (TPS) for
system changes.5.3.4.2.2 Perform development testing of the
technical changes5.3.4.2.3 Create applicable Code and Configuration
which are efficient (do not contain unnecessary looping and/or internal data tables)
5.3.4.2.4 Monitoring and maintain integration and accurate data exchanges between ECC, BI, SCM, SRM, GRC, IDM, MDG, Gateway, and related Navy ERP (SAP) components.
5.3.4.2.5 Support and maintain system integration processes, activities, etc.
5.3.4.2.6 Abide by Navy ERP configuration, change, development, and release management processes
5.3.4.2.7 Analyze the impact of vendor-required or - recommended, SAP OSS notes, SAP patches, and NetWeaver plug-ins on NAVY ERP (SAP).
5.3.4.2.8 Implement and maintain Design Changes and Engineering Change Proposals (ECPs) to resolve, change, or improve technical and functional requirements.
5.3.4.2.9 Supporting system refreshes and upgrades for Navy ERP (SAP) and subcomponents to meet policy changes aligned with Navy, DoD, and SAP guidance.
5.3.4.2.10 Support roadmap to HANA, configuration, table verification and mapping, and cross-team coordination.
5.3.4.2.11 Support Attunity Gold Client Software or equivalent implementation and sustainment.
5.3.4.2.12 Providing support for all phases of master and transactional data lifecycles by following related policies/procedures, implementing appropriate technologies, frameworks, and utilities to ensure system continuity and stability.
5.3.4.2.13 Create related Technical Specifications (e.g. SOPs, Desk Guides, TDS, TFS, HLDs) which perform proper unit testing of technical changes
document technical design considerations / changes
5.3.4.3 User Management (UM)5.3.4.3.1 Provide User Access, User Access
Requirements (UAR), SAP Roles development, and SAP Roles Management including the use of SAP Governance, Risk and Compliance(GRC) suite, Identify Management (IDM), or an approved equivalent technical solution
5.3.4.3.2 Provide direct assistance with SAP User Provisioning, Role Maintenance and GRC user updates.
5.3.4.3.3 Maintain User Access Reports and Separation of Duties reports using SAP Access Violation Management/GRC
5.3.4.3.4 Ensure the Greenlight AVM tool maintains an operational posture regarding availability and accessibility
5.3.4.3.5 Maintain / Enhance / Create risks within the Greenlight AVM tool
5.3.4.3.6 Update User Management standard operating procedures and User Management documentations including policies and procedures
5.3.4.3.7 Write role test scripts for unit and regression testing
5.3.4.3.8 Support test events through creation of test IDs, collaboration with functional testing, and troubleshoot discrepancies during test events related to UM
5.3.4.3.9 Resolve UM related HEAT tickets. Resources are to follow current and approved HEAT Ticket Service Level Targets.
5.3.4.3.10 Work Access Enforcer requests for Tier 35.3.4.3.11 Respond to audit data calls such as running
User Access Reports and Separation of Duties reports
5.3.5 Data Management Processes and Support Tasks and Responsibilities. The objective of this subtask is to provide system support in data management to ensure system continuity and integrity. In performance of this TO, the Contractor shall provide and coordinate support with the following, which include:
5.3.5.1 Make efficient and effective use of current and prospective Navy ERP (SAP) Data Management principals and processes (e.g., Data Migration, Data Conversion, Data Maintenance, Data Governance, Data Analysis and Reporting, Data Distribution, and Data Archiving).
5.3.5.2 Perform and complete Data Management Life Cycle tasks
Creation/Development, Validation, Testing, Implementation, and Post-Production Support, as defined by the Government Lead, including:
5.3.5.2.1 Navy ERP (SAP) functional and technical teams’, Enterprise Business Offices’ (EBO), external customers ‘requests, and various work requests approved by Navy ERP Governance Board including:□ Service Requests (RSC tickets)□ Data Management Production Incident
Tickets (Defects, Break/Fixes, and IDOC Reprocessing)
□ Data Service and Data Maintenance Requests (DSR), DM Tickets, Quality Center Incidents (QCIs)
□ Data Conversions, Data Loads, Data Distributions, and Data Migration Requests
□ Data Mapping and Data Validation□ Data Reports and Data Extracts using
Business Objects Data (BODS), Business Warehouse (BW), and Crystal Reports, etc
5.3.5.2.2 Error identification, root cause analysis, troubleshooting, and resolution
5.3.5.2.3 Trend analysis, metrics, statistics, and reports including:□ Table Validations□ Data Warehousing/BW□ Data Management Maintenance□ Error resolution□ BODS□ RSC Tickets (SLTs, Aging, Discrepancies,
SOP Compliance)5.3.5.2.4 Data Reconciliation5.3.5.2.5 Data Extracts and Reports involving
BODS/BW development, execution, and maintenance
5.3.5.2.6 Data Refreshes5.3.5.2.7 Attunity Gold Client Software or equivalent
implementation5.3.5.2.8 Technical upgrades5.3.5.2.9 Data Archiving5.3.5.2.10 Data Integrity and Quality Control via SAP
Master Data Governance (MDG) application, or similar application
5.3.5.2.11 Data Management Training Materials, as requested by the Government Lead(s)
5.3.5.2.12 Development, revision, and maintenance of
Standard Operating Procedures (SOPs) and related documentation for Data Management activities at all levels.
5.3.5.2.13 Research, development, documentation, and implementation in support of new capabilities as defined by the Government Lead and Tier III Leadership
5.3.5.2.14 Content reviews/walk-throughs, including to “as-is” processes and “to-be” processes for all system and documentation changes
5.3.6 Interface Management Processes and Support Tasks and Responsibilities. The objective of this subtask is to provide system support in interface management to ensure completeness and accuracy of data exchanges throughout the enterprise. In performance of this TO, the Contractor shall provide and coordinate support with, which include:
5.3.6.1 Make efficient and effective use of current and prospective Navy ERP (SAP) Interface Management principals, policies (e.g., Government and commercial), procedures, and processes to ensure completeness, accuracy, and auditability of data exchanges
5.3.6.2 Perform and support the Interface life cycle and various work requests approved by Navy ERP Governance Board, as defined by the Government Lead, including: Project Preparation, Business Process Blueprinting, Realization, Final Preparation, Go-Live, Stabilization, Monitoring, and Continual Evaluation
5.3.6.2.1 Provide direct assistance within the Business process requirements gathering process
5.3.6.2.2 Create, maintain, and recommend changes for Interface Control Agreements (ICAs) and Memorandum Of Agreements (MOAs/MOUs)
5.3.6.2.3 Coordinate interface functional/technical requirements development process with partners and Navy ERP (SAP) functional/technical teams
5.3.6.2.4 Provide direct assistance within the functional and technical design processes.
5.3.6.2.5 Create, maintain, and recommend changes for process diagrams, flowcharts, workshops, and walk-throughs with partners and Navy ERP (SAP) functional teams throughout the business process blueprinting.
5.3.6.2.6 Coordinate development, configuration, and establishment of interface design and connectivity; including, mapping and transfer of data from sources.
5.3.6.2.7 Provide direct assistance with/perform interface cycle testing, scheduling, migration, and user training; including, validations and coordination with Government (DoD and non-DoD)
partners.5.3.6.2.8 Provide direct assistance with/develop
Transition and Integration Plan for new interfaces in the Production Environment.
5.3.6.2.9 Provide direct assistance with scheduling and validating the interface, establishing baseline including frequencies and Transfer Protocols.
5.3.6.2.10 Provide direct assistance with Navy ERP (SAP) interface monitoring, error resolution, error logs,reporting, root cause and trend analysis, and notifications,
5.3.6.2.11 Provide direct assistance with Service Desk Production incident ticket resolution (e.g., error identification, troubleshooting, and providing notifications to RSC, Functional/Technical teams, and Customers)
5.3.6.2.12 Provide direct assistance with automation of monitoring, reporting, and notifications processes.
5.3.6.2.13 Provide direct assistance with job processing for potential changes or enhancements, including recommendations for improvements to Interface Management processes.
5.3.6.3 Provide direct assistance with various Audit and Compliance requirements (i.e. SFIS compliance, DLMS compliance, JITC)
5.3.6.4 Provide direct assistance with Reconciliation processes for Navy ERP (SAP) interfaces.
5.3.6.5 Provide direct assistance with Audit support.5.3.6.6 Provide direct assistance with documentation creation,
revision, and updates throughout the interface life cycle (e.g., SOPs, error logs, JSRs, FRDSs, etc)
5.3.6.7 Provide direct assistance with reviewing interface performance and stability; including providing feedback for adjustments and optimization.
5.3.6.8 Create and maintain Interface Management Training materials.5.3.6.9 Research, develop, document, and implement new
capabilities5.3.6.10 Conduct content reviews/walk-throughs, including “as-
is” processes and “to-be” processes for all system and documentation changes
5.3.7 Training Processes and Support Tasks and Responsibilities. The objective of this subtask is to provide training governance strategy, training solution modernization, and training content creation for Navy ERP (SAP) enterprise training systems. In performance of this TO, the Contractor shall provide and coordinate support with, which include:
5.3.7.1 Provide the enterprise training governance strategy.5.3.7.2 Provide the enterprise training solution modernization
using commercial and Government best practices and approaches.
5.3.7.3 Support the training lifecycle in different environments, including: Ancile uPerform, SAP Enable Now and SAP LSO.
5.3.7.4 Provide the creation of training content for new functionality and updating existing course content based on changes in business processes.
5.3.7.5 Provide the publication of training content.
5.3.7.6 Provide the SAP authoring of training content.
5.4 Program of Record (POR) Enhancements. In addition to following section 5.1, the objective of this task is to enhance the capabilities of Navy ERP (SAP) to ensure continued alignment, improvement, and standardization of end-to-end business processes, compliance, and optimization. Specifically, during daily operation of the following activities, the end result could yield in an enhancement to the N-ERP solution in order for the team to operate /support the Customer effectively and efficiently: HEAT break/fix analysis, Emergency Work Request (EWR), Production incident, Audit (NFR, PBC, FISCAM). Following is the estimated annual level of effort for each of the aforementioned activity based on historical data:□ HEAT break/fix analysis: 20,000 hours□ EWR planned work: 5,600 hours□ Production incidents: 10,000 hours□ Audit: 41,000 hours
5.4.1 Navy ERP (SAP) POR Enhancement Services and Processes. The following POR Enhancement services and processes include:
5.4.1.1 Enhancements for Data Management Processes: Data Maintenance, Governance, Data Quality, Architecture, Modelling and MetaData, Data Services, Analysis, Reporting, Migration, Distribution, and Data Archiving.
5.4.1.2 Enhancements for Interface Management Processes5.4.1.3 Enhancements for Custom Code Analysis and Business
Process Optimization5.4.1.4 Enhancements for Training Processes5.4.1.5 Enhancements for Supply Processes5.4.1.6 Supply Master Data5.4.1.7 Order Fulfillment5.4.1.8 Allowancing5.4.1.9 Procurement/Material Management Inventory Management5.4.1.10 Warehouse Management5.4.1.11 Supply Chain Management (Planning)5.4.1.12 Enhancements for Financial Processes5.4.1.13 Funds Management5.4.1.14 Controlling5.4.1.15 Sales and Distribution5.4.1.16 Grants/Finance5.4.1.17 Project Systems5.4.1.18 Asset Management5.4.1.19 Workforce Management5.4.1.20 Enhancements for Technical Processes (RICE,
Middleware, & etc.)5.4.1.21 Enhancements for Audit and Compliance Processes5.4.1.22 Cost Estimation
5.4.1.23 Integrated Master Schedule updates5.4.1.24 Other enhancements may include capability
releases. Examples are below:5.4.1.24.1 Emergency Work Requests (EWRs)5.4.1.24.2 Complex contracting5.4.1.24.3 Financial Logistics Integrated
Requirements Report (FLIRR)5.4.1.24.4 Demand Requirements Planning (DRP)5.4.1.24.5 Forecasting5.4.1.24.6 Automatic Identification Technology (AIT)5.4.1.24.7 Automated testing5.4.1.24.8 Supply & Financial Billing5.4.1.24.9 Naval Aviation Logistics Command
Management Information System (NALCOMIS)
5.4.1.24.10 Mobile computing5.4.1.24.11 Carcass Tracking5.4.1.24.12 Purchase Requisition / Purchase Order5.4.1.24.13Integrated Technical Item Management &
Procurement (ITIMP)5.4.1.24.14Invoicing, Receiving, Acceptance, and Property
Transfer (iRAPT) formerly known as WideArea Work Flow (WAWF)
5.4.1.24.15 Ledger postings5.4.1.24.16 Archiving5.4.1.24.17Standard Financial Information Structure
(SFIS)5.4.1.24.18 Outfitting/Allowancing
5.4.2 Navy ERP (SAP) POR Enhancement Tasks and Responsibilities. In performance of this TO, the Contractor shall provide and coordinate support with, which include:
5.4.2.1 Follow Navy ERP (SAP)’s established standards and procedures throughout each stage of the software development lifecycle enhancement.
5.4.2.2 Where applicable, follow the requirements detailed within Section 5.1.3 as such POR requirements are also applicable to POR enhancement tasks and responsibilities.
5.4.2.3 Work closely with the applicable Government Team Lead(s)/Team(s) to ensure all aspects of POR enhancement work are clearly communicated and agreed upon prior to solution implementation.
5.4.2.4 Work with the applicable teams to ensure cross-integration is satisfactory for all enhancements and changes being implemented across the Navy ERP (SAP) enterprise.
5.4.2.5 Ensure that conflicts between various development objects are addressed timely, and that the POR teams can sustain the various new enhancements/functionalities being introduced by other team(s).
5.4.2.6 Create and maintain enhancement documentation for Navy ERP (SAP) processes, desk guides, and report procedures, etc.
5.4.2.7 Provide assistance with enhancement of software lifecycle throughout the enterprise (Plan, Analyze, Design, Build, Test in all environments, Deployment, and Post-Production Support services).
5.4.2.8 Provide estimates and level of complexity for each enhancement/capability as requested by the Government.
5.4.2.9 Provide direct assistance with POR enhancements, which require changes to hardware, software, licenses, installation, and/or services.
5.4.2.10 Provide direct assistance with upgrades to support the maturation of infrastructure and business processes across Navy ERP (SAP), including: Infrastructures, Operating Systems, Databases, and Application Version Upgrades.
5.4.2.11 Assist with enhancements related to business process efficiencies, interoperability, data accuracy, and system performance, stabilization, and availability.
5.4.2.12 Provide direct assistance with completion of remaining work on deployed functionality, and resolving limitations in infrastructure.
5.4.2.13 Support infrastructure modernization to address additional users, system scalability, technology refreshes, prevailing industry standards, and emerging technologies.
5.4.2.14 Provide direct assistance with seamless integration across Navy ERP (SAP) components and teams to maximize success of each implementation.
5.4.2.15 Provide direct assistance with capacity planning model implementation and execution.
5.4.2.16 Provide direct assistance with incorporating enhancements into the POR Release Schedule, utilizing standard Government software tools.
5.4.2.17 Provide direct assistance with system updates to meet changes in compliance requirements, audit readiness compliance and assurance, business enterprise architecture compliance, and other enterprise standards compliance.
5.4.2.18 Provide direct assistance with enhancement of access capabilities.
5.4.2.19 Provide direct assistance with automation of manual business processes.
5.4.2.20 Provide direct assistance with automation of report capabilities.
5.5 Technical Operations. This task along with associated deliverables will be executed as an independent option. The objective of this task is to execute the areas of technical operations sustainment, Engineering Change Proposal (ECP) support,and special projects support.
5.5.1 General System Operation . The Contractor shall:5.5.1.1 Provide services in support of general operations activities
necessary for the daily batch and online operations of the Navy ERP (SAP) solution and related components. The key activities are centered on the submission and execution of the batch workload.
5.5.1.2 Provide these services in support of activities related to interface jobs as well as typical batch jobs or work within the SAP system.
5.5.1.3 Provide daily operations as follows:5.5.1.3.1 Develop appropriate procedures and
measurements to ensure the quality, efficiency, and timeliness of the overall release process (e.g., software configuration management and version control)
5.5.1.3.2 Apply continuous process improvement techniques and update procedures to ensure they evolve with changing requirements, technological innovations and industry best practices
5.5.1.3.3 Coordinate and work with other teams, organizations, or functions as appropriate to build, maintain, monitor, resolve issues, and operate the Navy ERP systems and components
5.5.1.3.4 Provide the required information and participate in mandatory Systems Engineering reviews as they occur
5.5.1.3.5 Follow and comply with prescribed incident reporting techniques, tasks, and tools
5.5.1.3.6 Maintain 24 x 7 coverage, as appropriate in order to maintain Navy-ERP performance objectives and to respond to critical situations or system failures
5.5.1.3.7 Provide and execute typical and appropriate project management techniques and work products for the coordination, direction, and statusing of work as necessary
5.5.1.3.8 Explain, familiarize, and educate government personnel on any related technology, process, standard, technique, approach, or tool utilized
within the context of this agreement and for delivery of indicated services
5.5.1.3.9 Assist the government to achieve high continuity, availability, efficiency, integrity, and performance of system related technical, operational, and programmatic components and processes
5.5.1.3.10 Appropriately test all system changes in accordance with Navy ERP, DoN, and DoD policy and standards, and leading industry practices
5.5.1.3.11 Provide performance metrics as required5.5.2 Batch Job Operations. The Contractor shall provide services in support
of maintaining and executing the Navy ERP system’s batch jobs via the job scheduling tool.
5.5.2.1 Configure in TIVOLI or comparable job scheduling tool [in accordance with Job Scheduling Requests (JSR)] new jobs to be executed on the requested schedule with the required inter- job dependencies
5.5.2.2 Work with requesters to enable more accurate and complete JSRs
5.5.2.3 In accordance with JSR complete changes to existing jobs or various parameters guiding the execution of jobs
5.5.2.4 Maintain an effective batch jobs “run book” documenting the appropriate operations of the batch environment
5.5.2.5 Execute appropriate tests for additions or changes to the schedule
5.5.2.6 Execute and monitor the daily jobs (Production and non- production) across the Navy ERP environments on a 24x7 schedule
5.5.2.7 Coordinate the appropriate response, mitigation, or responses and contact the appropriate program stakeholders to address changes to the normal operating status or to resolve issues or errors with the batch schedule or other system issues during off-shifts
5.5.2.8 Assess the impact of external forces (e.g., hardware or application failure, tele-communications (TCOMMS) failures, planned outages, requests, etc.) on the batch schedule and initiate the appropriate job schedule changes
5.5.2.9 Perform other system related actions as may be defined in the JSRs
5.5.3 Operations Coordination. The Contractor shall provide services in support of the daily coordination of all operations activities including dynamic changes and additions to the overall operating schedule.
5.5.3.1 Coordinate, respond, adjust, remediate, and communicate to appropriate stakeholders with respect to ongoing daily changes
to the tempo, configuration, and schedule of daily operations for the production and non-production Navy ERP technical system components
5.5.3.2 Prepare and deliver communications related to immediate operational issues, changes, and anomalies; coordinate communications of non-immediate issues and changes to appropriate stakeholders as may be required.
5.5.3.3 Communicate and coordinate Navy ERP operations with external service providers (e.g., data center, Navy/Marine Corps Intranet (NMCI), Help Desk, etc.) as appropriate.
5.5.3.4 When requested, provide special initiative or project coordination and oversight leadership (e.g., “war room facilitation and oversight”)
5.5.4 Release Management. The Contractor shall provide services in support of production release management (e.g., software configuration management and version control) to include those activities necessary for managing and executing the systematic planning, packaging, scheduling, and release of software, technical, business, data, and access changes to the Navy ERP SAP production and non-production environments.
5.5.4.1 Manage systematic process (e.g. planning, scheduling, packaging and releasing) to the production and non-production environments; review, analyze, and document release failures and monitor corrective actions where required
5.5.4.2 Analyze the appropriate task tracking tool, such as Hewlett Packard (HP) Quality Center (QC) tool items to ensure proper coordination of production scheduling requirements with the Project Management team.
5.5.4.3 Monitor release processes to recommend improvements5.5.4.4 Monitor planned work and release items to ensure
appropriate quality and completeness prior to preparation for production release
5.5.4.5 Support Release Manager Working Group (RMWG) as required to obtain alignment on release dependencies
5.5.4.6 Support and lead Technical Change Control Board (TCCB) meetings in order to provide a controlled method of documenting and approving the movement of changes (transports), action items and maintenance activities to be conducted in the Quality and Production environments
5.5.4.7 Develop TCCB minutes and distribute5.5.4.8 Prepare, assemble, and distribute pre and post Release
Notes prior to each scheduled release5.5.4.9 Coordinate software releases to ensure successful technical
changes to the SAP ERP production environment5.5.5 Transport Management . The Contractor shall provide services in
support of technical control and execution of changes in the Navy ERP SAP production and non-production environments.
5.5.5.1 Create Change Documents as requested by the Reports, Interfaces, Conversions and Enhancements (RICE) and Functional Teams or as a result of Request for Change (RFC) approvals as required
5.5.5.2 Create Transports as approved and requested by Government Functional Team Lead as required
5.5.5.3 Move Transports throughout the Navy ERP Landscapes and into production upon approval
5.5.5.4 Maintain Approved Production Transport tracking spreadsheet5.5.5.5 Ensure review of any Middleware packages and updates by
the RICE team to ensure proper version is identified prior to import. (Middleware changes are imported by the BASIS team.)
5.5.5.6 Maintain Maintenance Cycles5.5.5.6.1 Monitor Task List to clear any errors generated5.5.5.6.2 Ensure all Change Documents are assigned
to the correct Project and have require fields populated
5.5.5.6.3 Move Change documents to correct project5.5.5.6.4 Update Change Documents to reflect
correct status5.5.5.7 Update task tracking system to reflect current status in
regards to the transport and/or testing5.5.5.8 Conduct transport tool training for any new users5.5.5.9 Perform necessary tasks to support the upgrade of the
transport management tool5.5.6 Regression Testing and Quality Assurance. The Contractor shall provide
services in support of those activities necessary to ensure the quality, correctness, and efficiency of changes to the SAP solution, as well as the adherence to defined system engineering process and standards, and Navy ERP Program documentation standards.
5.5.6.1 The Contractor shall manage/coordinate regression testing activities for regression test events (major releases, scheduled releases, and non-scheduled releases)
5.5.6.2 The Contractor shall provide quality reviews of technical packages (e.g., documentation) and cross-system entries to ensure accuracy across program tools for changes to the Navy ERP solution.
5.5.6.3 Execute Critical Business Process Test manual and automated test sets (Regression)
5.5.6.4 Execute manual functional change tests5.5.6.5 Develop scripts and maintain automated test sets5.5.6.6 Review test plans for impact to critical business processes5.5.6.7 Validate that the functional test plans prove out the
requirements for the change and are adequate to test the change during a regression event
5.5.6.8 Document and provide test event metrics5.5.6.9 Create, update, and maintain documentation (Test strategy,
Standard Operating Procedures (SoPs), Processes, Policies, etc.)
5.5.6.10 Support and participate in various decision boards in the change management process
5.5.6.11 Support and enforce Navy ERP processes and changes5.5.6.12 Perform high level qualitative review of configuration
items5.5.6.13 Manage Technical Data Package (TDP)5.5.6.14 Assist functional resources to ensure their documentation
is complete and all other requirements are met to enter the test event
5.5.6.15 Build and maintain file structure for test plans in appropriate test tracking/management tool (e.g. HP QC)
5.5.6.16 Perform ad hoc and audit validations of configuration items, (ex TDP items, Business Process Master List (BPML), Role Matrix, Supply Data Management (SDM))
5.5.6.17 Maintain supporting test documentation/results5.5.6.18 Provide traceability from the high level requirements of
Capability Production Document (CPD) down to the artifact that satisfies the requirement (test cases or documentation)
5.5.7 Technical Infrastructure Architecture. The Contractor shall provide services in support of technical infrastructure architecture activities necessary for the effective technical design, build, configuration, operation, monitoring, issue diagnosis and issue resolution of the Navy ERP systems and infrastructure components located at Patuxent River, Maryland (primary data center) and China Lake, California (secondary backup data center). It is anticipated that the contractor shall be required to perform this work on-site at the Patuxent River data center occasionally and onsite at the China Lake data center rarely.
5.5.7.1 The data centers provide the actual services related to the provisioning, positioning, powering, configuration, and technical administration of storage, processor, and network components for Navy ERP under the general architectural-level oversight of the Navy ERP team members providing servicesin this PWS.
5.5.7.2 Manage the technical infrastructure architecture (e.g., hardware& system software, network and data infrastructure components) ensuring ongoing appropriate levels of performance, throughput, and availability in accordance with prescribed levels described in the CPD
5.5.7.3 Ensure that architecture complies with evolving policy and guidance issues by DoD and the DoN CIO;
5.5.7.4 Complete the necessary capacity planning activities to ensure the availability of infrastructure to support the Navy ERP software system as its workload changes over time
5.5.7.5 Diagnose and mitigate or correct technical issues that adversely impact the availability, throughput or performance of the production or non-production systems
5.5.7.6 Maintain a strategic technology plan and update yearly (A Technology and Tech Refresh Strategy with 3 & 5 year forward looking views shall be updated annually.)
5.5.7.7 Develop a yearly technology refresh plan including a detailed deployment plan for new and modified components (A Technology Refresh schedule and a Technology Refresh Detailed Plan shall be provided annually)
5.5.7.8 Maintain and regularly reconfirm the effectiveness of all technology and processes to ensure the logical and physical integrity of the system (System integrity assurance, backup, and recovery strategy shall be updated annually.)
5.5.7.9 Work with the government team to install/configure the required hardware components, software components, and applicable licenses
5.5.7.10 Manage the versions of all components to ensure that all components are near to current release levels and are covered by standard Original Equipment Manufacturer (OEM) vendor maintenance programs or services
5.5.7.11 Develop and review appropriate System Change or Outage Requests (SCOR) requests for infrastructure changes to be made by data center and NERP BASIS personnel
5.5.7.12 Maintain close coordination and high levels of communications with the data center support teams per NAVSUP BSC leadership direction
5.5.7.13 Work with the NAVSUP BSC Interface Control team to manage all technical aspects of Navy ERP interface processes and changes
5.5.7.14 Work with the appropriate Cyber Security team members, monitor the compliance of all cyber security requirements with respect to the technical components and operation of the Navy ERP system to ensure components meet STIG/IAVA compliance
5.5.7.15 Participate in recurring technical assessments, audits and reviews (e.g., SAP Technology Assessments)
5.5.7.16 Conduct hardware and software market research evaluations and prepare specific recommendations
5.5.7.17 Manage all DoD related repository requirements related to software, hardware and technical standards to include, but not limited to; DoN Application and Database Management System (DADMS), DoD IT Portfolio Repository (DITPR)-
DON, Navy Information Dominance Approval System (NAV- IDAS), DoD Architecture Framework (DODAF), etc.
5.5.7.18 Provide data assurance and data integrity through definition of backup policy and the use of up-to-date backup technologies
5.5.7.19 Update disaster recovery test plans and execution plans and conduct periodic disaster recovery testing and exercises (A Disaster Failover Test and Exercise coming year Plan & Schedule Disaster Failover Test and Exercise Detailed Work Plans and Disaster Failover Test and Exercise After Action Report shall be submitted per project schedule.)
5.5.7.20 Document infrastructure and data center requirements, and plan for data center consolidation at both the PAX River and China Lake sites if necessary
5.5.7.21 Assist in troubleshooting issues with Navy ERP systems, document failures and outages in accordance with the failure reporting and corrective action system
5.5.7.22 Document issues, facilitate, and conduct monthly failure review boards; Failure Review & Analysis Corrective Action System (FRACAS)
5.5.7.23 Monitor system performance to forecast/anticipate performance bottlenecks and work with NAVSUP BSC teams to resolve up on discovery
5.5.7.24 Recommend technology changes to improve system performance
5.5.7.25 Provide performance metrics as required5.5.7.26 Respond as appropriate to relevant data calls with respect
to system components, configuration, effectiveness, licensing, or operations
5.5.8 SAP BASIS Technical Administration . The Contractor shall provide services in support of SAP BASIS technical administration activities necessary for the effective technical design, build, configuration, operation, and issue diagnosis of the Navy ERP SAP systems and components. SAP Roles Security Administration for the systems as a whole is NOT included in this effort. The contractor shall:
5.5.8.1 Execute the analysis, design, build and configuration activities necessary for the initial build and periodic refresh of all components for the SAP environments (e.g., clients, instances, data files, etc.)
5.5.8.2 Perform performance, sizing, capacity, and throughput monitoring of the Navy ERP non-Production systems
5.5.8.3 Ensure that adequate backup and recovery processes are available and operational in order to maintain the integrity of all systems in the event of system or component failure
5.5.8.4 Execute database administration and Database Management System (DBMS) administration support for the Oracle DBMS
and SAP MAX DB systems and databases including the building, monitoring, and tuning of databases to support the SAP solution
5.5.8.5 Maintain and monitor Navy ERP printer tables and other SAP configuration tables as needed
5.5.8.6 Work closely with and support other Navy ERP stakeholders (e.g., RICE, Functional Teams, Testers, Roles Security, etc.) as needed to solve functional, data, access, or other technical issues with the production and non-production systems
5.5.8.7 Capture and provide the appropriate system data to respond to data calls or the measurement of performance metrics
5.5.9 Program Tool Technical Administration . The Navy ERP Program utilizes and relies on a variety of technical tools to enable effective business and technical processes and information. The Contractor shall provide services in support of the technical administration activities required to install, configure and maintain (e.g., administer) the tools based on business, technical, standardization, and process requirements identified by other functions within the Navy ERP program or user base.
5.5.9.1 Execute the technical analysis, design, build and configuration activities necessary for the initial build and periodic refresh of all Program tools
5.5.9.2 Provide ongoing assessment of the readiness of the tools (e.g., capacity planning, performance monitoring, etc.)
5.5.9.3 Assess and report licensing requirements and compliance of the tools
5.5.9.4 Provide assessment and diagnosis of the tools in the event of issues or processing anomalies
5.5.9.5 Coordinate and work with OEM and data center personnel to diagnose and correct technical issues with the tools
5.5.9.6 Ensure ongoing backup capabilities to ensure minimal disruption in the event of tool failure
5.5.9.7 Conduct assessments and market research in order to provide ongoing information to enable the program to assess the effective capability of currently owned or tools being considered
5.5.10 Cyber Security. Cyber Security includes tasks which the contractor shall provide in order to protect and defend information and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-repudiation. This includes providing for restoration of information systems by incorporating protection, detection, and reaction capabilities.
5.5.10.1 The Contractor shall provide services in support of activities necessary to ensure the Navy ERP solution and all components (software and hardware) are designed, configured, and maintained in accordance with all applicable DoD and Navy requirements, protocols, standard, policy, etc.
5.5.10.2 The Contractor shall also provide services in support of the identification, planning, coordination and facilitation of all certification activities. The Contractor shall ensure that the Navy ERP Authorization to Operate (ATO) remains intact as well as meets the DoD Risk Management Framework information systems security criteria.
5.6 Task Order Support. The objective of this task is to provide management and support to NAVSUP BSC 98 to ensure compliance and seamless task order transition.
5.6.1 Configuration Management (CM) Compliance. In performance of this TO, the Contractor shall:
5.6.1.1 Adhere to Navy ERP (SAP)’s established CM processes. CM is the process that integrates the technical and administrative actions of identifying the functional, performance, and physical characteristics of a Configuration Item (CI) and controls the changes to those characteristics. CIs are monitored and tracked throughout their component lifecycle. CM covers identifying, controlling, maintaining, and verifying CIs, including their versions, constituent components and relationships.
5.6.1.2 Manage configuration information and system baseline artifacts to document the changes to all the landscapes as they are updated over time.
5.6.1.3 Populate the Government repository with all documentation related to the landscape configuration and system baseline artifacts as they are updated over time.
5.6.1.4 Employ automated processes to load and update the CMDB so as to reduce errors and reduce costs. Use Government Furnished Equipment (GFE) software and recommend other software to populate CMDB such as Discovery tool which provides inventory and audit, enterprise systems and network management. These shall interface with the CMDB, be used to update the CMDB, and subsequently compare the actual 'live' configuration with the records stored in the CMDB.
5.6.1.5 Collect, review, track, and archive Configuration Control documents.
5.6.1.6 Ensure configuration and design documentations are updated before any changes, upgrades, and/or POR enhancements are implemented.
5.6.1.7 Manage releases and updates to the production environment.5.6.1.8 Manage any changes to the baseline project plan or committed
maintenance or POR enhancement dates in accordance with the Navy ERP (SAP) CMP.
5.6.1.9 Coordinate and execute a Change Request (CR) impact assessment for all system changes and provide written advice and recommendations regarding the impact of changes to the originators of the CR. This includes coordination with the
Government assigned team and the Government Configuration Control Board (CCB) Manager.
5.6.1.10 Complete system software, hardware or change documentation change request (in a Navy ERP (SAP) approved template, including project plans and timelines) for eachchange and participate in review and discussions as a part of the appropriate Navy ERP (SAP) identified change review body.
5.6.1.11 Administer the flow of system software, hardware, and change documentation between the various change review and control bodies, change requestors, and other participants in the change review and control processes. This includes administering the flow of requests (1) rejected, (2) deferred, (3) returned for more information, (4) approved, and (5) approved with conditions.
5.6.2 Resource Management Tasks and Responsibility. Tasks and Responsibilities include the following. The Contractor shall:
5.6.2.1 Provide the requisite number of technically qualified, technically accredited staff who have the depth and breadth of experience, expertise, and skills necessary to perform the tasks.
5.6.2.2 Plan, schedule, and coordinate resources in regards to schedules and attendance, on-boarding and orientation,training, badging, Common Access Card (CAC) access, system access and use, and out-processing.
5.6.2.3 Ensure vacancies are filled with technically qualified, accredited (as required by the position), and skilled personnel.
5.6.2.4 Provide facility assistance in escorting and sign-in of personnel not badged.
5.6.2.5 Provide management and oversight of Contractor personnel, sub-contractors, and consultants under the control of the Contractor.
5.6.2.6 Use resources (e.g., information, technologies, equipment, financial, and labor) in the most efficient way possible to contribute directly to accomplishing Navy ERP (SAP) objectives.
5.6.2.7 Responsible for tracking and reporting: initial and ongoing training of employees of annual Information Assurance (IA) or specialized training , manpower reporting, and Small Business Subcontractor reporting.
5.6.2.8 Be proactive in establishing and maintaining operational guides that document the Navy ERP (SAP) organization, responsibilities, and processes that can be used to train resources, transfer knowledge, and create the basis for knowledge management.
5.6.2.9 Replace, modify and/or add staffing resources as needed in a timely, professional and consistent manner.
5.6.3 Mentoring and Knowledge Transfer Services Tasks and Responsibility. Tasks and Responsibilities include to the following. The Contractor shall:
5.6.3.1 Assist with the three types of knowledge transfer services5.6.3.1.1 Explicit: Step-by-step transfer of process,
procedures, design methodology, and other support documentation
5.6.3.1.2 Tacit: Observable knowledge through one-on- one training
5.6.3.1.3 Capture: Definition of a “to-be” process and procedure.
5.6.3.2 Assist with mentoring subject matter experts in knowledge transfer workshops, interviews and other information exchange forums.
5.6.3.3 Assist with the knowledge capture services that shall be provided with extracting and recording knowledge from other subject matter experts, stakeholders, customers, and decision maker sources.
5.6.3.4 Provide ongoing knowledge transfer from Contractors to Government as work is being performed using any one or combination of the three types of knowledge transfer services identified above (i.e. one-on-one mentoring, group training, training documentation (SOPs, Desk Guides, Reference Sheets), etc).
5.6.3.5 Assist with knowledge and skill gaps identification processes within the teams.
5.6.3.6 Assist Government personnel throughout the software development process to facilitate knowledge transfer in Planning, Analyzing, Designing, Building, Testing, Deployment, and Post-Deployment Production support, to include receiving government leads’ approval on various deliverables.
5.6.3.7 Assist with knowledge transfer in Business Process Procedures (BPPs) as it applies to updating training course content.
5.6.4 Transition Support.5.6.4.1 Transition: Phase-In. The objective of this task is to receive
knowledge transfer requirements and services from off- boarding Contractor personnel, as required. The Contractor shall:
5.6.4.1.1 Participate in Transition Phase-in tasks to orderly and efficiently receive knowledge
transfer from the off-boarding Contractor, coordinated by the government.
5.6.4.1.2 The Transition Phase-in shall be considered the first thirty (30) days prior to the contract performance period.
5.6.4.1.3 The Onboarding/Transition Phase-in Plan shall consist of a timeline for support personnel, transitioning actions, and sufficient detail to ensure that no break in services is experienced. Onboarding Contractor leads provide Onboarding Plan to the government leads.
5.6.4.1.4 Conduct a kick-off meeting with the government to review, negotiate, and approve onboarding plan to include staffing requirements and allocation
5.6.4.1.5 Meet with incumbent vendor and the government to garner completed and work-in- progress tasks, challenges, etc… to prepare and present a transition-in plan to the government for review, negotiation, and approval. The transition-in plan shall detail how the new vendor plans to satisfactorily deliver the requirements set forth on this task order.
5.6.4.2 Transition: Phase-Out5.6.4.2.1 Participate in Transition Phase-Out tasks to
orderly and efficiently provide knowledge transfer to the Onboarding Contractor personnel, coordinated by the government.
5.6.4.2.2 The Transition Phase-Out shall be at least 30 days prior the end of the period of performance.
5.6.4.2.3 Minimum 15 business days notification for each contractor resource that is off-boarding during the period of the task order.
5.6.4.2.4 The contractor shall provide a designated point of contact, and provide advice, knowledge transfer and support in the timeline and transition plans of government data, functions and services to the new awardee and government team(s).
5.6.4.2.5 Meet with the government 30 days prior to the end of the period of performance to review, negotiate, and approve the transition-out plan. The transition-out plan shall detail how the incumbent vendor will transition knowledge of
completed and work-in-progress tasks to the new vendor and the government.
5.7 Cost-Plus Requirements. In addition to following section 5.1, the contractor shall:5.7.1 Assessment. The objective of this subtask is to assess prioritized work
items to provide Rough Order of Magnitude (ROM) and/or Preliminary Cost Estimates (PCE) for scope of work:
5.7.1.1 Work with the Navy ERP Tier III government team to establish an approved and ranked list of workload items and business requirement changes with supporting Functional Requirement Design Specifications (FRDS) documents with content to support the necessary functional changes, update the NavyERP Quality Center Database with the appropriate defect/design tracking item, have desired changes vetted by Government Tier III Supply and Finance Process Owners of impacted business areas for Business Process impact and desirability (no negative impact).
5.7.1.2 Participate in estimates of work hours for each software development life cycle phase to meet required timeframe including effort/hours, complexity, RICEFW impacts, Cross Process/External Partner impacts, and required skillset
5.7.1.3 Participate in assessment of Business Functionality change across standard SAP modules and custom RICEFW modules for overall level of effort and rough ECD (based on identified changes)
5.7.1.4 Provide the Process Owners with potential functional bucket efficiencies (similar functional process areas or similar RICEFW dependencies or external partner impacts) that may help streamline the Plan/Analyze/Design/Build/Test and Deploy phases
5.7.1.5 Provide assessment of Standard SAP ERP functionality with requested stakeholder change, assessing the impact to the Sustainment tail to enable the government (TierIII) to make a decision on the best course of action.
5.7.2 Develop Functional Requirement Documentation and comply with the NAVSUP BSC Tier III FRDS processes.
5.7.3 Provide the Government with estimated completion dates based on team capacity bandwidth and based on prioritization for each software development life cycle phase to meet deadline for completion of the WBS
5.7.4 Meet estimated completion dates for each assigned WBS task unless special circumstances approved by the TA permit missing the completion date.
5.7.5 Follow and comply with NAVSUP BSC Tier III current Release Management Processes
5.7.6 Create related Technical Specifications (e.g. TDS, TFS, HLDs) which:5.6.6.1.1 Perform proper unit testing of technical changes
5.6.6.1.2 Document technical design considerations / changes
5.6.7 Create/Update related Test Plans and comply with the NAVSUP BSC Tier III Test Plan processes.
5.6.8 Execute Test Plans. Execute applicable Test Plans & Test Cases (Unit, System, Functional, Interface, Regression, Performance, Integration and/or Interoperability) and comply with the NAVSUP BSC Tier III Test Plan processes.
5.6.9 Prepare New/Revised Software Modules for Production Environment Migration and comply with the NAVSUP BSC Tier III Test Plan processes.
5.6.10 Provide Post-Production Support and comply with NAVSUP BSC Tier III Post-production support processes.
6.1 Transition: Int eg rat io n of the Pha se- In and Pha se- Out . The accomplishment of this plan requires close coordination between the contractor and all Government representatives to ensure that all tasks are accomplished prior to end of the transition period. The contractor may satisfy the requirements of the Transition Phase-in on or before the 30 day deadline. Should the contractor determine that all of the requisite items have been accomplished prior to the 30 day deadline; the contractor may advise the Contracting Officer Representative accordingly.
6.2 Transition: Phase-In. The Contractor shall:6.2.1 Participate in Transition Phase-in tasks to orderly and efficiently receive
knowledge transfer from the off-boarding Contractor, coordinated by the government.
6.2.2 The Transition Phase-in shall be considered the thirty (30) days prior to the contract performance period identified as a separate CLIN.
6.2.3 The Onboarding/Transition Phase-in Plan shall consist of a timeline for support personnel, transitioning actions, and sufficient detail to ensure that no break in services is experienced. Onboarding Contractor leads provide Onboarding Plan to the government leads.
6.2.4 The Onboarding/Transition Phase-in Plan shall include resources qualifications and experience.
6.2.5 Conduct a kick-off meeting with the government to review, negotiate, and approve onboarding plan to include staffing requirements and allocation
6.2.6 Meet with incumbent vendor and the government to garner completed and work-in-progress tasks, challenges, etc… to prepare and present a transition-in plan to the government for review, negotiation, and approval. The transition-in plan shall detail how the new vendor plans to satisfactorily deliver the requirements set forth on this task order.
6.3 Transition: Phase-Out6.3.1 Meet with the government 30 days prior to the end of the period of
performance to review, negotiate, and approve the transition-out plan. The transition-out plan shall detail how the incumbent vendor will
transition knowledge of completed and work-in-progress tasks to the new vendor and the government.
6.3.2 The Transition-out Plan shall provide a timeline for support personnel, transitioning actions, and sufficient detail to ensure that no break in services is experienced.
6.3.3 Participate in Transition Phase-Out tasks to orderly and efficiently provide knowledge transfer to the Onboarding Contractor personnel, coordinated by the government.
6.3.4 The Transition Phase-Out shall be at least 30 days prior the end of the period of performance.
6.3.5 Minimum 15 business days notification for each contractor resource that is off-boarding during the period of the task order.
6.3.6 The contractor shall provide a designated point of contact, and provide advice, knowledge transfer and support in the timeline and transition plans of government data, functions and services to the new awardee and government team(s).
6.4 Transition: Integration Actions6.4.1 Government leads inform government resources to participate in
knowledge transfer sessions.6.4.2 Off-boarding Contractor resources conduct knowledge transfer
sessions with government resources and onboarding contractor resources.
6.4.3 Onboarding Contractor resources receive all Government Furnished Information (GFI) directly related to the tasks specified herein from the government and off-boarding contractor resources.
6.4.4 The off-boarding contractor resources shall provide information for the migration of government data, functions, and services to the government resources and onboarding contractor resources.
6.4.5 Government resources participate and evaluate knowledge transfer sessions and provide information to government lead.
6.4.6 Government lead receives evaluation and negotiates with off-boarding Vendor to provide more info if needed.
6.4.7 Government lead approves completed Knowledge Transfer (KT).
6.5 Transition: Integration Checklist6.5.1 Knowledge transfer to government & Incoming Contractor resources.6.5.2 Documentation transfer to government & Incoming Contractor resources.6.5.3 GFE transfer to government & Incoming Contractor resources.
6.6 TA Process The incumbent contractor shall submit a Resource Allocation Plan to the TA within 7 days of award. This Resource Allocation Plan shall detail how the contractor will accomplish the receipt of the following phase in tasks.
6.6.1 The Resource Allocation Plan shall include all resources qualifications and experiences for TA review and approval. Personally IdentifiableInformation (PII)-redacted resumes shall serve as supplemental documents to the Resource Allocation Plan.
6.6.2 The contractor will provide master copies of the transition plan to the TA and NAVSUP BSC COR.
6.6.3 The accomplishment of this plan requires close coordination between the contractor and all Government representatives to ensure that all tasks are accomplished prior to end of the transition period.
6.6.4 Should the contractor determine that all of the requisite items have been accomplished prior to the 30 day deadline; the contractor may advise the Contracting Officer accordingly.
6.6.5 The contractor may satisfy the requirements of the Transition Phase-in on or before the 30 day deadline.
6.6.6 When the Contractor determines that all of the Transition Phase-in requirements have been fulfilled, he/she shall advise the Contracting Officer.
6.6.7 Upon review, verification, and acceptance of Transition Phase-in tasks by the TA, the Contractor shall commence service execution of the contract.
7.1 Deliverables: The contractor shall provide deliverables as specified in section 5.0 Requirement/Tasks and ensure that work products and updates provide for the deliverables listed below:
7.2 Contractor is required to provide draft and final versions of deliverables IAW the timeframes and measurements specified in the Quality Assurance Surveillance Plan (QASP).
□ The due dates listed in the QASP are for final deliverables; hence, draft deliverables must be submitted in advance of these dates to allow time for Government review and Contractor update as described above.
□ Deliverable due dates proposed by the Contractor shall take into account the review periods described below:
o All deliverables shall be received by the Government no less than 30 calendar days prior to the end of the Period of Performance.
□ Draft deliverables will be reviewed and feedback and/or requested changes provided within maximum 5 business days.
□ Government reserves the right to request a formal review session with the Contractor during these timeframes and may request that the Contractor make changes to any version of a deliverable.
□ If any deliverable is rejected, the Contractor will be notified within the specified time periods, and will have 3 business days within which to rework the deliverable and resubmit for Government approval.
7.3 POR Overall Support Deliverables. The Overall Support deliverables shall be applicable to the firm-fixed and cost-plus POR deliverables. The contractor shall provide deliverables as specified in section 5.1 Requirement/Tasks and ensure that work products and updates provide for the deliverables listed below:
7.2.1 All deliverables shall be completed using a government-approved format.
7.2.2 All Navy ERP (SAP)-related deliverables shall be stored and maintained within government-approved databases / documentation repositories.
7.2.3 All Navy ERP (SAP)-related deliverables shall be provided in an editable format for future revisions by government personnel.
7.2.4 The Contractor shall provide the Government with electronic access to All Navy ERP (SAP)-related deliverables, including access to printable reports, metrics containing raw data and formulas, etc…
7.2.5 All Navy ERP (SAP)-related deliverables shall be subject to Government review and approval.
7.2.6 Contractor shall prepare and submit the deliverables via email on or before the required due date to the government teams and COR.
7.2.7 For deliverables that are not documents (e.g., software configurations), the Contractor shall submit a description of the deliverable and any associated documentation or descriptive information to the government teams, with final approval by the COR.
7.2.8 All changes to any version of a deliverable and/or deliverable outline shall be reviewed and approved by the government teams, with final approval by the COR.
7.2.9 Rejection of any deliverable by the Government does not excuse the Contractor from meeting the baseline due dates for any other deliverables.
7.2.10 Provide meeting minutes for each and all meetings for all Navy ERP (SAP) related tasks. Meeting minutes shall be provided to the applicable Government Team Leads and the TA no later than one week (7 calendar days) of meeting occurrence.
7.2.11 Develop FRDS to define and refine business and functional requirements and design.
7.2.12 Develop Work Breakdown Structure (WBS) in MS Project to clearly define and outline work execution plan
7.2.13 Create Technical Specification documents (e.g. TDS, TFS, HLDs) to detail each unit of work (UOM)
7.2.14 Perform and document all applicable code and configuration rationales as part of the Development lifecycle
7.2.15 Create/update test plans appropriate to the proposed functional and technical solution
7.2.16 Execute the applicable test plans / test cases appropriate to the proposed functional and technical solution and document the results. As appropriate, the contractor can be required to execute test plans / test cases multiple times: Unit, System, Functional, Interface, Regression, Performance, Integration and/or Interoperability.
7.2.17 Prepare new/revised software modules to be migrated to the Production environment
7.2.18 Provide post-production support to ensure the technical migration package(s) were installed and are operating without errors in
Production; document all errors found during postproduction support with root cause identified.
7.3 Firm-fixed Core POR Deliverables. The contractor shall provide deliverables as specified in section 5.2 Requirement/Tasks and ensure that work products and updates provide for the deliverables listed below:
7.3.1 Sustain POR Systems Deliverables. In performance of this TO, the Contractor shall deliver the following, which include:
7.3.1.1 Responsible for delivery throughout every stage of the software lifecycle (Plan, Analyze, Design, Build, Test, Integration, Deployment, and Post Production Support) in accordance with Navy ERP (SAP)’s established standards and procedures.
7.3.1.2 Perform, deliver, and provide maintenance for Navy ERP (SAP) and subcomponents to meet policy changes aligned with: Navy, DoD, Financial Management Office (FMO), and/or SAP guidance.
7.3.1.3 Deliver metrics and reports on corrective maintenance, repair defects, and post-production support to meet service level times/requirements (SLT) and/or key release milestones in production.
7.3.1.4 Deliver metrics/reports and documentation supporting Navy ERP (SAP) Releases, including Pre-Release Notes, and Post-Release Notes.
7.3.1.5 Deliver POR Service Review Status Reports and other metrics, including: HEAT Tickets, QCIs, etc.
7.3.1.6 Deliver metrics and reports to support issue resolutions, including: data integrity, data quality, data migration, data conversion, training, roles, user management, interface connectivity, security, etc…
7.3.1.7 Deliver regular status updates on communications with Navy ERP (SAP) system partners, and existing Navy Legacy systems, to ensure design and configuration data is accurately shared.
7.3.1.8 Perform monitoring and deliver metrics/reports on integration and accuracy of data exchanges between ECC, BI, SCM, SRM, GRC, and related Navy ERP (SAP) components.
7.3.1.9 Deliver support throughout entire system integration processes, activities, etc.
7.3.1.10 Implement and deliver impact analysis/reports/metrics and recommendations on vendor-required or -recommended modifications, including: SAP OSS notes, SAP patches, and NetWeaver plug-ins on NAVY ERP (SAP).
7.3.1.11 Implement Design Changes and Engineering Change Proposals (ECPs) to resolve, change, or improve technical and functional requirements.
7.3.1.12 Deliver analysis, metrics, and reports on RFCs in relation to system impacts, including: architecture, roles, training, cross- team/functionality, data management, interfaces, etc…
7.3.1.13 Conduct content reviews/walk-throughs, including “as-is” processes and “to-be” processes for all system and documentation changes.
7.3.1.14 Perform, deliver, and provide reports/metrics on system refreshes and upgrades for Navy ERP (SAP) and subcomponents to meet policy changes aligned with Navy, DoD, and SAP guidance.
7.3.1.15 Perform, deliver, and provide documentation (creations and revisions) and reports/metrics on HANA, configuration, table verification and mapping, and cross-team coordination.
7.3.1.16 Perform, deliver, and provide documentation (creations and revisions) and reports/metrics on Attunity Gold Client Software implementation and sustainment.
7.3.1.17 Deliver technical documentation (creations and revisions) and Code Review approval prior to Testing phase, including: High Level Designs (HLDs) and Technical Design Specifications (TDSs).
7.3.1.18 Deliver Navy ERP (SAP)-related document creations and revisions prior to Development Phase including: Standard Operating Procedures (SOPs), Functional Requirements Design Specifications (FRDSs), Desk Guides, etc.
7.3.1.19 Perform, deliver, and provide status reports for all phases of master and transactional data lifecycles by following related policies/procedures, implementing appropriate technologies, frameworks, and utilities to ensure system continuity and stability.
7.3.1.20 Perform, deliver, and provide reports on interface lifecycle management system continuity, stability, and auditability.
7.3.1.21 Perform, deliver, and provide new procedures (as required), reports, and metrics on interface reconciliation and error resolution to assure that data exchanges are accurate and auditable.
7.3.1.22 Perform, deliver, and provide reports/metrics on maintenance activities (e.g., scheduled and unscheduled patches, SAP Online SAP Support Notes (OSS), fixes, and/or releases) along with BSC and BSC-recommended stakeholders (e.g., Government and Contractor functional and technical teams/sub- teams)
7.3.1.23 Perform, deliver, and provide reports/metrics on Navy ERP (SAP) system closings, period closings (e.g., month-end, year-end and year-start activities).
7.3.1.24 Perform, deliver, and provide reports/metrics on financial auditability and system compliance requirements in accordance with guidance, policies, and standards (e.g., SFIS, DLMS, JITC).
7.3.1.25 Deliver, maintain, and provide reports/metrics on complete set of architecture views for NAVY ERP (SAP) aligned with the DoD Architecture Framework (DODAF) artifacts and Navy ERP (SAP) Architecture Book.
7.3.1.26 Deliver, conduct, and provide reports/metrics on defined traceability and referential integrity checks between architecture views to ensure compliance with Navy ERP (SAP), DoDAF, Business Process Modeling Notation (BPMN), and Data architecture standards.
7.3.1.27 Deliver grammatically and functionally clear descriptions for objects defined within DoDAF artifacts.
7.3.1.28 Deliver, maintain, and provide reports/metrics on System Architect encyclopedias, back-ups, and USRPROPS (user properties).
7.3.1.29 Obtain government approval of completed changes and document completion of Request for Change (RFC) related architecture action items in Dimensions tool or other government identified procedure.
7.3.1.30 Deliver Test Plan (Regression Test Plans and Functional Test Plans (RTPs/FTPs)) revisions prior to moving out of Unit test and into Regression/Quality test and validation.
7.3.1.31 Deliver weekly individual personnel status reports containing accomplishments, achievements, and issues to Government team leads.
7.3.2 Tier III Service Desk Deliverables. In performance of this TO, the Contractor shall deliver the following, which include:
7.3.2.1 Operate a Tier III Service Desk, resolve, and provide reports/metrics/trends/statistics for incident tickets from various sources (e.g., RSC HEAT tickets, etc…), on a weekly or bi-weekly basis
7.3.2.2 Deliver detailed assessments of key issues to the Government POR Teams and Government POR Director (proposed weekly).
7.3.2.3 Resolve and provide reports/metrics/trends/statistics for Defects, Break/Fixes, Maintenance Items, Action Items, Design Changes (RFC), Engineering Change Proposals (ECP), including providing specific requirements and feedback (proposed weekly).
7.3.2.4 Resolve and provide reports/metrics/trends/statistics for Data Service Requests, Ad Hoc Requests, Functional Maintenance Requests, and Projects (proposed weekly).
7.3.2.5 Resolve and provide reports/metrics/trends/statistics for Operations and Maintenance Tasks (proposed weekly).
7.3.2.6 Conduct and provide reports/metrics for testing Navy ERP (SAP) including positive, negative, stress, regression, etc.
7.3.2.7 Perform, deliver, document actions in HEAT/QC, and provide reports/metrics on Production Cutover, Deployment, and Post- Production Support.
7.3.2.8 Perform, deliver, and provide reports/metrics on Technical Support and System Monitoring.
7.3.2.9 Deliver software support for applications, utilities, and components.
7.3.2.10 Perform, deliver, and provide reports/metrics on Interface Error Resolution and Maintenance.
7.3.2.11 Perform, deliver, and provide reports/metrics on SAP Workflow and incidents, including the involvement of third party providers (e.g., SAP, network service providers).
7.3.2.12 Obtain approval from Government boards, create and deliver transports, and migrate code/configuration/functionality through the Navy ERP (SAP) landscape.
7.3.2.13 Resolve, document actions in HEAT/QC, and provide reports/metrics on all Batch Process failures in a timely manner to ensure data exchanges between Navy ERP (SAP) and partner systems are accurate, while complying with audit requirements.
7.3.2.14 Deliver resolutions, developments, tests, Resolve, develop, test, implement, document actions in HEAT/QC, and provide reports/metrics on solutions for sustainment modifications, software releases, and fixes (scheduled and unscheduled).
7.3.2.15 Create new, maintain existing, and deliver Standard Operating Procedures (SOPs) in order to address service incident tickets in a standardized and consistent manner and transfer knowledge.
7.3.2.16 Distribute appropriate communications and provide status on interactions to various Navy ERP (SAP) teams (e.g., Program Management Office (PMO), Financial Management Office (FMO), SSC-LANT, Navy ERP (SAP) Tier II, Enterprise Business Offices (EBOs), Item Managers, Navy ERP (SAP) Tier III Functional and Technical Teams, and system partners).
7.3.2.17 Perform and deliver report/metrics for HEAT ticket assignments, resolutions, resolution times, SOPs utilized, etc…for entire incident/problem life cycle.
7.3.2.18 Perform and deliver report for daily monitoring services associated with the ongoing health checks, status reporting, and problem management of Navy ERP (SAP) support activities to ensure production issues are resolved effectively and efficiently and within Navy ERP (SAP)’s established Service Level Targets (SLTs).
7.3.2.19 Perform and deliver updated task and workload tracking/management system(s) as the Navy ERP (SAP) environment evolves.
7.3.2.20 Create, perform and Deliver Business Operations and Business Optimization Metrics/reports (WKLY).
7.3.2.21 Conduct bi-weekly deep dive of operations topics (e.g., tickets, interface metrics) meetings.
7.3.2.22 Conduct content reviews/walk-throughs, including to “as- is” processes and “to-be” processes for all system and documentation changes.
7.3.3 Business Intelligence and Data Warehousing Deliverables. In performance of this TO, the Contractor shall deliver the following, which include:
7.3.3.1 Provide reporting capability and an intuitive BI interface to enable users to explore data.
7.3.3.2 Provide a robust way to search, capture, store, reuse, and publish metadata objects (e.g., dimensions, hierarchies, measures, and performance metrics) and report layout objects. Reporting capabilities include: data management, data warehouse, data marts, and data delivery.
7.3.3.3 Provide mechanisms for queries; assist in building queries; design and build dashboards and Cubes; and train users in the logic, processes, flows, and use of the system.
7.3.3.4 Provide the validation and ‘checkout’ process to ensure data consistency. To include: process chains, data loads, and/or manual data loads.
7.3.3.5 Report updates to NAVY ERP (SAP) financial dashboard (e.g., obligations rate, unliquidated obligations, and Intermediate Document (IDoc) errors).
7.3.3.6 Provide logging process-chain diagrams at detailed level (their interdependence and dependencies on) for various BW InfoObjects.
7.3.3.7 Provide performance testing results of cross-component impacts (e.g., an ECC change which will degrade BI performance or cause data to be omitted from reports)
7.3.3.8 Provide test and release management processes, checks, and plans for each software release.
7.3.3.9 Provide assessment of gaps in NAVY ERP (SAP) BI solution.7.3.3.10 Implement a standard security, metadata,
administration, portal integration, object model, and query engine.
7.3.3.11 Provide BI processes necessary to affect Schemas and establish the logic, design, mapping, and transfer of data from sources.
7.3.3.12 Update quarterly operational data store that support operative data analysis.
7.3.3.13 Conduct content reviews/walk-throughs, including “as-is” processes and “to-be” processes for all system and documentation changes.
7.3.3.14 SAP software developer’s kit for creating BI applications, integrating them into a business process, and/or embedding them in another application.
7.3.3.15 Events or tasks allotted to specific users, based on predefined business rules.
7.3.3.16 ETL of data and information from other Government (DoD and non-DoD) partners.
7.3.3.17 Automation of the data mart processes aligned with schemas, organize data into separate tiers according to specified policies, and
7.3.3.18 Automation of data migration from one tier to another based migration criteria.
7.3.3.19 Authoritative sources, issues and barriers to accessing data sources, and make recommendations on a governance structure, and establish methods for ensuring data quality.
7.3.3.20 Information Lifecycle Management (ILM) Archiving Strategy that enables more complex criteria for storage management without replication.
7.3.3.21 Maintain Standard Operating Procedures (SOPs) for BI activities at all levels.
7.3.3.22 Conduct planning and analysis services, associated research, process development and implementation, and configuration of the BI application based on user requirement.
7.3.4 Cross-Team Integration Deliverables. In performance of this TO, the Contractor shall deliver the following, which include:
7.3.4.1 Provide integration review and readiness services for all changes being implemented for Navy ERP (SAP). This includes changes/enhancements that are not POR work.
7.3.4.2 Receive all approvals from Government boards, as required.7.3.4.3 Document all changes, including approvals, in HEAT and QC.7.3.4.4 Provide resource schedules that cover all stages of
software lifecycle development.7.3.4.5 Distribute appropriate communications to various Navy ERP
(SAP) teams (e.g., Program Management Office (PMO), FinancialManagement Office (FMO), SSC-LANT, Navy ERP (SAP) Tier II, Enterprise Business Offices (EBOs), Item Managers, Navy ERP (SAP) Tier III Functional and Technical Teams, and system partners).
7.3.4.6 Provide Government lead with status report throughout the software development life cycle.
7.3.4.7 Create, maintain, and provide documentation supporting Navy ERP (SAP) Releases (including pre- and post-Release Notes) to Government.
7.3.4.8 Conduct content reviews/walk-throughs, including “as-is” processes and “to-be” processes for all system and documentation changes.
7.3.5 Technical Management Deliverables. In performance of this TO, the Contractor shall deliver the following, which include:
7.3.5.1 Provide analysis and status reports in support of Navy ERP (SAP) software/hardware enhancements, upgrades, and system optimizations.
7.3.5.2 Provide analysis and status reports in support of research and feasibility analysis for current and prospective hardware, software, Commercial Off-The-Shelf (COTS) tools, and applications.
7.3.5.3 Provide root cause analyses and corrective actions for business processes.
7.3.5.4 Provide documentation on technical and functional system enhancements, reporting, and conversions.
7.3.5.5 Provide Technical Project Summaries (TPS) for system changes.7.3.5.6 Provide assistance and document software lifecycle
improvements, including: configuration management, documentation management, data architecture, business processes management, functional/technical processes management, and training.
7.3.5.7 Provide assistance and document interface management processes, including: Interface Mapping Diagrams (e.g., SV-1, SV-6), Interface Control Agreements (ICAs), Memorandum of Agreements/Understanding (MOAs/MOUs), creation, migration, testing, validations, maintenance, data mappings, monitoring, and error resolution.
7.3.5.8 Provide assistance and document BODS performance improvements, including: hardware, software, configuration, coding, and script writing.
7.3.5.9 Provide assistance and document SAP User Provisioning, Role Maintenance and GRC user updates.
7.3.5.10 Provide GRC Approver Master Listing (WKLY)7.3.5.11 Provide List of Super User Privileged Management
SPM IDs (when changed)7.3.5.12 Provide User to Role Mapping (BI-WE)7.3.5.13 Provide Remedy User List (BI-WE)7.3.5.14 Provide User Role Matrix (MTHLY)7.3.5.15 Provide Role to T-Code Matrix (MTHLY)7.3.5.16 Provide User Status Report (WKLY)7.3.5.17 Provide List of Firefighter IDs (MTHLY)7.3.5.18 Report quarterly review of Navy ERP (SAP) “as-is” and
identify and recommend software and/or hardware rationalization and consolidation with the objective to improve performance and reduce operating costs.
7.3.5.19 Report design improvements (i.e., interfaces, business processes, configuration, or hardware) that will improve performance and reduce operating costs.
7.3.5.20 Provide and document products in the Navy ERP (SAP) baseline, including recommendations on upgrades and maintenance activities to balance cost and performance.
7.3.5.21 Conduct content reviews/walk-throughs, including “as-is” processes and “to-be” processes for all system and documentation changes.
7.3.6 Data Management Processes and Support Deliverables. In performance of this TO, the Contractor shall deliver the following throughout the Data Maintenance life cycle, as defined by the Government Lead, which include:
7.3.6.1 Provide and document all Data Management Requests using LSMWs, ABAP, TCodes, and BODS, including:7.3.6.1.1 RSC tickets7.3.6.1.2 Defects7.3.6.1.3 Break/Fixes7.3.6.1.4 IDOC Reprocessing7.3.6.1.5 DSRs7.3.6.1.6 QCIs7.3.6.1.7 Data Conversions, Data Loads, Data Distributions,
and Data Migrations7.3.6.1.8 Data Mappings and Data Validation7.3.6.1.9 Data Reports and Data Extracts
7.3.6.2 Provide and document error identification, root cause analysis, troubleshooting, and resolution processes
7.3.6.3 Provide trend analysis, metrics, statistics, and reports for the following, including:7.3.6.3.1 Table Validations7.3.6.3.2 Data Warehousing/BW7.3.6.3.3 Data Management Maintenance7.3.6.3.4 Error resolution7.3.6.3.5 BODS7.3.6.3.6 RSC Tickets (SLTs, Aging, Discrepancies, SOP
Compliance), etc)7.3.6.4 Provide and document Data Reconciliation7.3.6.5 Provide and document Data Extracts and Reports
involving BODS/BW development, execution, and maintenance
7.3.6.6 Provide and document Data Refreshes
7.3.6.7 Provide and document Attunity Gold Client Software implementation
7.3.6.8 Provide and document Technical upgrades7.3.6.9 Provide and document Data Archiving7.3.6.10 Configure, implement, test, document, use, and provide
statistics/reports for SAP Master Data Governance (MDG) application or similar application to support Data Integrity and Quality Control
7.3.6.11 Provide Data Management Training Materials7.3.6.12 Develop and maintain Standard Operating Procedures (SOPs)
and related documentation for Data Management activities at all levels
7.3.6.13 Research, develop, document, and implement new capabilities7.3.6.14 Conduct and document content reviews/walk-throughs,
including “as-is” processes and “to-be” processes for all system and documentation changes
7.3.7 Interface Management Processes and Support Deliverables. In performance of this TO, the Contractor shall deliver the following throughout the Interface life cycle, as defined by the Government Lead, which include:
7.3.7.1 Follow current and prospective Navy ERP (SAP) Interface Management principals, policies (e.g., Government and commercial), procedures, and processes to ensure completeness, accuracy, and auditability of data exchanges.
7.3.7.2 Provide, deliver, and document all Interface Life Cycle work requests approved by Navy ERP Governance Board, as defined by the Government Lead, including:7.3.7.2.1 Business process requirements gathering process7.3.7.2.2 Changes for Interface Control Agreements (ICAs)
and Memorandum Of Agreements (MOAs/MOUs)7.3.7.2.3 Coordination for interface functional/technical
requirements development process with partners and Navy ERP (SAP) functional/technical teams
7.3.7.2.4 Functional and technical design processes.7.3.7.2.5 Changes for process diagrams, flowcharts, workshops,
and walk-throughs with partners and Navy ERP (SAP) functional teams throughout the business process blueprinting.
7.3.7.2.6 Coordination for development, configuration, and establishment of interface design and connectivity; including, mapping and transfer of data from sources.
7.3.7.2.7 Interface cycle testing, scheduling, migration, and user training; including, validations and coordination with Government (DoD and non-DoD) partners, including trend analysis, metrics, statistics, and reports
7.3.7.2.8 Transition and Integration Plan for new interfaces in the Production Environment.
7.3.7.2.9 Schedule and validate the interface for frequencies, formatting, and Transfer Protocols, including trend analysis, metrics, statistics, and reports
7.3.7.2.10 Navy ERP (SAP) interface monitoring, error resolution, error logs, reporting, root cause and trend analysis, and notifications, including trend analysis, metrics, statistics, and reports
7.3.7.2.11 Service Desk Production incident ticket resolution (e.g., error identification, troubleshooting, and providing notifications to RSC, Functional/Technical teams, and Customers) , including trend analysis, metrics,statistics, and reports
7.3.7.2.12 Automation of monitoring, reporting, and notifications processes, including trend analysis, metrics, statistics, and reports
7.3.7.2.13 Job processing for potential changes or enhancements, including recommendations for improvements to Interface Management processes
7.3.7.3 Provide, deliver, and document trend analysis, metrics, statistics, and reports for various Audit and Compliance requirements (i.e. SFIS compliance, DLMS compliance, JITC)
7.3.7.4 Provide, deliver, and document trend analysis, metrics, statistics, and reports for Reconciliation processes for Navy ERP (SAP) interfaces.
7.3.7.5 Provide, deliver, and document trend analysis, metrics, statistics, and reports for Audit support.
7.3.7.6 Provide, deliver, and document documentation creation, revision, and updates throughout the interface life cycle (e.g., SOPs, error logs, JSRs, FRDSs, etc)
7.3.7.7 Provide, deliver, and document trend analysis, metrics, statistics, and reports for interface performance and stability; including providing feedback for adjustments and optimization.
7.3.7.8 Provide, deliver, and document Interface Management Training materials.
7.3.7.9 Research, develop, document, deliver, and report new capabilities
7.3.7.10 Conduct content reviews/walk-throughs, including “as-is” processes and “to-be” processes for all system and documentation changes
7.3.8 Training Processes and Support Deliverables. In performance of this TO, the Contractor shall deliver the following, which include:
7.3.8.1 Provide and deliver the enterprise training governance strategy documents to the Government lead for approval.
7.3.8.2 Provide and deliver modernized enterprise training solution course content to the Government lead for approval.
7.3.8.3 Provide and deliver training content using the Navy ERP training framework, including Ancile uPerform and SAP LSO tools. This includes the lifecycle of creating, publishing and authoring training course content.
7.3.8.4 Provide and deliver Ancile uPerform training course components: templates, course content, course simulation files, audio files, etc.
7.3.8.5 Provide and deliver published training course content file to be imported into the SAP LSO authoring tool.
7.3.8.6 Provide and deliver training content for new functionality and update existing course content based on changes in business processes. This includes applying BPP revisions to training material content and republishing the updated course for end user consumption.
7.3.8.7 Review, approve, and post BPPs for Production Releases to the ECMS tool or equivalent Government tool.
7.3.8.8 Develop, document, deliver, and maintain SAP LSO Master Repository architecture/structure/hierarchy and obtain approval for permissions.
7.3.8.9 Provide and deliver SAP LSO training course components: publishing content, authoring content, distribution of content for use/ consumption, impart SAP training qualifications.
7.3.8.10 Provide and deliver reports/statistics on issues with the SAP LSO Authoring environment tools: Import resources, Learning Objectives Manager, Template Manager, Repository Explorer, Packaging, Learning Net Conversion, Wizard, Customization and Configuration
7.3.8.11 Provide and deliver statistical reports on Navy ERP (SAP) training participation, as requested by the Government lead.
7.3.8.12 Provide and deliver a training course that describes the best business practices for the training course creation, publication, and authoring lifecycle to the Government lead for approval.
7.3.8.13 Provide, deliver, and post monthly Roles-to-Course Qualifications Matrix.
7.3.8.14 Conduct content reviews/walk-throughs, including “as-is” processes and “to-be” processes for all system and documentation changes.
7.3.8.15 Provide and document testing and troubleshooting throughout the Training life cycle, as requested by Government lead
7.3.9 POR Enhancements Deliverables. The contractor shall provide deliverables as specified in section 5.3 Requirement/Tasks and ensure that work products and updates provide for the deliverables listed below:
7.3.9.1 Provide weekly status reports on resolved limitations due to infrastructure deltas.
7.3.9.2 Provide weekly status reports on installations of hardware, software and licenses.
7.3.9.3 Provide weekly status reports on integration across the Navy ERP (SAP) components and ensure data Application capacity plan.
7.3.9.4 Provide and document the POR Enhancements Plan.7.3.9.5 Provide estimates and level of complexity for each
enhancement / capability as requested by the government.7.3.9.6 Provide POR release schedule to include,
o Infrastructure upgrades,o Operating system upgrades,o Database upgrades,o Major application version upgrades
o Capability Releases
7.4 Technical Operations Deliverables. The contractor shall ensure that work products and updates are delivered as specified in section 5.4 Requirement/Tasks and provide the deliverables listed below:
7.4.1.1 Provide TCCB Minutes7.4.1.2 Provide Pre and Post Release Notes7.4.1.3 Provide Change Documents7.4.1.4 Provide Production Transport Tracking Spreadsheet7.4.1.5 Provide Test Event Metrics7.4.1.6 Provide Strategic Technology Plan7.4.1.7 Provide Annual Technology Refresh Plan7.4.1.8 Provide Annual Technology Refresh Schedule in the beginning
of each fiscal year7.4.1.9 Provide Disaster Recovery Test Plan7.4.1.10 Provide Disaster Recovery Execution Plan7.4.1.11 Provide Disaster Recovery Exercise Detailed Work Plan7.4.1.12 Provide Disaster Recovery Failover Test and
Exercise After Action7.4.1.13 Provide System Change or Outage Request7.4.1.14 Provide performance metrics as requested7.4.1.15 Develop and respond to data calls
7.4.2 Knowledge Transfer Deliverables. In performance of this TO, the Contractor shall deliver the following, which include:
7.4.2.1 Provide mentoring/knowledge transfer documentation, lesson plans, and mentoring reports (Monthly). The mentoring report shall include:
□ Trainer Name□ Trainee Name
□ Date Knowledge Transfer began□ Date Knowledge Transfer completed□ Description of skill/knowledge area
7.5 Cost-Plus Deliverables. The contractor shall provide deliverables as specified in section 5.6 Requirement/Tasks and ensure that work products and updates provide for the deliverables listed below:
7.5.1 Rough Order of Magnitude (ROM) and/or Preliminary Cost Estimates (PCE) will be developed alongside with and provided to the NAVSUP BSC Project Management team to appropriately plan for each work item. ROM / PCE will contain estimated hours, level of effort, complexity, RICEFW impacts, Cross Process/External Partner impacts, and the required skillset for each assigned work item.
7.5.2 The contractor will develop FRDS to define and refine business and functional requirements and design.
7.5.3 The contractor will develop Work Breakdown Structure (WBS) in MS Project to clearly define and outline work execution plan
7.5.4 The contractor will create Technical Specification documents (e.g. TDS, TFS, HLDs) to detail each unit of work (UOM)
7.5.5 The contractor will perform and document all applicable code and configuration rationales as part of the Development lifecycle
7.5.6 The contractor will create/update test plans appropriate to the proposed functional and technical solution
7.5.7 The contractor will execute the applicable test plans / test cases appropriate to the proposed functional and technical solution and document the results. As appropriate, the contractor can be required to execute test plans / test cases multiple times: Unit, System, Functional, Interface, Regression, Performance, Integration and/or Interoperability.
7.5.8 The contractor will prepare new/revised software modules to be migrated to the Production environment
7.5.9 The contractor will provide post-production support to ensure the technical migration package(s) were installed and are operating without errors in Production; document all errors found during postproduction support with root cause identified.
7.5.10 The contractor will provide Cross-Team Integration.7.5.11 Provide and document implementation/cutover schedule and
includes post implementation checkouts.7.5.12 Ensure all functional/technical designs are complete.
7.6 Travel Deliverables. In performance of this TO, the Contractor shall deliver the following, which include:
7.6.1 Provide monthly (if applicable) Travel Reports. Travel reports shall be sent electronically to the TA and COR. Travel reports shall include: destination, date of government approval prior to travel, dates of travel, subjects discussed, and any issues/problems encountered and recommended solutions.
7.7 Weekly Status Report. In performance of this TO, the Contractor shall deliver the following, which include:
7.7.1 Status reports shall be split into two identical reports, one for the firm- fixed requirements and one for the cost-plus requirements. The reports shall be sent electronically to the Technical Assistant (TA) and Contracting Officer’s Representative (COR) within three (3) calendar days following the end of the weekly period (typically on Friday) documenting the performance on the task order. The weekly status report shall include the following elements:
Resources by name broken out by functional area and modules, by project, and by planned project hours
Date project/task received and associated metrics Status of work with accomplishments documented Percentage of hours burned/worked - broken out by
hours planned vs actuals (identify overtime hours actuals) Percentage of project/task completed - broken out by development phases (based upon schedule)
Estimated date of project/task completion Release status and metrics Any issues/problems/risks encountered or possible and
recommended solutions, and any significant deviations Funding metrics broken out by associated CLINs and by
projects (budgeted, funded, actuals, and shortfalls) Changes to the Project Management Plan (PMP) to include
roles and responsibilities, schedule changes, and fundingchanges
Identify any Government dependencies that are overdue which impact schedule or performance
Resource capacity and include staffing changes) Resource commuting travel metrics
8.0 P e r io d of P e r fo rman ce :
Work shall be performed from the period of performance start date for twelve months (including the Transition – Phase-In Period) with two (2) additional one (1) year option periods. A 30-day start-up period is required prior to the period of performance as defined in section 5.4.4.1 and mentioned again below. The contractor shall follow Naval Support Activity base policy for reporting to work during severe weather and base closure. The contractor is not authorized to begin work until both the Visit Authorization Request (VAR) and System Authorization Access Request - Navy (SAAR-N) forms have been successfully processed and base and system access have been granted.
START-UP PERIOD
It is intended to make award of the resultant contractual vehicle in time to allow an approximate 30 day start-up period in advance of the actual commencement of the performance period. All contractor resource onboarding documents must be submitted via the prime contractor. The prime contractor shall make all necessary preparations, during this start-up period, to assume full responsibility for “productive” performance as of the performance start date (unless a transition period is called out in this PWS, then full responsibility shall be assumed after the transition period).
Definition of “productive”:a. Visit Authorization Request (VAR)b. Contractor Information Sheet (CIS)c. FD-258 fingerprint cardd. Completed EQIP (Electronic Investigation) within 20 days after contract awarde. All contractor resource(s) must have an active JPAS profile within 20 days after
contract awardf. Common Access Card (CAC)g. System Authorization Access Request – Navy (SAAR-N)h. Cyber Awareness Training Certificationi. Information Assurance (IA) certification (if applicable)j. User Access Request (UAR)
Note (1): Invoicing by the contractor will begin as of the commencement of services and no reimbursement will be paid by the Government for efforts expended during the start-up period. Note (2): Dual Citizenship and Foreign Nationals are not allowed access to the functional/system side of ERP/SAP.
9.1 P l a ce of Performance :
The NAVSUP BSC, Mechanicsburg PA is the primary site for performance. The contractor may be required to perform Technical Infrastructure Architecture work on-site at the Patuxent River data center occasionally and onsite at the China Lake data center rarely. For some tasks, the contractor may be required to travel to other Navy/DOD sites in support of projects pre-approved by the TA and COR. Overseas Travel is not required.
□ Senior SAP – OF/SD/MM/SCM/PROC or Other COTS Equivo There shall always be at least one SME on-site each week, for
each functional/module team (OF, IM, WM, PR/MM, SMD, SCM/PL)
o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ Senior Finance/Controlling/Asset Accounting or Asset Mgto There shall always be at least one SME on-site for each functional/module
team (FI, FM, WFM, SD, PS, CO, AM),o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ ABAP/RICE Developer or Other COTS Equivo There shall always be at least two key resources on-site 100% each week.
o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ MIDDLEWARE DEVELOPER -INFORMATICA/ WEBMETHODS OR EQUIVo There shall always be at least two key resources on-site 100% each week.o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ User Managemento There shall always be at least two key resources on-site 100% each week.o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ Data Managemento There shall always be at least two key resources on-site 100% each week.o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ Data Analyst (Interface Control)o There shall always be at least two key resources on-site 100% each week.o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ Senior Training SMEo Key personnel shall be on-site 100% of the time, Monday – Thursday.o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday
□ Enterprise Architecto There shall always be at least one key resource on-site 100% each week.o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ Data Modeler (Data Architect)o There shall always be at least one key resource on-site 100% each week.o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ Midlevel SAP (Tivoli)o Maintain 24 x 7 coverage, as appropriate in order to maintain Navy-ERP operation
and performance objectives and to respond to critical situations or system failures. Shift coverage is acceptable.
o There shall always be at least one key resource on-site 100% each week.o Minimum core office hours are 0800-1600, Monday - Thursday. o Fridays may be an off-site workday.o Shift coverage outside of the core office hours as defined above can be
performed off-site.
□ Technical Architectureo There shall always be at least one key resource on-site 100% each week.o Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday.
□ Quality Assurance / Regression Testero There shall always be at least one resource on-site each weeko Minimum core office hours are 0800-1600, Monday - Thursday.o Fridays may be an off-site workday
o During regression test event, additional coverage beyond specified above and Friday on-site representative may be required.
□ SAP BASISo Maintain 24 x 7 coverage, as appropriate in order to maintain Navy-ERP operation and
performance objectives and to respond to critical situations or system failures. Shift coverage is acceptable.
o There shall always be at least one key resource on-site 100% each week.Minimum core office hours are 0800-1600, Monday – Thursday.
o Fridays may be an off-site workday.o Shift coverage outside of the core office hours as defined above can be performed off-
site.
□ All other Non-Key personnel shall be onsite at a minimum of least 50% of the time, with a minimum of core office hours Monday-Thursday from 0800-1600 and Friday may be offsite full workday.
□ If Cost-Plus contractor resources will incur overtime or excessive burn hours greater than 15 hours in a work week, a courtesy email notification shall be sent to the TA and COR prior to execution, and metrics shall be included in the weekly status report
10.1 Travel :
The contractor may be required to travel to CONUS, such as other Navy commands in and around the DC Area (includes DC, cities of Alexandria, Falls Church and Fairfax, and the counties of Arlington and Fairfax, in Virginia; and the counties of Montgomery and Prince George's in Maryland). Up to 20 business days (not concurrent) of travel may be required, with up to four (4) people per day. Travel shall be in accordance with FAR 31.205-46. All travel must be pre-approved in writing by the TA and COR prior to the actual travel and all travel must be funded in the contract prior to any travel expenses being incurred. Travel 12 hours or less, per diem does not apply. Foreign (overseas) Travel will not be required for this Task Order.
If travel is required, the contractor is responsible for making all needed arrangements for their personnel.
10.2 Travel Policy . The Government will reimburse the contractor for allowable travel costs incurred by the contractor in performance of this PWS and determined to be in accordance with FAR subpart 31.2, subject to the following provisions:
□ Travel required for tasks assigned under this contract shall be governed in accordance with rules set forth for temporary duty travel in FAR 31.205-46.
10.3 Travel other . Travel, subsistence, and associated labor charges for travel time are authorized whenever a task assignment requires work to be accomplished at a temporary alternate worksite. Travel performed for personal convenience will not be reimbursed.
10.6 Air/Rail Travel . In rendering the services, the contractor shall be reimbursed for the actual costs of transportation incurred by its personnel not to exceed the cost of economy class
rail, or plane fare, to the extent that such transportation is necessary for the performance of the services hereunder and is authorized by the Contracting Officer’s Representative (COR). Such authorization by the COR shall be indicated in the order or in some other suitable written form.
11.0 Security:
Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information Technology (IT) Systems or Protected Health Information (Jan 2017)
Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The Deputy Secretary of Defense Directive-Type Memorandum (DTM) 08-006 – “DoD Implementation of Homeland Security Presidential Directive – 12 (HSPD-12)” dated November 26, 2008 (or its subsequent DoD instruction) directs implementation of HSPD-12. This clause is in accordance with HSPD-12 and its implementing directives.
APPLICABILITYThis clause applies to contractor employees requiring physical access to any area of a federally controlled base, facility or activity and/or requiring access to a DoN or DoD computer/network/system to perform certain unclassified sensitive duties. This clause also applies to contractor employees who access Privacy Act and Protected Health Information, provide support associated with fiduciary duties, or perform duties that have been identified as National Security Position, as advised by the command security manager. It is the responsibilityof the responsible security officer of the command/facility where the work is performed to ensure compliance.
Each contractor employee providing services at a Navy Command under this contract is required to obtain a Department of Defense Common Access Card (DoD CAC). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.
ACCESS TO FEDERAL FACILITIESPer HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a DoD CAC. When access to a base, facility or activity is required contractor employees shall in-process with the Command’s Security Manager upon arrival to the Command and shall out-process prior to their departure at the completion of the individual’s performance under the contract.
ACCESS TO DOD IT SYSTEMSIn accordance with SECNAV M-5510.30, contractor employees who require access to DoN or DoD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAV M-5510.30, includes positions which require access to information protected under the Privacy Act, to include Protected Health Information (PHI). All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity’s Command Information Assurance Manager.
Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) or T5 or T5R equivalent investigation , which is a higher level investigation than the National Agency Check with Law and Credit (NACLC)/T3/T3R described below. Due to the privileged system access, an investigation suitable for High Risk national security positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1, and must be trained and certified on the Operating System or Computing Environment they are required to maintain.
Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out- process prior to their departure at the completion of the individual’s performance under the contract. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N; therefore, the government employeewith knowledge of the system/network access required or the COR shall sign the SAAR-N as the “supervisor”.
The SAAR-N shall be forwarded to the Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.
When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.
INTERIM ACCESSThe Command's Security Manager may authorize issuance of a DoD CAC and interim access to a DoN or DoD unclassified computer/network upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.
DENIAL OR TERMINATION OF ACCESSThe potential consequences of any requirement under this clause including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall
insert this clause in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.
CONTRACTOR’S SECURITY REPRESENTATIVEThe contractor shall designate an employee to serve as the Contractor’s Security Representative. Within three work days after contract award, the contractor shall provide to the requiring activity’s Security Manager and the Contracting Officer, in writing, the name, title, address and phone number for the Contractor’s Security Representative. The Contractor’s Security Representative shall be the primary point of contact on any security matter. The Contractor’s Security Representative shall not be replaced or removed without prior notice to the Contracting Officer and Command Security Manager.
BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FORCONTRACTORS ASSIGNED TO NATIONAL SECURITY POSITIONS OR PERFORMING SENSITIVEDUTIESNavy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. Contractor employees under this contract are recognized as Non- Critical Sensitive [ADP/IT-II] positions when the contract scope of work require physical access to a federally controlled base, facility or activity and/or requiring access to a DoD computer/network, to perform unclassified sensitive duties. This designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably completed NACLC or T3 or T3R equivalent investigation to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The investigation consists of a standard NAC and a FBI fingerprint check plus law enforcement checks and credit check. Each contractor employee filling a non-critical sensitive or IT-II position is required to complete:
• SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product)
• Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)• Original Signed Release Statements
Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date. Background investigations shall be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.
Regardless of their duties or IT access requirements ALL contractor employees shall in-process with the Command’s Security Manager upon arrival to the command and shall out-process prior to their departure at the completion of the individual’s performance under the contract.Employees requiring IT access shall also check-in and check-out with the Navy Command’s
Information Assurance Manager. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The SAAR-N shall be forwarded to the Navy Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date.
The contractor shall ensure that each contract employee requiring access to IT systems or networks complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. Contractor employees shall accurately complete the required investigative forms prior to submission to the Command Security Manager. The Command’s Security Manager will review the submitted documentation for completeness prior to submitting it to the Office of Personnel Management (OPM); Potential suitability or security issues identified may render the contractor employee ineligible for the assignment. An unfavorable determination is final (subject to SF-86 appeal procedures) and such a determination does not relieve the contractor from meeting any contractual obligation under the contract. The Command’s Security Manager will forward the required forms to OPM for processing. Once the investigation is complete, the results will be forwarded by OPM to the DoD Central Adjudication Facility (CAF) for a determination.
If the contractor employee already possesses a current favorably adjudicated investigation, the contractor shall submit a Visit Authorization Request (VAR) via the Joint Personnel Adjudication System (JPAS) or a hard copy VAR directly from the contractor’s Security Representative. Although the contractor will take JPAS “Owning” role over the contractor employee, the Navy Command will take JPAS "Servicing" role over the contractor employee during the hiring process and for the duration of assignment under that contract. The contractor shall include the IT Position Category per SECNAV M-5510.30 for each employee designated on a VAR. The VAR requires annual renewal for the duration of the employee’s performance under the contract.
BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR CONTRACTORS ASSIGNED TO OR PERFORMING NON- SENSITIVE DUTIESContractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc. ...) and who require physical access to publicly accessible areas to perform those duties shall meet the following minimum requirements:
• Must be either a US citizen or a US permanent resident with a minimum of 3 years legal residency in the United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DoD instruction) and• Must have a favorably completed National Agency Check with Written Inquiries (NACI) or T1 investigation equivalent including a FBI fingerprint check prior to installation access.
To be considered for a favorable trustworthiness determination, the Contractor’s Security Representative must submit for all employees each of the following:
• SF-85 Questionnaire for Non-Sensitive Positions• Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)• Original Signed Release Statements
The contractor shall ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or T1 equivalent investigation, or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.
* Consult with your Command Security Manager and Information Assurance Manager for local policy when IT-III (non-sensitive) access is required for non-US citizens outside the United States.
DoD 8570.01-M Information Assurance Workforce Improvement Program. No Additional IA Certification Required X Information Assurance DoD 8570.01-M Required:
IA Certification Level: Resources with Privileged Access requires Technical Level 1
DoD Directive 8570.1 of 15 Aug 2004, Information Assurance Training, Certification, and Workforce Management DoD 8570.01- Manual of 19 December 2005, IA Workforce Improvement Program SECNAV Instruction 5239.3B of 17 June 2009, DON Information Assurance Policy SECNAV Manual-5239.2 of 29 May 2009, DON Information Assurance Workforce Management Manual to Support the Information Assurance Workforce Improvement Program
Computing Environment Certification: Cyber Security Certification
The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including-(1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M.(2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.
(a) Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.
(b) Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.
Proof of the above indicated IA certification and computing environment certification is to be provided for all contractor personnel along with the vendor quote. In addition to the IA certificate, active enrollment and participation in the certification maintenance program must be established prior to contract award to ensure the appropriate access can be secured by contractor resources. Questions and additional information requirements may be addressed by contacting the NAVSUP Business Systems Center Information Assurance Manager (IAM).
Certification shall be forwarded to: Kevin McNamara, Code 94NAVSUP Business Systems Center IAM 5450 Carlisle Pike, Bldg 409 Mechanicsburg, PA 17055Email: [email protected]
12.0 G ove rnm e nt Furn is h e d Equipment :
The government will provide work facilities to the on-site contractor. The government will provide computer hardware and software required and access to local telephones with long distance access when the contractor is acting on behalf of the government at the government site. If the contractor is supporting off-site, the government will provide GFE computers for access to government systems (if needed).
13.1 Qua lific at io n s/ E x p e r ie n ce :
The contractor resource(s) must either be able to obtain interim access due to a favorable review of the investigative questionnaire and advance favorable fingerprint results, or be able to obtain access due to a current favorably adjudicated investigation to enable the contractor to start performance immediately upon the period of performance start date.
This task order requires key personnel under this task as defined in Section 16.3 of the basic contract PWS. The Contractor shall provide to the COR and TA PII-redacted resumes of all key personnel to review and approve qualifications and experience requirements at a minimum of 15 days prior to onboarding.
The Contractor shall make no substitutions of key personnel unless the substitution is necessitated by illness, death, or termination of employment. The Contractor shall notify the Contracting Officer within 15 calendar days after the occurrence of any of these events and provide any necessary information. The Contractor shall submit the information to the Contracting Officer at least 15 days prior to making any permanent substitutions for any contractor personnel. No personnel substitutions will be executed without Government approval by the COR. The Contractor shall provide a detailed explanation of the circumstances
necessitating the proposed substitutions, complete resumes for the proposed substitutes, and any additional information requested by the Contracting Officer. All proposed substitutes must have qualifications that are equal to or higher than the qualifications required of the person to be replaced.
For all positions performing under this task order, the contractor resources shall have the technical experience as described in the PIRMDS2 Personnel Qualifications (attachment X) for all proposed Labor Categories. Additional qualifications and experiences described below for all proposed Labor Categories:
Functional Expert – Senior (Supply):□ At a minimum 9 senior resources are considered key personnel positions in the
following modules:o At a minimum 2 Inventory Management/Warehouse Management
resources are considered key personnel positionso At a minimum 2 Order Fulfillment and Allowancing resources are
considered key personnel positionso At a minimum 2 Procurement resources are considered key personnel positionso At a minimum 2 Supply Chain Management/Planning resources are
considered key personnel positionso At a minimum 1 Supply Master Data resources are considered key personnel
positions□ Prefer a minimum of 10 years of SAP experience□ Require a minimum of 5 years Navy ERP (SAP) experience within the past 10 years□ The designated key personnel shall possess Subject Matter Expert (SME) experience in
the applicable functional/module area listed below (in a Tier 3 environment is preferred):o Order Fulfillment
□ Minimum knowledge of: NALCOMIS, Shipbuilding, Transaction Item Reporting (TIR), Logistics Reassignment, Backorder Processing, Defense Logistics Management System (DLMS), Triology, IDOCs
o Inventory Management□ Minimum knowledge of: Commercial Asset Visibility (CAV) /
Commercial Asset Visibility - Organic Repairable Module (CAV-ORM), EH&S / HAZMAT, Defense Logistics Management System (DLMS), Electronic Retrograde Management System (eRMS), IUID, RFID, AIT,Stock (Plant vs. Project), Triology, IDOCs
o Warehouse Management□ Minimum knowledge of: Issues, Deliveries, Shipment, Receipts,
Materials movements, Warehouse/Plant/Storage Type/Bins functionality and configuration, IDOCs
o Materials Management / Procurement□ Minimum knowledge of: Commercial Asset Visibility (CAV) /
Commercial Asset Visibility - Organic Repairables Module (CAV-ORM) Readiness Suite, Workflow, Shipbuilding, ITIMP, Trilogy, DACS, SPS,SCES and EPS, Triology, IDOCs
o Supply Chain Management / Planning
□ Minimum knowledge of: FLIRR, Forecasting, DRP, CIF, Disposal, Quarterly levels, Federal Logistics Information System (FLIS), Logistics Reassignment, DLMS, TIR, IDOCs
o Supply Master Data□ Minimum knowledge and experience of: Readiness Suite, FLIS,
CIF, Logistics Reassignment, Supply Master Date, Vendor master, Annual Price Updates, Change notice, IDOCs
□ Key and non-key personnel shall have knowledge and/or experience of Navy ERP in the following areas:
o Knowledge and/or Experience of Navy ERP (SAP) financials postings, requirements, dependencies, and impacts.
o Experience in sustainment resource planning or work planning, and release scheduling activities supporting all of the following: system change requests, defects, customer reported incidents, system upgrades, system performance tuning and role updates and changes (in a Tier 3 environment is preferred).
o Experience in the application of functional and technical expertise to improve the performance of the business; resolution of functional and technical integration issues across SAP modules (in a Tier 3 environment is preferred).
o Experience in using Solution Manager to manage and test configuration / development effort through the production landscape
o Experience with SAP Technical and/or Functional upgrade efforts.o Experience in software development lifecycle surrounding requirements
gathering, analysis, design, development, documentation, test (unit, functional, integration, regression, stress, and user acceptance), implementation, and post production support of standard and custom business solutions supporting various SAP modules, such as ECC, BW, SCM, SRM, etc… (in a Tier 3 environment is preferred).
o Knowledge in new emerging technologies such as SAP HANA or equivalent.
Functional Expert – Senior (Finance):□ At a minimum 13 senior resources are considered key personnel positions
in the following modules:o At a minimum 2 Finance resources are considered key personnel positionso At a minimum 2 Asset Management resources are considered key personnel
positionso At a minimum 2 Funds Management resources are considered key personnel
positionso At a minimum 2 Projects Systems resources are considered key personnel
positionso At a minimum 2 Sales and Distribution resources are considered key personnel
positionso At a minimum 1 Workforce Management resource is considered a key
personnel positiono At a minimum 2 Controlling resources are considered key personnel positions
□ Prefer a minimum of 10 years of SAP experience□ Require a minimum of 5 years Navy ERP (SAP) experience within the past 10 years□ Expert knowledge and experience with Navy ERP and U.S. Federal
financial management processes
□ The designated key personnel shall possess Subject Matter Expert (SME) experience in the applicable functional/module listed below:
o Funds Management□ Knowledge and experience in Budgetary Ledger and USSGL posting
logic□ Experience in SAP GTAS implementation□ Experience in SFIS 10.0/MR compliance is highly preferred□ Experience with SAP Budget Control System and Availability
Control customization at a U.S. Federal agency□ 2 -3 Federal year-end closes performed
o Finance□ Knowledge and experience in federal financial systems and
interface support with DDEF, APVM/PPVM, DDRS, DTS, ADS□ Experience working with external partners, e.g. DFAS□ Experience with budgetary ledger and USSGL posting logic□ Knowledge and experience with SAP GTAS implementation□ Knowledge and experience with SFIS 10.0/MR compliance□ Knowledge and experience with multiple month-end closings for federal
agencieso Workforce Management
□ Experience with Workforce management/SAP HR in employee time tracking, ESS/MSS, SDA, payroll and reporting.
□ Experience highly preferred for interface support with Defense Civilian Pay System (DCPS), personnel management, training and qualifications.
o Sales and Distribution□ Experience with SAP billing and reimbursable funding, Resource Related
Billing (RRB), Budgetary Ledger and USSGL posting logic, Foreign Military Sales (FMS) Direct Cite, General Fund & Working Capital Fund.
□ Knowledge and experience with multiple month-end closings for federal agencies
□ Experience with a minimum of 2 -3 Federal year-end closeso Project Systems
□ Navy ERP Project Funding solution highly preferred, maintaining project structures, capturing costs and reporting.
o Controlling□ Navy ERP gross pay, Cost Redistribution Account (CRA), overhead
and labor processing, assessments, distributions, cost transfers and reporting.
□ Knowledge and experience with multiple month-end closings for federal agencies
o Asset Management□ Experience preferred with Navy ERP Acquire to Dispose business
process, intercompany and intracompany assets, asset workflow; asset depreciation and settlement.
□ General Equipment Construction in Progress (GE CIP) implementation at a Federal agency, highly preferred
□ Key personnel and non-key personnel shall have knowledge and/or experience of Navy ERP in the following areas:
o Experience in sustainment resource planning or work planning, and release scheduling activities supporting all of the following: system change requests,
defects, customer reported incidents, system upgrades, system performance tuning and role updates and changes (in a Tier 3 environment is preferred).
o Experience in the application of functional and technical expertise to improve the performance of the business; resolution of functional and technical integration issues across SAP modules (in a Tier 3 environment is preferred).
o Experience in development and configuration of various SAP modules, including but not limited to the following: Funds Management, Workforce Management, Asset Management, Controlling, Finance, Grants, Project Systems, Sales Distribution, etc… (in a Tier 3 environment is preferred).
o Experience with SAP Technical and/or Functional upgrade efforts.o Experience in software development lifecycle surrounding requirements
gathering, analysis, design, development, documentation, test (unit, functional, integration, regression, stress, and user acceptance), implementation, and post production support of standard and custom business solutions supporting various SAP modules, such as ECC, BW, SCM, SRM, etc… (in a Tier 3 environment is preferred).
o Knowledge in new emerging technologies such as SAP HANA or equivalent
ABAP Developer – Senior:□ At a minimum 2 resources are considered key personnel positions□ Senior Personnel :
o Prefer a minimum of 12 years of SAP experience in RICEo Require a minimum of 5 years Navy ERP (SAP) experience within the past
10 yearso Prefer a minimum of 3 years on SAP Fiori, SAPUI5 & SAP Gateway, SAP
Mobile Platform, and SAP Screen Persona 2.0/3.0o Prefer a minimum of 4 years experience in interface visual designo Prefer a minimum of 4 years experience with the use of the Axure
prototyping/mockup software tool□ The designated key and non-key personnel shall possess expert knowledge
and experience in all of the following:o Experience in SAP configuration and documentationo Experience with SAP integration through internet & mobile technologies
(iOS and Android mobile app design), on ABAP OO / and on the latest SAP technologies - SAPUI5, SAP Fiori, SAP HANA XS & SAP Screen Persona
o Technical experience in SAPUI5, SAP Fiori, SAP Gateway & ODATA, REST, XML, XSLT, and SOAP, HTML5, CSS, AJAX, JavaScript, jQuery, JSON,ABAP OO (specialized in development of complete new custom applications &
frameworks ), ABAP WebDynpro, ABAP/4, ABAP OO, RFC, BAPI, FM's,Enhancements, Scripts, ALV & BDC
o Knowledge and experience in inbound/outbound interface architectureo Experience developing integrations in WebMethods and MQ Serieso Experience in NetWeaver Portal, Supply Portal, Timekeeping Portal, BI
Portal and Federation between different Portals.o Experience in ABAP Workbench, Debug and SQL tracing tools.
□ Key and non-key personnel shall possess expert knowledge and experience in at least 2 or more of the following critical data management functionalities listed below:
o Experience in Web Dynpro JAVA, Web Dynpro ABAP, MVC Framework, Floor Plan Manager (FPM), NWDS, and NWDI
o Experience with Classic reporting / ALV, BDC, LSMW, BAPI, BADI, User Exits, ALE, EDI, RFC, IDocs, Data dictionary objects, Function Modules & Groups, Dialog Programming, Screen painter, Menu painter, Table creation, Search Help and Views, Java Web Dynpro, ABAP Web Dynpro, SAP Scripts, Smart Forms, BSP, Workflow and Data Migration.
o Knowledge and experience in SAP technical architecture, system level troubleshooting
o Experience in development of various SAP Workflow functionalitieso Experience in code, test, and analyze new applications and make changes to
existing applicationso Experience of HR development.o Experience in establishing global standards to ensure consistency across all Fiori
appso Experience in designing the information architecture, user interface and
user interactions for systemso Experience in developing low fidelity and high fidelity prototypes and be able
to evaluate the designs' usability through cognitive walkthroughs and heuristic reviews
o Experience in planning and executing other forms of usability evaluations including informal and formal usability tests
o Experience in cohesively working closely with other developers and analysts throughout the software development lifecycle
□ Key and non-key personnel shall have knowledge in the following, but not limited to:o Knowledge of data through Portal and reports for all environments – ECC,
BW SRM, Portal, BOBJ, NWBC, WebMethods, MDG and SCMo Knowledge of a wide array of IT activities and processes beyond SAPo Knowledge of object oriented programmingo Knowledge/experience of behavior based research programs to create
persona models and use cases.o Knowledge/experience of creating user flows, interactive prototypes, and
visual designso Knowledge/experience of design patterns, industry trends, and great approaches
to solve problemso Knowledge/experience as a creative problem-solver with a strong eye for detail
o Knowledge/experience, and understanding of responsive web development and design
o Broad knowledge of user profiles and personas and how to use them in design development and in a walkthrough
o Knowledge/experience of cascading style sheets, HTML5 and javascript development.
o Minimum of 4 years experience in Agile development methods preferred
Middleware Developer:□ At a minimum 2 resources are considered key personnel positions.□ Middleware resources require privileged access and require a PAA form and an SSBI.□ Senior Personnel :
o Prefer a minimum of 12 years of SAP experience and 5 years of WebMethodso Require a minimum of 5 years Navy ERP (SAP) experience within the past 10
years and 3 years of WebMethodso Prefer a minimum 8 years of experience in development and integration solutions
supporto Prefer a minimum 4 years of experience developing with Service Flows,
Adapter Connections, and Portlet technologieso Prefer a minimum 4 years of coding skills in Java (Java SE, Java EE, XML, XML
Schema, XSD,XSLT/XPath and JSON technologies) and SQLo Prefer a minimum 4 years of experience in developing SOAP/REST web serviceso Prefer a minimum 4 years of experience working with web services securityo Prefer a minimum 4 years of experience with transmission protocols (http/s, ftp/s, sftp)
□ Key and non-key personnel shall possess expert knowledge and experience in the listed below:
o Expert level knowledge of Software AG WebMethods 9.x Integration Server and related technologies
o Experience documenting and communicating integration designs aligned to business requirements
o Experience designing queries and working with standard object/relational databases such as Oracle, MS SQL
o Experience with Source control/Bug Tracking/Automated Build tools Jira and Jenkins
o Software AG WebMethods Integration Server performance tuning experience a plus□ Key and non-key personnel shall have knowledge/experience in the following, but not
limited to:o Experience with CA API Gateway and/or IBM WebSphere MQ is preferred.o Strong Knowledge of SOAP, REST, JMS architecture Concepts and PUB/SUB
Patterno Strong knowledge of web services securityo Strong knowledge of Java SE, Java EE, XML, XML Schema, XSD,
XSLT/XPath and JSON technologies
SAP Security Management:□ At a minimum 4 senior resources are considered key personnel positions□ Senior personnel: Minimum of 7 years of SAP experience□ Minimum of 3 years Navy ERP (SAP) Roles Security and/or User Management
experience within the past 7 years□ Thorough knowledge in SAP Infrastructure, with emphasis on Roles Security, role
design, role authorizations□ Minimum of 3 years of experience in an SAP environment supporting User Access
Requirements, User Provisioning, SAP Roles development, and SAP Roles Management including the use of SAP Governance, Risk and Compliance (GRC) suite
□ Documentation skills to include technical writing, standard operating procedures, functional design specifications
□ Microsoft Office Suite to include Access and Excel□ Develop, test, and maintain Navy ERP (SAP) roles□ Troubleshooting roles security issues and providing customer support□ Experience in development lifecycle surrounding requirements gathering, analysis,
design, role development, documentation, test (unit, functional, integration, regression, stress, and user acceptance), implementation, and post production support of standard and custom roles supporting various SAP modules.
□ Senior personnel team must collectively possess experience and knowledge of Roles Security activities including but not limited to:
o AVM Greenlighto CUA and IDMo Transport managemento Audit, audit readiness, roles security related audit topics, separation of duties, user
access review, risks, GRC rule set, etc.o GRC configuration, patching, OSS note analysis and supporting technical updateso Business Objects, Webi, and portal role developmento Role development experience and general Navy ERP experience in ECC, BW,
SCM, SRM, Document Builder, Solution Manager, GRCo Knowledge in new emerging technologies such as SAP HANA or equivalent
□ Basic-Level personnel – shall follow the PIRMDS2 Personnel Qualifications for User Management labor category
Data Warehouse Analyst:□ At a minimum 2 resources are considered key personnel positions□ Senior Personnel:
o Prefer a minimum of 10 years of SAP experienceo Require a minimum of 5 years Navy ERP (SAP) experience within the past 10 years
and/or minimum 3 years of Navy ERP (SAP) data management (DM) experience□ Intermediate Personnel:
o Prefer a minimum of 5 years of SAP experienceo Require a minimum of 2 years Navy ERP (SAP) experience within the past 10
years and/or minimum 1.5 years of Navy ERP (SAP) DM experience□ The designated key personnel shall possess Subject Matter Expert (SME) experience in
the applicable functional area listed below:o Data Management
Including but not limited to:□ Data Service Requests□ Integration and Coordination (including supporting PMO, EA, Functional
Teams, Technical Teams, Tier II)□ Documentation (including SOPs, strategy documents, white papers, …)□ Audit and Compliance
o BI (including BW, BODS, BAPI)
o Navy ERP Governance-Approved Data Management Projects□ Key personnel and non-key personnel shall have experience in at least 2 or more of the
following critical data management functionalities within Navy ERP (SAP):o SAP T-Codes, Applications, and Toolso BI (including BW, BODS, BAPI)o Data Archivingo Data Migrationo Data Conversion and Data Loadso Data Distribution o
Data Maintenance oData Governance oData Analysis
o Data Extracts and Reportingo Data Mappingo Data Validationo Data Reconciliationo Data Refreshes and Upgrades
□ It is preferred that Key personnel and non-key personnel have knowledge and/or experience of data management functionalities within Navy ERP (SAP):
o BI (including BW, BODS, BAPI)o ETLo Data Archivingo Data Migrationo Data Conversion and Data Loadso Data Distribution o
Data Maintenance oData Governanceo Data Analysiso Data Extracts and Reportingo Data Mappingo Data Validationo Data Reconciliationo Data Refreshes and Upgradeso Relational and Object-Oriented Databaseso Various Programming Languages (e.g. JAVA, SQL, C, C+, …)o Various Data Management Tools (e.g. MDG, Attunity Gold Client Software, SAP
Archiving, Oracle, Informatica, …)o Various Data Modelling Tools (e.g. ERWIN, SAFYR, SADIE, …o Various Data Reporting Tools (e.g. Cognos, Crystal Reports, SAS, …)o Various SAP Toolso Configuration and Release Management Tools (e.g. Dimensions, HEAT, QC)o ERP Functional and Business Knowledgeo Software, SAP Archiving, Oracle, Informatica, …)o New emerging technologies such as SAP HANA or equivalent
Data Warehousing Programmer (Interface Control):□ At a minimum 2 resources are considered key personnel positions□ Senior Personnel:
o Prefer a minimum of 10 years of SAP experience
o Require a minimum of 5 years Navy ERP (SAP) experience within the past 10 years
□ Mid-Level Personnel:o Prefer a minimum of 5 years of SAP experience within the past 5 yearso Require a minimum 3 year Navy ERP (SAP) experience within the past 5 years
□ The designated key personnel shall possess Subject Matter Expert (SME) experience in the applicable functional area listed below:
o Interface Management Including but not limited to:
□ Interface Control□ Integration and Coordination
□ PMO Support (including ICAs, MOAs, ATOs, Policies)□ EA Support (including SV-1, SV-6, data modelling, data mapping)□ Functional Team Support□ Technical Team Support (including MW, RICE, TAT, BASIS)□ Tier II and Partners Support
□ Interface Management Documentation (including SOPs, strategy documents, white papers, …)
o Audit (1 Mid-Level SME)o Compliance (including DLMS, SFIS, JITC)
□ Key personnel and non-key personnel shall have experience in at least 2 or more of the following critical interface life cycle management functionalities within Navy ERP (SAP):
o Requirements Analysiso Documentation Creation and Maintenance (ICAs, MOAs, Policies, SOPs, strategy
documents, white papers)o Interface Monitoring and Error Resolutiono Interface Reconciliationo Interface Migrationo Interface Testing and Validations (cycle testing, end-to-end testing)o Compliance (DLMS, SFIS, JITC)o Interface Deployment (creation, connectivity testing)o Interface Integration (including supporting PMO, EA, Functional Teams,
Technical Teams, Tier II)o Interface Production Support and Error Resolutiono Interface Data Mappingo Audit and Compliance
□ It is preferred that Key personnel and non-key personnel have knowledge and/or experience of interface life cycle management functionalities within Navy ERP (SAP):
o Interface Data Mappingo Root Cause Analysis and Troubleshootingo Interface Reconciliationo DLMS/EDIo DLMS Compliance (ADCs/PDCs)o Compliance (SFIS, JITC)o MILSTRIP/MILSTRAPo IDOC Processes and Error Resolutiono WebMethods, MQ Serieso ETLo Navy and DoD Partner Systems
o Navy and DoD Standards and Regulationso BW Reportso Various SAP T-Codes, Applications, and Tools (e.g. ZMON, ZRMIM0025,
Solution Manager, …)o Configuration and Release Management Tools (e.g. Dimensions, HEAT, QC)o Interface and Data Flowcharts, Diagrams, and Modelso ERP Functional and Business Knowledgeo New emerging technologies such as SAP HANA or equivalent
Information Systems Training Manager:□ At a minimum 1 Training resource is considered a key personnel position.□ Senior Personnel: Minimum 5 years of experience in Ancile uPerform tool on both the
server and client side and minimum 5 year experience with the SAP Learning Solutions (LSO) tool/equivalent tool
□ The designated key personnel shall possess Subject Matter Expert (SME) experience in the applicable functional areas listed below:
o Ancile uPerform (Version 5.20 or higher)□ Serves as uPerform System Administrator□ Serves as uPerform Publishing Administrator□ Creating and maintaining course templates□ Creating, maintaining, and publishing course content□ Creating and maintaining simulation files□ Creating and maintaining audio files□ Modernizing course content from Ancile Info Pak to Ancile uPerform□ uPerform project administration□ uPerform Workflow
o SAP LSO and SAP Authoring Environment (SAP AE_RE) or equivalent□ Master repository architecture/structure/hierarchy□ Master repository and permissions□ Managing Work Area□ Publishing content□ Authoring content□ Distribution of content for use/consumption□ Reporting□ SAP LSO-relevant T-Codes□ Imparting SAP Training qualifications□ Trouble-shooting connections, Repository Explorer,
o HEAT□ Identify, analyze, provide root cause analysis, and resolve customer issues
related to uPerform and SAP LSOo BPPs
□ Review business process changes and identify impacts to training courses□ Update and republish courses
□ Knowledge in new emerging technologies such as SAP HANA or equivalent
Data Architect:□ At a minimum 1 Data Architecture resource is considered a key personnel position□ Minimum of 3 years of Data Architecture experience and minimum 1 year ERWIN data
architecture tool experience within the past ten years (1).□ Knowledge of SAP business processes and table use.
□ Knowledge of SAFYR tool use.□ Expert experience using Excel spreadsheets including the use of formulas and data
manipulation.□ Knowledge of the Department of Defense Architecture Framework (DoDAF) and the
development of Data and Information Models.□ Knowledge in new emerging technologies such as SAP HANA or equivalent
Systems Administrator:□ At a minimum 2 senior resources are considered key personnel positions.□ Senior Personnel: Minimum of 7 years of SAP and 3 years of Navy ERP Tivoli
experience□ Intermediate Personnel: Minimum of 3 years of Tivoli or comparable job scheduling
tool and 1 year of SAP experience□ These personnel shall possess knowledge and experience in the listed below:
o Scheduling, testing, and managing SAP jobs through the Tivoli or comparable job scheduling tool
o Monitoring SAP jobs through the Tivoli or comparable job scheduling tool around the clocko Document, report, escalate, triage job failures to the appropriate teamso Assessing impacts to scheduled jobs due to external forces (e.g. hardware or application failure,
interface outages, etc.)
Systems Engineer :□ At a minimum 2 senior resources are considered key personnel positions. □ Senior Personnel: Minimum of 5 years of Navy ERP BASIS and 10 years of SAP
experience□ Mid-level Personnel: Minimum of 3 years of Navy ERP BASIS and 5 years of SAP
experience□ These resources require privileged access and require a PAA form and an SSBI.□ These personnel shall possess knowledge and experience in the listed below:
o Maintain database integrityo Perform database routine maintenance such as UNIX and/or OS patching, table indexing, change
pointers, etc.o Perform technical upgrade
o Perform analysis of, document, report, escalate, triage and resolve database performance issueso Monitor and maintain database performanceo Monitor, maintain, and enhance middleware technologyo Analyze, design, build, and/or configure activities necessary for the initial build or periodic refresh
of components for the SAP environmentso Perform / Execute COOP for backup and recovery of production and non-production
environmentso Perform / Execute environment refreshes of production and non-production environments using
various technologies, tools, methodologieso Develop / Maintain project schedules for various consecutive projects / effortso Manage CHARMs and Transports through Solution Manager or applicable tool to migrate SAP
ERP changes through the non-production and production environmentso Maintain / update printing tableso Maintain / update / create middleware IDs in non-production and/or production environments to
support various projects / efforts
IT Systems Solution Architect:□ At a minimum 2 resources are considered key personnel positions.
□ Senior Personnel: Minimum of 3 years of Navy ERP Technical Architecture and 7 years of SAP experience
□ These resources require privileged access and require a PAA form and an SSBI.□ These personnel shall possess knowledge and experience in the listed below:
o Manage and enhance/update/upgrade technical infrastructure architecture (e.g. hardware, software, network, data components, etc.) for SAP ERP operating environment
o Diagnose and mitigate / correct technical issues that adversely impact the availability, throughput or performance of the production and/or non-production systems
o Perform analysis of, document, report, escalate, triage and resolve database and/or system issueso Perform / Execute environment refreshes of production and non-production environments using
various technologies, tools, methodologieso Develop / Maintain project schedules for various consecutive projects / effortso Manage and enforce to ensure technical infrastructure architecture satisfy all applicable cyber
security requirements for defined / mandated for the DoD and/or the DoN CIOo Monitor and maintain effectiveness of all technology and processes to ensure a logical and
physical integrity of the production and non-production systemso Manage and upgrade, when appropriate, all components applicable to a SAP ERP system to a new
version, closest to the current release levelso Work with data centers and/or various other service providers to manage / maintain an good
operational posture for the production and non-production systemso Perform / Execute COOP for backup and recovery of production and non-production
environmentso Monitor system performance to identify and forecast performance bottlenecks and take the
necessary steps to improveo Manage/maintain and enhance/update vendor procurement gateway technology to support the
Navy ERP Grants functionality
Quality Assurance Analyst:□ At a minimum 2 senior resources are considered key personnel positions. □ Minimum of 2 years of Navy ERP Regression Testing and 2 years of SAP experience□ These personnel shall possess knowledge and experience in the listed below:
o Execute regression test scripts within a Quality Assurance (QA) environment in a manual and automatic fashion to support scheduled and unscheduled releases
o Record test results within the applicable test tracking toolo Review and load test plans into test tracking tool to validate functionality and requirementso Review design and technical packages to ensure quality and the proper processes are followedo Manage / Coordinate regression test events with program stakeholderso Develop / Update / Maintain automated test scripts based on test plans submitted by the
systems integratorso Perform upgrade / maintenance tasks of a test tracking toolo Perform analysis of, document, report, escalate, triage and resolve issues / defects / bugs
found during regression testingo Provide testing metrics to show progress of each regression test evento Create, update, and maintain test strategy, standard operating procedures, processes,
policies, etc. surrounding regression testo Utilize WorkSoft technology to execute automated test scripts (CBTs).
14.0 Non-Disclosure Agreement:
The Business Sensitive Information Non-disclosure Agreement is required for this order. Refer to DFARS 252.204-7000, Disclosure of Information, and DFARS 252.204-7003, Control of Government Personnel Work Product.
15.1 NAVSUP Business Sys t e m s Center Procedures for Contractor Access/Visi t Authorization R e qu es t (VA R ) :
□ A company letter to the Technical Assistant (TA) containing the following information:□ Contract Information
o Contract Numbero Date Issuedo Date of Expirationo Name and phone number of the TAo Purposeo Systems to be accessedo Files/Data requiredo Type of access required (i.e., inquiry/update/delete)o Equipment to be used with location and mode of access identifiedo Security point of contact including address and phone number
□ Information for all contractor employees requesting access, to include:o Full Nameo Job Titleo Date of Birtho Place of Birtho Citizenshipo Social Security Numbero Naturalization Number (if applicable)o Type and date of Security Investigation.o Government Clearance Level (if applicable)o Valid email address for the Contractor’s employee
□ Appropriate Company Official's signature
2. A System Authorization Access Request Navy (SAAR-N) form (OPNAV 5239/14) with original signatures and a copy of the DOD Annual IA Awareness Training Completion Certificate for each contractor employee sent to the TA.
16.0 P oi nt s of C o nta c t:
Technical Assistant (TA): Organization/Code: NAVSUP Business Systems Center (Code 98) Address: 5450 Carlisle Pike, Bldg 407
Mechanicsburg, PA 17055
COR/Invoice Acceptor: Organization/Code: NAVSUP Business Systems Center (Code 9113) Address: 5450 Carlisle Pike, Bldg 409
Mechanicsburg PA 17055