N6426725R0354.pdf

CODE

(Hour)

PAGE(S)

until 05:00 PM local time 24 Mar 2025

X

A X B X C X D

EX

X

G F 62 - 76

77 - 89 X H 90

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

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

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

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

1 90

(If other than Item 7)

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

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

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

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N64267 8. ADDRESS OFFER TO

See Item 7

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

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

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 5

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

6 - 39

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

41 - 42

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 44 - 47 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 48 - 52 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

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

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

13. DISCOUNT FOR PROMPT PAYMENT

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

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

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

FACILITY

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

SOLICITATION, OFFER AND AWARD

X

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

PART I - THE SCHEDULE

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

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

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

AWARD (To be completed by Government)

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

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

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

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

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

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

53 - 60

PART II - CONTRACT CLAUSES

NAVAL SURFACE WARFARE CENTER CORONA DIV.

1999 FOURTH STREET BLDG 510

NORCO CA 92860

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

24 Mar 2025

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6426725R0354

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

1000 347,728 Labor

Hours

Base Period Labor

CPFF

FOB: Destination

BRAND NAME/SOLE SOURCE: SS

PSC CD: DA01

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

1100 276,832 Labor

Hours

Option Period Labor

CPFF

FOB: Destination

FIXED FEE

TOTAL EST COST + FEE

2000 1 Lot Base Period ODC

COST

FOB: Destination

2100 1 Lot Option Period ODC

COST

FOB: Destination

Base Period CDRLs

Not Separately Priced FOB: Destination

Option Period CDRLs

Not Separately Priced FOB: Destination

CLAUSES INCORPORATED BY FULL TEXT

B-216-H006 FEE TABLE (NAVSEA) (MAR 2019)

Labor CLIN Labor Hours Cost Per Hour*

Fee Rate Per Hour*

Loaded Hourly Rate

1000 347,728 TBD TBD TBD

1100 276,832 TBD TBD TBD

*The offeror shall divide the proposed fee for each CLIN by the quantity of labor hours indicated to complete the table. Fee is calculated based on cost less FCCOM; if FCCOM is proposed, necessary columns may be added.

In the event of any inconsistency between the above table and the CLIN pricing, the CLIN pricing shall take precedence.

(End of text)

B-231-H001 TRAVEL COSTS (NAVSEA) (OCT 2018)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its actual travel costs in accordance with FAR 31.205-46. The travel costs to be reimbursed shall be those costs for which the Contractor has maintained appropriate documentation and which have been determined to be allowable, allocable, and reasonable by the Procuring Contracting Officer, Administrative Contracting Officer, or their duly authorized representative.

(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.

(c) Relocation costs and travel costs incidental to relocation are allowable to the extent provided in FAR 31.205-35;

however, Procuring Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incidental to relocation.

(d) The Contractor shall not be reimbursed for the following daily local travel costs:

(i) travel at U.S. Military Installations where Government transportation is available,

(ii) travel performed for personal convenience/errands, including commuting to and from work, and

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the Contractor's or employee's convenience.

B-232-H005 PAYMENTS OF FEE(S) (LEVEL OF EFFORT)--ALTERNATE I (NAVSEA) (OCT 2018)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts.

(b) The Government shall make payments to the Contractor, subject to and per the clause in this contract entitled "Fixed Fee" (FAR 52.216-8) or "Incentive Fee", (FAR 52.216-10), as applicable. Such payments shall be submitted by and payable to the Contractor pursuant to the clause of this contract entitled "Allowable Cost and Payment" (FAR 52.216-7), subject to the withholding terms and conditions of the "Fixed Fee" or "Incentive Fee" clause, as applicable. Fee paid per hour shall be based on total fee dollars divided by total hours to be provided. Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract.

CLAUSES INCORPORATED BY FULL TEXT

B-232-H006 LIMITATION OF COST OR LIMITATION OF FUNDS CLARIFICATION (NAVSEA) (OCT 2018)

The clause entitled "Limitation of Cost" (FAR 52.232-20) or "Limitation of Funds" (FAR 52.232-22), as appropriate, shall apply separately and independently to each separately identified estimated cost.

Section C - Descriptions and Specifications

SECTION C

1. Contract Title. Navy Maritime Maintenance Enterprise Solution (NMMES) Sustainment and Modernization Support

2. Background.

Naval Sea Systems Command, Digital Program Office (DPO SEA03D3) has program management responsibilities for the development and maintenance of shore based ship maintenance and logistics systems. DPO SEA03D3 has the lead for ensuring an affordable maintenance solution is in place and operating worldwide in support of the Ship Maintenance Community (SMC). In support of this goal, DPO has the requirement for Information Technology (IT) support to provide sustainment and development/modernization solutions for current and future GOTS/COTS systems. This support focuses on rapid deployment, flexibility, and the use of common open operating architecture where applicable to meet SMC needs. A current list of DPO Systems is included in Attachment 01 – System Information, which may be unilaterally revised by the Government during contract performance. Systems are generally grouped into two categories; 1) Ship Maintenance (SM) Systems and 2) Ship Lifecycle Management (SLM) Systems. Within the SM group of systems are Enterprise Systems and Local Systems, abbreviated as SM-E and SM-L, respectively.

3. Objective.

The performance objective, standards, and assessment plan described below are applicable to the total scope of services being performed under this Contract.

3.1 Performance Objective: The objective of this procurement is for the contractor to provide operations support and sustainment services for systems engineering, testing, and evaluation of hardware and software information technology systems, hardware design, procurement assistance, system integration, software maintenance (i.e.

upgrades, fixes, and coding repairs), data center operations support, and Information Technology (IT) facility management. The work under this Contract will include program and project management support, development of end items resulting from maintenance activities, and life cycle support for existing or proposed solutions. The contractor shall provide support services to ensure the successful programming (for the purpose of sustainment), testing, training, deployment, implementation, and operation of Navy Shore Based Maintenance systems managed by DPO. There are currently 79 information technology systems managed by DPO. Future technological refresh periods and application rationalization efforts may alter this number. Additionally, Facility Equipment Maintenance (FEM) sustainment and modernization effort is part of the objective of this procurement. Amplifying technical instructions may be issued under a separate tailored Technical Instruction (TI).

3.2 Performance Constraints: The contractor is required to adhere to applicable guidance contained in the SEA 03D3 Program Management Plan for Information Technology and all subsidiary plans (See Exhibit B-1). This will be referred to as the DPO PMP for future reference. In addition, the contractor must adhere to any and all applicable statutes and Department of Defense (DoD) and Department of the Navy (DoN) rules, regulations, and policies.

Therefore, contractor personnel assigned to this effort shall have and maintain expertise in applicable statues and DoD and DON information technology related rules, regulations, and policies.

4. Scope.

Navy Shore Based Maintenance IT solutions encompass a range of capabilities from systems in sustainment to new, emerging net centric technologies. As a result, the contractor is required to assist the government in providing IT solutions for activities throughout all operating levels of all customer organizations in support of all functional requirements including Command and Control (C2), Intelligence, and Mission support areas, and to all elements of the GIG. The footprint of these systems is global in nature but concentrated around the Navy’s Naval Shipyards (NSY), Intermediate Maintenance Facilities (IMF), Regional Maintenance Centers (RMC), and Ship Repair facilities (SRF). The contractor shall assist the government by furnishing all personnel and managed services needed to satisfy the worldwide development, deployment, operation, maintenance, and sustainment requirements of its customers. Services and support anticipated under this Contract exist within the scope of the 13 task areas identified below:

* Task 1 - Enterprise IT Policy and Planning

* Task 2 - Performance Benchmarking

* Task 3 – Business Process Reengineering (BPR)

* Task 4 - Requirements Analysis and Software Programming

* Task 5 – Software research and Prototyping

* Task 6 - Information and Software Engineering

* Task 7 - Product Integration

* Task 8 - Test and Evaluation (T&E)

* Task 9 - Asset Management

* Task 10 – Information Assurance Certification and Accreditation

* Task 11 - Installation Support

* Task 12 – Data Center Support for Programming and Testing

* Task 13 – System Administration, Database Management, Help Desk Support, and Production Operations

5. Performance Requirements.

5.1 Task 1 - Enterprise IT Policy and Planning. The contractor shall provide assistance in the technical analysis and assessment of policy and aid in the development of organizational plans and program management activities.

The contractor shall be familiar with DoD and DoN acquisition, budgeting, and investment management policies and regulations for Defense Business Systems (DBS).

5.1.1 Subtask 1--Policy. The contractor shall provide technical support services and assistance to customer organizations and assess IT policies, standards, guidelines, and procedures to ensure a balance of security, readiness, and operational requirements. The contractor personnel working on this effort shall be familiar with and shall maintain an expertise in DoD and DoN Acquisition policies and directives, Information Assurance (IA) requirements, Certification and Accreditation (C&A), Navy Information Dominance Approval System (NAV-IDAS) process, DoD Architecture Framework (DoDAF), DoD and DoN organizational hierarchy and chain of command.

5.1.2 Subtask 2--Planning. The contractor shall review, draft, and make recommendations regarding consolidation of strategic, management, and operational plans, including requirements definition and mission planning. This will include providing input, analyses, and recommendations to the overall program Enterprise Architecture (EA) Plan, as well as for any lower-level supporting plans. The contractor’s assistance in the development of plans shall be in accordance with the DON Architecture Development Guide or other applicable guidance as it applies to the requested document.

5.1.3 Subtask 3--Process Management. The contractor shall participate in and assist the Government in the review, re-engineering, and management of technical and business processes such as advanced planning, financial reporting, engineering, solution fielding, strategic and operational planning, engineering, training, operations, and customer support. Processes shall be in accordance with the DPO Program Management Plan (PMP). More detail provided in CLIN 0003 (Task 3) – Business Process Reengineering.

5.1.4 Subtask 4-- Audit Assistance – The contractor shall provide program and quality audit assistance to the government. Establish, maintain, and conduct audit processes and procedures for government projects. Provide assessments during the audit process and provide inputs to government management.

5.1.5 Subtask 5-- Program and Project Management Support Services. The contractor shall provide program and project management support functions, including:

5.1.5.1 Security and Regulatory Compliance. The contractor shall provide assistance to the program office in support of security and regulatory compliance. (Also see CLIN 0001 (Task 1)0: Security Engineering Certification and Accreditation.)

5.1.5.2 Document Generation. The contractor shall provide systems engineering support services to draft, review, revise, and deliver documents required by the CDRLs in this Contract. The contractor shall provide detailed meeting minutes at the completion of all meetings between contractor and PMO, as well as for meetings with other Program

Managers. The contractor shall develop such documentation and documentation resulting from the contractor’s studies, analyses, assessments, system implementations and architectures, and engineering design activities. Such documentation may include subject matter originated by the contractor as well as Government-provided topics and information. (CDRL A001-A024)

5.1.5.3 Risk Management. The contractor shall support the government’s Risk Management Plan for the identification, assessment, prioritization, handling, and monitoring of contractor performance, cost, and schedule risks under this contract. Additional Risk Management Plans may be required for individual projects or efforts. The contractor shall be responsible for ensuring appropriate risk handling actions as detailed in the Risk Management Plan are completed. The contractor shall provide requested information and presentation material to the government for the approval and the periodic review of its risk management. This will include cost estimates associated with mitigation plans, mitigation plan progression, changes in status, metrics, triggers, or trends and other related information. The contractor may use the risk matrix and probability or impact criteria provided by the government.

Additionally, the contractor shall input risks into the government provided risk management tool and shall update the tool in accordance with the government Risk Management Plan which is provided as Exhibit B-5. (CDRL A019, A021)

5.1.5.4 Performance Measurement – The contractor shall assist the Government management team in the analysis and maintenance of project financial and schedule data in support of project performance analyses applied to Government projects for shore based ship maintenance and logistics information technology systems. More information is provided in Section 7 – Performance Standards.

5.1.5.5 Business Case Analysis – The contractor shall perform business case analyses on proposed projects or initiatives. Business case analysis efforts shall follow the DoD Product Support Business Case Analysis Guidebook or DoN Standard Business Case Analysis Template published by the DoN Chief Information Officer (DoN-CIO), but be commensurate with the size and scope of the project being proposed. Business Case Analysis should also include necessary software cost estimating activities.

5.1.5.6 Government Reporting Schedule – The contractor shall assist in the tracking and execution of government reporting and project schedules. The contractor shall provide estimates on schedule validity and determine the impacts of deviations from the current plan. The contractor shall provide mitigation plans and options based on input from government management.

5.1.6 Subtask 6-- Software Direction Policies. The contractor shall support procurement activities for software products identified by the government. The contractor shall support organizations with the responsibility for determining the strategic use of software products.

5.2 Task 2 - Performance Benchmarking. The contractor shall provide support for program, functional, and technical baseline analyses as well as evaluate existing Enterprise Architecture (EA) and configuration data metrics.

The contractor shall have knowledge about and expertise in the Department of Defense Architecture Framework (DoDAF) Version 2.02 and be familiar with development and analysis of the relevant artifacts.

5.2.1 Subtask 1-- Program Benchmarking. The contractor shall review and evaluate functional and technical programs for integration implications. The contractor’s review and evaluation shall include factors such as operational scope, functional and process relationships, business practices, resource requirements, and cost impacts and may include the development of All View (AV), Operational View (OV), Systems and Services View (SV), and Technical Standards View (TV) products in accordance with DoDAF requirements. (CDRL A006, A019)

5.2.2 Subtask 2-- Functional Benchmarking. The contractor shall review, evaluate, and report to the Government its findings and recommendations on defined work processes and information needs of users within and across the functional area being examined. This effort shall include functional and cross functional requirements definition, functional descriptions, functional architectures, and requirements validation. The contractor shall facilitate the development and review of functional requirements stemming from changes in the project management, resource management, financial management, and material management business processes. The contractor shall document, analyze, and report on differences in the way common functional operations or processes are executed or interfaced, benchmark these processes against best commercial practices, identify existing “as-is” processes and data, and document known problems in existing processes and data that the contractor recommends should be corrected to provide a functionally adequate standard. The contractor shall recommend data processes, interfaces, and data baselines that together meet the process and associated information needs of the functional activity. (CDRL A006, A019)

5.2.3 Subtask 3-- Technical Benchmarking. The contractor shall examine current and emerging technologies, systems, and services for effectiveness or potential to support customer needs and provide recommendation to the Government. These technologies/systems/services may include legacy systems or migration to new technologies.

The contractor shall analyze the business case of proposed application alterations and changes to current business processes and provide recommendations to the Government. For those alterations and changes approved by the Government, the contractor shall provide oversight for implementation of the changes to corporate software systems. (CDRL A006, A019)

5.2.4 Subtask 4-- Benchmarking Tools and Methods. The contractor shall develop new or modify existing tools and methods to enable a disciplined process of benchmarking. Examples include templates, checklists, models and guidelines. The contractor shall document and submit to the Government for approval, proposed changes to a process manual. The contractor shall write, review, and submit recommended changes to corporate NAVSEA Instructions and Manuals that require modification due to project management process changes. The contractor shall assist users with integration of analytical instrumentation such as metric recording tools with corporate applications to document system health. (CDRL A006, A019, A024)

5.2.5 Subtask 5-- Baseline Definition. The contractor shall identify the baseline of existing support for the functional area or activity either being supported or for which support is contemplated. These efforts include business systems analyses of functions and the inventory of support tools and their use. The contractor shall assist in the performance of the initial steps of establishing or reviewing operations, processes, and data and information baseline for the functional or technical activity.

5.2.6 Subtask 6-- Capture Current Program Metrics. The contractor shall capture, compile, and report metrics for each system. The metrics shall be those needed to analyze reliability, usage, and size data and to improve the operational availability of the system. The metrics may include, for example, help-desk call volume, trouble ticket type volume, lines of code, function point analysis, number of interfaces, number of requirements, execution time, system memory and processor load, and program load time. Additionally, the contractor shall support the development of Service Level Agreement (SLA) metrics based on benchmark results. (CDRL A019, A024)

5.2.7 Subtask 7-- External Interfaces and Data Flow. The contractor shall document each external interface, including a description of the service, the classification of the data, the ports used, the protocol used, the direction (inbound, outbound, or both), whether it is Navy-Marine Corps Intranet Unclassified Network Protection Policy (UNPP) compliant, the service host name and any requirement for cross domain solution (cross-domain solutions require additional documentation). The contractor shall provide data management and analysis support. (CDRL A011, A019, A024)

5.2.8 Subtask 8-– Configuration Management (CM). The Contractor shall provide configuration management services for all PMO applications and products. The contractor shall utilize the NMMES Software Development Lifecycle (SDLC) toolset to perform configuration management activities in accordance with the NMMES Configuration Management Plan provided as Exhibit B-3. At this time, the NMMES SDLC toolset consists of Serena Dimensions (Configuration Item Repository), Serena Business Manager (Configuration Management and Workflow), IBM Rational Rhapsody (Systems Requirements Specifications), IBM Rational DOORS (Requirements Management and Traceability), and HP ALM and UFT (Test and Defect Management and Risk Management). The contractor shall provide updates to the NMMES Configuration Management Plan, maintain applicable configuration items through the entire product lifecycle, provide training on CM tools and processes, and provide applicable configuration metrics to the management team. The contractor shall be responsible for migrating configuration items from legacy tools and storage locations to the DPO SDLC toolset. (CDRL A019, A024)

*NOTE: Access to the DPO SDLC tools will be controlled by the government. System access will be based on available licenses. Licenses are shared by both government and contractor personnel and are not unlimited. System access will be allocated based on contractor and government functional needs. Additional licenses may be purchased if deemed necessary by the government to satisfy program and project requirements.

5.3 Task 3 - Business Process Reengineering (BPR). The contractor shall assist in conducting BPR activities associated with the Shore-based maintenance and logistics systems to include: process improvement, lean events, and formal BPR efforts. The contractor personnel performing this effort shall be familiar with, and have and maintain expertise in, DoD and DoN BPR guidance.

5.3.1 Subtask 1-- Process Improvement. The contractor shall provide support to manage, train, deploy, implement, evaluate, report on, and maintain Lean and other Continuous Process Improvement projects and to provide services required to provide full lifecycle support to include developing recommended business concepts and aligning those business process concepts with IT defect corrections and IT improvements. The contractor shall assess, evaluate, and report on activity efforts to achieve productivity improvement goals. The contractor shall perform and report on engineering feasibility studies and analyses including; statistical research, reliability and maintainability analyses, cost benefit analyses, data collection, and field investigations in order to assess systems, equipment, and organizational performance factors. (CDRL A007, A019, A024)

5.3.2 Subtask 2-–Lean Events. The contractor shall provide a Site Integrator to support Lean Six Sigma and other continuous improvement initiatives. The Site Integrator shall support Executive Planning Sessions, Value Stream Analysis, Rapid Improvement Events, and other Lean events. Support includes assisting LEAN Implementers in pre-event and post-event procedures, as well as supporting the Lean event itself, and providing documentation on the new process and the associated implementation strategy, facilitating and providing consultation during lean events, analyzing the impact of proposed Lean functional enhancements on business processes and providing cost estimates to implement the change(s) recommended by the Lean event participants. (CDRL A019)

5.3.3 Subtask 3-- Formal BPR. The contractor shall participate in formal BPR efforts in support of new developments. BPR is required before any new government IT procurements can be authorized. The contractor shall align the formal BPR efforts with the requirements in the DoD 5000.02 guidance. (CDRL A007)

5.4 Task 4 - Requirements Analysis and Software Programming. The contractor shall perform requirements analysis and software programming/technical upgrade/break-fix coding activities in accordance with the NMMES Systems Engineering Plan (SEP). The SEP contains requirements associated with performing programming and maintenance activities on the NMMES suite of information technology systems. The contractor is required to use the DPO Software Development Life Cycle (SDLC) tool set when performing all programming and modernization work. In general, software programming will only occur when necessary for operations and maintenance related activities. The contractor shall perform requirements analysis activities in accordance with the NMMES Systems Engineering Plan (SEP) provided at Exhibit B-2. The SEP contains the technical requirements associated with performing programming and maintenance activities on the NMMES suite of information technology systems. The requirements in this plan will be tailored by the government for individual programs or projects based on their continual cost and risk stature. The requirements listed below contain the high level tasks required to execute effective requirements analyses and software programming activities.

5.4.1 Subtask 1-– Technical Design Support. The contractor shall support the government in designing solutions to correct system deficiencies and implement government-approved improvements and technological refresh efforts.

This subtask includes the following actions:

5.4.1.1 Technical Support. The contractor shall provide technical support to supplement design activities, including providing information and design reports on specialized software (i.e., software languages, Database Management Software (DBMS), client-server applications, etc.); analyses and evaluations of existing GOTS and COTS packages;

review and evaluation of management, planning, security, audit and other products; attendance at design sessions and generation, evaluation, and modification of design documents. (CDRL A019, A024)

5.4.1.2 Technical and Requirements Planning. The contractor shall assist the government with the development of schedules and implementation plans with definable deliverables, including identification of parallel operations, identification of technical approaches, and a description of anticipated prototype results. The contractor shall plan and participate in Joint Requirements Planning (JRP) sessions, design reviews, and Joint Applications Development (JAD) sessions, both informal and formal. (CDRL A008, A009, A016, A017)

5.4.1.3 System Requirements Review (SRR). The contractor shall determine whether the information technology systems under review have requirements that are fully defined and consistent, and whether traceability of systems’ requirements to higher level requirements and documents has been maintained. The contractor shall analyze to determine whether the system requirements, available technology, and program resources form a satisfactory basis for proceeding in the phase with an acceptable level of risk. The contractor shall perform analyses of requirements including the design, programming, installation, testing, and validation of applications and databases for enterprise use. The contractor shall report the results of its reviews including its findings and recommendations as well as completed Software Requirements Specifications (SRS) documents. (CDRL A001, A002, A008, A009, A010, A011, A012, A014, A019)

5.4.1.4 Preliminary Design Review (PDR). The contractor shall conduct a PDR for each specified programming project. Informal design reviews used to supplement the formal PDR may be held at times agreed to by the Government and the Contractor. (CDRL A001, A002, A008, A009, A010, A011, A012, A014, A019)

5.4.1.5 Design Documents. The contractor shall prepare and provide Software Design Descriptions (SDD), and Interface Design Descriptions (IDD), Requirements Design Packages (RDP), and program cost estimates. (CDRL A010, A011, A012, A019)

5.4.2. Subtask 2-- Software programming. The contractor shall provide programming support for the life-cycle maintenance of the identified applications, including coding and unit testing of software modifications to correct STRs and implement ECPs as authorized per System Release Documents. More detail on the testing requirements is provided in CLIN 0008 (Task 8) - Test and Evaluation (T&E). The contractor shall plan programming and maintenance activities to meet government determined milestones. Other programming actions include:

5.4.2.1 Critical Design Review (CDR). Prior to application coding, the contractor shall participate in a Critical Design Review (CDR) of its proposed design. The CDR shall consist of a review of all documentation [i.e. – requirements, system specification, user feedback, beta software, and other similar or related documentation. and resources, as well as verify that all plans [i.e. – implementation plan, project plan, test plan, risk management plan] are completed to an acceptable level. In addition, the government team will verify that the contractor’s design is in compliance with the following requirements: Information Assurance (IA), Enterprise Architecture (EA), and Configuration Management (CM). The contractor shall ensure that the detail design is in accordance with the project’s specifications and that the design solution can meet the stated performance requirements within cost (project budget), schedule, risk and other system constraints. It will also ensure that the detailed design will meet all project performance and functional requirements. Finally, the contractor shall ensure that the project is ready for integration testing. The CDR will verify that each of these requirements has been met by the contractor. The contractor shall prepare and deliver CDR minutes. The contractor will not be authorized to proceed further with the design and programming process, until successful completion of the CDR. (CDRL A001, A002, A010, A011, A012, A019)

5.4.2.2 Detail Design Activities. The contractor shall provide detailed systems design for government review and approval including detailed data and process models, program specifications, interface specifications and documentation, screen and report designs, prototypes, testing, program control specifications, structure charts, module definitions, either compile or build units, data usage definitions, networking or teleprocessing considerations, and hardware and network architecture, as well as lifecycle management and certification (e.g. Risk Management Framework, etc.). The contractor shall: establish detailed systems architecture, design database and file structures, finalize input and output designs, define special design considerations, define program design specifications, finalize test, conversion, and implementation plans, and perform simultaneous documentation of development for certification process requirements. (CDRL A010, A011, A012)

5.4.2.3 Update applicable databases to support software programming activities. The contractor is required to manage the separate database instances throughout an application’s life cycle. (CDRL A012, A015)

5.4.3 Subtask 3-– System Installation. The contractor shall support all system and application installation efforts and identify and resolve inter-operating issues with new releases and interfaces. Software installation entails all efforts required to move a system or application out of the test/development environment into the production environment.

(CDRL A015, A016)

5.4.4 Subtask 4-– Test and Evaluation (T&E). The contractor is responsible for planning, coordinating, and executing unit and integration testing. (CDRL A017, A018, A023)

5.4.5 Subtask 5-- Applications Maintenance and Sustainment. The contractor shall provide support services for maintenance of standard/common/migration applications to include analysis of problem or change requests, preparation of resource estimates and schedules to effect necessary changes, design and code changes, conduct testing of all changes, complete and update all documentation affected by the required changes to include Software Version Descriptions (SVD); and coordinate change implementation through obtaining Government approvals and providing user notifications. The Contractor shall provide software developers with experience in various 4th generation programming languages and database systems that will operate on platforms to include MS Windows, Unix, and Linux (See Attachment 02 - Technical Requirements). Plan and schedule system maintenance activities based upon Government determined milestones. (CDRL A008, A009, A10, A011, A012, A013, A014, A015, A016, A017, A018, A019, A024)

5.4.5.1 Trouble Ticket Resolution. The Contractor shall resolve software trouble tickets, incorporate required software changes resulting from information security alerts, perform regular database analyses and maintenance, and make changes to ensure existing software functions continue to operate within the desired maintenance processes.

The contractor shall provide cost, schedule, and resource availability estimates for STRs, ECPs or DMRs. (CDRL A024)

5.4.5.2 Interface Support. The contractor shall provide interface support services for systems having interfaces with Government applications. The contractor shall assist in alteration activities with external systems to ensure minimal interruption to system functionality and shall provide coordination with other agencies in the troubleshooting of application related client and server anomalies and assist in the resolution of these problems.

5.4.5.3 File support. The contractor shall develop, deliver, and maintain the “makefiles” used to build the applicable executables and the support files used to prepare the release packages for solutions to STRs, ECPs, and DMRs.

(CDRL A013)

5.5 Task 5 - Software Research and Prototyping. The contractor shall perform market research activities by assessing market conditions, developing and deploying prototypes, providing prototype support, and supplying analysis of non-corporate software for use in the ship maintenance community.

5.5.1 Subtask 1-- Market Conditions. The contractor shall assist the government in researching current market conditions and provide advice and recommendations on the use of COTS products to help streamline Navy Shore Maintenance Activities. The contractor shall focus on leveraging the best commercial off-the-shelf (COTS) solutions, open systems, and web services to meet the needs of the Navy Maintenance Community. This effort may include evaluation of new software development, performance monitoring, tuning, testing, and capacity planning tools, including product research, product analysis and product benchmarking. (A019)

5.5.2 Subtask 2-- Prototype Programming and Deployment. The contractor shall assist the government in providing definition, programming, tailoring, installation, testing, evaluation, operation, and training of prototype systems and services. This requirement may cover the entire life-cycle of a prototype from initial knowledge engineering and user requirements identification through prototype evolution or any part thereof to provide an operational product that supports evolving mission requirements. (A019)

5.5.3 Subtask 3-– Prototype Support. The strategy to provide plug and play services requires the operation and maintenance of prototype applications and databases. The contractor shall maintain prototype applications and databases and analyze them to determine optimal cross-functional solutions for integration concepts and problems integral to the integration process.

5.5.4 Subtask 4-- Technical Consulting Support. The contractor shall provide support including expert analysis of non-corporate software for the purpose of evaluating its effectiveness to satisfy shore based maintenance requirements. The contractor shall provide evaluation and recommendations, for selection of commercial and Government-owned products identified by Government management, technical working groups, or users. The contractor shall evaluate, advise, and assist in the development of conceptual implementation plans for new software.

5.6 Task 6 - Information and Software Engineering. The contractor shall provide technical input, advice, and recommendations in the areas of data architecture development, data management strategies, integration strategies, data migration implementation planning, Server DBA support, System Backups, and Trouble Ticket Resolution.

5.6.1 Subtask 1-- Data Architecture Development. The contractor shall identify and evaluate functional data architectures in accordance with the Department of Defense Architecture Framework 2.0 (DOD-AF 2.0) guidelines.

(See the NMMES Systems Engineering Plan, Exhibit B-2) (CDRL A006)

5.6.2 Subtask 2-- Data Management Strategy Development. The contractor shall identify and recommend methodologies for centralized management of distributed database environments, functional processes to identify single data entry points, and opportunities for data reuse by other standard/common /migration systems and applications. (CDRL A006, A019)

5.6.3 Subtask 3-- Cross-Functional Integration Strategy Development. The contractor shall evaluate functional areas and their associated standard/common /migration systems to identify and recommend opportunities for cross-functional data integration and data sharing. (CDRL A006, A019)

5.6.4 Subtask 4-- Implementation Planning. The contractor shall develop and recommend transition plans for the implementation of data migration strategies developed under this task area. The contractor shall perform preliminary development tasks during system design to ensure that technical specifications and designs are feasible, meet defined requirements, and effectively achieve the desired quality standards. These preliminary development tasks may include the development and demonstration of prototypes, models or proofs. (CDRL A015, A019)

5.6.5 Subtask 5-– Implementation Support. The contractor shall provide implementation of enterprise services including the identification and evaluation of interim and target functional and data architectures to support the core services; identification of methodologies for centralized management of distributed database environments;

identification of opportunities for cross-functional data integration and data sharing; and the development of transition plans for the implementation of data migration strategies. The contractor’s identification of interim and target functional data architectures shall include identification and evaluation of open systems standards; standard modeling and software engineering tools; process and simulation models; logical, functional and physical data models; and data elements targeted for standardization. (CDRL A006, A015, A019)

5.7 Task 7 - Product Integration. The contractor shall provide product integration services to assemble information technology products from separate components. This includes all actions from assisting the Government to develop the business case and mission statement to assisting the Government to develop the target architecture and integration strategies.

5.7.1 Subtask 1-- Mission Statement /CONOPS Alignment. The Contractor shall analyze mission statements and recommend actions to ensure the needs of the user are met during the process of system rationalization. The contractor shall also recommend amendments or new mission statements for integrated systems. The contractor’s recommended mission statements shall contain a high-level description of the system and clearly define the overall mission for which the fully accredited system will be used. The recommended mission statement shall also ensure the description includes how the system contributes to the mission of the organization. The contractor shall develop and provide a draft Concept of Operation (CONOPS) to explain the basic functioning of the system. (CDRL A006, A019)

5.7.2 Subtask 2-- Interim and Target Architecture. The contractor shall identify, design, submit for Government approval, and implement interim and target architectures, both functional and technical. The contractor shall identify the standards for compliance to include a description of services for managing, formatting, and exchanging data.

(CDRL A006)

5.7.3 Subtask 3-- Integration and Migration Strategy Development. The contractor shall analyze current support requirements and capabilities in relation to existing functions, operations, technology, and technical trends. Using the resultant information, the contractor shall develop recommended strategies for the migration of support from its current base to an integrated functional and technical structure that meets customer requirements. Integration strategy development encompasses consideration of:

* Number of applications/systems

* Number of installations

* Current technical architecture

* Connectivity

* Degree of integration

* Degree of compliance with existing DoD and Federal agency standards and guidelines

* Performance requirements

* Contract vehicles

* Functional requirements

* Current functional process improvements

* Current system programming projects

* Consequences of lost functionality

* Overall implementation risk

(CDRL A015, A019)

5.7.4 Subtask 4-– Application Rationalization Support. The contractor shall support government rationalization efforts to reduce the number of applications in the corporate portfolio. Application rationalization assistance efforts under this contract will be to satisfy requirements derived from sustainment needs or DoD/DoN IT initiatives. This process involves end-to-end analysis of the application or system portfolio in each functional domain, identifying the overlapping functionalities, unused applications, and system bottlenecks. Such analysis requires ascertaining the relationship of each asset to process, function, capability, data input, and data output.

5.8 Task 8 - Test and Evaluation (T&E). The contractor shall perform unit testing and integration testing and provide support for the remaining government testing efforts. This effort includes the development of test plans, writing of test scripts, submission of test plans and scripts for Government approval, and problem resolution resulting from issues discovered during any level of testing. All T&E activities shall be executed in accordance with the guidance in the PMP and Test and Evaluation Strategy (TES).

NOTE: The contractor’s Test and evaluation team must be separate and independent from the programming team.

Test and evaluation activities must maintain independence from the programming team to eliminate any bias in the test and evaluation results. The contractor is required to follow the T&E requirements in the DPO TES.

5.8.1 Subtask 1-- Technical Tasks. The contractor shall provide technical support to early operational assessments, developmental testing, operational testing, and evaluation of IT systems. The nature of the Testing Team mission is all inclusive and the unique test and evaluation support requirements will be detailed separately. The contractor shall submit a Test Plan to the Government for approval in accordance with CDRL A017 and the guidance in the DPO

TES.

5.8.2 Subtask 2-– Testing Documentation. The contractor shall develop, deliver, and maintain testing documentation of the testing process and results. Testing artifacts include the documentation described in Paragraphs 5.8.2.1 through 5.8.2.8 below. Testing artifacts and documentation shall be maintained within the DPO SDLC tools. (CDRL A017, A018, A023)

5.8.2.1 Test Plan. The contractor shall provide a Test Plan for the project which shall define tests, testing techniques, and a test schedule suitable for each application’s requirements to support the contractor’s responsibility for Unit Testing (Component Testing) and Integration Testing. The contractor shall develop and maintain Testing Documentation. The contractor shall develop and maintain the following documents and testing artifacts:

5.8.2.2 Test Cases. The contractor shall develop and update IT test cases, test procedures, and test scripts for each system’s, modules/ subsystems, and scenarios for all Engineering Change Proposals (ECPs), System Improvement Requests (SIRs), defects and enhancements. Test cases shall ensure traceability to SIRS/defects/enhancements and requirements specifications and enable mapping of software to the test case. (CDRL A017, A023)

5.8.2.3 Test Schedules. The contractor shall provide integrated test schedules for multi-phased testing. Test schedules shall include test planning functions, test configuration functions for preparation of the test platforms, test development function for development and revision of test cases, and test execution functions. Test schedules must include milestones for required System Engineering reviews. (CDRL A017, A023)

5.8.2.4 Test Status reports. The contractor shall provide test status reports. Test Reports shall include test metrics identifying the number of test cases planned for testing, number of test cases actually executed by the test team, number and percentage of test cases passed, and the number and percentage of test cases that failed testing. Metrics will address testing progress of each application’s user access controls, modules, subsystems, and functional roles.

(CDRL A021)

5.8.2.5 Requirements Traceability Matrix (RTM). The contractor shall provide a test requirements traceability matrix. The Traceability Matrix is a tool to show the relationship between functional requirements and actual test cases developed to test the requirement. At a minimum, each functional requirement shall have a single test case linked to the requirement to evaluate functionality. (CDRL A017, A018, A019, A023)

5.8.2.6 Test logs. The contractor shall document the outcome of each test with applicable configuration and pass/fail data. (CDRL A018)

5.8.2.7 Test Summary Report. Upon conclusion of Integrated Testing, the contractor shall prepare and…